top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

How NAS COUNT is constructed and managed during time...

+1 vote

128-bit Counter blocks (Tn, n=0,1...) are constructed in order to, e.g. cipher/decipher NAS messages. Each T block contains a sequence number, an overflow counter and a 64-bit zone also used as counter.
Altogether, there are three "counting" fields in each T block.
How/when each one of these three fields is: initialized, reset and managed/increamented during time?
What happens to each field when a new NAS message is received?

posted Jul 27, 2014 by Hr

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button
Is your problem solved??? or do you have some issues further.

1 Answer

0 votes

Reference: 3GPP TS 24.301 V8.0.0 (2008-12)
The NAS COUNT counters use 24 bit internal representation and are independently maintained by UE and MME. The NAS COUNT is constructed as a NAS sequence number (least significant bits) concatenated with a NAS overflow counter (most significant bits). When NAS COUNT is input to NAS ciphering or NAS integrity algorithms it is considered to be a 32-bit entity where the most significant bits are padded with zeros.

The network NAS COUNT shall be initialized to zero in the first SECURITY MODE COMMAND when a new security context is activated following a successful authentication and key agreement (AKA) procedure. The UE NAS COUNT shall be initialized to zero when the UE receives the first SECURITY MODE COMMAND message after a successful AKA procedure and uses it in the following SECURITY MODE COMPLETE message.

The NAS sequence number part of the NAS COUNT is exchanged between the UE and the MME as part of the NAS signalling. After each new or retransmitted outbound NAS message, the sender shall always increase the NAS COUNT number by one. Specifically, the NAS sequence number is increased by one, and if the result is zero (due to wrap around), the NAS overflow counter is also incremented by one. The receiving side estimates the NAS COUNT used by the sending side. Specifically, if the NAS sequence number wraps around, the NAS overflow counter is incremented by one.

answer Jul 27, 2014 by Salil Agrawal
Thanks for your quick reply.
Suppose a cipherd message length is more than 128-bits, so several T counter blocks are required in order to decipher it. How these counters are managed in this case (same single message)?
Similar Questions
+1 vote

What does it mean for MME and UE ? what are action need to do ?

0 votes

When the MME sends a DL NAS message is the connection between MME and UE held long enough just to receive the message ? What happens if there are back-to-back NAS messages to be delivered, does the the UE open a connection to MME and receive all the messages at once. Or does it open close the connection to get each of the messages separately.

+5 votes

Uplink NAS transport message is used between eNodeB and MME to pass NAS messages between UE and MME transparently.
Since eNodeB has already communicated TAI and E-CGI as part of "Initial UE message" and MME knows current serving (cell and tai ) of UE then why both IEs are mandatory in Uplink NAS transport. I think it should be optional and it should be included in the message when there is a change in serving (cell or tai or both).

+1 vote

In which cases/scenarios, an UE would maintain multiple active NAS connection with the different serving networks ?