WO2013009229A1 - Gestion d'ensembles de valeurs attribués à des dispositifs sans fil - Google Patents

Gestion d'ensembles de valeurs attribués à des dispositifs sans fil Download PDF

Info

Publication number
WO2013009229A1
WO2013009229A1 PCT/SE2011/050946 SE2011050946W WO2013009229A1 WO 2013009229 A1 WO2013009229 A1 WO 2013009229A1 SE 2011050946 W SE2011050946 W SE 2011050946W WO 2013009229 A1 WO2013009229 A1 WO 2013009229A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless device
keep
management server
timer period
subscriber management
Prior art date
Application number
PCT/SE2011/050946
Other languages
English (en)
Inventor
Shinta Sugimoto
Toshikane Oda
Ryoji Kato
Johan Hjelm
Shingo Murakami
Original Assignee
Telefonaktiebolaget L M Ericsson (Publ)
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 Telefonaktiebolaget L M Ericsson (Publ) filed Critical Telefonaktiebolaget L M Ericsson (Publ)
Priority to PCT/SE2011/050946 priority Critical patent/WO2013009229A1/fr
Publication of WO2013009229A1 publication Critical patent/WO2013009229A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
    • H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28—Timers or timing mechanisms used in protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30—Security of mobile devices; Security of mobile applications
    • H04W12/35—Protecting application or service provisioning, e.g. securing SIM application provisioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/76—Group identity

