CN108307377B - Method and device for sending message to UE (user Equipment) and M2M management platform - Google Patents

Method and device for sending message to UE (user Equipment) and M2M management platform Download PDF

Info

Publication number
CN108307377B
CN108307377B CN201710279153.8A CN201710279153A CN108307377B CN 108307377 B CN108307377 B CN 108307377B CN 201710279153 A CN201710279153 A CN 201710279153A CN 108307377 B CN108307377 B CN 108307377B
Authority
CN
China
Prior art keywords
target
preset reachable
reachable time
time
preset
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201710279153.8A
Other languages
Chinese (zh)
Other versions
CN108307377A (en
Inventor
徐蓓
张永靖
朱锦涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Huawei Cloud Computing Technology Co ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of CN108307377A publication Critical patent/CN108307377A/en
Application granted granted Critical
Publication of CN108307377B publication Critical patent/CN108307377B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Abstract

A method, a device and an M2M management platform for sending messages to UE are used for solving the problem that the standby time of the UE is shortened because a PSM timer in a network server and a preset reachable time list in an M2M management platform are not synchronous. The method comprises the following steps: the M2M management platform receives a downlink data request message sent by an application server AS, wherein the downlink data request message comprises an identifier of a target UE; searching a preset reachable time list of the target UE, which is locally stored, according to the identifier of the target UE; determining a source parameter in the preset reachable time list as a Network; judging whether the current time T1 is within the preset reachable time period; and if so, sending the downlink data request message to the target UE.

Description

Method and device for sending message to UE (user Equipment) and M2M management platform
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a method and a device for sending a message to UE (user equipment) and an M2M management platform.
Background
In the internet of things, a User Equipment (UE) registers on a Machine to Machine (M2M) management platform, and the M2M management platform stores a preset reachable time list of the terminal, where the preset reachable time list includes information of a preset reachable time period of the UE. When the application server sends the downlink data request message to the UE, the downlink data request message is firstly sent to the M2M management platform, and the M2M management platform sends the downlink data request message to the UE within the preset reachable time period of the UE.
When there is no uplink service data to be transmitted, the UE enters an Idle (Idle) state from a Connected (Connected) state, and enters a Power Save Mode (PSM) after maintaining the Idle state for a certain period of time. Herein, the Idle state of the UE is also called as reachable state. It can be seen that the time period when the UE is actually in the reachable state is dynamic, depending on whether the UE has an uplink traffic demand.
However, the preset reachable time period saved by the M2M management platform is fixed and unchanged, and is different from the time period in which the UE is actually in a reachable state, so that the UE may be in a PSM within the preset reachable time period saved by the M2M management platform, and if the M2M management platform sends the downlink data request message to the UE at this time, the UE will exit from the PSM to receive the message, so that the time of the UE in the PSM is shortened, which is not beneficial to saving the power of the UE, and thus the standby time of the UE is shortened.
Disclosure of Invention
The embodiment of the invention provides a method and a device for sending a message to UE (user equipment) and an M2M management platform, which are used for solving the problem that the standby time of the UE is shortened because a PSM (pulse position modulation) timer in a network server is asynchronous with a preset reachable time list in the M2M management platform.
A first aspect of an embodiment of the present invention provides a method for sending a message to a user equipment UE. Firstly, an M2M management platform receives a downlink data request message sent by an application server AS, wherein the downlink data request message comprises an identifier of a target UE; the M2M management platform searches a locally stored preset reachable time list of the target UE according to the identification of the target UE, the preset reachable time list stores information of a preset reachable time period of the target UE, and the preset reachable time period refers to a time period of the UE in a reachable state predicted according to the time when the UE enters an Idle state, the Idle state duration of the UE in a PSM timer and a position updating period; the M2M management platform determines that a source parameter in the preset reachable time list is a Network, where the source parameter is a Network indicating that the starting time of the preset reachable time period in the preset reachable time list is the same as the starting time of an Idle state timer set for the target UE in a Network server, that is, the preset reachable time list is synchronized with a PSM timer in the Network server; the M2M management platform judges whether the current time T1 is within the preset reachable time period; if yes, the M2M management platform sends the downlink data request message to the target UE.
Since the source parameter of the preset reachable time list in the M2M management platform is Network, that is, the preset reachable time list is synchronized with the PSM timer in the Network server. Therefore, when the current time T1 is within the preset reachable period, the current time T1 is also within the specified Idle state period of the PSM timer in the web server, not within the specified PSM period of the PSM timer in the web server. The M2M management platform sends the downlink data request message to the UE at T1, which does not reduce the PSM period of the UE and ensures that the UE has a longer standby time.
In some implementations of the first aspect, the downlink data request message further includes a request expiration timestamp and an operation execution time; when the M2M management platform judges whether the T1 is located within the preset reachable time period, determining the starting time T2 of the next preset reachable time period after T1 according to the preset reachable time list; judging whether the request expiration timestamp and the operation execution time are both later than T2; if so, the M2M management platform sends the downlink data request message to the target UE within a next preset reachable time period after the T1 and before the expiration timestamp and the operation execution time. When the M2M management platform is not located in the preset reachable time period at the current time T1, the M2M management platform can send the downlink data request message to the target UE within the next preset reachable time period and before the expiration timestamp and the operation execution time, so that the UE can receive the downlink data request message in time, and the UE can obtain the downlink application data sent by the AS soon AS possible.
In some implementations of the first aspect, when determining that the request expiration timestamp and the operation execution time are both later than T2, the M2M management platform returns an error response to the AS that the downlink data request message cannot be sent to the target UE, and informs the AS that the downlink data request message cannot be successfully sent.
In some implementations of the first aspect, when determining that the request expiration timestamp is earlier than T2, the M2M management platform returns to the AS an error response that the downlink data request message cannot be sent to the target UE before the request expiration timestamp, so that the AS corrects the request expiration timestamp set for the downlink data request message.
In some implementations of the first aspect, when the M2M management platform determines that the request expiration timestamp is later than T2 and the operation execution time is earlier than T2, the M2M management platform returns an error to the AS that the downlink data request message cannot be sent to the target UE before the operation execution time, so that the AS can correct the operation execution time set for the downlink data request message.
In some implementations of the first aspect, when the M2M management platform determines that any one of the request expiration timestamp and the operation execution time is earlier than T2, the M2M management platform sends, to the AS, information of a preset reachable time period in the preset reachable time list, where the information of the preset reachable time period is used to indicate that the request expiration timestamp and the operation execution time in the downlink data request message are modified to reach times that have not yet arrived, so that the M2M management platform can send the downlink data request message with the modified time limit parameter to the UE within the preset reachable time period. .
In some implementations of the first aspect, the M2M management platform subscribes to an Idle state of the target UE from a network server to receive a registration request of the target UE, where the registration request includes information of a preset reachable time period of the target UE; locally creating the preset reachable time list for the target UE, wherein the preset reachable time list comprises the preset reachable time period in the registration request; receiving an Idle state report of the target UE returned by the network server, wherein the Idle state report comprises an identifier of the target UE and the time when the target UE enters an Idle state, and when the network server detects that the UE is switched from a Connected state to the Idle state, sending the Idle state report to an M2M management platform; taking the moment when the target UE enters the Idle state as the starting moment of the preset reachable time period; and setting the source parameter of the preset reachable time list as Network. In this implementation, after the M2M management platform synchronizes the preset reachable time list with the PSM timer set in the Network server, the source parameter of the preset reachable time list is set to Network to indicate that the preset reachable time list is synchronized with the PSM timer set in the Network server. After receiving a downlink data request message sent to the UE by the AS request, the M2M management platform determines when to send the downlink data request message to the UE according to the preset reachable time list, so AS to ensure that the PSM duration of the UE is not reduced.
In some implementation manners of the first aspect, the M2M management platform sends, to the target UE, information that a source parameter is set to a preset reachable time period in the preset reachable time list of the Network. Because the information of the preset reachable time period sent by the M2M management platform to the UE is synchronized with the PSM timer in the network server, the reachable time period locally stored by the UE is synchronized with the PSM timer in the network server, and the time for the UE to keep the Idle state according to the reachable time period locally stored by the UE is in the time period specified by the PSM timer in the network server when the UE is in the Idle state, but not in the time period specified by the PSM timer in the network server when the UE is in the PSM, thereby avoiding the reduction of the PSM time period of the UE caused by the UE keeping the Idle state in the PSM time period specified by the PSM timer and ensuring that the UE has longer standby time.
In some implementations of the first aspect, the M2M management platform further receives a second downlink data request message sent by the AS, where the second downlink data request message includes an identifier of a second target UE; searching a second preset reachable time list of the second target UE, which is locally stored, according to the identifier of the second target UE; determining the source parameter in the second preset reachable time list as a Device; judging whether the current time T3 is within a preset reachable time period in the second preset reachable time list; and if so, sending the second downlink data request message to the second target UE. In this implementation, when the source parameter of the second preset reachable time list in the M2M management platform is set to be Device, the preset reachable time period in the M2M management platform is consistent with the preset reachable time period locally stored by the second target UE, so at the time within the preset reachable time period in the M2M management platform, the UE maintains the Idle state according to the locally stored preset reachable time period. The M2M management platform sends downlink data request messages to the UE in the preset reachable time period in the second preset reachable time list, and the UE is all in Idle state, so as to ensure that the UE can timely and correctly receive the downlink data request messages sent by the M2M management platform.
In some implementations of the first aspect, when the M2M management platform determines that T3 is not located within the preset reachable time period of the second preset reachable time list, determining a time T4 of receiving the message of the second target UE for the last time, and since the UE sends the uplink message to the M2M management platform in the Connected state, if there is no uplink data transmission requirement, switching from the Connected state to the Idle state, a difference between a time T4 of receiving the message of the second target UE for the last time by the M2M management platform and a time when the second target UE switches from the Connected state to the Idle state is small, and a difference between the time T4 and the time when the second target UE switches from the Connected state to the Idle state is negligible, in an embodiment of the present invention, the time T4 is regarded as a time when the second target UE switches from the Connected state to the Idle state; judging whether the difference value between the T3 and the T4 is larger than the Idle state duration of the second target UE; if not, the M2M management platform sends the second downlink data request message to the second target UE. In this embodiment, when the difference between the current time T3 and the time T4 is not greater than the Idle state duration of the second target UE, the M2M management platform may determine that the time interval between the current time T3 and the time when the second target UE switches from the Connected state to the Idle state has not exceeded the Idle state duration of the second target UE, indicating that the current time T3 is still within the Idle state duration specified by the PSM timer of the network server. The M2M management platform sends the second downlink data request message to the second target UE at time T3, which not only enables the second target UE to receive the second downlink data request message in time. Moreover, since the time T3 at which the M2M management platform sends the second downlink data request message to the second target UE is within the Idle state time period specified by the PSM timer of the network server, rather than within the PSM time period specified by the PSM timer of the network server, sending the second downlink data request message to the second target UE at the M2M management platform does not result in a reduction in the PSM time period of the second target UE, and ensures that the second target UE has a longer standby time.
In some implementation manners of the first aspect, when the M2M management platform determines that the difference between T3 and T4 is greater than the Idle-state duration of the second target UE, the M2M management platform returns an error response indicating that the second target UE is currently in an unreachable state to the AS, and informs the AS that the second downlink data request message is not successfully sent to the second target UE.
A second aspect of the embodiments of the present invention provides a synchronization method. Firstly, the M2M management platform subscribes the Idle state of the target UE to a network server; then, the M2M management platform receives a registration request of the target UE, where the registration request includes information of a preset reachable time period of the target UE; then, the M2M management platform locally creates a preset reachable time list for the target UE, where the preset reachable time list includes the preset reachable time period in the registration request; then, the M2M management platform receives an Idle status report of the target UE returned by the network server, where the Idle status report includes an identifier of the target UE and a time when the target UE enters an Idle state; then, the M2M management platform takes the time when the target UE enters the Idle state as the starting time of the preset reachable time period; setting the source parameter of the preset reachable time list as Network; then, the M2M management platform sends information of a preset reachable time period in the preset reachable time list to the target UE. In this implementation, after the M2M management platform synchronizes the preset reachable time list with the PSM timer set in the Network server, the source parameter of the preset reachable time list is set to Network to indicate that the preset reachable time list is synchronized with the PSM timer set in the Network server. After receiving a downlink data request message sent to the UE by the AS request, the M2M management platform determines when to send the downlink data request message to the UE according to the preset reachable time list, so AS to ensure that the PSM duration of the UE is not reduced.
In some implementations of the first aspect or the second aspect, before the M2M, before the searching, according to the identifier of the target UE, a locally stored preset reachable time list of the target UE, the method further includes:
the M2M management platform receives a registration request of the target UE, wherein the registration request comprises information of a preset reachable time period of the target UE;
the M2M management platform locally creates the preset reachable time list for the target UE, where the preset reachable time list includes the preset reachable time period in the registration request.
In some implementations of the first or second aspect, the Idle status report further includes an Idle status duration and a location update period of the target UE; or, the Idle state timer in the network server is set by the M2M management platform, and the M2M management platform stores the Idle state duration and the location update period; after the M2M management platform takes the time when the target UE enters the Idle state as the starting time of the preset reachable time period, the method further includes: the M2M management platform takes the time when the target UE enters the Idle state plus the time of the Idle state duration as the end time of the preset reachable time period in the preset reachable time list; and taking the position updating period as a time interval between adjacent preset reachable time periods in the preset reachable time list. The embodiment can avoid the inconsistency of the duration of the preset reachable time period and the duration of the Idle state or the inconsistency of the interval between adjacent preset reachable time periods and the position updating period caused by possible errors, and ensure that the preset reachable time list is synchronous with the PSM timer set in the network server.
A third aspect of embodiments of the present invention provides an apparatus for sending a message to a UE, where the apparatus is configured to perform the method in the first aspect or any possible implementation of the first aspect. In particular, the apparatus comprises means for performing the method of the first aspect described above or any possible implementation of the first aspect.
A fourth aspect of the embodiments of the present invention provides an apparatus for sending a message to a UE, where the apparatus is configured to perform the method in the second aspect or any possible implementation of the second aspect. In particular, the apparatus comprises means for performing the method of the second aspect described above or any possible implementation of the second aspect.
A fifth aspect of embodiments of the present invention provides an M2M management platform, where the M2M management platform is configured to execute the method in the first aspect or any possible implementation of the first aspect. Specifically, the M2M management platform includes a processor, and a memory, a first communication interface and a second communication interface respectively connected to the processor; the first communication interface is to: receiving a downlink data request message sent by an AS, wherein the downlink data request message comprises an identifier of a target UE; the second communication interface is to: communicating with the target UE; the memory is to: storing a preset reachable time list of the target UE, wherein the preset reachable time list stores information of a preset reachable time period of the target UE; the processor is configured to perform the method of the first aspect or any possible implementation of the first aspect through the memory, the first communication interface, and the second communication interface.
A sixth aspect of embodiments of the present invention provides an M2M management platform, where the M2M management platform is configured to perform a method in the second aspect or any possible implementation of the second aspect. Specifically, the M2M management platform includes a second processor, and a second memory, a fourth communication interface, and a fifth communication interface respectively connected to the second processor; the fourth communication interface is configured to: communicating with a network server; the fifth communication interface is configured to: receiving a registration request of the target UE, wherein the registration request comprises information of a preset reachable time period of the target UE; the second processor is configured to perform the method of the second aspect or any possible implementation of the second aspect through the second memory, the fourth communication interface, and the fifth communication interface.
A seventh aspect of embodiments of the present invention provides a computer-readable medium for storing a computer program comprising instructions for performing the first aspect or the method in any possible implementation of the first aspect.
An eighth aspect of embodiments of the present invention provides a computer-readable medium for storing a computer program comprising instructions for performing the second aspect or the method in any possible implementation of the second aspect.
The present application may be further combined to provide further implementations on the basis of the implementations provided by the above aspects.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that are required to be used in the description of the embodiments will be briefly described below.
FIG. 1 is a diagram illustrating an idle state and a power saving mode of a UE;
fig. 2 is a schematic flowchart illustrating a process of setting a PSM timer at a network server and setting a preset reachable time list for the UE at an M2M management platform according to the prior art;
FIG. 3 is a schematic diagram of a communication system according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a communication system according to an embodiment of the present invention applied to a 3GPP network;
FIG. 5 is a flowchart illustrating a method for sending a message to a UE according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating a list of pre-set reachable times in an embodiment of the invention;
fig. 7 is a schematic flowchart of a synchronization method according to an embodiment of the present invention;
fig. 8 is another flowchart illustrating a method for sending a message to a UE according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of an apparatus 50 for sending a message to a UE according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of an apparatus 60 for sending a message to a UE according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of an M2M management platform 70 according to an embodiment of the present invention;
fig. 12 is a schematic structural diagram of an M2M management platform 80 according to an embodiment of the present invention;
fig. 13 is a schematic structural diagram of a network server 900 according to an embodiment of the present invention;
fig. 14 is a functional block diagram of a network server 1000 according to an embodiment of the present invention;
Detailed Description
In order to facilitate understanding of the technical solutions provided by the embodiments of the present invention, the related prior art is described below.
Fig. 1 is a diagram illustrating Idle state and power saving mode PSM of a UE. When the UE is in a connectable Connected state, if there is no uplink data transmission requirement, the UE enters an Idle state, and the UE maintains the Idle state for a preset time. And if the UE has an uplink data transmission requirement in the Idle state, switching to the Connected state for data transmission. If there is no uplink data transmission requirement within the preset duration, the UE switches to the power saving mode PSM. And when the UE is in the PSM, the radio frequency module is closed to save power, and the UE is switched to a Connected state after maintaining the PSM for another preset time to check whether a data transmission requirement exists. The time period in which the UE is in the Idle state is referred to as an reachable time period of the UE.
Fig. 2 is a schematic diagram of a process of setting a PSM timer at a network server and setting a preset reachable time list at an M2M management platform for a UE, where the process includes the following steps:
step 101, the UE negotiates with the network server to determine a parameter of a power saving mode timer PSM timer of the UE.
The negotiation process may be implemented by an attach (attach) procedure, a Tracking Area Update (TAU) procedure, or a Route Area Update (RAU) procedure of the UE. The parameters of the PSM timer include an Idle state duration of the UE and a location update period of the UE, which may be a TAU period or a RAU period. Referring to fig. 1, the Idle state duration of the UE refers to a duration between the time when the UE enters the Idle state and the time when the UE switches to the PSM, and the duration when the UE maintains the PSM is obtained by subtracting the Idle state duration of the UE from the location update period. For convenience of differentiation, in the embodiment of the present invention, the duration of the Idle state of the UE is referred to as a first preset duration, the location update period is referred to as a second preset duration, and the duration of the PSM maintenance of the UE is referred to as a third preset duration.
Step 102, the network server returns the set PSM timer parameter to the UE.
The PSM timer parameter includes the Idle status duration of the UE and the location update period of the UE.
Step 103, the UE sets a local PSM timer according to the PSM timer parameter returned by the network server.
The PSM timer parameter local to the UE is consistent with the PSM timer parameter returned by the network server.
And step 104, the UE determines the preset reachable time period of the UE according to the local PSM timer.
The preset reachable time period refers to a time period in which the UE is expected to be in a reachable state according to the time when the UE enters the Idle state, the Idle state duration of the UE in the PSM timer, and the location update period.
For example, a timestamp (timestamp) when the UE enters the Idle state is 2:00, the duration of the Idle state of the UE is 30min, a location update period is 4 hours, and a preset reachable time period of the UE is: 2:00-2:30,6:00-6:30, 10:00-10:30, 14:00-14:30, 18:00-18:30, 22:00-22:30.
Step 105, the UE sends an uplink message to the M2M management platform, where the uplink message includes information of a preset reachable time period of the UE.
Step 106, the M2M management platform creates a preset time period list for the UE, where the preset reachable time period list includes the preset reachable time period of the UE.
Referring to table 1, the preset time period list may be represented by a schedule (schedule).
Figure BDA0001279095880000061
Figure BDA0001279095880000071
TABLE 1
Wherein the value 0 in "number of weeks" means sunday.
In the above example where the time stamp in the Idle state is 2:00, the preset reachable time list is set to have a numerical value of "0 to 30" in the "score" column and "2, 6, 10, 14, 18, 22" in the "number of hours" column, as shown in the format of table 1.
In step 107, the M2M management platform sets a PSM timer for the UE in the network server according to the preset time period list.
The M2M management platform can determine the duration of Idle state and the location update period according to the preset time period list, and set the PSM timer for the UE in the network server according to the determined parameters.
In step 108, the UE synchronizes the parameters of the PSM timer from the network server.
The UE may synchronize the parameters of the PSM timer from the network server through the TAU procedure.
Although the PSM timer set for the UE in the network server and the preset reachable time list stored for the UE in the M2M management platform can be temporarily synchronized through the above procedure, that is, the preset reachable time period in the preset reachable time list coincides with the reachable time period determined according to the PSM timer. However, the above synchronization is not sustainable, and as the UE runs, the PSM timer in the network server becomes out of synchronization with the preset reachable time list in the M2M management platform.
This is because the preset time period in the preset reachable time list in the M2M management platform is an absolute time period, having a certain start time and end time. The UE's reachable period specified by the PSM timer in the network server is dynamic, with the start time depending on when the UE switches to Idle state due to no uplink data transmission need in the Connected state. Therefore, as the UE operates, the time when the UE switches from the Connected state to the Idle state is necessarily deviated from the fixed starting time of the preset time period in the M2M management platform, so that the PSM timer in the network server and the preset reachable time list in the M2M management platform become out of synchronization.
The PSM timer in the network server being out of sync with the preset reachable time list in the M2M management platform will in turn result in less PSM periods for the UE. This is because the M2M management platform will send downlink data to the UE in the preset reachable time period of the preset reachable time list, and the UE will switch to Idle state in the locally stored preset reachable time period to receive the downlink data sent by the M2M management platform. However, since the PSM timer in the network server is not synchronized with the pre-set reachable time list in the M2M management platform, the PSM time shall be defined as the time of the PSM in the network server at the time within the pre-set reachable time period in the pre-set reachable time list, for example, at the time 6:20 in the case of the timestamp 2: 00. Therefore, the UE switches to the Idle state at the time when the UE should be in the PSM, which reduces the time when the UE is actually in the PSM, and shortens the standby time of the UE.
In order to solve the problem that the standby time of the UE is shortened due to the fact that the PSM timer in the Network server is not synchronized with the preset reachable time list in the M2M management platform, in the embodiment of the present invention, a source parameter indicating the reachable time list is added to the preset reachable time list of the M2M management platform, when the source parameter is a Network (Network), the M2M management platform determines that the preset reachable time list is synchronized with the PSM timer in the Network server, and sends a downlink data request message to the UE within the preset reachable time period of the preset reachable time list. Because the preset reachable time list is synchronous with the PSM timer in the network server, the time when the M2M management platform sends the downlink data request message to the UE is in the Idle state time period defined by the PSM timer in the network server, so that the UE is prevented from being switched to the Idle state in the PSM time period specified by the PSM timer, the PSM time period of the UE is ensured not to be reduced, and the UE has longer standby time.
The embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
The techniques described herein may be used in various communication systems, such as 3G, 4G, or next generation communication systems, such as Global System for Mobile communications (GSM), Code Division Multiple Access (Code Division Multiple Access, CDMA) systems, Time Division Multiple Access (TDMA) systems, Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA), Frequency Division Multiple Access (Frequency Division Multiple Access, FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Frequency Division Multiple Access (SC-FDMA) systems, General Packet Radio Service (GPRS) systems, Long Term Evolution (Long Term Evolution, LTE), and other types of communication systems.
Fig. 3 provides a schematic diagram of a communication system of an embodiment of the present invention. The communication system includes a UE10, an M2M management platform 20, a web Server 30, and an Application Server (AS) 40.
The network server 30, which is a generic term for at least one network element in the core network, is configured to provide network services for the UE 10. As in the 3rd Generation Partnership Project (3 GPP) communication system shown in fig. 4, the network server 30 may include: a Short Message Service Center (SMC-SC), a Mobility Management Entity (MME), a Service Gateway (S-GW), a Serving General Packet Radio Service Support Node (SGSN), a Machine Type Communication Interworking Function (MTC-IWF), a Service Capability Exposure Function (SCEF), a Gateway GPRS Support Node (GGSN), and a Public Data Network Gateway (P-GW). It should be noted that the structure shown in fig. 4 is an exemplary illustration, and in some embodiments, the network Server 30 may further include other network elements, such as a Home Subscriber Server (HSS); in other embodiments, the network server 30 may not include some or all of the network elements shown in fig. 4. In this embodiment of the present invention, the network server 30 is further configured to negotiate a parameter of the PSM timer with the UE10, and send the parameter of the PSM timer determined by negotiation to the UE10 (the above-mentioned functions may be implemented by the MME or the HSS). In some embodiments, the network server 30 is further configured to: receiving a request for the M2M management platform 20 to subscribe to the Idle state of the UE10 (this function may be implemented by the SCEF); in response to the request, upon detecting that the UE10 enters the Idle state, an Idle state report of the UE10 is sent to the M2M management platform 20 (this function may be implemented by the MME or HSS), which includes the identity of the UE10 and the time at which the UE10 entered the Idle state.
UE10, refers to a device that provides voice and/or data connectivity to a user and may include, for example, a handheld device having wireless connection capability or a processing device connected to a wireless modem. The UE10 may communicate with a core Network via a Radio Access Network (RAN), exchanging voice and/or data with the RAN. The UE10 may include a mobile phone (or "cellular" phone), a mobile computer, a tablet computer, a Personal Digital Assistant (PDA), a media player, a smart television, and so forth. In the embodiment of the present invention, the UE10 may communicate with the network server 3 in the core network, for example, the UE10 negotiates the parameter of the PSM timer with the network server 30 and receives the parameter of the PSM timer from the network server. The UE10 may also be configured with an application service, and communicate with the M2M management platform 20 through a core network, for example, the UE10 sends a registration request to the M2M management platform 20 through the core network, and may carry information of the preset reachable time period of the UE10 in the registration request, or the UE10 carries information of the preset reachable time period of the UE10 to the M2M management platform 20 through the core network after sending the registration request; for another example, the UE10 receives a downlink data request message sent by the AS40 from the M2M management platform 20 through the core network, and responds to the downlink data request message. In some embodiments, the UE10 is further configured to receive, through the core Network, information that the source parameter sent by the M2M management platform 20 is set to be a preset reachable time period in a preset reachable time list of the Network, update a locally stored preset reachable time period according to the received information of the preset reachable time period, so as to switch to an Idle state in the preset reachable time period, and receive a downlink data request message sent by the M2M management platform 20.
The application server AS40 is configured to provide an application service to the UE10, for example, the AS40 sends a downlink data request message to the UE10, in this embodiment of the present invention, the AS40 sends the downlink data request message to the M2M management platform 20, and requests the M2M management platform 20 to forward the downlink data request message to the UE 10. For another example, the AS40 may be further configured to receive information of a preset reachable time period in the preset reachable time list sent by the M2M management platform 20, and modify the request expiration timestamp and the operation execution time in the downlink data request message to be after the not-yet-arrived reachable time.
The M2M Management platform 20 is used for Device Management (DM) of the UE 10. Specifically, the M2M management platform 20 may set a PSM timer in the network server 30 for the UE 10; the M2M management platform 20 locally saves a preset reachable time list of the UE10, receives a downlink data request message sent by the AS40 to the UE, and determines when to send the downlink data request message to the UE10 according to the saved preset reachable time list. For example, when the source parameter in the preset reachable time list is Network, the M2M management platform 20 determines whether the current time T1 is within the preset reachable time period; if yes, the M2M management platform sends a downlink data request message to the target UE. For another example, if the current time T1 is not within the preset reachable time period, the M2M management platform 20 determines, according to the preset reachable time list, a starting time T2 of a next preset reachable time period after T1; the M2M management platform 20 determines whether the request expiration timestamp and the operation execution time are both later than T2; if so, the M2M management platform buffers the downlink data request message and sends the downlink data request message to the target UE within the next preset reachable time period after T1 and before the expiration timestamp and the operation execution time. For another example, if any one of the request expiration timestamp and the operation execution time is earlier than T2, the M2M management platform returns an error response to the AS40 that the downlink data request message cannot be sent to the target UE. For example, if any one of the request expiration timestamp and the operation execution time is earlier than T2, the M2M management platform 20 sends information of the preset reachable time period in the preset reachable time list to the AS40, and instructs the AS40 to modify the request expiration timestamp and the operation execution time in the downstream data request message to be after the not-yet-arrived reachable time.
Since the source parameter of the preset reachable time list in the M2M management platform is Network, that is, the preset reachable time list is synchronized with the PSM timer in the Network server. Therefore, when the current time T1 is within the preset reachable period, the current time T1 is also within the specified Idle state period of the PSM timer in the web server, not within the specified PSM period of the PSM timer in the web server. The M2M management platform sends the downlink data request message to the UE at T1, which does not reduce the PSM period of the UE and ensures that the UE has a longer standby time.
In some embodiments of the invention, the M2M management platform 20 may also be used to subscribe to the Idle state of the UE10 with the network server 30; receiving a registration request of the UE10, and locally creating a preset reachable time list for the UE according to the information of the preset reachable time period of the UE10 included in the registration request; receiving an Idle state report of the UE returned by the network server 30, and taking a time when the UE enters the Idle state as a starting time of a preset reachable time period according to a time when the UE enters the Idle state included in the Idle state report; and setting the source parameter of the preset reachable time list as Network. In other embodiments, the M2M management platform 20 may further be configured to send, to the UE, information of a preset reachable time period in a preset reachable time list with a source parameter of Network.
In some embodiments of the present invention, the M2M management platform 20 may be further configured to receive a second downlink data request message sent by the AS40, and search a second preset reachable time list of a second target UE stored locally according to an identifier of the second target UE included in the second downlink data request message; determining the source parameter in the second preset reachable time list as the Device; judging whether the current time T3 is within the preset reachable time period in the second preset reachable time list; and if so, sending a second downlink data request message to the second target UE. In other embodiments, the M2M management platform 20 determines the time T4 at which the message of the second target UE was last received when T3 is not within the preset reachable time period of the second preset reachable time list; judging whether the difference value between the T3 and the T4 is larger than the Idle state duration of the second target UE; and if not, the station sends a second downlink data request message to the second target UE. In some embodiments, the M2M management platform 20 returns an error response to the AS when the difference between T3 and T4 is greater than the Idle state duration of the second target UE, with the current second target UE being in an unreachable state.
It should be noted that, in the embodiment of the present invention, the "M2M management platform sends a message to the UE," which means that the M2M management platform sends a message to the UE through the core network. Similarly, the "UE sends a message to the M2M management platform" refers to the UE sending a message to the M2M management platform through the core network. For the sake of convenience, the following description of the embodiments of the present invention is not repeated.
Fig. 5 provides a flowchart of a method for sending a message to a UE in conjunction with the communication system shown in fig. 3 or fig. 4, the method including the steps of:
step 201, the AS sends a downlink data request message to the M2M management platform, where the downlink data request message includes an identifier of the target UE.
Step 202, the M2M management platform receives the downlink data request message sent by the AS, and searches a locally stored preset reachable time list of the target UE according to the identifier of the target UE.
The preset reachable time list holds information of the preset reachable time period of the target UE, and the creation process of the preset reachable time list is described in the foregoing steps 105 to 106, and is not repeated here.
In step 203, the M2M management platform determines that the source parameter in the preset reachable time list is Network.
In the embodiment of the present invention, a source parameter is added to a preset reachable time list stored by an M2M management platform, and when the source parameter is Network, it indicates that the starting time of a preset reachable time period in the preset reachable time list is the same as the starting time of an Idle-Idle state timer set for a target UE in a Network server, and the preset reachable time list is synchronized with a PSM timer in the Network server.
Fig. 6 is a schematic diagram of one possible implementation of the preset reachable time list, where referring to table 1, a subscription (subscription) indicates a network element subscribed to the preset reachable event list from the M2M management platform, for example, an identifier of one or more ASs subscribed to the preset reachable event list. Wherein, the number "1" refers to the necessary item, and the number of the item is 1, "L" indicates that the item is a list, "0" indicates that the item is optional, "n" indicates that the number of the item can be 2 or more than two.
Step 204, the M2M management platform determines whether the current time T1 is within a preset reachable time period in the preset reachable time list; if yes, go to step 205.
In step 205, the M2M management platform sends a downlink data request message to the target UE.
Since the source parameter of the preset reachable time list in the M2M management platform is Network, that is, the preset reachable time list is synchronized with the PSM timer in the Network server. Therefore, when the current time T1 is within the preset reachable period, the current time T1 is also within the specified Idle state period of the PSM timer in the web server, not within the specified PSM period of the PSM timer in the web server. The M2M management platform sends the downlink data request message to the UE at T1, which does not reduce the PSM period of the UE and ensures that the UE has a longer standby time.
In step 206, the UE receives the downlink data request message and responds to the downlink data request message.
And the UE responds to the downlink data request message and executes the operation requested by the downlink data request message. Optionally, the UE returns a response message for receiving the downlink data request message to the AS through the core network.
It is noted that step 206 is presented for completeness of a scheme and is not a necessary step for implementing an embodiment of the present invention.
As an alternative embodiment, when it is determined through step 204 that the current time T1 is not located within the preset reachable time period in the preset reachable time list, the following steps are continuously performed:
in step 207, the M2M management platform determines the starting time T2 of the next preset reachable time period after T1 according to the preset reachable time list.
The preset reachable time list includes 2 or more preset reachable time periods, when the current time T1 is not located in a preset reachable time period, it indicates that the current time T1 is located at a time between two adjacent preset reachable time periods, and the M2M management platform determines the starting time of the next upcoming preset reachable time period, so as to determine whether to send the downlink data request message in the next preset reachable time period.
In step 208, the M2M management platform determines whether the request expiration timestamp and the operation execution time are both later than T2. If yes, go to step 209.
And the request expiration timestamp and the operation execution time are time limit parameters set by the AS for the downlink data request message, wherein the request expiration timestamp represents the last valid time of the downlink data request message, and the downlink data request message fails when the request expiration timestamp exceeds the request expiration timestamp. The operation execution time indicates a time period for which the operation corresponding to the downlink data request message is executed, and beyond the operation execution time, the operation requested by the downlink data request message will not be executed by the UE.
In step 209, the M2M management platform sends a downlink data request message to the target UE within the next preset reachable time period after T1 and before the expiration timestamp and the operation execution time.
The request expiration timestamp and the operation execution time are both located after the starting time T2 of the next preset reachable time period, which indicates that the sending of the downlink data request message to the UE in at least a part of the next preset reachable time period meets the time limit requirement of AE. Specifically, if the request expiration timestamp and the operation execution time are both later than the end time of the next preset reachable time period, it indicates that the downlink data request message sent to the UE in the next preset reachable time period both meets the time limit requirement of AE; if at least one of the request expiration timestamp and the operation execution time is between the start time and the end time of the next preset reachable time period, the sending of the downlink data request message to the UE in the time period from T2 to the earlier one of the request expiration timestamp and the operation execution time meets the time limit requirement of the AE. Optionally, the M2M management platform sends a downlink data request message to the UE at time T2, so that the UE can receive the message in time.
Through the scheme, when the current time T1 is not within the preset reachable time period, the M2M management platform can cache the downlink data request message for the UE, and send the downlink data request message to the target UE within the next preset reachable time period and before the expiration timestamp and the operation execution time, so that the UE can receive the downlink data request message in time, and the UE can obtain the downlink application data sent by the AS AS soon AS possible.
As an alternative embodiment, when the management platform determines in step M2M that the request expiration timestamp and the operation execution time are not both later than T2, the management platform continues to execute step 210: the M2M management platform returns an error response to the AS that the downlink data request message cannot be sent to the target UE.
Since the request expiration timestamp and the operation execution time are not both later than T2, indicating that the downlink data request message has exceeded the time limit set by the AS before the next preset reachable time period comes, and in the time period from the current time T1 to the start time T2 of the next preset reachable time period, the UE is in PSM, and the M2M management platform cannot send the downlink data request message to the UE. Therefore, the downlink data request message cannot be successfully sent to the UE, and the M2M management platform returns an error response to the AS that the downlink data request message cannot be sent to the target UE, so AS to inform the AS that the downlink data request message cannot be successfully sent.
As an alternative implementation, step 210 may include the following implementation:
first, if the request expiration timestamp is earlier than T2, the M2M management platform returns an error response to the AS that the downlink data request message cannot be sent to the target UE before the request expiration timestamp.
Secondly, if the request expiration timestamp is later than T2 and the operation execution time is earlier than T2, the M2M management platform returns an error to the AS that the downlink data request message cannot be sent to the target UE before the operation execution time.
Since the M2M management platform informs the AS of the exact reason why the downlink data cannot be sent, it is convenient for the AS to correct the request expiration timestamp or the operation execution time set for the downlink data request message, and to send the downlink data request message of the corrected request expiration timestamp or operation execution time to the M2M management platform again, and the M2M management platform can send the downlink data request message to the UE within the preset reachable time period.
As an alternative embodiment, when the management platform determines in step M2M that the request expiration timestamp and the operation execution time are not both later than T2, the following steps are further performed:
in step 211, the M2M management platform sends information of the preset reachable time period in the preset reachable time list to the AS.
The M2M management platform may send information indicating all the preset reachable time periods in the preset reachable time list to the AS, or may send only information indicating the next reachable time period to the AS.
In step 212, the AS modifies the request expiration timestamp and the operation execution time in the downlink data request message to the not-yet-arrived reachable time according to the information of the preset reachable time period, and sends the downlink data request message with the modified expiration timestamp and the modified operation execution time to the UE again.
The AS may set the request expiration timestamp and the operation execution time to be after the end time of the next preset reachable time period, and the M2M management platform may send the downlink data request message to the UE at any time within the next preset time period. The AS may also set the request expiration timestamp and the operation execution time to be between the start time T2 and the end time of the next preset reachable time period, and the M2M management platform may send the downlink data request message to the UE in the time period from T2 to the earlier one of the request expiration timestamp and the operation execution time.
In this optional embodiment, when the M2M management platform cannot send the downlink data request message to the target UE, the AS changes the time limit parameter in the downlink data request message by sending the information of the preset reachable time period of the UE to the AS, so that the M2M management platform can send the downlink data request message with the modified time limit parameter to the UE within the preset reachable time period.
It should be noted that the step 211 may be executed simultaneously with the step 210, or the step 210 is executed first and then the step 211 is executed, or the step 211 is executed first and then the step 210 is executed.
Fig. 7 is a flowchart illustrating a synchronization method according to another embodiment of the present invention, where the synchronization method includes the following steps:
in step 301, the M2M management platform subscribes to the Idle status of the target UE from the network server.
As an example, in the communication system shown in fig. 4, the M2M management platform calls an API interface to set the subscription information of the UE Idle status to the SCEF by using an External Identifier (External Identifier) or a Mobile Station Integrated Services Digital Network Number (MSISDN) pre-issued for the M2M management platform. The SCEF sends the subscription information of the UE Idle state to the HSS/MME through the S6t interface, the HSS/MME subscribes the Idle state of the UE for the M2M management platform according to the subscription information of the UE Idle state, and sends an Idle state report of the UE to the M2M management platform when the UE connected state is switched to the Idle state.
Step 302, the M2M management platform receives a registration request of the target UE, where the registration request includes information of a preset reachable time period of the target UE.
Step 302 may be performed after step 301 or before step 301, and the embodiment of the present invention is not limited thereto.
Step 303, the M2M management platform locally creates a preset reachable time list for the target UE, where the preset reachable time list includes the preset reachable time period in the registration request.
Step 304, when detecting that the UE switches from the Connected state to the Idle state, the network server generates an Idle state report of the UE, and sends the Idle state report to the M2M management platform. The Idle status report includes the identity of the target UE and the time at which the target UE entered the Idle state.
The embodiment of the invention improves the parameters of the communication interface in the network server so as to send the information in the Idle state report to the M2M management platform through the communication interface. For example, taking the structure shown in fig. 4 as an example, a "UE-Idle-Timestamp" parameter is added to both the interface for communication between the MME and the SCEF and the interface for communication between the SCEF and the M2M management platform, so as to carry the time when the target UE enters the Idle state, thereby implementing that the MME sends the time when the target UE enters the Idle state to the SCEF, and the SCEF sends the time when the target UE enters the Idle state to the M2M management platform.
In step 305, the M2M management platform updates the locally stored preset reachable time list according to the Idle status report.
The M2M management platform locates a preset reachable time list created for the target UE according to the identifier of the target UE in the Idle status report, and takes the time when the target UE enters the Idle status as the starting time of the preset reachable time period.
The M2M management platform generates the preset reachable time list according to the information of the preset reachable time period sent by the UE, and the time interval between adjacent preset reachable time periods in the information of the preset reachable time period sent by the UE is equal to the location update period in the PSM timer parameter negotiated by the UE and the network server, and the duration of each preset reachable time period is equal to the Idle state duration in the PSM timer parameter. Therefore, the time interval between adjacent preset reachable time periods in the preset reachable time list in the M2M management platform is equal to the location update period specified by the PSM timer set in the network server, and the duration of each preset reachable time period in the preset reachable time list in the M2M management platform is equal to the Idle state duration specified by the PSM timer set in the network server. Therefore, the M2M management platform can synchronize the preset reachable time list with the PSMtimer set in the network server as long as the time when the target UE enters the Idle state is taken as the starting time of the preset reachable time period.
Step 306, the M2M management platform sets the source parameter of the preset reachable time list as Network.
After the M2M management platform synchronizes the pre-set reachable time list with the PSM timer set in the Network server, the source parameter of the pre-set reachable time list is set to Network to indicate that the pre-set reachable time list has been synchronized with the PSM timer set in the Network server. After receiving the downlink data request message sent by the AS request to the UE, the M2M management platform may determine when to send the downlink data request message to the UE through the above steps 203 to 211, so AS to ensure that the PSM duration of the UE is not reduced.
As an alternative embodiment, in step 305, the M2M management platform further updates the preset reachable time list through the Idle state duration and the location update period in the PSM timer parameter. Specifically, the M2M management platform takes the time when the target UE enters the Idle state plus the time length of the Idle state as the end time of the preset reachable time period in the preset reachable time list; and taking the position updating period as a time interval between adjacent preset reachable time periods in the preset reachable time list.
The M2M management platform may obtain the Idle state duration and the location update period through a variety of ways, including:
firstly, the Idle status report generated by the network server further includes the Idle status duration and the location update period of the target UE, and the M2M management platform obtains the Idle status duration and the location update period from the received Idle status report.
Taking the structure shown in fig. 4 as an example, a parameter for carrying the Idle state duration and a parameter for carrying the location update period are added to both an interface for communication between the MME and the SCEF and an interface for communication between the SCEF and the M2M management platform, so that the purpose that the MME sends the Idle state duration and the location update period to the SCEF and the SCEF sends the Idle state duration and the location update period to the M2M management platform is achieved.
Secondly, the PSM timer of the UE in the network server is set for the UE by the M2M management platform, so the M2M management platform stores parameters such as the Idle state duration and the location update period of the PSM timer in the network server, and the M2M management platform can read the locally stored parameters.
Although the M2M management platform creates the preset reachable time list, the duration of the preset reachable time period is equal to the duration of the Idle state in the PSM timer parameter, and the interval between adjacent preset reachable time periods is equal to the location update period in the PSM timer parameter, after receiving the Idle state report, the M2M management platform still updates the preset reachable time list through the duration of the Idle state and the location update period in the PSM timer parameter, so as to avoid inconsistency between the duration of the preset reachable time period and the duration of the Idle state or inconsistency between adjacent preset reachable time periods and the location update period due to possible errors, and ensure that the preset reachable time list is synchronized with the PSM timer set in the network server.
As an optional implementation manner, after step 306, the following steps are further included:
step 307, the M2M management platform sends information of the preset reachable time period in the preset reachable time list with the source parameter set as Network to the target UE.
The information of the preset reachable time period may be the preset reachable time list itself, or may be information that only indicates the preset reachable time period in the reachable time list. After synchronizing the locally stored preset reachable time list with the PSM timer in the network server, the M2M management platform sends the information of the preset reachable time period in the preset reachable time list to the UE, so that the UE updates the locally stored preset reachable time period according to the information of the preset reachable time period.
Step 308, the UE receives the information of the preset reachable time period sent by the M2M management platform, and updates the locally stored preset reachable time period according to the received information of the preset reachable time period.
The reachable time period locally stored by the UE is used to indicate that the UE maintains the Idle state in the reachable time period, so that the UE can receive the downlink data request message possibly sent by the M2M management platform in the preset reachable time period.
Because the information of the preset reachable time period sent by the M2M management platform to the UE is synchronized with the PSM timer in the network server, the reachable time period locally stored by the UE is synchronized with the PSM timer in the network server, and the time for the UE to keep the Idle state according to the reachable time period locally stored by the UE is in the time period specified by the PSM timer in the network server when the UE is in the Idle state, but not in the time period specified by the PSM timer in the network server when the UE is in the PSM, thereby avoiding the reduction of the PSM time period of the UE caused by the UE keeping the Idle state in the PSM time period specified by the PSM timer and ensuring that the UE has longer standby time.
As an alternative implementation manner of all the foregoing embodiments, referring to fig. 8, the method provided in the embodiment of the present invention further includes the following steps:
in step 401, the AS sends a second downlink data request message to the M2M management platform, where the second downlink data request message includes an identifier of the second target UE.
Step 402, the M2M management platform receives a second downlink data request message sent by the AS, and searches a second preset reachable time list of the second target UE stored locally according to the identifier of the second target UE.
In step 403, the M2M management platform determines the source parameter in the second list of pre-set reachable times as the Device.
When the second target UE registers in the M2M management platform, the M2M management platform sends information of the preset reachable time period of the second target UE to the M2M management platform, and creates a preset reachable time list for the second target UE according to the information of the preset reachable time period of the second target UE, and sets a source parameter of the preset reachable time list as Device, which indicates that the preset reachable time period in the preset reachable time list is determined by the UE.
In step 404, the M2M management platform determines whether the current time T3 is within the preset reachable time period in the second preset reachable time list. If yes, go to step 405.
In step 405, the M2M management platform sends a second downlink data request message to the second target UE.
Since the preset reachable time period in the M2M management platform is consistent with the preset reachable time period locally stored by the second target UE when the source parameter of the second preset reachable time list in the M2M management platform is set as Device, the UE maintains the Idle state according to the locally stored preset reachable time period at the time within the preset reachable time period in the M2M management platform. The M2M management platform sends downlink data request messages to the UE in the preset reachable time period in the second preset reachable time list, and the UE is all in Idle state, so as to ensure that the UE can timely and correctly receive the downlink data request messages sent by the M2M management platform.
As an alternative implementation manner, when it is determined that T3 is not located within the preset reachable time period of the second preset reachable time list through step 404, the method further includes the following steps:
at step 406, the M2M management platform determines the time T4 at which the message for the second target UE was last received.
The M2M management platform records a history record of receiving uplink messages sent by the second target UE, or records only a record of last receiving uplink messages of the second target UE, and the M2M management platform determines the time T4 of last receiving messages of the second target UE according to the records.
Step 407, the M2M management platform determines whether the difference between T3 and T4 is greater than the Idle state duration of the second target UE; if not, go to step 408.
Since the time interval between adjacent reachable time periods in the second preset reachable time list in the M2M management platform is equal to the Idle state duration of the second target UE, the M2M management platform may determine the Idle state duration of the second target UE according to the time interval between adjacent reachable time periods in the second preset reachable time list. Alternatively, the M2M management platform may obtain the Idle state duration of the second target UE in the manner described in two of the manners described above when the M2M management platform obtains the Idle state of the target UE in step 305, which is not repeated here.
In step 408, the M2M management platform sends a second downlink data request message to the second target UE.
Referring to fig. 1, after the UE is in the Connected state and sends the uplink message to the M2M management platform, if there is no uplink data transmission requirement, the Connected state is switched to the Idle state, so the time T4 when the M2M management platform receives the message of the second target UE for the last time is very different from the time when the second target UE is switched from the Connected state to the Idle state, and the difference between the two times is negligible. In the embodiment of the present invention, the M2M management platform regards the T4 as the time when the second target UE switches from the Connected state to the Idle state.
When the difference between the current time T3 and the time T4 is not greater than the Idle state duration of the second target UE, the M2M management platform may determine that the time interval between the current time T3 and the time when the second target UE switches from the Connected state to the Idle state has not exceeded the Idle state duration of the second target UE, indicating that the current time T3 is still within the Idle state duration specified by the PSM timer of the network server. The M2M management platform sends the second downlink data request message to the second target UE at time T3, which not only enables the second target UE to receive the second downlink data request message in time. Moreover, since the time T3 at which the M2M management platform sends the second downlink data request message to the second target UE is within the Idle state time period specified by the PSM timer of the network server, rather than within the PSM time period specified by the PSM timer of the network server, sending the second downlink data request message to the second target UE at the M2M management platform does not result in a reduction in the PSM time period of the second target UE, and ensures that the second target UE has a longer standby time.
As an optional implementation manner, when it is determined that the difference between T3 and T4 is greater than the Idle state duration of the second target UE through step 407, step 409 is further included: the M2M management platform returns an error response to the AS that the current second target UE is in the unreachable state.
When the difference between T3 and T4 is greater than the Idle state duration of the second target UE, the M2M management platform may determine that the time interval between the current time T3 and the time when the second target UE switches from the Connected state to the Idle state has exceeded the Idle state duration of the second target UE, indicating that the current time T3 is not within the Idle state duration specified by the PSM timer of the network server. Also, the M2M management platform has also determined that T3 is not located within the preset reachable time period of the second preset reachable time list through step 404, so the M2M management platform may determine that the second target device is not in a reachable state at the current time T3, and if the M2M management platform sends the second downlink data request message to the second target device at T3, the second target UE cannot receive the second downlink data request message. Therefore, the M2M management platform does not send the second downlink data request message to the second target UE, but returns an error response indicating that the second target UE is currently in an unreachable state to the AS, and informs the AS that the second downlink data request message is not successfully sent to the second target UE.
Fig. 9 is a schematic structural diagram of an apparatus 50 for sending a message to a UE according to another embodiment of the present invention, where the apparatus 50 includes:
a first receiving module 51, configured to receive a downlink data request message sent by an AS, where the downlink data request message includes an identifier of a target UE;
a determination module 52 configured to: searching a preset reachable time list of the target UE, which is locally stored, according to the identifier of the target UE, wherein the preset reachable time list stores information of a preset reachable time period of the target UE; determining that a source parameter in the preset reachable time list is Network, wherein the source parameter is Network indicating that the starting time of the preset reachable time period in the preset reachable time list is the same as the starting time of an Idle state timer set for the target UE in a Network server;
the judging module 53 judges whether the current time T1 is within the preset reachable time period;
a sending module 54, configured to send the downlink data request message to the target UE when the determining module 53 determines that the T1 is located within the preset reachable time period.
As an optional implementation manner, the downlink data request message further includes a request expiration timestamp and an operation execution time;
the determining module 53 is further configured to: when the T1 is judged not to be within the preset reachable time period, determining the starting time T2 of the next preset reachable time period after T1 according to the preset reachable time list; judging whether the request expiration timestamp and the operation execution time are both later than T2;
the sending module 54 is further configured to: when the determining module 53 determines that the request expiration timestamp and the operation execution time are both later than T2, the downlink data request message is sent to the target UE within the next preset reachable time period after T1 and before the expiration timestamp and the operation execution time.
As an optional implementation manner, the sending module 54 is further configured to: when the determining module 53 determines that any one of the request expiration timestamp and the operation execution time is earlier than T2, an error response indicating that the downlink data request message cannot be sent to the target UE is returned to the AS.
As an optional implementation manner, the sending module 54 is further configured to: when the determining module 53 determines that any one of the request expiration timestamp and the operation execution time is earlier than T2, sending information of a preset reachable time period in the preset reachable time list to the AS, where the information of the preset reachable time period is used to indicate that the request expiration timestamp and the operation execution time in the downlink data request message are modified to be after the unreachable time that has not yet arrived.
As an optional implementation, the apparatus 50 further includes:
a second receiving module 56, configured to receive a registration request of the target UE, where the registration request includes information of a preset reachable time period of the target UE;
a creating module 57, configured to create the preset reachable time list locally for the target UE, where the preset reachable time list includes the preset reachable time period in the registration request.
As an optional implementation, the apparatus 50 further includes:
a subscription module 55, configured to subscribe to an Idle state of the target UE from a Network server before the determining module 52 determines that the source parameter in the preset reachable time list is Network;
a third receiving module 58, configured to receive an Idle status report of the target UE returned by the network server, where the Idle status report includes an identifier of the target UE and a time when the target UE enters an Idle status;
an adjusting module 59, configured to use a time when the target UE enters an Idle state as a starting time of the preset reachable time period; and setting the source parameter of the preset reachable time list as Network.
As an optional implementation manner, the Idle status report further includes an Idle status duration and a location update period of the target UE; or, the Idle state timer in the network server is set by the M2M management platform, and the M2M management platform stores the Idle state duration and the location update period;
the adjusting module 59 is further configured to:
taking the time when the target UE enters the Idle state plus the time of the Idle state duration as the ending time of the preset reachable time period in the preset reachable time list; and
and taking the position updating period as a time interval between adjacent preset reachable time periods in the preset reachable time list.
As an optional implementation manner, the sending module 54 is further configured to: and sending the information of the preset reachable time period in the preset reachable time list adjusted by the adjusting module to the target UE.
As an optional implementation manner, the first receiving module 51 is further configured to: receiving a second downlink data request message sent by the AS, wherein the second downlink data request message comprises an identifier of a second target UE;
the determination module 52 is further configured to: searching a second preset reachable time list of the second target UE, which is locally stored, according to the identifier of the second target UE; determining the source parameter in the second preset reachable time list as a Device;
the determining module 53 is further configured to: judging whether the current time T3 is within a preset reachable time period in the second preset reachable time list;
the sending module 54 is further configured to: and when the determining module determines that T3 is located within the preset reachable time period in the second preset reachable time list, sending the second downlink data request message to the second target UE.
As an optional implementation manner, the determining module 53 is further configured to: determining a time T4 of last receiving of the message of the second target UE when it is judged that T3 is not located within the preset reachable time period of the second preset reachable time list; judging whether the difference value between the T3 and the T4 is larger than the Idle state duration of the second target UE;
the sending module 54 is further configured to: and when the judging module judges that the difference value between the T3 and the T4 is not greater than the Idle state duration of the second target UE, sending the second downlink data request message to the second target UE.
The implementation of each module of the apparatus 50 refers to the implementation of the method corresponding to fig. 5 to 8, and is not described in detail herein.
Fig. 10 is a schematic structural diagram of an apparatus 60 for updating a preset reachable time list according to another embodiment of the present invention, including:
a second subscription module 61, configured to subscribe to the Idle state of the target UE from the network server;
a fourth receiving module 62, configured to receive a registration request of the target UE, where the registration request includes information of a preset reachable time period of the target UE;
a second creating module 63, configured to create a preset reachable time list locally for the target UE, where the preset reachable time list includes the preset reachable time period in the registration request;
a fifth receiving module 64, configured to receive an Idle status report of the target UE returned by the network server, where the Idle status report includes an identifier of the target UE and a time when the target UE enters an Idle status;
a second adjusting module 65 configured to: taking the moment when the target UE enters the Idle state as the starting moment of the preset reachable time period; setting the source parameter of the preset reachable time list as Network;
a second sending module 66, configured to send information of a preset reachable time period in the preset reachable time list to the target UE.
The implementation of each module of the apparatus 60 refers to the implementation of the method corresponding to fig. 7, and is not described in detail herein.
Fig. 11 is a schematic structural diagram of an M2M management platform 70 according to another embodiment of the present invention, in which the M2M management platform 70 includes a bus 71, and a processor 72, a memory 73, a first communication interface 74 and a second communication interface 75 respectively connected to the bus 71.
The first communication interface 74 is configured to: receiving a downlink data request message sent by an AS, wherein the downlink data request message comprises an identifier of a target UE.
As an example, when the M2M management platform 70 is applied to the communication system shown in fig. 4, the first communication interface 74 is an Mca interface.
The second communication interface is to: communicating with a core network.
As an example, in the case of the communication system shown in fig. 4, the second communication Interface 75 may be an Application Programming Interface (API) or an Mcn Interface for communicating with the SCEF.
The memory 73 is used for: storing a preset reachable time list of the target UE, wherein the preset reachable time list stores information of a preset reachable time period of the target UE;
the processor 72 is configured to:
searching a preset reachable time list of the target UE, which is locally stored, according to the identifier of the target UE, wherein the preset reachable time list stores information of a preset reachable time period of the target UE;
determining that a source parameter in the preset reachable time list is Network, wherein the source parameter is that Network indicates that the starting time of the preset reachable time period in the preset reachable time list is the same as the starting time of an Idle state timer set for the target UE in a Network server of a core Network;
judging whether the current time T1 is within the preset reachable time period;
if yes, the second communication interface 75 is instructed to send the downlink data request message to the target UE through a core network.
The second communication interface 75 is further configured to send the downlink data request message to the target UE through the core network in response to the indication from the processor 72.
As an optional implementation manner, the downlink data request message further includes a request expiration timestamp and an operation execution time; the processor 72 is further configured to: when the T1 is judged not to be within the preset reachable time period, determining the starting time T2 of the next preset reachable time period after T1 according to the preset reachable time list; judging whether the request expiration timestamp and the operation execution time are both later than T2; if yes, the downlink data request message is sent to the target UE through the second communication interface 75 within a next preset reachable time period after the T1 and before the expiration timestamp and the operation execution time.
As an alternative implementation, the processor 72 is further configured to: and when judging that any one of the request expiration timestamp and the operation execution time is earlier than T2, returning an error response that the downlink data request message cannot be sent to the target UE to the AS through the first communication interface 74.
As an alternative implementation, the processor 72 is further configured to: when it is determined that any one of the request expiration timestamp and the operation execution time is earlier than T2, instructing the first communication interface 74 to send information of a preset reachable time period in the preset reachable time list to the AS through a core network, where the information of the preset reachable time period is used to instruct that the request expiration timestamp and the operation execution time in the downlink data request message are modified to be after the unreachable time that has not yet arrived.
As an optional implementation manner, the second communication interface 75 is further configured to: receiving a registration request sent by the target UE from a core network, wherein the registration request comprises information of a preset reachable time period of the target UE;
the processor 72 is further configured to create the preset reachable time list for the target UE, and store the preset reachable time list in the memory, where the preset reachable time list includes the preset reachable time period in the registration request.
As an alternative implementation, the processor 72 is further configured to: before determining that the source parameter in the preset reachable time list is Network, subscribing the Idle state of the target UE to a Network server through the second communication interface 75;
receiving, through the second communication interface 75, an Idle status report of the target UE returned by the receiving network server, where the Idle status report includes an identifier of the target UE and a time when the target UE enters an Idle status;
taking the moment when the target UE enters the Idle state as the starting moment of the preset reachable time period;
and setting the source parameter of the preset reachable time list as Network.
As an optional implementation manner, the Idle status report further includes an Idle status duration and a location update period of the target UE; or, the Idle state timer in the network server is set by the M2M management platform, and the M2M management platform stores the Idle state duration and the location update period;
the processor 72 is further configured to: after the time when the target UE enters the Idle state is taken as the starting time of the preset reachable time period, the time when the target UE enters the Idle state plus the time of the Idle state duration is taken as the ending time of the preset reachable time period in the preset reachable time list; and
and taking the position updating period as a time interval between adjacent preset reachable time periods in the preset reachable time list.
As an optional implementation manner, the second communication interface 75 is further configured to: after the processor 72 sets the source parameter to Network, information of a preset reachable time period in the preset reachable time list is sent to the target UE through a core Network.
As an optional implementation manner, the first communication interface 74 is further configured to: receiving a second downlink data request message sent by the AS, wherein the second downlink data request message comprises an identifier of a second target UE;
the processor 72 is further configured to: searching a second preset reachable time list of the second target UE, which is locally stored, according to the identifier of the second target UE;
determining the source parameter in the second preset reachable time list as a Device;
judging whether the current time T3 is within a preset reachable time period in the second preset reachable time list;
if yes, the second communication interface 75 is instructed to send the second downlink data request message to the second target UE through the second communication interface 75.
As an alternative implementation, the processor 72 is further configured to: determining a time T4 of last receiving of the message of the second target UE when it is judged that T3 is not located within the preset reachable time period of the second preset reachable time list;
judging whether the difference value between the T3 and the T4 is larger than the Idle state duration of the second target UE;
and if not, indicating the second communication interface to send the second downlink data request message to the second target UE through the second communication interface 75 of the core network.
The embodiment of the M2M management platform 70 refers to the embodiments of the corresponding methods in fig. 5 to 8, and will not be described in detail herein.
Fig. 12 is a schematic structural diagram of an M2M management platform 80 according to another embodiment of the present invention, in which the M2M management platform 80 includes a bus 81, and a second processor 82, a second memory 83, and a third communication interface 84 respectively connected to the bus 81.
The third communication interface 84 is configured to: and receiving a registration request of the target UE through a core network, wherein the registration request comprises information of a preset reachable time period of the target UE.
The second processor 82 is configured to: creating a preset reachable time list for the target UE in the second memory 83, the preset reachable time list including the preset reachable time period in the registration request;
subscribing to the Idle state of the target UE from the network server through the third communication interface 84;
receiving an Idle status report of the target UE from a core network through the third communication interface 84, where the Idle status report includes an identifier of the target UE and a time when the target UE enters an Idle status;
taking the moment when the target UE enters the Idle state as the starting moment of the preset reachable time period; and are
Setting the source parameter of the preset reachable time list as Network;
and instructing the third communication interface 84 to send information of the preset reachable time period in the preset reachable time list to the target UE through the core network.
The third communication interface is further configured to send, in response to the instruction of the second processor 82, information of a preset reachable time period in the preset reachable time list to the target UE through a core network.
The embodiment of the M2M management platform 70 refers to the embodiments of the corresponding methods in fig. 5 to 8, and will not be described in detail herein.
The processor 72 and the second processor 82 may be a single processing element or may be a combination of a plurality of processing elements. For example, the processor 72 and the second processor 82 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement embodiments of the present invention, such as: one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs).
The memory 73 and the second memory 83 may be a single memory element or a combination of a plurality of memory elements, and are used for storing executable program codes or parameters, data, and the like required by the M2M management platform to operate. The Memory 73 and the second Memory 83 may include a Random-Access Memory (RAM) or a Non-Volatile Memory (NVM), such as a magnetic disk Memory, a Flash Memory (Flash Memory), and the like.
As shown in fig. 13, the network server in fig. 7 may be implemented by the computer device (or system) in fig. 13.
Fig. 13 is a schematic diagram of a computer device according to an embodiment of the present invention. The computer device 900 includes at least one processor 901, a communication bus 902, memory 903, and at least one communication interface 904.
Processor 901 can be a general processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present invention.
Communication bus 902 may include a path that transfers information between the aforementioned components.
Communication interface 904 may be implemented using any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc.
The memory 903 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.
The memory 903 is used for storing application program codes for implementing the present invention, and the processor 901 controls the execution. The processor 201 is configured to execute the application code stored in the memory 203, thereby implementing the functions of the network server described in fig. 7.
In particular implementations, processor 901 may include one or more CPUs such as CPU0 and CPU1 in fig. 13 as one embodiment.
In particular implementations, computer device 900 may include multiple processors, such as processor 901 and processor 908 in FIG. 13, for example, as an embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).
In particular implementations, computer device 900 may also include an output device 905 and an input device 906, as one embodiment. An output device 905, which is in communication with the processor 901, may display information in a variety of ways. For example, the output device 905 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device 906, which is in communication with the processor 901, may accept input from a user in a variety of ways. For example, the input device 906 may be a mouse, keyboard, touch screen device, or sensing device, among others.
The computer device 900 described above may be a general purpose computer device or a special purpose computer device. In a specific implementation, the computer device 900 may be a desktop computer, a laptop computer, a web server, a Personal Digital Assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or a device with a similar structure as in fig. 13. Embodiments of the present invention are not limited by the type of computer device 900.
The embodiment of the present invention may also perform functional module division on the network server shown in fig. 7, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one module. The integrated module can be realized in a form of hardware, and can also be realized in a form of a software functional module. It should be noted that, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
For example, fig. 14 shows a schematic diagram of a possible structure of a network server related to fig. 7, and the apparatus 1000 includes a receiving module 1001 and a sending module 1002. The receiving module 1001 is configured to receive a subscription request sent by an M2M management platform, where the subscription request is a request for subscribing to an Idle state of a UE; a sending module 1002, configured to send an idle status report of the UE to the M2M management platform according to the subscription request received by the receiving module when the status of the UE is switched to the idle status, where the report includes an identifier of the UE and a time when the UE enters the idle status. As shown in fig. 4, the core network may include a plurality of network servers, where the network server responsible for receiving the Idle state subscription request of the UE and the network server responsible for detecting the UE state may not be the same entity, in this case, the sending module 1002 is further configured to forward the Idle state subscription request of the UE to the network server (e.g. MME) responsible for detecting the UE state; the receiving module is further configured to receive an idle status report of the UE sent by a network server responsible for detecting a UE status, and send the status report to the M2M management platform, where the status report includes an identifier of the UE and a time when the UE enters the idle status. The above functional modules may be implemented in the form of hardware, or in the form of software functional modules. In a simple embodiment, one skilled in the art will recognize that the web server 1000 may take the form shown in FIG. 13. For example, the receiving module 1001 in fig. 14 may be implemented by receiving a request through the communication interface 904 in fig. 13 and calling a code in the memory 903 through the processor 901, which is not limited in this respect in the embodiment of the present invention.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the embodiments of the present invention and their equivalents, the embodiments of the present invention are also intended to encompass such modifications and variations.

