CN107155222B - Context management method and device based on keep-alive - Google Patents
Context management method and device based on keep-alive Download PDFInfo
- Publication number
- CN107155222B CN107155222B CN201610121601.7A CN201610121601A CN107155222B CN 107155222 B CN107155222 B CN 107155222B CN 201610121601 A CN201610121601 A CN 201610121601A CN 107155222 B CN107155222 B CN 107155222B
- Authority
- CN
- China
- Prior art keywords
- alive
- keep
- context
- network side
- behavior
- 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
Links
- 238000007726 management method Methods 0.000 title claims abstract description 46
- 238000000034 method Methods 0.000 claims description 39
- 230000008569 process Effects 0.000 claims description 12
- 238000012545 processing Methods 0.000 claims description 12
- 238000012546 transfer Methods 0.000 claims description 11
- 230000009467 reduction Effects 0.000 claims description 5
- 230000006399 behavior Effects 0.000 abstract description 97
- 238000012423 maintenance Methods 0.000 abstract description 7
- 238000004891 communication Methods 0.000 description 18
- 230000006870 function Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 6
- 238000013507 mapping Methods 0.000 description 6
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000000605 extraction Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a context management method based on keep-alive, which comprises the following steps: acquiring keep-alive behaviors of User Equipment (UE); context information of the UE is managed based on keep-alive behavior of the UE. The invention also discloses context management equipment based on keep-alive. By adopting the technical scheme of the invention, context maintenance can be provided for the UE as required, and the full use of network resources is ensured.
Description
Technical Field
The present invention relates to the field of wireless communication technologies, and in particular, to a keep-alive context management method and device.
Background
With the continuous development of communication technology and the continuous emergence of new services, the traditional mobile users have not satisfied simple voice, short message and low-speed data services, and the rapid development of communication networks is promoted by the change of user requirements.
In current communication networks, such as the fourth Generation mobile communication technology (4G) network, both the core network and the access network can keep alive the context of a User Equipment (UE). However, the current UE context keep-alive method either occupies network resources for a long time or requires frequent interaction between the UE and the network side to maintain the context.
Disclosure of Invention
In view of this, the present invention is expected to provide a context management method and device based on keep-alive, which can provide context maintenance for the UE as required and simultaneously ensure full use of network resources.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a context management method based on keep-alive, which comprises the following steps:
acquiring the keep-alive behavior of the UE;
context information of the UE is managed based on keep-alive behavior of the UE.
In the foregoing solution, preferably, the acquiring the keep-alive behavior of the UE includes:
the network side determines whether the UE meets the starting condition for executing the keep-alive operation according to a preset rule;
and when the UE is determined to meet the starting condition for executing the keep-alive operation, the keep-alive behavior of the UE is obtained.
In the foregoing solution, preferably, the determining, by the network side according to a preset rule, whether the UE needs to perform a keep-alive operation includes:
determining whether the UE needs to execute keep-alive operation or not based on preset, estimated or pre-negotiated user keep-alive behavior information; or
The network side detects the current network resource, and when the network resource meets the preset condition, the UE is determined to need to execute the keep-alive operation.
In the foregoing solution, preferably, the preset, pre-estimated, or pre-negotiated user keep-alive behavior information includes:
user keep-alive behavior information notified by the UE; or
The network side and the UE negotiate to determine user keep-alive behavior information; or
And the user keep-alive behavior information is judged by the network side.
In the above scheme, preferably, the user keep-alive behavior information is a context timer configured for the UE by the network side;
wherein the context timer is a keep alive timer, or,
and in the timing time of each context timer, if no data occurs, the UE needs to send a user keep-alive behavior message to the network side.
In the foregoing solution, preferably, the method further includes:
the network side pre-configures context keep-alive resources for the UE based on the context timer so that the UE performs keep-alive operation by using the context keep-alive resources.
In the foregoing solution, preferably, the managing context information of the UE based on the keep-alive behavior of the UE includes:
in the process that the UE executes the keep-alive operation according to the keep-alive resources configured for the UE by the network side, the network side completes the storage, or the update, or the transfer, or the release or the priority reduction of the context information.
In the foregoing solution, preferably, the releasing or reducing the priority of the context information by the network side includes:
when a new keep-alive clock period of the context timer arrives, if the network side does not receive the keep-alive message fed back by the UE side within a certain time, the context information is judged to be overdue or unimportant, and the stored context information is released or priority reduction processing is carried out;
wherein the certain time includes: keep alive clock period + pre-estimate air interface delay.
In the foregoing solution, preferably, the transferring context information by the network side includes:
when the keep-alive behavior of the UE is different from the context storage administration area where the UE last transmits data, the context of the UE is judged to be transferred, and the stored context information is transferred and/or updated.
In the foregoing solution, preferably, the updating of the context information by the network side includes:
and when the context of the UE is detected to be updated, or the context is transferred, or a keep-alive message carrying context update and sent by the UE is received, updating the stored context information.
The invention also provides a context management method based on keep-alive, which is applied to a terminal side and comprises the following steps:
and the UE executes the user keep-alive behavior based on the user keep-alive behavior information.
In the foregoing scheme, preferably, the user keep-alive behavior information is:
user keep-alive behavior information determined by the UE;
the UE and the network side determine the user keep-alive behavior information through negotiation: or
And the user keep-alive behavior information is judged by the network side.
In the foregoing solution, preferably, the user keep-alive behavior information determined by the UE includes:
and in the timing time of each context timer, sending a user keep-alive behavior message to the network side when a preset condition is met.
In the foregoing scheme, preferably, the preset condition includes: no data occurs.
In the foregoing solution, preferably, the method further includes:
and the UE performs keep-alive operation by utilizing the keep-alive resources configured for the UE by the network side.
The invention also provides context management equipment based on keep-alive, which comprises:
an obtaining unit, configured to obtain a keep-alive behavior of the UE;
and the management unit is used for managing the context information of the UE based on the keep-alive behavior of the UE.
In the foregoing solution, preferably, the obtaining unit is further configured to:
determining whether the UE meets a starting condition for executing the keep-alive operation according to a preset rule;
when the UE is determined to meet the starting condition for executing the keep-alive operation, the keep-alive behavior of the UE is obtained;
the method for determining whether the UE meets the starting condition of executing the keep-alive operation according to the preset rule comprises the following steps:
determining whether the UE needs to execute keep-alive operation or not based on preset, estimated or pre-negotiated user keep-alive behavior information; or
The network side detects the current network resource, and when the network resource meets the preset condition, the UE is determined to need to execute the keep-alive operation.
In the foregoing solution, preferably, the preset, pre-estimated, or pre-negotiated user keep-alive behavior information includes:
user keep-alive behavior information notified by the UE; or
The network side and the UE negotiate to determine user keep-alive behavior information; or
And the network side judges the user keep-alive behavior information.
In the above scheme, preferably, the user keep-alive behavior information is a context timer configured for the UE by the network side;
wherein the context timer is a keep alive timer, or,
the context timer is a user keep-alive behavior message sent by the UE to the network side under the condition that no data occurs in the timing time of each context timer.
In the foregoing solution, preferably, the apparatus includes:
and the configuration unit is used for pre-configuring context keep-alive resources for the UE based on the context timer so that the UE performs keep-alive operation by utilizing the context keep-alive resources.
In the foregoing solution, preferably, the management unit is further configured to:
and in the process that the UE executes the keep-alive operation according to the keep-alive resources configured for the UE by the network side, storing, updating, transferring, releasing or lowering the priority of the context information.
In the foregoing solution, preferably, the management unit includes:
a release subunit, configured to, when a new keep-alive clock cycle of the context timer arrives, if the network side does not receive a keep-alive message fed back by the UE side within a certain time, determine that the context information is expired or is not important, and release or lower priority processing the stored context information;
wherein the certain time includes: keep alive clock period + pre-estimate air interface delay.
In the foregoing solution, preferably, the management unit further includes:
and the transfer subunit is used for judging that the context of the UE is transferred and transferring the stored context information when the keep-alive behavior of the UE is different from the context storage administration area where the UE last transmits data.
In the foregoing solution, preferably, the management unit further includes:
and the updating subunit is configured to update the stored context information when detecting that the context of the UE is updated, or transferring the context, or receiving a keep-alive message carrying context update sent by the UE.
The invention also provides context management equipment based on keep-alive, which comprises:
the determining unit is used for acquiring the keep-alive behavior information of the user;
the processing unit is used for executing the user keep-alive behavior based on the user keep-alive behavior information;
wherein, the user keep-alive behavior information is as follows:
user keep-alive behavior information determined by the UE;
the UE and the network side determine the user keep-alive behavior information through negotiation:
wherein, the user keep-alive behavior information determined by the UE is: when the preset conditions are met within the timing time of each context timer, sending a user keep-alive behavior message to a network side; wherein the preset conditions include: no data occurs.
In the foregoing solution, preferably, the apparatus further includes:
and the keep-alive unit is used for carrying out keep-alive operation by utilizing the keep-alive resources configured for the keep-alive unit by the network side.
According to the context management method and device based on keep-alive, provided by the invention, the network side acquires the keep-alive behavior of the UE; managing context information of the UE based on keep-alive behavior of the UE; therefore, the context information of the UE can be better managed based on the keep-alive behavior of the UE, the context maintenance is provided for the UE according to the requirement, and meanwhile, the full use of network resources is guaranteed.
Drawings
FIG. 1 is a flowchart of an implementation of a context management method based on keep-alive provided by the present invention;
FIG. 2 is a flow diagram illustrating one implementation of keep-alive based contextual communication provided by the present invention;
FIG. 3 is a flow diagram illustrating another implementation of keep-alive based contextual communication provided by the present invention;
FIG. 4 is a schematic diagram of a keep-alive context management device according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of another keep-alive-based context management device provided by the present invention.
Detailed Description
So that the manner in which the features and aspects of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings.
Example one
FIG. 1 is a flowchart of an implementation of a context management method based on keep-alive provided by the present invention; as shown in fig. 1, the method mainly includes:
step 101: and acquiring the keep-alive behavior of the UE.
Preferably, the acquiring the keep-alive behavior of the UE includes:
the network side determines whether the UE meets the starting condition for executing the keep-alive operation according to a preset rule;
and when the UE is determined to meet the starting condition for executing the keep-alive operation, the keep-alive behavior of the UE is obtained.
Preferably, the determining, by the network side according to a preset rule, whether the UE needs to perform a keep-alive operation may include:
determining whether the UE needs to execute keep-alive operation or not based on preset, estimated or pre-negotiated user keep-alive behavior information; or
The network side detects the current network resource, and when the network resource meets the preset condition, the UE is determined to need to execute the keep-alive operation.
That is, the UE may actively send a keep-alive request to the network side according to the configuration; or, the network side sends the keep-alive command to the UE as needed, for example, if the network load is high, the keep-alive command is sent to the UE.
Preferably, the preset, pre-estimated or pre-negotiated user keep-alive behavior information includes:
user keep-alive behavior information notified by the UE; or
The network side and the UE negotiate to determine user keep-alive behavior information; or
And the network side judges the user keep-alive behavior information.
Preferably, the user keep-alive behavior information is a context timer configured for the UE by the network side;
wherein the context timer is a keep alive timer, or,
the context timer is that the UE sends a user keep-alive behavior message to the network side if no data occurs within the timing time of each context timer.
Step 103: context information of the UE is managed based on keep-alive behavior of the UE.
In the foregoing scheme, the method may further include:
step 100: the network side configures a context timer for the UE.
Preferably, the configuring, by the network side, a context timer for the UE may include:
a network side acquires the behavior characteristics and/or the service characteristics of UE;
and configuring a dedicated context timer for the UE according to the behavior characteristic and/or the service characteristic.
Here, the behavior feature may refer to mobility; the traffic characteristics may refer to a traffic period, a traffic interval, and the like.
Further, after acquiring the behavior feature and/or the service feature of the UE, the network side may further include:
classifying the UE according to the behavior characteristics and/or the service characteristics of the UE;
the network side configures a dedicated context timer for each type of UE.
Preferably, the configuring a dedicated context timer for the UE according to the behavior feature and/or the traffic feature includes:
when the traffic intervals of the UEs are centrally distributed at T0, setting the keep alive clock period of the context timer to nt 0; if the mobility of the UE is lower than a first threshold value, continuing to prolong the keep-alive clock period N T0, and setting the keep-alive clock period to M N T0, wherein M is more than 1, N is a positive integer, and T0 is the interval between two data packets;
or,
when the probability that the traffic interval of the UE is larger than T1 is lower than a second threshold, setting the keep-alive clock period of the context timer to be T1, wherein T1 is larger than T0, and T1 is the interval between two data packets; if the mobility of the UE is above a third threshold, continuing to shorten the keep-alive clock period T1, setting the keep-alive clock period to P T1, where P < 1.
That is, the keep-alive clock period is related to both the occurrence rule of the traffic and the mobility of the UE, and focuses more on the occurrence rule of the user traffic itself.
The reference index for determining the mobility may be a moving rate of the UE or a number of cells that the UE passes through in a unit time.
Of course, those skilled in the art should understand that the specific implementation manner of configuring the UE with the dedicated context timer according to the behavior feature and/or the traffic feature is not limited to the above-listed ones, and will not be described herein again.
Preferably, the method further comprises:
and the network side pre-configures context keep-alive resources for the UE based on the context timer so that the UE performs keep-alive operation by utilizing the context keep-alive resources within the timing duration of the context timer.
The network side pre-configures context keep-alive resources for the UE based on the context timer, which may include:
when the network side pre-configures the context keep-alive resource for the UE, the pre-configured context keep-alive resource can ensure that the UE and the network side at least keep the following communication within the timing period of each context timer:
traffic communication, communication of keep-alive information for maintaining context;
wherein the communication of keep-alive information to maintain context comprises: first keep alive request information initiated by a network side and a first keep alive response message initiated by a user side; second keep-alive request information initiated by the user side and second keep-alive response information initiated by the network side; keep-alive consultation information initiated by the network side and keep-alive consultation response messages initiated by the user side.
In the foregoing solution, preferably, the method further includes:
the network side sends a keep-alive command and keep-alive resource configuration information to the UE;
the UE executes keep-alive operation according to the keep-alive resources configured for the UE by the network side;
in the process of the UE performing the keep-alive operation, the network side completes the storage, or the update, or the transfer, or the release or the priority reduction of the context information.
Here, the network side can send keep-alive commands and keep-alive resource configuration information to one or a group of UEs.
Specifically, the context information of the UE with the keep-alive requirement is reserved or updated; releasing or reducing the storage priority of the context information of the UE without the keep-alive requirement; here, lowering the storage priority means: once the resources are in shortage (such as the storage of the context information is influenced), the resources occupied by the context information with low storage priority are preferentially released.
Specifically, the network side completing the release or reducing the priority of the context information may include:
when a new keep-alive clock period of the context timer arrives, if the network side does not receive the keep-alive message fed back by the UE side within a certain time, the context information is judged to be overdue or unimportant, and the stored context information is released or priority reduction processing is carried out;
wherein the certain time may be: keep alive clock period + pre-estimate air interface delay.
Specifically, the network side completes the transfer of context information, including:
when the keep-alive behavior of the UE is different from the context storage administration area where the UE last transmits data, the context of the UE is judged to be transferred, and the stored context information is transferred and/or updated.
Specifically, the network side completes the update of the context information, including:
and when the context of the UE is detected to be updated, or the context is transferred, or a keep-alive message carrying context update and sent by the UE is received, updating the stored context information.
Specifically, the network side completes the storage of the context information, and may include:
extracting the wireless information from the context information; wherein the wireless information comprises a context identifier;
performing resource pre-scheduling on keep-alive information transmission based on the context identification of the UE at the access side;
wherein, the pre-scheduling resources for keep-alive information transmission based on the context identifier of the UE at the access side comprises:
and performing resource mapping corresponding to the wireless information according to the wireless information, and reserving wireless resources on corresponding time resources based on a resource mapping result, so that the UE directly uses the corresponding wireless resources to perform keep-alive operation when a keep-alive clock of the context timer arrives.
Therefore, by pre-scheduling the keep-alive information, the resource overhead can be reduced.
Correspondingly, the invention also discloses a context management method based on keep-alive, which is applied to the UE side and comprises the following steps:
and the UE executes the user keep-alive behavior based on the user keep-alive behavior information.
In the foregoing scheme, preferably, the user keep-alive behavior information is:
user keep-alive behavior information determined by the UE;
the UE and the network side determine the user keep-alive behavior information through negotiation: or
And the user keep-alive behavior information is judged by the network side.
In the foregoing solution, preferably, the user keep-alive behavior information determined by the UE includes:
and in the timing time of each context timer, sending a user keep-alive behavior message to the network side when a preset condition is met.
Optionally, the preset conditions include: no data occurs.
In the foregoing solution, preferably, the method further includes:
and the UE performs keep-alive operation by utilizing the keep-alive resources configured for the UE by the network side.
The context management method based on keep-alive provided by the embodiment can provide context maintenance for the UE according to needs, and meanwhile, the full use of network resources is guaranteed.
Example two
Fig. 2 is a schematic diagram of an implementation process of keep-alive context communication provided by the present invention, and as shown in fig. 2, the process mainly includes:
step 201: the old base station configures a context timer based on the behavior characteristics and the service characteristics of the UE; context keep-alive resources are preconfigured based on the context timer (since the UE keep-alive period may be moving over a considerable range, involving co-scheduling of the large range keep-alive resources).
Step 202: the old base station sends context keep-alive resource pre-configuration/pre-scheduling information to the UE;
wherein the context keep-alive resource pre-configuration/pre-scheduling message carries configuration information of a context timer configured for the UE.
Of course, the configuration information of the context timer may be carried explicitly or implicitly.
Wherein, the explicit carrying may refer to directly carrying a keep alive clock period of a context timer; the implicit carrying may refer to notifying the UE of how often to report information to the old base station.
Here, step 202 is applicable to 3 scenarios. In particular, the method comprises the following steps of,
the first scenario is: the old base station knows that the UE is still at the original site, which is denoted by C1;
the second case is: the old base station does not know whether the UE is still at the original site, which is denoted by C2;
the third scenario refers to: the UE is at the new site, represented by C3 in the figure.
Step 203: the UE carries out context keep-alive according to keep-alive preconfiguration and sends a keep-alive message to the old base station;
here, step 203 is applicable to 2 scenarios. In particular, the method comprises the following steps of,
the first scenario is: the old base station knows that the UE is still at the original site, which is denoted by C1;
the second case is: the old base station does not know whether the UE is still at the original site, which is indicated by C2 in the figure.
Step 204: the old base station sends a keep-alive confirmation message to the UE;
here, step 204 is the same as the applicable scenario of step 203.
Step 205: in a first scenario, the old base station retains the context message; in the second scenario, if the old base station does not receive the keep-alive message within the specified time (including the allowed retransmission time), the context is released, or the storage priority is lowered.
Step 206: the UE carries out context keep-alive according to keep-alive preconfiguration and sends a keep-alive message to a new base station;
here, step 206 applies to 1 scenario. Namely, the third case: the UE is at the new site, represented by C3 in the figure.
Step 207: the new base station sends a context information extraction message to the old base station;
step 208: the old base station transfers the context information of the user and modifies the context information as required;
step 209: the old base station sends a context information transfer message to the new base station;
step 210: the new base station sends a keep-alive acknowledgement message to the UE.
Here, the applicable scenarios of steps 207, 208, 209, 210 are the same as the applicable scenario of step 206.
In the above procedure, if resource pre-scheduling is not included, it is equivalent to the UE needing to acquire resources through access, collision resolution, and scheduling each time.
In the above communication flow, two major processes are mainly involved, the first major process is: when a new keep-alive clock period of the context timer arrives, if the old base station does not receive the keep-alive message fed back by the UE side within the keep-alive clock period plus the estimated air interface delay time, the context information is judged to be overdue, and the stored context information is released. The second major process is: the old base station extracts the wireless information from the context information; and performing resource mapping corresponding to the wireless information according to the wireless information, and reserving wireless resources on corresponding time resources based on a resource mapping result for the corresponding UE to perform keep-alive information transmission. For example, based on the context identifier of the UE on the access side, the corresponding resource information is bound, so that when the keep-alive clock of the context timer arrives, the UE directly uses the corresponding radio resource to perform keep-alive operation.
EXAMPLE III
Fig. 3 is a schematic diagram of another implementation flow of keep-alive context communication provided by the present invention, and as shown in fig. 3, the flow mainly includes:
step 301: the old base station decides to initiate a keep-alive command, possibly including keep-alive resource configuration, initiating a keep-alive paging message (ID of paging, such as context ID of user).
Step 302: the old base station keeps alive paging or scheduling information to the UE;
here, step 302 applies to 3 scenarios. In particular, the method comprises the following steps of,
the first scenario is: the old base station knows that the UE is still at the original site, which is denoted by C1;
the second case is: the old base station does not know whether the UE is still at the original site, which is denoted by C2;
the third scenario refers to: the UE is at the new site, represented by C3 in the figure.
Of course, the old base station may notify the UE of the keep-alive paging or scheduling message in one step, or may notify the UE in multiple steps.
Step 303: the UE conducts context keep-alive based on keep-alive preconfiguration or scheduling information and sends keep-alive messages to the old base station;
here, step 303 is applicable to 2 scenarios. In particular, the method comprises the following steps of,
the first scenario is: the old base station knows that the UE is still at the original site, which is denoted by C1;
the second case is: the old base station does not know whether the UE is still at the original site, which is indicated by C2 in the figure.
Step 304: the old base station sends a keep-alive acknowledgement message to the user.
Here, step 304 is the same as the applicable scenario of step 303.
Step 305: in a first scenario, the old base station retains the context message; in the second scenario, if the old base station does not receive the keep-alive message within the specified time (including the allowed retransmission time), the context is released, or the storage priority is lowered.
Step 306: the UE carries out context keep-alive according to keep-alive preconfiguration and sends a keep-alive message to a new base station;
here, step 306 applies to 1 scenario. Namely, the third case: the UE is at the new site, represented by C3 in the figure.
Step 307: the new base station sends a context information extraction message to the old base station;
step 308: the old base station transfers the context information of the user and modifies the context information as required;
step 309: the old base station sends a context information transfer message to the new base station;
step 310: the new base station sends a keep-alive acknowledgement message to the UE.
Here, the applicable scenarios of steps 307, 308, 309, 310 are the same as the applicable scenario of step 306.
In the communication flow, the base station sends a keep-alive command and keep-alive resource configuration to one or a group of UE, and the UE receiving the keep-alive resource configuration executes keep-alive operation; in the process of the keep-alive operation performed by the UE, the base station completes storage, or update, or transfer, or release, etc. of the context information.
It should be noted that the solution of the present invention may also be used for context maintenance of an LTE system, where the RRC Inactivity Timer may be used as a context Timer, and when the time of the RRC Inactivity Timer reaches, the RRC Inactivity Timer does not immediately release the RRC connection, but first asks the user whether to continue maintaining the connection or waits for the user to initiate connection delay, and after the determination, decides whether to release the RRC. This scheme has relatively little gain for the traditional single-station single-cell scenario, and the local context may be invalid after the user moves. Then, in the future more and more "de-cellular" (5G, 6G, etc. design concept), a plurality of sites have a very close cooperation relationship logically, and a shared context can be realized through some shared marks, etc.
For example, in a C-RAN scenario, the scheme of the present invention can also have good gain when applied to an LTE system. The gain is also more prominent for small data traffic with weak mobility. Here, the C-RAN refers to a Radio Access Network (RAN) based on Centralized (Centralized).
Example four
Fig. 4 is a schematic structural diagram of a keep-alive context management device provided by the present invention, and as shown in fig. 4, the device mainly includes:
an obtaining unit 41, configured to obtain a keep-alive behavior of the UE;
a management unit 42, configured to manage context information of the UE based on the keep-alive behavior of the UE.
Preferably, the obtaining unit 41 is further configured to:
determining whether the UE meets a starting condition for executing the keep-alive operation according to a preset rule;
when the UE is determined to meet the starting condition for executing the keep-alive operation, the keep-alive behavior of the UE is obtained;
the method for determining whether the UE meets the starting condition of executing the keep-alive operation according to the preset rule comprises the following steps:
determining whether the UE needs to execute keep-alive operation or not based on preset, estimated or pre-negotiated user keep-alive behavior information; or
The network side detects the current network resource, and when the network resource meets the preset condition, the UE is determined to need to execute the keep-alive operation.
Preferably, the preset, pre-estimated or pre-negotiated user keep-alive behavior information includes:
user keep-alive behavior information notified by the UE; or
The network side and the UE negotiate to determine user keep-alive behavior information; or
And the network side judges the user keep-alive behavior information.
Specifically, the user keep-alive behavior information is a context timer configured for the UE by the network side;
wherein the context timer is a keep alive timer, or,
the context timer is a user keep-alive behavior message sent by the UE to the network side under the condition that no data occurs in the timing time of each context timer.
In the foregoing solution, preferably, the apparatus further includes:
a configuration unit 43, configured to configure a context timer for the UE; and based on the context timer, pre-configuring context keep-alive resources for the UE so that the UE performs keep-alive operation by utilizing the context keep-alive resources within the timing duration of the context timer.
In the foregoing solution, preferably, the configuration unit 43 includes:
an obtaining subunit 431, configured to obtain a behavior feature and/or a service feature of the UE;
a configuration subunit 432, configured to configure a dedicated context timer for the UE according to the behavior feature and/or the service feature.
In the foregoing solution, preferably, the configuration subunit 442 is further configured to:
when the traffic intervals of the UEs are centrally distributed at T0, setting the keep alive clock period of the context timer to nt 0; if the mobility of the UE is lower than a first threshold value, continuing to prolong the keep-alive clock period N T0, and setting the keep-alive clock period to M N T0, wherein M is more than 1, N is a positive integer, and T0 is the interval between two data packets;
or,
when the probability that the traffic interval of the UE is larger than T1 is lower than a second threshold, setting the keep-alive clock period of the context timer to be T1, wherein T1 is larger than T0, and T1 is the interval between two data packets; if the mobility of the UE is above a third threshold, continuing to shorten the keep-alive clock period T1, setting the keep-alive clock period to P T1, where P < 1.
That is, the keep-alive clock period is related to both the occurrence rule of the traffic and the mobility of the UE, and focuses more on the occurrence rule of the user traffic itself.
The reference index for determining the mobility may be a moving rate of the UE or a number of cells that the UE passes through in a unit time.
Of course, those skilled in the art should understand that the specific implementation manner of configuring the UE with the dedicated context timer according to the behavior feature and/or the traffic feature is not limited to the above-listed ones, and will not be described herein again.
In the foregoing solution, preferably, the management unit 42 is further configured to:
and in the process that the UE executes the keep-alive operation according to the keep-alive resources configured for the UE by the network side, storing, updating, transferring, releasing or lowering the priority of the context information.
In the foregoing solution, preferably, the management unit 42 includes:
a release subunit 421, configured to, when a new keep-alive clock cycle of the context timer arrives, if the network side does not receive the keep-alive message fed back by the UE side within a certain time, determine that the context information is expired or is not important, and release or lower priority the stored context information;
wherein the certain time includes: keep alive clock period + pre-estimate air interface delay.
In the foregoing solution, preferably, the management unit 42 further includes:
a transferring subunit 422, configured to determine that the context of the UE is transferred and transfer the stored context information when the keep-alive behavior of the UE is different from the context storage jurisdiction where the UE last performs data transmission.
In the foregoing solution, preferably, the management unit 42 further includes:
an updating subunit 423, configured to update the stored context information when detecting that the context of the UE is updated, or the context is transferred, or a keep-alive message carrying context update and sent by the UE is received.
In the foregoing solution, optionally, the management unit 42 further includes:
an extracting subunit 424, configured to extract the wireless information from the context information; wherein the wireless information comprises a context identifier;
a prescheduling subunit 425, configured to perform resource prescheduling on the keep-alive information transmission based on the context identifier of the UE on the access side.
In the foregoing scheme, preferably, the pre-scheduling subunit 425 is further configured to: and performing resource mapping corresponding to the wireless information according to the wireless information, and reserving wireless resources on corresponding time resources based on a resource mapping result, so that the UE directly uses the corresponding wireless resources to perform keep-alive operation when a keep-alive clock of the context timer arrives.
The keep-alive based context management apparatus described above can be deployed on a base station.
It should be understood by those skilled in the art that the functions of the units in the context management device based on keep-alive according to this embodiment can be understood by referring to the related description of the context management method based on keep-alive, and the units in the context management device based on keep-alive according to this embodiment can be implemented by an analog circuit that implements the functions described in this embodiment, and can also be implemented by running software that executes the functions described in this embodiment on an intelligent terminal.
In practical applications, the specific structures of the acquiring unit 41, the managing unit 42, and the configuring unit 43 may all correspond to a processor. The specific structure of the processor may be a Central Processing Unit (CPU), a Micro Controller Unit (MCU), a Digital Signal Processor (DSP), a Programmable Logic Controller (PLC), or other electronic components or a collection of electronic components having a Processing function. The processor includes executable codes, the executable codes are stored in a storage medium, the processor can be connected to the storage medium through a communication interface such as a bus, and when the corresponding functions of the specific modules are executed, the executable codes are read from the storage medium and executed. The portion of the storage medium used to store the executable code is preferably a non-transitory storage medium.
The context management device based on keep-alive can provide context maintenance for the UE according to needs, and meanwhile, the full use of network resources is guaranteed. Specifically, the validity of the context is guaranteed through the keep-alive behavior; the shunting of the context can be carried out through the keep-alive behavior; meanwhile, the resource pre-scheduling can be carried out on the transmission of the keep-alive information by binding the context identifier.
EXAMPLE five
Fig. 5 is a schematic structural diagram of another keep-alive-based context management device provided by the present invention, and as shown in fig. 5, the device mainly includes:
the determining unit 51 is configured to obtain user keep-alive behavior information;
a processing unit 52, configured to execute a user keep-alive behavior based on the user keep-alive behavior information;
wherein, the user keep-alive behavior information is as follows:
user keep-alive behavior information determined by the UE;
the UE and the network side determine the user keep-alive behavior information through negotiation:
wherein, the user keep-alive behavior information determined by the UE is: when the preset conditions are met within the timing time of each context timer, sending a user keep-alive behavior message to a network side; wherein the preset conditions include: no data occurs.
Preferably, the apparatus further comprises:
the keep-alive unit 53 is configured to perform keep-alive operation by using the keep-alive resources configured for the network side.
The keep-alive based context management apparatus described above can be deployed on a UE.
It should be understood by those skilled in the art that the functions of the units in the context management device based on keep-alive according to this embodiment can be understood by referring to the related description of the context management method based on keep-alive, and the units in the context management device based on keep-alive according to this embodiment can be implemented by an analog circuit that implements the functions described in this embodiment, and can also be implemented by running software that executes the functions described in this embodiment on an intelligent terminal.
In practical applications, the specific structures of the determining unit 51, the processing unit 52 and the keep-alive unit 53 may all correspond to a processor. The specific structure of the processor can be an electronic component or a collection of electronic components with processing functions, such as a CPU, an MCU, a DSP or a PLC. The processor includes executable codes, the executable codes are stored in a storage medium, the processor can be connected to the storage medium through a communication interface such as a bus, and when the corresponding functions of the specific modules are executed, the executable codes are read from the storage medium and executed. The portion of the storage medium used to store the executable code is preferably a non-transitory storage medium.
The context management device based on keep-alive can provide context maintenance for the UE according to needs, and meanwhile, the full use of network resources is guaranteed.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units; can be located in one place or distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, all the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
Those of ordinary skill in the art will understand that: all or part of the steps for realizing the method embodiments can be completed by hardware related to program instructions, the program can be stored in a computer readable storage medium, and the program executes the steps comprising the method embodiments when executed; and the aforementioned storage medium includes: various media capable of storing program codes, such as a removable Memory device, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, and an optical disk.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (12)
1. A method for keep-alive based context management, the method comprising:
determining whether the UE needs to execute keep-alive operation or not based on preset, estimated or pre-negotiated user keep-alive behavior information; the user keep-alive behavior information is a context timer configured for the UE by the network side;
when the UE is determined to meet the starting condition for executing the keep-alive operation, the keep-alive behavior of the UE is obtained;
the network side pre-configures context keep-alive resources for the UE based on the context timer;
managing context information of the UE based on keep-alive behavior of the UE;
the context timer configured by the network side for the UE includes:
a network side acquires the behavior characteristics and/or the service characteristics of UE;
and configuring a dedicated context timer for the UE according to the behavior characteristics and/or the service characteristics.
2. The method of claim 1, wherein the pre-set, pre-estimated, or pre-negotiated user keep-alive behavior information comprises:
user keep-alive behavior information notified by the UE; or
The network side and the UE negotiate to determine user keep-alive behavior information; or
And the user keep-alive behavior information is judged by the network side.
3. The method of claim 2, wherein the user keep-alive behavior information is a context timer configured for the UE by the network side; wherein the context timer is a keep alive timer, or,
the context timer is a user keep-alive behavior message sent by the UE to the network side under the condition that no data occurs in the timing time of each context timer.
4. The method of claim 1, wherein managing context information of the UE based on keep-alive behavior of the UE comprises:
in the process that the UE executes the keep-alive operation according to the keep-alive resources configured for the UE by the network side, the network side stores, updates, transfers, releases or reduces the priority of the context information.
5. The method of claim 4, wherein the releasing or prioritizing the context information by the network side comprises:
when a new keep-alive clock period of the context timer arrives, if the network side does not receive the keep-alive message fed back by the UE side within a certain time, the context information is judged to be overdue or unimportant, and the stored context information is released or priority reduction processing is carried out;
wherein the certain time includes: keep alive clock period + pre-estimate air interface delay.
6. The method of claim 4, wherein the transferring context information by the network side comprises:
when the keep-alive behavior of the UE is different from the context storage administration area where the UE last transmits data, the context of the UE is judged to be transferred, and the stored context information is transferred or updated.
7. The method of claim 4, wherein the updating of the context information by the network side comprises:
and when the context of the UE is detected to be updated, or the context is transferred, or a keep-alive message carrying context update and sent by the UE is received, updating the stored context information.
8. A keep-alive-based context management method applied to a terminal side is characterized by comprising the following steps:
the UE executes the user keep-alive behavior based on the user keep-alive behavior information;
the executing the user keep-alive behavior based on the user keep-alive behavior information comprises:
the UE utilizes the keep-alive resources configured for the UE by the network side to carry out keep-alive operation;
the user keep-alive behavior information is as follows:
within the timing time of each context timer, when a preset condition is met, a user keep-alive behavior message is sent to a network side; or
And the user keep-alive behavior information is judged by the network side.
9. The method according to claim 8, wherein the preset condition comprises: no data occurs.
10. A keep-alive based context management device, the device comprising:
the acquisition unit is used for determining whether the UE needs to execute the keep-alive operation or not based on the preset, estimated or pre-negotiated user keep-alive behavior information; the user keep-alive behavior information is a context timer configured for the UE by the network side;
when the UE is determined to meet the starting condition for executing the keep-alive operation, the keep-alive behavior of the UE is obtained;
the context timer configured by the network side for the UE includes:
a network side acquires the behavior characteristics and/or the service characteristics of UE;
configuring a dedicated context timer for the UE according to the behavior characteristics and/or the service characteristics;
the management unit is used for managing the context information of the UE based on the keep-alive behavior of the UE;
and the configuration unit is used for pre-configuring context keep-alive resources for the UE based on the context timer so that the UE performs keep-alive operation by utilizing the context keep-alive resources.
11. The apparatus of claim 10, wherein the management unit is further configured to:
and in the process that the UE executes the keep-alive operation according to the keep-alive resources configured for the UE by the network side, storing, updating, transferring, releasing or lowering the priority of the context information.
12. A keep-alive based context management device, the device comprising:
the determining unit is used for acquiring the keep-alive behavior information of the user;
the processing unit is used for executing the user keep-alive behavior based on the user keep-alive behavior information;
the keep-alive unit is used for carrying out keep-alive operation by utilizing the keep-alive resources configured for the keep-alive unit by the network side;
the user keep-alive behavior information is as follows:
within the timing time of each context timer, when a preset condition is met, a user keep-alive behavior message is sent to a network side; or
And the user keep-alive behavior information is judged by the network side.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610121601.7A CN107155222B (en) | 2016-03-03 | 2016-03-03 | Context management method and device based on keep-alive |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610121601.7A CN107155222B (en) | 2016-03-03 | 2016-03-03 | Context management method and device based on keep-alive |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107155222A CN107155222A (en) | 2017-09-12 |
| CN107155222B true CN107155222B (en) | 2020-04-17 |
Family
ID=59791468
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610121601.7A Active CN107155222B (en) | 2016-03-03 | 2016-03-03 | Context management method and device based on keep-alive |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107155222B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114143914B (en) * | 2018-01-11 | 2024-05-17 | 惠州Tcl移动通信有限公司 | Paging method and device |
| CN110753356B (en) * | 2018-07-23 | 2023-05-05 | 中国移动通信有限公司研究院 | Method, device and storage medium for enabling user plane optimization function |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012150473A1 (en) * | 2011-05-03 | 2012-11-08 | Nokia Corporation | Method and apparatus for keep-alive signalling |
| CN103096293A (en) * | 2011-11-04 | 2013-05-08 | 中兴通讯股份有限公司 | Application data processing method and device |
| CN103975614A (en) * | 2012-11-14 | 2014-08-06 | 华为技术有限公司 | Method and apparatus for processing wireless link failure |
| CN105228238A (en) * | 2014-06-13 | 2016-01-06 | 中国移动通信集团公司 | A kind of periodically keep-alive transmission method, equipment and system |
-
2016
- 2016-03-03 CN CN201610121601.7A patent/CN107155222B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012150473A1 (en) * | 2011-05-03 | 2012-11-08 | Nokia Corporation | Method and apparatus for keep-alive signalling |
| CN103096293A (en) * | 2011-11-04 | 2013-05-08 | 中兴通讯股份有限公司 | Application data processing method and device |
| CN103975614A (en) * | 2012-11-14 | 2014-08-06 | 华为技术有限公司 | Method and apparatus for processing wireless link failure |
| CN105228238A (en) * | 2014-06-13 | 2016-01-06 | 中国移动通信集团公司 | A kind of periodically keep-alive transmission method, equipment and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107155222A (en) | 2017-09-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108616950B (en) | Mobility management method between wireless access networks, core network equipment and base station | |
| WO2018014741A1 (en) | Data transmission, reception and transfer method and apparatus | |
| CN107370573B (en) | Method and equipment for transmitting downlink data | |
| WO2018019001A1 (en) | Terminal state conversion method and apparatus | |
| CN107396455A (en) | Connection processing method and device | |
| CN109691197A (en) | A kind of data transmission method, equipment and system | |
| CN104105199A (en) | Paging method, device and system | |
| CN107231623A (en) | A kind of data dispatching method, base station and system | |
| US11706732B2 (en) | Method and apparatus for controlling UE for cellular IoT service in 5G mobile communication system | |
| US8767660B2 (en) | Method and system for releasing resources and evolved node base | |
| JP7178407B2 (en) | Method, apparatus and computer storage medium for controlling limited UE capabilities | |
| JP2023551453A (en) | Positioning method and communication device | |
| CN104768233A (en) | A D2D communicating method and terminal | |
| CN107155222B (en) | Context management method and device based on keep-alive | |
| CN107925930A (en) | A kind of acquisition methods, relevant device and the system of customer equipment context information | |
| CN110858993B (en) | Information transmission method and device | |
| CN110290565B (en) | Access layer context management method and device | |
| US9729302B2 (en) | Apparatus and method for controlling resources in a core network | |
| CN102883297A (en) | Method and system for activating terminal | |
| CN103582035B (en) | A kind of management method and system of radio-resource-configuration | |
| US20200252842A1 (en) | Managing cell group configuration in disaggregated base station architecture | |
| EP3300437B1 (en) | Paging for downlink data transfer in connectionless mode in a mobile system | |
| EP3716664B1 (en) | Data transmission method and device, and computer storage medium | |
| EP3716684B1 (en) | Method and system for acquiring terminal context, computer storage medium | |
| CN112543206B (en) | Group establishing method, access device, system and storage medium |
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 |