1. http://www.sharetechnote.com/html/Handbook_LTE.html

2. http://4g-portal.com/

3. http://howltestuffworks.blogspot.kr/

4. http://www.netmanias.com/

5. http://lteinwireless.blogspot.kr/

6. http://www.simpletechpost.com/

저작자 표시 비영리 변경 금지
신고

WRITTEN BY
빅터크룸
머 먹고 사냐.....

받은 트랙백이 없고 , 댓글이 없습니다.
secret

http://www.sharetechnote.com/html/Handbook_LTE_DRX.html


Even while there is no traffic between the network and UE, UE has to keep listening to Network. At least it should be ready to decode PDCCH. It means UE has to be "ON" all the time even when there is no traffic. But being ON all the time would drain the battery.

You may ask "Then why don't UE shut down (getting into a sleep mode) when there is no traffic ?". Sounds good, but what if Network tries to send some data to UE while the UE is in the sleep mode ?

 

Then what would be the ideal solution for this ? what is the ideal solution to save battery consumption and still does not lose chance of receiving the data that Network sent to UE ?

 

One of the solution for this is let UE get into sleeping mode for a certain period of time and wake up again checking if there is any data coming from the network and getting into sleeping mode again if there is no data and wake up again... repeaing this cycles. This kind of periodic repeatition of "sleep mode and wake up mode" is called DRX (Discontinous Reception".

 

Does it sound simple ? It may.. but in reality implemting DRX may not be as simple as you may expected because there should be well designed synchronization between UE and Network. In worst case,  Network tries to send some data while UE is in sleep mode and UE tries to wake up when there is no data to be recieved. To prevent this kind of worst case scenario, UE and Network has a well defined agreement about when UE has to be in sleep mode and when UE has to wake up. This agreement is defined in 3GPP TS36.321 Section 5.7 for connected mode, and TS36.304

Section 7.1 for idle mode.

 

Now let's look into a little bit detailed aspect of CDRX (Connected Mode DRX) operation. Followings are the list of aspects that I want to talk about

 

 

RRC Connection Reconfiguration for DRX Setting

 

In normal operation, UE has to be awake all the time and monitor PDCCH for every subframe meaning that it has to be awake all the time since it doesn't know exactly when the network will transmit the data for it. Logically there is no problem with this, but there would be a practical problem. It is power consumption issue on UE side. If UE is always up even when there is no data being transmitted to it from the network, it would be wasting the energy.

Then what would be the solution to save the energy on UE side. There may be several ways, but one of the most common way is to use DRX. DRX is a mechanism in which UE gets into sleep mode for a certain period of time and wake up for another period of time.

It sounds good. Then you may have a question. How can we synchronize UE-wakeup timing with Network transmission timing for the UE. If these two timing does not match, there can be a worst case where UE is awake but Network does not transmit anything or Network transmit something for the UE but UE is in sleep mode. One solution would be that Network decide when to let UE sleep and when towake it up and inform the timing to the UE using a RRC message.

 

 

In reality, Network informs UE of this timing using RRC ConnectionReconfiguration or RRC Connection Setup as follows (Following is the example configuration from RRC ConnectionReconfiguration, but you can do the samething in RRC Connection Setup as well).

 

    rrcConnectionReconfiguration-r8

     dedicatedInfoNASList: 1 item

         Item 0

             DedicatedInfoNAS: 27bd5ad9de05620ec101050403696d730902000000000000...

                ....

     radioResourceConfigDedicated

         drb-ToAddModList: 1 item

             ...

         mac-MainConfig: explicitValue (0)

             explicitValue

                 ul-SCH-Config

                     ...

                 drx-Config: setup (1)

                     setup

                         onDurationTimer: psf6 (5)

                         drx-InactivityTimer: psf1920 (20)

                         drx-RetransmissionTimer: psf16 (5)

                         longDRX-CycleStartOffset: sf1280 (13)

                             sf1280: 0

                         shortDRX

                             shortDRX-Cycle: sf10 (3)

                             drxShortCycleTimer: 10 shortDRX-Cycles

                 timeAlignmentTimerDedicated: infinity (7)

                 phr-Config: setup (1)

                     setup

                         ...

                 mac-MainConfig-v1020

         physicalConfigDedicated

             ....

 

Following table shows the meaning of each DRX parameters.

 

DRX Parameter

Description

DRX Cycle

The duration of one 'ON time' +  one 'OFF time'. (This value does not explicitely specified in RRC messages. This is calculated by the subframe time and longdrx-CycleStartOffset)

onDurationTimer

The duration of 'ON time' within one DRX cycle

drx-Inactivity timer

Specify how long UE should remain 'ON' after the reception of a PDCCH. When this timer is on UE remains in 'ON state' which may extend UE ON period into the period which is 'OFF' period otherwise. (See the figure for < case 2 > below)

drx-Retransmission timer

Specifies the maximum number of consecutive PDCCH subframes the UE should remain active to wait an incoming retransmission after the first available retransmission time

shortDRX-Cycle

DRX cycle which can be implemented within the 'OFF' period of a long DRX Cycle.(See the figure for < case 4 > below)

drxShortCycleTimer

The consecutive number of subframes the UE shall follow the short DRX cycle after the DRX Inactivity Timer has expired(See the figure for < case 4 > below)

 

Before we go into further detail, let me give you a couple of figures that would help your understanding.

 

< Case 1 > : Only Long DRX Cycle is configured and No PDCCH is received during the cycle.

 

 

< Case 2 > : Only Long DRX Cycle is configured and a PDCCH is received during a cycle (You will notice the real 'ON time' May get extended depending on DRX Inactivity Timer and when the PDCCH is recieved as shown in thick Blue line).

 

 

< Case 3 > : Only Long DRX Cycle is configured and a PDCCH and DRX Command MAC CE are received during a cycle (You will notice the real 'ON time' MAY get shorter depending on exactly when DRX Command MAC CE is received as shown in thick Blue line).

 

 

< Case 4 > : Both Long DRX Cycle and Short DRX Cycle are configured and No PDCCH is received during the cycle. This may be the most complicated case related to DRX cycle. Overall logic goes like this

    i) When C DRX is configured and the last DCI (PDCCH) arrived

    ii) drx-inactivityTimer starts and 'Wake-up status' continues until the drx-inactivityTimer expires.

    iii) After drx-inactivityTimer expired and the shortDrxCycle condition meet, the shortDrxCycle starts and drxShortCycleTimer starts.

    iv) If there is no DCI(no PDCCH) until drxShortCycleTimer expires, Long Drx Cycle starts.

    v) If any DCI (PDCCH) arrives during the wake-up period of any DRX cycle, go to step ii).

 

