Hands On: MAC Log analysis Deep Drive Amarisoft Test Bed

1.1 Transfer of Upper Layer PDUs

1.2 Error Correction through ARQ(Only for AM Data Transfer)

1.3 Segmentation and Reassembly of RLC SDUs

1.4 Re-segmentation of RLC SDU Segment

1.5 Duplicate Detection (Only for AM Data Transfer)

1.6 RLC SDU Discard (Only for UM & AM)

1.7 RLC Re-establishment

1.8 Protocol Error Detection (Only for AM Data Transfer)

2.1 TM-RLC Entity Behavior 4.2.1.1.2, 4.2.1.1.3

2.2 UM-RLC Entity Behavior-TX Side 4.2.1.2.2

2.3 UM-RLC Entity Behavior-RX Side 4.2.1.2.3

2.4 AM-RLC Entity Behavior-TX Side 4.2.1.3.2

2.4 Example1 First Transmission with Segmentation

2.4 Example 2 Re-Transmission with Re-Segmentation

2.5 AM-RLC Entity Behavior-RX Side 4.2.1.3.3

2.5 Example 3-Duplicate Detection, Example 4-Loss Detection and Retransmission Request, Example 5-Re-Assembly as soon as possible

3.1 TM Data Transfer Procedures-Tx Side 5.2.1.1.1

3.2 TM Data Transfer Procedures-Rx Side 5.2.1.2.1

Complete Walkthrough

3.3 UM Data Transfer Procedures-Tx Side 5.2.2.1.1

3.4 UM Data Transfer Procedures-Rx Side 5.2.2.2.2

3.4.1 UM Data Transfer Procedures-Rx Side-Action When a UMD PDU is Received from Lower Layer 5.2.2.2.2

3.4.2 UM Data Transfer Procedures-Rx Side-Action When a UMD PDU is Placed in the Reception Buffer 5.2.2.2.3

Example: UM RLC Receive Operations-5.2.2.2.3

3.4.3 UM Data Transfer Procedures-Rx Side-Action When t-Reassembly Expires 5.2.2.2.4

3.5 AM Data Transfer Procedures-Tx Side 5.2.3.1.1

3.6 AM Data Transfer Procedures-Tx Side: Transmitting Window Definition

3.7 AM Data Transfer Procedures-Tx Side: SN Assignment for New SDUs

3.8 AM Data Transfer Procedures-Tx Side: Positive ACK Handeling

3.9 AM Data Transfer Procedures-Tx Side: Discard of SDU when TX Discarded SDU is configured

3.10 AM Data Transfer Procedures-Rx Side 5.2.3.2.1

3.11 AM Data Transfer Procedures-Rx Side: Action When an AMD PDU is Received from Lower Layer 5.2.3.2.2

3.12 AM Data Transfer Procedures-Rx Side: Actions When t-Rx Discard Expires 5.2.3.2.5

3.13 AM Data Transfer Procedures-Rx Side: Actions When t-Re-Assembly Expires 5.2.3.2.4

4.1 ARQ Procedure in AM RLC

5.1 RLC AM Retransmission Handling Procedure

6.1 Polling in AM RLC

6.2 Counter Based Polling

6.3 Event Based Polling

6.4 Reception of a Status Report 5.3.3.3

6.5 Expiry of t-Poll Retransmit 5.3.3.4

7.1 Status Reporting in AM RLC

7.2 Polling from Peer 5.3.4.1

7.2 Polling from Peer-Examples

7.3 Detection of Reception Failure (t-Re-Assembly Expiry)

7.4 Detection of Discard (t-RXDiscard Expiry)

7.5 Status Prohibit Timer (t-Status Prohibit)

7.6 Constructing a Status PDU

Complete Walkthrough: Poll + Status Construction

8.1 Data Volume Calculation for MAC Buffer Status Reporting

8.2 Regular RLC Data Volume (For MAC BSR)

8.3 Delay Critical RLC Data Volume

8.4 Delay Reporting RLC Data Volume

8.5 Inclusion of Status PDU in Data Volume

9.1 TMD PDU

9.2 UMD PDU 6.2.2.3

9.3 AMD PDU 6.2.2.4

9.4 STATUS PDU 6.2.2.5

Complete Walkthrough -From SDU to PDU to Status

Hands On: RLC Log analysis Deep Drive Amarisoft Test Bed

Transfer of Data (User Plane & Control Plane)

Maintenance of PDCP Sequence Numbers (SNs)

Header Compression & Decompression (ROHC)

Ciphering & Deciphering (Encryption)

Integrity Protection & Verification

Timer-Based SDU Discard

PDU Set Discard

Routing (Split Bearers & DAPS Bearer)

Duplication

Reordering & In-Order Delivery

Duplicate Discarding

PDCP layer, functional view(TS 38.323 4.2.2)

Services (TS 38.323 4.3.1)

Robust header compression and decompression TS 38.323 5.7

ROHC Modes in 5G: Unidirectional Mode (U-mode)

U-mode PCAP validation

Bidirectional Optimistic Mode (O-mode)- TS 38.323/RFC 3095

Bidirectional Reliable Mode (R-mode)

Header decompression using ROHC Flow Diagram (TS 38.323 5.7.5)

Ciphering and deciphering Deep Drive (TS 38.323 5.8)

Integrity Protection and Verification Deep Drive (TS 38.323 5.9)

PDCP Data Structure (TS 38.323 6.2.2/6.2.3)

PDCP Structure Parameter (TS 38.323 6.3)

Hands On: PDCP Log analysis Deep Drive Amarisoft Test Bed