RCC-L1 Configurations

Route Cache Controller level 1 (RCC-L1) functionality removes limitations to the number of records held in the routing tables, and ensures that even if the routing table is near to full capacity, new subscriber IDs or session IDs are still added to the tables.

When enabled, the RCC-L1 manages the Route Cache and handles all routing requests from service users such as Network Enabler (NE) and Traffic Routing Agent (TRA). Every new record is placed into the routing tables regardless of the number of available records. If the Route Cache becomes close to full, the RCC-L1 discards old Route Cache records using a least recently used (LRU) eviction policy. For information about enabling and configuring RCC-L1 functionality, see the discussion about configuring an RCC-L1 instance.

LRU Queue Management

When RCC-L1 receives a record insert request, it updates its local cache, and the newly inserted record is placed at the back of the LRU queue. When the RCC-L1 receives a LRU eviction notification, the evicted record is removed from the Route Cache and discarded.

Each time the service user (TRA or NE) successfully looks up a record in the Route Cache, the record is moved to the back of the LRU eviction queue.

Route Cache Miss Handling

The RCC-L1 resolves records which cannot be found in L1 Route Cache instances from the engine processing servers. For more information, see the discussion about Route Cache miss handling.

For information about configuring RCC-L1s, see the discussion about configuring an RCC level 1 instance.