Claims (35)

1. A method for sending a message to a user equipment, UE, comprising:
a machine and machine M2M management platform receives a downlink data request message sent by an application server AS, wherein the downlink data request message comprises an identifier of a target UE;
the M2M management platform searches a locally stored preset reachable time list of the target UE according to the identifier of the target UE, wherein the preset reachable time list stores information of a preset reachable time period of the target UE;
the M2M management platform determines that a source parameter in the preset reachable time list is a Network, and the source parameter is a Network indicating that the starting time of the preset reachable time period in the preset reachable time list is the same as the starting time of an Idle state timer set for the target UE in a Network server;
the M2M management platform judges whether the current time T1 is within the preset reachable time period;
if yes, the M2M management platform sends the downlink data request message to the target UE.
2. The method of claim 1, wherein the downstream data request message further comprises a request expiration timestamp and an operation execution time; after the M2M management platform determines whether T1 is within the preset reachable time period, the method further includes:
if the T1 is not located within the preset reachable time period, the M2M management platform determines a starting time T2 of a next preset reachable time period after T1 according to the preset reachable time list;
the M2M management platform determining whether the request expiration timestamp and the operation execution time are both later than T2;
if so, the M2M management platform sends the downlink data request message to the target UE within a next preset reachable time period after the T1 and before the expiration timestamp and the operation execution time.
3. The method as claimed in claim 2, wherein the M2M management platform determining whether the request expiration timestamp and the operation execution time are both later than T2, further comprising:
if any one of the request expiration timestamp and the operation execution time is earlier than T2, the M2M management platform returns an error response to the AS, wherein the error response indicates that the downlink data request message cannot be sent to the target UE.
4. The method of claim 3, wherein if any of the request expiration timestamp and the operation execution time is earlier than T2, the M2M management platform returns an error response to the AS that the downlink data request message cannot be sent to the target UE, comprising:
if the request expiration timestamp is earlier than T2, the M2M management platform returns to the AS an error response that the downlink data request message cannot be sent to the target UE before the request expiration timestamp; or
If the request expiration timestamp is later than T2 and the operation execution time is earlier than T2, the M2M management platform returns an error to the AS that the downlink data request message cannot be sent to the target UE before the operation execution time.
5. The method of any of claims 2 to 4, further comprising:
if any one of the request expiration timestamp and the operation execution time is earlier than T2, the M2M management platform sends information of a preset reachable time period in the preset reachable time list to the AS, where the information of the preset reachable time period is used to indicate that the request expiration timestamp and the operation execution time in the downlink data request message are modified to be after the unreachable time that has not yet arrived.
6. The method according to any one of claims 1 to 4, wherein before the M2M management platform searching the locally stored preset reachable time list of the target UE according to the identity of the target UE, the method further comprises:
the M2M management platform receives a registration request of the target UE, wherein the registration request comprises information of a preset reachable time period of the target UE;
the M2M management platform locally creates the preset reachable time list for the target UE, where the preset reachable time list includes the preset reachable time period in the registration request.
7. The method according to any one of claims 1 to 4, wherein before the M2M management platform determines that the source parameter in the preset reachable time list is Network, the method further comprises:
the M2M management platform subscribes the Idle state of the target UE to a network server;
the M2M management platform receives an Idle status report of the target UE returned by a network server, wherein the Idle status report comprises the identification of the target UE and the time when the target UE enters the Idle status;
the M2M management platform takes the time when the target UE enters the Idle state as the starting time of the preset reachable time period; and are
And setting the source parameter of the preset reachable time list as Network.
8. The method of claim 7, wherein the Idle status report further comprises an Idle status duration and a location update period of the target UE; or, the Idle state timer in the network server is set by the M2M management platform, and the M2M management platform stores the Idle state duration and the location update period;
after the M2M management platform takes the time when the target UE enters the Idle state as the starting time of the preset reachable time period, the method further includes:
the M2M management platform takes the time when the target UE enters the Idle state plus the time of the Idle state duration as the end time of the preset reachable time period in the preset reachable time list; and
and taking the position updating period as a time interval between adjacent preset reachable time periods in the preset reachable time list.
9. The method of claim 7, wherein after the M2M management platform sets the sourcing parameter to Network, further comprising:
and the M2M management platform sends information of a preset reachable time period in the preset reachable time list to the target UE.
10. The method of any of claims 1 to 4, further comprising:
the M2M management platform receives a second downlink data request message sent by the AS, where the second downlink data request message includes an identifier of a second target UE;
the M2M management platform searches a second preset reachable time list of the second target UE, which is locally stored, according to the identifier of the second target UE;
the M2M management platform determines the source parameter in the second preset reachable time list as a Device;
the M2M management platform determines whether the current time T3 is within a preset reachable time period in the second preset reachable time list;
if yes, the M2M management platform sends the second downlink data request message to the second target UE.
11. The method of claim 10, wherein after the M2M management platform determines whether T3 is within the preset reachable time period of the second preset reachable time list, further comprising:
if T3 is not located within the preset reachable time period of the second preset reachable time list, the M2M management platform determines a time T4 at which the message of the second target UE was received last time;
the M2M management platform determining whether the difference between T3 and T4 is greater than the Idle state duration of the second target UE;
if not, the M2M management platform sends the second downlink data request message to the second target UE.
12. The method of claim 11, further comprising, after the M2M management platform determines whether the difference between T3 and T4 is greater than the Idle state duration of the second target UE;
if the difference between T3 and T4 is greater than the Idle state duration of the second target UE, the M2M management platform returns an error response to the AS that the second target UE is currently in an unreachable state.
13. A method of synchronization, comprising:
the M2M management platform subscribes the Idle state of the target UE to the network server;
the M2M management platform receives a registration request of the target UE, wherein the registration request comprises information of a preset reachable time period of the target UE;
the M2M management platform locally creates a preset reachable time list for the target UE, wherein the preset reachable time list comprises the preset reachable time period in the registration request;
the M2M management platform receives an Idle status report of the target UE returned by a network server, wherein the Idle status report comprises the identification of the target UE and the time when the target UE enters the Idle status;
the M2M management platform takes the time when the target UE enters the Idle state as the starting time of the preset reachable time period; and are
Setting a source parameter of the preset reachable time list as Network;
and the M2M management platform sends information of a preset reachable time period in the preset reachable time list to the target UE.
14. An apparatus for sending a message to a UE, comprising:
a first receiving module, configured to receive a downlink data request message sent by an AS, where the downlink data request message includes an identifier of a target UE;
a determination module to: searching a preset reachable time list of the target UE, which is locally stored, according to the identifier of the target UE, wherein the preset reachable time list stores information of a preset reachable time period of the target UE; determining that a source parameter in the preset reachable time list is Network, wherein the source parameter is Network indicating that the starting time of the preset reachable time period in the preset reachable time list is the same as the starting time of an Idle state timer set for the target UE in a Network server;
the judging module is used for judging whether the current time T1 is within the preset reachable time period;
a sending module, configured to send the downlink data request message to the target UE when the determining module determines that T1 is located within the preset reachable time period.
15. The apparatus of claim 14, wherein the downstream data request message further comprises a request expiration timestamp and an operation execution time;
the judging module is further configured to: when the T1 is judged not to be within the preset reachable time period, determining the starting time T2 of the next preset reachable time period after T1 according to the preset reachable time list; judging whether the request expiration timestamp and the operation execution time are both later than T2;
the sending module is further configured to: and when the judging module judges that the request expiration timestamp and the operation execution time are both later than T2, sending the downlink data request message to the target UE within the next preset reachable time period after T1 and before the expiration timestamp and the operation execution time.
16. The apparatus of claim 15, wherein the sending module is further configured to: and when the judging module judges that any one of the request expiration timestamp and the operation execution time is earlier than T2, returning an error response that the downlink data request message cannot be sent to the target UE to the AS.
17. The apparatus of claim 15 or 16, wherein the sending module is further configured to: and when the judging module judges that any one of the request expiration timestamp and the operation execution time is earlier than T2, sending information of a preset reachable time period in the preset reachable time list to the AS, wherein the information of the preset reachable time period is used for indicating that the request expiration timestamp and the operation execution time in the downlink data request message are modified into the unreachable time which does not arrive yet.
18. The apparatus of any one of claims 14 to 16, further comprising:
a second receiving module, configured to receive a registration request of the target UE, where the registration request includes information of a preset reachable time period of the target UE;
a creating module, configured to create the preset reachable time list locally for the target UE, where the preset reachable time list includes the preset reachable time period in the registration request.
19. The apparatus of any one of claims 14 to 16, further comprising:
a subscription module, configured to subscribe to a Network server for an Idle state of the target UE before the determining module determines that the source parameter in the preset reachable time list is Network;
a third receiving module, configured to receive an Idle status report of the target UE, where the Idle status report includes an identifier of the target UE and a time when the target UE enters an Idle status;
an adjusting module, configured to use a time when the target UE enters an Idle state as a starting time of the preset reachable time period; and setting the source parameter of the preset reachable time list as Network.
20. The apparatus of claim 19, wherein the Idle status report further comprises an Idle status duration and a location update period of the target UE; or, the Idle state timer in the network server is set by an M2M management platform, and the M2M management platform stores the Idle state duration and the location update period;
the adjusting module is further configured to:
taking the time when the target UE enters the Idle state plus the time of the Idle state duration as the ending time of the preset reachable time period in the preset reachable time list; and
and taking the position updating period as a time interval between adjacent preset reachable time periods in the preset reachable time list.
21. The apparatus of claim 19, wherein the sending module is further configured to: and sending the information of the preset reachable time period in the preset reachable time list adjusted by the adjusting module to the target UE.
22. The apparatus of any one of claims 14 to 16, wherein the first receiving module is further configured to: receiving a second downlink data request message sent by the AS, wherein the second downlink data request message comprises an identifier of a second target UE;
the determination module is further to: searching a second preset reachable time list of the second target UE, which is locally stored, according to the identifier of the second target UE; determining the source parameter in the second preset reachable time list as a Device;
the judging module is further configured to: judging whether the current time T3 is within a preset reachable time period in the second preset reachable time list;
the sending module is further configured to: and when the determining module determines that T3 is located within the preset reachable time period in the second preset reachable time list, sending the second downlink data request message to the second target UE.
23. The apparatus of claim 22, wherein the determining module is further configured to: determining a time T4 of last receiving of the message of the second target UE when it is judged that T3 is not located within the preset reachable time period of the second preset reachable time list; judging whether the difference value between the T3 and the T4 is larger than the Idle state duration of the second target UE;
the sending module is further configured to: and when the judging module judges that the difference value between the T3 and the T4 is not greater than the Idle state duration of the second target UE, sending the second downlink data request message to the second target UE.
24. An apparatus for updating a preset reachable time list, comprising:
the second subscription module is used for subscribing the Idle state of the target UE to the network server;
a fourth receiving module, configured to receive a registration request of the target UE, where the registration request includes information of a preset reachable time period of the target UE;
a second creating module, configured to create a preset reachable time list locally for the target UE, where the preset reachable time list includes the preset reachable time period in the registration request;
a fifth receiving module, configured to receive an Idle status report of the target UE, where the Idle status report includes an identifier of the target UE and a time when the target UE enters an Idle status, where the Idle status report is returned by a network server;
a second adjustment module to: taking the moment when the target UE enters the Idle state as the starting moment of the preset reachable time period; setting the source parameter of the preset reachable time list as Network;
and the second sending module is used for sending the information of the preset reachable time period in the preset reachable time list to the target UE.
25. An M2M management platform, comprising a processor, a memory connected with the processor, a first communication interface and a second communication interface;
the first communication interface is to: receiving a downlink data request message sent by an AS, wherein the downlink data request message comprises an identifier of a target UE;
the second communication interface is to: communicating with a core network;
the memory is to: storing a preset reachable time list of the target UE, wherein the preset reachable time list stores information of a preset reachable time period of the target UE;
the processor is configured to:
searching a preset reachable time list of the target UE, which is locally stored, according to the identifier of the target UE, wherein the preset reachable time list stores information of a preset reachable time period of the target UE;
determining that a source parameter in the preset reachable time list is Network, wherein the source parameter is that Network indicates that the starting time of the preset reachable time period in the preset reachable time list is the same as the starting time of an Idle state timer set for the target UE in a Network server of a core Network;
judging whether the current time T1 is within the preset reachable time period;
and if so, indicating the second communication interface to send the downlink data request message to the target UE through a core network.
26. The platform of claim 25, wherein the downstream data request message further comprises a request expiration timestamp and an operation execution time;
the processor is further configured to: when the T1 is judged not to be within the preset reachable time period, determining the starting time T2 of the next preset reachable time period after T1 according to the preset reachable time list; judging whether the request expiration timestamp and the operation execution time are both later than T2; if yes, instructing the second communication interface to send the downlink data request message to the target UE through a core network within a next preset reachable time period after the T1 and before the expiration timestamp and the operation execution time.
27. The platform of claim 26, wherein the processor is further configured to: and when judging that any one of the request expiration timestamp and the operation execution time is earlier than T2, returning an error response that the downlink data request message cannot be sent to the target UE to the AS through the first communication interface.
28. The platform of claim 26 or 27, wherein the processor is further configured to: and when any one of the request expiration timestamp and the operation execution time is judged to be earlier than T2, sending information of a preset reachable time period in the preset reachable time list to the AS through the first communication interface, wherein the information of the preset reachable time period is used for indicating that the request expiration timestamp and the operation execution time in the downlink data request message are modified into the unreachable time which does not come yet.
29. The platform of any of claims 25 to 27, wherein the second communication interface is further configured to: receiving a registration request sent by the target UE from a core network, wherein the registration request comprises information of a preset reachable time period of the target UE;
the processor is further configured to create the preset reachable time list for the target UE, and store the preset reachable time list in the memory, where the preset reachable time list includes the preset reachable time period in the registration request.
30. The platform of any one of claims 25 to 27, wherein the processor is further configured to:
before determining that the source parameter in the preset reachable time list is Network, subscribing the Idle state of the target UE to a Network server through the second communication interface;
receiving, by the second communication interface, an Idle status report of the target UE, which is returned by the receiving network server, where the Idle status report includes an identifier of the target UE and a time when the target UE enters an Idle status;
taking the moment when the target UE enters the Idle state as the starting moment of the preset reachable time period;
and setting the source parameter of the preset reachable time list as Network.
31. The platform of claim 30, wherein the Idle status report further includes an Idle status duration and a location update period of the target UE; or, the Idle state timer in the network server is set by the M2M management platform, and the M2M management platform stores the Idle state duration and the location update period;
the processor is further configured to: after the time when the target UE enters the Idle state is taken as the starting time of the preset reachable time period, the time when the target UE enters the Idle state plus the time of the Idle state duration is taken as the ending time of the preset reachable time period in the preset reachable time list; and taking the position updating period as a time interval between adjacent preset reachable time periods in the preset reachable time list.
32. The platform of claim 30, wherein the second communication interface is further configured to: and after the processor sets the source parameter as Network, sending information of a preset reachable time period in the preset reachable time list to the target UE through a core Network.
33. The platform of any one of claims 25 to 27, wherein the first communication interface is further configured to: receiving a second downlink data request message sent by the AS, wherein the second downlink data request message comprises an identifier of a second target UE;
the processor is further configured to: searching a second preset reachable time list of the second target UE, which is locally stored, according to the identifier of the second target UE;
determining the source parameter in the second preset reachable time list as a Device;
judging whether the current time T3 is within a preset reachable time period in the second preset reachable time list;
and if so, indicating the second communication interface to send the second downlink data request message to the second target UE through a core network.
34. The platform of claim 33, wherein the processor is further configured to: determining a time T4 of last receiving of the message of the second target UE when it is judged that T3 is not located within the preset reachable time period of the second preset reachable time list;
judging whether the difference value between the T3 and the T4 is larger than the Idle state duration of the second target UE;
and if not, indicating the second communication interface to send the second downlink data request message to the second target UE through a core network.
35. An M2M management platform, comprising a second processor, a second memory and a third communication interface, wherein the second memory and the third communication interface are respectively connected with the second processor;
the third communication interface is configured to receive, through core network communication, a registration request sent by a target UE, where the registration request includes information of a preset reachable time period of the target UE;
the second processor to:
creating a preset reachable time list for the target UE in the second memory, the preset reachable time list including the preset reachable time period in the registration request;
subscribing the Idle state of the target UE to a network server of a core network through the third communication interface;
receiving an Idle state report of the target UE, which is returned by a network server through the third communication interface, wherein the Idle state report comprises an identifier of the target UE and a time when the target UE enters an Idle state;
taking the moment when the target UE enters the Idle state as the starting moment of the preset reachable time period; and are
Setting a source parameter of the preset reachable time list as Network;
and instructing the third communication interface to send information of a preset reachable time period in the preset reachable time list to the target UE through a core network.
CN201710279153.8A 2017-01-13 2017-04-25 Method and device for sending message to UE (user Equipment) and M2M management platform Active CN108307377B (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2017100258568 2017-01-13
CN201710025856 2017-01-13

Publications (2)

Publication Number Publication Date
CN108307377A CN108307377A (en) 2018-07-20
CN108307377B true CN108307377B (en) 2021-05-18

Family

ID=62872306

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710279153.8A Active CN108307377B (en) 2017-01-13 2017-04-25 Method and device for sending message to UE (user Equipment) and M2M management platform

Country Status (1)

Country Link
CN (1) CN108307377B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111277992B (en) * 2018-12-05 2022-09-16 中国电信股份有限公司 Method and system for determining terminal network state
CN111866817B (en) * 2020-06-23 2024-04-05 广东以诺通讯有限公司 D2D terminal mode communication selection method under 5G hybrid networking
CN113905409A (en) * 2021-10-09 2022-01-07 天翼物联科技有限公司 Terminal accessibility detection method, device, network equipment and storage medium

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
PT3419206T (en) * 2007-02-14 2021-08-19 Guangdong Oppo Mobile Telecommunications Corp Ltd Method and system for recovering from drx timing de-synchronization in lte-active
CN101459871A (en) * 2007-12-14 2009-06-17 华为技术有限公司 Method, system and apparatus for paging periodic synchronization of access terminal and access network
CN104349363B (en) * 2013-08-09 2017-11-24 上海贝尔股份有限公司 A kind of method, equipment and system for being used to determine connection status auxiliary parameter
CN107431918B (en) * 2015-03-25 2020-09-04 Lg 电子株式会社 Method for monitoring UE accessibility in wireless communication system and device thereof
US10149343B2 (en) * 2015-05-11 2018-12-04 Apple Inc. Use of baseband triggers to coalesce application data activity

Also Published As

Publication number Publication date
CN108307377A (en) 2018-07-20

Similar Documents

Publication Publication Date Title
CN108617034B (en) Connection state control method, equipment and system for terminal
EP4016881A1 (en) Method for achieving time synchronization and related device
US20220174631A1 (en) Time synchronization method and apparatus, computer-readable medium, and electronic device
KR101407872B1 (en) Method for realizing user-reachable and multi-mode terminal
US8983463B2 (en) Mobile communication system, location registration method, relay node and control method thereof, and storage medium of control program
JP7111164B2 (en) RRC inactive state optimization
JP6665946B2 (en) Base station, core network device and communication device
JP2019506791A (en) RRC connection resumption procedure
CN108307377B (en) Method and device for sending message to UE (user Equipment) and M2M management platform
CN101179561B (en) Method for user facility to attach to network and system thereof
CN106416391B (en) Paging method, user equipment, base station and core network equipment
CN109495942B (en) Data transmission method, device and system based on user equipment position
EP3836639B1 (en) Synchronization cycle determination methods and devices
US20220070963A1 (en) Core network node and method
EP3794901B1 (en) Apparatus and methods for network scheduled ue transition to cm-connected/rrc connected mode in 5gs
US10880830B2 (en) Systems and methods for selective preemption of UE power saving mode (PSM)
WO2018192527A1 (en) Time synchronization method and device
CN105554870A (en) Uplink synchronization method and mobile terminal
TW201906431A (en) Location tracking method and base station and user equipment using same
RU2698425C1 (en) Method and device for transmitting downlink data notification messages
KR100778339B1 (en) Location processing method for 3gpp mobile communication system and paging method using the same
US20230084453A1 (en) Registered ue count in slice service area
CN113079553A (en) Information transmission method and device
JP5796633B2 (en) PROCESSING DEVICE, COMMUNICATION SYSTEM, COMMUNICATION TERMINAL, TERMINAL DEVICE CONTROL METHOD, AND PROGRAM
CN104159300A (en) Paging method and equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20220217

Address after: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province

Patentee after: Huawei Cloud Computing Technology Co.,Ltd.

Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd.

TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20221209

Address after: 518129 Huawei Headquarters Office Building 101, Wankecheng Community, Bantian Street, Longgang District, Shenzhen, Guangdong

Patentee after: Shenzhen Huawei Cloud Computing Technology Co.,Ltd.

Address before: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province

Patentee before: Huawei Cloud Computing Technology Co.,Ltd.