CN106162719B - For the users consistency detection method and system in LTE system - Google Patents

For the users consistency detection method and system in LTE system Download PDF

Info

Publication number
CN106162719B
CN106162719B CN201610859373.3A CN201610859373A CN106162719B CN 106162719 B CN106162719 B CN 106162719B CN 201610859373 A CN201610859373 A CN 201610859373A CN 106162719 B CN106162719 B CN 106162719B
Authority
CN
China
Prior art keywords
user
list
mac
present
rlc
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201610859373.3A
Other languages
Chinese (zh)
Other versions
CN106162719A (en
Inventor
张艳欢
田宇兴
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CICT Mobile Communication Technology Co Ltd
Original Assignee
Wuhan Hongxin Telecommunication Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Wuhan Hongxin Telecommunication Technologies Co Ltd filed Critical Wuhan Hongxin Telecommunication Technologies Co Ltd
Priority to CN201610859373.3A priority Critical patent/CN106162719B/en
Publication of CN106162719A publication Critical patent/CN106162719A/en
Application granted granted Critical
Publication of CN106162719B publication Critical patent/CN106162719B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition

Abstract

The present invention provides a kind of users consistency detection method and system in LTE system, whether the user that L3 starting periodical timer detects each interlayer of L3 and PDCP/RLC/MAC respectively is consistent, interlayer user is carried out to inconsistent user and deletes release processing, whether MAC starts periodical timer has business to carry out User Status detection according to user, for the reporting of user in Idle state to L3, complete user is carried out to each layer in base station and user terminal and deletes release processing.The present invention carries out the users consistency detection between each layer of base station side by starting periodical timer timing, User Status detection is carried out in conjunction with counting user portfolio, user between each layer of base station side L3 and PDCP/RLC/MAC is inconsistent and corpse customer problem solving, and avoids the wasting of resources and influences the process and business of other normal users.

Description

For the users consistency detection method and system in LTE system
Technical field
The present invention relates to one of mobile communication field LTE (Long Term Evolution, long term evolution) system use The improved technology scheme of family consistency detection.
Background technique
In LTE system, base station side protocol stack include RRC (Radio Resource Control, wireless resource management), PDCP (Packet Data Convergence Protocol, Packet Data Convergence Protocol), RLC (Radio Link Control, wireless spread-spectrum technology), MAC (Media Accesss Contol, media access control), that is, LTE system is real L3/L2 in existing, L3 (layer 3) realize the function of RRC radio resource control layer, and L2 (layer 2) includes PDCP/RLC/MAC three parts Function.All it is standalone module between each layer, there is respective resource management and memory headroom.Theoretically, the user of each layer needs Consistency is maintained, i.e., the number of users of each layer and the unique identifier of each user will fit like a glove, and otherwise will cause resource Waste and hang dead, influence the access and operation flow of other normal users, or even cause entire base station side system can not be normal Operation.
Summary of the invention
The purpose of the present invention is to overcome the shortcomings of the existing technology, provides a kind of improved technology scheme of users consistency, It is real for solving the problems, such as that the wasting of resources caused by each interlayer user of base station side L3 and PDCP/RLC/MAC is inconsistent and resource extension are dead Now each interlayer number of users and identifier are completely the same, eliminate corpse user to the access of other normal users and the shadow of business It rings.
Technical solution of the present invention provides a kind of users consistency detection method in LTE system, and L3 starts the period Property timer detect respectively each interlayer of L3 and PDCP/RLC/MAC user it is whether consistent, interlayer use is carried out to inconsistent user Release processing is deleted at family, and whether MAC starts periodical timer has business to carry out User Status detection according to user, for being in The reporting of user of Idle state carries out complete user to each layer in base station and user terminal and deletes release processing to L3;
Implementation includes executing following operation in a base station,
When cell is established, L3 successively starts 3 periodical timers, including successively starts L3 and PDCP periodically timing Device, L3 and RLC periodical timer, L3 and MAC cycle timer;It includes being used for that MAC starts 2 periodical timers simultaneously The periodical timer of sleep state judgement, is denoted as MAC cycle timer 1, for judging the periodical timer of Idle state, remembers For MAC cycle timer 2;
After L3 and PDCP periodical timer are overtime, users consistency detection is carried out, if there is inconsistent user, L3 It issues user and deletes message to PDCP;After L3 and RLC periodical timer are overtime, users consistency detection is carried out, if there is Inconsistent user, L3 issue user and delete message to RLC;L3 carries out users consistency with after MAC cycle timer expiry Detection, if there is inconsistent user, L3 issues user and deletes message to MAC;
The detection of MAC User Status, including the portfolio that user in the measurement period time is transmitted, when user is activated state, etc. To 1 time-out of MAC cycle timer, if there is user is set to activated state by business, if user is set to sleep state without business; When user is sleep state, waiting MAC cycle timer 2 is overtime, if there is user is set to activated state by business, if without business User is set to Idle state;User Status result is reported to L3;After L3 receives reporting message, in Idle state user into The complete UE of row deletes process.
Moreover, carrying out users consistency detection, including use following son after the L3 and PDCP periodical timer time-out Step,
Step 201, when L3 and PDCP periodical timer time-out, L3 issue user query message to PDCP;
Step 202, after PDCP receives user query message, PDCP local user list is traversed, by all N number of customer instances RNTI be reported to L3, when no customer instance, reports N=0;
Step 203, after L3 receives PDCP reporting message, the user list that L3 local user list and PDCP are reported is carried out It compares;
If entering step 204 in the user list that certain user is present in L3 local user list and PDCP is reported;
If certain user is present in L3 local user list but is not present in the user list that PDCP is reported, enter step 205;
If certain user is present in the list of PDCP report of user but is not present in L3 local user's list, 206 are entered step;
Step 204, due in certain user is present in L3 local user list and PDCP is reported user list, then not locating Reason, terminates this process;
Step 205, since certain user is present in L3 local user list but is not present in the user list that PDCP reports, then L3 issues complete UE and deletes process, terminates this process;
Step 206, since certain user is present in the list of PDCP report of user but is not present in L3 local user's list, then L3 It only issues user and deletes after message receives message to PDCP, PDCP and discharge the user resources, terminate this process.
Moreover, carrying out users consistency detection, including use following son after the L3 and RLC periodical timer time-out Step,
Step 301, when L3 and RLC periodical timer time-out, L3 issue user query message to RLC;
Step 302, after RLC receives user query message, RLC local user list is traversed, by all M customer instances RNTI is reported to L3, and when no customer instance reports M=0;
Step 303, after L3 receives RLC reporting message, the user list that L3 local user list and RLC are reported compares It is right;
If entering step 304 in the user list that certain user is present in L3 local user list and RLC is reported;
If certain user is present in L3 local user list but is not present in the user list that RLC is reported, enter step 305;
If certain user is present in the list of RLC report of user but is not present in L3 local user's list, 306 are entered step;
Step 304, due in certain user is present in L3 local user list and RLC is reported user list, then not handling, Terminate this process;
Step 305, since certain user is present in L3 local user list but is not present in the user list that RLC reports, then L3 issues complete UE and deletes process, terminates this process;
Step 306, since certain user is present in the list of RLC report of user but is not present in L3 local user's list, then L3 It only issues user and deletes after message receives message to RLC, RLC and discharge the user resources, terminate this process.
Moreover, carrying out users consistency detection, including middle using following after the L3 and MAC cycle timer expiry Sub-step,
Step 401, when L3 and MAC cycle timer expiry, L3 issue user query message to MAC;
Step 402, after MAC receives user query message, MAC local user list is traversed, by all P customer instances RNTI is reported to L3, and when no customer instance reports P=0;
Step 403, after L3 receives MAC reporting message, the user list that L3 local user list and MAC are reported compares It is right;
If entering step 404 in the user list that certain user is present in L3 local user list and MAC is reported;
If certain user is present in L3 local user list but is not present in the user list that MAC is reported, enter step 405;
If certain user is present in the list of MAC report of user but is not present in L3 local user's list, 406 are entered step;
Step 404, due in certain user is present in L3 local user list and MAC is reported user list, then not handling, Terminate this process;
Step 405, since certain user is present in L3 local user list but is not present in the user list that MAC reports, then L3 issues complete UE and deletes process, terminates this process;
Step 406, since certain user is present in the list of MAC report of user but is not present in L3 local user's list, then L3 It only issues user and deletes after message receives message to MAC, MAC and discharge the user resources, terminate this process.
Moreover, the MAC User Status detection, including following sub-step is used,
Step 501, the portfolio that user is transmitted in the MAC measurement period time;
Step 502, when user is activated state, waiting MAC cycle timer 1 is overtime, if timer duration is T minutes; If there is user is set to activated state by business, if user is set to sleep state without business, subsequently into step 504;
Step 503, when user is sleep state, waiting MAC cycle timer 2 is overtime, if timer duration is S minutes, S >T;If there is user is set to activated state by business, if user is set to Idle state without business, subsequently into step 504;
Step 504, step 502 and 503 gained User Status results are reported to L3;
Step 505, after L3 receives reporting message, the user in Idle state is subjected to complete UE and deletes process.
The present invention also provides a kind of users consistency detection systems in LTE system, for being started periodically by L3 Whether the user that timer detects each interlayer of L3 and PDCP/RLC/MAC respectively is consistent, carries out interlayer user to inconsistent user Release processing is deleted, whether MAC starts periodical timer has business to carry out User Status detection according to user, in sky The reporting of user of not busy state carries out complete user to each layer in base station and user terminal and deletes release processing to L3;
Including being arranged in a base station with lower module,
First module, when establishing for cell, L3 successively starts 3 periodical timers, including successively start L3 with PDCP periodical timer, L3 and RLC periodical timer, L3 and MAC cycle timer;MAC starts 2 periodicity simultaneously Timer includes the periodical timer for sleep state judgement, MAC cycle timer 1 is denoted as, for judging Idle state Periodical timer is denoted as MAC cycle timer 2;
Second module carries out users consistency detection, if there is not after L3 and PDCP periodical timer time-out Consistent user, L3 issue user and delete message to PDCP;
Third module carries out users consistency detection, if there is not after L3 and RLC periodical timer time-out Consistent user, L3 issue user and delete message to RLC;
4th module carries out users consistency detection, if there is not after L3 and MAC cycle timer expiry Consistent user, L3 issue user and delete message to MAC;
5th module when user is activated state, waits MAC for the portfolio that user in the MAC measurement period time is transmitted 1 time-out of periodical timer, if there is user is set to activated state by business, if user is set to sleep state without business;When with Family is sleep state, MAC cycle timer 2 time-out is waited, if there is user is set to activated state by business, if will use without business Family is set to Idle state;User Status result is reported to L3;After L3 receives reporting message, the user in Idle state has been carried out Whole UE deletes process.
Moreover, include in the second module with lower unit,
Unit M201, for issuing user query message to PDCP as L3 and PDCP periodical timer time-out, L3;
Unit M202 after receiving user query message for PDCP, traverses PDCP local user list, by all N number of use The RNTI of family example is reported to L3, and when no customer instance reports N=0;
Unit M203, after receiving PDCP reporting message for L3, the user that L3 local user list and PDCP are reported is arranged Table is compared;
In the user list that if certain user is present in L3 local user list and PDCP is reported, order unit M204 work Make;
If certain user is present in L3 local user list but is not present in the user list that PDCP is reported, order unit M205 work;
If certain user is present in the list of PDCP report of user but is not present in L3 local user's list, order unit M206 Work;
Unit M204, due in certain user is present in L3 local user list and PDCP is reported user list, then not locating Reason terminates the work of this module;
Unit M205, since certain user is present in L3 local user list but is not present in the user list that PDCP reports, Then L3 issues complete UE and deletes process, terminates the work of this module;
Unit M206, since certain user is present in the list of PDCP report of user but is not present in L3 local user's list, then L3, which only issues user and deletes after message receives message to PDCP, PDCP, discharges the user resources, terminates the work of this module.
Moreover, include in third module with lower unit,
Unit M301, for issuing user query message to RLC as L3 and RLC periodical timer time-out, L3;
Unit M302 after receiving user query message for RLC, traverses RLC local user list, by all M users The RNTI of example is reported to L3, and when no customer instance reports M=0;
Unit M303, after receiving RLC reporting message for L3, user list that L3 local user list and RLC are reported It is compared;
In the user list that if certain user is present in L3 local user list and RLC is reported, order unit M304 work;
If certain user is present in L3 local user list but is not present in the user list that RLC is reported, order unit M305 work;
If certain user is present in the list of RLC report of user but is not present in L3 local user's list, order unit M306 Work;
Unit M304, due in certain user is present in L3 local user list and RLC is reported user list, then not locating Reason terminates the work of this module;
Unit M305, since certain user is present in L3 local user list but is not present in the user list that RLC reports, then L3 issues complete UE and deletes process, terminates the work of this module;
Unit M306, since certain user is present in the list of RLC report of user but is not present in L3 local user's list, then L3 It only issues user and deletes after message receives message to RLC, RLC and discharge the user resources, terminate the work of this module.
Moreover, include in the 4th module with lower unit,
Unit M401, for when L3 and MAC cycle timer expiry, L3 to issue user query message to MAC;
Unit M402 after receiving user query message for MAC, traverses MAC local user list, by all P users The RNTI of example is reported to L3, and when no customer instance reports P=0;
Unit M403, after receiving MAC reporting message for L3, user list that L3 local user list and MAC are reported It is compared;
In the user list that if certain user is present in L3 local user list and MAC is reported, order unit M404 work;
If certain user is present in L3 local user list but is not present in the user list that MAC is reported, order unit M405 work;
If certain user is present in the list of MAC report of user but is not present in L3 local user's list, order unit M406 Work;
Unit M404, due in certain user is present in L3 local user list and MAC is reported user list, then not locating Reason terminates the work of this module;
Unit M405, since certain user is present in L3 local user list but is not present in the user list that MAC reports, then L3 issues complete UE and deletes process, terminates the work of this module;
Unit M406, since certain user is present in the list of MAC report of user but is not present in L3 local user's list, then L3 It only issues user and deletes after message receives message to MAC, MAC and discharge the user resources, terminate the work of this module.
Moreover, include in the 5th module with lower unit,
Unit M501, the portfolio transmitted for user in the MAC measurement period time;
Unit M502 waits 1 time-out of MAC cycle timer, if timer duration is T for being activated state as user Minute;If there is user is set to activated state by business, if user is set to sleep state without business, then order unit M504 work Make;
Unit M503 waits MAC cycle timer 2 time-out, if timer duration is S for being sleep state as user Minute, S > T;
If there is user is set to activated state by business, if user is set to Idle state without business, then order unit M504 work;
Unit M504, for unit M502 and 503 gained User Status results to be reported to L3;
User in Idle state after receiving reporting message for L3, is carried out complete UE and deletes process by unit M505.
The prior art is compared, the present invention provides a kind of users consistency detection technique schemes, to solve base station side agreement The wasting of resources and resource caused by each layer user of stack is inconsistent hang dead problem, eliminate corpse user to the access of other normal users and The influence of operation flow, it is ensured that the normal operation of entire base station system.Beneficial features of the invention are as follows:
1), the users consistency detection method starts the method for the individual periodical timer of each interlayer using L3, timing It goes to inquire and compare each layer user information, by L3 as master control, it is consistent that each layer separate single one reaches user therewith, to realize base Standing, each interlayer user is completely the same, and scheme is simple, and realization is easier, and clear thinking, interactivity is strong, do not influence existing procedure and Business.
2), the users consistency detection method, solves defect of the existing technology, eliminates between each standalone module The wasting of resources caused by user is inconsistent and resource hang dead problem, the especially influence to other normal users access and business, The whole system even resulted in can not operation the problem of, have practical value.
Detailed description of the invention
Fig. 1 is flow chart of the embodiment of the present invention.
Fig. 2 is L3 of the embodiment of the present invention and PDCP users consistency detects detail flowchart.
Fig. 3 is L3 of the embodiment of the present invention and RLC users consistency detects detail flowchart.
Fig. 4 is L3 of the embodiment of the present invention and MAC users consistency detects detail flowchart.
Fig. 5 is that MAC of embodiment of the present invention User Status detects detail flowchart.
Specific embodiment
Below by specific embodiment combination attached drawing, invention is further described in detail.
The present invention detects the user of each interlayer of L3 and PDCP/RLC/MAC by starting periodical timer by L3 respectively It is no consistent, interlayer user is carried out to inconsistent user and deletes release processing, MAC start periodical timer according to user whether There is business to carry out User Status detection, for the reporting of user in Idle state to L3, each layer in base station and user terminal are carried out Completely user deletes release processing, solves base station side L3 and the inconsistent caused resource wave of each interlayer user of PDCP/RLC/MAC Take and resource hangs dead problem.
Referring to attached drawing 1, embodiment institute providing method is comprised the steps of:
101) when cell is established, L3 successively starts 3 periodical timers, including successively starts L3 and PDCP and periodically determine When device, L3 and RLC periodical timer, L3 and MAC cycle timer (timer duration suggests 1~5 minute, default 3 it is fixed When device all value 3 minutes, 3 timers starting time intervals are also 3 minutes), periodicity of the MAC starting for Idle state judgement Timer;Further, one can also be arranged for judging the periodical timer of sleep state;
In embodiment, MAC starts 2 periodical timers (timer duration is suggested 1~30 minute) simultaneously, including is used for The periodical timer of sleep state judgement, is denoted as MAC cycle timer 1, for judging the periodical timer of Idle state, remembers For MAC cycle timer 2;
After starting L3 and PDCP periodical timer, MAC cycle timer 1, MAC cycle timer 2, enter simultaneously 102) and 105);
102) after L3 and PDCP periodical timer are overtime, users consistency detection is carried out, if there is inconsistent use Family, L3 issue user and delete message to PDCP;After L3 and PDCP periodical timer are overtime, it is periodically fixed that L3 starts L3 and RLC When device, into 103);
103) after L3 and RLC periodical timer are overtime, users consistency detection is carried out, if there is inconsistent use Family, L3 issue user and delete message to RLC;After L3 and RLC periodical timer are overtime, L3 starts L3 and MAC cycle timing Device, into 103);
104) L3 carries out users consistency detection, if there is inconsistent use with after MAC cycle timer expiry Family, L3 issue user and delete message to MAC;Terminate the whether consistent inspection department of user of L3 and each interlayer of PDCP/RLC/MAC Reason;
105) after MAC cycle timer expiry, judge whether user has business transmission in cycle time, if without if User is set to Idle state and is reported to L3, L3, which issues user and deletes, to be given UE (terminal), while each layer of base station side also will be deleted this User.
Specifically, when cell is established, L3 starts the cycle timer with PDCP layers, starting and RLC in the step 101) The cycle timer of layer, the cycle timer of starting and MAC layer, while MAC also will start 2 periodicity of User Status detection Timer.
Specifically, for L3 with after PDCP periodical timer time-out, L3 can issue user query message in the step 102) To PDCP layers, after PDCP receives query messages, local user's list is traversed, and user information is reported to L3, L3 is by it and originally Ground user list is compared, and inconsistent user L3 can issue user and delete message to PDCP.
Specifically, for L3 with after RLC periodical timer time-out, L3 can issue user query message in the step 103) To rlc layer, after RLC receives query messages, local user's list is traversed, and user information is reported to L3, L3 is by itself and local User list is compared, and inconsistent user L3 can issue user and delete message to RLC.
Specifically, for L3 with after MAC cycle timer expiry, L3 can issue user query message in the step 104) To MAC layer, after MAC receives query messages, local user's list is traversed, and user information is reported to L3, L3 is by itself and local User list is compared, and inconsistent user L3 can issue user and delete message to MAC.
Specifically, in the step 105), after MAC cycle timer expiry, according to the user counted in cycle time Portfolio, to judge that user currently should be in activated state or sleep state or Idle state, for being in the user of Idle state Needing to be reported to L3, L3 can carry out complete user to the user and delete process, deletion message is all issued to PDCP/RLC/MAC, Rrc release message is issued to terminal simultaneously.
It is limited by above step, starting periodical timer detects the user of L3 Yu each interlayer of PDCP/RLC/MAC respectively It is whether consistent, interlayer user is carried out to inconsistent user and deletes release processing, MAC, which starts periodical timer according to user, is It is no to there is business to carry out User Status detection, for the reporting of user in Idle state to L3, to each layer in base station and user terminal into The complete user that goes deletes release processing, solves base station side L3 and the inconsistent caused resource of each interlayer user of PDCP/RLC/MAC Waste and resource hang dead problem.
Referring to FIG. 1, carrying out users consistency inspection after 102) L3 and PDCP periodical timer are overtime in overall procedure It surveys, if there is inconsistent user, L3 issues user and deletes message to PDCP, and detailed process refers to be illustrated in Fig. 2;Then 103) after L3 and RLC periodical timer are overtime, users consistency detection is carried out, if there is inconsistent user, L3 is issued User deletes message to RLC, and detailed process refers to be illustrated in Fig. 3;Then 104) after L3 and MAC cycle timer expiry, into The detection of row users consistency, if there is inconsistent user, L3 issues user and deletes message to MAC, and detailed process refers to Fig. 4 Middle explanation;105) after MAC cycle timer expiry, judge whether user has business transmission in cycle time, if without if User is set to Idle state and is reported to L3, L3, which issues user and deletes, to be given UE (terminal), while each layer of base station side also will be deleted this User, detailed process refers to be illustrated in Fig. 5.
When it is implemented, can start to carry out the portfolio that user is transmitted in MAC measurement period after 101) executing, according to 105) timeout case of MAC cycle timer executes, do not need is executing 102) -104) just execution is 105).
Referring to FIG. 2, specific step is as follows for step 102):
Step 201, when L3 periodical timer time-out (specially L3 and PDCP periodical timer, if timer duration It is X minutes), L3 issues user query message to PDCP;
Step 202, after PDCP receives user query message, PDCP local user list is traversed, by all N number of customer instances RNTI be reported to L3, no customer instance will also report N=0;
Step 203, after L3 receives PDCP reporting message, the user list that L3 local user list and PDCP are reported is carried out It compares;
If certain user is present in the two lists, 204 are entered step;
If certain user is present in L3 local user list but is not present in the user list that PDCP is reported, enter step 205;
If certain user is present in the list of PDCP report of user but is not present in L3 local user's list, 206 are entered step;
Step 204, it if certain user is present in the two lists, does not handle, terminates this process;
Step 205, if certain user is present in L3 local user list but is not present in the user list that PDCP is reported, L3 issues complete UE and deletes process, and standard agreement process does not repeat here, terminates this process;
Step 206, if certain user is present in the list of PDCP report of user but is not present in L3 local user's list, L3 It only issues user and deletes after message receives message to PDCP, PDCP and discharge the user resources, terminate this process;
After above step, the users consistency of L3 Yu two interlayer of PDCP are reached.
Referring to FIG. 3, specific step is as follows for step 103):
Step 301, when L3 periodical timer time-out (specially L3 and RLC periodical timer, if timer duration is Y minutes), L3 issues user query message to RLC;
Step 302, after RLC receives user query message, RLC local user list is traversed, by all M customer instances RNTI is reported to L3, and no customer instance will also report M=0;
Step 303, after L3 receives RLC reporting message, the user list that L3 local user list and RLC are reported compares It is right;
If certain user is present in the two lists, 304 are entered step;
If certain user is present in L3 local user list but is not present in the user list that RLC is reported, enter step 305;
If certain user is present in the list of RLC report of user but is not present in L3 local user's list, 306 are entered step;
Step 304, it if certain user is present in the two lists, does not handle, terminates this process;
Step 305, if certain user is present in L3 local user list but is not present in the user list that RLC is reported, L3 issues complete UE and deletes process, and standard agreement process does not repeat here, terminates this process;
Step 306, if certain user is present in the list of RLC report of user but is not present in L3 local user's list, L3 It only issues user and deletes after message receives message to RLC, RLC and discharge the user resources, terminate this process;
After above step, the users consistency of L3 Yu two interlayer of RLC are reached.
Referring to FIG. 4, specific step is as follows for step 104):
Step 401, when L3 periodical timer time-out (specially L3 and MAC cycle timer, if timer duration is Z minutes), L3 issues user query message to MAC;
Step 402, after MAC receives user query message, MAC local user list is traversed, by all P customer instances RNTI is reported to L3, and no customer instance will also report P=0;
Step 403, after L3 receives MAC reporting message, the user list that L3 local user list and MAC are reported compares It is right;
If certain user is present in the two lists, 404 are entered step;
If certain user is present in L3 local user list but is not present in the user list that MAC is reported, enter step 405;
If certain user is present in the list of MAC report of user but is not present in L3 local user's list, 406 are entered step;
Step 404, it if certain user is present in the two lists, does not handle, terminates this process;
Step 405, if certain user is present in L3 local user list but is not present in the user list that MAC is reported, L3 issues complete UE and deletes process, and standard agreement process does not repeat here, terminates this process;
Step 406, if certain user is present in the list of MAC report of user but is not present in L3 local user's list, L3 It only issues user and deletes after message receives message to MAC, MAC and discharge the user resources, terminate this process;
After above step, the users consistency of L3 Yu two interlayer of MAC are reached.
Preferably, timer duration X=Y=Z.
Referring to FIG. 5, specific step is as follows for step 105):
Step 501, the portfolio that user is transmitted in the MAC measurement period time;
Step 502, when user is activated state, wait MAC cycle timer 1 overtime (setting timer duration as T minutes), If there is business, user is set to activated state, if user is set to sleep state (the short time interior user without business without business It is first set to sleep state, needs to observe a period of time (preventing ping-pong) again, determining it, there is no business demands, then are set to sky Not busy state), subsequently into step 504;
Step 503, when user is sleep state, MAC cycle timer 2 time-out is waited (to set timer duration as S minutes, S > T), if there is business, user is set to activated state, if user is set to Idle state, and (user of Idle state is always without business Resource but not substantive business demand is occupied, base station side is needed actively to discharge), subsequently into step 504;
Step 504, User Status result in step 502 and 503 is reported to L3;
Step 505, after L3 receives reporting message, the user in Idle state is subjected to complete UE and deletes process, standard Agreement process does not repeat here.
When it is implemented, method provided by the present invention can realize automatic running process based on software technology, mould can also be used Block mode realizes corresponding system.The embodiment of the present invention also provides a kind of users consistency detection system in LTE system, Whether the user for detecting each interlayer of L3 and PDCP/RLC/MAC respectively by L3 starting periodical timer is consistent, to inconsistent User carry out interlayer user delete release processing, MAC start periodical timer according to user whether have business carry out user State-detection carries out complete user's deletion to each layer in base station and user terminal for the reporting of user in Idle state to L3 Release processing;
Including being arranged in a base station with lower module,
First module, when establishing for cell, L3 successively starts 3 periodical timers, including successively start L3 with PDCP periodical timer, L3 and RLC periodical timer, L3 and MAC cycle timer;MAC starts 2 periodicity simultaneously Timer includes the periodical timer for sleep state judgement, MAC cycle timer 1 is denoted as, for judging Idle state Periodical timer is denoted as MAC cycle timer 2;
Second module carries out users consistency detection, if there is not after L3 and PDCP periodical timer time-out Consistent user, L3 issue user and delete message to PDCP;
Third module carries out users consistency detection, if there is not after L3 and RLC periodical timer time-out Consistent user, L3 issue user and delete message to RLC;
4th module carries out users consistency detection, if there is not after L3 and MAC cycle timer expiry Consistent user, L3 issue user and delete message to MAC;
5th module when user is activated state, waits MAC for the portfolio that user in the MAC measurement period time is transmitted 1 time-out of periodical timer, if there is user is set to activated state by business, if user is set to sleep state without business;When with Family is sleep state, MAC cycle timer 2 time-out is waited, if there is user is set to activated state by business, if will use without business Family is set to Idle state;User Status result is reported to L3;After L3 receives reporting message, the user in Idle state has been carried out Whole UE deletes process.
Each module specific implementation can be found in corresponding steps, and it will not go into details by the present invention.
The above content is specific embodiment is combined, further detailed description of the invention, and it cannot be said that this hair Bright specific implementation is only limited to these instructions.For those of ordinary skill in the art to which the present invention belongs, it is not taking off Under the premise of from present inventive concept, a number of simple deductions or replacements can also be made, all shall be regarded as belonging to protection of the invention Range.