Definitions

  • the present invention relates to allocation of value sets used for accessing a network to a group of wireless devices.
  • wireless devices have an IC card called a Universal Integrated Circuit Card (UICC) which stores a
  • SIM Subscriber Identity Module
  • the SIM includes unique data or a value set for a wireless device having the SIM, such as an International Mobile Subscriber
  • IMSI International Mobile Subscriber Identity
  • secret value a secret value
  • M2M Machine to Machine
  • MCIM Machine Communication Identity Module
  • an MCIM is used to indicate a value set necessary for accessing the home network, such as an IMSI and a secret value.
  • the M2M is suitable for applications which use a large number of wireless devices such as water or electronic metering or traffic supervising using cameras. In such applications, wireless devices do not need to connect to the home network permanently.
  • each wireless device may connect to the home network and transmit data for a certain period of time.
  • all wireless devices need to be provisioned independently and obtain their own MCIM for connecting to the home network, even though all wireless devices do not transmit data simultaneously.
  • the present invention provides a subscriber management server and a wireless device for obviating above mentioned disadvantages and sharing the value sets used for accessing a network by a group of
  • a subscriber management server for managing value sets, which are allocated to wireless devices in a group and used by the wireless devices for accessing a network.
  • the subscriber management server includes: a storage unit configured to store data indicating an allocation status of each value set in the group; a keep-alive unit configured to transmit a response signal to a wireless device in response to receiving a keep-alive signal from the wireless device, a value set being allocated to the wireless devices; an allocation unit configured to change the allocation status of the value set from allocated to unallocated if the keep- alive signal is not received from the wireless device within a receive timer period; and a timer
  • determination unit configured to determine the receive timer period; wherein the keep-alive unit is further configured to transmit the receive timer period to the wireless device using the response signal.
  • the timer determination unit may be
  • the value included in the keep-alive signal may be
  • the receive timer period may be greater than the detach timer value.
  • timer determination unit may become longer as a number of unallocated value sets in the group becomes larger.
  • a wireless device which uses a value set allocated by a subscriber management server to access a network.
  • the wireless device includes: a keep-alive unit configured to transmit a keep-alive signal to the subscriber management server while the value set is allocated to the wireless device; and a communication unit configured to stop using the value set if a response signal of the keep-alive signal is not
  • acknowledgment timer period is determined based on a first value indicated from the subscriber management server .
  • the first value may be a receive timer period included in the response signal
  • acknowledgment timer period may be shorter than the receive timer period by the predetermined period.
  • a method, in a subscriber management server for managing value sets, which are allocated to wireless devices in a group and used by the wireless devices for accessing a network.
  • the method includes the steps of: transmitting a response signal to a wireless device, to which a value set is allocated, in response to
  • the wireless device receiving a keep-alive signal from the wireless device; and deallocating the value set from the wireless device if the keep-alive signal is not received within a receive timer period from the wireless device; wherein the subscriber management server determines the receive timer period and informs the wireless device of the receive timer period using the response signal.
  • a method, in a wireless device for managing a value set allocated by a subscriber management server to access a network.
  • the method includes the steps of:
  • FIG. 1 shows a system according to an embodiment of the present invention
  • FIG. 2 is a block diagram of a subscriber management server according to an embodiment of the present invention.
  • Fig. 3 is a table indicating allocation statuses of MCIMs in a group according to an embodiment of the present invention
  • FIG. 4 is a block diagram of a wireless device according to an embodiment of the present invention .
  • Fig. 5 is a flow chart of allocating an MCIM to a wireless device according to an embodiment of the present invention.
  • Fig. 6 shows a part of an MCIM request message according to an embodiment of the present invention .
  • Fig. 7 shows a part of an MCIM response message according to an embodiment of the present invention .
  • Fig. 8 is a sequence diagram of a keep- alive mechanism according to an embodiment of the present invention.
  • Fig. 9 shows an exchange of timer periods in a keep-alive mechanism according to an embodiment of the present invention.
  • Figs. 10, 11 and 12 are exemplary sequence diagrams among a wireless device, subscriber management server and a home network.
  • a certain number of value sets used for accessing a network are shared by a group of wireless devices.
  • K MCIMs which will be referred to as an MCIM pool, can be shared by the N wireless devices.
  • the operator of the home network can conserve network resources, that is, MCIMs, and the owner of the group of wireless devices can save on costs, because the number of subscribed wireless devices can be reduced from N to K.
  • Fig. 1 shows an exemplary embodiment of a system according to the present invention.
  • the system includes N wireless devices 1, a subscriber management server 2 and a home network 3 of wireless devices 1.
  • the N wireless devices 1 belong to the same group and share an MCIM pool including K MCIMs, where K ⁇ N.
  • Each MCIM includes values necessary for accessing the home network, such as an IMSI and a secret value.
  • IMSI IMSI
  • secret value a value necessary for accessing the home network
  • a subscriber management server 2 is provided for managing the MCIM pool.
  • the subscriber management server 2 is, for example, deployed and operated by the Registration Operator, which handles MCIM provisioning in accordance with the 3GPP TR 33.812. However, the subscriber management server 2 may be deployed and operated by any network operators .
  • the communication between wireless devices 1 and the subscriber server 2 is indicated as independent from the communication between wireless devices 1 and the home network 3. However, the wireless devices 1 may communicate with the
  • the wireless devices 1 may attach to the home network 3 via one or more other networks and/or a network which deploys and operates the subscriber management server 2.
  • FIG. 2 is a block diagram of the subscriber management server 2 according to an embodiment of the present invention.
  • a storage unit 21 stores a database of assignable MCIMs, that is, MCIM pools, for each group and their statuses, that is, allocated or
  • the storage unit 21 stores MCIM allocation statuses for two MCIM groups #1 and #2.
  • Fig. 3 shows the MCIM allocation statuses for the group #1 shown in Fig. 1, which includes N wireless devices 1 and shares K MCIMs. According to Fig. 3, MCIMs #1, #4 and #K are allocated to wireless devices 1 in the group, and MCIMs #2 and #3 are not allocated.
  • the subscriber management server 2 determines the group of each
  • wireless device 1 based on, for example, a device identifier such as International Mobile Equipment
  • the subscriber management server 2 To determine the group based on the IMEI, the subscriber management server 2 also has a database indicating a relation between the group and the IMEI, which is not shown in Fig. 2. Instead of determining the group based on the device identifier, the wireless device 1 may send the group identifier in each message to the subscribe management server 2.
  • IMEI IMEI
  • the wireless device 1 may send the group identifier in each message to the subscribe management server 2.
  • a keep-alive unit 22 manages a keep-alive mechanism which is described in more detail later.
  • the keep-alive unit 22 transmits a response signal or message called an acknowledgement signal or message to the wireless device 1.
  • An allocation unit 23 manages allocation statuses of each MCIM pool. More specifically, if a request signal or message for MCIM is received from a wireless device 1, the allocation unit 23 determines the group of the wireless device 1, confirms the
  • allocation statuses of the group stored in the storage unit 21 allocates unallocated MCIM to the wireless device 1, and updates the allocation statuses stored in the storage unit 21. If a keep-alive signal is not received within a predetermined period called a receive timer period from the wireless device 1, to which an MCIM is allocated, the allocation unit 23 deallocates the allocated MCIM from the wireless device 1, and updates the allocation status of the MCIM stored in the storage unit 21 from allocated to unallocated.
  • a timer determination unit 24 determines timer periods used in the keep-alive mechanism.
  • the storage unit 21 may be a memory such as a random access memory or flash memory or may be a hard-disk drive apparatus.
  • the keep-alive unit 22, the allocation unit 23 and/or the timer determination unit 24 may be realized using a processor, which is
  • management server 2 may be implemented by software, hardware or a combination of software and hardware.
  • Fig. 4 is a block diagram of each wireless device 1.
  • a storage unit 11 may be a memory such as a random access memory or flash memory.
  • a keep-alive unit 12, a communication unit 13 and/or a remote provisioning unit 14 may be realized using a processor, which is programmed by a program. In other words, by running the program on the processor, the function of the keep-alive unit 12, the communication unit 13 and/or the remote provisioning unit 14 can be realized.
  • each unit of the wireless device 1 may be implemented by software, hardware or by a combination of software and hardware.
  • the storage unit 11 stores some MCIMs in the MCIM pool. These MCIMs are ones, which the
  • wireless device 1 used before or is currently using.
  • the MCIM #1 and #5 are stored in the storage unit 11.
  • the keep-alive unit 12 manages the keep- alive mechanism while an MCIM is allocated to the wireless device 1.
  • a communication unit 13 handles communication via the home network 3 while the MCIM is allocated.
  • the remote provisioning unit 14 manages whether or not the wireless device 1 has a usable MCIM. In other words, the remote provisioning unit 14
  • the remote provisioning unit 14 initiates an MCIM allocation procedure in accordance with an exemplary embodiment as shown in Fig. 5.
  • step SI of Fig. 5 the remote
  • the provisioning unit 14 of the wireless device 1 sends an MCIM permission request message to the subscriber management server 2.
  • the MCIM permission request message includes information, which indicates candidate MCIMs selected from MCIMs stored in the storage unit 11.
  • the candidate MCIMs may be indicated by IMSI. If there is no MCIM in the storage unit 11, a candidate field is null. If a candidate field includes a plurality of candidate MCIMs, it may be in descending order of preference.
  • the duration fields of the MCIM permission request message carry start and end times regarding a usage of the MCIM. It is possible to specify only a start or end time. Further, start or end times may be set to null, which means no start or end time is specified at the time.
  • a regularity field carries information regarding whether or not the wireless device 1 uses the MCIM repeatedly. If the wireless device 1 uses the MCIM repeatedly, information
  • indicating a frequency may be also included in the regularity field.
  • the allocation unit 23 of the subscriber management server 2 receives the MCIM permission request message and checks the group of the wireless device 1, which sends the MCIM permission request message, for example, based on the IMEI. Then, the allocation unit 23 confirms an allocation status of each of the candidate MCIMs in the MCIM permission request message using the database in the storage unit 21. After this, the allocation unit 23 transmits an MCIM permission response message to the wireless device 1, and the wireless device 1 receives the MCIM
  • the MCIM permission response message includes a candidate MCIM field, which is a copy of the same field in the MCIM permission request message.
  • a permission field of the MCIM permission response message carries information indicating "denied” or "accepted” for each candidate MCIM.
  • a reason field carries information indicating a reason why the candidate MCIM is indicated as "denied” in the permission field.
  • candidate MCIM cannot be allocated.
  • the reason will be that the MCIM is already used by another wireless device 1.
  • other reasons can be specified for operation and/or maintenance purpose.
  • step S3 the remote provisioning unit 14 confirms whether or not at least one MCIM is accepted. If not, the remote provisioning unit 14 initiates an MCIM remote provisioning procedure with the subscriber management server 2 in step S5. In step S5, the remote provisioning unit 14 sends a request message to the subscriber management server 2. In response to receipt of the request message, the allocation unit 23 of the subscriber management server 2 allocates one
  • the communication unit 14 can start
  • the allocation unit 23 informs the wireless device 1 that no MCIM can be allocated to it.
  • step S3 If at least one MCIM is accepted in step S3, the remote provisioning unit 14 selects one MCIM among the accepted MCIMs in step S4, and informs the
  • the allocation unit 23 of the subscriber management server 2 updates the allocation statuses stored in the storage unit 21 based on the information from the wireless device 1.
  • the communication unit 14 can start communication via the home network 3 using the selected MCIM.
  • the subscriber management server 2 reports "denied” or "accepted” for each candidate MCIM, and the wireless device 1 selects one MCIM from among the accepted MCIMs.
  • the subscriber management server 2 may select one MCIM from among the candidate MCIMs, and inform the wireless device 1 of the selected MCIM.
  • Fig. 8 shows a sequence diagram of the keep-alive mechanism between the wireless device 1 and the subscriber management server 2 according to an embodiment of the present invention.
  • the keep-alive unit 12 of the wireless device 1 periodically transmits a keep-alive signal to the subscriber management server 2 while one MCIM is allocated to the wireless device 1, and the keep-alive unit 22 of the subscriber management server 2 transmits an acknowledgment signal (ACK) to the wireless device 1 in response to receiving the keep-alive signal.
  • ACK acknowledgment signal
  • the keep-alive mechanism three timer periods are managed and maintained.
  • the first one is a send timer period.
  • the send timer period indicates the interval between keep-alive signals as shown in Fig. 8.
  • the keep-alive unit 12 transmits a keep-alive signal every send timer period.
  • the second timer period is a receive timer period, which is used by the allocation unit 23 of the subscriber management server 2. If the subscriber management server 2 does not receive the keep-alive signal within the receive timer period, the allocation unit 23 deallocates the MCIM allocated to the wireless device 1, and updates the allocation status of the MCIM stored in the storage unit 21 from allocated to
  • the third timer period is an ACK timer period, which is used by the communication unit 13 of the wireless device 1. If the wireless device 1 does not receive the ACK signal within the ACK timer period, the communication unit 13 considers the allocation of the MCIM to no longer be valid, and stops transmitting signals to the home network 3. If the wireless device 1 needs to transmit data to the home network 3, the remote provisioning unit 14 initiates the MCIM
  • the wireless device 1 transmits a keep-alive signal to the subscriber management server 2 in steps S40 and S42, and the subscriber management server 2 transmits an ACK signal to the wireless device 1 in steps S41 and S43 in response to receipt of the keep-alive signal in steps S40 and S42.
  • the keep-alive signal transmitted from the wireless device 1 does not reach the subscriber
  • step S44 the wireless device 1 stops using the MCIM and communicating via the home network 3 because the ACK timer period has expired.
  • step S46 the subscriber management server 2 deallocates the MCIM from the wireless device 1 because the receive timer has period expired .
  • the receive timer period is longer than the send timer period.
  • the receive timer period may be set 2 or 3 times longer than a send timer period.
  • the ACK timer period is shorter than the receive timer period by a predetermined period, for example, by several minutes. This ensures that an MCIM, whose status is unallocated at the subscriber
  • management server 2 is not used by the wireless device 1 for communication via the home network 3.
  • the keep-alive signal may be exchanged in higher-layer protocols above the IP layer. For example,
  • the keep-alive signal can be an HTTP request message (e.g., HTTP POST) and the acknowledgment signal can be an HTTP response message.
  • HTTP request message e.g., HTTP POST
  • acknowledgment signal can be an HTTP response message.
  • the advantage of the keep-alive mechanism is that the subscriber management server 2 is able to determine which MCIMs can be revoked. In the absence of the keep-alive mechanism, it is very difficult for the subscriber management server 2 to differentiate between an MCIM which is being used by a wireless device 1 from one which is not.
  • timer periods affect the efficiency of re-cycling MCIMs in the MCIM pool. If these timer periods are too short, re-allocation of MCIMs may occur frequently among the MCIM pool. This may be cumbersome for the user of the wireless device 1 because each re ⁇ allocation of an MCIM causes disruption in
  • the wireless device 1 and the subscriber management server 2 negotiate values of these timer periods to maximize the usage efficiency of the MCIM pool as shown in Fig. 9.
  • the wireless device 1 transmits a proposed send timer period and a proposed receive timer period using the keep-alive signal.
  • the subscriber management server 2 determines the send timer period and the receive timer period based on the proposed values from the wireless device 1, and
  • the wireless device 1 proposes 38 minutes for the send timer period and 116 minutes for the receive timer period, and the subscriber management server 2 determines 60 minutes for the send timer period and 150 minutes for the receive timer period.
  • the ACK timer period is not included in the keep-alive and the ACK signals. This is because the ACK timer period may be automatically determined from the determined receive timer period, because it is shorter than the receive timer period by the predetermined period, for example, by 5 minutes. However, it is possible to exchange a proposed and determined ACK timer period in the keep-alive signal and the ACK signal. Further, in Fig. 9, both the send and receive timer periods are exchanged. However, said exchange may include the send timer period or the receive timer period, in which case one value is determined from the other value. For example, only the receive timer period may be exchanged, in which case the send timer period is determined by dividing the receive timer period by a predetermined number.
  • the wireless device 1 uses the send timer period determined by the subscriber management server 2 and the ACK timer period obtained from the receive timer period determined by the subscriber management server 2.
  • the communication unit 13 of the wireless device 1 determines a proposed receive timer period based on a detach timer value such as the implicit detach timer specified in 3GPP TS 24.008.
  • the detach timer indicates a period used by a network to determine whether or not the wireless device is attached to the network. More specifically, if the routing area update signal is not received from the wireless device 1 within a period specified by the detach timer, the network determines that the wireless device 1 is not attached to the network.
  • the receive timer period may be greater than the detach timer, which is specified by the home network 3 and reported to the wireless device 1 connecting to the home network 3. More specifically, the receive timer period may be set to a value 2 or 3 times longer than the detach timer.
  • the communication unit 13 of the wireless device 1 sends a detach request signal to the home network 3 to detach from the home network 3, and then stops using the MCIM after completing the detach procedure with the home network 3. This avoids the contradictory situation described above.
  • the wireless device 1 informs the subscriber management server 2 of the proposed receive timer period, which is determined based on the detach timer.
  • the proposed receive timer period may be set to a value 2 or 3 times longer than the detach timer.
  • the wireless device 1 may take into account other parameters such as a device type or usage in order to determine the proposed receive timer period because the frequency of data transmission depends on the device type or usage. For example, the wireless device 1 may propose a shorter receive timer period if the wireless device 1 transmits short burst data with a long interval.
  • the timer determination unit 24 of the subscriber management server 2 determines the receive timer period based on the proposed receive timer period, and preferably the determined receive timer period is greater than the detach timer value. To determine the receive timer period and send timer period, the timer value determination unit 24 of the subscriber
  • the registration server 2 may consider the availability of MCIMs in the MCIM pool, which are only known to the subscriber management server 2. If the number of unallocated MCIMs becomes larger, the timer value determination unit 24 may set longer receive timer periods in order to reduce overhead communications.
  • the timer value determination unit 24 may set shorter receive timer periods in order to avoid
  • determination unit 24 facilitates MCIM recycling by shortening the receive timer period in cases where the number of unallocated MCIMs becomes smaller.
  • determination unit 24 may use the proposed receive timer period as the determined receive timer period when the number of unallocated MCIMs for the group is very low, and use receive timer periods longer than the proposed receive timer period as the determined receive timer period when the number of unallocated MCIMs for the group is high.
  • the wireless device 1 decides the proposed receive timer period based on the detach timer value and/or device type or usage, and transmits the proposed receive timer period to the subscriber management server 2.
  • the wireless device 1 may transmit the detach timer value, device type or usage to the subscriber management server 2 directly.
  • the subscriber management server 2 decides timer periods based on these values from the wireless device 1 and the availability of MCIMs in the MCIM pool .
  • Figs. 10 and 11 show an exemplary sequence among the wireless device 1, the subscriber management server 2 and the home network 3.
  • management server 2 is omitted from figures for
  • step S10 of Fig. 10 the wireless device
  • step Sll the wireless device 1 transmits a keep-alive signal to the subscriber management server 2.
  • step Sll the wireless device 1 performs a routing area update procedure.
  • step S12 the wireless device 1 moves into an area from which it cannot connect to the subscriber management 2. Thus, keep-alive messages do not reach the subscriber management 2.
  • step S13 the wireless device 1 returns to an area from which it can connect to the subscriber management 2, and transmits a keep-alive signal.
  • the wireless device 1 retransmits the keep-alive signal in step S13 after it returns to the coverage area while the send timer period has not expired in step S13.
  • step S12 This is because the wireless device 1 recognizes in step S12 that it is outside of the coverage area.
  • the wireless device 1 may only transmit a single keep-alive signal for each send timer period, and may not transmit a keep-alive signal in step S13.
  • step S14 the wireless device 1 performs a routing area update.
  • steps S15 and S16 the wireless device 1 transmits a keep-alive signal to the subscriber management server 2.
  • step S17 the wireless device 1 performs a routing area update procedure with the home network 3.
  • step S18 the wireless device 1 is turned off by the user.
  • step S19 the wireless device 1 is detached from the home network 3 due to expiration of the detach timer. That is, the home network 3 cleans up the mobility management state regarding the wireless device 1.
  • step S20 the subscriber management server 2 deallocates the MCIM assigned to the wireless device 1 from the wireless device 1 due to expiration of the receive timer period.
  • the allocation unit 23 changes the allocation status of the MCIM, which is allocated to the wireless device 1, from allocated to unallocated.
  • deallocation of the MCIM by the subscriber management server 2 happens after detachment from the home network 3.
  • step S21 of Fig. 11 the wireless device 1 is turned on.
  • the wireless device 1 is configured to determine that there is no allocated or valid MCIM for the wireless device 1 after power-on.
  • the wireless device 1 performs an IMSI attach procedure and a PDP context activation procedure with the subscriber management server 2 in steps S22 and S23, in accordance with the 3GPP TS 23.060.
  • the wireless device 1 is configured to revert to a predetermined network, that is, to the network that operates the subscriber
  • the wireless device 1 performs the IMSI attach
  • the wireless device 1 may perform these procedures with other apparatuses in a network, which operates the subscriber management server 2.
  • step S24 the wireless device 1
  • step S25 the subscriber management server 2 transmits an MCIM permission response message to the wireless device 1 in response to the MCIM permission request message.
  • the one MCIM is allocated to the wireless device 1 in step S25.
  • steps S26 and S27 the wireless device 1 performs an IMSI attach procedure and a PDP context activation procedure with the home network 3 in accordance with the 3GPP TS 23.060.
  • step S28 the wireless device 1 begins transmitting a keep-alive signal.
  • Fig. 12 shows another exemplary sequence among the wireless device 1, the subscriber management server 2 and the home network 3.
  • the acknowledgement signal from the subscriber management server 2 is also omitted in Fig. 12 for simplification.
  • step S30 the wireless device 1
  • step S31 the wireless device 1 performs a routing area update procedure with the home network 3.
  • step S32 the wireless device 1 transmits a keep-alive signal to the subscriber
  • step S33 the wireless device 1
  • step S34 the wireless device 1 performs a routing area update procedure with the home network 3.
  • step S35 the ACK timer period expires at the wireless device 1. Therefore, the wireless device 1 transmits a detach request to the home network 3 to initiate a detach procedure with the home network 3, and then the wireless device 1 stops using the allocated MCIM. In other words, the communication unit 13 of the wireless device 1 determines the allocation to be no longer valid and changes the status of the MCIM from allocated to unallocated.
  • step S36 the receive timer period expires at the subscriber
  • management server 2 changes the status of the MCIM allocated to the wireless device 1 to "unallocated".
  • K MCIMs are shared by N wireless devices 1, where K ⁇ N, without requiring any modification to the home network 3. Since the
  • subscriber management server 2 decides the timer periods used for the keep-alive mechanism, the usage efficiency of MCIMs in the MCIM pool is improved and may be maximized.
  • the invention may be achieved by a program, which realizes the functions of the above embodiments.
  • Programs defining functions on the invention can be delivered to the subscriber management server 2 or the wireless device using non-transitory computer-readable storage media or via a network. It should be understood the invention may be implemented by software, hardware or a combination of software and hardware .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un serveur de gestion d'abonné servant à gérer des ensembles de valeurs devant être attribués à des dispositifs sans fil d'un groupe. Un serveur de gestion d'abonné comprend : une unité de stockage configurée pour stocker des données indiquant un état d'attribution de chaque ensemble de valeurs dans le groupe ; une unité de maintien de connexion configurée pour émettre un signal de réponse à un dispositif sans fil, auquel un ensemble de valeurs est attribué, en réponse à la réception d'un signal de maintien de connexion en provenance du dispositif sans fil ; une unité d'attribution configurée pour modifier l'état d'attribution de l'ensemble de valeurs d'attribué à non attribué si le signal de maintien de connexion n'est pas reçu en provenance du dispositif sans fil dans une période de temporisation de réception ; et une unité de détermination de temporisation configurée pour déterminer la période de temporisation de réception ; l'unité de maintien de connexion étant en outre configurée pour transmettre la période de temporisation de réception au dispositif sans fil au moyen du signal de réponse.
