CN107027140A - Protocal layers customer instance consistency maintaining method in a kind of LTE - Google Patents
Protocal layers customer instance consistency maintaining method in a kind of LTE Download PDFInfo
- Publication number
- CN107027140A CN107027140A CN201710189611.9A CN201710189611A CN107027140A CN 107027140 A CN107027140 A CN 107027140A CN 201710189611 A CN201710189611 A CN 201710189611A CN 107027140 A CN107027140 A CN 107027140A
- Authority
- CN
- China
- Prior art keywords
- layer
- customer instance
- message
- rrc
- customer
- 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.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/321—Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Protocal layers customer instance consistency maintaining method in a kind of LTE, users consistency inspection is carried out based on periodically timing, if layer L3 and layer LX carries out users consistency inspection, layer L3 initiates user profile inquiry request by interlayer message to layer LX；Layer LX is received after message issues a layer L3 by interlayer message by the customer instance information that this module is safeguarded；Layer L3 is checked the customer instance information of customer instance information with layer LX this module in message, for customer instance in layer L3 presence in the non-existent situations of layer LX, initiate user's context release flow, when being not present and existing in layer LX in layer L3 for customer instance, layer L3 notifies layer LX to delete the customer instance.The present invention checks the customer instance information of protocal layers by periodic interlayer interacting message, and inconsistent customer instance is discharged, so as to ensure protocal layers customer instance uniformity.
Description
Technical field
The present invention relates to moving communicating field, used in particular it relates to solve protocal layers in a kind of LTE system
The method of family example inconsistence problems.
Background technology
4g nets are exactly that forth generation mobile communications network .lte (long term evolution Long Term Evolutions) is a 4g net
Network standard.LTE eNB (base station) chain of command agreement stack is made up of multiple protocol layers, including layer one (Physical Layer, letter
Claim PHY, i.e. physical layer, also known as L1), layer two (Layer2, also known as L2), layer three (rrc layer, RRC is wireless heterogeneous networks,
Also known as L3).Its middle level two is divided into tri- sublayers of MAC, RLC, PDCP again.In general, eNB is carried out to chain of command customer instance
During management, L3 (RRC), L2 (MAC, RLC, PDCP), L1 (PHY) each layer can all safeguard the user's context of oneself.In chain of command
In signaling process, each layer transmits user profile by way of message communicating.When user accesses eNB systems, each layer is required for
Customer instance is created for the user.When user discharges from eNB systems, each layer is required for deleting the user's reality created for the user
Example.Because message communicating exception or inter-process are abnormal, each layer may be real without synchronous establishment customer instance or deletion user
Example, so as to cause customer instance inconsistent.And this customer instance is inconsistent, and the user can be caused can not to be normally carried out signaling flow
Journey and business transmission, can cause eNB system resources to be hung and extremely normally be run so as to have influence on system.
The content of the invention
Problem to be solved by this invention is inconsistent for the protocal layers customer instance that occurs in LTE eNB systems
Which kind of scheme is situation, take customer instance is recovered into consistent, so that safeguards system is normally run.
Technical solution of the present invention provides protocal layers customer instance consistency maintaining method, the protocol layer in a kind of LTE
Including layer L1, layer L2, layer L3, layer L1 is PHY layer, and layer L3 is rrc layer, and L2 points of layer is tri- sublayers of MAC, RLC, PDCP,
After the foundation of eNB cells, layer L3 starts periodical timer, while counter N is reset；
Periodical timer the 4N+1 times, the 4N+2 times, the 4N+3 times, the 4N+4 times time-out when, layer L3 respectively with
Certain layer carries out users consistency inspection among layer L2 PDCP sublayers, layer L2 rlc sublayer, layer L2 media access control sublayer, layer L1；
Then N=N+1 is made, counter N is added 1, returns and continues next round processing；
Wherein, users consistency checks that implementation is, if layer L3 and layer LX carries out users consistency inspection, layer LX is layer
L2 PDCP sublayers, layer L2 rlc sublayer, layer L2 media access control sublayer or layer L1；Layer L3 initiates user by interlayer message to layer LX
Information inquiring request；Layer LX is received after message issues a layer L3 by interlayer message by the customer instance information that this module is safeguarded；Layer
L3 is received after message, the customer instance information of customer instance information with layer LX this module in message is checked, according to core
To result to carry out corresponding processing as follows,
(1) it need not be handled when both are completely the same；
(2) exist for customer instance in layer L3 and in the non-existent situations of layer LX, initiate user's context release flow,
Including the release of S1 links, RRC Connection Releases and local release；
(3) when being not present and existing in layer LX in layer L3 for customer instance, layer L3 notifies layer LX to delete the user
Example.
Moreover, when the 4N+1 times time-out of periodical timer, it is consistent that layer L3 carries out user with layer L2 PDCP sublayers
Property check；When the 4N+2 times time-out of periodical timer, layer L3 and layer L2 rlc sublayer carries out users consistency inspection；
When the 4N+3 times time-out of periodical timer, layer L3 and layer L2 media access control sublayer carries out users consistency inspection；It is periodically fixed
When the time-out of device the 4N+4 times when, layer L3 and layer L1 carries out users consistency inspection.
Moreover, a length of 5 minutes during periodical timer.
The present invention proposes a kind of method for solving protocal layers customer instance inconsistence problems, is disappeared by periodic interlayer
Cease interaction to check the customer instance information of protocal layers, and inconsistent customer instance is discharged, so as to ensure each association
Layer customer instance uniformity is discussed, there is important application value in moving communicating field, with important market value.
Brief description of the drawings
Fig. 1 is the schematic diagram of the embodiment of the present invention；
Fig. 2 is the flow chart of the embodiment of the present invention.
Embodiment
Understand for the ease of those of ordinary skill in the art and implement the present invention, below in conjunction with the accompanying drawings and embodiment
The present invention is described in further detail.
The present invention proposed periodically to send message mutually between each layers of eNB, and each layer use of oneself is carried in the message
Family example information.Message root is received according to customer instance information in message and the customer instance information of this layer of inside, verification is
It is no to there is a situation where that customer instance is inconsistent.It is inconsistent if there is customer instance, then related customer instance is discharged
Processing.
, can be in the following ways according to technical solution of the present invention referring to Fig. 1：
A) start cycle timer, put N=0：After the foundation of eNB cells, L3 (RRC) starts periodical timer, duration
For 5 minutes.Counter N is reset simultaneously.When it is implemented, it can also be provided that other durations.The duration is smaller, then finds simultaneously
The problem of processing user is inconsistent is more timely, but the interlayer message of consumption is more；Conversely, finding and handling that user is inconsistent to be asked
Inscribe more not in time, but the interlayer message of consumption is fewer.
B) L3 issues PDCP user information requests：When the 4N+1 times time-out of periodical timer, L3 (RRC) and L2
(PDCP) users consistency inspection is carried out.L3 (RRC) will by interlayer message to L2 (PDCP) initiate user profile inquiry request.
C) PDCP issues the response of L3 user profile：L2 (PDCP) receives safeguard this module by interlayer message after message
Customer instance information issues L3 (RRC).
D) customer instance information is checked, respective handling is carried out according to checked result：L3 (RRC) is received after message, by message
In the customer instance information of customer instance information with L3 (RRC) this module checked.Carried out according to the result of verification corresponding
Processing.It need not be handled when both are completely the same；Exist for customer instance in L3 (RRC) and at L2 (PDCP)
Non-existent situation, initiates user's context release flow, including the release of S1 links, RRC Connection Releases and local release；It is right
The situation for being not present and existing in L2 (PDCP) in L3 (RRC) in customer instance, L3 (RRC) notifies L2 (PDCP) to delete the user
Example.
E) when the 4N+2 times time-out of periodical timer, L3 (RRC) and L2 (RLC) carries out users consistency inspection
Look into.Treatment principle and above-mentioned steps b)~d) it is identical.
F) when the 4N+3 times time-out of periodical timer, L3 (RRC) and L2 (MAC) carries out users consistency inspection
Look into.Treatment principle and above-mentioned steps b)~d) it is identical.
G) when the 4N+4 times time-out of periodical timer, L3 (RRC) and L1 (PHY) carries out users consistency inspection
Look into.Treatment principle and above-mentioned steps b)~d) it is identical.Then N=N+1 is made, counter N is added 1, return to step b) continues next
Take turns flow processing.
Setting in step a) so that users consistency inspection is periodic, and usage cycles timer is controlled；
Step b), c) in, use interlayer messaging user example information；
In step d), the customer instance of two modules is checked, handled accordingly according to the result of verification, it is right
Customer instance can be initiated by L3 (RRC) in inconsistent situation to delete, so that it is consistent to recover customer instance.
When it is implemented, the order that L3 (RRC) is checked L2 (PDCP), L2 (RLC), L2 (MAC), L1 (PHY)
It can adjust, equivalents can be considered as.
Referring to Fig. 2, embodiment for for each layer customer instance of L3, L2, L1 in eNB carry out that consistency check provides it is specific
Flow is as follows：
1) start cycle timer, put N=0：L3 (RRC) starts periodical timer, and timer duration is set to 5 points
Clock, while by counter N clear 0；
2) L3 issues PDCP user information requests：When periodical timer (4N+1) is secondary overtime, L3 (RRC) passes through
Interlayer message initiates customer instance inquiry request to L2 (PDCP)；
3) PDCP issues the response of L3 user profile：L2 (PDCP) is received after message, is safeguarded this module by interlayer message
Customer instance information issue L3 (RRC)；
4) customer instance information is checked：When L3 (RRC) receives L2 (PDCP) customer instance information, with L3 (RRC) this mould
The customer instance information of block is checked.5) or 6) handled, respectively enterd accordingly according to the result of verification.
5) inconsistent situation 1, L3 (RRC) is present but UE examples are not present in L2 (PDCP), and L3 (RRC) initiates complete UE and released
Release journey：If customer instance exists in L3 (RRC) but is not present in L2 (PDCP), L3 (RRC) initiates user's context release
Flow, including S1 releases, RRC releases and local release；
6) inconsistent situation 2, L3 (RRC) is not present but L2 (PDCP) has UE examples, and L3 issues PDCP user's release please
Ask：If customer instance is not present in L3 (RRC) but existed in L2 (PDCP), L3 (RRC) passes through interlayer message informing L2
(PDCP) customer instance is discharged；
7) L3 issues RLC user information requests：When periodical timer (4N+2) is secondary overtime, L3 (RRC) passes through
Interlayer message initiates customer instance inquiry request to L2 (RLC)；
8) RLC issues the response of L3 user profile：L2 (RLC) is received after message, is safeguarded this module by interlayer message
Customer instance information issues L3 (RRC)；
9) customer instance information is checked：When L3 (RRC) receives L2 (RLC) customer instance information, with L3 (RRC) this module
Customer instance information checked.10) or 11) handled, respectively enterd accordingly according to the result of verification.
10) inconsistent situation 1, L3 (RRC) is present but UE examples are not present in L2 (RLC), and L3 (RRC) initiates complete UE and released
Release journey, including S1 releases, RRC releases and local release：If customer instance exist in L3 (RRC) but in L2 (RLC) no
In the presence of L3 (RRC) initiates user's context release flow, including S1 releases, RRC releases and local release；
11) inconsistent situation 2, L3 (RRC) is not present but L2 (RLC) has UE examples, and L3 issues RLC user's release please
Ask：If customer instance is not present in L3 (RRC) but existed in L2 (RLC), L3 (RRC) passes through interlayer message informing L2 (RLC)
Discharge the customer instance；
12) L3 issues MAC user information requests：When periodical timer (4N+3) is secondary overtime, L3 (RRC) passes through
Interlayer message initiates customer instance inquiry request to L2 (MAC)；
13) MAC issues the response of L3 user profile：L2 (MAC) is received after message, is safeguarded this module by interlayer message
Customer instance information issues L3 (RRC)；
14) customer instance information is checked：When L3 (RRC) receives L2 (MAC) customer instance information, with L3 (RRC) this mould
The customer instance information of block is checked.15) or 16) handled, respectively enterd accordingly according to the result of verification.
15) inconsistent situation 1, L3 (RRC) is present but UE examples are not present in L2 (MAC), and L3 (RRC) initiates complete UE and released
Release journey, including S1 releases, RRC releases and local release：If customer instance exist in L3 (RRC) but in L2 (MAC) no
In the presence of L3 (RRC) initiates user's context release flow, including S1 releases, RRC releases and local release；
16) inconsistent situation 2, L3 (RRC) is not present but L2 (MAC) has UE examples, and L3 issues MAC user's release please
Ask：If customer instance is not present in L3 (RRC) but existed in L2 (MAC), L3 (RRC) passes through interlayer message informing L2 (MAC)
Discharge the customer instance；
17) L3 issues L1 user information requests：When periodical timer (4N+4) is secondary overtime, L3 (RRC) passes through
Interlayer message initiates customer instance inquiry request to L1 (PHY)；
18) L1 issues L3 user profile response：L1 (PHY) is received after message, is safeguarded this module by interlayer message
Customer instance information issue L3 (RRC)；
19) customer instance information is checked：When L3 (RRC) receives L1 (PHY) customer instance information, with L3 (RRC) this mould
The customer instance information of block is checked.20) or 21) handled, respectively enterd accordingly according to the result of verification.
20) inconsistent situation 1, L3 (RRC) is present but UE examples are not present in L1 (PHY), and L3 (RRC) initiates complete UE and released
Release journey, including S1 releases, RRC releases and local release：If customer instance exist in L3 (RRC) but in L1 (PHY) no
In the presence of L3 (RRC) initiates user's context release flow, including S1 releases, RRC releases and local release；
21) inconsistent situation 2, L3 (RRC) is not present but L1 (PHY) has UE examples, and L3 issues L1 user's releasing request：
If customer instance is not present in L3 (RRC) but existed in L1 (PHY), L3 (RRC) is discharged by interlayer message informing L1 (PHY)
The customer instance；
22) counter N is added 1, return to step 2), continue next round flow processing.
When it is implemented, those skilled in the art can realize the automatic running of above flow using computer software mode.
It is above the present invention preferably embodiment, but embodiments of the present invention and is not restricted to the described embodiments,
Other any Spirit Essences for not running counter to the present invention and the change made under principle, modification, replacement, combine, simplify and should be
Equivalent substitute mode, is included within protection scope of the present invention.
Claims (3)
1. a kind of protocal layers customer instance consistency maintaining method in LTE, the protocol layer includes layer L1, layer L2, layer L3, layer
L1 is PHY layer, and layer L3 is rrc layer, and L2 points of layer is tri- sublayers of MAC, RLC, PDCP, it is characterised in that：
After the foundation of eNB cells, layer L3 starts periodical timer, while counter N is reset；
Periodical timer the 4N+1 times, the 4N+2 times, the 4N+3 times, the 4N+4 times time-out when, layer L3 respectively with layer L2
PDCP sublayers, layer L2 rlc sublayer, layer L2 media access control sublayer, certain layer carries out users consistency inspection among layer L1；
Then N=N+1 is made, counter N is added 1, returns and continues next round processing；
Wherein, users consistency checks that implementation is, if layer L3 and layer LX carries out users consistency inspection, layer LX is layer L2's
PDCP sublayers, layer L2 rlc sublayer, layer L2 media access control sublayer or layer L1；Layer L3 initiates user profile by interlayer message to layer LX
Inquiry request；Layer LX is received after message issues a layer L3 by interlayer message by the customer instance information that this module is safeguarded；Layer L3 is received
To after message, the customer instance information of customer instance information with layer LX this module in message is checked, according to verification
As a result corresponding processing is carried out as follows,
(1) it need not be handled when both are completely the same；
(2) exist for customer instance in layer L3 and in the non-existent situations of layer LX, initiate user's context release flow, including
The release of S1 links, RRC Connection Releases and local release；
(3) when being not present and existing in layer LX in layer L3 for customer instance, layer L3 notifies layer LX to delete the customer instance.
2. protocal layers customer instance consistency maintaining method in LTE according to claim 1, it is characterised in that：Periodically
When the 4N+1 times time-out of timer, layer L3 and layer L2 PDCP sublayers carry out users consistency inspection；Periodical timer
When the 4N+2 times time-out, layer L3 and layer L2 rlc sublayer carries out users consistency inspection；Periodical timer the 4N+3 times
When overtime, layer L3 and layer L2 media access control sublayer carries out users consistency inspection；The time-out of periodical timer the 4N+4 times when
Wait, layer L3 and layer L1 carries out users consistency inspection.
3. protocal layers customer instance consistency maintaining method in LTE according to claim 1 or claim 2, it is characterised in that：Cycle
Property timer duration be 5 minutes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710189611.9A CN107027140A (en) | 2017-03-27 | 2017-03-27 | Protocal layers customer instance consistency maintaining method in a kind of LTE |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710189611.9A CN107027140A (en) | 2017-03-27 | 2017-03-27 | Protocal layers customer instance consistency maintaining method in a kind of LTE |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107027140A true CN107027140A (en) | 2017-08-08 |
Family
ID=59525349
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710189611.9A Pending CN107027140A (en) | 2017-03-27 | 2017-03-27 | Protocal layers customer instance consistency maintaining method in a kind of LTE |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107027140A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1777127A (en) * | 2005-12-08 | 2006-05-24 | 中国移动通信集团公司 | Protocol conformance measuring device and method |
| CN101808356A (en) * | 2010-04-20 | 2010-08-18 | 工业和信息化部电信传输研究所 | Protocol simulation system for TD-SCDMA terminal protocol conformance tests |
| WO2012108687A2 (en) * | 2011-02-08 | 2012-08-16 | Ahnlab., Inc. | Method of detecting arp spoofing attacks using arp locking and computer-readable recording medium storing program for executing the method |
| US20140278295A1 (en) * | 2013-03-15 | 2014-09-18 | Schrodinger, Llc | Cycle Closure Estimation of Relative Binding Affinities and Errors |
| CN104661255A (en) * | 2015-02-16 | 2015-05-27 | 北京电信技术发展产业协会 | Method and device for testing carrier aggregation consistency of LTE-A (long term evolution-advance) terminal on RRC (radio resource control) layer |
| 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 |
| CN106162719A (en) * | 2016-09-28 | 2016-11-23 | 武汉虹信通信技术有限责任公司 | Users consistency detection method in LTE system and system |
-
2017
- 2017-03-27 CN CN201710189611.9A patent/CN107027140A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1777127A (en) * | 2005-12-08 | 2006-05-24 | 中国移动通信集团公司 | Protocol conformance measuring device and method |
| CN101808356A (en) * | 2010-04-20 | 2010-08-18 | 工业和信息化部电信传输研究所 | Protocol simulation system for TD-SCDMA terminal protocol conformance tests |
| WO2012108687A2 (en) * | 2011-02-08 | 2012-08-16 | Ahnlab., Inc. | Method of detecting arp spoofing attacks using arp locking and computer-readable recording medium storing program for executing the method |
| US20140278295A1 (en) * | 2013-03-15 | 2014-09-18 | Schrodinger, Llc | Cycle Closure Estimation of Relative Binding Affinities and Errors |
| CN104661255A (en) * | 2015-02-16 | 2015-05-27 | 北京电信技术发展产业协会 | Method and device for testing carrier aggregation consistency of LTE-A (long term evolution-advance) terminal on RRC (radio resource control) layer |
| 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 |
| CN106162719A (en) * | 2016-09-28 | 2016-11-23 | 武汉虹信通信技术有限责任公司 | Users consistency detection method in LTE system and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11871349B2 (en) | Sleep method for terminal device and apparatus | |
| CN102917444B (en) | The method and device of discontinuous reception under idle condition | |
| CN105594141B (en) | Method and system for the random access procedure between eNB in carrier wave polymerization | |
| CN107690163A (en) | Cell switching method and device | |
| CN109246802A (en) | Wireless heterogeneous networks Connection Release method and device, base station and user equipment | |
| CN104113928A (en) | Radio bearer control (RBC) message processing method and device | |
| CN108616950A (en) | Motion management method, equipment of the core network between Radio Access Network and base station | |
| TW201233224A (en) | Methods for handling mobility management (MM) back-off operations | |
| CN110536383A (en) | Terminal power-economizing method, base station and terminal | |
| CN105122930A (en) | Method and apparatus for setting up/releasing radio resource control connection between evolved node b and user equipment in communication system | |
| CN101541059A (en) | Device and method to remove access restriction and chip group | |
| EP3197098B1 (en) | Heartbeat cycle setting method and terminal | |
| CN103313420A (en) | Terminal link release method, access network device and terminal | |
| CN110268763A (en) | Reception scheme | |
| CN107710810A (en) | The inactive process of the equipment of business with delay-tolerant | |
| CN108370606A (en) | Early stage Connection Release | |
| WO2019213822A1 (en) | Method and apparatus for suspending rrc connection, and computer storage medium | |
| CN109982442A (en) | A kind of method run on a user device and user equipment | |
| CN106535336A (en) | Base station and discontinuous reception and disposal method thereof | |
| US20210168893A1 (en) | Method and Device for Resuming Data Radio Bearer, Storage Medium and Electronic Device | |
| CN103298023A (en) | Method and device for detecting terminal heartbeat | |
| CN104427598B (en) | Exempt from the method and apparatus of heartbeat in line service for a long time | |
| CN109803455A (en) | Connection control, method for processing business and device | |
| CN102281578A (en) | Method and device for deactivating cell | |
| WO2020088091A1 (en) | Status reporting method and device, message receiving method and device, storage medium, and electronic 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170808 |
|
| RJ01 | Rejection of invention patent application after publication |