WO2018233554A1 - Method and apparatus for suspending user terminal - Google Patents

Abstract

A method for suspending a user terminal comprises: monitoring the activeness of internet-of-things user terminals accessing a base station, and determining an inactive internet-of-things user terminal according to the monitoring result; counting the inactive time period of the inactive internet-of-things user terminal; and when the counted inactive time period exceeds a time period, making a suspension acceptance decision on the inactive internet-of-things user terminal, and performing an operation for suspending or releasing the inactive internet-of-things user terminal according to the suspension acceptance decision result.

Description

Method and device for suspending user terminal Technical field

The present disclosure relates to, but is not limited to, the field of Internet of Things technology, and in particular, a method and apparatus for suspending a user terminal.

Background technique

The Internet of Things is an important part of the new generation of information technology, and an important stage of development in the era of "informatization." Its English name is: "Internet of things (IoT)". As the name suggests, the Internet of Things is the Internet that connects things. Cell-based NB-IoT (Narrow Band Internet of Things) is an important branch of the Internet of Everything. Built on a cellular network, NB-IoT consumes only about 180 kHz of bandwidth and can be deployed directly on a GSM (Global System for Mobile) network, a UMTS (Universal Mobile Telecommunications System) network, or LTE (Long Term). Evolution, long-term evolution) network to reduce deployment costs and achieve smooth upgrades.

The introduction of NB-IoT has brought great improvement requirements to LTE networks. In the LTE process, for the NB-IoT terminal, the number of units of data is transmitted, and the terminal energy consumption and network signaling overhead are too high. On the one hand, in order to transmit or receive data of a small number of bytes, the terminal enters the connected state from the idle state, and the consumed network signaling overhead is far greater than the data payload itself; on the other hand, the complex signaling procedure based on LTE, It also brings a lot of overhead to the power consumption of the terminal.

In order to meet the access requirements of NB-IoT terminals, 3GPP (3rd Generation Partnership Project) has enhanced the overall architecture and process of the network, and proposed a control plane optimized transmission scheme and a user plane optimized transmission scheme.

The control plane optimized transmission scheme generally implements transmission of IP (Internet Protocol) data or non-IP data between the NB-IoT terminal and the network through control plane signaling. According to the solution, the user equipment (UE) can carry the NAS in the radio signaling bearer SRB (Signaling radio bearer) in the process of requesting the RRC (Radio Resource Control) connection. Network Attached Storage (Network Attached Storage), which carries IP data or non-IP data in the NAS packet to achieve the use of the control plane to transmit user plane data, referred to as CP (Control Plane, control plane) working mode.

The user plane optimized transmission scheme generally introduces an RRC connection suspension and recovery process. After the terminal enters the idle state, the base station and the network still store important context information of the terminal, so as to quickly reestablish the wireless connection and the core network connection through the recovery process, thereby reducing the network. Information interaction, referred to as UP (User Plane, user plane) working mode.

In the CP working mode, if there is no service for a period of time after the UE accesses, the eNodeB (Evolved Node B) releases the RRC connection of the UE. The RRC release process is similar to the LTE system. The eNodeB sends an RRC Connection Release-NB message on the SRB1 (Signalling Radio Bearers1) through the DL-DCCH (Downlink Logical-Dedicated Control CHannel). The message may optionally carry redirection information (for cell selection) and extended latency information (the extended latency information that the terminal will receive to the NAS).

In the UP working mode, if there is no service for a period of time after the UE accesses, the eNodeB suspends the RRC connection of the UE. When the eNodeB decides to suspend the RRC connection, the eNodeB sends an RRC Connection Release-NB message to the SRB1 through the downlink logical channel DL-DCCH. The release reason carried in the message is RRC suspension and carries the recovery identifier (ResumeID). The terminal performs related operations of the access layer context suspension. In addition, the message may optionally carry redirection information and extended waiting time information.

In the NB-IoT system, if the UE accesses in the UP mode, it only switches between the suspend state and the active state until the terminal or the core network actively releases for some reason.

Summary of the invention

In the NB-IoT system, since the suspension of the UE needs to save context information on the eNodeB side, it occupies a certain resource.

The present disclosure provides a method and apparatus for suspending a user terminal, which can prevent a base station from effectively controlling the suspension of the user, resulting in wasted system resources and degraded system performance.

