Method and device for negotiating position updating time
Technical Field
The present invention relates to the field of mobile communications, and in particular, to a method and an apparatus for negotiating location update time.
Background
In recent years, machine-to-machine communication (M2M, multimedia machine) services are gradually beginning to be applied, such as logistics systems, remote meter reading, smart home, and the like. M2M belongs to Machine Type Communication (MTC). M2M service providers develop M2M services using existing wireless networks, such as Packet Switched (PS) networks like global system for mobile communications (GSM), General Packet Radio Service (GPRS), Evolved Packet System (EPS), etc. The M2M service has significant differences with human-to-human communication (H2H, human) services, and requires necessary optimization of existing networks to achieve optimal network management and network communication quality.
In the existing application scenario, the M2M terminal may implement wireless access through various networks such as GSM, GPRS, EPS, etc., the access mode may also be a short message mode, or an IP mode, etc., and data transmission may also be performed through a short message mode, or an IP mode, etc. Therefore, MTC can use the CS (circuit switch) domain service (e.g. sms) in the GSM network, or the PS domain service (e.g. PS sms, IP, etc.) in the IP network.
The architecture for implementing the M2M service in a GSM network is depicted in fig. 1. The GSM network mainly includes GSM/EDGE radio access network (GERAN, GSM EDGE access network), Mobile services switching center (MSC, Mobile-services switching center), visitor location register (VLR, VisitorLocationRegister), Home Location Register (HLR), and so on, and MTC user terminals (UE, user equipment) can interact with MTCServer through the GSM network.
The MSC is the core part of the GSM network system and is the functional entity that controls and performs voice circuit switching for mobile stations located in its coverage area. The MSC provides a switching function, performs functions such as paging access, channel allocation, call connection, traffic control, charging, base station management, etc. for a mobile subscriber, and also performs switching between Base Station Subsystems (BSS), MSC and auxiliary radio resource management, mobility management, etc., and provides an interface function facing other functional entities of the system and facing a fixed network.
The HLR is used for storing the subscription data of the user and the current MSC/VLR address and is connected with the MSC through a D interface.
The MTCServer is an M2M application server for providing M2M applications to users, and is connected to the MSC through an mtcms interface.
A machine type communication device (mtcu), similar to a UE, is responsible for collecting information of several collectors and accessing a core network through a wireless access node to interact data with an mtserver.
Fig. 2 is a prior art procedure for performing network location update by accessing mtcu to CS network, comprising the following steps:
step 201, the MSC configures a Location Update (LU) timer duration of the whole network according to the operator policy and notifies GERAN, wherein the location update adopts a T3212 timer; then, GERAN sends the time length of the location update timer unified for the whole network (i.e., the time length of the T3212 timer) to the mtcre through a Broadcast Control Channel (BCCH).
Step 202, the MTCE saves the time length of a position updating timer issued by GERAN, sets the time length of the position updating timer of the MTCE, and then initiates a subsequent timing position updating process according to the time length of the position updating timer, namely, the timing position updating process is initiated when the timer arrives;
step 203, the mtce initiates a first location update request (i.e. attach request) to the MSC in the network, where the location update request carries information such as the mtce identifier;
step 204, the MSC requests an authentication duration from the HLR.
Step 205, the MSC authenticates and authenticates the necessary access to the MTCE according to the authentication duration;
step 206, after the authentication is passed, the MSC initiates a location update request to the HLR, downloads the mtue subscriber subscription data, and checks if the mtue is allowed to access the network according to the subscription data, if so, performs step 207.
Step 207, when the mtue is allowed to access the network, the MSC sends a location update accept message to the mtue, and the location update is successful, and the mtue completes the attachment on the MSC.
M2M services are networked applications and services that are core to machine terminal intelligent interactions. The intelligent machine terminal is adopted, information is transmitted through a wireless network, an informatization solution is provided for a client, and the informatization solution is used for meeting the informatization requirements of the client on monitoring, commanding and scheduling, data acquisition, measurement and the like.
The communication target of M2M is machine-to-machine, and may be communication between human and machine, communication between machine and server, and communication between different intelligent terminals. MTC devices for different applications have different characteristics, such as elevator devices, etc. having low mobility, packet domain only service (PSonly) attributes, while monitoring and warning devices have low data transmission and high availability attributes in addition to low mobility, PSonly attributes. Therefore, different system optimizations are required for MTC devices with different applications, and MTC devices can be effectively managed, monitored, paid, and the like.
Among the M2M related requirements, low mobility (Lowmobility), transmit only (MOonly), power saving (extra lowpowerconsumption) and the like, there is a need to extend or dynamically adjust the duration of the location update timer, so as to achieve the purposes of saving power, saving network resources and reducing mobility management. In a PS network, such as a GPRS network or an EPS network, the duration of the location update timer may be sent to the mtcu ue through an attach accept (attach accept)/tracking area location update (TAU) message, so as to dynamically adjust the location update time (i.e., the duration of the location update timer) at the device level. However, in the CS network, the time length of the location update timer is full network level and is issued through BCCH, so that in the CS network, dynamic adjustment of the location update time at the device level cannot be realized.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a method and an apparatus for negotiating location update time, which can solve the problem that dynamic adjustment of the device-level location update time cannot be implemented in a CS network.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a method for negotiating position updating time, which comprises the following steps:
setting a position updating timer duration at a set Machine Type Communication (MTC) user terminal (UE) end, and informing a Mobile Switching Center (MSC); the MSC sets the location updating timer duration of the MTCE service at the local terminal according to the location updating timer duration of the MTCE terminal;
or,
setting the time length of a location updating timer of the MTCE service at the MSC end, and informing the MTCE; and the MTCE sets the time length of the location updating timer at the local terminal according to the time length of the location updating timer serving the MTCE at the MSC terminal.
Further, the setting of the location update timer duration at the mtcu end specifically includes:
the MTCE sets the time length of a location updating timer of the local terminal according to application requirements and related configuration strategies; or the MTC Server sets the time length of a location update timer at the MTCE terminal according to the application of the MTCE.
Further, notifying the MSC of the duration of the location update timer set at the mtce ue side, specifically:
the mtcu notifies the MSC of the location update timer duration of the mtcu end through a device (Facility) message, an Unstructured Supplementary Service Data (USSD) message, a timing location update message, or an attach message.
Further, before the mtue notifies the MSC of the location update timer duration set by the mtue end through a Facility message, the method further includes:
the mtcu sends a Register message to the MSC, and instructs the MSC to perform negotiation of location update time through an event identifier in the Register message.
Further, the MSC sets the location update timer duration of the mtue service at the local terminal according to the location update timer duration set by the mtue terminal, specifically:
the time length of a location updating timer set by the MTCE terminal is single time length, and the MSC sets the time length as the time length of the location updating timer serving the MTCE at the local terminal by adopting the time length;
when the location update timer duration set by the mtcc end is a list comprising a plurality of durations, the MSC selects one location update timer duration from the list to set as the location update timer duration serving the mtcc at the local end.
Further, after the MSC side sets the duration of the location update timer for the mtue service, the method further includes:
and the MSC sends a Facility response, a USSD response, a timing location update response or an attachment response to the MTCE and informs the MTCE of successful location update time negotiation.
Further, when the duration of the location update timer set by the mtcc ue is a list containing a plurality of durations, the method further includes:
the MSC sends the time length of the location update timer selected from the list to the MTCE through the Facility response, the USSD response, the timing location update response or the attachment response;
and the MTCE sets the time length of the location updating timer selected from the list as the time length of the location updating timer of the local terminal.
When the MSC sends a Facility response to the MTCC, the method further comprises:
and after receiving the Facility response, the MTCU sends a Release Complete (Complete) message to the MSC to inform the MSC of the completion of the negotiation of the location updating time.
Further, the setting of the location update timer duration at the MSC end specifically includes:
the MSC acquires the time length of a location updating timer from the subscription data of the MTCE, and sets the acquired time length of the location updating timer as the time length of the location updating timer serving the MTCE at the local terminal; or,
and the MSC determines the time length of the location updating timer serving the MTCE according to the characteristics of the MTCE and sets the time length of the location updating timer serving the MTCE at the local terminal.
Further, notifying the mtue of the time length of the location update timer serving the mtue at the MSC end, specifically:
the MSC notifies the MTCE of the time length of a local location update timer serving the MTCE through a Facility message, a USSD message or a location update acceptance message.
Further, the mtcu sets the location update timer duration at the home terminal according to the location update timer duration for the mtcu service at the MSC terminal, specifically:
the MTCE adopts the location update timer duration of the MSC end serving the MTCE carried in the Facility message, the USSD message or the location update receiving message to set as the location update timer duration of the local end.
Further, before the MSC notifies the mtcu of a location update timer duration for serving the mtcu, which is set by the local terminal, through a Facility message, the method further includes:
and the MSC sends a Register message to the MTCE, and indicates the MTCE to negotiate the location updating time through an event identifier in the Register message.
Further, after the mtcu ue sets the duration of the location update timer, the method further includes:
and the MTCE sends a Facility response, a USSD response or a location update completion message to the MSC to inform the MSC of successful location update time negotiation.
Further, when the mtcu ue transmits a Facility response to the MSC, the method further comprises:
and after receiving the Facility response, the MSC sends a ReleaseComplete message to the MTCE to inform the MTCE of finishing the negotiation of the location updating time.
The invention also provides a device for negotiating the position updating time, which comprises: a setting module and a notification module, wherein:
the setting module is used for setting the time length of the location updating timer at the MTCE terminal, and after the informing module informs the MSC of the time length of the location updating timer at the MTCE terminal, the time length of the location updating timer for the MTCE service is set at the MSC terminal; the location updating system is also used for setting the time length of a location updating timer of the MTCE service at the MSC end, and setting the time length of the location updating timer at the MTCE end after the informing module informs the MTCE of the time length of the location updating timer at the MSC end;
the notification module is used for notifying the MSC of the time length of the location update timer of the MTCE end set by the setting module; and the MTCE is also informed of the time length of the location update timer at the MSC end set by the setting module.
In the location update time negotiation scheme of the invention, after MTCE or MSC sets the time length of the location update timer of itself according to the actual application requirement, the time length of the location update timer of the local terminal is informed to the opposite side through the messages of Facility request, USSD request, timing location update request, attachment request or location update acceptance, etc., so in the CS network, the time length of the location update timer can be dynamically adjusted at the equipment level, and the requirement of prolonging or dynamically adjusting the time length of the location update timer according to the MTCE characteristic in the M2M application is met.
Drawings
Fig. 1 is an implementation architecture of M2M service in a GSM network;
FIG. 2 is a flow of a MTCE accessing a CS network to perform network location update in the prior art;
FIG. 3 is a flowchart illustrating a method for negotiating a location update time according to the present invention;
FIG. 4 is a flowchart illustrating a location update time negotiation method according to an embodiment of the present invention;
FIG. 5 is a flowchart illustrating a method for negotiating a location update time according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating a method for negotiating a three-location update time according to an embodiment of the present invention;
FIG. 7 is a flowchart illustrating a method for negotiating a four-location update time according to an embodiment of the present invention;
FIG. 8 is a flowchart illustrating a method for negotiating a five-position update time according to an embodiment of the present invention;
fig. 9 is a flowchart illustrating a method for negotiating a six-position update time according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a device for negotiating a location update time according to the present invention.
Detailed Description
The technical solution of the present invention is further elaborated below with reference to the drawings and the specific embodiments.
In order to solve the problem that dynamic adjustment of the location update time of the equipment level cannot be realized in the CS network, in the invention, the MTCE and the MSC need to negotiate the location update time, and after the negotiation is successful, the MTCE and the MSC both adopt the negotiated location update time to set the location update time of the local terminal. By adopting the method and the device, the time interval of the MTCUE for initiating the timing location updating process can be dynamically prolonged so as to meet the requirement of M2M application. If the negotiation of the location updating time fails, the MTCE and the MSC still adopt the uniform location updating time of the whole network to carry out the setting of the local terminal so as to prevent the abnormal scene of inconsistent location updating time of the two terminals.
In the invention, the position updating time refers to the time length of a position updating timer, and the time length is a parameter of the position updating timer; the location update timer described in the present invention may adopt a T3212 timer.
The method for negotiating the location update time of the present invention is shown in fig. 3, and comprises the following steps:
step 301, setting a time length of a location update timer at an MTCE terminal, and notifying an MSC; the MSC sets the location update timer duration of the MTCE service at the local terminal according to the location update timer duration of the MTCE terminal.
Step 302, setting the time length of a location update timer of the MTCE service at the MSC end, and informing the MTCE; the MTCE sets the time length of the location update timer at the local terminal according to the time length of the location update timer at the MSC terminal.
Steps 301 and 302 are two parallel methods of location update time negotiation.
The method for negotiating the location update time according to the present invention will be described below with reference to specific embodiments.
Example one
As shown in fig. 4, after the mtcu ue updates the duration of the location update timer of the local terminal, it initiates negotiation to the CS network, that is, the MSC, through a Facility message, and completes setting of the location update time of the mtcu ue and the MSC. The Facility message may be used for transmitting messages between the mtue and the MSC when the CS session is established, or may be used for non-session methods, such as subscription modification of supplementary services (call forwarding, three-way calling, etc.). The embodiment is that a negotiation process of position updating time is initiated by means of Facility messages; the negotiation of the location update time in this embodiment comprises the steps of:
step 401, after the mtce ue is started, initially setting a time length of a location update timer of a home terminal according to application requirements and related configuration strategies, such as low mobility requirements, power saving requirements, MOonly requirements and the like; if the MTCE does not initially set the location update timer duration of the local terminal, the MTCServer can set the location update timer duration for the MTCE according to different applications of the MTCE.
The location update timer duration may be a single duration or a list composed of multiple durations, for example, the multiple location update timer durations set on the mtcu included in the list are multiples of the location update timer duration unified in the whole network, a value range of the multiple is 1 to n, and n is a natural number.
The mtue also needs to attach to the MSC after being powered on, and establish a Mobility Management (MM) connection with the MSC.
Step 402, after the mtue establishes MM connection with the MSC, if the mtue is configured with a location update timer duration different from the duration of the entire network, the mtue needs to negotiate the location update time with the MSC: the mtue initiates a registration (Register) message to the MSC, which carries an event identifier for indicating that a negotiation for location update time is required. After receiving the Register message, the MSC prepares to perform negotiation of location update time.
Step 403, the mtcc initiates a Facility message to the MSC, where the Facility message carries the duration of the location update timer set by the local terminal, in addition to the event identifier same as that in the Register message.
Step 404, the MSC processes the Facility message, takes out the time length of the location update timer therein, and sets the time length of the location update timer at the home terminal.
If the location update timer duration carried in the Facility message is a list, the MSC needs to select an applicable location update timer duration from the list according to an operator policy, and set the location update timer duration as the location update timer duration of the home terminal (serving the mtcu).
The MSC uses the selected location update timer duration as its own location update timer duration, i.e., the location update timer duration of the network side used by the mtcu. If the location update timer carried by the Facility message has a single duration, the MSC may use the location update timer duration.
It should be noted that the MSC may also calculate a time length (which may need to be longer than the selected time length of the location update timer) according to the selected time length of the location update timer, and set the time length of the location update timer at the local terminal.
Step 405, the MSC sends the time length of the location update timer set at the home terminal to the mtcu through a Facility response, and the mtcu carries an indication that the setting of the location update timer at the network side is successful, so as to inform the mtcu that the negotiation of the location update time is successful.
The MTCE adopts the time length of the location updating timer set by the MSC end as the time length of the location updating timer of the local end, and then the negotiation of the location updating time is completed.
If the duration of the location update timer carried by the Facility message is a single duration, after the MSC sets the duration of the location update timer at the home terminal, the Facility response sent to the mtcc may only include an indication that the network-side location update timer is successfully set.
If the MSC fails to set the duration of the location update timer of the home terminal in step 404, the Facility response of step 405 carries an indication that the network-side location update timer has failed to set, and informs the mtcre that the location update time negotiation of this time has failed.
Step 406, regardless of whether the negotiation is successful or not, after receiving the Facility response, the mtcu sends a ReleaseComplete message to the MSC, and the event identifier carried in the message is used to indicate that the negotiation of the location update timing is ended.
Example two
As shown in fig. 5, after the mtcu updates the duration of the location update timer of the local terminal, it initiates negotiation to the MSC through an Unstructured Supplementary Service Data (USSD) message, and completes the update of the location update time between the mtcu and the MSC. USSD is a data interaction technique developed on the basis of the GSM short message system, and has a higher transmission rate and stronger interactivity than short message services, using a connection-oriented interactive session mode that provides a transparent channel. The invention completes the negotiation of position updating time between MTCE and MSC by using USSD message; the negotiation of the location update time in this embodiment comprises the steps of:
step 501 is the same as step 401, and is not described herein again.
Step 502, after the MM connection is established between the mtue and the MSC, if the mtue is configured with a location update timer duration different from the duration of the entire network, the mtue needs to negotiate the location update time with the MSC; MTCUE initiates USSD message to MSC, which carries the time length of location updating timer set by local terminal and an event mark for indicating negotiation of location updating time.
Step 503, the MSC processes the USSD message, takes out the duration of the location update timer therein, and sets the duration of the location update timer at the home terminal. The processing here is the same as step 404 and is not described again.
Step 504, the MSC sends the duration of the location update timer set by the home terminal to the mtcu through USSD response, and informs the mtcu that the negotiation of the location update time of this time is successful, with an indication that the location update timer on the network side is successfully set.
The MTCE adopts the time length of the location updating timer set by the MSC end as the time length of the location updating timer of the local end, and then the negotiation of the location updating time is completed.
If the duration of the location update timer carried by the USSD message is a single duration, after the MSC sets the duration of the location update timer at the home terminal, the USSD response sent to the mtcc may only include an indication that the setting of the location update timer at the network side is successful.
If the MSC fails to set the duration of the location update timer of the local terminal in step 503, the USSD response in step 504 carries an indication that the network-side location update timer has failed to set, and informs the mtce that the location update time negotiation fails this time.
EXAMPLE III
As shown in fig. 6, after the mtcc updates the location update timer duration of the local terminal, the location update timer duration configured by the local terminal is carried in the attach message or the timing location update message, and initiates negotiation to the MSC, thereby completing setting of the location update time between the mtcc and the MSC. In the embodiment, the negotiation process of the position updating time is initiated by using the attachment message or the timing position updating message of the CS network; the negotiation of the location update time in this embodiment comprises the steps of:
the processing of step 601 is the same as step 401, and is not described herein again.
Step 602, after the mtue establishes MM connection with the MSC, if the mtue is configured with a location update timer duration different from the duration of the entire network, the mtue needs to negotiate the location update time with the MSC: the mtce initiates a timing location update message or an attach message to the MSC, carrying the duration of the location update timer set by the home terminal and an event identifier for indicating negotiation of location update time.
Step 603, the MSC processes the timing location update message or the attach message, takes out the duration of the location update timer therein, and sets the duration of the location update timer at the home terminal. The processing here is the same as step 404 and is not described again.
Step 604, the MSC sends the time length of the location update timer set at the home terminal to the mtcu through the timed location update response or the attach response, and carries an indication that the network-side location update timer is successfully set, to notify the mtcu that the negotiation of the location update time of this time is successful.
The MTCE adopts the time length of the location updating timer set by the MSC end as the time length of the location updating timer of the local end, and then the negotiation of the location updating time is completed.
If the time length of the location update timer carried by the timing location update message or the attach message is a single time length, the MSC sets the time length of the location update timer at the home terminal, and then the timing location update response or the attach response sent to the mtcc may only include an indication that the setting of the location update timer at the network side is successful.
If the MSC fails to set the duration of the location update timer of the local terminal in step 603, the timed location update response or the attach response of step 604 carries an indication that the network-side location update timer has failed to set, and informs the mtcre that the location update time negotiation fails this time.
Example four
As shown in fig. 7, the MSC determines the location update timer duration for the mtcu ue service according to the operator policy, and initiates negotiation to the mtcu ue through Facility message, completing setting of the location update timer duration of the mtcu ue and the MSC; the negotiation of the location update time of this embodiment comprises the steps of:
in step 701, the MSC determines a location update timer duration for the mtue service.
If the location update timer duration for the mtue service is the subscription data of the mtue, when the mtue initiates the location update procedure, the HLR sends the subscription data of the mtue to the MSC (as in step 206 in fig. 2), and the MSC obtains the location update timer duration for the mtue service from the subscription data of the mtue.
If the location update timer duration for serving the mtcu is not the subscription data of the mtcu, the MSC may determine a location update timer duration for serving the mtcu through operator policy according to the characteristics of the mtcu, such as low mobility, power saving, mobility, and the like.
It should be noted that the MSC determines the duration of the location update timer to be a single duration rather than a list.
In step 702, the MSC sets the determined time length of the location update timer serving the mtcc as the time length of the location update timer of the local terminal.
Step 703, after the mtce establishes MM connection with the MSC, the MSC initiates a Register message to the mtce, where the message carries an event identifier for indicating that negotiation of location update time is required. The mtue prepares to perform location update time negotiation after receiving the Register message.
In step 704, the MSC initiates a Facility message to the mtcc, which carries the duration of the location update timer set by the local terminal in step 702, in addition to the event identifier same as that in the Register message.
Step 705, the mtue processes the Facility message, takes out the time length of the location update timer therein, and sets the time length as the time length of the location update timer of the local terminal.
Step 706, the mtce returns a Facility response to the MSC and carries an indication that the mtce-side location update timer setting is successful, and then the location update time negotiation is completed; if the mtce fails to set the duration of the location update timer of the local terminal in step 705, the Facility response carries an mtce-side location update timer setting failure indication to inform the MSC that the negotiation of the location update time fails.
Step 707, after receiving the Facility response, the MSC sends a ReleaseComplete message to the mtcc regardless of whether the negotiation of the location update time is successful, where an event identifier carried in the message is used to indicate that the negotiation of the location update time is ended.
EXAMPLE five
As shown in fig. 8, the MSC determines the duration of the location update timer used by the mtcc according to the operator policy, and initiates negotiation to the mtcc through USSD message, thereby completing setting of the duration of the location update timer between the mtcc and the MSC; the negotiation of the location update time of this embodiment comprises the steps of:
the processing of steps 801 to 802 is the same as the processing of steps 701 to 702, and the description thereof is omitted.
Step 803, after the mtcu establishes MM connection with the MSC, the MSC initiates a USSD message to the mtcu, where the USSD message carries the duration of the location update timer set by the home terminal and an event identifier used to indicate negotiation of location update time.
Step 804, the mtcc ue processes the USSD message, takes out the duration of the location update timer therein, and sets the duration as the duration of the location update timer of the local terminal.
Step 805, the mtce returns USSD response to the MSC, and carries an mtce side location update timer setting success indication, and the negotiation of this location update timing is completed; if the mtcc fails to set the duration of the location update timer of the local terminal in step 804, the mtcc side location update timer setting failure indication is carried in the USSD response to inform the MSC that the negotiation of the location update time fails.
EXAMPLE six
As shown in fig. 9, the negotiation of the location update time of this embodiment includes the following steps:
in step 901, the mtue initiates a location update request to the MSC, which may be a first location update request (i.e. attach request) or a timing location update request, where the mtue identity is carried.
Step 902, the MSC processes the location update request and obtains the subscription data of the mtue from the HLR.
Step 903, the MSC sets the duration of the location update timer of the home terminal.
If the subscription data acquired in step 902 includes the location update timer duration for the mtue service, the MSC sets the location update timer duration in the subscription data to the location update timer duration of the home terminal;
if the subscription data obtained in step 902 does not include the time length of the location update timer serving the mtcu, the MSC may determine the time length of the location update timer serving the mtcu through an operator policy according to the characteristics of the mtcu, such as low mobility, power saving, MOonly, and the like, and set the time length as the time length of the location update timer at the home terminal.
In step 904, after the MSC completes the location update procedure (step 207 in fig. 2), the MSC sends a location update accept message to the mtcc, where the location update accept message carries the duration of the location update timer of the local terminal set by the MSC.
Step 905, the mtcu takes out the time length of the location update timer from the location update accept message, and sets the time length as the time length of the location update timer of the local terminal.
Step 906, the mtce sends a location update complete message to the MSC, wherein the message carries an mtce-side location update timer setting success indication, thus completing the location update time negotiation; if the mtcc fails to set the duration of the location update timer in step 905, the location update complete message carries an mtcc-side location update timer setting failure indication to inform the MSC that the negotiation of the location update time fails.
In the above embodiment, if the negotiation of the location update time fails, the mtcu and the MSC still set the local terminal by using the time length of the location update timer unified in the whole network, so as to prevent an abnormal scenario in which the location update times at the two terminals are inconsistent.
In order to implement the above method, the present invention provides a device for negotiating a location update time, as shown in fig. 10, including: a setup module 10 and a notification module 20, wherein:
a setting module 10, configured to set a location update timer duration at an mtcc ue end, and set the location update timer duration for the mtcc service at the MSC end after the notifying module 20 notifies the MSC of the location update timer duration of the mtcc end; the location update timer is also configured to set a location update timer duration for the mtcu service at the MSC end, and set the location update timer duration at the mtcu end after the notification module 20 notifies the mtcu of the location update timer duration at the MSC end;
a notifying module 20, configured to notify the MSC of the duration of the location update timer of the mtce ue end set by the setting module 10; and is further configured to notify the mtue of the duration of the location update timer at the MSC end, which is set by the setting module 10.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.