CN108307548B - Method for managing cluster communication system resource - Google Patents
Method for managing cluster communication system resource Download PDFInfo
- Publication number
- CN108307548B CN108307548B CN201610818468.0A CN201610818468A CN108307548B CN 108307548 B CN108307548 B CN 108307548B CN 201610818468 A CN201610818468 A CN 201610818468A CN 108307548 B CN108307548 B CN 108307548B
- Authority
- CN
- China
- Prior art keywords
- cluster
- target
- base station
- trunking
- terminal
- 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
Images
Abstract
The invention discloses a method for managing cluster communication system resources, which comprises the following steps: after modifying a target trunking terminal ID corresponding to a target trunking base station ID in a pre-established trunking context, a trunking core network determines whether the target trunking base station ID corresponds to at least one trunking terminal ID; and the cluster core network starts timing after determining that the target cluster base station ID does not correspond to at least one cluster terminal ID, and sends a cluster context release message to the target cluster base station after the timing duration reaches a preset threshold, so that the target cluster base station releases downlink cluster wireless access bearer resources after receiving the cluster context release message. Compared with the prior art, the invention can release the cluster group context of the single target cluster base station after determining that no cluster terminal exists under the target cluster base station by pre-establishing the cluster group context, thereby enabling the target cluster base station to release the cluster resources.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a method for managing cluster communication system resources.
Background
With the development of communication technology, a cluster communication system, hereinafter referred to as a cluster, has emerged. The cluster is an economic and flexible command and dispatch communication system developed in recent years, and is widely applied to units such as government organs, energy traffic, airport terminals, industrial and mining enterprises, fire-fighting policemen, water conservancy, military and the like so as to meet the requirement of internal communication and contact of each unit.
The trunking function is that trunking channels used by trunking groups are added on the basis of an LTE public network, the added trunking channels are all point-to-multipoint downlink channels, and trunking channel sharing is performed by trunking group members. The trunking base station sends trunking signaling or service data through a trunking channel, and trunking group members monitor the trunking channel and receive data, but unlike the LTE public network, a trunking terminal in an IDLE state (RRC _ IDLE) of radio resource control can receive data by monitoring the trunking channel.
The Group call service is the most basic service provided by a cluster, and each cluster Group includes a cluster Group ID (TGID) and a Group call Area, where the Group call Area is defined as a cluster cell and is also called Tracking Area (TA). Trunking terminals (trunking terminals, i.e. terminals in a trunking wireless communication system) belonging to the same trunking group share one downlink channel, and a group call service shares a signaling service or a data service to trunking terminals in all cells under the same TA through a point-to-multipoint channel. If a TA includes a plurality of trunking base stations (trunking base stations, i.e., base stations in a trunking wireless communication system), and each trunking base station has a trunking terminal, each cell corresponding to each trunking base station needs to establish a trunking service channel. Fig. 1 shows a schematic diagram of a trunking service scenario, and in fig. 1, a trunking terminal 2, a trunking terminal 3, and a trunking terminal 4 belong to the same trunking group; the cell 1, the cell 2 and the cell 3 belong to the same TA, and the TA comprises two trunking base stations, namely a trunking base station A and a trunking base station B; the TPCCH (Trunking Paging Control Channel), TTCH (Trunking traffic Channel), and TCCH (Trunking Control Channel) belong to downlink shared channels of the Trunking group in different cells of the same TA.
The TPCCH is a downlink channel of a cluster dedicated point-to-multipoint mode and is used for transmitting paging messages of cluster group calling and single calling. The TTCH is a downlink traffic channel of a point-to-multipoint mode shared by members in the cluster group, and is mapped to a transmission channel: downlink Shared Channel (Downlink Shared Channel DL-SCH), which is further mapped to a physical Channel: the physical downlink shared channel PDSCH. The TCCH is a downlink channel of a point-to-multipoint mode for transmitting control information by members in the cluster group, and is mapped to a transmission channel: DL-SCH, in turn mapped to physical channel: and a PDSCH.
The trunking terminal under the IDLE state (RRC _ IDLE) of radio resource control, called non-speaking right user or called user, has the right to release the group call service, and the specific flow is as follows from step 1 to step 12:
cluster terminals in idle state, e.g. UEbTriggering group call service release process, UEbThe RRC connection establishment procedure needs to be performed first to enter a connected state (RRC _ CONNECT).
Step 1: UE (user Equipment)bSending a Non-Access Stratum (NAS) direct transmission message to a cluster base station b where the NAS direct transmission message is located, wherein the NAS direct transmission message carries a group call service release request;
step 2: the cluster base station b transmits the group calling service release request to the cluster core network;
and step 3: cluster core network to UEbUser information of the UE is verified to confirm the UEbThe method comprises the steps that a group calling service release authority exists, and group calling service release is determined to be executed;
and 4, step 4: cluster core network to UEbSending downlink NAS message and replying UEbThe group calling service releases the response;
and 5: if the UEaHaving the right to speak, i.e. UEaIn a radio resource controlled connected state (RRC _ CONNECT), the UEaAlso called as the calling user who initiates the group call service, optionally, the cluster core network sends the UEaSending a downlink NAS direct transmission message, and executing a group calling service release process;
step 6, optional, if the UEaAfter receiving the downlink NAS direct transmission message sent by the cluster core network, the UEaAnd sending a group calling service release response to the cluster core network through the uplink NAS direct transmission message.
And 7: cluster core network to UEaAnd UEbSending a downlink NAS direct transfer message, wherein the NAS direct transfer message carries a group calling service release reason;
and 8: UE (user Equipment)aExecuting a special bearer release process with a cluster core network;
and step 9: cluster core network to UEaThe cluster base station a and the UE are locatedbThe cluster base station b sends a group call context release message;
step 10: the cluster base station a and the cluster base station b respectively transmit to the UEaAnd UEbSending RRC layer group calling service release information;
step 11: the cluster base station a and the cluster base station b carry out a group calling resource releasing process;
step 12: and the cluster base station a and the cluster base station b send a group calling context release response to the cluster core network.
In the above process, the group call service release process initiated by the cluster core network starts from step 7, and includes steps 7-12; if there is a user in the current group call service having the right of speaking, e.g. UEaThen steps 5 and 6 are also included.
If the trunking core network triggers the group call service release by taking the speaking right idle time as a condition, the trunking core network needs to set an initiating speaking right idle timer after a speaking right user releases the speaking right, and if a non-speaking right user obtains the speaking right during the running period of the speaking right idle timer, the timer is set to zero; once the timing duration of the talk right idle timer reaches the threshold, the cluster core network triggers the group call release process.
A Trunking Mobility Session management Entity (TMSE) in the Trunking core network sends a Trunking Group Context Release message (trunk Context Release Command) to a Trunking base station a and a Trunking base station b, where the Group call Context Release message is a request for the base station to Release a Context (Context) of a Trunking Group member. The group call context release message cannot be used for a single user. Members under the same cluster Group may be located under multiple base stations, and the TMSE must manage the relationship between one TMSE sounding Group S1AP ID and multiple eNB sounding Group S1AP IDs. The TMSE must release the group call user context under each base station separately.
As can be seen from fig. 1, when there is a group call service, it is necessary to establish TPCCH, TTCH, and TCCH for all cells to complete the trunking signaling and service scheduling. However, for the release of the TPCCH, the TTCH and the TCCH, the TPCCH, the TTCH and the TCCH are released only when the whole trunking service is released.
On the basis of fig. 1, a trunking service scenario as shown in fig. 2 is further given, and when there is trunking service, if a trunking terminal 1 moves to a cell 2 corresponding to a trunking base station a, then there is no trunking terminal under a cell 3 corresponding to a source base station (i.e., a trunking base station B) of the trunking terminal 1. However, the trunking base station B also periodically transmits trunking paging messages through the TPCCH and periodically transmits trunking data through the TCCH, which causes serious waste of resources.
There are two ways (1) and (2) for the trunking terminal 1 to move to the trunking base station a, which are as follows:
(1) when the trunking terminal 1 is in an IDLE state (RRC _ IDLE) of radio resource control, the trunking terminal 1 is also called a non-talk right user, and after the trunking terminal 1 establishes an RRC connection with the trunking base station a, the trunking base station a sends an initialization Message (Initial UE Message) to a Mobility Management Entity (MME) of the trunking core network through an S1 interface, where the initialization Message carries a Cell Global Identity (CGI) of a Cell (i.e., Cell 2) where the trunking terminal 1 is currently located, and the CGI includes a base station ID (i.e., an ID of the trunking base station a).
(2) When the trunking terminal 1 is in a radio resource control (RRC _ CONNECT) connected state, the trunking terminal 1 is also called a talk right user, the trunking base station B sends a trunking terminal 1 Handover Request message to the trunking core network, the trunking core network sends a Handover Request message to the trunking base station a, and after the trunking base station a feeds back a Handover Request acknowledgement (Handover Request ACK) message, sends a Handover Command (Handover Command) to the trunking base station B; and then the trunking base station B sends an RRC connection reconfiguration message to the trunking terminal 1, the trunking terminal 1 sends an RRC connection reconfiguration completion message to the trunking base station A based on the RRC connection reconfiguration message, and the trunking base station A sends a Handover notification (Handover notification) message to a trunking core network. The Handover notification message carries a CGI of a cell (i.e., cell 2) where the trunking terminal 1 is currently located, and the CGI includes a base station ID (i.e., an ID of a trunking base station a).
As can be seen from fig. 2, the trunking terminal 1 moves to the cell 2, but the cell 3 still has the trunking channel of the trunking group, and the trunking base station B still sends trunking signaling and trunking data to the cell 3, which causes serious waste of resources.
In summary, in the current trunking network, when there is a trunking service, the trunking base station configures trunking channels and sends trunking signaling and trunking data for all cells of the TA in which the trunking group members are located, and after the trunking group member cell is reselected, there may be a case where the source trunking base station does not have a trunking terminal, but the trunking service is in the range of the TA in which the trunking terminal is located, so that the source trunking base station still sends trunking signaling and trunking data, which greatly wastes wireless resources.
Disclosure of Invention
In view of the above, the present invention proposes a method of managing resources of a trunked communication system that overcomes or at least partially solves the above mentioned problems.
The invention provides a method for managing cluster communication system resources, which comprises the following steps:
after modifying a target trunking terminal ID corresponding to a target trunking base station ID in a pre-established trunking context, a trunking core network determines whether the target trunking base station ID corresponds to at least one trunking terminal ID;
and the cluster core network starts timing after determining that the target cluster base station ID does not correspond to at least one cluster terminal ID, and sends a cluster context release message to the target cluster base station after the timing duration reaches a preset threshold, so that the target cluster base station releases downlink cluster wireless access bearer resources after receiving the cluster context release message.
Optionally, the starting timing includes:
the cluster core network starts a target resource monitoring timer corresponding to the target cluster base station ID so as to enable the target resource monitoring timer to start timing;
after the starting of the timing, the method further comprises the following steps:
and when the cluster core network modifies the pre-established cluster context, if the cluster terminal ID corresponding to the target cluster base station ID is added, the target resource monitoring timer is stopped so as to clear the timing duration of the target resource monitoring timer.
Optionally, the sending a cluster group context release message to the target cluster base station, so that the target cluster base station releases downlink cluster radio access bearer resources after receiving the cluster group context release message, includes:
reserving the cluster group context, and sending a first cluster group context release message to the target cluster base station, so that the target cluster base station releases downlink cluster radio access bearer resources after receiving the first release message;
or the like, or, alternatively,
and sending a second release message of the cluster context to the target cluster base station, wherein the second release message carries release information of a proprietary base station, so that the target cluster base station releases downlink cluster radio access bearer resources after receiving the second release message.
Optionally, the method further includes a step of modifying, by the trunking core network, a target trunking terminal ID corresponding to the target trunking base station ID in the pre-established trunking context, where the step is specifically as follows:
the cluster core network acquires a target Cell Global Identity (CGI) of a target cluster terminal and a target cluster base station ID contained in the target CGI;
the cluster core network searches whether the target cluster base station ID exists in a pre-established cluster group context;
if not, the cluster core network increases the target cluster base station ID in the cluster group context, and increases the corresponding relation between the target cluster base station ID and the target cluster terminal ID.
Optionally, the acquiring, by the cluster core network, a target cell global identity CGI of a target cluster terminal and a target cluster base station ID included in the target CGI includes:
if the target cluster terminal is in an IDLE state RRC _ IDLE controlled by radio resources, after receiving an initialization message of the target cluster terminal reported by a target cluster base station, the cluster core network extracts a target CGI carried in the initialization message and a target cluster base station ID contained in the target CGI;
and if the target trunking terminal is in a radio resource control connection state RRC _ CONNECT, the trunking core network extracts a target CGI carried in a Handover notification message and a target trunking base station ID contained in the target CGI after receiving the Handover notification message of the target trunking terminal reported by a target trunking base station.
Optionally, if the target cluster base station ID exists in the cluster group context, the cluster core network adds the corresponding relationship between the target cluster base station ID and the target cluster terminal ID in the cluster group context.
Optionally, before the cluster core network searches whether the target cluster base station ID exists from a pre-established cluster group context, the method further includes:
the cluster core network searches whether the target cluster terminal ID exists in a pre-established cluster group context;
and if the target cluster terminal ID does not exist, the cluster core network searches whether the target cluster base station ID exists from a pre-established cluster group context.
Optionally, if the target trunking terminal ID exists in the trunking group context, the trunking core network modifies the trunking base station ID corresponding to the target trunking terminal ID in the trunking group context from the source trunking base station ID to the target trunking base station ID, and deletes the correspondence between the target trunking terminal ID and the source trunking base station ID.
Optionally, the modifying, by the trunking core network, the trunking base station ID corresponding to the target trunking terminal ID in the trunking group context from the source trunking base station ID to the target trunking base station ID, and deleting the correspondence between the target trunking terminal ID and the source trunking base station ID by the trunking core network includes:
the cluster core network searches whether the target cluster base station ID exists in a pre-established cluster group context;
if the target cluster base station ID exists in the cluster group context, the cluster core network takes the cluster base station ID corresponding to the target cluster terminal ID in the cluster group context as the target cluster base station ID, and deletes the corresponding relation between the target cluster terminal ID and the source cluster base station ID.
Optionally, if the target cluster base station ID does not exist in the cluster group context, the cluster core network adds the target cluster base station ID in the cluster group context, adds a correspondence between the target cluster base station ID and the target cluster terminal ID, and deletes the correspondence between the target cluster terminal ID and the source cluster base station ID.
Compared with the prior art, the method for managing the cluster communication system resources, provided by the invention, can release the cluster group context of the single target cluster base station after determining that no cluster terminal exists under the target cluster base station through pre-establishing the cluster group context, so that the target cluster base station releases the cluster resources.
Drawings
FIG. 1 is a diagram illustrating a cluster service scenario in the prior art;
FIG. 2 is a diagram illustrating a cluster service scenario in the prior art;
fig. 3 is a flowchart of a method for managing resources of a trunking communication system according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some embodiments, but not all embodiments, of the present invention.
It should be noted that, in this document, "first" and "second" are used only to distinguish the same names, and do not imply a relationship or order between the names.
As shown in fig. 1, the present embodiment discloses a method for managing resources of a trunking communication system, which may include the following steps 301 and 302:
301. after modifying a target trunking terminal ID corresponding to a target trunking base station ID in a pre-established trunking context, a trunking core network determines whether the target trunking base station ID corresponds to at least one trunking terminal ID.
In this embodiment, the cluster group context may be established in advance in a mobility management entity MME of the cluster core network.
In this embodiment, the cluster group context includes the following information: the cluster group identification TGID, each cluster base station ID corresponding to the TGID and the cluster terminal ID corresponding to each cluster base station ID.
302. After determining that the target cluster base station ID does not correspond to at least one cluster terminal ID, the cluster core network starts timing, and sends a cluster context release message to the target cluster base station after the timing duration reaches a preset threshold, so that the target cluster base station releases a downlink cluster Radio Bearer Resource (Radio Bearer Resource) after receiving the cluster context release message.
In this embodiment, the preset threshold may be set according to an actual situation.
Compared with the prior art, the method for managing the cluster communication system resources provided by this embodiment may release the cluster context of the single target cluster base station after determining that there is no cluster terminal under the target cluster base station by pre-establishing the cluster context, so that the target cluster base station releases the cluster resources.
Further, in this embodiment, a cluster group context is established on an MME of a cluster core network, a cluster base station is used as a unit to manage cluster terminals in the cluster group context, when the cluster terminals in the cluster group have no cluster terminals under a source cluster base station due to mobility, the source cluster base station is notified to release a cluster channel, and in order to prevent ping-pong movement, the cluster core network starts timing, and after a timing duration reaches a preset threshold, a cluster resource release flow is started, and after receiving a release signaling, the cluster base station releases the cluster channel, thereby effectively saving wireless resources.
In one specific example, the starting of the timing in step 302 includes:
the cluster core network starts a target resource monitoring timer corresponding to the target cluster base station ID so as to enable the target resource monitoring timer to start timing;
after the starting of the timing, the method further comprises the following steps:
and when the cluster core network modifies the pre-established cluster context, if the cluster terminal ID corresponding to the target cluster base station ID is added, the target resource monitoring timer is stopped so as to clear the timing duration of the target resource monitoring timer.
In this embodiment, the cluster context further includes the following information: and a resource monitoring timer corresponding to each cluster base station ID. The resource monitoring timer may be configurable through the network management.
In this embodiment, the cluster core network starts the resource monitoring timer, starts the cluster resource release process after the resource monitoring timer expires, and releases the cluster channel after the cluster base station receives the release signaling, thereby effectively saving the wireless resources.
In a specific example, the sending, in step 302, a cluster group context release message to the target cluster base station, so that the target cluster base station releases downlink cluster radio access bearer resources after receiving the cluster group context release message, includes:
reserving the cluster group context, and sending a first cluster group context release message to the target cluster base station, so that the target cluster base station releases downlink cluster radio access bearer resources after receiving the first release message;
or the like, or, alternatively,
and sending a second release message of the cluster context to the target cluster base station, wherein the second release message carries release information of a proprietary base station, so that the target cluster base station releases downlink cluster radio access bearer resources after receiving the second release message.
In this embodiment, due to the mobility of the trunking terminal, when the trunking core network detects that there is no trunking terminal under a certain trunking base station ID, the trunking core network starts a resource monitoring timer corresponding to the trunking base station ID, and after the timer expires, a release process is started, where the release process includes the following two schemes:
placing a first plan: after a resource monitoring timer corresponding to a certain cluster base station ID is overtime, the cluster core network only sends a first release message to the cluster base station to trigger the process that the cluster base station releases the cluster group context, but the cluster core network does not delete the cluster group context, and after the cluster base station receives the first release message, the protocol and the implementation compatibility are good as the existing processing mode.
Scheme II: add optional Information Element (IE) in the cluster context release message: and releasing (Dedicated eNodeB Release) by the special base station to obtain a second Release message. And after the resource monitoring timer corresponding to the ID of a certain cluster base station is overtime, the cluster core network only sends a second release message to the cluster base station, and the cluster base station releases the cluster resources after receiving the second release message but does not inform the UE of releasing the cluster resources.
Therefore, after the trunking terminal of the trunking group moves, under the scene that the source trunking base station has no trunking terminal, the trunking group no longer occupies the radio resource of the cell, and the use of the radio resource of the trunking paging channel TPCCH, the trunking common channel TCCH and the trunking traffic channel TTCH is improved.
The cluster base station where the cluster terminal of a certain cluster group is not located does not perform cluster service, and the load of the single board is reduced.
In a specific example, the method of fig. 3 further includes step 300, not shown in fig. 3: the cluster core network modifies a target cluster terminal ID corresponding to a target cluster base station ID in a pre-established cluster context, and specifically comprises steps 3001-3003:
3001. the cluster core network acquires a target Cell Global Identity (CGI) of a target cluster terminal and a target cluster base station ID contained in the target CGI;
3002. the cluster core network searches whether the target cluster base station ID exists in a pre-established cluster group context; if not, go to step 3003; if yes, go to step 3004;
3003. the cluster core network increases the target cluster base station ID in the cluster group context and increases the corresponding relation between the target cluster base station ID and the target cluster terminal ID;
3004. and the cluster core network increases the corresponding relation between the target cluster base station ID and the target cluster terminal ID in the cluster group context.
In a specific example, the step 3001 of acquiring, by the trunking core network, a target cell global identity CGI of a target trunking terminal and a target trunking base station ID included in the target CGI includes:
if the target trunking terminal is in an IDLE state RRC _ IDLE of radio resource control, after receiving an initialization Message (Initial UE Message) of the target trunking terminal reported by a target trunking base station, the trunking core network extracts a target CGI carried in the initialization Message and a target trunking base station ID included in the target CGI;
and if the target trunking terminal is in a radio resource control connection state RRC _ CONNECT, the trunking core network extracts a target CGI carried in a Handover notification message and a target trunking base station ID contained in the target CGI after receiving the Handover notification message of the target trunking terminal reported by a target trunking base station.
In this embodiment, when a trunking terminal accesses, a trunking core network searches whether there is a trunking base station ID from a pre-established trunking group context according to a CGI carried in a received INITIAL UE MESSAGE of the trunking terminal and extracts an Identifier (ID) of the trunking base station from the CGI, and if not, creates the identifier and stores the trunking terminal ID under the trunking base station ID, and if so, adds the trunking terminal ID under the trunking base station ID. Thus, after the access of the cluster terminal is completed, the cluster group context is established.
In a specific example, before the trunking core network searches whether the target trunking base station ID exists from the pre-established trunking group context in step 3002, the method further includes step 3001' not shown in fig. 3:
3001' said cluster core network searches whether there is said target cluster terminal ID from pre-established cluster group context; if the target cluster terminal ID does not exist, executing step 3002; otherwise, step 3002' not shown in fig. 3 is performed:
3002' the cluster core network modifies the cluster base station ID corresponding to the target cluster terminal ID in the cluster group context from the source cluster base station ID to the target cluster base station ID, and deletes the correspondence between the target cluster terminal ID and the source cluster base station ID.
In a specific example, step 3002' includes: the cluster core network searches whether the target cluster base station ID exists in a pre-established cluster group context; if the target cluster base station ID exists in the cluster group context, the cluster core network takes the cluster base station ID corresponding to the target cluster terminal ID in the cluster group context as the target cluster base station ID, and deletes the corresponding relation between the target cluster terminal ID and the source cluster base station ID. If the target cluster base station ID does not exist in the cluster group context, the cluster core network adds the target cluster base station ID in the cluster group context, adds the corresponding relation between the target cluster base station ID and the target cluster terminal ID, and deletes the corresponding relation between the target cluster terminal ID and the source cluster base station ID.
In this embodiment, if a trunking terminal is in RRC _ IDLE, if a cell change occurs, a Tracking Area Update (TAU) process is triggered according to an existing trunking design, so that an initialization message sent by a trunking base station to a trunking core network carries a CGI (including a trunking base station ID), the trunking core network determines according to the trunking base station ID, if a pre-established trunking group context has the trunking base station ID, the trunking terminal ID is added to the trunking base station ID, if not, the trunking base station ID is created, the trunking terminal ID is searched in the trunking group context, a record of the trunking terminal ID under a source trunking base station ID is deleted, and if only one record exists under the source trunking base station ID, the source trunking base station ID is deleted, and a group call release message of the source trunking base station ID is triggered.
Those skilled in the art will appreciate that although some embodiments described herein include some features included in other embodiments instead of others, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments.
Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope defined by the appended claims.
Claims (10)
1. A method for managing resources of a trunked communication system, comprising:
after modifying a target trunking terminal ID corresponding to a target trunking base station ID in a pre-established trunking context, a trunking core network determines whether the target trunking base station ID corresponds to at least one trunking terminal ID; the cluster group context contains the following information: cluster group identification TGID, each cluster base station ID corresponding to the TGID and cluster terminal ID corresponding to each cluster base station ID;
and the cluster core network starts timing after determining that the target cluster base station ID does not correspond to at least one cluster terminal ID, and sends a cluster context release message to the target cluster base station after the timing duration reaches a preset threshold, so that the target cluster base station releases downlink cluster wireless access bearer resources after receiving the cluster context release message.
2. The method of claim 1, wherein the starting timing comprises:
the cluster core network starts a target resource monitoring timer corresponding to the target cluster base station ID so as to enable the target resource monitoring timer to start timing;
after the starting of the timing, the method further comprises the following steps:
and when the cluster core network modifies the pre-established cluster context, if the cluster terminal ID corresponding to the target cluster base station ID is added, the target resource monitoring timer is stopped so as to clear the timing duration of the target resource monitoring timer.
3. The method of claim 1, wherein the sending a cluster group context release message to the target cluster base station to enable the target cluster base station to release downlink cluster radio access bearer resources after receiving the cluster group context release message comprises:
reserving the cluster group context, and sending a first cluster group context release message to the target cluster base station, so that the target cluster base station releases downlink cluster radio access bearer resources after receiving the first release message;
or the like, or, alternatively,
and sending a second release message of the cluster context to the target cluster base station, wherein the second release message carries release information of a proprietary base station, so that the target cluster base station releases downlink cluster radio access bearer resources after receiving the second release message.
4. The method according to claim 1, wherein the method further comprises a step of modifying, by the trunking core network, a target trunking terminal ID corresponding to a target trunking base station ID in a pre-established trunking context, specifically as follows:
the cluster core network acquires a target Cell Global Identity (CGI) of a target cluster terminal and a target cluster base station ID contained in the target CGI;
the cluster core network searches whether the target cluster base station ID exists in a pre-established cluster group context;
if not, the cluster core network increases the target cluster base station ID in the cluster group context, and increases the corresponding relation between the target cluster base station ID and the target cluster terminal ID.
5. The method according to claim 4, wherein the acquiring, by the cluster core network, a target Cell Global Identity (CGI) of a target cluster terminal and a target cluster base station ID included in the target CGI includes:
if the target cluster terminal is in an IDLE state RRC _ IDLE controlled by radio resources, after receiving an initialization message of the target cluster terminal reported by a target cluster base station, the cluster core network extracts a target CGI carried in the initialization message and a target cluster base station ID contained in the target CGI;
and if the target trunking terminal is in a radio resource control connection state RRC _ CONNECT, the trunking core network extracts a target CGI carried in a Handover notification message and a target trunking base station ID contained in the target CGI after receiving the Handover notification message of the target trunking terminal reported by a target trunking base station.
6. The method according to claim 4, wherein if the target cluster base station ID exists in the cluster group context, the cluster core network adds the correspondence between the target cluster base station ID and the target cluster terminal ID in the cluster group context.
7. The method of claim 4, wherein before the clustered core network looking up whether the target clustered base station ID exists from a pre-established clustered group context, the method further comprises:
the cluster core network searches whether the target cluster terminal ID exists in a pre-established cluster group context;
and if the target cluster terminal ID does not exist, the cluster core network searches whether the target cluster base station ID exists from a pre-established cluster group context.
8. The method according to claim 7, wherein if the target trunking terminal ID exists in the trunking group context, the trunking core network modifies a trunking base station ID corresponding to the target trunking terminal ID in the trunking group context from a source trunking base station ID to the target trunking base station ID, and deletes a correspondence between the target trunking terminal ID and the source trunking base station ID.
9. The method of claim 8, wherein the cluster core network modifies a cluster base station ID corresponding to the target cluster terminal ID in the cluster group context from a source cluster base station ID to the target cluster base station ID, and deletes a correspondence between the target cluster terminal ID and the source cluster base station ID, and the method comprises:
the cluster core network searches whether the target cluster base station ID exists in a pre-established cluster group context;
if the target cluster base station ID exists in the cluster group context, the cluster core network takes the cluster base station ID corresponding to the target cluster terminal ID in the cluster group context as the target cluster base station ID, and deletes the corresponding relation between the target cluster terminal ID and the source cluster base station ID.
10. The method according to claim 9, wherein if the target cluster base station ID does not exist in the cluster group context, the cluster core network adds the target cluster base station ID, adds the correspondence between the target cluster base station ID and the target cluster terminal ID, and deletes the correspondence between the target cluster terminal ID and the source cluster base station ID in the cluster group context.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610818468.0A CN108307548B (en) | 2016-09-12 | 2016-09-12 | Method for managing cluster communication system resource |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610818468.0A CN108307548B (en) | 2016-09-12 | 2016-09-12 | Method for managing cluster communication system resource |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108307548A CN108307548A (en) | 2018-07-20 |
| CN108307548B true CN108307548B (en) | 2020-12-01 |
Family
ID=62871848
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610818468.0A Active CN108307548B (en) | 2016-09-12 | 2016-09-12 | Method for managing cluster communication system resource |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108307548B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111757279B (en) * | 2020-06-24 | 2022-06-24 | 海能达通信股份有限公司 | Method, system and related equipment for reducing switching time delay of LTE broadband trunking system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101106762A (en) * | 2006-11-17 | 2008-01-16 | 中兴通讯股份有限公司 | A method for periodical release of idle calls in digital cluster system |
| CN102137331A (en) * | 2010-01-22 | 2011-07-27 | 普天信息技术研究院有限公司 | Method for determining and regulating group calling region information |
| CN102149048A (en) * | 2011-03-29 | 2011-08-10 | 海能达通信股份有限公司 | User management method and calling method of cluster system as well as terminal |
| CN103581837A (en) * | 2012-08-08 | 2014-02-12 | 成都鼎桥通信技术有限公司 | Resource allocation method and resource deletion method and device |
-
2016
- 2016-09-12 CN CN201610818468.0A patent/CN108307548B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101106762A (en) * | 2006-11-17 | 2008-01-16 | 中兴通讯股份有限公司 | A method for periodical release of idle calls in digital cluster system |
| CN102137331A (en) * | 2010-01-22 | 2011-07-27 | 普天信息技术研究院有限公司 | Method for determining and regulating group calling region information |
| CN102149048A (en) * | 2011-03-29 | 2011-08-10 | 海能达通信股份有限公司 | User management method and calling method of cluster system as well as terminal |
| CN103581837A (en) * | 2012-08-08 | 2014-02-12 | 成都鼎桥通信技术有限公司 | Resource allocation method and resource deletion method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108307548A (en) | 2018-07-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230180274A1 (en) | Data scheduling method, base station, and system | |
| WO2016123809A1 (en) | Signaling optimization method and device | |
| CN107251642B (en) | User device, base station, and connection establishment method | |
| CN107666691B (en) | Terminal state conversion method and device | |
| US8874112B2 (en) | Service dependent inactivity timer | |
| US10470108B2 (en) | Signal transmission and reception method by remote UE in a wireless communication system and device for same | |
| CN112040567B (en) | Method and device for recovering RRC connection and computer storage medium | |
| KR102264618B1 (en) | Communication method, access network device, and terminal | |
| CN108616822B (en) | Method for reselecting group calling called cell of LTE (Long term evolution) trunking system | |
| CN107113906B (en) | Method and device for releasing Radio Resource Control (RRC) connection | |
| US10462719B2 (en) | Method, device and system for supporting transmission of a group service | |
| WO2017113986A1 (en) | Mobility management method, user equipment, and base station | |
| WO2018127030A1 (en) | Method and device for notification of information about ran-based notification area | |
| CN109417699A (en) | A kind of state switching method and device | |
| CN103733657A (en) | Identification of ue counting results in embms | |
| WO2018228210A1 (en) | Method and device for managing cell, and storage medium | |
| WO2018010583A1 (en) | Network system | |
| CN101925037A (en) | Method and base station for establishing call | |
| EP2809109A1 (en) | Wireless communication system, radio base station, radio terminal, and wireless communication method | |
| CN108307452B (en) | Connection recovery method and device, base station and user terminal | |
| CN108307548B (en) | Method for managing cluster communication system resource | |
| WO2013113240A1 (en) | Method for transmitting rn information, method for paging ue and apparatus thereof | |
| WO2014111057A1 (en) | Broadband cluster communication system, and resource release and establishment method thereof, terminal, and base station | |
| US11140656B2 (en) | Paging in a group communications system | |
| CN105813054B (en) | PAL management method and device, and paging realization method and device |
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 |