An embodiment of the present disclosure provides a method for a user terminal to hang, comprising:

Monitoring the activity level of the IoT user terminal accessing the base station, and determining the inactive IoT user terminal according to the monitoring result;

Counting the inactivity time of the inactive IoT user terminal;

When the inactive duration of the timeout expires, the inactive IoT user terminal is suspended and accepted, and the operation of suspending or releasing the inactive IoT user terminal is performed according to the pending admission decision result.

The embodiment of the present disclosure further provides an apparatus for suspending a user terminal, including:

The monitoring module is configured to: monitor an activity level of the IoT user terminal accessing the base station, and determine an inactive IoT user terminal according to the monitoring result;

a timing module, configured to: time an inactive duration of the inactive IoT user terminal;

Suspending the admission decision processing module, configured to: when the inactive duration of the timing expires, suspending the acceptance decision on the inactive IoT user terminal, and executing the inactive IoT user according to the pending acceptance decision result The operation of the terminal to suspend or release.

Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed, implement the method of suspending the user terminal.

According to the solution provided by the embodiment of the present disclosure, after the suspended admission decision process is performed on the monitored inactive IoT user terminal, the operation of suspending or releasing the inactive IoT user terminal is performed, so that the eNodeB can effectively control The hang of the user enables the system resources to be effectively utilized, and the system performance is degraded due to excessive memory usage.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

FIG. 1 is a flowchart of a method for suspending a user terminal according to an embodiment of the present disclosure;

2 is a schematic diagram of a device for suspending a user terminal according to an embodiment of the present disclosure;

3 is a block diagram of a user suspension control provided by an embodiment of the present disclosure;

4 is a flowchart of a user-suspended admission decision provided by an embodiment of the present disclosure;

FIG. 5 is a flowchart of a decision of suspending a user for demolitions according to an embodiment of the present disclosure.

Preferred embodiment of the present disclosure

Embodiments of the present disclosure will be described below with reference to the accompanying drawings.

In the NB-IoT system, after the UE accesses the UP working mode, it only switches between the suspended state and the active state until the terminal or the core network actively releases for some reason. Since the suspension of the UE needs to save context information on the eNodeB side, it occupies a certain resource. Therefore, the technical solution of the embodiment of the present disclosure is used to implement the suspension of the UE according to the actual situation of the base station to ensure stable operation of the system.

First embodiment

FIG. 1 is a flowchart of a method for suspending a user terminal according to an embodiment of the present disclosure. As shown in FIG. 1 , the following steps may be performed by a base station:

Step S101: monitoring the activity level of the IoT user terminal accessing the base station, and determining the inactive IoT user terminal according to the monitoring result;

Step S102: Timing the inactivity duration of the inactive IoT user terminal;

Step S103: When the inactive duration of the timer expires, the inactive IoT user terminal is suspended and accepted, and the operation of suspending or releasing the inactive IoT user terminal is performed according to the pending admission decision result. .

The embodiment of the present disclosure may further include: the base station separately monitors the memory occupancy rate and suspends the number of the Internet of Things user terminals to determine whether the access base station is in a congested state; and when determining that the access base station is in a congested state The base station clears context information of the IoT user terminal.

The base station separately monitors the memory occupancy rate and suspends the number of the Internet of Things user terminals, and determines whether the access base station is in a congested state, and the method includes: the base station passes the memory occupancy rate and suspends the Internet of Things user terminal. The quantity is separately monitored to obtain the memory occupancy rate and the number of IoT user terminals are suspended; when the memory usage rate obtained by the base station exceeds the preset memory occupation threshold, the access base station is judged to be in a congested state; or when the base station is When the number of the suspended IoT user terminals exceeds the preset number of pending thresholds, it is determined that the access base station is in a congested state.

The clearing the context information of the Internet of Things user terminal may include: the base station determines the priority of the IoT user terminal by traversing all the priorities of the suspended IoT user terminal, and clears the lowest priority object. Context information of the networked user terminal; the eNB traverses the hang time of all suspended IoT user terminals, determines the IoT user terminal whose hang time exceeds the preset time limit, and clears the hang time longer than the preset duration The context information of the IoT user terminal of the threshold.