Claims (4)

1. a kind of users consistency detection method in LTE system, it is characterised in that: L3 starts periodical timer difference Whether the user for detecting each interlayer of L3 and PDCP/RLC/MAC is consistent, carries out interlayer user to inconsistent user and deletes at release Reason, whether MAC starts periodical timer has business to carry out User Status detection according to user, for being in the user of Idle state It is reported to L3, complete user is carried out to each layer in base station and user terminal and deletes release processing;
Implementation includes executing following operation in a base station,
101) when cell is established, L3 successively starts 3 periodical timers, including successively starts L3 and PDCP periodically timing Device, L3 and RLC periodical timer, L3 and MAC cycle timer;It includes being used for that MAC starts 2 periodical timers simultaneously The periodical timer of sleep state judgement, is denoted as MAC cycle timer 1, for judging the periodical timer of Idle state, remembers For MAC cycle timer 2;
102) after L3 and PDCP periodical timer are overtime, users consistency detection is carried out, if there is inconsistent user, L3 It issues user and deletes message to PDCP;After L3 and PDCP periodical timer are overtime, L3 starts L3 and RLC periodical timer, Into 103);
After the L3 and PDCP periodical timer are overtime, users consistency detection is carried out, including use following sub-step, step 201, as L3 and PDCP periodical timer time-out, L3 issues user query message to PDCP;
Step 202, after PDCP receives user query message, PDCP local user list is traversed, by all N number of customer instances RNTI is reported to L3, and when no customer instance reports N=0;
Step 203, after L3 receives PDCP reporting message, the user list that L3 local user list and PDCP are reported compares It is right;
If entering step 204 in the user list that certain user is present in L3 local user list and PDCP is reported;
If certain user is present in L3 local user list but is not present in the user list that PDCP is reported, 205 are entered step;
If certain user is present in the list of PDCP report of user but is not present in L3 local user's list, 206 are entered step;
Step 204, it due in certain user is present in L3 local user list and PDCP is reported user list, then not handling, ties This process of beam;
Step 205, since certain user is present in L3 local user list but is not present in the user list that PDCP reports, then under L3 It sends out UE complete and deletes process, terminate this process;
Step 206, since certain user is present in the list of PDCP report of user but is not present in L3 local user's list, then L3 only under Hair family, which is deleted after message receives message to PDCP, PDCP, discharges the user resources, terminates this process;
103) after L3 and RLC periodical timer are overtime, users consistency detection is carried out, if there is inconsistent user, L3 It issues user and deletes message to RLC;After L3 and RLC periodical timer are overtime, L3 starts L3 and MAC cycle timer, into Enter 104);
After the L3 and RLC periodical timer are overtime, users consistency detection is carried out, including use following sub-step, step 301, as L3 and RLC periodical timer time-out, L3 issues user query message to RLC;
Step 302, after RLC receives user query message, RLC local user list is traversed, by the RNTI of all M customer instances It is reported to L3, when no customer instance reports M=0;
Step 303, after L3 receives RLC reporting message, the user list that L3 local user list and RLC report is compared; If entering step 304 in the user list that certain user is present in L3 local user list and RLC is reported;
If certain user is present in L3 local user list but is not present in the user list that RLC is reported, 305 are entered step;
If certain user is present in the list of RLC report of user but is not present in L3 local user's list, 306 are entered step;
Step 304, due in certain user is present in L3 local user list and RLC is reported user list, then not handling, terminate This process;
Step 305, since certain user is present in L3 local user list but is not present in the user list that RLC reports, then under L3 It sends out UE complete and deletes process, terminate this process;
Step 306, since certain user is present in the list of RLC report of user but is not present in L3 local user's list, then L3 only under Hair family, which is deleted after message receives message to RLC, RLC, discharges the user resources, terminates this process;
104) L3 carries out users consistency detection, if there is inconsistent user, L3 with after MAC cycle timer expiry It issues user and deletes message to MAC;The whether consistent inspection of the user for terminating L3 and each interlayer of PDCP/RLC/MAC is handled;It is described For L3 with after MAC cycle timer expiry, step 401 progress users consistency detection, including use following sub-step work as L3 With MAC cycle timer expiry, L3 issues user query message to MAC;
Step 402, after MAC receives user query message, MAC local user list is traversed, by the RNTI of all P customer instances It is reported to L3, when no customer instance reports P=0;
Step 403, after L3 receives MAC reporting message, the user list that L3 local user list and MAC report is compared; If entering step 404 in the user list that certain user is present in L3 local user list and MAC is reported;
If certain user is present in L3 local user list but is not present in the user list that MAC is reported, 405 are entered step;
If certain user is present in the list of MAC report of user but is not present in L3 local user's list, 406 are entered step;
Step 404, due in certain user is present in L3 local user list and MAC is reported user list, then not handling, terminate This process;
Step 405, since certain user is present in L3 local user list but is not present in the user list that MAC reports, then under L3 It sends out UE complete and deletes process, terminate this process;
Step 406, since certain user is present in the list of MAC report of user but is not present in L3 local user's list, then L3 only under Hair family, which is deleted after message receives message to MAC, MAC, discharges the user resources, terminates this process;
105) after MAC cycle timer expiry, judge that whether user has business transmission in cycle time, will use if not Family is set to Idle state and is reported to L3, and L3 issues user and deletes to terminal UE, while each layer of base station side also will be deleted the user;
The detection of MAC User Status when user is activated state, waits MAC including the portfolio that user in the measurement period time is transmitted 1 time-out of periodical timer, if there is user is set to activated state by business, if user is set to sleep state without business;When with Family is sleep state, MAC cycle timer 2 time-out is waited, if there is user is set to activated state by business, if will use without business Family is set to Idle state;User Status result is reported to L3;After L3 receives reporting message, the user in Idle state has been carried out Whole UE deletes process.
2. according to claim 1 for the users consistency detection method in LTE system, it is characterised in that: the MAC is used Family state-detection, including following sub-step is used,
Step 501, the portfolio that user is transmitted in the MAC measurement period time;
Step 502, when user is activated state, waiting MAC cycle timer 1 is overtime, if timer duration is T minutes;If There is business that user is set to activated state, if user is set to sleep state without business, subsequently into step 504;
Step 503, when user is sleep state, waiting MAC cycle timer 2 is overtime, if timer duration is S minutes, S > T; If there is user is set to activated state by business, if user is set to Idle state without business, subsequently into step 504;
Step 504, step 502 and 503 gained User Status results are reported to L3;
Step 505, after L3 receives reporting message, the user in Idle state is subjected to complete UE and deletes process.
3. a kind of users consistency detection system in LTE system, it is characterised in that: for starting periodically timing by L3 Whether the user that device detects each interlayer of L3 and PDCP/RLC/MAC respectively is consistent, carries out interlayer user deletion to inconsistent user Release processing, whether MAC starts periodical timer has business to carry out User Status detection according to user, for being in Idle state Reporting of user to L3, complete user is carried out to each layer in base station and user terminal and deletes release processing;
Including being arranged in a base station with lower module,
First module, when establishing for cell, L3 successively starts 3 periodical timers, including successively starts L3 and PDCP weeks Phase property timer, L3 and RLC periodical timer, L3 and MAC cycle timer;MAC starts 2 periodical timers simultaneously Including the periodical timer judged for sleep state, it is denoted as MAC cycle timer 1, for judging the periodicity of Idle state Timer is denoted as MAC cycle timer 2;
Second module carries out users consistency detection, if there is inconsistent after L3 and PDCP periodical timer time-out User, L3 issue user delete message to PDCP;
Include in second module with lower unit,
Unit M201, for issuing user query message to PDCP as L3 and PDCP periodical timer time-out, L3;
Unit M202 after receiving user query message for PDCP, traverses PDCP local user list, and all N number of users are real The RNTI of example is reported to L3, and when no customer instance reports N=0;
Unit M203, after receiving PDCP reporting message for L3, user list that L3 local user list and PDCP are reported into Row compares;
In the user list that if certain user is present in L3 local user list and PDCP is reported, order unit M204 work;
If certain user is present in L3 local user list but is not present in the user list that PDCP is reported, order unit M205 work Make;
If certain user is present in the list of PDCP report of user but is not present in L3 local user's list, order unit M206 work Make;
Unit M204 is tied due in certain user is present in L3 local user list and PDCP is reported user list, then not handling The work of this module of beam;
Unit M205, since certain user is present in L3 local user list but is not present in the user list that PDCP reports, then L3 It issues complete UE and deletes process, terminate the work of this module;
Unit M206, since certain user is present in the list of PDCP report of user but is not present in L3 local user's list, then L3 It issues user and deletes after message receives message to PDCP, PDCP and discharge the user resources, terminate the work of this module;
Third module carries out users consistency detection, if there is inconsistent after L3 and RLC periodical timer time-out User, L3 issue user delete message to RLC;
Include in third module with lower unit,
Unit M301, for issuing user query message to RLC as L3 and RLC periodical timer time-out, L3;
Unit M302 after receiving user query message for RLC, traverses RLC local user list, by all M customer instances RNTI be reported to L3, when no customer instance, reports M=0;
Unit M303, after receiving RLC reporting message for L3, the user list that L3 local user list and RLC are reported is carried out It compares;
In the user list that if certain user is present in L3 local user list and RLC is reported, order unit M304 work;
If certain user is present in L3 local user list but is not present in the user list that RLC is reported, order unit M305 work Make;If certain user is present in the list of RLC report of user but is not present in L3 local user's list, order unit M306 work;
Unit M304 is tied due in certain user is present in L3 local user list and RLC is reported user list, then not handling The work of this module of beam;
Unit M305, since certain user is present in L3 local user list but is not present in the user list that RLC reports, then under L3 It sends out UE complete and deletes process, terminate the work of this module;
Unit M306, since certain user is present in the list of RLC report of user but is not present in L3 local user's list, then L3 only under Hair family, which is deleted after message receives message to RLC, RLC, discharges the user resources, terminates the work of this module;
4th module carries out users consistency detection, if there is inconsistent after L3 and MAC cycle timer expiry User, L3 issue user delete message to MAC;
Include in 4th module with lower unit,
Unit M401, for when L3 and MAC cycle timer expiry, L3 to issue user query message to MAC;
Unit M402 after receiving user query message for MAC, traverses MAC local user list, by all P customer instances RNTI be reported to L3, when no customer instance, reports P=0;
Unit M403, after receiving MAC reporting message for L3, the user list that L3 local user list and MAC are reported is carried out It compares;
In the user list that if certain user is present in L3 local user list and MAC is reported, order unit M404 work;
If certain user is present in L3 local user list but is not present in the user list that MAC is reported, order unit M405 work Make;If certain user is present in the list of MAC report of user but is not present in L3 local user's list, order unit M406 work;
Unit M404 is tied due in certain user is present in L3 local user list and MAC is reported user list, then not handling The work of this module of beam;
Unit M405, since certain user is present in L3 local user list but is not present in the user list that MAC reports, then under L3 It sends out UE complete and deletes process, terminate the work of this module;
Unit M406, since certain user is present in the list of MAC report of user but is not present in L3 local user's list, then L3 only under Hair family, which is deleted after message receives message to MAC, MAC, discharges the user resources, terminates the work of this module;
5th module when user is activated state, waits MAC cycle for the portfolio that user in the MAC measurement period time is transmitted Property the time-out of timer 1, if there is user is set to activated state by business, if user is set to sleep state without business;When user is Sleep state waits MAC cycle timer 2 time-out, if there is user is set to activated state by business, if set user without business For Idle state;User Status result is reported to L3;After L3 receives reporting message, the user in Idle state is carried out complete UE deletes process.
4. according to claim 3 for the users consistency detection system in LTE system, it is characterised in that: the 5th module In include with lower unit,
Unit M501, the portfolio transmitted for user in the MAC measurement period time;
Unit M502 waits 1 time-out of MAC cycle timer, if timer duration is T minutes for being activated state as user; If there is user is set to activated state by business, if user is set to sleep state without business, then order unit M504 works;
Unit M503, for being sleep state as user, waiting MAC cycle timer 2 time-out, if timer duration is S minutes, S>T;
If there is user is set to activated state by business, if user is set to Idle state without business, then order unit M504 work Make;Unit M504, for unit M502 and 503 gained User Status results to be reported to L3;
User in Idle state after receiving reporting message for L3, is carried out complete UE and deletes process by unit M505.
CN201610859373.3A 2016-09-28 2016-09-28 For the users consistency detection method and system in LTE system Active CN106162719B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610859373.3A CN106162719B (en) 2016-09-28 2016-09-28 For the users consistency detection method and system in LTE system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610859373.3A CN106162719B (en) 2016-09-28 2016-09-28 For the users consistency detection method and system in LTE system

