ments) to process the final measured value that can be reported to the net- work. If beams are not used, then process simplifies to the same model as in LTE (i.e. L1 filtering followed by L3 filtering) (Table 7.6). 7.7.6 RRC Support of Upper Layers 7.7.6.1 NAS Message Transfer RRC supports NAS message transfer, which is required for, for example, connection setup to exchange the required DRB information between the UE and the network. The NAS messages may be either transferred with dedicated RRC messages designed for NAS message transfer in the uplink/downlink or piggybacked within other RRC mes- sages. The piggybacking can be performed upon RRC reconfiguration (in the downlink direction) or upon the RRC setup/resume completion (in the uplink direction). The information within the NAS messages is always fully transparent to the RRC, which merely sends or receives the messages and passes them directly to the NAS layer without attempting to decode or comprehend them. 7.7.6.2 Network Slicing Network slicing (as described in Chapter 5) is an important concept in NR but is almost invisible to the RRC layer. It is only visible in the completion of RRC setup when the UE passes its current S-NSSAI list to the network. This information is the same information that is included in the NAS protocol also passed in the same message, but since NAS is terminated in the AMF, the gNB is not required to comprehend the NAS protocol. 7 5G Radio Protocols Signaling the UE S-NSSAI list over RRC allows the gNB to perform faster AMF selection toward the correct network slice without requiring it to comprehend the NAS protocol. 7.7.6.3 UE Capability Transfer With the proliferation of different UE vendors and new models being released continu- ously, the network needs to understand the UE capabilities to configure the UE correctly. The RRC defines a procedure that allows the UE to indicate this information to network, along with the ASN.1 encoding format that allows the capabilities to be comprehended by the gNB regardless of the version o