The inactive IoT user terminal suspends the admission decision when the timed inactivity timeout expires, and performs the suspending or releasing of the inactive IoT user terminal according to the pending admission decision result. The operation may include: determining whether the access base station is in a congested state when the timed inactive timeout expires; and determining that the access base station is in a congested state, by sequentially performing a probabilistic rejection, currently suspending the Internet of Things user terminal The quantity and the pending acceptance decision of the current memory usage, and performing the operation of suspending or releasing the inactive IoT user terminal according to the pending acceptance decision result.

When determining that the access base station is in a congested state, the suspending acceptance decision of the probabilistic rejection, the number of currently suspended Internet of Things user terminals, and the current memory occupancy rate are sequentially performed, and according to the pending acceptance decision result, The operation of suspending or releasing the inactive IoT user terminal may include: when determining that the access base station is in a congested state, the base station generates a random number for determining that the inactive IoT user terminal suspends admission, And determining whether the random number is less than a preset suspension probability rejection threshold; when determining that the random number is less than a preset suspension probability rejection threshold, the base station determines whether the number of currently suspended Internet of Things user terminals is less than The preset maximum number of suspended IoT user terminals, when it is determined that the random number is not less than the preset suspension probability rejection threshold, the release operation of the inactive IoT user terminal is performed; when the current suspension is determined When the number of IoT user terminals is less than the preset maximum number of suspended IoT user terminals, the base station determines whether the current memory usage ratio is less than a preset. The maximum memory usage, when it is determined that the number of currently suspended IoT user terminals is not less than the preset maximum number of suspended IoT user terminals, the release operation of the inactive IoT user terminal is performed; when the current memory usage is determined to be less than Performing a suspending operation of the inactive IoT user terminal when the maximum memory usage is preset, and executing the inactive IoT user terminal when determining that the current memory usage is not less than a preset maximum memory usage rate Release operation.

Second embodiment

2 is a schematic diagram of a device for suspending a user terminal according to an embodiment of the present disclosure. As shown in FIG. 2, the monitoring module 201 may be configured to: monitor an activity level of an Internet of Things user terminal that accesses a base station, And determining, according to the monitoring result, the inactive IoT user terminal; the timing module 202 is configured to: time the inactive duration of the inactive IoT user terminal; and suspend the admission decision processing module 203, set to: when timing When the inactivity timeout expires, the inactive IoT user terminal is suspended and accepted, and the operation of suspending or releasing the inactive IoT user terminal is performed according to the pending admission decision result.

The embodiment of the present disclosure may further include: a clearing processing unit, configured to: determine whether the access base station is in a congested state by monitoring a memory occupancy rate and suspending the number of the Internet of Things user terminals, respectively; When the base station is in a congested state, the context information of the IoT user terminal is cleared.

Optionally, the clearing processing unit includes: a monitoring subunit, configured to: monitor memory occupancy rate and suspend the number of IoT user terminals separately, obtain memory occupancy rate, and suspend the number of IoT user terminals; The unit is set to: when the obtained memory usage exceeds a preset memory occupation threshold, or when the obtained number of suspended IoT user terminals exceeds a preset number of pending thresholds, the access is determined. The base station is in a congested state; the clearing processing subunit is configured to: determine the priority of the lowest priority IoT user terminal by traversing the priority of all suspended IoT user terminals, and clear the context of the lowest priority IoT user terminal Information, and by traversing the hang time of all suspended IoT user terminals, determining an IoT user terminal whose hang time exceeds a preset time limit, and clearing the hang time longer than a preset time limit Context information for networked user terminals.

The suspending control of the disclosed embodiment may include the following two aspects of the strategy:

Acceptance control

When there is an IoT user terminal that needs to be suspended, the eNodeB can make a probabilistic rejection, suspend the number of IoT user terminals, and determine the memory usage. When the judgment is passed, the IoT user terminal can be suspended; when the decision is not passed, the IoT user terminal can be released.

2. Load control

When the load control switch is turned on, the timer period can be set to detect the total number of currently suspended IoT user terminals and the memory occupancy rate. If the maximum threshold value is exceeded 80%, the eNodeB can be determined to be already in the Internet of Things user. The congestion state of the terminal is suspended, and the congestion identifier is set. In the congested state, the eNodeB can select the IoT user terminal with the lowest priority or the suspension duration exceeding the set threshold in the currently suspended IoT user terminal, and put it into the forced disconnect queue to clear the context information of these IoT user terminals.