Following is one example showing this overall logic. This is just one example.. there can be almost infinite number of different combination is possible.

 

 

Let me give you a couple of question ?

    i) What would be the best period for sleeping and wake-up period ?

    ii) What kind of problem would happen if sleeping time is too short whereas wake-up time is very long ?

    iii) What kind of problem would happen if sleeping time is too long whereas wake-up time is very short ?

 

There would be no best answer for the question i). The answer will be different depending on situation.

The answer to question ii) would be that you would not save much energy on UE side since UE is awake most of the time.

The answer to question iii) would be that you would save much energy on UE side but there may be longer delay for data reception when network wants to send some data.

 

Now let's get into further details on exactly what happens on UE side when this DRX is working. This is very complicated process especially if both long DRX cycle and short DRX cycle are configured. Don't try to understand all the details at once. Just try to go through this process as often as possible. Try to understand only one if() statement at once.

 

if(drx-Config == setup) {

      if((Short DRX Cycle  is configured/activated)

           && ( [(SFN * 10) + subframe number] mod (shortDRX_Cycle) == (drxStartOffset) mod (shortDRX_Cycle)) {

                   start onDurationTimer;

      }

 

       if((Long DRX Cycle  is configured/activated)

           && ( [(SFN * 10) + subframe number] mod (longDRX_Cycle) == (drxStartOffset) ) {

                   start onDurationTimer;

      }

 

       if( (a HARQ RTT Timer expires in this subframe)  

           && (the data in the soft buffer of the corresponding HARQ process was not successfully decoded) {

                   start the drx-RetransmissionTimer for the corresponding HARQ process;

      }

 

       if( DRX Command MAC control element is received ) {

                   stop onDurationTimer;

                   stop drx-InactivityTimer;

      }

 

       if( (drx-InactivityTimer expires)  

           || (DRX Command MAC control element is received in this subframe) {

                   if (the Short DRX cycle is configured ) {   

                            start or restart drxShortCycleTimer;

                            use the Short DRX Cycle;

                   } else {

                            use the Long DRX cycle;

                   }

      }

 

       if( drxShortCycleTimer expires in this subframe ) {

                   use the Long DRX cycle;

      }

 

       if( during the Active Time, for a PDCCH-subframe,

           if the subframe is not required for uplink transmission for halfduplex FDD UE operation and

           if the subframe is not part of a configured measurement gap) {

                   monitor the PDCCH;

                   if (PDCCH indicates a DL transmission ||  DL assignment has been configured for this subframe ) {   

                            start the HARQ RTT Timer for the corresponding HARQ process;

                            stop the drx-RetransmissionTimer for the corresponding HARQ process;

                   }

 

                   if (the PDCCH indicates a new transmission (DL or UL) ) {   

                            start or restart drx-InactivityTimer;

                   }

      }

 

       if( not in the Active Time) {

                   CQI/PMI/RI on PUCCH and SRS shall not be reported;

       }

}

 

< Example >

 

The DRX parameters that I used are as follows. As you see, only Long DRX is configured in this example and I didn't enable the short DRX for simplicity.

 

 

Click here to download the analysis file.

 

Overall procedure that I applied is as follows.

    i) < Persistant Scheduling for both DL/UL >

    ii) RRC Connection Reconfiguration (Notifies the DRX configuration to UE)

    iii) Configure DRX parameters on Network simulator side

    iv) Receive RRC Connection Reconfiguration Complete

    v) Stop transmit PDCCH (DCI 0/DCI 1) from here to all the way to the end.

 

You may see from the spreadsheet that was linked above that the DRX ON does not start right away after step ii). It is because we still need to send PDCCH for step iv).

 

Just open up the spreadsheet linked above and follow through each row and at every row ask your self "Why this should DRX ON ?" or "Why this should be DRX OFF". This is the only way you can understand the DRX mechanism in full detail.

This example is the simplest case. so you have to make it sure to understand at least this example. I will keep adding examples with various complexity.

 

 

UE Capability Information for DRX Supportability

 

Even though CDRX is a very important feature in terms of energy saving on UE side and a lot of live network enables this feature, it is not the mandatory requirement on UE.  Therefore, even though most of UE would support this feature, there would be some UE (especially UE released at very early stage of LTE) that may not support this feature. So UE needs to inform the network about CDRX supportability and Network can optionally enable or disable based on UE capability and Network operator's requirement. CDRX supportability is informed to network via UE Capability Information message as shown below.

 

ueCapabilityInformation-r8

     ue-CapabilityRAT-ContainerList: 1 item

         Item 0

             UE-CapabilityRAT-Container

                 rat-Type: eutra (0)

                 ueCapabilityRAT-Container: c9980050c08616082058b58fff15b1ffe2fe3ffc53c7ff8b...

                     UE-EUTRA-Capability

                         accessStratumRelease: rel10 (2)

                         ue-Category: 4

                         pdcp-Parameters

                         ..

                         phyLayerParameters

                             ....

                         rf-Parameters

                             ....

                         measParameters

                             ....

                         featureGroupIndicators: 7fcffeb2

                             0... .... = Indicator 1: ...

                             .1.. .... = Indicator 2: ...

                             ..1. .... = Indicator 3: ...

                             ...1 .... = Indicator 4: Short DRX cycle - Supported

                             .... 1... = Indicator 5: Long DRX cycle;

                                                   DRX command MAC control element - Supported

                             .... .1.. = Indicator 6: ....

 

 

Some misconception about CDRX

 

I often see some of the misconception about CDRX and followings are some of the examples

  • If Network enables CDRX configuration in RRC Connection Reconfiguration message, UE MUST go to sleep and eNB MUST stop transmitting the data IN ANY SITUATION according to the specified Cycle. But this is not true. The precondition to go into DRX mode (sleep mode) is that there is no data(PDCCH, MAC CE) during the onTime. If there is any data transmitted to UE during onTime, the onTime gets extended. In worst case, if there is data being continuously transmitted to UE, UE/eNB will never gets into the sleep mode.
  • If CDRX gets into sleep mode, UE energy consumption should decrease. In theory, this is true and this is one of the most important motivation of employing CDRX. However, you may see some UE (especially at early stage of development) that does not show any outstanding reduction of energy consumption even when the DRX is in sleep period. To make the best use of CDRX, UE maker (and chipset maker) properly implement the chipset in such a way that UE Radio Stack is guaranteed to go into sleep mode (turning off most of unecessary processes and timers etc).

 

 

