U.S. patent application number 14/011764 was filed with the patent office on 2013-12-26 for mobility management method, serving gprs support node or mobility management entity, and terminal.
This patent application is currently assigned to Huawei Device Co.,Ltd.. The applicant listed for this patent is Huawei Device Co.,Ltd.. Invention is credited to Hui JIN, Xiaojuan LI, Shuiping Long, Rui WANG.
Application Number | 20130343285 14/011764 |
Document ID | / |
Family ID | 44251789 |
Filed Date | 2013-12-26 |
United States Patent
Application |
20130343285 |
Kind Code |
A1 |
Long; Shuiping ; et
al. |
December 26, 2013 |
MOBILITY MANAGEMENT METHOD, SERVING GPRS SUPPORT NODE OR MOBILITY
MANAGEMENT ENTITY, AND TERMINAL
Abstract
The present invention discloses a mobility management method, a
serving GPRS support node (SGSN) or a mobility management entity
(MME), and a terminal. Setting or dynamically modifying the
mobility management frequency of a particular terminal among
numerous terminals is enabled. The technical solution of the
present invention includes: obtaining subscription data of a
terminal, where the subscription data carries periodic update
setting information; obtaining a periodic update interval of the
terminal according to the periodic update setting information;
sending the periodic update interval to the terminal; and setting a
value that is a longer than the periodic update interval of the
terminal as a mobile reachable interval for monitoring the periodic
update of the terminal.
Inventors: |
Long; Shuiping; (Beijing,
CN) ; WANG; Rui; (Shenzhen, CN) ; JIN;
Hui; (Beijing, CN) ; LI; Xiaojuan; (Beijing,
CN) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Huawei Device Co.,Ltd. |
Shenzhen |
|
CN |
|
|
Assignee: |
Huawei Device Co.,Ltd.
Shenzhen
CN
|
Family ID: |
44251789 |
Appl. No.: |
14/011764 |
Filed: |
August 28, 2013 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
13543604 |
Jul 6, 2012 |
8554233 |
|
|
14011764 |
|
|
|
|
PCT/CN2011/070053 |
Jan 6, 2011 |
|
|
|
13543604 |
|
|
|
|
Current U.S.
Class: |
370/328 |
Current CPC
Class: |
H04W 8/18 20130101; H04W
8/12 20130101; H04W 60/02 20130101; H04W 8/02 20130101 |
Class at
Publication: |
370/328 |
International
Class: |
H04W 8/02 20060101
H04W008/02 |
Foreign Application Data
Date |
Code |
Application Number |
Jan 11, 2010 |
CN |
201010003404.8 |
Claims
1. A mobility management method, comprising: obtaining, by a
service support node, subscription data of a terminal, wherein the
subscription data of the terminal carries periodic update setting
information; obtaining, by the service support node, a periodic
update interval according to the periodic update setting
information; and sending, by the service support node, the periodic
update interval to the terminal, wherein the terminal performs one
or more periodic update according to the periodic update
interval.
2. The method according to claim 1, wherein the obtaining the
subscription data of the terminal comprises: after receiving an
Attach Request message from the terminal, sending an Update
Location message to a subscriber server; and receiving the
subscription data of the terminal from the subscriber server,
wherein the subscription data carries the periodic update setting
information.
3. The method according to claim 1, wherein the obtaining the
subscription data of the terminal comprises: receiving the
subscription data from a subscriber server when the subscriber
server resets the periodic update setting information of the
terminal, wherein the subscription data carries the periodic update
setting information.
4. The method according to claim 1, wherein the periodic update
setting information carried in the subscription data comprises any
one of: a multiplication factor of a regular periodic update
interval; a specified periodic update interval; and an increment
value of a regular periodic update interval.
5. The method according to claim 4, wherein when the periodic
update setting information comprises a multiplication factor of a
regular periodic update interval, the obtaining the periodic update
interval according to the periodic update setting information
comprises: obtaining the regular periodic update interval; and
multiplying the regular periodic update interval with the
multiplication factor to obtain the periodic update interval.
6. The method according to claim 4, wherein when the periodic
update setting information comprises a specified periodic update
interval, the obtaining the periodic update interval of the
terminal according to the periodic update setting information
comprises: using the specified periodic update interval as the
periodic update interval.
7. The method according to claim 4, wherein when the periodic
update setting information comprises an increment value of a
regular periodic update interval, the obtaining the periodic update
interval of the terminal according to the periodic update setting
information comprises: obtaining the regular periodic update
interval; and adding the increment value to the regular periodic
update interval to obtain the periodic update interval.
8. The method according to claim 1, further comprising: setting a
value, which is longer than the periodic update interval of the
terminal, as a mobile reachable interval for monitoring a periodic
update of the terminal.
9. The method according to claim 1, wherein the service support
node is a serving GPRS support node (SGSN) or a mobility management
entity (MME).
10. The method according to claim 1, wherein the subscriber server
is a home location register (HLR) or a home subscriber server
(HSS).
11. The method according to claim 1, wherein the periodic update is
a periodic routing area update (RAU) or a periodic tracking area
update (TAU).
12. A service support node, comprising: a receiving unit,
configured to receive subscription data of a terminal from a
subscriber server, wherein the subscription data of the terminal
carries periodic update setting information; a processor,
configured to obtain a periodic update interval of the terminal
according to the periodic update setting information; a
transmitting unit, configured to transmit the periodic update
interval to the terminal, wherein the terminal performs one or more
periodic update according to the periodic update interval.
13. The service support node according to claim 12, wherein prior
to receiving the subscription data of the terminal form the
subscriber server, the receiving unit is configured to receive an
Attach Request message from the terminal, and the transmitting unit
is configured to transmit an Update Location message to the
subscriber server; and wherein the subscription data of the
terminal is received from the subscriber server in response to the
Update Location message, and the subscription data carries the
periodic update setting information.
14. The service support node according to claim 12, wherein the
subscription data from the subscriber server is received when the
subscriber server resets the periodic update setting information of
the terminal, and wherein the subscription data of the terminal
carries the periodic update setting information.
15. The service support node according to claim 12, wherein the
periodic update setting information carried in the subscription
data comprises any one of: a multiplication factor of a regular
periodic update interval; a specified periodic update interval; and
an increment value of a regular periodic update interval.
16. The service support node according to claim 15, wherein when
the periodic update setting information comprises a multiplication
factor of a regular periodic update interval, the processor is
configured to obtain the regular periodic update interval and
multiply the regular periodic update interval with the
multiplication factor to obtain the periodic update interval of the
terminal; when the periodic update setting information comprises a
specified periodic update interval, the processor is configured to
set the specified periodic update interval as the periodic update
interval of the terminal; and when the periodic update setting
information is an increment value of a regular periodic update
interval, the processor is configured to obtain the regular
periodic update interval and add the increment value to the regular
periodic update interval to obtain the periodic update interval of
the terminal.
17. The service support node according to claim 12, wherein the
periodic update interval is sent to the terminal in one of the
following messages: an Attach Accept message, wherein the Attach
Accept message carries the periodic update interval of the
terminal; and an Update Accept message, wherein the update Accept
message carries the periodic update interval of the terminal.
18. The service support node according to claim 12, wherein the
processor is further configured to set a value, which is longer
than the periodic update interval of the terminal, as a mobile
reachable interval for monitoring a periodic update of the
terminal.
19. The service support node according to claim 12, wherein the
service support node is a serving GPRS support node (SGSN) or a
mobility management entity (MME).
20. The service support node according to claim 12, wherein the
subscriber server is a home location register (HLR) or a home
subscriber server (HSS).
21. The service support node according to claim 12, wherein the
periodic update is a periodic routing area update (RAU) or a
periodic tracking area update (TAU).
22. A mobility management method, comprising: receiving, by a
terminal, a periodic update interval from a service support node,
wherein the periodic update interval is obtained by the service
support node according to periodic update setting information
carried in subscription data of the terminal; and executing, by the
terminal, one or more periodic update according to the received
periodic update interval.
23. The method according to claim 22, wherein the periodic update
setting information in the subscription data of the terminal
comprises any one of: a multiplication factor of a regular periodic
update interval; a specified periodic update interval; and an
increment value of the regular periodic update interval.
24. The method according to claim 22, wherein the receiving the
periodic update interval from the service support node comprises:
sending an Attach Request message to the service support node; and
receiving an Attach Accept message from the service support node,
wherein the Attach Accept message comprises the periodic update
interval.
25. The method according to claim 22, wherein the receiving the
periodic update interval from the service support node comprises:
sending an Update Request message to the service support node; and
receiving an Update Accept message from the service support node,
wherein the Update Accept message comprises the periodic update
interval.
26. The method according to claim 22, wherein the service support
node is a serving GPRS support node (SGSN) or a mobility management
entity (MME).
27. The method according to claim 22, wherein the subscriber server
is a home location register (HLR) or a home subscriber server
(HSS).
28. The method according to claim 22, wherein the periodic update
is a periodic routing area update (RAU) or a periodic tracking area
update (TAU).
29. A terminal, comprising: a receiving unit, configured to receive
a periodic update interval from a service support node, wherein the
periodic update interval is obtained by the service support node
according to periodic update setting information carried in
subscription data of the terminal; and a update executing unit,
configured to execute one or more periodic update according to the
received periodic update interval.
30. The terminal according to claim 29, wherein the terminal
further comprises: a transmitting unit, configured to send an
Attach Request message to the service support node; and wherein the
periodic update interval is received through an Attach Accept
message.
31. The terminal according to claim 29, wherein the terminal
further comprises: a transmitting unit, configured to send a update
Request message to the service support node; and wherein the
periodic update interval is received through an Update Accept
message.
32. The terminal according to claim 29, wherein the service support
node is a serving GPRS support node (SGSN) or a mobility management
entity (MME).
33. The terminal according to claim 29, wherein the subscriber
server is a home location register (HLR) or a home subscriber
server (HSS).
34. The terminal according to claim 29, wherein the periodic update
is a periodic routing area update (RAU) or a periodic tracking area
update (TAU).
35. The terminal according to claim 29, wherein the terminal is a
user equipment or a mobile station.
Description
[0001] This application is a continuation of U.S. patent
application Ser. No. 13/543,604, filed on Jul. 6, 2012, which is a
continuation of International Application No. PCT/CN2011/070053,
filed on Jan. 6, 2011. The International Application claims
priority to Chinese Patent Application No. 201010003404.8, filed on
Jan. 11, 2010. The aforementioned patent applications are hereby
incorporated by reference in their entireties.
FIELD OF THE INVENTION
[0002] The present invention relates to the mobile communication
field, and in particular, to a mobility management method, a
serving general packet radio service (GPRS) support node or a
mobility management entity, and a terminal.
BACKGROUND OF THE INVENTION
[0003] In a conventional mobility management (MM) technology, a
terminal, such as a user equipment (UE) or a mobile station (MS),
performs a periodic routing area update (RAU) or a periodic
tracking area update (TAU) (collectively called periodic update
hereinafter), and a periodic update interval (also known as a
periodic update timer) is controlled by a serving GPRS support node
(SGSN) or a mobility management entity (MME), where the RAU is
performed with the SGSN and the TAU is performed with the MME.
[0004] The SGSN or the MME (collectively called service support
node hereinafter) may send a periodic update timer to the terminal
through an Attach Accept message or an Update Accept message, and
this timer is unique in one routing area (RA) or in one tracking
area identity (TAI) list, that is, all terminals in a certain area
use the same timer.
[0005] The terminal runs the periodic update timer locally, and
upon expiry of the timer, the terminal initiates a periodic update
procedure and restarts the timer. Accordingly, the service support
node has a mobile reachable timer, and the mobile reachable timer
is a little longer than the periodic update timer (for example, 20
seconds or 1 minute longer), and is used for monitoring the
periodic update procedure of the terminal. If the mobile reachable
timer expires, the service support node clears a paging proceed
flag (PPF) to zero, so that the service support node does not
perform terminal paging.
[0006] It has been found that the conventional mobility management
technology as described above cannot set or dynamically modify the
mobility management frequency of a particular terminal among
numerous terminals.
SUMMARY OF THE INVENTION
[0007] Embodiments of the present invention provide a mobility
management method and a service support node, which can set or
dynamically modify the mobility management frequency of a
particular terminal among numerous terminals.
[0008] To achieve the foregoing objective, the embodiments of the
present invention adopt the following technical solution:
[0009] A mobility management method includes: obtaining
subscription data of a terminal, where the subscription data
carries periodic update setting information; obtaining a periodic
update timer of the terminal according to the periodic update
setting information; sending the periodic update timer of the
terminal to the terminal; and setting a value, which is a little
longer than the periodic update timer of the terminal, as a mobile
reachable timer for monitoring a periodic update of the
terminal.
[0010] A service support node includes: a subscription data
obtaining unit, configured to obtain subscription data of a
terminal, where the subscription data carries periodic update
setting information; a timer obtaining unit, configured to obtain a
periodic update timer of the terminal according to the periodic
update setting information; a timer sending unit, configured to
send the periodic update timer of the terminal to the terminal; and
a setting unit, configured to set a value, which is a little longer
than the periodic update timer of the terminal, as a mobile
reachable timer for monitoring a periodic update of the
terminal.
[0011] The mobility management method and the service support node
according to the embodiments of the present invention obtain the
periodic update setting information of the network with respect to
the terminal through the subscription data, obtain the periodic
update timer of the terminal according to the periodic update
setting information, and send the periodic update timer to the
terminal, and meanwhile set a value, which is a little longer than
the periodic update timer of the terminal, as a mobility reachable
timer for monitoring the periodic update of the terminal, thereby
achieving the objective of setting or dynamically modifying the
mobility management frequency of a particular terminal, and solving
the problem that the prior art cannot set or dynamically modify the
mobility management frequency of a particular terminal among
numerous terminals.
[0012] The embodiments of the present invention also provide a
mobility management method and a service support node, which can
set or dynamically modify a mobility management frequency of a
particular terminal among numerous terminals.
[0013] To achieve the foregoing objective, the embodiments of the
present invention adopt the following technical solution:
[0014] A mobility management method includes: obtaining
subscription data of a terminal, where the subscription data
carries a periodic update deactivation indicator; sending
deactivation information of a periodic update timer to the terminal
according to the periodic update deactivation indicator; and
stopping a mobile reachable timer so as to stop monitoring a
periodic update of the terminal.
[0015] A service support node includes: a subscription data
obtaining unit, configured to obtain subscription data of a
terminal, where the subscription data carries a periodic update
deactivation indicator; a deactivation information sending unit,
configured to send deactivation information of a periodic update
timer to the terminal according to the periodic update deactivation
indicator; and a stopping unit, configured to stop a mobile
reachable timer so as to stop monitoring a periodic update of the
terminal.
[0016] The mobility management method and the service support node
according to the embodiments of the present invention obtain the
periodic update deactivation indicator of the network with respect
to the terminal through the subscription data, send the
deactivation information of the periodic update timer to the
terminal according to the periodic update deactivation indicator,
and meanwhile stop the mobile reachable timer so as to stop
monitoring the periodic update of the terminal. Thereby, the
mobility management frequency of a particular terminal may be
decreased, the utilization of network resources may be improved,
the objective of setting or dynamically modifying the mobility
management frequency of a particular terminal is achieved, and the
problem that the prior art cannot set or dynamically modify the
mobility management frequency of a particular terminal among
numerous terminals is solved.
[0017] For the terminal, the embodiments of the present invention
provide a mobility management method and a terminal, which can set
or dynamically modify, in cooperation with the network, the
mobility management frequency of a particular terminal among
numerous terminals.
[0018] To achieve the foregoing objective, the embodiments of the
present invention adopt the following technical solution:
[0019] A mobility management method includes: receiving a periodic
update timer from a service support node, where the periodic update
timer is obtained by the service support node according to periodic
update setting information in subscription data; and executing a
periodic update according to the received periodic update
timer.
[0020] A terminal includes: a timer receiving unit, configured to
receive a periodic update timer from a service support node, where
the periodic update timer is obtained by the service support node
according to periodic update setting information in subscription
data; and an update executing unit, configured to execute a
periodic update according to the received periodic update
timer.
[0021] In the mobility management method and the terminal according
to the embodiments of the present invention, the terminal receives
the periodic update timer that is obtained by the service support
node according to the periodic update setting information in the
subscription data, and executes a periodic update according to the
received periodic update timer. Thereby, the terminal can set or
dynamically modify, in cooperation with the network, the mobility
management frequency of a particular terminal among numerous
terminals.
[0022] For the terminal, the embodiments of the present invention
also provide a mobility management method and a terminal, which can
set or dynamically modify, in cooperation with the network, the
mobility management frequency of a particular terminal among
numerous terminals.
[0023] To achieve the foregoing objective, the embodiments of the
present invention adopt the following technical solution:
[0024] A mobility management method includes: receiving
deactivation information of a periodic update timer from a service
support node, where the deactivation information is sent by the
service support node according to a periodic update deactivation
indicator in subscription data; and stopping executing a periodic
update according to the received deactivation information of the
periodic update timer.
[0025] A terminal includes: a deactivation information receiving
unit, configured to receive deactivation information of a periodic
update timer from a service support node, where the deactivation
information is sent by the service support node according to a
periodic update deactivation indicator in subscription data; and a
periodic update stopping unit, configured to stop executing a
periodic update according to the deactivation information of the
periodic update timer received by the deactivation information
receiving unit.
[0026] In the mobility management method and the terminal according
to the embodiments of the present invention, the terminal receives
the deactivation information of the periodic update timer that is
sent by the service support node according to the periodic update
deactivation indicator in the subscription data, and stops
executing the periodic update according to the received
deactivation information of the periodic update timer. Thereby, the
terminal can set or dynamically modify, in cooperation with the
network, the mobility management frequency of a particular terminal
among numerous terminals.
BRIEF DESCRIPTION OF THE DRAWINGS
[0027] To make the technical solution of the embodiments of the
present invention or the prior art clearer, the accompanying
drawings used in the description of the embodiments or the prior
art are briefly described below. Evidently, the accompanying
drawings illustrate only some exemplary embodiments of the present
invention and persons skilled in the art may obtain other drawings
based on these drawings without creative efforts.
[0028] FIG. 1 is a flowchart of a mobility management method
according to an embodiment of the present invention;
[0029] FIG. 2 is a first simplified block diagram of a service
support node according to an embodiment of the present
invention;
[0030] FIG. 3 is a second simplified block diagram of a service
support node according to an embodiment of the present
invention;
[0031] FIG. 4 is a flowchart of another mobility management method
according to an embodiment of the present invention;
[0032] FIG. 5 is a first simplified block diagram of another
service support node according to an embodiment of the present
invention;
[0033] FIG. 6 is a second simplified block diagram of another
service support node according to an embodiment of the present
invention;
[0034] FIG. 7 is a sequence chart of a mobility management method
according to a first embodiment of the present invention;
[0035] FIG. 8 is a sequence chart of a mobility management method
according to a second embodiment of the present invention;
[0036] FIG. 9 is a sequence chart of a mobility management method
according to a third embodiment of the present invention;
[0037] FIG. 10 is a sequence chart of an embodiment for activating
a periodic update of a terminal according to the present
invention;
[0038] FIG. 11 is a sequence chart of another embodiment for
activating a periodic update of a terminal according to the present
invention;
[0039] FIG. 12 is a flowchart of a mobility management method for a
terminal according to an embodiment of the present invention;
[0040] FIG. 13 is a simplified block diagram of a terminal
according to an embodiment of the present invention;
[0041] FIG. 14 is a first flowchart of another mobility management
method for a terminal according to an embodiment of the present
invention;
[0042] FIG. 15 is a second flowchart of another mobility management
method for a terminal according to an embodiment of the present
invention;
[0043] FIG. 16 is a first simplified block diagram of another
terminal according to an embodiment of the present invention;
and
[0044] FIG. 17 is a second simplified block diagram of another
terminal according to an embodiment of the present invention.
DETAILED DESCRIPTION OF THE EMBODIMENTS
[0045] The technical solution of the embodiments of the present
invention is described clearly and completely in the following with
reference to the accompanying drawings in the embodiments of the
present invention. It is evident that the described embodiments are
only some exemplary embodiments of the present invention, rather
than all embodiments of the present invention. All other
embodiments that persons skilled in the art obtain without creative
efforts based on the embodiments of the present invention also fall
within the protection scope of the present invention.
[0046] As shown in FIG. 1, a mobility management method according
to an embodiment of the present invention includes the following
steps:
[0047] Step 11: Obtain subscription data of a terminal, where the
subscription data carries periodic update setting information.
[0048] A service support node may obtain the periodic update
setting information of the terminal from a home location register
(HLR) or a home subscriber server (HSS) (collectively called
subscriber server hereinafter) in one of the following two
modes:
[0049] First mode: In an attach procedure of the terminal, when the
service support node receives an Attach Request from the terminal,
the service support node sends an Update Location message to the
subscriber server and receives the subscription data sent by the
subscriber server, where the subscription data carries the periodic
update setting information.
[0050] Second mode: If the terminal has already attached, when the
subscriber server needs to reset the periodic update of the
terminal, the subscriber server sends new subscription data to the
service support node, where the subscription data carries the
periodic update setting information. Scenarios where the subscriber
server resets the periodic update of the terminal include a
scenario where the subscriber server has previously set the
periodic update of the terminal, or a scenario where the terminal
uses a regular periodic update timer.
[0051] The periodic update setting information carried in the
subscription data may take one of the following three forms: [0052]
A1. a multiplication factor of a regular periodic update timer;
[0053] B1. a specified periodic update timer; and [0054] C1. an
increment value of a regular periodic update timer.
[0055] In any one of the above forms, a conventional message (the
Insert User Data message) used by the subscriber server for sending
the subscription data to the service support node needs to be
enhanced. For one example, a parameter "Periodic Update Timer
Multiplication Factor" may be added, using an 8-bit coding, and the
multiplication factor takes a value from 0 to 255 (0 may be used to
indicate that the periodic update is deactivated). For another
example, a parameter "Predefined Periodic Update Timer" may be
added, using an 8-bit coding, where 5 bits represents a timer value
and 3 bits defines a unit of the timer value, such as 1 hour, 1
day, 1 week, or 1 month. For yet another example, a parameter
"Periodic Update Timer Increment" may be added to represent an
increment value for the regular periodic update timer.
[0056] Step 12: Obtain a periodic update timer of the terminal
according to the periodic update setting information.
[0057] After the service support node receives the periodic update
setting information of the terminal, the following three possible
processing ways may be used to obtain the periodic update timer of
the terminal:
[0058] A2. when the periodic update setting information is a
multiplication factor of the regular periodic update timer,
obtaining the regular periodic update timer and multiplying the
regular periodic update timer with the multiplication factor to
obtain the periodic update timer of the terminal; or
[0059] B2. when the periodic update setting information is a
specified periodic update timer, directly using the specified
periodic update timer as the periodic update timer of the terminal;
or
[0060] C2. when the periodic update setting information is an
increment value of the regular periodic update timer, obtaining the
regular periodic update timer and adding the increment value to the
regular periodic update timer to obtain the periodic update timer
of the terminal.
[0061] Step 13: Send the periodic update timer of the terminal to
the terminal.
[0062] Corresponding to the two modes for the service support node
to obtain the periodic update setting information of the terminal,
the service support node may send the periodic update timer of the
terminal to the terminal in the following two modes:
[0063] First mode: In the attach procedure of the terminal, the
service support node sends an Attach Accept message to the
terminal, where the Attach Accept message carries the periodic
update timer of the terminal.
[0064] Second mode: If the terminal has already attached, the
service support node sends an Update Accept message to the
terminal, where the Update Accept message carries the periodic
update timer of the terminal.
[0065] It should be noted that in order to support a longer update
interval than that of the prior art, the value unit part of the
conventional general packet radio service (GPRS) timer information
element (IE) may be enhanced. The conventional GPRS Timer IE is
defined as follows (excerpted from 3GPP TS 24.008):
##STR00001## [0066] where,
TABLE-US-00001 [0066] Timer value (octet 2) Bits 5 to 1 represent
the binary coded timer value. Bits 6 to 8 define the timer value
unit for the GPRS timer as follows: Bits 8 7 6 0 0 0 value is
incremented in multiples of 2 seconds 0 0 1 value is incremented in
multiples of 1 minute 0 1 0 value is incremented in multiples of
decihours (6 minutes) 1 1 1 value indicates that the timer is
deactivated Other values shall be interpreted as multiples of 1
minute in this version of the protocol.
[0067] Specifically, the present invention may define several new
coded values for the timer value unit to obtain a bigger time unit.
For example, value unit codes 011, 100, 101, and 110 may be added
and are respectively defined as follows: 011 means that the unit is
1 hour, 100 means that the unit is 10 hours, 101 means that the
unit is 100 hours, and 110 means that the unit is 1000 hours; or
011 means that the unit is 1 hour, 100 means that the unit is 1
day, 101 means that the unit is 1 week, 110 means that the unit is
1 month, and so on. All these newly added value units are bigger
than the conventional maximum value unit, that is, 6 minutes.
[0068] Step 14: Set a value that is a little longer than the
periodic update timer of the terminal as a mobile reachable timer
for monitoring the periodic update of the terminal.
[0069] As with the conventional mobility management method, the
service support node needs to set a value, which is a little longer
than the periodic update timer of the terminal, as the mobile
reachable timer for monitoring the periodic update of the terminal.
If the mobile reachable timer expires, the service support node
clears a paging proceed flag (PPF) to zero, so that the service
support node does not perform terminal paging.
[0070] In the mobility management method according to this
embodiment of the present invention, the periodic update setting
information the network set for the terminal is obtained through
the subscription data, the periodic update timer of the terminal is
obtained according to the periodic update setting information, and
the periodic update timer is sent to the terminal, and, meanwhile,
a value, which is a little longer than the periodic update timer of
the terminal, is set as a mobility reachable timer for monitoring
the periodic update of the terminal, thereby achieving the
objective of setting or dynamically modifying the mobility
management frequency of a particular terminal, and solving the
problem that the prior art cannot set or dynamically modify the
mobility management frequency of a particular terminal among
numerous terminals. In addition, by setting or dynamically
modifying the periodic update of a particular terminal to an update
interval that is longer than the regular periodic update timer, the
utilization of the network resources may be improved.
[0071] Based on the mobility management method according to the
embodiment of the present invention, as shown in FIG. 2, an
embodiment of the present invention provides service support node.
The service support node may be an SGSN or an MME. The service
support node includes:
[0072] a subscription data obtaining unit 21, configured to obtain
subscription data of a terminal, where the subscription data
carries periodic update setting information;
[0073] a timer obtaining unit 22, configured to obtain a periodic
update timer of the terminal according to the periodic update
setting information;
[0074] a timer sending unit 23, configured to send the periodic
update timer of the terminal to the terminal; and
[0075] a setting unit 24, configured to set a value, which is
longer than the periodic update timer of the terminal, as a mobile
reachable timer for monitoring the periodic update of the
terminal.
[0076] Further, as shown in FIG. 3, the subscription data obtaining
unit 21 may include:
[0077] a first obtaining subunit 211, configured to send, after
receiving an Attach Request from the terminal, an Update Location
message to a subscriber server (an HLR or an HSS), and receive the
subscription data sent by the subscriber server, where the
subscription data carries the periodic update setting information;
or
[0078] a second obtaining subunit 212, configured to receive, when
the subscriber server resets the periodic update of the terminal,
the subscription data sent by the subscriber server, where the
subscription data carries the periodic update setting
information.
[0079] The timer obtaining unit 22 may include any one of the
following subunits:
[0080] a first obtaining subunit 221, configured to obtain, when
the periodic update setting information is a multiplication factor
of a regular periodic update timer, the regular periodic update
timer and multiply the regular periodic update timer with the
multiplication factor to obtain the periodic update timer of the
terminal;
[0081] a second obtaining subunit 222, configured to directly use,
when the periodic update setting information is a specified
periodic update timer, the specified periodic update timer as the
periodic update timer of the terminal; or
[0082] a third obtaining subunit 223, configured to obtain, when
the periodic update setting information is an increment value of
the regular periodic update timer, the regular periodic update
timer and add the increment value to the regular periodic update
timer to obtain the periodic update timer of the terminal.
[0083] Corresponding to the subunits included in the subscription
data obtaining unit 21, the timer sending unit 23 may include:
[0084] a first sending subunit 231, configured to send an Attach
Accept message to the terminal, where the Attach Accept message
carries the periodic update timer of the terminal; or
[0085] a second sending subunit 232, configured to send an Update
Accept message to the terminal, where the Update Accept message
carries the periodic update timer of the terminal.
[0086] For the specific implementation method of the service
support node according to the embodiment of the present invention,
reference may be made to the mobility management method according
to the embodiment of the present invention, which is not described
here again.
[0087] In the service support node according to this embodiment of
the present invention, the subscription data obtaining unit 21
obtains the periodic update setting information of the network with
respect to the terminal, the timer obtaining unit 22 obtains the
periodic update timer of the terminal according to the periodic
update setting information, and the timer sending unit 23 sends the
periodic update timer to the terminal, and meanwhile the setting
unit 24 sets a value, which is a little longer than the periodic
update timer of the terminal, as a mobility reachable timer for
monitoring the periodic update of the terminal, thereby achieving
the objective of setting or dynamically modifying the mobility
management frequency of a particular terminal, and solving the
problem that the prior art cannot set or dynamically modify the
mobility management frequency of a particular terminal among
numerous terminals.
[0088] As shown in FIG. 4, another mobility management method
according to an embodiment of the present invention includes the
following steps:
[0089] Step 41: Obtain subscription data of a terminal, where the
subscription data carries a periodic update deactivation
indicator.
[0090] The service support node may use one of the following two
ways to obtain the periodic update deactivation indicator of the
terminal from the subscriber server:
[0091] First way: In the attach procedure of the terminal, when the
service support node receives an Attach Request from the terminal,
the service support node sends an Update Location message to the
subscriber server and receives the subscription data sent by the
subscriber server, where the subscription data carries the periodic
update deactivation indicator.
[0092] Second way: If the terminal has attached, when the
subscriber server needs to reset the periodic update of the
terminal, the subscriber server sends new subscription data to the
service support node, where the subscription data carries the
periodic update deactivation indicator. The scenarios where the
subscriber server resets the periodic update of the terminal
include a scenario where the subscriber server has previously set
the periodic update of the terminal or a scenario where the
terminal uses a regular periodic update timer.
[0093] The periodic update deactivation indicator carried in the
subscription data may be a deactivation indicator of the periodic
update timer or a value of the periodic update timer that is set to
zero. At this time, the service support node skips the operation of
obtaining the regular periodic update timer.
[0094] Step 42: Send the deactivation information of the periodic
update timer to the terminal according to the periodic update
deactivation indicator.
[0095] The service support node may use either of the following
ways to send the deactivation information of the periodic update
timer to the terminal according to the received periodic update
deactivation indicator of the terminal:
[0096] The used value unit of the periodic update timer indicates
that the timer is deactivated, for example, the value unit of the
periodic update timer may be set to a binary value "111" (timer
value unit=111);
[0097] or, the value of the periodic update timer is set to zero
(timer value=0).
[0098] Step 43: Stop the mobile reachable timer so as to stop
monitoring the periodic update of the terminal.
[0099] At this time, the service support node stops the mobile
reachable timer and stops monitoring the periodic update of the
terminal.
[0100] Optionally, when the periodic update of the terminal needs
to be reactivated, the subscriber server may modify the
subscription data in the service support node to activate the
periodic update of the terminal. Therefore, the mobility management
method according to the embodiment of the present invention may
also include the following:
[0101] The service support node obtains the subscription data of
the terminal again, where the subscription data carries a periodic
update activation indicator; and the service support node activates
the periodic update of the terminal according to the periodic
update activation indicator.
[0102] The service support node may use one of the following two
ways to activate the periodic update of the terminal according to
the periodic update activation indicator:
[0103] First way: The service support node sends a Detach Request
message to the terminal to instruct the terminal to re-initiate an
attach procedure, and activate the periodic update of the terminal
through the attach procedure re-initiated by the terminal.
[0104] Specifically, after receiving the Attach Request of the
terminal, the service support node obtains the regular periodic
update timer, and sends an Attach Accept message to the terminal,
where the Attach Accept message carries the regular periodic update
timer; and then, the service support node sets a value, which is a
little longer than the regular periodic update timer, as a mobile
reachable timer for monitoring the periodic update of the
terminal.
[0105] Second way: After receiving the Update Request initiated by
the terminal, the service support node activates the periodic
update of the terminal through the Update Accept message.
[0106] Specifically, after receiving the Update Request initiated
by the terminal, the service support node obtains the regular
periodic update timer, and sends a Update Accept message to the
terminal, where the Update Accept message carries the regular
periodic update timer; and then, the service support node sets a
value, which is a little longer than the regular periodic update
timer, as a mobile reachable timer for monitoring the periodic
update of the terminal.
[0107] The mobility management method according to the embodiment
of the present invention obtains the periodic update deactivation
indicator of the network with respect to the terminal through the
subscription data, sends the deactivation information of the
periodic update timer to the terminal according to the periodic
update deactivation indicator, and meanwhile stops the mobile
reachable timer so as to stop monitoring the periodic update of the
terminal. As a result, the mobility management frequency of a
particular terminal may be decreased, and the utilization of
network resources is improved. In addition, when the network needs
to activate the periodic update of the terminal, the subscription
data in the service support node may be modified again, thereby
achieving the objective of setting or dynamically modifying the
mobility management frequency of a particular terminal, and solving
the problem that the prior art cannot set or dynamically modify the
mobility management frequency of a particular terminal among
numerous terminals.
[0108] Based on the mobility management method according to the
embodiment of the present invention, as shown in FIG. 5, an
embodiment of the present invention provides another service
support node, including:
[0109] a subscription data obtaining unit 51, configured to obtain
subscription data of a terminal, where the subscription data
carries a periodic update deactivation indicator;
[0110] a deactivation information sending unit 52, configured to
send deactivation information of a periodic update timer to the
terminal according to the periodic update deactivation indicator;
and
[0111] a stopping unit 53, configured to stop a mobile reachable
timer so as to stop monitoring the periodic update of the
terminal.
[0112] Optionally, as shown in FIG. 6, the service support node may
also include:
[0113] a subscription data re-obtaining unit 61, configured to
re-obtain the subscription data of the terminal, where the
subscription data carries a periodic update activation indicator;
and
[0114] an activation processing unit 62, configured to activate the
periodic update of the terminal according to the periodic update
activation indicator.
[0115] And further, the activation processing unit 62 may
include:
[0116] a first activation processing subunit 621, configured to
send a Detach Request message to the terminal to instruct the
terminal to re-initiate an attach procedure, and activate the
periodic update of the terminal through the attach procedure
re-initiated by the terminal;
[0117] or
[0118] a second activation processing subunit 622, configured to
activate, after receiving the Update Request initiated by the
terminal, the periodic update of the terminal through the Update
Accept message.
[0119] For the specific implementation method of the service
support node according to this embodiment of the present invention,
reference may be made to another mobility management method
according to the embodiment of the present invention, which is not
described here again.
[0120] In the service support node according to this embodiment of
the present invention, the subscription data obtaining unit 51
obtains the periodic update deactivation indicator of the network
with respect to the terminal, the deactivation information sending
unit 52 sends the deactivation information of the periodic update
timer to the terminal according to the periodic update deactivation
indicator, and meanwhile the stopping unit 53 stops the mobile
reachable timer so as to stop monitoring the periodic update of the
terminal. As a result, the mobility management frequency of a
particular terminal may be decreased, and the utilization of
network resources may be improved. In addition, when the network
needs to activate the periodic update of the terminal, the
subscription data re-obtaining unit 61 may obtain the periodic
update activation indicator of the network with respect to the
terminal, and the activation processing unit 62 activates the
periodic update of the terminal according to the periodic update
activation indicator, thereby achieving the objective of setting or
dynamically modifying the mobility management frequency of a
particular terminal, and solving the problem that the prior art
cannot set or dynamically modify the mobility management frequency
of a particular terminal among numerous terminals.
[0121] In order to enable those skilled in the art to understand
the technical solution of the embodiments of the present invention
more clearly, the mobility management method according to the
embodiments of the present invention is described below in detail
with reference to specific embodiments.
[0122] First embodiment: In the attach procedure of the terminal,
the service support node obtains the subscription data from a
subscriber server, where the subscription data instructs the
service support node to deliver a special periodic update timer (as
opposed to the regular periodic update timer) to the terminal.
[0123] As shown in FIG. 7, the mobility management method according
to this embodiment includes the following steps:
[0124] Step 71: The terminal initiates an Attach Request to the
service support node.
[0125] Step 72: The service support node sends an Update Location
message to the subscriber server.
[0126] Step 73: The subscriber server sends an Insert Subscriber
Data message (the subscriber data is also known as subscription
data) to the service support node, where the message carries the
periodic update setting information.
[0127] The periodic update setting information may take any one of
the following three ways:
[0128] a. a multiplication factor of the regular periodic update
timer;
[0129] b. directly giving a specified periodic update timer;
and
[0130] c. an increment value of the regular periodic update
timer.
[0131] Step 74: The service support node obtains a periodic update
timer of the terminal according to the periodic update setting
information.
[0132] There are three possible ways for the service support node
to process the received periodic update setting information: a.
obtaining the regular periodic update timer, and multiplying the
regular periodic update timer with the multiplication factor to
obtain the periodic update timer of the terminal; b. directly using
the specified periodic update timer as the periodic update timer of
the terminal; and c. obtaining the regular periodic update timer,
and adding the increment value to the regular periodic update timer
to obtain the periodic update timer of the terminal.
[0133] Step 75: The service support node sends an Insert Subscriber
Data Ack message to the subscriber server.
[0134] Step 76: The subscriber server sends an Update Location Ack
message to the service support node.
[0135] Step 77: The service support node sends an Attach Accept
message to the terminal, where the message carries the periodic
update timer of the terminal.
[0136] Step 78: The service support node sets a value, which is a
little longer than the periodic update timer of the terminal, as a
mobile reachable timer for monitoring the subsequent periodic
update of the terminal.
[0137] Second embodiment: If the terminal has attached, the HLR or
the HSS initiates a modification of the subscription data in the
service support node, instructing the service support node to
modify the periodic update timer of the terminal.
[0138] As shown in FIG. 8, the mobility management method according
to this embodiment includes the following steps:
[0139] Step 81: The subscriber server sends an Insert Subscriber
Data message to the service support node, where the message carries
the periodic update setting information.
[0140] The periodic update setting information may take any one of
the following three forms:
[0141] a. a multiplication factor of the regular periodic update
timer;
[0142] b. a specified periodic update timer; and c. an increment
value of the regular periodic update timer.
[0143] Step 82: The service support node sends an Insert Subscriber
Data Ack message to the subscriber server.
[0144] Step 83: The terminal initiates an Update Request to the
service support node.
[0145] The update type may be an update or a periodic update.
[0146] Step 84: The service support node obtains a periodic update
timer of the terminal according to the periodic update setting
information.
[0147] Being triggered by the Update Request of the terminal, the
service support node executes three kinds of possible
processing:
[0148] a. obtaining the regular periodic update timer and
multiplying the regular periodic update timer with the
multiplication factor to obtain the periodic update timer of the
terminal;
[0149] b. directly using the specified periodic update timer as the
periodic update timer of the terminal; and
[0150] c. obtaining the regular periodic update timer and adding
the increment value to the regular periodic update timer to obtain
the periodic update timer of the terminal.
[0151] Step 85: The service support node sends an Update Accept
message to the terminal, where the message carries the periodic
update timer of the terminal.
[0152] Step 86: The service support node sets a value, which is a
little longer than the periodic update timer of the terminal, as a
mobile reachable timer for monitoring the subsequent periodic
update of the terminal.
[0153] In the mobility management methods according to the first
embodiment and the second embodiment, the subscription data
instructs the service support node to deliver the special periodic
update timer for the terminal, thereby achieving the objective of
setting or dynamically modifying the mobility management frequency
of a particular terminal, and solving the problem that the prior
art cannot set or dynamically modify the mobility management
frequency of a particular terminal among numerous terminals.
[0154] Third embodiment: In the attach procedure of the terminal,
the service support node obtains the subscription data from the
subscriber server, where the subscription data instructs the
service support node to deactivate the periodic update timer of the
terminal.
[0155] As shown in FIG. 9, the mobility management method according
to this embodiment includes the following steps:
[0156] Step 91: The terminal initiates an Attach Request to the
service support node.
[0157] Step 92: The service support node sends an Update Location
message to the subscriber server.
[0158] Step 93: The subscriber server sends an Insert Subscriber
Data message to the service support node, where the message carries
a periodic update deactivation indicator.
[0159] The periodic update deactivation indicator may directly
indicate that the periodic update timer of the terminal is
deactivated or that the periodic update timer is zero. It may be
understood that the periodic update deactivation indicator may also
be referred to as periodic update deactivation setting
information.
[0160] Step 94: The service support node skips the operation of
obtaining the regular periodic update timer.
[0161] Step 95: The service support node sends an Insert Subscriber
Data Ack message to the subscriber server.
[0162] Step 96: The subscriber server sends an Update Location Ack
message to the service support node.
[0163] Step 97: The service support node sends an Attach Accept
message to the terminal, where the message carries the deactivation
information of the periodic update timer.
[0164] The deactivation information of the periodic update timer
may take either of the following ways: setting the value unit of
the periodic update timer to a binary value "111" (timer value
unit=111) or setting the value of the periodic update timer to zero
(timer value=0), to indicate that the periodic update timer is
deactivated.
[0165] Step 98: The service support node stops the mobile reachable
timer so as to stop monitoring the subsequent periodic update of
the terminal.
[0166] It is worth noting that if the terminal has attached, the
subscriber server may also initiate the modification of the
subscription data in the service support node, instructing the
service support node to deactivate the periodic update timer of the
terminal. The specific procedure may be similar to that of the
foregoing second embodiment, and is not repeatedly described
here.
[0167] In addition, if the periodic update of the terminal has been
deactivated, when the periodic update of the terminal needs to be
reactivated, the subscriber server may initiate the modification of
the subscription data in the service support node, instructing the
service support node to activate the periodic update of the
terminal. The service support node may initiate a detach procedure
to instruct the terminal to re-initiate an attach procedure, and
activate the periodic update during a subsequent attach procedure
of the terminal; or the service support node may activate the
periodic update through a location update procedure initiated by
the terminal.
[0168] As shown in FIG. 10, an embodiment for activating a periodic
update of a terminal according to the present invention includes
the following steps:
[0169] Step 101: The subscriber server sends an Insert Subscriber
Data message to the service support node, where the message carries
a periodic update activation indicator.
[0170] Step 102: The service support node sends an Insert
Subscriber Data Ack message to the subscriber server.
[0171] Step 103: The service support node sends a Detach Request
message to the terminal, where a detach type indicates that the
terminal needs to attach again.
[0172] Step 104: The terminal sends a Detach Accept message to the
service support node.
[0173] Step 105: The terminal sends an Attach Request message to
the service support node.
[0174] Step 106: The service support node obtains the regular
periodic update timer.
[0175] Step 107: The service support node sends an Attach Accept
message to the terminal, where the message carries the obtained
regular periodic update timer.
[0176] Step 108: The service support node sets a value, which is a
little longer than the regular periodic update timer, as a mobile
reachable timer for monitoring the subsequent periodic update of
the terminal.
[0177] As shown in FIG. 11, another embodiment for activating a
periodic update of a terminal according to the present invention
includes the following steps:
[0178] Step 111: The subscriber server sends an Insert Subscriber
Data message to the service support node, where the message carries
a periodic update activation indicator.
[0179] Step 112: The service support node sends an Insert
Subscriber Data Ack message to the subscriber server.
[0180] Step 113: The terminal actively sends a Location Update
Request message to the service support node.
[0181] Step 114: The service support node obtains the regular
periodic update timer.
[0182] Step 115: The service support node sends a Location Update
Accept message to the terminal, where the message carries the
obtained regular periodic update timer.
[0183] Step 116: The service support node sets a value, which is a
little longer than the regular periodic update timer, as a mobile
reachable timer for monitoring the subsequent periodic update of
the terminal.
[0184] In the mobility management method according to the third
embodiment, the service support node is instructed by the
subscription data to deactivate the periodic update of the
terminal. As a result, the mobility management frequency of a
particular terminal may be decreased, and the utilization of
network resources may be improved. In addition, when the periodic
update of the terminal needs to be activated, the service support
node is instructed again by the subscription data to activate the
periodic update of the terminal, thereby achieving the objective of
setting or dynamically modifying the mobility management frequency
of a particular terminal, and solving the problem that the prior
art cannot set or dynamically modify the mobility management
frequency of a particular terminal among numerous terminals.
[0185] For the terminal, as shown in FIG. 12, a mobility management
method according to an embodiment of the present invention includes
the following steps:
[0186] Step 121: Receive a periodic update timer from an service
support node, where the periodic update timer is obtained by the
service support node according to the periodic update setting
information in subscription data; and
[0187] Step 122: Execute a periodic update according to the
received periodic update timer.
[0188] The periodic update setting information in the subscription
data may include: a multiplication factor of the regular periodic
update timer; or a specified periodic update timer; or an increment
value of the regular periodic update timer.
[0189] The terminal may receive the periodic update timer from the
service support node in the following ways: sending an Attach
Request message to the service support node, and receiving the
periodic update timer through an Attach Accept message; or sending
an Update Request message to the service support node, and
receiving the periodic update timer through an Update Accept
message.
[0190] And, in order to support a longer update interval than that
of the prior art, the code of the value unit of the periodic update
timer received by the terminal may include: 011, or 100, or 101, or
110, and the value unit is larger than 6 minutes. For example, the
following definitions may be applied: 011 means that the unit is 1
hour, 100 means that the unit is 10 hours, 101 means that the unit
is 100 hours, and 110 means that the unit is 1000 hours; or 011
means that the unit is 1 hour, 100 means that the unit is 1 day,
101 means that the unit is 1 week, 110 means that the unit is 1
month, and so on.
[0191] Based on the mobility management method, as shown in FIG.
13, an embodiment of the present invention also provides a
terminal, including:
[0192] a timer receiving unit 131, configured to receive a periodic
update timer from a service support node, where the periodic update
timer is obtained by the service support node according to the
periodic update setting information in the subscription data;
and
[0193] an update executing unit 132, configured to execute a
periodic update according to the received periodic update
timer.
[0194] In the mobility management method and the terminal according
to the embodiments of the present invention, the terminal receives
the periodic update timer that is obtained by the service support
node according to the periodic update setting information in the
subscription data, and executes a periodic update according to the
received periodic update timer. Thereby, the mobility management
frequency of a particular terminal among numerous terminals can be
set or dynamically modified in cooperation with the network.
[0195] For the terminal, as shown in FIG. 14, another mobility
management method according to an embodiment of the present
invention includes the following steps:
[0196] Step 141: Receive deactivation information of a periodic
update timer from a service support node, where the deactivation
information is sent by the service support node according to a
periodic update deactivation indicator in subscription data.
[0197] Step 142: Stop executing a periodic update according to the
received deactivation information of the periodic update timer.
[0198] The deactivation information of the periodic update timer
received by the terminal includes: the value unit of the periodic
update timer indicating that the timer is deactivated; or the value
of the periodic update timer that is set to zero.
[0199] If the periodic update of the terminal has been deactivated,
optionally, the mobility management method according to the
embodiment of the present invention, as shown in FIG. 15, may also
include the following steps:
[0200] Step 151: Receive activation information of the periodic
update timer from the service support node, where the activation
information is sent by the service support node according to a
periodic update activation indicator in subscription data.
[0201] Step 152: Activate the periodic update according to the
received activation information of the periodic update timer.
[0202] Based on the mobility management method, as shown in FIG.
16, an embodiment of the present invention provides another
terminal, including:
[0203] a deactivation information receiving unit 161, configured to
receive deactivation information of a periodic update timer from a
service support node, where the deactivation information is sent by
the service support node according to a periodic update
deactivation indicator in subscription data; and
[0204] an update stopping unit 162, configured to stop executing a
periodic update according to the deactivation information of the
periodic update timer received by the deactivation information
receiving unit.
[0205] Optionally, as shown in FIG. 17, the terminal according to
the embodiment of the present invention may also include:
[0206] an activation information receiving unit 171, configured to
receive activation information of a periodic update timer from a
service support node, where the activation information is sent by
the service support node according to a periodic update activation
indicator in subscription data; and
[0207] an update activating unit 172, configured to activate a
periodic update according to the activation information of the
periodic update timer received by the activation information
receiving unit.
[0208] In the mobility management method and the terminal according
to the embodiments of the present invention, the terminal receives
the deactivation information of the periodic update timer that is
sent by the service support node according to the periodic update
deactivation indicator in the subscription data, and stops
executing the periodic update according to the received
deactivation information of the periodic update timer. Thereby, the
mobility management frequency of a particular terminal among
numerous terminals can be set or dynamically modified in
cooperation with the network.
[0209] In summary, the mobility management methods according to the
embodiments of the present invention may be applied in low-mobility
machine-type communication (MTC). MTC is a kind of data
communication and relates to one or more entities not requiring any
interaction with a natural person. In low-mobility MTC
applications, such as a family health monitoring device, an
automatic vending machine, a water meter/ammeter, hydrological
monitoring, forest fire monitoring, and bridge monitoring, the
terminal device is stationary permanently, or moves infrequently,
for example, moving only once a week, or moving only in a certain
area, such as moving in a cell, moving in one or more location
areas (LAs), routing areas (RAs) or tracking areas (TAs).
Therefore, the utilization of network resources may be improved by
setting or dynamically modifying the mobility management frequency
of a particular MTC terminal (or called an MTC device) among
numerous terminals.
[0210] Persons skilled in the art may understand that all or part
of steps in the methods of the above embodiments may be implemented
by relevant hardware instructed by a program. The program may be
stored in a computer readable storage medium, such as a ROM/RAM, a
magnetic disk, and an optical disk.
[0211] The above are only exemplary embodiments of the present
invention, but the protection scope of the present invention is not
limited thereto. Any modification or substitution readily
conceivable by those skilled in the art within the scope of the
technology disclosed in the present invention shall be covered
within the protection scope of the present invention. Therefore,
the protection scope of the present invention is subject to the
appended claims.
* * * * *