The embodiments of the present disclosure will be described in detail below with reference to FIGS. 3 to 5.

First, configure the dedicated parameters of the user suspend control on the background network management, as shown in Table 1:

Table 1: Special parameter configuration table for user suspension control

Numbering	parameter name	Parameter meaning	Ranges	Defaults
1	@SuspendBanConSwch	Suspend load control switch	0: off; 1: on	0
2	@SuspendPrioritySwch	Suspend priority control switch	0: off; 1: on	0
3	@SuspendTimeConSwch	Suspend duration control switch	0: off; 1: on	0
4	@SuspendMaxTime	Maximum time to hang	0～10000s	1440s
5	@SuspendPrabRejThrd	Suspend probability rejection threshold	0-100	50
6	@SuspendTotalNum	Maximum number of suspended users	0-120000	120000
7	@MemUsedMaxRate	Maximum memory usage	0-100	90

FIG. 3 is a schematic diagram of a module device for user suspend control according to an embodiment of the present disclosure. As shown in FIG. 3, FIG. 3 may include a control module, a decision module, and an implementation module.

The control module is configured to: determine whether the user inactivity timer or the suspend load control timer expires, and if it times out, send it to the decision module.

After the power-on is completed, the base station can detect the suspended load control switch @SuspendBanConSwch of the network management configuration. If it is turned on, the periodic load control timer can be set. When the timer expires, the suspended user can be forced to enter the suspended decision.

When a user accesses in the UP mode, if there is no service for a period of time, that is, after the inactivity timer expires, the user can enter the admission decision.

The decision module may be configured to: perform a decision according to the type of the triggered message, wherein the decision may include an admission decision suspended by the user, and the determination may further include suspending the user's forced demolition decision.

The implementation module may be configured to: perform corresponding operations according to the decision result of the decision module. If the admission is successful after the user's pending acceptance decision, the user suspends the process, and if the admission fails, the user release process can be performed. After the user's forced demolition decision is suspended, the user's demolitions in the queue can be executed to clear the context information of these users.

FIG. 4 is a flowchart of a user-suspended admission decision provided by an embodiment of the present disclosure. As shown in FIG. 4, FIG. 4 may include:

Step 401: Determine whether the current congestion identifier is set (the identifier is set in the demolit decision), if the flag is 1, proceed to the next step to make a probabilistic rejection decision, if the flag is 0, then go to step 404;

Step 402: Generate a random number, ranging from 0 to 100.

Step 403: Determine whether the random number is less than the suspend probability rejection threshold @SuspendPrabRejThrd, if the random number is less than the suspend probability rejection threshold @SuspendPrabRejThrd, proceed to the next step, if the random number is not less than the suspend probability rejection threshold @SuspendPrabRejThrd, the admission fails;

Step 404: Determine whether the current number of suspended users is less than the maximum number of suspended users @SuspendTotalNum. If the number of currently suspended users is less than the maximum number of suspended users @SuspendTotalNum, proceed to the next step, if the number of currently suspended users is not less than the maximum pending number The number of users @SuspendTotalNum failed to accept;

Step 405: Determine whether the current memory usage is less than the maximum memory usage rate @MemUsedMaxRate. If the current memory usage is less than the maximum memory usage rate @MemUsedMaxRate, the admission is successful. If the current memory usage is not less than the maximum memory usage rate @MemUsedMaxRate, the admission fails.

FIG. 5 is a flowchart of a decision of suspending a user to dismantle the embodiment of the present disclosure. As shown in FIG. 5, the method may include:

Step 501: Determine whether the current user suspension number is greater than 80% of the maximum number of suspended users @SuspendTotalNum, or whether the current memory usage rate is greater than 80% of the maximum memory usage rate @MemUsedMaxRate. If any of the above conditions are met, the process proceeds to step 501a. If the congestion flag is 1, the process proceeds to step 502. If the above conditions are not met, the process proceeds to step 501b, that is, the congestion flag is 0, and the implementation module is entered. Step 501 can include:

Step 501c, determining whether the current user suspension number is greater than 80% of the maximum number of suspended users @SuspendTotalNum, and if so, proceeding to step 501a; otherwise, proceeding to step 501d;