How to test CDRX

 

Configuring DRX in RRC Connection Reconfiguration would be relatively simple, but verifying on whether the DRX is properly working is not that simple. Since this happens at the subframe timing, it is not possible to test the operation with eye balling. There are several steps you have to check.

  • i) Make it sure there is no data traffic long enough to trigger CDRX sleep mode (you may use wireshark to verify this)
  • ii) If you have access to eNB log, you have to check the data transmission status at each subframe and confirm that there is no data transmission at MAC/PHY level.
  • iii) If you have access to UE log, you have to check the data reception or SR(Scheduling Request)/BSR(Buffer Status Report) for long enough to trigger CDRX sleep mode.
  • iv) The most conclusive verification should come from the measurement of real energy consumption on UE side. Even though all the previous conditions are met, UE energy consumption (current consumption) does decrease during CDRX sleep mode there is no point of using this technology. You would see current consumption pattern as shown below (marked as C-DRX) if CDRX is properly working. If you want to do exact measurement the sleeping /wake-up time on UE side during CDRX operation, you would need a current measurement equipment that supports very high sampling rate (very short sampling time). I used a Keysight(Agilent) N67XX family for this test.

 

Following illustration shows overall pattern of current consumption during the typical operation of mobile phone. In this page, just pay attention to the section labeled as C-DRX.

 

 

Following is an example of real current consumption measurement during the DRX cycle (if you use the high sampling power analyzer) you can measure exact timing of wake-up /sleeping time. You would notice that depending on DRX configuration the baseline current consumption would be different and the decreasing the baseline would be one of the important optimization parameters in terms of energy consumption.

 

저작자 표시 비영리 변경 금지
신고

WRITTEN BY
빅터크룸
머 먹고 사냐.....

받은 트랙백이 없고 , 댓글이 없습니다.
secret

http://know-lte.blogspot.kr/2016/07/cdrx-connected-mode-drx.html



Connected Mode DRX (CDRX)

In addition to Idle mode DRX, LTE had RRC mode DRX as well also known as Connected Mode DRX (CDRX), the purpose of both the DRX is same to conserve the battery power. During RRC connected state when there is no data transmission in either direction (UL/DL) UE goes into the DRX mode. It starts monitoring the PDCCH channel discontinuously in other words UE is in sleep and wake cycle.

Without the DRX the UE needs to monitor PDCCH in every subframe to check if there is downlink data available which drains the battery fast.


Without DRX
Battery Consumption without DRX

In the figure above, without DRX feature the UE is monitoring the PDCCH every subframe, so the UE will never be in the sleep state.

With DRX support, The UE monitors PDCCH at regular intervals during wake cycle. The DRX configurations are configured by the network in RRC Connection Setup request and RRC connection reconfiguration request. Here is the drx configuration:

rrcConnectionReconfiguration
....
    ul-SCH-Config
    ...
        DRX-Config ::= CHOICE {
            release     NULL,
            setup       SEQUENCE {
                onDurationTimer     ENUMERATED {
psf1, psf2, psf3, psf4, psf5, psf6, psf8, psf10, psf20, psf30, psf40, psf50, psf60, psf80, psf100, psf200},
                drx-InactivityTimer ENUMERATED {
psf1, psf2, psf3, psf4, psf5, psf6, psf8, psf10, psf20, psf30, psf40,psf50, psf60, psf80, psf100, psf200, psf300, psf500, psf750, psf1280, psf1920, psf2560, spare10, spare9, spare8, spare7, spare6,
                                    spare5, spare4, spare3, spare2, spare1},
                drx-RetransmissionTimer ENUMERATED {
psf1, psf2, psf4, psf6, psf8, psf16, psf24, psf33},
                longDRX-CycleStartOffset  CHOICE {
                                    sf10  INTEGER(0..9),
                                    sf20  INTEGER(0..19),
                                    sf32  INTEGER(0..31),
                                    sf40  INTEGER(0..39),
                                    sf64  INTEGER(0..63),
                                    sf80  INTEGER(0..79),
                                    sf128 INTEGER(0..127),
                                    sf160 INTEGER(0..159),
                                    sf256 INTEGER(0..255),
                                    sf320 INTEGER(0..319),
                                    sf512 INTEGER(0..511),
                                    sf640 INTEGER(0..639),
                                    sf1024      INTEGER(0..1023),
                                    sf1280      INTEGER(0..1279),
                                    sf2048      INTEGER(0..2047),
                                    sf2560      INTEGER(0..2559)
                  },
                  shortDRX    SEQUENCE {
                                    shortDRX-Cycle ENUMERATED     {
                                    sf2, sf5, sf8, sf10, sf16, sf20,
                                    sf32, sf40, sf64, sf80, sf128, sf160,
                                    sf256, sf320, sf512, sf640},
                  drxShortCycleTimer      INTEGER (1..16)
            }          

DRX cycle LTE
DRX Cycle
       IEs of rrcConnectionReconfiguration with respect to drx-config setup is discussed here: 
DRX Cycle:- is the periodic repetition of ON Duration (Monitoring PDCCH) and OFF Duration (DRX activity).
DRX Inactivity Timer: - specifies the time in terms of TTI duration after successful decoded PDCCH, to go again in OFF Duration.
On Duration Timer: Specifies the number of consecutive PDCCH subframe(s) need to be decoded after wakeup from the DRX Cycle.
DRX Retransmission Timer:  Specifies the consecutive number of PDCCH subframe(s) to monitor when retransmission is expected by the UE. 
DRX short cycle: It is the first DRX cycle that the UE enters after successful expiration of DRX inactivity timer. UE will be in the short DRX cycle till the expiration of DRX short cycle timer after that it will be in Long DRX cycle. 
DRX Short Cycle Timer: This parameter specifies the number of consecutive subframe(s) the UE shall follow the short DRX cycle after the DRX Inactivity Timer has expired.


Lets understand CDRX with example: 

From RRC connection reconfiguration the following DRX parameters are configured

DrxInactivityTimer : 6
OnDurationTimer : 2
shortDrxTimer : 6
LongDrxCycle : 12
drxStartOffset : 0
drxShortCycleTimer : 2 


CDRX- Connected Mode DRX

 Here UE is in connected mode and monitor PDCCH, After successful attempt of DL data, the DrxInactivityTimer started. As per example here it starts for 6 subframes. If there is any UL or DL data transmission during DrxInactivityTimer the timer restarts again.
If DrxInactivityTimer expired, UE now enters the DRX cycle. Power saving mode started from here. It starts the ShortDrxCycle here it is of 6 subframes and OnDuration is 2sf. 
DrxShortCycleTimer = ShortDrxCycle *   DrxShortCycleTimer. So it runs for 12sf. 
After expiration of DrxShortCycleTimer UE now enters the LongDrxCycle. 
This process continues till RRC inactivity timer expires. Once the RRC inactivity timer expires the UE moved into the IDLE mode DRX.


저작자 표시 비영리 변경 금지
신고

WRITTEN BY
빅터크룸
머 먹고 사냐.....

받은 트랙백이 없고 , 댓글이 없습니다.
secret
EPS mobility management messages
Message typeDirectionMessageReference
0x4266to UEAttach accept8.2.1
0x4367to NetworkAttach complete8.2.2
0x4468to UEAttach reject8.2.3
0x4165to NetworkAttach request8.2.4
0x5c92to NetworkAuthentication failure8.2.5
0x5484to UEAuthentication reject8.2.6
0x5282to UEAuthentication request8.2.7
0x5383to NetworkAuthentication response8.2.8
0x64100to UECS Service notification8.2.9
0x4670to UEDetach accept (UE originating detach)8.2.10.1
0x4670to NetworkDetach accept (UE terminated detach)8.2.10.2
0x4569to NetworkDetach request (UE originating detach)8.2.11.1
0x4569to UEDetach request (UE terminated detach)8.2.11.2
0x6298to UEDownlink NAS transport8.2.12
0x6197to UEEMM information8.2.13
0x6096bothEMM status8.2.14
0x4c76to NetworkExtended service request8.2.15
0x5080to UEGUTI reallocation command8.2.16
0x5181to NetworkGUTI reallocation complete8.2.17
0x5585to UEIdentity request8.2.18
0x5686to NetworkIdentity response8.2.19
0x5d93to UESecurity mode command8.2.20
0x5e94to NetworkSecurity mode complete8.2.21
0x5f95to NetworkSecurity mode reject8.2.22
bothSecurity protected NAS message8.2.23
0x4d77to UEService reject8.2.24
to NetworkService request8.2.25
0x4973to UETracking area update accept8.2.26
0x4a74to NetworkTracking area update complete8.2.27
0x4b75to UETracking area update reject8.2.28
0x4872to NetworkTracking area update request8.2.29
0x6399to NetworkUplink NAS transport8.2.30
0x68104to UEDownlink generic NAS transport8.2.31
0x69105to NetworkUplink generic NAS transport8.2.32
Nb = 34


EPS session management messages
Message typeDirectionMessageReference
0xc6198to NetworkActivate dedicated EPS bearer context accept8.3.1
0xc7199to NetworkActivate dedicated EPS bearer context reject8.3.2
0xc5197to UEActivate dedicated EPS bearer context request8.3.3
0xc2194to NetworkActivate default EPS bearer context accept8.3.4
0xc3195to NetworkActivate default EPS bearer context reject8.3.5
0xc1193to UEActivate default EPS bearer context request8.3.6
0xd5213to UEBearer resource allocation reject8.3.7
0xd4212to NetworkBearer resource allocation request8.3.8
0xd7215to UEBearer resource modification reject8.3.9
0xd6214to NetworkBearer resource modification request8.3.10
0xce206to NetworkDeactivate EPS bearer context accept8.3.11
0xcd205to UEDeactivate EPS bearer context request8.3.12
0xd9217to UEESM information request8.3.13
0xda218to NetworkESM information response8.3.14
0xe8232bothESM status8.3.15
0xca202to NetworkModify EPS bearer context accept8.3.16
0xcb203to NetworkModify EPS bearer context reject8.3.17
0xc9201to UEModify EPS bearer context request8.3.18
0xdb219to UENotification8.3.18A
0xd1209to UEPDN connectivity reject8.3.19
0xd0208to NetworkPDN connectivity request8.3.20
0xd3211to UEPDN disconnect reject8.3.21
0xd2210to NetworkPDN disconnect request8.3.22
Nb = 23


Presence (24.007)

M
Mandatory
O
Optional
C
Conditional

Total length X,Y-Z

X
Minimum length with mandatory IEI only
Y
Minimum length with all IEIs
Z
Maximum length with all IEIs

EPS mobility management message

8.2.1 Attach accept

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Attach accept message identityMessage type
9.8
MV1
EPS attach resultEPS attach result
9.9.3.10
MV1/2
Spare half octetSpare half octet
9.9.2.9
MV1/2
T3412 valueGPRS timer
9.9.3.16
MV1
TAI listTracking area identity list
9.9.3.33
MLV7-97
ESM message containerESM message container
9.9.3.15
MLV-E5-n
50GUTIEPS mobile identity
9.9.3.12
OTLV13
13Location area identificationLocation area identification
9.9.2.2
OTV6
23MS identityMobile identity
9.9.2.3
OTLV7-10
53EMM causeEMM cause
9.9.3.9
OTV2
17T3402 valueGPRS timer
9.9.3.16
OTV2
59T3423 valueGPRS timer
9.9.3.16
OTV2
4AEquivalent PLMNsPLMN list
9.9.2.8
OTLV5-47
34Emergency number listEmergency number list
9.9.3.37
OTLV5-50
64EPS network feature supportEPS network feature support
9.9.3.12A
OTLV3
F-Additional update resultAdditional update result
9.9.3.0A
OTV1
5ET3412 extended valueGPRS timer 3
9.9.3.16B
OTLV3
Nb IEI = 19M = 8, O = 1116,65-n


8.2.2 Attach complete

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Attach complete message identityMessage type
9.8
MV1
ESM message containerESM message container
9.9.3.15
MLV-E5-n
Nb IEI = 4M = 47-n


8.2.3 Attach reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Attach reject message identityMessage type
9.8
MV1
EMM causeEMM cause
9.9.3.9
MV1
78ESM message containerESM message container
9.9.3.15
OTLV-E6-n
5FT3346 valueGPRS timer 2
9.9.3.16A
OTLV3
16T3402 valueGPRS timer 2
9.9.3.16A
OTLV3
Nb IEI = 7M = 4, O = 33,15-n


8.2.4 Attach request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Attach request message identityMessage type
9.8
MV1
EPS attach typeEPS attach type
9.9.3.11
MV1/2
NAS key set identifierNAS key set identifier
9.9.3.21
MV1/2
EPS mobile identityEPS mobile identity
9.9.3.12
MLV5-12
UE network capabilityUE network capability
9.9.3.34
MLV3-14
ESM message containerESM message container
9.9.3.15
MLV-E5-n
19Old P-TMSI signatureP-TMSI signature
9.9.3.26
OTV4
50Additional GUTIEPS mobile identity
9.9.3.12
OTLV13
52Last visited registered TAITracking area identity
9.9.3.32
OTV6
5CDRX parameterDRX parameter
9.9.3.8
OTV3
31MS network capabilityMS network capability
9.9.3.20
OTLV4-10
13Old location area identificationLocation area identification
9.9.2.2
OTV6
9-TMSI statusTMSI status
9.9.3.31
OTV1
11Mobile station classmark 2Mobile station classmark 2
9.9.2.4
OTLV5
20Mobile station classmark 3Mobile station classmark 3
9.9.2.5
OTLV2-34
40Supported CodecsSupported Codec List
9.9.2.10
OTLV5-n
F-Additional update typeAdditional update type
9.9.3.0B
OTV1
5DVoice domain preference and UE's usage settingVoice domain preference and UE's usage setting
9.9.3.44
OTLV3
D-Device propertiesDevice properties
9.9.2.0A
OTV1
E-Old GUTI typeGUTI type
9.9.3.45
OTV1
C-MS network feature supportMS network feature support
9.9.3.20A
OTV1
10TMSI based NRI containerNetwork resource identifier container
9.9.3.24A
OTLV4
Nb IEI = 24M = 8, O = 1616,76-n


8.2.5 Authentication failure

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Authentication failure message typeMessage type
9.8
MV1
EMM causeEMM cause
9.9.3.9
MV1
30Authentication failure parameterAuthentication failure parameter
9.9.3.1
OTLV16
Nb IEI = 5M = 4, O = 13,19-19


8.2.6 Authentication reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Authentication reject message typeMessage type
9.8
MV1
Nb IEI = 3M = 32


8.2.7 Authentication request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Authentication request message typeMessage type
9.8
MV1
NAS key set identifier ASMENAS key set identifier
9.9.3.21
MV1/2
Spare half octetSpare half octet
9.9.2.9
MV1/2
Authentication parameter RAND (EPS challenge)Authentication parameter RAND
9.9.3.3
MV16
Authentication parameter AUTN (EPS challenge)Authentication parameter AUTN
9.9.3.2
MLV17
Nb IEI = 7M = 736


8.2.8 Authentication response

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Authentication response message typeMessage type
9.8
MV1
Authentication response parameterAuthentication response parameter
9.9.3.4
MLV5-17
Nb IEI = 4M = 47-19


8.2.9 CS service notification

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
CS service notification message identityMessage type
9.8
MV1
Paging identityPaging identity
9.9.3.25A
MV1
60CLICLI
9.9.3.38
OTLV3-14
61SS CodeSS Code
9.9.3.39
OTV2
62LCS indicatorLCS indicator
9.9.3.40
OTV2
63LCS client identityLCS client identity
9.9.3.41
OTLV3-257
Nb IEI = 8M = 4, O = 43,13-278


8.2.10.1 Detach accept (UE originating detach)

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Detach accept message identityMessage type
9.8
MV1
Nb IEI = 3M = 32


8.2.10.2 Detach accept (UE terminated detach)

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Detach accept message identityMessage type
9.8
MV1
Nb IEI = 3M = 32


8.2.11.1 Detach request (UE originating detach)

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Detach request message identityMessage type
9.8
MV1
Detach typeDetach type
9.9.3.7
MV1/2
NAS key set identifierNAS key set identifier
9.9.3.21
MV1/2
EPS mobile identityEPS mobile identity
9.9.3.12
MLV5-12
Nb IEI = 6M = 68-15


8.2.11.2 Detach request (UE terminated detach)

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Detach request message identityMessage type
9.8
MV1
Detach typeDetach type
9.9.3.7
MV1/2
Spare half octetSpare half octet
9.9.2.9
MV1/2
53EMM causeEMM cause
9.9.3.9
OTV2
Nb IEI = 6M = 5, O = 13,5-5


8.2.12 Downlink NAS Transport

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Downlink NAS transport message identityMessage type
9.8
MV1
NAS message containerNAS message container
9.9.3.22
MLV3-252
Nb IEI = 4M = 45-254


8.2.13 EMM information

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
EMM information message identityMessage type
9.8
MV1
43Full name for networkNetwork name
9.9.3.24
OTLV3-n
45Short name for networkNetwork name
9.9.3.24
OTLV3-n
46Local time zoneTime zone
9.9.3.29
OTV2
47Universal time and local time zoneTime zone and time
9.9.3.30
OTV8
49Network daylight saving timeDaylight saving time
9.9.3.6
OTLV3
Nb IEI = 8M = 3, O = 52,21-n


8.2.14 EMM status

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
EMM status message identityMessage type
9.8
MV1
EMM causeEMM cause
9.9.3.9
MV1
Nb IEI = 4M = 43


8.2.15 Extended service request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Extended service request message identityMessage type
9.8
MV1
Service typeService type
9.9.3.27
MV1/2
NAS key set identifierNAS key set identifier
9.9.3.21
MV1/2
M-TMSIMobile identity
9.9.2.3
MLV6
B-CSFB responseCSFB response
9.9.3.5
CTV1
57EPS bearer context statusEPS bearer context status
9.9.2.1
OTLV4
D-Device propertiesDevice properties
9.9.2.0A
OTV1
Nb IEI = 9M = 6, C = 1, O = 29,15-15


8.2.16 GUTI reallocation command

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
GUTI reallocation command message identityMessage type
9.8
MV1
GUTIEPS mobile identity
9.9.3.12
MLV12
54TAI listTracking area identity list
9.9.3.33
OTLV8-98
Nb IEI = 5M = 4, O = 114,22-112


8.2.17 GUTI reallocation complete

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
GUTI reallocation complete message identityMessage type
9.8
MV1
Nb IEI = 3M = 32


8.2.18 Identity request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Identity request message identityMessage type
9.8
MV1
Identity typeIdentity type 2
9.9.3.17
MV1/2
Spare half octetSpare half octet
9.9.2.9
MV1/2
Nb IEI = 5M = 53


8.2.19 Identity response

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Identity response messageMessage type
9.8
MV1
Mobile identityMobile identity
9.9.2.3
MLV4-10
Nb IEI = 4M = 46-12


8.2.20 Security mode command

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Security mode command message identityMessage type
9.8
MV1
Selected NAS security algorithmsNAS security algorithms
9.9.3.23
MV1
NAS key set identifierNAS key set identifier
9.9.3.21
MV1/2
Spare half octetSpare half octet
9.9.2.9
MV1/2
Replayed UE security capabilitiesUE security capability
9.9.3.36
MLV3-6
C-IMEISV requestIMEISV request
9.9.3.18
OTV1
55Replayed nonce UENonce
9.9.3.25
OTV5
56Nonce MMENonce
9.9.3.25
OTV5
Nb IEI = 10M = 7, O = 37,18-21


8.2.21 Security mode complete

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Security mode complete message identityMessage type
9.8
MV1
23IMEISVMobile identity
9.9.2.3
OTLV11
Nb IEI = 4M = 3, O = 12,13-13


8.2.22 Security mode reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Security mode reject message identityMessage type
9.8
MV1
EMM causeEMM cause
9.9.3.9
MV1
Nb IEI = 4M = 43


8.2.23 Security protected NAS message

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Message authentication codeMessage authentication code
9.5
MV4
Sequence numberSequence number
9.6
MV1
NAS messageNAS message
9.7
MV1-n
Nb IEI = 5M = 57-n


8.2.24 Service reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Service reject message identityMessage type
9.8
MV1
EMM causeEMM cause
9.9.3.9
MV1
5BT3442 valueGPRS timer
9.9.3.16
CTV2
5FT3346 valueGPRS timer 2
9.9.3.16A
OTLV3
Nb IEI = 6M = 4, C = 1, O = 13,8-8


8.2.25 Service request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
KSI and sequence numberKSI and sequence number
9.9.3.19
MV1
Message authentication code (short)Short MAC
9.9.3.28
MV2
Nb IEI = 4M = 44


8.2.26 Tracking area update accept

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Tracking area update accept message identityMessage type
9.8
MV1
EPS update resultEPS update result
9.9.3.13
MV1/2
Spare half octetSpare half octet
9.9.2.9
MV1/2
5AT3412 valueGPRS timer
9.9.3.16
OTV2
50GUTIEPS mobile identity
9.9.3.12
OTLV13
54TAI listTracking area identity list
9.9.3.33
OTLV8-98
57EPS bearer context statusEPS bearer context status
9.9.2.1
OTLV4
13Location area identificationLocation area identification
9.9.2.2
OTV6
23MS identityMobile identity
9.9.2.3
OTLV7-10
53EMM causeEMM cause
9.9.3.9
OTV2
17T3402 valueGPRS timer
9.9.3.16
OTV2
59T3423 valueGPRS timer
9.9.3.16
OTV2
4AEquivalent PLMNsPLMN list
9.9.2.8
OTLV5-47
34Emergency number listEmergency number list
9.9.3.37
OTLV5-50
64EPS network feature supportEPS network feature support
9.9.3.12A
OTLV3
F-Additional update resultAdditional update result
9.9.3.0A
OTV1
5ET3412 extended valueGPRS timer 3
9.9.3.16B
OTLV3
Nb IEI = 19M = 5, O = 143,66-246


8.2.27 Tracking area update complete

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Tracking area update complete message identityMessage type
9.8
MV1
Nb IEI = 3M = 32


8.2.28 Tracking area update reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
message identityMessage type
9.8
MV1
EMM causeEMM cause
9.9.3.9
MV1
5FT3346 valueGPRS timer 2
9.9.3.16A
OTLV3
Nb IEI = 5M = 4, O = 13,6-6


8.2.29 Tracking area update request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Tracking area update request message identityMessage type
9.8
MV1
EPS update typeEPS update type
9.9.3.14
MV1/2
NAS key set identifierNAS key set identifier
9.9.3.21
MV1/2
Old GUTIEPS mobile identity
9.9.3.12
MLV12
B-Non-current native NAS key set identifierNAS key set identifier
9.9.3.21
OTV1
8-GPRS ciphering key sequence numberCiphering key sequence number
9.9.3.4a
OTV1
19Old P-TMSI signatureP-TMSI signature
9.9.3.26
OTV4
50Additional GUTIEPS mobile identity
9.9.3.12
OTLV13
55NonceUENonce
9.9.3.25
OTV5
58UE network capabilityUE network capability
9.9.3.34
OTLV4-15
52Last visited registered TAITracking area identity
9.9.3.32
OTV6
5CDRX parameterDRX parameter
9.9.3.8
OTV3
A-UE radio capability information update neededUE radio capability information update needed
9.9.3.35
OTV1
57EPS bearer context statusEPS bearer context status
9.9.2.1
OTLV4
31MS network capabilityMS network capability
9.9.3.20
OTLV4-10
13Old location area identificationLocation area identification
9.9.2.2
OTV6
9-TMSI statusTMSI status
9.9.3.31
OTV1
11Mobile station classmark 2Mobile station classmark 2
9.9.2.4
OTLV5
20Mobile station classmark 3Mobile station classmark 3
9.9.2.5
OTLV2-34
40Supported CodecsSupported Codec List
9.9.2.10
OTLV5-n
F-Additional update typeAdditional update type
9.9.3.0B
OTV1
5DVoice domain preference and UE's usage settingVoice domain preference and UE's usage setting
9.9.3.44
OTLV3
E-Old GUTI typeGUTI type
9.9.3.45
OTV1
D-Device propertiesDevice properties
9.9.2.0A
OTV1
C-MS network feature supportMS network feature support
9.9.3.20A
OTV1
10TMSI based NRI containerNetwork resource identifier container
9.9.3.24A
OTLV4
Nb IEI = 28M = 6, O = 2215,91-n


8.2.30 Uplink NAS Transport

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Uplink NAS transport message identityMessage type
9.8
MV1
NAS message containerNAS message container
9.9.3.22
MLV3-252
Nb IEI = 4M = 45-254


8.2.31 Downlink generic NAS transport

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Downlink generic NAS transport message identityMessage type
9.8
MV1
Generic message container typeGeneric message container type
9.9.3.42
MV1
Generic message containerGeneric message container
9.9.3.43
MLV-E3-n
65Additional informationAdditional information
9.9.2.0
OTLV3-n
Nb IEI = 6M = 5, O = 16,9-n


8.2.32 Uplink generic NAS transport

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
Security header typeSecurity header type
9.3.1
MV1/2
Uplink generic NAS transport message identityMessage type
9.8
MV1
Generic message container typeGeneric message container type
9.9.3.42
MV1
Generic message containerGeneric message container
9.9.3.43
MLV-E3-n
65Additional informationAdditional information
9.9.2.0
OTLV3-n
Nb IEI = 6M = 5, O = 16,9-n


EPS session management message

8.3.1 Activate dedicated EPS bearer context accept

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Activate dedicated EPS bearer context accept message identityMessage type
9.8
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 5M = 4, O = 13,6-256


8.3.2 Activate dedicated EPS bearer context reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Activate dedicated EPS bearer context reject message identityMessage type
9.8
MV1
ESM causeESM cause
9.9.4.4
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 6M = 5, O = 14,7-257


8.3.3 Activate dedicated EPS bearer context request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Activate dedicated EPS bearer context request message identityMessage type
9.8
MV1
Linked EPS bearer identityLinked EPS bearer identity
9.9.4.6
MV1/2
Spare half octetSpare half octet
9.9.2.9
MV1/2
EPS QoSEPS quality of service
9.9.4.3
MLV2-14
TFTTraffic flow template
9.9.4.16
MLV2-256
5DTransaction identifierTransaction identifier
9.9.4.17
OTLV3-4
30Negotiated QoSQuality of service
9.9.4.12
OTLV14-22
32Negotiated LLC SAPILLC service access point identifier
9.9.4.7
OTV2
8-Radio priorityRadio priority
9.9.4.13
OTV1
34Packet flow IdentifierPacket flow Identifier
9.9.4.8
OTLV3
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 14M = 8, O = 68,34-559


8.3.4 Activate default EPS bearer context accept

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Activate default EPS bearer context accept message identityMessage type
9.8
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 5M = 4, O = 13,6-256


8.3.5 Activate default EPS bearer context reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Activate default EPS bearer context reject message identityMessage type
9.8
MV1
ESM causeESM cause
9.9.4.4
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 6M = 5, O = 14,7-257


8.3.6 Activate default EPS bearer context request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Activate default EPS bearer context request message identityMessage type
9.8
MV1
EPS QoSEPS quality of service
9.9.4.3
MLV2-14
Access point nameAccess point name
9.9.4.1
MLV2-101
PDN addressPDN address
9.9.4.9
MLV6-14
5DTransaction identifierTransaction identifier
9.9.4.17
OTLV3-4
30Negotiated QoSQuality of service
9.9.4.12
OTLV14-22
32Negotiated LLC SAPILLC service access point identifier
9.9.4.7
OTV2
8-Radio priorityRadio priority
9.9.4.13
OTV1
34Packet flow IdentifierPacket flow Identifier
9.9.4.8
OTLV3
5EAPN-AMBRAPN aggregate maximum bit rate
9.9.4.2
OTLV4-8
58ESM causeESM cause
9.9.4.4
OTV2
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
B-Connectivity typeConnectivity type
9.9.4.2A
OTV1
Nb IEI = 16M = 7, O = 913,46-428


8.3.7 Bearer resource allocation reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Bearer resource allocation reject message identityMessage type
9.8
MV1
ESM causeESM cause
9.9.4.4
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
37T3396 valueGPRS timer 3
9.9.3.16B
OTLV3
Nb IEI = 7M = 5, O = 24,10-260


8.3.8 Bearer resource allocation request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Bearer resource allocation request message identityMessage type
9.8
MV1
Linked EPS bearer identityLinked EPS bearer identity
9.9.4.6
MV1/2
Spare half octetSpare half octet
9.9.2.9
MV1/2
Traffic flow aggregateTraffic flow aggregate description
9.9.4.15
MLV2-256
Required traffic flow QoSEPS quality of service
9.9.4.3
MLV2-14
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
C-Device propertiesDevice properties
9.9.2.0A
OTV1
Nb IEI = 10M = 8, O = 28,12-528


8.3.9 Bearer resource modification reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Bearer resource modification reject message identityMessage type
9.8
MV1
ESM causeESM cause
9.9.4.4
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
37T3396 valueGPRS timer 3
9.9.3.16B
OTLV3
Nb IEI = 7M = 5, O = 24,10-260


8.3.10 Bearer resource modification request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Bearer resource modification request message identityMessage type
9.8
MV1
EPS bearer identity for packet filterLinked EPS bearer identity
9.9.4.6
MV1/2
Spare half octetSpare half octet
9.9.2.9
MV1/2
Traffic flow aggregateTraffic flow aggregate description
9.9.4.15
MLV2-256
5BRequired traffic flow QoSEPS quality of service
9.9.4.3
OTLV3-15
58ESM causeESM cause
9.9.4.4
OTV2
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
C-Device propertiesDevice properties
9.9.2.0A
OTV1
Nb IEI = 11M = 7, O = 46,15-531


8.3.11 Deactivate EPS bearer context accept

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Deactivate EPS bearer context accept message identityMessage type
9.8
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 5M = 4, O = 13,6-256


8.3.12 Deactivate EPS bearer context request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Deactivate EPS bearer context request message identityMessage type
9.8
MV1
ESM causeESM cause
9.9.4.4
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
37T3396 valueGPRS timer 3
9.9.3.16B
OTLV3
Nb IEI = 7M = 5, O = 24,10-260


8.3.13 ESM information request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
ESM information request message identityMessage type
9.8
MV1
Nb IEI = 4M = 43


8.3.14 ESM information response

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
ESM information response message identityMessage type
9.8
MV1
28Access point nameAccess point name
9.9.4.1
OTLV3-102
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 6M = 4, O = 23,9-358


8.3.15 ESM status

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
ESM status message identityMessage type
9.8
MV1
ESM causeESM cause
9.9.4.4
MV1
Nb IEI = 5M = 54


8.3.16 Modify EPS bearer context accept

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Modify EPS bearer context accept message identityMessage type
9.8
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 5M = 4, O = 13,6-256


8.3.17 Modify EPS bearer context reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Modify EPS bearer context reject message identityMessage type
9.8
MV1
ESM causeESM cause
9.9.4.4
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 6M = 5, O = 14,7-257


8.3.18 Modify EPS bearer context request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Modify EPS bearer context request message identityMessage type
9.8
MV1
5BNew EPS QoSEPS quality of service
9.9.4.3
OTLV3-15
36TFTTraffic flow template
9.9.4.16
OTLV3-257
30New QoSQuality of service
9.9.4.12
OTLV14-22
32Negotiated LLC SAPILLC service access point identifier
9.9.4.7
OTV2
8-Radio priorityRadio priority
9.9.4.13
OTV1
34Packet flow IdentifierPacket flow Identifier
9.9.4.8
OTLV3
5EAPN-AMBRAPN aggregate maximum bit rate
9.9.4.2
OTLV4-8
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 12M = 4, O = 83,36-564


8.3.18A Notification

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
Notification message identityMessage type
9.8
MV1
Notification indicatorNotification indicator
9.9.4.7A
MLV2
Nb IEI = 5M = 55


8.3.19 PDN connectivity reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
PDN connectivity reject message identityMessage type
9.8
MV1
ESM causeESM cause
9.9.4.4
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
37T3396 valueGPRS timer 3
9.9.3.16B
OTLV3
Nb IEI = 7M = 5, O = 24,10-260


8.3.20 PDN connectivity request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
PDN connectivity request message identityMessage type
9.8
MV1
Request typeRequest type
9.9.4.14
MV1/2
PDN typePDN type
9.9.4.10
MV1/2
D-ESM information transfer flagESM information transfer flag
9.9.4.5
OTV1
28Access point nameAccess point name
9.9.4.1
OTLV3-102
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
C-Device propertiesDevice properties
9.9.2.0A
OTV1
Nb IEI = 10M = 6, O = 44,12-361


8.3.21 PDN disconnect reject

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
PDN disconnect reject message identityMessage type
9.8
MV1
ESM causeESM cause
9.9.4.4
MV1
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 6M = 5, O = 14,7-257


8.3.22 PDN disconnect request

IEIInformation ElementType/ReferencePresenceFormatLength
Protocol discriminatorProtocol discriminator
9.2
MV1/2
EPS bearer identityEPS bearer identity
9.3.2
MV1/2
Procedure transaction identityProcedure transaction identity
9.4
MV1
PDN disconnect request message identityMessage type
9.8
MV1
Linked EPS bearer identityLinked EPS bearer identity
9.9.4.6
MV1/2
Spare half octetSpare half octet
9.9.2.9
MV1/2
27Protocol configuration optionsProtocol configuration options
9.9.4.11
OTLV3-253
Nb IEI = 7M = 6, O = 14,7-257



Ref. http://niviuk.free.fr/lte_nas.php

저작자 표시 비영리 변경 금지
신고

WRITTEN BY
빅터크룸
머 먹고 사냐.....

LTE, NAS
받은 트랙백이 없고 , 댓글이 없습니다.
secret

Contents of Response APDU

CodeLengthDescriptionM/O
DataLrResponse data stringOptional
SW11Status byte 1Mandatory
SW21Status byte 2Mandatory


SW1, SW2를 Status Word라 부르며, 다음과 같은 응답값을 가진다.

Normal processing

SW1SW2Description 
9000- Normal ending of the command
91XX- Normal ending of the command, with extra information from the proactive UICC containing a command for the terminal. Length 'XX' of the response data.
92XX- Normal ending of the command, with extra information concerning an ongoing data transfer session.


Postponed processing

SW1SW2Description 
9300- SIM Application Toolkit is busy. Command cannot be executed at present, further normal commands are allowed.


Warning

SW1SW2Description 
6200- No information given, state of non volatile memory unchanged.
6281- Part of returned data may be corrupted.
6282- End of file/record reached before reading Le bytes.
6283- Selected file invalidated.
6285- Selected file in termination state.
62F1- More data available.
62F2- More data available and proactive command pending.
62F3- Response data available.
63F1- More data expected.
63F2- More data expected and proactive command pending.
63CX- Command successful but after using an internal update retry roution 'X' times
- Verification failed, 'X' retries remaining (see note)
NOTE:For the VERIFY PIN command, SW1SW2 indicates that the command was successful but the PIN was not correct and there are 'X' retries left. For all other commands it indicates the number of internal retries performed by the card to complete the command.


Execution errors

SW1SW2Description 
6400- No information given, state of non-volatile memory unchanged.
6500- No information given, state of non-volatile memory changed.
6581- Memory problem.


Checking errors

SW1SW2Description 
6700- Wrong length
67XX- The interpretation of this status word is command dependent, except for SW2 = '00'
6B00- Wrong parameter(s) P1-P2
6D00- Instruction code not supported or invalid.
6E00- Class not supported.
6F00- Technical problem, no precise diagnosis.
6FXX- The interpretation of this status word is command dependent, except for SW2 = '00'


Functions in CLA not supported

SW1SW2Description 
6800- No information given
6881- Logical channel not supported
6882- Secure messaging not supported


Command not allowed

SW1SW2Description 
6900- No information given
6981- Command incompatible with fire structure
6982- Secure status not satisfied
6983- Authentication/PIN method blocked
6984- Referenced data invalidated
6985- Conditions of use not satisfied
6986- Command not allowed (no EF selected)
6989- Command not allowed - secure channel - security not satisfied


Wrong parameters

SW1SW2Description 
6A80- Incorrect parameters in the data field.
6A81- Function not supported.
6A82- File not found.
6A83- Record not found.
6A84- Not enough memory space.
6A86- Incorrect parameters P1 to P2.
6A87- Lc inconsistent with P1 to P2.
6A88- Referenced data not found.


Application errors

SW1SW2Description 
9850- INCREASE cannot be performed, max value reached.
9862- Authentication error, application specific.
9863- Security session or association expired.
NOTE:Applications may define their own error codes.


저작자 표시 비영리 변경 금지
신고

WRITTEN BY
빅터크룸
머 먹고 사냐.....

받은 트랙백이 없고 , 댓글이 없습니다.
secret