Publications (2)

Publication Number Publication Date
CN106162719A CN106162719A (en) 2016-11-23
CN106162719B true CN106162719B (en) 2019-09-10

Family

ID=57340889

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610859373.3A Active CN106162719B (en) 2016-09-28 2016-09-28 For the users consistency detection method and system in LTE system

Country Status (1)

Country Link
CN (1) CN106162719B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107027140A (en) * 2017-03-27 2017-08-08 武汉虹信通信技术有限责任公司 Protocal layers customer instance consistency maintaining method in a kind of LTE
CN111343647B (en) * 2018-12-19 2022-08-02 中国移动通信集团重庆有限公司 Method, apparatus, device and medium for user perception evaluation
CN111526381B (en) * 2020-04-20 2021-07-09 北京创世云科技股份有限公司 Method and device for optimizing live broadcast resources and electronic equipment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1316141A (en) * 1998-06-13 2001-10-03 三星电子株式会社 State synchronizing method and device of base and mobile station in CDMA system
CN1855918A (en) * 2005-04-25 2006-11-01 华为技术有限公司 Method for maintaining status synchronization between protocol layers in command stream in service stream
CN1905480A (en) * 2006-07-27 2007-01-31 普天信息技术研究院 Base station starting method
CN104661254A (en) * 2015-02-16 2015-05-27 北京电信技术发展产业协会 Method and device for testing carrier aggregation consistency of LTE-A (long term evolution-advance) terminal on MAC (media access control) layer
CN105376863A (en) * 2015-11-13 2016-03-02 重庆邮电大学 Method and device for managing wireless resources of mobile terminal

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030210714A1 (en) * 2002-05-10 2003-11-13 Chih-Hsiang Wu Method for avoiding loss of pdcp pdus in a wireless communications system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1316141A (en) * 1998-06-13 2001-10-03 三星电子株式会社 State synchronizing method and device of base and mobile station in CDMA system
CN1855918A (en) * 2005-04-25 2006-11-01 华为技术有限公司 Method for maintaining status synchronization between protocol layers in command stream in service stream
CN1905480A (en) * 2006-07-27 2007-01-31 普天信息技术研究院 Base station starting method
CN104661254A (en) * 2015-02-16 2015-05-27 北京电信技术发展产业协会 Method and device for testing carrier aggregation consistency of LTE-A (long term evolution-advance) terminal on MAC (media access control) layer
CN105376863A (en) * 2015-11-13 2016-03-02 重庆邮电大学 Method and device for managing wireless resources of mobile terminal