Step 501d, determining whether the current memory occupancy rate is greater than 80% of the maximum memory usage rate @MemUsedMaxRate, if yes, proceeding to step 501a; otherwise, proceeding to step 501b;

Step 502: Determine whether the suspend priority control switch @SuspendPrioritySwch is turned on. If it is traversing all the currently suspended users, proceed to step 502a, that is, put the user with the lowest priority into the demolit queue, and proceed to step 503; if not, traverse the current Suspend all users do nothing to go directly to step 503;

Step 503: Determine whether the suspend duration control switch @SuspendTimeConSwch is open. If it is traversing all the currently suspended users, proceed to step 503a, that is, put the user whose suspend duration is greater than the suspending maximum duration @SuspendMaxTime into the demolit queue, and then enter Demolition implementation module; if you are not traversing all users currently suspended, do not do anything directly into the demolitation implementation module.

The embodiments of the present disclosure are described in detail below with an optional embodiment:

Third embodiment: no load control, suspension acceptance

The process can include:

1) The network management is configured as the system default value, and the base station is initialized.

2) Since @SuspendBanConSwch is 0, the load control cycle timer is not set and the load control device is not entered.

3) Now when a user accesses in UP mode, the inactivity timer expires and the flow enters the admission control device. Since the congestion flag is 0, no probability rejection decision is made. Then judge the current number of suspended users, less than @SuspendTotalNum, and then determine the current memory usage, less than @MemUsedMaxRate, suspend acceptance, the execution user hangs.

Fourth embodiment: no load control, the number of suspended users fails to accept

The process can include:

1) The network management configuration @SuspendTotalNum is 1, and other parameters are default values.

2) Since @SuspendBanConSwch is 0, the load control cycle timer is not set and the load control device is not entered.

3) Assuming that one user has been suspended, one user has now entered the suspended admission control device. First, it is judged that the congestion flag is 0, and the probability rejection decision is not performed. Then judge the current number of suspended users, equal to @SuspendTotalNum, the pending acceptance decision fails, and the user release is performed.

Fifth embodiment: no load control, memory occupancy acceptance failure

The process can include:

1) The network management configuration @MemUsedMaxRate is 1, and other parameters are default values.

2) Since @SuspendBanConSwch is 0, the load control cycle timer is not set and the load control device is not entered.

3) The base station is initialized and no user has been suspended. There is now a user entering the suspended admission control device. It is judged that the congestion flag is 0, and the probability rejection decision is not performed. Then, it is determined that the number of currently suspended users is less than @SuspendTotalNum, and then the current user occupancy rate is greater than @MemUsedMaxRate, the acceptance decision fails, and the user release is performed.

Sixth embodiment: performing load control, probability acceptance failure

The process can include:

1) The network management configuration @SuspendBanConSwch is 1, @SuspendTotalNum is 1, and other parameters are default values.

2) After the base station is initialized, the load cycle timer is set, and the timer enters the load control device after the timer expires. At the beginning, no user hangs, and the current number of users and memory usage do not exceed 80% of the maximum threshold. The congestion flag is 0 and the device is exited.

3) Assume that a user has hanged and the timer has timed out and entered the load receiving device. It is judged that the current number of users is 1, which is greater than @SuspendTotalNum*80%, and the congestion flag is 1, and then the forced demolition decision is made. Since @SuspendPrioritySwch and @SuspendTimeConSwch are both 0, the device is exited without processing.

4) Next, a user to be suspended enters the admission control device, and when the congestion flag is detected as 1, a probabilistic rejection decision is made. The base station generates a random number that is less than or equal to @SuspendPrabRejThrd, the admission decision fails, and the user release is performed.

Seventh embodiment: performing load control and forcibly disassembling users

The process can include:

1) The network management configuration @SuspendBanConSwch, @SuspendPrioritySwch, @SuspendTimeConSwch are all open, @SuspendMaxTime is 5 minutes, and other parameters are default values.

2) Assume that three users are currently suspended. User A has a priority of 1 and a suspend time of 1 minute. User B has a priority of 2 and a suspend time of 6 minutes. User C has a priority of 2. The hang time is 2 minutes.

3) After the load control timer expires, it enters the load receiving device. If the current number of users is less than @SuspendTotalNum*80% and the current memory usage is greater than @MemUsedMaxRate*80%, the congestion flag is set to 1.

