Single-cell cluster user management method

Abstract

The invention discloses a single-cell cluster user management method. The method comprises the steps: setting one cluster user list in each cluster cell, wherein the cluster user lists are used for storing the contexts of users in the cell of a cluster; setting one corresponding cell control table for each cluster cell at a network side, wherein the cell control tables are respectively used for storing the head of the cluster user link of the corresponding cluster cell; inserting the context of the user behind a head node in the cluster user link of the corresponding cluster cell when a user enters the cluster cell; judging whether the user is located in the cell where he is ready to leave or not according to the context of the user when the user needs to leave the cluster cell; deleting the context of the user from the cluster user list of the cluster cell if the user is located in the cell where he is ready to leave, or else, ending the flow. The above method can accurately record the number of users in each cluster cell in various types of complex cross scenarios, guarantees the accuracy of the number of the users, and effectively prevents wrong operations from affecting the group business.

Description

technical field [0001] The invention relates to the field of communication technology, in particular to a method for managing cluster users in a single cell. Background technique [0002] In the trunking service, if the number of group users in the group cell is 0, idle mobile resource management needs to be performed, that is, if there is still no user in the cell after a certain period of time, the group resources of the cell will be released. In the prior art, a counter is generally assigned to each group cell to record the current group user number of the group cell. When a user enters the cell, the counter is incremented by one; when a user leaves the cell, the counter minus one. The life cycle of the number of group users is consistent with the life cycle of the group resources of the cell to which they belong, that is, the counter is maintained when the group resource is created, and the counter is cleared when the group resource is released. [0003] In the prior a...

AI Technical Summary

Problems solved by technology

However, there will be a problem with the above method: if a user UE1 is handed over from cell a to cell b, the group resources under cell b are due to user plane error, cell deactivation, base station inactivity timer timeout, etc. is released, the counter of cell b is cleared; immediately, another user UE2 joins this group under cell b, and at this time, the group resource of cell b will be built immediately and the actual number of users under the current cell will be counted. Since the handover of UE1 has not been completed at this time, UE1 is still under cell a and will not be counted under cell b, so the number of users under cell b will only record UE2 at this time, that is, the reading of the timer is 1

If the handover operation of UE1 fails in the subsequent process, then according to the handover method in the prior art, the counter under cell b will be decremented by one, so the number of users in this cell b will be 0, and because of idle mobile resource management Release the group resources of the cell b, causing UE2 to fail to monitor normally

[0004] According to the above situation, it can be seen that in some crossover scenarios, the user who triggers the decrement of the counter of the cell may not be counted in the counter, and the counter itself cannot identify and protect this scenario, resulting in group services being affected. negative effect

[0005] In addition, in the prior art solutions, the operation of the counter is very frequent, and the addition and subtraction of the counter is strongly coupled with the specific process. Therefore, if each addition and subtraction operation of the counter is to be correct and the counting of the counter is accurate, it is necessary to analyze the related scenarios. Sort out one by one to ensure that there is no repeated addition and subtraction, and that there are no omissions and no conflicts in the scene. Therefore, the technical difficulty of implementation is relatively high; and when adding new scenes, various scenes need to be reorganized, which brings repeated work, so the development labor cost is very high. High, resulting in waste of labor costs, and low scalability

[0006] In addition, since there is only one counter in each group cell in the prior art to indicate the current number of group users, the amount of information is too small to obtain user real-name information, so it is impossible to query which users are in a certain cell, and it is also impossible to quickly Query which group cell a user is currently in, which cannot meet the maintenance and testing requirements

Images