PCT/SE2011/050946 2011-07-12 2011-07-12 Gestion d'ensembles de valeurs attribués à des dispositifs sans fil WO2013009229A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2011/050946 WO2013009229A1 (fr) 2011-07-12 2011-07-12 Gestion d'ensembles de valeurs attribués à des dispositifs sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2011/050946 WO2013009229A1 (fr) 2011-07-12 2011-07-12 Gestion d'ensembles de valeurs attribués à des dispositifs sans fil

Publications (1)

Publication Number Publication Date
WO2013009229A1 true WO2013009229A1 (fr) 2013-01-17

Family

ID=47506298

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2011/050946 WO2013009229A1 (fr) 2011-07-12 2011-07-12 Gestion d'ensembles de valeurs attribués à des dispositifs sans fil

Country Status (1)

Country Link
WO (1) WO2013009229A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1860832A1 (fr) * 2006-05-24 2007-11-28 Motorola, Inc. Mécanisme keep-alive aux réseaux de communications sans fil UMA-GAN
WO2009092115A2 (fr) * 2008-01-18 2009-07-23 Interdigital Patent Holdings, Inc. Procede et appareil permettant une communication machine-machine
WO2009138820A1 (fr) * 2008-05-15 2009-11-19 Nokia Corporation Procédés, appareils et produits-programmes d'ordinateur permettant d'assurer la coordination de communication entre deux dispositifs
US7739385B1 (en) * 2003-06-16 2010-06-15 Cisco Technology, Inc. Explicit locking of resources in devices accessible on a network
WO2011066409A1 (fr) * 2009-11-25 2011-06-03 Interdigital Patent Holdings, Inc. Pré-enregistrement de communication de type par machine

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7739385B1 (en) * 2003-06-16 2010-06-15 Cisco Technology, Inc. Explicit locking of resources in devices accessible on a network
EP1860832A1 (fr) * 2006-05-24 2007-11-28 Motorola, Inc. Mécanisme keep-alive aux réseaux de communications sans fil UMA-GAN
WO2009092115A2 (fr) * 2008-01-18 2009-07-23 Interdigital Patent Holdings, Inc. Procede et appareil permettant une communication machine-machine
WO2009138820A1 (fr) * 2008-05-15 2009-11-19 Nokia Corporation Procédés, appareils et produits-programmes d'ordinateur permettant d'assurer la coordination de communication entre deux dispositifs
WO2011066409A1 (fr) * 2009-11-25 2011-06-03 Interdigital Patent Holdings, Inc. Pré-enregistrement de communication de type par machine

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and system Aspects; Feasibility study on Remote Management of USIM Application on M2ME Equipment", RELEASE 9. 3GPP TR 32.812 V 1.3.0., February 2009 (2009-02-01), pages 14 - 18 *