4) Next, it is judged that @SuspendPrioritySwch is 1, traversing the priority of the suspended user, and placing the user A with the priority of 1 into the forced disconnect queue.

5) Next, it is judged that @SuspendTimeConSwch is 1, the traversal duration of the suspended user is traversed, and the user B smaller than the threshold @SuspendMaxTime is placed in the forced detach queue.

6) Release the user in the forced disconnect queue, delete the context information of users A and B, and exit the load control device.

According to the solution provided by the embodiment of the present disclosure, the eNodeB can effectively control the hang of the user, so that the system resources can be effectively utilized, and the system performance is prevented from being degraded due to excessive memory usage.

Embodiments of the present disclosure also provide a base station suspended by a user terminal, including admission control and load control. The admission control may be used to monitor the activity level of the IoT user terminal accessing the base station, and determine the inactive IoT user terminal according to the monitoring result, and time the inactivity time of the inactive IoT user terminal. When the inactive duration of the timeout expires, the inactive IoT user terminal is suspended and accepted, and the operation of suspending or releasing the inactive IoT user terminal is performed according to the pending admission decision result. The load control may be used to monitor whether the access base station is in a congested state by monitoring the memory occupancy rate and suspending the number of the IoT user terminals respectively; when determining that the access base station is in a congested state, the base station clears Context information of the Internet of Things user terminal.

An embodiment of the present disclosure further provides an electronic device suspended by a user terminal, the electronic device comprising: a processor and a memory, wherein the memory is configured to store executable program code; the processor reads the The executable program code stored in the memory runs a program corresponding to the executable program code for performing the following steps:

Monitoring the activity level of the IoT user terminal accessing the base station, and determining the inactive IoT user terminal according to the monitoring result;

Counting the inactivity time of the inactive IoT user terminal;

When the inactive duration of the timeout expires, the inactive IoT user terminal is suspended and accepted, and the operation of suspending or releasing the inactive IoT user terminal is performed according to the pending admission decision result.

Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed, implement the method of suspending the user terminal.

Those of ordinary skill in the art will appreciate that all or some of the steps, systems, and functional blocks/units of the methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical The components work together. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules or other data. Sex, removable and non-removable media. The computer storage medium includes, but is not limited to, Random Access Memory (RAM), Read-Only Memory (ROM), and Electrically Erasable Programmable Read-only Memory (EEPROM). Flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cassette, magnetic tape, disk storage or other magnetic storage device, or Any other medium used to store the desired information and that can be accessed by the computer. Moreover, it is well known to those skilled in the art that communication media typically includes computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media. .

A person skilled in the art can understand that the technical solutions of the present disclosure may be modified or equivalent, without departing from the spirit and scope of the present disclosure, and should be included in the scope of the claims of the present disclosure.

Industrial applicability

According to the solution provided by the embodiment of the present disclosure, after the suspended admission decision process is performed on the monitored inactive IoT user terminal, the operation of suspending or releasing the inactive IoT user terminal is performed, so that the eNodeB can effectively control The hang of the user enables the system resources to be effectively utilized, and the system performance is degraded due to excessive memory usage.

Claims (10)

1. A method for a user terminal to hang, comprising:

   Monitoring the activity level of the IoT user terminal accessing the base station, and determining the inactive IoT user terminal according to the monitoring result;

   Counting the inactivity time of the inactive IoT user terminal;

   When the inactive duration of the timeout expires, the inactive IoT user terminal is suspended and accepted, and the operation of suspending or releasing the inactive IoT user terminal is performed according to the pending admission decision result.
2. The method of claim 1 further comprising:

   Determining whether the access base station is in a congested state by monitoring the memory occupancy rate and suspending the number of the Internet of Things user terminals respectively;

   When it is determined that the access base station is in a congested state, the context information of the Internet of Things user terminal is cleared.
3. The method according to claim 2, wherein the monitoring of the memory occupancy rate and the suspension of the number of IoT user terminals respectively determines whether the access base station is in a congested state comprises:

   By monitoring the memory usage and the number of suspended IoT user terminals separately, the memory occupancy rate and the number of IoT user terminals are suspended;

   When the obtained memory usage exceeds a preset memory occupation threshold, determining that the access base station is in a congested state; or

   When the number of the suspended Internet of Things user terminals exceeds the preset number of pending thresholds, it is determined that the access base station is in a congested state.