Also Published As

Publication number Publication date
CN106162719A (en) 2016-11-23

Similar Documents

Publication Publication Date Title
CN101562894B (en) Sending method of buffer state report and equipment thereof
CN106304374B (en) A kind of machine communication dispatching method, base station and user equipment
CN103378939B (en) A kind of downlink data transmission method and device
CN104620660B (en) Idle state accidental access method and equipment
CN106162719B (en) For the users consistency detection method and system in LTE system
CN105828452B (en) Communication means, communication device, access point and the website of WLAN
CN106034318A (en) Method and device for controlling discontinuous reception
CN105722195A (en) Discontinuous reception method and device
CN101427521B (en) reliable multicast in the network with power saving protocol
CN109644454A (en) Terminal wake-up control method, device and storage medium
CN109068376A (en) Method and device, storage medium into low power consumpting state
CN110268763A (en) Reception scheme
DE602008002374D1 (en) A method and apparatus for managing discontinuous downlink receive operation in a wireless communication system
CN106961727A (en) A kind of paging and its control method and device
CN104703145A (en) Cluster group calling-blind detection capacity processing method, device and system
CN108282849A (en) Data transmission, data receiver method and device, access point, website
CN107708194A (en) A kind of message filtering method and device, terminal and readable storage medium storing program for executing
CN108934059A (en) The selection method and relevant device of unlicensed band persistent district
CN102164422A (en) Method and system for releasing resources and base station
CN107113817A (en) Data transmission method, device, base station and user equipment
CN102143533B (en) Methods and equipment for reporting information generated in random access process and determining parameters
CN105992320A (en) Discontinuous reception method, wireless access network node and terminal
CN105165077B (en) A kind of carrier data transmission method and device
CN1553719A (en) Realizing method for housing estate broadcasting service
CN112788654B (en) Information reporting method, terminal and base station

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
CP03 Change of name, title or address

Address after: 430205 Hubei city of Wuhan province Jiangxia Hidden Dragon Island Tan lake two Road No. 1

Patentee after: CITIC Mobile Communication Technology Co., Ltd

Address before: 430073 Hubei province Wuhan Dongxin East Lake high tech Development Zone, Road No. 5

Patentee before: Wuhan Hongxin Telecommunication Technologies Co.,Ltd.

CP03 Change of name, title or address
CP01 Change in the name or title of a patent holder

Address after: 430205 No.1 tanhu 2nd Road, Canglong Island, Jiangxia District, Wuhan City, Hubei Province

Patentee after: CITIC Mobile Communication Technology Co.,Ltd.

Address before: 430205 No.1 tanhu 2nd Road, Canglong Island, Jiangxia District, Wuhan City, Hubei Province

Patentee before: CITIC Mobile Communication Technology Co., Ltd

CP01 Change in the name or title of a patent holder