Similar Documents

Publication Publication Date Title
CN110402603B (zh) 管理无线通信系统中注册和会话的方法和执行该方法的装置
KR101883418B1 (ko) Ｄ2ｄ 통신에서 제어 평면을 위한 시스템 및 방법
WO2016043561A2 (fr) Procédé et appareil de communication dans un système de communication sans fil qui prend en charge une communication d2d
CN103096290A (zh) 建立设备到设备连接的方法、装置和系统
US20130148526A1 (en) Apparatus and method for controlling group setting in device-to-device communication
CN105264971A (zh) 用于执行针对设备到设备通信的状态转变的方法和装置
CN103024924A (zh) D2d终端的连接建立方法、装置及系统
US10492122B2 (en) Terminal discovery method, terminal, server, base station, management entity, and system
CN103096502A (zh) 建立设备到设备连接的方法、装置和系统
US9357380B2 (en) Subscription module assignment managing server and subscription module assignment managing method
KR20120090456A (ko) 통신시스템에서 단말의 프로파일을 제공하기 위한 시스템 및 방법
CN110677849B (zh) 一种通信终端的隐私保护方法、装置、设备及存储介质
EP2555545B1 (fr) Procédé et système pour sélectionner une entité de gestion de mobilité d'un groupe de terminaux
KR100765182B1 (ko) 이동통신 시스템에서 접근 등급 제한 리스트를 이용한 패킷서비스 상태 제공 장치 및 방법
US9936531B2 (en) Method and device for proximity discovery among UEs
US9148746B2 (en) Method and device for controlling the access of equipment for a network of the machine-to-machine type to the resources of a cellular telephony network
CN105025593B (zh) 一种释放实体的方法及设备
JP2019514245A (ja) 端末デバイス間の関連付けを確立するための方法及びデバイス
CN105210331A (zh) 通信系统、通信定时控制设备、连接控制设备、通信定时控制方法及计算机可读介质
US20190261435A1 (en) Network selection with stateless network functions
WO2013009229A1 (fr) Gestion d'ensembles de valeurs attribués à des dispositifs sans fil
US20150087322A1 (en) Connection procedure for cellular mobile networks
JP6584260B2 (ja) 無線通信システム及び無線通信方法
JP2021114660A (ja) 通信装置、管理装置およびそれらの制御方法
KR20200099949A (ko) 5G 이동통신 시스템에서 셀룰러 IoT 서비스를 위해 단말을 제어하는 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11869328

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11869328

Country of ref document: EP

Kind code of ref document: A1