4. The method of claim 2, wherein the clearing context information of the Internet of Things user terminal comprises:

   By traversing the priority of all suspended IoT user terminals, determining the lowest priority IoT user terminal, and clearing the context information of the lowest priority IoT user terminal;

   By traversing the hang time of all suspended IoT user terminals, determining the IoT user terminal whose hang time exceeds the preset time limit, and clearing the IoT user terminal whose hang time exceeds the preset time limit Contextual information.
5. The method of claim 1, wherein the inactive IoT user terminal suspends the admission decision when the timed inactivity time expires, and performs the inactivity according to the pending admission decision result The operation of the IoT user terminal to suspend or release includes:

   When the inactive duration of the timer expires, determining whether the access base station is in a congested state;

   When it is determined that the access base station is in a congested state, the probabilistic rejection, the number of currently suspended IoT user terminals, and the pending acceptance judgment of the current memory occupancy rate are sequentially performed, and the failure is performed according to the pending acceptance decision result. The operation of the active IoT user terminal to suspend or release.
6. The method according to claim 5, wherein when determining that the access base station is in a congested state, the pending acceptance decision is made by sequentially performing a probabilistic rejection, a number of currently suspended Internet of Things user terminals, and a current memory occupancy rate. And performing the operation of suspending or releasing the inactive IoT user terminal according to the suspension acceptance decision result, including:

   When determining that the access base station is in a congested state, generating a random number for determining that the inactive IoT user terminal suspends admission, and determining whether the random number is less than a preset suspension probability rejection threshold;

   When it is determined that the random number is less than a preset suspension probability rejection threshold, determining whether the number of currently suspended Internet of Things user terminals is less than a preset maximum number of suspended Internet of Things user terminals; when determining that the random number is not less than Performing a release operation of the inactive IoT user terminal when the preset suspend probability reject threshold is performed;

   When it is determined that the number of currently suspended IoT user terminals is less than the preset maximum number of suspended IoT user terminals, it is determined whether the current memory usage rate is less than a preset maximum memory usage rate; when judging that the number of currently suspended IoT user terminals is not When the number of the maximum suspended IoT user terminals is less than the preset maximum, the release operation of the inactive IoT user terminal is performed;

   When the current memory usage is less than the preset maximum memory usage, the suspending operation of the inactive IoT user terminal is performed; when it is determined that the current memory usage is not less than the preset maximum memory usage, the performing The release operation of the inactive IoT user terminal.
7. A device for suspending a user terminal, comprising:

   The monitoring module is configured to: monitor an activity level of the IoT user terminal accessing the base station, and determine an inactive IoT user terminal according to the monitoring result;

   a timing module, configured to: time an inactive duration of the inactive IoT user terminal;

   Suspending the acceptance decision processing module, configured to: when the inactive duration of the timing expires, suspending the acceptance decision on the inactive IoT user terminal, and executing the inactive Internet of Things according to the pending acceptance decision result The operation of the user terminal to suspend or release.
8. The apparatus of claim 7 further comprising:

   The clearing processing unit is configured to: determine whether the access base station is in a congested state by monitoring the memory occupancy rate and suspending the number of the IoT user terminals respectively; and when the access base station is determined to be in a congested state, clearing Context information of the Internet of Things user terminal.
9. The apparatus of claim 8 wherein said clearing processing unit comprises:

   The monitoring subunit is configured to: monitor the memory occupancy rate and the number of suspended IoT user terminals separately, and obtain the memory occupancy rate and the number of suspended IoT user terminals;

   The determining subunit is set to: when the obtained memory occupancy exceeds a preset memory occupation threshold, or when the obtained number of suspended IoT user terminals exceeds a preset number of pending thresholds, The access base station is in a congested state.
10. The apparatus of claim 9, wherein the clear processing unit comprises:

    The clear processing subunit is configured to: determine the context information of the lowest priority IoT user terminal by traversing the priority of all suspended IoT user terminals, and clear the context information of the lowest priority IoT user terminal, and traverse All the IoT user terminals that suspend the IoT user terminal are determined, and the IoT user terminal whose suspension time exceeds the preset time limit is determined, and the context of the IoT user terminal whose suspension time exceeds the preset time limit is cleared. information.

Images