spec5g.csv

,Paragraph,Simplification
0,"In 5G NR, for the procedures such as handover to a stronger cells or adding a new Carrier Component (CC) in the case of Carrier Aggression, it is required to measure the serving cell and neighbor cell signal strength or signal quality matrix i.e. RSRP or RSRQ. This requirement enables the measurement process to be executed appropriately, maintaining the radio link quality. In LTE, all eNodeBs continually transmits Cell-specific Reference Signal (CRS), so it is easy for the mobile device to measure the cell quality of neighboring cells. However in 5G NR, there is the concept of CRS has be removed to reduce the overhead and Reference Signal interference from other cells.","In 5G NR, signal strength or signal quality matrix (RSRP or RSRQ) must be assessed for handover to a stronger cell or adding a new Carrier Component (CC) in Carrier Aggression. This ensures correct measurement and radio link quality. In LTE, all eNodeBs transmit CRS so mobile devices can readily measure cell quality. 5G NR removes CRS to reduce cell interference."
1,"5G NR has introduced cell signal measurement by using SS/PBCH Block (SSB), which is composed of Synchronizations Signal (SS) and Physical Broadcast Channel (PBCH) having longer transmission periodicity than CRS. The number of SSB in one burst depend on the Operating frequency. If Operating frequency (fc) is < 3GHz (FR1) the no. of SSB is 4, for  fc = 3GHz to 6 GHz (FR1) no. of SSB  is 8 and for fc >6 GHz mm-wave no. of SSB is be 64 within one burst.","5G NR measures cell signal with SS/PBCH Block (SSB), which has a longer transmission period than CRS. Frequency affects SSB bursts. Operating frequency (fc) of 3GHz (FR1) has 4 SSB, 3GHz to 6GHz (FR1) has 8, and >6GHz has 64 mm-wave SSB in one burst."
2,New Radio (NR) is the wireless standard and foundation for the 5th generation of mobile networks.Its development is part of continuous mobile broadband evolution process to meet the requirements of 5G as outlined by IMT-2020. NR aims to make wireless broadband same as of wireline with the fiber-like performance at a significantly lower cost-per-bit. To achieve this NR is exploring new spectrum opportunities to address the expected capacity and data rates and this spectrum is spread in cmWave and mmWaves band.,New Radio (NR) is the wireless standard and foundation for the 5th generation of mobile networks. Its development is part of continuous mobile baseband evolution process to meet the requirements of 5G.
3,"Current regulations in the U.S. allow a device with such a high EIRP but not in a mobile phone form factor. However, achieving this EIRP is a technical challenge by itself and may come to the market at a much later stage. From that perspective, a service provider should consider a shorter ISD in its business case. Current literature and presentations at various conferences indicate that cell sizes of 250 m or less are being planned for the early stage of radio equipment. Now it needs to be determined if a shorter ISD, such as 250 m, fulfills the business case for 5G mmWave FWA.","Current literature and presentations at various conferences indicate the cell sizes are of 250 m or less are being planned for the early stage of radio equipment. It needs to be determined if a shorter ISD such as 250m, fulfills the business case of 5G mmWave."
4,"In general, it is  very critical for a UE to consider the certain assumption in terms of the relationship between the radio channels experienced by different downlink transmissions e.g. UE needs to understand what reference signal(s) should be used for channel estimation for a certain downlink transmission and determine relevant channel-state information required for scheduling and link-adaptation purposes. For the same reason, the concept of antenna port is used in the 5G NR and it follows the same principles as in 4G LTE. The term “antenna port” is a logical concept related to physical layer (L1), and not the physical one like RF antenna which is visible on tower.",It is important for UE to consider the certain assumption in terms of relationshops between the radio channels experienced by different downlink transmissions. The concept of antenna port is same in 4G and 5G. 
5,"NR supports both wideband and narrowband precoding for the PDCCH. In wideband precoding, PDCCH DMRSs are transmitted in all contiguous REGs of a CORESET carrying the PDCCH using the same precoder. On the other hand, in the narrowband precoding, PDCCH DMRSs are transmitted only in the REG bundles actually used for the PDCCH transmission, and precoding is constant only within the REG bundle. The former can maximize the frequency domain processing gain and the latter can take advantage of frequency dependent beamforming gain. Since the same precoding is applied to payload and the corresponding DMRS, precoding is transparent to the UE.","NR supports narrowband and wideband PDCCH. Wideband precoding uses the same precoder for all contiguous REGs of a CORESET. Narrowband precoding transmits PDCCH DMRSs only in REG bundles and is constant only within the REG bundle. First, optimize FDP gain, then FDB gain. Payload and DMRS precoding is transparent to the UE."
6,"Radio channel between the base station and UE introduces delay spread in the time domain. This delay spread is generated by the transmitted signal reaching the receiver from multiple paths which have different distances environment, terrain, and clutter result in different delays. Delay spread of the received signal pulse caused by multi-path is the difference between the maximum transmission latency in largest path and the minimum transmission latency in shorted path. The latency varies with the varies with the environment, terrain, and clutter, and does not have an absolute mapping relationship with the cell radius.","Radio channel delay spread between base station and UE. This delay dispersion is caused by the broadcast signal reaching the receiver from several pathways with varied lengths.
Multi-path delay spread is the difference between the largest path's greatest and shortest transmission latencies. Latency varies with surroundings, terrain, and clutter and does not map to cell radius."
7,"In Legacy 4G LTE networks and 5G NR till release 15, the UE typically releases the connection from the source cell before the connection is established with the target cell (Hard Handover). Due to this, UL and DL transmission is finalized at source cell before the UE starts to communicate with the target cell results an interruption of a few tens of milliseconds in the communication between the UE and the base station. This interruption is very critical for URLCC use case /application with in 5G. So 3GPP has proposed a solution to overcome this problem as part of Release 16 named as Dual Active Protocol Stack (DAPS) where UE connection with source cell to remain active for Rx and Tx of user data, until it is able to send and receive user data in the target cell. This put a new requirement at UE  side to simultaneously receive and transmit data at both source cell and target cell for a short time period during the handover procedure. In my view, this is similar to soft handover procedure.","UE releases source cell connection before target cell connection in 4G LTE and 5G NR until release 15. Due to this, source cell finalizes UL and DL transmission before UE starts interacting with destination cell, creating a few tens of milliseconds of UE-base station halt. 5G URLCC needs this interruption. As part of Release 16, 3GPP has suggested Dual Active Protocol Stack (DAPS), where UE connection with source cell remains active until it can send and receive user data in the destination cell. During handover, UE must receive and transmit data at both source and target cells. The transition looks easy."
8,"To support DAHO, UE has to keep Dual Stack in Active state. One user plane protocol stack for the target cell, containing PHY (Physical), MAC (Medium Access Control) and RLC (Radio Link Control) layers, while keeping the second user plane protocol stack active for transmission and reception of user data in the source cell. UE receives user data simultaneously from both the source and target cell, the PDCP (Packet Data Convergence Protocol) layer is reconfigured to a common PDCP entity for the source and target user plane protocol stacks. To secure in-sequence delivery of user data, PDCP Sequence Number (SN) continuation is maintained throughout the handover procedure. For that reason, a common (for source and target) re-ordering and duplication function is provided in the single PDCP entity. Ciphering/deciphering and header compression/decompression need to be handled separately in the common PDCP entity, depending on the origin/destination of the downlink/uplink data packet.","DAHO requires UE's Dual Stack. One user plane protocol stack for the target cell, with PHY, MAC, and RLC layers, and another for source cell data transmission and reception. When UE receives user data from both the source and target cell, the PDCP layer becomes a common entity for the source and target user plane protocol stacks. PDCP Sequence Number (SN) continuation ensures in-sequence data transmission. PDCP provides source-and-destination reordering and duplicating. PDCP must handle downlink/uplink data packet ciphering/deciphering, header compression/decompression individually."
9,"Upon receiving DAPS handover command message, the UE suspends source cell SRBs, stops sending and receiving any RRC control plane signalling toward the source cell, and establishes SRBs for the target cell. The UE releases the source cell SRBs configuration upon receiving source cell release indication from the target cell after successful DAPS handover execution. When DAPS handover to the target cell fails and if the source cell link is available, then the UE reverts back to the source cell configuration and activate source cell SRBs for control plane signalling.","UE suspends source cell SRBs, stops sending and receiving RRC control plane signaling, and creates target cell SRBs upon receiving DAPS handover command message. The UE releases source cell SRBs configuration after a successful DAPS handover. When DAPS handover fails, the UE reverts to the source cell configuration and activates source cell SRBs."
10,"Where GUAMI identifies one or more AMF(s). When the GUAMI identifies only one AMF, the 5G-TMSI identifies the UE uniquely within the AMF. However, when AMF assigns a 5G-GUTI to the UE with a GUAMI value used by more than one AMF, the AMF shall ensure that the 5G-TMSI value used within the assigned 5G-GUTI is not already in use by the other AMF(s) sharing that GUAMI value.  Where AMF Region ID identifies the region, AMF Set ID uniquely identifies the AMF Set within the AMF Region and AMF Pointer identifies one or more AMFs within the AMF Set.","GUAMI detects AMF (s). When GUAMI finds only one AMF, 5G-TMSI identifies the UE within it. When an AMF assigns a 5G-GUTI to a UE with a GUAMI value shared by more than one AMF, it must guarantee that the 5G-TMSI value is not already in use by the other AMF(s). AMF Region ID identifies the region, AMF Set ID identifies the AMF Set within the region, and AMF Pointer indicates one or more AMFs inside the set."
11,"As indicated, 5G NR Meas Gap Length is not fixed and 3GPP specifications made it configurable. By having a fixed Meas Gap could cause unnecessarily degradation of throughput in the serving cell. The SMTC window and window duration can be set to match SSB transmissions and accordingly the MGL . For example, if we consider SMTC window duration as 2 ms and the Meas Gap Length as 6 ms, here 4 ms segment would  not  be  available for transmission and reception of data in the serving cell will result in low DL/UL throughput.","5G NR Meas Gap Length is adjustable per 3GPP specs. A fixed Meas Gap can degrade serving cell throughput. The SMTC window and duration can match SSB transmissions and the MGL. If SMTC window duration is 2 ms and Meas Gap Length is 6 ms, a 4 ms segment is not accessible for transmission, resulting in limited DL/UL throughput."
12,"The SSB periodicity can be configured for each cell in the range of 5,10,20,40,80 or 160 ms. However, mobile device do not need to measure cell signal with periodicity as the SSB and the appropriate measurement periodicity can be configured according to the channel condition. This is desirable and can help to avoid unnecessary measurements and reduce the power consumption on Mobile Device (UE). 3GPP specifications has introduced SSB-based RRM Measurement Timing Configuration window (called SMTC window) shall be notify to Device (UE) regarding the measurement periodicity and timings of SSBs that Device (UE) can use for measurements.","SSB periodicity is 5,10,20,40,80 or 160 ms per cell. Mobile devices can set SSB and measurement periodicity dependent on channel status. This reduces unnecessary measurements and battery use (UE). 3GPP specifications have introduced an SSB-based RRM Measurement Timing Configuration window (SMTC window) to alert Device (UE) of measurement periodicity and SSB timings."
13,"SS-RSRP stands for Synchronization Signal reference signal received power. It is defined as the linear average over the power contributions (in Watt) of the resource elements that carry SSS. The measurement time resource(s) for SS-RSRP are confined within SS/PBCH Block Measurement Time Configuration (SMTC) window duration. For SS-RSRP determination, demodulation reference signals for PBCH and, if indicated by higher layers, CSI RS in addition to SSS may be used.. SS-RSRP using demodulation reference signal for PBCH or CSI reference signal shall be measured by linear averaging over the power contributions of the resource elements that carry corresponding reference signals taking into account power scaling for the reference signals.","Synchronization Signal strength (SS-RSRP) is the linear average of resource parts' power contributions (in Watt). SMTC limits SS-RSRP measuring time. SS-RSRP can be determined using PBCH demodulation reference signals and, if higher layers indicate, CSI RS. SS-RSRP using demodulation reference signal for PBCH or CSI reference signal is measured by linearly averaging resource element power contributions."
14,"CSI-RSRP stands for CSI reference signal received power. It is defined as the linear average over the power contributions (in watt) of the resource elements that carry CSI-RS configured for RSRP measurements within the considered measurement frequency bandwidth in the configured CSI-RS occasions. For CSI-RSRP determination CSI reference signals transmitted on antenna port 3000 shall be used, if CSI_RSRP is used for L1-RSRP, CSI reference signals transmitted on antenna ports 3000, 3001 can be used. For intra-frequency CSI-RSRP measurements, if the measurement gap is not configured, UE is not expected to measure the CSI-RS resource(s) outside of the active downlink bandwidth part.","CSI-RSRP is received signal power. It's the linear average of the power contributions (in watt) of resource elements that carry CSI-RS for RSRP measurements in configured CSI-RS instances. If L1-RSRP uses CSI RSRP, antenna ports 3000, 3001 can be used. If the measurement gap isn't given, UE shouldn't measure intra-frequency CSI-RSRP resources outside the active downlink bandwidth."
15,"Handover, or handoff in 5G NR or 4G LTE happens when a Data/Voice call is transferred from one cell to the an adjacent cell as the Mobile user moves through the network coverage area. Before any base station software is released for field, it goes through multiple level of testing’s (regression, load etc.) in Vendor’s and Customer’s Lab. This kind of testing in Lab is mostly done in cabled environment to avoid interference for self and to other cells. The objective of handover cabled setup is to simulate the field over the air scenario mean during handover signal from serving cell worsen and neighbors cell signal becomes better. Considering this in cabled setup, we need to mix the signal from two cells and control the signal path from both cell in a such way that one cell signal reduce and other cell signal increase and vice versa.","When a mobile user goes through a 5G NR or 4G LTE network service region, a Data/Voice call is transferred to a nearby cell. Before base station software is given for field, it's tested in the vendor's and customer's labs (regression, load, etc.). This lab testing is frequently cabled to reduce interference. Handover cabled setup simulates over-the-air scenario where serving cell signal declines and nearby cell signal increases. In a cabled design, we must mix and regulate two cells' signal routes such one cell's signal declines and the other's increases."
16,"The verify first verification before attempting for HO test, one should try to test that Mobile should be able to attach individual cells. This can be verified setting max attenuation in cell#1 signal path (Port 1,2) mobile should attach to cell#2 and When setting max attenuation in cell#2 signal path (Port 3,4) mobile should be able to attach to cell#1. While performing handover, you have to create a sequence script where we can control the signal path from two cells. Some digital attenuator allows this to control or create handover sequencer using GUI as shown in below figure. When creating script or configuring HO sequencer we need to to be careful on the attenuation step and interval (dB/sec), if the interval is low or step is high can cause for radio link failures (RLFs).","Mobile should be able to attach individual cells before attempting HO test. This may be checked by setting max attenuation in cell#1 signal path (Port 1,2) and cell#2 signal path (Port 3,4).
During handover, develop a sequence script to regulate the signal path from two cells. Some digital attenuators allow GUI management or creation of handover sequencers. When writing a script or establishing a HO sequencer, the attenuation step and interval (dB/sec) must be carefully considered to avoid radio connection failures (RLFs)."
17,"The Inactive RNTI (I-RNTI) is applicable to the RRC Inactive State. While comparing with other RNTI, the I-RNTI is not used to scramble the CRC bits. Instead, the I-RNTI is used to address the UE within RRC signalling messages. An I-RNTI can be allocated to a UE within an RRC Release message when it is moving from RRC Connected to RRC Inactive as part of suspendConfig. The I-RNTI is used to identify both the UE and the gNB which hosts the UE context, this is required to move the UE context from one gNB to another gNB when UE is mobile while RRC Inactive. But here is a check, 3GPP specifications does not specify the number of bits which should be used to identify the gNB, and the number of bits which should be used to identify the UE within total the I-RNTI bits. The division of the total number of bits is left to the network implementation.","The RRC Inactive State uses the I-RNTI. I-RNTI doesn't scramble CRC bits like other RNTIs. In RRC signaling messages, the I-RNTI addresses the UE. An I-RNTI can be allocated to a UE via an RRC Release message as part of suspendConfig. The I-RNTI identifies both the UE and the gNB that hosts the UE context, which is needed to move the UE context from one gNB to another when the UE is mobile and RRC is inactive. 3GPP specifications do not specify how many I-RNTI bits should be used to identify the gNB and the UE. Network implementation divides bits."
18,The RRC Resume Request is transmitted during the RACH procedure as MSG3 cannot be segmented and must be transmitted using a single Transport Block. Due to this reason the message size must be kept relatively small to make sure the reliable reception when the UE is at cell edge. Using the short I-RNTI  message size becomes 48 bit which can be transmitted using a single Transport block. The RRC Resume Request 1 message which included full I-RNTI has a size of 64 bits so it requires relatively good coverage for reliable reception. full I-RNTI support could be used for in-building or small cells  deployments where the coverage conditions are mostly good.,"As MSG3 cannot be segmented, the RRC Resume Request is sent during RACH. To ensure reliable reception at the cell edge, message size must be maintained modest. Using I-low RNTI's message size, a single Transport block can transfer 48 bits. The 64-bit RRC Resume Request 1 message with full I-RNTI requires sufficient coverage for reliable reception. In-building or small cell deployments with good coverage can employ complete I-RNTI."
19,"In a wireless 5G network, when a mobile device (UE) travelling across different sites, it can be either in connected mobility or Idle mode mobility. Considering the two situation’s 5G mobility scenarios i.e. in Connected Mode Mobility UE does perform handover and in Idle mode mobility UE does cell selection/reselection.","When a UE travels across diffeent sites, it can be either in connected mobility or idle mode mobility. In connected mode mobility UE performs handover and in idle mode mobility UE does cell selection."
20,"Coverage based Inter Frequency Handover make use of A2 Event. When UE reports A2 event measurement where serving cell signal goes below than the defined threshold, the gNB determines the UE is in cell edge poor radio condition and configure Event A5 and Event A1 for inter frequency measurement. When  UE reports Event A5 i.e. serving cell signal drops below to Threshold 1 and signal from neighbor cell become better than Threshold 2, the gNB generates the target cells or target frequencies as per the measurement results. Following Layer 3 parameters are important while optimization Inter Frequency Handover.","When UE reports A2 event measurement where serving cell signal goes below than the defined threshold, the gNB determines the UE is in cell edge poor radio condition and configure A5 and A1 event for inter frequency measurement."
21,"In multi band co-coverage scenario, the frequency priory-based inter frequency handover is used to allow higher frequency to carry services as much as possible to keep low frequency band less loaded  and continue coverage. It used Event A4 related to inter frequency, where neighbor cell signal becomes better than threshold. When gNB receives Event A4 measurement and reported frequency has the highest traffic priority, gNB choose the frequency as target frequency and initiate handover immediately.","In multi band co-coverage, the frequency priority-based inter frequency handover is used to allow higher frequency to carry services as much as possible to keep low frequency band less loaded and continute coverage."
22,"When we want to connect a UE to 5G network, it has to synchronize in downlink as well as in uplink. Downlink synchronization is obtained after successfully decoding SSB, In order to establish uplink synchronization and RRC connection, UE has to perform RACH random access procedure.","When UE wants to connect to 5G, it has to synchronize in downlink as well as in uplink. Downlink synchronization is obtanied after successfully decoding SSB and uplink synchronization is done through RACH random access procedure."
23,"A Mobile device has to measure the neighboring cells signal and other carrier components. Having a single RF module to control the Mobile manufacturing cost and form factor, device has to perform all this measurements, Transmission and reception of data using single RF module. Mobile can measurement the neighbor signal transmitting on the same frequency very easy while simultaneously transmitting and receiving data from the serving cell. While for measuring cell operating at different frequency (Inter frequency Neighbors) and Other RAT (LTE is other RAT for 5G NR) mobile has to suspended communication (Tx/Rx) with serving cell and needs to tune RF module to configured frequencies (configured Meas Objects) and resume connection with serving cell after some duration. The time duration during which mobile suspends it communication with serving cell to measure inter frequency neighbor or other RAT neighbor is known as Measurement Gap (Meas Gap).","Mobile devices measure cell and carrier signals. Using a single RF module, the device must measure, send, and receive data. Mobile can measure neighbor signal on same frequency while sending and receiving data. For measuring cells running at different frequencies (Inter frequency Neighbors) and Other RAT (LTE is other RAT for 5G NR), mobile must suspend Tx/Rx with serving cell, tune RF module to configured frequencies (configured Meas Objects), and reconnect with serving cell after some duration. Mobile suspends connection with its serving cell to measure interfrequency or RAT neighbors (Meas Gap)."
24,"Similar to LTE, in 5G NR also RRC is responsible for providing measurement gap pattern configuration to UE. This is done using MeasGapConfig IE within the MeasConfig IE and is carried by RRC Reconfiguration message. It has two part, first part specifies control setup/release of meas gap and second part specifies measurement gap configuration and controls setup/release.","Similar to LTE, 5G NR RRC configures UE's measurement gap pattern. This is done in MeasConfig IE and carried via RRC Reconfiguration message. First portion specifies measurement gap control setup/release, second part configuration and controls setup/release."
25,"The MSG3 is very first PUSCH transmission scheduled by MSG2 with the RAR UL grant. A UL grant includes scheduling information for frequency hopping, frequency and time domain resource allocation, MCS, and transmit power control necessary information required for MSG3.","The MSG3 is very first PUSCH tranmission scheduled by MSG2 with the RAR UL grant. A UL graint includes scheduling information for frequency hopping, frequency and time domain resource allocation."
26,"In 5G NR, CORESET is known as Control Resource Set. It is a set of physical resources within a specific area in Downlink Resource Grid and used to carry PDCCH (DCI). NR PDCCHs are specifically designed to transmit in a configurable control resource set (CORESET). A CORESET is analogous to the control region in LTE but is generalized in the sense that the set of RBs and the set of OFDM symbols in which it is located are configurable with the corresponding PDCCH search spaces. Such configuration flexibilities of control regions including time, frequency, numerologies, and operating points enable NR to address a wide range of use cases",CORESET is a set of physical resources within specific area in Downlink Resource Grid and used to carry PDCCH. NR PDCCHs are specifically designed to transmit in a configurable control resource set. A CORESET is analogous to the control region in LTE but is generalized in the sense that the set of RBs and the set of OFDM symbols in which it is located are configurable with the corresponding PDCCH search spaces.
27,"Frequency allocation in a CORESET configuration can be contiguous or non-contiguous. CORESET configuration in time spans 1-3 consecutive OFDM symbols. The REs in a CORESET are organized in RE groups (REGs). Each REG consists of the 12 REs of one OFDM symbol in one RB. A PDCCH is confined to one CORESET and transmitted with its own demodulation reference signal (DMRS) enabling UE-specific beamforming of the control channel. A PDCCH is carried by 1, 2, 4, 8 or 16 control channel elements (CCEs) to accommodate different DCI payload size or different coding rates. Each CCE consists of 6 REGs. The CCE-to-REG mapping for a CORESET can be interleaved (for frequency diversity) or non-interleaved (for localized beam-forming).","CORESET can allocate contiguous or non-contiguous frequencies. CORESET has 1-3 OFDM symbols. Grouping CORESET REs (REGs). One REG has 12 OFDM REs. A PDCCH is confined to one CORESET and broadcasts its own DMRS, enabling UE-specific beamforming. PDCCHs have 1, 2, 4, 8 or 16 CCEs to handle different DCI payload sizes or coding rates. 6 REGs govern CCEs. CORESET CCE-to-REG interleaved or not? (for localized beam-forming)."
28,"A REG bundle is a set of indivisible resources consisting of neighboring REGs. A REG bundle spans across all OFDM symbols for the given CORESET. Therefore, interleaved CCEto-REG mapping can enable both a time domain processing gain and frequency domain diversity. Interleaved CCE-to-REG mapping can be visualized as a process for which REG bundle indices are continuously filled in an array row-wise first and then read out column-wise. This process is often called block interleaving. By this means, adjacent CCEs for a PDCCH are broken down into scattered REG bundles in the frequency domain. On the other hand, for non-interleaved CCE-to-REG mapping, all CCEs for a DCI with AL L are mapped in consecutive REG bundles of the CORESET. Once the REGs corresponding to a PDCCH are determined, the modulated symbols of the PDCCH are mapped to the REs of the determined REGs in the frequency domain first and the time domain second, i.e. in increasing order of the RE index and symbol index, respectively.","REG bundles include nearby REGs. REG bundles feature CORESET OFDM symbols. Interleaved CCEto-REG mapping offers processing gain and frequency domain variation. Interleaved CCE-to-REG mapping fills and reads REG bundle indices row-by-row. This is block interleaving. This creates frequency-domain REG bundles from adjacent PDCCH CCEs. All DCI CCEs with AL L are mapped in consecutive CORESET REG bundles. Once the REGs for a PDCCH are found, the modulated symbols are mapped to the REs in the frequency domain first, then the time domain, in increasing order of the RE index and symbol index."
29,"A wider Bandwidth has direct impact on the peak and user experienced data rates, however users are not always demanding high data rate.  The use of wide BW may imply higher idling power consumption both from RF and baseband signal processing perspectives. In regards to this , new concept of BWP  has been introduced for 5G-NR provides a means of operating UEs with smaller BW than the configured CBW, which makes NR an energy efficient solution despite the support of wideband operation.
Alternatively, one may consider to schedule a UE such that it only transmits or receives within a certain frequency range. Compared to this approach, the difference with BWP is that the UE is not required to transmit or receive outside of the configured frequency range of the active BWP, which attributes power saving.","In 5G BWP has been introduced of operating UEs with smaller BW than the configured CBW, which makes NR energy efficient solution despite support of wideband operation."
30,"An active UL bandwidth part (BWP) is indicated by higher layers for a PUSCH transmission scheduled by a RAR UL grant. For determining the frequency domain resource allocation for the PUSCH transmission within the active UL BWP UE does follow below mentioned steps. In both cases, despite the start RB may be different, the maximum no. of RBs for frequency domain resource allocation always equals the number of RBs in the initial UL BWP. The frequency domain resource allocation is by uplink resource allocation type 1.","For determining the frequency domain resource allocation for the PUSCH transmission within the active UL, UE processes the frequency domain resource assignment fields. "
31,"N26 interface is an interface which interconnects the 5G Core network function AMF with 4G network node MME and enables interworking between 5G to 4G and visa versa. N26 interface is used to transfer UE’s authentication and session context as the UE moves between the 5GS and 4G-EPS systems. The support for N26 interface between AMF in 5GC and MME in EPC is required to enable seamless session continuity for inter-system handover which will be critical for voice services. For example, if a Voice call is initiated in 5G NR i.e VONR call can be continued when there is an Inter-RAT handover to LTE and the voice call be continued as a VoLTE Call.",N26 interface connects the 5G core network function AMF with 4G network node MME and enables interworking between 5G to 4G and vise versa.
32,"When UE is connecting to 4G-EPS and sends Attach Request indicating support for N1 mode, then MME supporting inter-system interworking with 5GS can set the Interworking N26 bit to either of follwoing within Attach Accept Message in EPS network feature support IE.","When UE is connecting to 4G-EPS and sends Attach Request indicating suppot for N1 mode, then MME supporting inter-system interwoking with 5GS can set the interworking N26 bit to either of following withing attach accept message in EPS network feature support IE."
33,"VoNR is standard voice service when 5G RAN is capable to support Voice Call with help of 5G Core and IMS, where as Voice Call support via EPS Fallback with handover is required when UE is moving out of 5G coverage and to continue Voice Call 5G RAN handover the UE to 4G and  when 5G RAN/5GC is not capable to support Voice service, it can fallback RAT to 4G as soon as UE request for Voice session.","VoNR is standard voice service when 5G RAN is capable to support Voice Call with help of 5G Core and IMS, where as Voice Call support via EPS Fallback with handover is required when UE is moving out of 5G coverage and continue Voice Call 5G RAN handover the UE to 4G."
34,"NAS signalling exchange the information between the UE and the 5GC, RAN does not use it and transparently transfer the information. 5G System indicates the voice service support NAS during the registration procedure. This is required to provide higher granularity in feature support indication and in access restrictions.","NAS signaling exchanges the information between the UE and the 5GC, RAN does not use it and transprarently transfer the information."
35,UE sends it all network capability within Registration Request  and IE UE’s Usage Setting’ indicates that the higher layers of the UE support the IMS Voice service and 5GS provides feature support information elements (IEs) which indicates support for certain features to the UE  with Registration Accept message. ,UE sends it all network capability within Registration Request and IE UE's Settings indicate that the higher layers of the UE support the IMS Voice service and 5GS provides feature support.
36,"In 5G Network, Non-access stratum (NAS) layer managed the PLMN specfic Network Failure and Authentication Failures between the 5G UE and 5G Core. Mutual authentication is a mandatory security procedure between the UE and the network, If either is suspecting any issue the it can send an Authentication Reject or Authentication Failure with relevant reason.",NAS layer managed the PLMN specific Network Failure and Authentication Failures between the 5G UE and 5G Core. Mutual authentication is a mandatory security procedure between the UE and the network.
37,"At 5GC, NAS Mobility Management (5GMM) procedures are responsible to keep track whereabouts of the UE, UE authentication and control integrity protection and ciphering. The 5GMM procedures also used by network to allocated temporary identities to the UE  such as 5G-GUTI and also request identity information such as SUCI and PEI from the UE. In addition, the 5GMM procedures provide the UE’s capability information to the network and the network may also inform the UE about information regarding specific services in the network.","5G Mobility Management (5GMM) procedures are responsible to keep track of the UE, UE authentication and control integity protection and ciphering. The 5GMM procedures also used by network to allocated temporary identities to the UE such as 5G-GUTI."
38,"5G connectivity service is named as PDU Session. A PDU session is very similar to an EPS bearer in LTE, except for the QoS model and the supported user data.  In transport point of view, a PDU session is made by a sequence of NG tunnels in 5G Core, and of one or more radio bearers on the radio interface. This set of “pipes” eventually connects the UE to its control functions and to the external data network for user traffic exchange.","5G connectivity service also known as a PDU session is very similar to an EPS bearer in LTE, except for QoS model and the supported user data. In transport point of view, a PDU session is made by sequence of NG tunnels in 5G Core, and of one or more radio bearers on the radio interface."
39,"In 5G Core Network, the Session Management Function (SMF) supports 5G Session Management cause handling for the PDU-Session-Establishment, PDU-Session-Modification and PDU-Session-Release procedures. When 5G Core is not manage the session it should sent an appropriate SM cause over the N1 message to the UE.","Session Management Function (SMF) supports 5G Session Management cause handling for the PDU-Session-Establishment, PDU-Session Modification and PDU-Session-Release procedures."
40,"If the connectivity with the requested DNN is rejected by the network, SMF sets the 5G Session Management (5GSM) cause IE of the PDU Session Establishment Reject message to indicate the reason for rejecting the PDU Session Establishment procedure. If the SMF does not accept the request to modify the PDU session, it sets the 5G Session Management (5GSM) cause IE of the PDU Session Modification Reject message to indicate the reason for rejecting the PDU session modification procedure. If the SMF does not accept the request to release the PDU session, SMF sets the 5G Session Management (5GSM) Cause IE of the PDU Session Release Reject message to indicate the reason for rejecting the PDU session release.","If connectivity with the requested DNN is rejected by the network, SMF sets the 5G Session Management (5GSM) cause IE of the PDU session establishment reject message to indicate the reason for rejecting the PDU Session Establishment procedure. If the SMF does not accept the request, it sets the 5G Session Management cause IE of the PDU Session Modification Reject message to indicate the reason for rejecting the PDU modification procedure."
41,"In 5G NR, Registration is a NAS layer or 5G Mobility Management (5GMM) process and it is very much similar to the Attach Process in LTE except some of the new IEs added or renamed mainly due to 5G Core network structure. Within 5G Core AMF is manage the registration procedure, which could be successful or could be reject due to different reasons.",5G registration is a NAS layer or 5GMM procedure and is very similar to the Attach process in LTE.
42,"The link budget is the calculation of total gain and loss in the system to conclude the received signal level (RxSL) at the receiver (UE). The received signal level is then compared to the receiver sensitivity (RxS) to check if the channel status is pass or fail.
The channel status is “Pass” if the received signal level (RxSL) is better than the reception sensitivity (RxS), else it is “Fail”.",The link budget is the calculation of total gain and loss in the system to conclude the received signal level at the receiver. The receiver signal level is then compared to the receiver sensitivity to check if the channel status is pass or fail.
43,"Multi-Operator Radio Access Network (MORAN) standard proposed an architecture where the eNBs/gNBs are shared, while the core network is proprietary to each network provider. The MORAN standard also proposed the sharing of the Radio Access Network (RAN), using dedicated radio frequencies assigned to each service provider. In this approach, they can independently control cell level e.g each operator can decide his own optimization parameters, Tx Power to control the cell range and interference.",Multi-Operator Radio Access Network standard proposed an architecture where eNBs/gNBs are shared. The MORAN standard also proposed the sharing of the RAN using dedicated radio frequencies assigned to each service provideer. 
44,"5th generation mobile networks or 5th generation wireless systems is abbreviated as 5G, and proposed next telecommunications standards beyond the current 4G/IMT-Advanced standards. 5G planning aims at higher capacity than current 4G, allowing a higher density of mobile broadband users, and supporting device-to-device, ultra reliable, and massive machine communications. It’s research and development also aims at lower latency than 4G equipment and lower battery consumption, for better implementation of the Internet of things.","5G is the next telecommunications standards beyon the current 4G. 5G planning aims at higher capacity than current 4G, allowing a higher density of mobile broadband users and supporting device-to-device, ultra reliable and massive machine communications."
45,"In Earlier versions of NR  3GPP Releases i.e. Rel.15, There was only one type of RACH procedure was defined, which is similar to LTE RACH procedure also known as 4-Step RACH procedure. In Release-16 NR version, 3GPP Introduced a new 2-Step RACH procedure which aims to improve the overall latency of RACH procedure. So the benefit of having a 2-Step RACH process over 4-Step RACH process is it reduces the network access latency. Now, there are two RACH procedures.",In LTE there was one 4-step LTE RACH procedure. In 5G 3GPP introduced a new 2-Step RACH procedure which aims to improve the overall latency of RACH procedure.
46,"Downlink multi-antenna transmission is a key technology of 5G NR. Signals transmitted from different antennas ports will experience different “radio channels” even if the set of antennas are located at the same site. In some cases, it is important that transmissions share the same antenna port. E.g PDSCH physical channel and PDSCH DMRS share the same antenna port, this helps the UE to estimate the channel using DMRS and use that information in decoding information content on PDSCH.","Downlink multi-antenna transmission is a key technology of 5G NR. It is important that transmissions share the same antenna port, this helps the UE to estimate the channel using DMRS and use the infromation in decoding information content."
47,"MIMO takes advantage of this property (different radio channel) across different antenna port to transmit multiple parallel streams of data.It is important to understand that antenna port is an abstract concept. There is a difference in logical ‘antenna port’ and physical ‘antenna element’. Specific transmissions use specific antenna ports and then those antenna ports are mapped onto one or more physical antenna elements. E.g. the Synchronization Signals, the PBCH and the PBCH Demodulation Reference Signal use antenna port 4000, i.e. all three transmissions share the same antenna port.",MIMO takes advantage of different radio channel accross different antenna port to transmit multiple parallel streams of data. There is a difference in logical antenna port and physical antenna element. 
48,One to one mapping is useful when operating in lower frequency bands which do not require beam-forming ( beam-forming requires multiple physical antenna elements). While one to many mapping is useful for beam-forming in higher frequency bands.,One to one mapping is useful when operating in lower frequency bands and one to mapping is useful for higher frequency bands.
49,"Beam-forming uses multiple physical antenna elements to direct the downlink transmissions towards a specific UE. This is typically achieved using an antenna array consisting of multiple columns of cross-polar antenna elements. The beam-forming helps to improve the link budget but is transparent to the UE, i.e. the UE does not require any explicit knowledge of the beam forming at the Base Station.",Beam-forming uses multiple physical antenna elements to direct the downlink transmissions towards a specific UE. This is done to improve the link budget but is transparent to the UE.
50,"In 5G NR or 4G LTE, Multiple Input-Multiple Output (MIMO) transmission is a key technology specifically in downlink. Signals transmitted from gNB/eNB via different antennas or signals subjected to different and for the receiver unknown, multiple antenna precoding will experience different radio channels even if the MIMO antennas are located at the same site.",In 4G and 5G MIMO is a key technology specifically in downlink. Signals transmitted from gNB/eNB via different antennas or signals subjected to different receivers will experience different radio channels even if the MIMO antennas are located at the same site. 
51,"According to 3GPP specification definition, an antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed.
In other words, each individual downlink transmission is carried out from a specific antenna port, the identity of which is known to the UE and the UE can assume that two transmitted signals have experienced the same radio channel if and only if they are transmitted from the same antenna port.",An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed.
52,"In practical, each antenna port, at least for the downlink transmission can be stated as corresponding to a specific reference signal. The UE receiver can assume that this reference signal can be used to estimate the channel corresponding to specific antenna port. The reference signals can also be used by the UE to derive channel-state information related to the antenna port.","Practically each antenna port, for the downlink transmission can be stated as corresponding to a specific reference signal. The reference signal can be used to estimate the channel corresponding to specific antenna port. "
53,"There is a defined structure in the antenna port numbering such that the antenna ports used for different purposes must have numbers in different ranges. For example, downlink antenna ports starting with 1000 are used for PDSCH. Different transmission layers for PDSCH can use antenna ports in this series, for example, 1000 and 1001 for a two-layer PDSCH transmission. It should be noted that an antenna port is an abstract concept that does not necessarily correspond to a specific physical antenna port.","Different antenna ports for different purposes must have numbers in different ranges. For example, downlink antenna ports starting with 1000 are used for PDSCH."
54,"There is no strict mapping of antenna ports to physical antenna ports in NR as well as in LTE. As in Release 8 LTE the support 2×2 and 4×4 MIMO schemes, there is can be assumed that a 1:1 mapping for antenna port 0 to 3 for Cell specific reference signal (C-RS). But in 5G NR the order of MIMO is about 64 x 64 or more and even numbering antenna ports is in thousand, so it can be directly mapped. The mapping of antenna port to physical antenna is controlled by beam forming as a certain beam needs to transmits the signal on certain antenna ports to form a desired beam. So there is a possibility that two antenna ports mapped to one physical antenna port or a single antenna port mapped to multiple physical antenna ports.",In NR there is no strict mapping of antenna ports to physical antenna ports. There can be assumed that a 1:1 mapping for antenna port 0 to 3 for cell specific reference signal.
55,"DCI based mechanism, although more prompt than the one based on MAC CE, requires additional consideration for error case handling, i.e. the case when a UE fails to decode the DCI containing the BWP activation/deactivation command. To help to recover from such a DCI lost scanarios, the activation/deactivation of DL BWP (or DL/UL BWP pair for the case of unpaired spectrum) by means of timer (bwp-inactivityTimer) is also introduced. With this mechanism, if a UE is not scheduled for a certain amount of time, i.e. expiration of timer, the UE switches its active DL BWP (or DL/UL BWP pair) to the default one.","DCI based mechanism requires additional consideration for error case handling. To help to recover from such a DCI lost scenarios, the activation/deactivation of DL is also introduced. "
56,"3GPP specification for 5G NR defines the three classes for base station namely, Wide Area Base Station, Medium Range Base Station and Local Area Base Station. These classes are corresponding to the Macro cell, Micro cell and Pico cell very well know cell types deployments. 3GPP has specified these classes to make sure that certain radio characteristics are in limits and suitable for specified deployment. These radio characteristics can be maximum allowed transmit power, minimum receiver sensitivity minimum distance between UE and or minimum coupling loss support.","In 5G there are three classes for base station namely, Wide Area Base Station, Medium Range Base Station and Local Area Base Station. These are corresponding to the Macro, Micro and Pico cell. These classes makes sure that certain radio characteristics such as maximum allowed transmit power, minimum receiver sensitivity are in limits and suitable for specified deployment."
57,"Base Stations Type 1-C and 1-H are classified into Wide Area, Medium range and Local Area classes considering their minimum coupling loss requirements for each class. The minimum coupling loss can be defined as the minimum path loss measurement between the base station antenna connector and UE antenna connector in dB, it is denoted by MCL. The MCL is measured at reference port A or B in case of Type 1-C base station and at TAB connector in case of Type 1-H. Below is the range for MCL to each base station class.","Base Stations Type 1-C and 1-H are classified into Wide Area, Medium range and Local Area classes considering their minimum coupling loss requirements for each class. The minimum coupling loss can be defined as the minimum path loss measurement between the base station antenna connector and UE antenna connector in DB."
58,"In base station Type 1-O and 2-O, the transceiver, RDN and Antenna array resides in with one box and does not have any RF connector or reference point at base station to perform the measurements. These types of base station also classified as Wide Area, Medium range and Local Area based on the minimum distance in meters between base stations and UE. This distance is measurement from Radiated Interface Boundary (RIB).","In base station Type 1-O and 2-O, the transceiver, RDN and Antenna array resides in white one box and does not have any RF connector. The base stations are classified as Wide Area, Medium range and Local Area based on the minimum distance between base stations and UE."
59,"BS type 1-C requirements are applied at the BS antenna connector (port A) for a single transmitter or receiver with a full complement of transceivers for the configuration in normal operating conditions. If any external element such as an amplifier, a filter or the combination of such devices is used, requirements apply at the far end antenna connector (port B).",BS type 1-C requirements are applied at the BS antenna connector for a single transmitter or receiver. If any external element is used requirements apply at the far end antenna connector.
60,"Radiated characteristics are defined over the air (OTA), where the operating band specific radiated interface is referred to as the Radiated Interface Boundary (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) characteristics in which the OTA requirements apply are detailed for each requirement. Conducted characteristics are defined at individual or groups of TAB connectors at the transceiver array boundary, which is the conducted interface between the transceiver unit array and the composite antenna.","Radiated characterisics are defined over the air, where the operating band specific radiated interface is referred to as the RIB. Radiated requirements are also referred to as OTA requirements. Conducted characteristics are defined at individual or groups of TAB connectors at the transceiver array boundary- the conducted interface between the transceiver unit array and the composite antenna. "
61,The transceiver unit array is part of the composite transceiver functionality generating modulated transmit signal structures and performing receiver combining and demodulation. The transceiver unit array contains an implementation specific number of transmitter units and an implementation specific number of receiver units. Transmitter units and receiver units may be combined into transceiver units. The transmitter/receiver units have the ability to transmit/receive parallel independent modulated symbol streams.,The transceiver unit array is part of the composite transceiver functionality and contains an implementation specific number of transmitter units and an implementation specific number of receiver units.
62,"The composite antenna contains a radio distribution network (RDN) and an antenna array. The RDN is a linear passive network which distributes the RF power generated by the transceiver unit array to the antenna array, and/or distributes the radio signals collected by the antenna array to the transceiver unit array, in an implementation specific way.",The composite antenna contains a radio distribution network (RDN) and an antenna array. The RDN is a linear passive network which distributes the RF power generated by the transceiver unit array to the antenna array.
63,"The 5G communication specially at higher frequencies or mmWave is using Massive MIMO with Beamforming. Beamforming is a signal processing technique that allows gNB send targeted beams of data to users, reducing interference and making more efficient use of the frequency spectrum with improved spectral efficiency.","5G communication uses massive MIMO with Beamforming. Beamforming is a signal processing technique that allows gNB send targetted beams of data to users, reducing interference and making more efficient use of the frequency spectrum with improved spectral efficiency. "
64,"When user is indoor or moving, the radio link between the UE and gNB is susceptible to blockage and degradation of RF signal which can suddenly interrupt the communication link result in Beam Failure. So to detect the Beam failure at right time, the UE should have some mechanism to measure such sudden and rapid changes in the communication link and simultaneously recover from it to continue the services. The UE does this with the help of Beam failure Recovery (BFR) procedure. BFR procedue is a combined effort of  UE PHY and MAC procedure without involvement of any higher layer signaling.",The radio link between the UE and gNB is susceptible to blockage and degradation of RF signal which can suddenly interrupt the communication link resulting in Beam Failure. The UE should have some mechanism to detect this at the right time. The procedure is called Beam Failure Recover (BFR). BFR is done on UE PHY and MAC procedure without involvment of any higher layer signaling.
65,"We should not get confuse/consider Beam Failure and Radio Link Failure (RLF) are same. In a multi beam sceranio, Radio Link Failure occurs when radio problems within a cell cannot be solved by the recovery procedures or UE is not able to find any suitable beam and Random Access procedure to any beam could not successful to recover the connection failure between gNB and UE. Where as Beam Failure occurs when UE lost the link from one Beam but it is able to make link to anothe beam and able to perform successful Random Access. Following fiugre   shows an example of  beam failure and radio link failure can be detected. For beam failure, there are still beam pairs that may be able to reestablish connection between the gNB and the UE.",Beam Failure and Radio Link Failure are not same. Radio Link Failure occurs when radio problems within a cell cannot be solved by the recovery procedures or UE is not able to find any suitable beam and Random Access procedure to any beam could not successful to recover the connection failure between gNB and UE. Where as Beam Failure occurs when UE lost the link from one Beam but it is able to make link to anther beam and able to perform successful Random Access.
66,"Beam failure detection is a combined L1/L2 procedure where L1 provides the MAC layer indications of beam failure instances (BFIs). The MAC layer counts the indications and declares failure when configured maximum number of BFI indications has been reached. So whenever the PHY layer detects that the RSRP of the Reference signal of the serving beam goes below the threshold i.e 10% BLER of a hypothetical PDCCH, it triggers a Beam failure instance (BFI) and sends it to MAC. MAC layer starts a timer as soon as it receives BFI and it keeps incrementing the counter by 1 for every BFI. When a certain threshold of BFI is reached i.e when BFI_COUNTER >= beamFailureInstanceMaxCount, MAC will trigger Beam Failure and will start the recovery procedure.","Beam failue detection is a combined L1/L2 procedure where L1 provides the MAC layer indications of beam failure instances. The MAC layer counts the indications and declares failure when configured maximum number of BFI indications has been reached. When the PHY layer detects the RSRP of reference signal of the serving beam goes below the threshold, it triggers a Beam failure instance and sends it to MAC. MAC layer starts a timer as soon as it receivers BFI and increments the counter. When a certain threshold of BFI is reached, MAC will trigger beam failure and will start the recovery procedure."
67,"There can be a scenario, where L1 stops sending beam failure instances to MAC or the signal quality has improved and L1 no longer detects any issues. In handle such cases, the UE MAC layer has a timer running everytime PHY reports a BFI, for every occurrence, it increments BFI_COUNTER by 1 and restarts the timer. If there are no beam failure instances received at MAC and the timer expires, the MAC layer will reset the BFI_COUNTER and assume that there are no more beam failure instances.”","L1 can stop sending beam failure instances to MAC or the signal quality has improved and L1 no longer detects any issues. To handle such case, the UE MAC layer has a timer everytime PHY reports a BFI, it increments by 1 and restarts. If there are not beam failure instances received and the timer expires, the MAC layer will reset the counter and assume there are no beam failures."
68,"The UE is provided with a set of resources for the recovery procedure in the BeamFailureRecoveryConfig via RRC message .The Beam Recovey happens by performing RACH on the best candidate beam selected during the Beam failure recovery procedure.
A UE Can perform below two RACH procedures for beam failure recovery request
So when a UE performs CBRA RACH for the recovery procedure, it is performed as a Normal Contention based RACH procedure.",UE has a set of resources for the recovery procedure in the BeamFailureRecoveryConfig via RRC message. This happens by performing RACH on best candidate beam selected during the Beam Failure recovery procedure.
69,"In 5G New Radio the cell bandwidth is expected to be large compared to LTE, but a UE’s receive and transmit bandwidth is not necessarily required to be same as of cell bandwidth. As per 3GPP specification 38.300, the receive and transmit bandwidth of a UE can be adjusted to a subset of total cell bandwidth referred as BWP. This bandwidth can shrink during period of low activity to save power; the bandwidth location can be changed to allow different services. The bandwidth adaption can be achieved by configuring the UE with BWP(s) telling the UE which of the configured BWPs is currently the active one.","5G cell bandwidth is expected to be large compared to LTE, but a UE's receive and transmit bandwidth is not necessarily required to be same of the cell bandwidth. This bandwidth can shrink during period of low activity to save power."
70,"Three types of BWP are available: Initial BWP is used to performs Initial Access Process. It includes Parameters like RMSI (Requested Minimum System Information), CORESET* and RMSI Frequency location/bandwidth/SCS. It can be 24~96 PRBs with different settings and relaxed to wider BWP after RMSI decoding. Active BWP is defined as UE specfic can also be used to BWP performs Initial Access Process. It is the first BWP where UE starts data transfer after RRC configuration/reconfiguration. The very first Active BWP should be different from the default BWP. Default BWP is again UE specific BWP and configured during RRC reconfiguration, if it not configured then it can be assumed that Intial BWP is the default BWP. Every UE would switch back to default BWP when BWP timer expires.","There are three types of BWP: initial BWP is used to perform initial Access process, Active BWP is defined as UE specific can also be used to BWP performs Initial Access Process, default BWP is UE specific BWP and configured during RRC reconfiguration."
71,The traffic patterns within one active data session can change frequently as the data rate may increase or decrease based on the type of service or the user behavior (accessing the internet and answering a phone call for example). It becomes very important to quick switch between different bandwidth parts to manage different power consumption for different data rates.,The traffic patterns within one active data session can change frequently as the data rate may increase or decrease based on the type of service or user behavior. It becomes very important to quick switch between different bandwidth parts to manage different power consumption.
72,"Radio Access barring control refers to a traffic congestion control mechanism to secure and ensure the success of critical communications calls such as emergency calls by restricting connection requests from mobile to base station. The radio access baring can be controlled can be caterogies into following two method: It’s up-to  the mobile operator to use one or both methods for access baring controls depending on the network connection and traffic conditions. For 5G NR, 3GPP has been standardizing a series of traffic congestion mechanism to control mobile communication access to network. There are two high level solutions for controlling network access attempts.",Radio Access barring control refers to a traffic congestion control mechanism to secure and ensure the success of critical communications call such as emergency calls. The radio access baring can be controlled  can be do in two methods. It's upto the mobile operator to use one or both methods.
73,"2G, 3G and 4G networks have used Access Class Barring (ACB) to control access. Access Class is an identifier assigned by network operator to each user to indicate its access priority and it is stored in SIM during provisioning data. Most of the normal SIMs are provisioned with an Access Class within the range o to 9. In addition, a limited group of users may be allocated SIM which have been provisioned with a special Access Class within the range 11 to 15.","2G, 3G, and 4G networks have used Acess Class Barring (ACB) to control access. Access class is assigned by network operator to each user to indicate its access priority. Most of the normal SIMs are provisioned with an Access Class within range 0 to 9."
74,"Various Access Class Barring solutions have evolved over time, e.g. barring specific Access Classes within the range 0 to 9; specifying a probability that access is permitted for a UE with Access Class 0 to 9; barring access for specific services and connection establishment causes. 3GPP release 15 specifications introduces the concept of Unified Access Control (UAC) which is based upon the use of’ Access Identities’ and ‘Access Categories’. A UE associates itself with an Access Identity based upon the available rules.","There are different Acess Class Barring solutions e.g., barring specific access classes, specifying a probability that access is permitted for a UE with Access Class 0 to 9; barring access for specific services and connection establishment causes."
75,"The NAS: Registration Accept message includes an ‘MPS Indicator‘ which can be set to ‘1’ when providing permission to use the MPS service, i.e. this flag can be used to allocate Access Identity 1. Similarly, the same field includes an ‘MCS Indicator’ which can be set to’ 1′ when providing permission to use the MCS service, i.e. this nag can be used to allocate Access Identity 2. Alternatively, the file ‘EFUAC AIC’ available in USIM can be used to provision Access Identity 1 or 2.",NAS Registration Accept message includes a MPS indicator which when set to 1 provides permission to use the MPS service. The same field includes an MCS Indicator which can be set to 1 when providing permission to use the MCS service.
76,"If a connection attempt matches multiple rules, then Access Category belonging to the lowest rule number is selected. UE with Access Category 0 are not subject to Access Barring because the network is responsible for managing mobile terminating calls or Page UE, i.e. the network should not page the UE if the connection is not allowed. Access Categories 32 to 63 can be configured by the operator. The NAS: Registration Accept message provided by the AMF can include the ‘Operator Defined Access Category Definitions’ field which specifies a set of mapping rules.","If a connection attempt matches multiple rules, then Access Category belonging the lowest number is selected. UE with Access Category 0 are not subject to Access Barring because the network is reponsible for manging mobile terminating class."
77,"Access Control Checks based upon Access Identity and Access Category are required when a UE initiates the transition from RRC Idle mode to RRC Connected mode. Access Control Checks arc also required for UE in RRC Connected and RRC Inactive modes when specific events occur, e.g. a mobile originated voice or video call is initiated, a mobile originated SMS is initiated, an uplink NAS message is used to setup or modify a PDU Session, uplink data transfer which requires the use of a suspended PDU Session.",Access Control Checks based on Access Identity and Access Category are required when UE initiates the transition from RRC Idle mode to RRC Connected mode. Access Control Checks arc also required for UE in RRC Connected and RRC Inactive models when specific events occur.
78,"The uac-Barringlnfo within SIB 1 provides the parameters to determine when an Access Barring check is required. An access barring check involves the UE generating a uniformly distributed random number between 0 and 1. If the random number is less than the value of  uac-BarringFactor, then the access attempt is permitted. Otherwise, the access attempt is barred. Configuring a value of ‘0’ for uac-BarringFactor means that all checks will lead to barred access attempts. If an access attempt is barred, the UE generates a second uniformly distributed random number between 0 and 1. The value of T390 is then set equal to (0.7 + 0.6 *rand) *uac-Barring Time seconds, where ‘rand’ is the random number. T390 defines the duration that the UE treats the cell as barred for the corresponding Access Category.","The uac-BarringInfo within SIB 1 provides the parameters to determine when an Access Barring check is required. Access barring check involved the UE generating a uniformly distributed random number between 0 and 1. if the random number is less than the value of uac-BarrierFactor, then the access attempt is permitted, otherwise the access attempt is barred."
79,"Cell search is the procedure by which a UE acquires time and frequency synchronization with a cell and decode the Cell ID of that cell. In 5G NR, Cell search concept is similar to what it is in LTE in terms of decoding Primary Sync Signal (PSS) and Secondary Sync Signal (SSS) to the Physical Cell ID (PCI).","Using cell search the UE acquires time and frequency synchronization with a cell and decode the Cell ID of that cell. In 5G NR, this concept is same as LTE."
80,"UE scans the frequency band on sync raster based  on which frequency band the UE is performing cell search on and is defined by 3GPP 38.104 section 5.4.3.3 to tune specific frequency. The synchronization raster indicates the frequency positions of the synchronization block that can be used by the UE for system acquisition when explicit signaling of the synchronization block position is not present. The synchronization raster and the subcarrier spacing of the synchronization block is depend on separately for each band. In further step UE decode primary and secondary synchronization signals to get Physical Cell ID [PCI], and PBCH DMRS, located on the synchronization raster. PSS, SSS, and NR-PBCH are transmitted in a Synchronization Signal Block (SS Block). SSB is consist of 4-symbol,  1-symbol PSS, a 1-symbol SSS, and a 2-symbol PBCH. Time synchronization in terms of symbol-level and slot-level and frequency synchronization are realized via PSS/SSS.",Synchronization raster indicates the frequency positions of the synchronization block that can be used by the UE for system acquisition when explicit signaling of the synchronization block position is not present. The synchronization raster and the subcarrier spacing of the synchronization block is dependent separately for each band.
81,"A collection of SS Bursts is referred to as an SS Burst Set. Both SS Burst and SS Burst Set may contain one or more elements, while the maximum number of SSBs in an SS Burst is frequency-dependent and it can 4 (below 3 GHz), 8 (3 to 6 GHz), or 64 (6 to 52.6 GHz). The periodicity of the SSB is configured by the network, while the default transmission periodicity for initial cell selection, the SS burst set periodicity is default at 20 ms for all frequency range i.e., 2 NR frames. This interval is four times longer than that in LTE (5 ms) and aims at reducing the “always-on” transmission overheads. The frame and slot timings are defined by the identifiers of SBSs and acquired by the UE.","A collection of SS bursts is referred to as an SS Burst set. Both SS Burst and SS Burst Set may contain one of more elements, while the maximum number of SSBs is an SS Burst may contain one or more elements, while the maximum number of SSBs in a SS Burst is frequency depndent and it can be 4, 8 or 64."
82,"The gNB define multiple candidate positions for SSBs within a radio frame, and this number corresponds to the number of beams radiated in a certain direction. Each SSB can be identified by a unique number called SSB index and identification of which SSB is detected is depend on where UE is located. UE measures the signal strength of Demodulation Reference Signal (PBCH DMRS) of each SSB it detected for a certain period (a period of one SSB Set). From the measurement result, UE can identifies the SSB index with the strongest signal strength. This SSB with the strongest signal strength is the best beam for the UE.",The gNB define multiple candidate positions for SSBs within a radio frame and this number corresponds to the number of beams radiated in a certain direction. Each SSB can be identidied by a unique number called SSB index and indication of which SSB is detected is dependent on the UEs location.
83,"In order to meet higher data rates and more diverse requirements of typical NR scenarios including eMBB, mMTC, and URLLC, a powerful and flexible channel coding scheme is one of the fundamental components of the NR access technology. In the recent RAN1# discussion, various channel coding schemes were discussed and 3GPP considered convolutional codes, turbo codes, polar codes and LDPC codes for evaluation. 3GPP has adopted Polar Coding for 5G/NR Uplink/Downlink control channel for eMBB. To improve the performance of polar coding, concatenated coding and combined decoding schemes are proposed.",A powerful and flexible channel coding scheme is one of the fundamental components of the NR access technology. 3GPP has adopted Polar Coding for 5G NR uplink/downlink control channel for eMBB.
84,"Polar codes can asymptotically (for code length going to infinity) achieve the capacity of any binary input symmetric memoryless channel with encoding and decoding complexity of the order O(N log N), where N is the code length. At present they are the only class of channel codes that are provably capacity achieving with an explicit construction. A Polar code is constructed by recursively applying a linear polarization transform to the binary input symmetric and memoryless channel W, expressed as the 2-by-2 matrix. Repeated use of the transform, n = log2(N) times, results in an N-by-N matrix, denoting the n-fold Kronecker product. Polar codes leverage a phenomenon known as channel polarization. Above transform together with a successive cancellation decoder structure turns the N available channels (N channel uses) in to another set of N bit-channels, referred to as synthesised channels, such that the capacities of these bit channels tend to 0 (fully unreliable) or to 1 (fully reliable) when N goes to infinity.","Polar codes can asymptotically achieve the capacity of any binary input symmetric memoryless channel with encoding and decoding complexity of O(N logN), where N is the code length.  A polar code is constructed by recursively applying a liner polarization transform to a binary input symmetric and memoryless channel."
85,"The proportion of reliable channels, K, tends to the capacity of the original communication channel. Data is communicated by placing information bits on the K reliable channels and placing fixed bits, usually zeros, on the N-K unreliable channels. These bits on the unreliable channels are referred to as frozen bits, and the set of their positions is referred to as the frozen set F of size N-K. Frozen bits and the frozen set is known by both the encoder and the decoder. In this way, a polar code of code length N, information word length K, and code rate R=K/N is constructed.","The proposition of reliable channels, K, tends to the capacity of the original communication channel. Data is communicated by placing information bits on the K reliable channels and placing fixed bits, usually zeros, on the N-K unreliable channels."
86,"An advantage of the class of Polar Codes is that different types of decoders are possible for the same encoder. Therefore Polar codes are suitable to be used in a wide range of scenarios with diverse requirements. In contrast, other candidate schemes, such as Turbo codes, LDPC codes, and (TB)CCs cannot provide such flexibility. The power and area efficiency of Turbo decoders deteriorates very fast when increasing the block size. LDPC codes perform typically well for large blocks and high rates, however, performance is poor for rates below half.  It is noted that such code rate range can be the most common scenario in eMBB case. ",Advantage of the class of polar codes is that different types of decoders are possible for same encoder. Compared to other candidate schemes polar codes are suitable to be used in a wide range of scenarios with diverse requirements.
87,"The performance of Polar Codes keeps improving along with increasing list size of the SCL decoder. According to our simulation with list sizes up to 2048, we have not observed any performance saturation so far. In contrast, we observe that the performance of turbo codes and LDPC codes saturates with the number of decoding iterations. As a result, the operators can keep improving the system capacity with newer ASIC technology. For example, when the list size is increased from 32 to 128 (the decoding complexity increases about by a factor of four), the BLER performance will gain another 0.5 ~0.7dB for some control channels. Therefore the system capacity can simply be increased with the availability of new Polar decoding chips.","The performance of Polar Codes keeps improving with increasing list size of SCL decoder compared to other codes such as turbo codes and LDPC codes. As a result, the operators keep moving the system capacity with newer ASIC technology."
88,"The latency performance of a communication system is analyzed for both control plane and user plane. In this post lets discuss about control plane latency. The definition of control plane latency as per 3GPP TR 38.913 is “the time to move from a battery efficient state e.g. IDLE  to the start of continuous data transfer e.g. ACTIVE” . Considering agreements made during the study item phase of NR, the control plane latency can be analyzed as the transition time from an inactive state to the time to send the first uplink packet in the inactive state.","The latency performance of a communication system is analyzed for both control plane and data plane. In NR, the control plane latency can be analyzed as the tranision time from an inactive state to the time to send the first uplink packet in the inactive state."
89,"In LTE control region, the PDCCH is allocated across entire system bandwidth but NR PDCCH is transmit in specifically designed CORESET region to a specific region in frequency domain. A UE is configured to blindly monitor a number of PDCCH candidates of different DCI formats and different aggregation levels. The blind decoding processing has an associated UE complexity cost but is required to provide flexible scheduling and handling of different DCI formats with lower overhead.","LTE PDCCH is assigned across the complete system bandwidth, however NR PDCCH is delivered in a CORESET zone. UE examines PDCCH candidates with different DCI formats and aggregation parameters. Blind decoding is required for flexible scheduling and low-overhead DCI format handling."
90,"3GPP has speficied a mapping between 5G-GUTI and 4G-GUTI. This mapping is required for UE mobility between 4G and 5G networks. For example, when a Mobile User moves from 5G to 4G, it requires to send a GUTI to MME, then mobile has to map the 5G-GUTI onto thw 4G-GUTI and forward it to MME.  MME perform a reverse mapping of 4G GUTI to 5G-GUTI to find out the AMF from where the MME needs to contact to fetch the UE context. In similar way, when a mobile moves from 4G to 5G, mobile maps and send 4G GUTI to AMF and AMF decode the MME ID for retrieve the User context. Below figure show the mapping and bit wise detailed information for 5G and 4G GUTI.","3GPP mapped 5G-GUTI to 4G-GUTI. This mapping is needed for 4G-to-5G UE mobility. When a mobile user switches from 5G to 4G, the mobile must transmit a GUTI to MME and map the 5G-GUTI onto the 4G-GUTI. MME reverse maps 4G GUTI to 5G-GUTI to locate the AMF to contact for UE context. When a smartphone goes from 4G to 5G, it maps and sends 4G GUTI to AMF, which decodes MME ID to obtain user context. Below is 5G and 4G GUTI mapping and bit-wise detail."
91,"A gNB may consist of a gNB-Control Unit (CU) and one or more gNB-Distributed Units (DUs), and the interface between gNB-CU and gNB-DU is called F1. The NG and Xn-C interfaces for a gNB terminate in the gNB-CU. The maximum number of gNB-DUs connected to a gNB-CU is only limited by implementation. As per 3GPP specifications one gNB-DU connects to only one gNB-CU, but implementations that allow multiple gNB-CUs to connect to a single gNB-DU e.g. for added resiliency, are not precluded. One gNB-DU may support one or more cells (sector). The internal structure of the gNB is not visible to the core network and other RAN nodes, so the gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.","A gNB consists of a gNB-Control Unit (CU) and one or more gNB-Distributed Units (DUs), and their interface is designated F1. gNB-CU terminates NG and Xn-C connections. Implementation limits the number of gNB-DUs connected to a gNB-CU. According to 3GPP specifications, one gNB-DU links to one gNB-CU, although implementations that allow several gNB-CUs to connect to a single gNB-DU are not barred. One gNB-DU can hold several cells (sector). The gNB-CU and associated gNB-DUs are only visible to other gNBs and the 5GC as gNBs."
92,"The gNB-CU-UP terminates the E1 interface connected with the gNB-CU-CP and the F1-U interface connected with the gNB-DU. A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs. The gNB-CU-CPis connected to the gNB-DU through the F1-C interface, and gNB-CU-UP is connected to the gNB-DU through the F1-U interface.  One gNB-CU-UP is connected to only one gNB-CU-CP, but implementations allowing a gNB-CU-UP to connect to multiple gNB-CU-CPs e.g. for added resiliency, are not precluded. One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP. One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP. The basic functions of the E1 interface include E1 interface management function and E1 bearer context management function.","The gNB-CU-UP terminates the gNB-CU-E1 CP's and gNB-F1-U DU's interfaces. A gNB can have a gNB-CU-CP, gNB-CU-UPs, and gNB-DUs. gNB-CU-CP is connected to gNB-DU via F1-C, and gNB-CU-UP via F1-U. One gNB-CU-UP is connected to one gNB-CU-CP, however many connections are possible for resiliency. One gNB-DU can control many gNB-CU-UPs. The same gNB-CU-CP can control numerous gNB-CU-UPs. E1 interface management and bearer context management are basic functionalities."
93,5G networks are expected to support applications demanding ultra-reliable and low latency communication services (URLLC). To support these kind of applications 5G-NR introduced grant free uplink transmission feature a.k.a. Transmission without grant (TWG). i.e. data transmission without resource request. Transmission without grant can avoid the regular handshake delay e.g. sending the scheduling request and waiting for UL grant allocation. Another advantage is that it can relax the stringent reliability requirements on control channels.,"5G networks will support ultra-reliable and low-latency applications (URLLC). 5G-NR introduced grant-free uplink transmission (a.k.a. Without permission (TWG). Transmitting data without requesting resources. Transmission without grant can skip the typical handshake delay, such as scheduling request and UL grant allocation. It also relaxes control channel dependability requirements."
94,"TWG Type 1 is very much similar to LTE semi-persistent scheduling (SPS) where UL data transmission is based on RRC reconfiguration without any L1 signaling. RRC provides the grant configuration to UE through higher layer parameter named as ConfiguredGrantConfig including the parameter rrc- ConfiguredUplinkGrant without the detection of any UL grant in a DCI. Potentially SPS scheduling can provide the suitability for deterministic URLLC traffic pattern, because the traffic properties can be well matched by appropriate resource configuration. In type 2 an additional L1 signaling (Downlink Control Indication) is introduced, where uplink is semi-persistently scheduled by an UL grant in a valid activation DCI. The Grant is activated and deactivated through DCI scrambled with CS-RNTI. RRC only provides the higher layer parameter ConfiguredGrantConfig not including rrc-ConfiguredUplinkGrant. The DCI signaling can enable fast modification of semi-persistently allocated resources. In this way, it enables the flexibility of UL Grant Free transmission in term of URLLC traffic properties for example packet arrival rate, number of UEs sharing the same resource pool and/or packet size.","TWG Type 1 is like LTE SPS, where UL data transfer uses RRC reconfiguration without L1 signaling. RRC delivers UE grant configuration through ConfiguredGrantConfig, including rrc-ConfiguredUplinkGrant, without detecting UL grant in DCI. If resource configuration meets traffic attributes, SPS scheduling may work for predictable URLLC traffic. In type 2, a UL grant in a valid activation DCI semi-persistently schedules uplink. DCI enables and deactivates Grant with CS-RNTI. RRC does not offer rrc-ConfiguredUplinkGrant. DCI signaling can swiftly adjust semi-persistent resources. UL Grant Free transmission is flexible in URLLC traffic aspects such packet arrival rate, number of UEs sharing a resource pool, and packet size."
95,"The extensions of X2 include functions adopting EN-DC and flow control for split bearers for non-standalone operation. The flow control function, which was defined for LTE-DC split bearers in Release 12, is used for appropriately split downlink data when using the radio resources of multi-ple RAN nodes. Although functions and interfaces just for basic flow control were specified for LTE-DC, the information exchanged between RAN nodes is further enhanced to optimize the flow control for non-standalone operation. Although Xn is based on the X2 function, the UE context management function is chiefly enhanced for adopting new QoS flow framework and network slice.","X2 adds EN-DC and split-bearer flow control for non-standalone operation. Flow control, defined for LTE-DC split bearers in Release 12, splits downlink data while employing multiple RAN nodes. LTE-DC specifies just basic flow control capabilities and interfaces, however information shared between RAN nodes optimizes flow control for non-standalone operation. Xn is based on X2, but UE context management is improved to embrace a new QoS flow framework and network slice."
96,"The extensions of S1 include a function that reports data volume for a specific RAT in non-standalone operation. In the standardization discussions, there were demands from operators for charging based on the data volume of each RAT (i.e., LTE and NR) in non-standalone operation. Thus, this function was introduced for calculating the amount of data volume via NR. In non-standalone operation, since the S1‒C interface is only established between the Master Node and Core Network, the data volume through Master Node terminated bearers is counted by the Master Node itself and reported directly to the Core Network via S1, while the data volume from Secondary Node terminated bearers is counted by Secondary Node and reported to Master Node via X2, and then reported by Master Node to Core Node via S1.","S1 extensions reveal RAT's non-standalone data volume. Operators sought payment based on LTE and NR data volume in non-standalone operation. NR data volume is calculated. In non-standalone operation, since the S1C interface is only established between Master Node and Core Network, data volume through Master Node terminated bearers is counted by Master Node and reported directly to Core Network via S1, while data volume from Secondary Node terminated bearers is counted by Secondary Node and reported to Master Node via X2, and then reported by Master Node to Core Node via S1."
97,"To address the issue of explosive in-creases of the bandwidth required for the transport between the Central Unit (CU) and Distributed Unit (DU) by the introduction of massive MIMO and extending the frequency bandwidth using Cloud RAN (C-RAN) deployment, the new functional split between CU (gNB-CU) and DU (gNB-DU) within gNB and the corresponding open interface between these nodes were defined. Specifically, a functional split was adopted where the PDCP layer and above can be located in the gNB-CU, and the RLC layer and below can be located in the gNB-DU. ","To address the explosive increases in bandwidth required for transport between the Central Unit (CU) and Distributed Unit (DU) by massive MIMO and Cloud RAN (C-RAN) deployment, a new functional split between CU (gNB-CU) and DU (gNB-DU) within gNB and the corresponding open interface between these nodes were defined. The PDCP layer and above can be located in the gNB-CU, and the RLC layer and below in the gNB-DU."
98,"In addition to the functional split between gNB-CU and gNB-DU, the functional split of C-plane and U-plane in gNB-CU. For example, when the C-plane function can be placed near gNB-DU and the U-plane functions can be placed near Core Network, the RRC signal used by the C-plane can be controlled without long delays and the U-plane functions can be placed in the cloud. Conversely, when the C-plane function is placed near Core Network and the U-plane function is placed near gNB-DU, it is possible to reduce the delays of U-plane signals for edge computing applications, and the C-plane functions can be migrated to the cloud.","In gNB-CU, C-plane and U-plane are functionally divided. When the C-plane function is near gNB-DU and the U-plane function is near Core Network, the C-RRC plane's signal may be regulated without significant delays and the U-plane functions can be placed in the cloud. When the C-plane function is near Core Network and the U-plane function is near gNB-DU, edge computing signal delays can be reduced and C-plane functions can be transferred to the cloud."
99,"With 3GPP standardization, an open interface between the C-plane termination parts and U-plane termination parts of gNB-CU has been specified so that this sort of functional separation can be achieved even between different vendors. A node that terminates the C-plane of gNB-CU is called gNB-CU-CP, and a node that terminates the U-plane of the gNB-CU is called gNB-CU-UP. The standard interface between these nodes is specified as E1.","3GPP standardization specifies an open interface between gNB-C-plane CU's and U-plane terminating portions, allowing functional separation even between suppliers. gNB-CU-CP terminates the C-plane, while gNB-CU-UP terminates the U-plane. E1 is the standard node interface."
100,"To support priority handling, multiple logical channels at MAC layer, each logical channel given its own RLC entity, which can be multiplexed into one transport channel by the MAC layer. At the receiver, the MAC layer handles the corresponding de-multiplexing and forwards the RLC PDUs to their respective RLC entity. To support the de-multiplexing at the receiver, a MAC header is used. In addition to multiplexing of different logical channels, the MAC layer can also insert MAC control elements into the transport blocks to be transmitted over the transport channels. A MAC control element is used for inband control signaling and identified with reserved values in the LCID field, where the LCID value indicates the type of control information.","To provide priority handling, the MAC layer multiplexes multiple logical channels into one transport channel. The MAC layer handles demultiplexing and forwarding RLC PDUs at the receiver. MAC headers support receiver demultiplexing. In addition to multiplexing logical channels, the MAC layer can inject control elements into transport blocks. A MAC control element is used for inband control signaling and designated with reserved values in the LCID field."
101,"The placement of the MAC headers has been improved in NR compared to LTE, considering the low latency applications in mind. Instead of placing all the MAC header information at the beginning of a MAC PDU (which implies that assembly of the MAC PDU can not start until the scheduling decision is available)  the sub-header corresponding to a certain MAC SDU is placed immediately before the SDU. This helps the PDUs to be pre-processed before scheduling decision is received . If necessary, padding can be appended to align the transport block size supported in NR. The sub-header contains the identity of the logical channel (LCID) from which the RLC PDU originated and the length of the PDU in bytes. There is also a flag indicating the size of the length indicator, as well as a reserved bit for future use.","For low-latency applications, NR's MAC header placement is better than LTE's. Instead of inserting all MAC header information at the beginning of a MAC PDU (which implies assembly can't begin until the scheduling decision is known), the sub-header is added before the SDU. Preprocessing PDUs helps with scheduling. If needed, padding can align NR transport block size. Sub-header contains LCID and PDU length in bytes. A length indicator flag and reserved bit are also included."
102,"Over all structure of MIB and SIB in NR is almost similar to LTE and other legacy technologies. However there is a major difference related to the periodical transmission of SIBs. In LTE and other legacy technologies the SIBs are broadcasted priodically regardless of whether UE wants it or not. But, in New Radio (NR) there are two versions of SIBs. One is being transmitted periodically like LTE and other is being transmitted only on-Demand i.e. when requested by UE.","NR's MIB and SIB are identical to LTE and other legacy technologies. However, SIB transmission is different. LTE and other legacy technologies broadcast SIBs whether UE likes them or not. NR has two SIB variants. One is transmitted periodically like LTE and the other on-demand via UE."
103,"During UE attach, after a radio bearer is set up, the eNB (in NSA Mode)  or gNB (in SA Mode) delivers measurement configurations to the UE based on the mobility trigger and policy settings. The measurement configuration can be included in the RRC Reconfiguration message or the RRC Resume message. It means that the network can update the measurement configuration for the UE while the UE is in a CONNECTED mode, resuming from INACTIVE to CONNECTED mode or provide a new measurement configuration in the handover command.","During UE attach, the eNB (in NSA Mode) or gNB (in SA Mode) sends measurement configurations to the UE based on the mobility trigger and policy settings. Measurement configuration can be incorporated in RRC Reconfiguration or RRC Resume. The network can alter the UE's measurement settings while it's connected, resuming from INACTIVE to CONNECTED, or in the handover instruction."
104,"A UE in RRC_CONNECTED maintains a measurement object list, a reporting configuration list, and a measurement identities list according to signalling and procedures in this specification. The measurement object list possibly includes NR intra-frequency object(s),  NR inter-frequency object(s) and inter-RAT objects. Similarly, the reporting configuration list includes NR and inter-RAT reporting configurations. Any measurement object can be linked to any reporting configuration of the same RAT type. Some reporting configurations may not be linked to a measurement object. Likewise, some measurement objects may not be linked to a reporting configuration. The measurement procedures distinguish the following types of cells: For NR measurement object(s), the UE measures and reports on the serving cell(s), listed cells and/or detected cells.","A RRC CONNECTED UE stores a measurement object list, a reporting configuration list, and a measurement identities list. Measurement objects may comprise NR intra-frequency, inter-frequency, and inter-RAT objects. NR and inter-RAT reporting configurations are also listed. Any measurement item can be linked to any same-RAT reporting configuration. Some reporting settings aren't related to measurements. Some measurement objects aren't related to reporting configurations. Measurements distinguish these sorts of cells: The UE measures and reports serving, listed, and/or detected cells for NR measurement objects."
105,"In any telecom technology (2G, 3G, 4G or 5G), mobility (handover) decision whether mobile device will be handover or not is taken by by base station based on measurement reports from the mobile device. There are multiple measurement items (RSRP, RSRQ, SINR) and multiple ways (periodic, event triggered) to measure the signal quality of the serving cell and neighbor cells. In Ideal case, a base station shall allow UE to report serving cell and neighbor cell signal quality and trigger the handover with single measurement, but in practice it can create overload conditions due to unnecessary ping pong handovers. As solution to avoid such situation, 3GPP specifications have proposed a set of predefined set of measurement report mechanism to be performed by UE. These predefined measurement report type is called “Event“. The type of “event” a UE have to report is specified by RRC signaling message sent by the base station.","In any telecom technology (2G, 3G, 4G or 5G), base stations make mobility (handover) decisions based on mobile device measurement reports. There are several approaches (periodic, event-triggered) to measure serving cell and neighbor cell signal quality (RSRP, RSRQ, SINR). A base station should allow UE to report serving cell and neighbor cell signal quality and trigger the handover with a single measurement, but in practice it can cause overload owing to unnecessary ping pong handovers. 3GPP specifications propose a set of standardized measurement report mechanisms for UE to use. This report type is called ""Event"" Base station RRC signaling specifies the ""event"" a UE must report."
106,"Event A2 is typically used to trigger a mobility procedure when a UE moves towards cell edge. Event A2 does not involve any neighbor cell measurements so it may be used to trigger a blind mobility procedure.or it may be used to triggers neighbor cell measurements which can then be used for a measurement based mobility procedure.
For example, the gNB may configure measurement gaps and inter-frequency or inter-system measurements after Event A2 has been triggered. This approach means that the UE only needs to complete the intra/inter frequency or Inter system measurements where coverage conditions are relatively poor and there is a high chance that a handover will be required.","Event A2 occurs when a UE approaches the cell edge. Event A2 doesn't measure neighboring cells, causing blind mobility. The procedure can trigger neighbor cell measurements. The gNB may configure measurement gaps, inter-frequency, or inter-system measurements when Event A2 is triggered. When coverage is low and a handover is likely, the UE must perform intra/inter frequency or inter system measurements."
107,"Event A3 is triggered when a neighbor cell becomes better than a special cell (SpCell) by an offset. A special cell is the primary serving cell of either the Master Cell Group (MCG) or Secondary Cell Group (SCG)). The offset can be either positive or negative. This event is typically used for intra-frequency or inter-frequency handover procedures. When Evenet A2 is triggered  the UE may be configured with measurement gaps to measure the inter frequency objects and Event A3 for inter-frequency handover. Event A3 provides a handover triggering mechanism based upon relative measurement results, e.g. it can be configured to trigger when the RSRP of a neighbor cell is stronger than the RSRP of special cell.","When a neighbor cell is offset-better than a SpCell, A3 is activated. MCG and SCG serve mostly through special cells. Positive/negative offset. This is a handover event. Event A2 may set the UE to measure inter-frequency objects and Event A3 to handover. When a neighbor cell's RSRP is stronger than a special cell's, Event A3 prompts a handover."
108,"Event A4 is triggered when neighbor cell becomes better than defined threshold. This event can be used for handover procedures which does not depend upon the coverage of the serving cell. For example, in load balancing feature take the decision to handover a UE away from the serving cell due to load conditions rather than radio conditions. In this case, the UE only needs to verify that the target cell is better than certain signal level threshold and can provides adequate coverage.","Event A4 is triggered when a neighbor cell improves. This event can be utilized for handovers that don't depend on cell coverage. In load balancing, decide to handover a UE based on load conditions rather than radio conditions. The UE just needs to validate that the target cell has appropriate signal level and coverage."
109,"Event A5 is triggered when a special cell becomes worse than threshold 1, while a neighboring cell becomes better than threshold 2. You can thing Event A5 is combination of Event A2 and Event A4.  This event  is typically used for intra-frequency or inter-frequency handover procedures. After Event A2 is trigger the UE may be configured with measurement gaps and an Event A5 for inter-frequency handover. Event A5 provides a handover triggering mechanism based upon absolute measurement results. It can be used to trigger a time critical handover when a current special cell becomes weak and it is necessary to change towards another cell which may not satisfy the criteria for an event A3 handover.","Event A5 occurs when a particular cell falls below threshold 1 and a nearby cell exceeds threshold 2. Event A5 combines A2 and A4.
This event is for intra- or inter-frequency handovers. After Event A2 is triggered, the UE can be setup for measurement gaps and inter-frequency handover. Event A5 triggers handover based on absolute measurements. It can trigger a time-critical handover when a special cell becomes weak and it's necessary to switch to another cell that doesn't meet event A3 requirements."
110,"Event B1 can be used for inter-RAT handover procedures which does not depend upon the coverage of the serving cell. For example, in load balancing feature take the decision to move a UE away from NR due to load conditions rather than radio conditions. In this case, the UE only needs to verify that the target cell in other RAT (e.g. LTE) is better than certain signal level threshold and can provides adequate coverage.","Event B1 is used for inter-RAT handovers that don't depend on cell coverage. In load balancing, shift a UE away from NR based on load, not radio circumstances. In this instance, the UE just needs to verify if the target cell in another RAT (e.g. LTE) has appropriate coverage."
111,"Event B2 is triggered when a primary serving cell becomes worse than threshold1, while a neighbor inter-RAT cell becomes better than threshold2. This can be used to trigger inter-RAT mobility procedures when the primary serving cell becomes weak. Inter-system neighbor cell measurements arc used to ensure that the target cell provides adequate coverage.",Event B2 is triggered when a primary serving cell is worse than threshold1 and a neighbor inter-RAT cell is better. This can trigger inter-RAT movement when the serving cell weakens. Measurements of neighbor cells guarantee that the target cell has enough coverage.
112,"NR-RSSI  stands for NR carrier Received Signal Strength Indicator, it comprises the linear average of the total received power (in Watt) observed only in certain OFDM symbols of measurement time resource(s), in the measurement bandwidth, over N number of resource blocks from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise etc. The measurement time resource(s) for NR Carrier RSSI are confined within SS/PBCH Block Measurement Time Configuration (SMTC) window duration.","NR-RSSI is the linear average of the total received power (in Watt) over N resource blocks from all sources, including co-channel serving and non-serving cells, neighboring channel interference, thermal noise, etc. SS/PBCH Block Measurement Time Configuration limits NR Carrier RSSI measurements (SMTC)."
113,"CSI-RSSI stands for CSI Received Signal Strength Indicator, it comprises the linear average of the total received power (in Watt) observed only in OFDM symbols of measurement time resource(s), in the measurement bandwidth, over N number of resource blocks from all sources, including cochannel serving and non-serving cells, adjacent channel interference, thermal noise etc. The measurement time resource(s) for CSI-RSSI corresponds to OFDM symbols containing configured CSI-RS occasions.","CSI-RSSI is the linear average of the total received power (in Watt) in OFDM symbols of measurement time resource(s), in the measurement bandwidth, over N resource blocks from all sources, including cochannel serving and non-serving cells, neighboring channel interference, thermal noise, etc. CSI-RSSI resources are OFDM symbols containing CSI-RS events."
114,CSI-SINR stands for CSI signal-to-noise and interference ratio.It is defined as the linear average over the power contribution (in Watt) of the resource elements carrying CSI reference signals divided by the linear average of the noise and interference power contribution (in Watt) over the resource elements carrying CSI reference signals within the same frequency bandwidth.,CSI-SINR is signal-to-noise-and-interference ratio. It's the linear average of the power contribution (in Watt) of resource components carrying CSI reference signals divided by the linear average of the noise and interference power contribution (in Watt) over the same frequency bandwidth.
115,"For any communication technology, Modulation and Coding Scheme (MCS) defines the numbers of useful bits which can carried by one symbol. In contrast with 5G or 4G, a symbol is defined as Resource Element (RE) and MCS defined as how many useful bits can be transmitted per Resource Element (RE) . MCS depends on radio signal quality in wireless link, better quality the higher MCS and the more useful bits can be transmitted with in a symbol and bad signal quality result in  lower MCS means less useful data can be transmitted with in a symbol. In other words, we can say MCS depends  Blocker Error Rate (BLER). Typically there is a BLER threshold defined that equal to 10%. To maintain BLER not more than this value in varying radio condition Modulation and Coding Scheme (MCS) is allocated by gNB using link adaptation algorithm. The allocated MCS is signalled to the UE  using DCI over PDCCH channel e.g. DCI 1_0, DCI 1_1.","MCS determines a communication system's usable bits per symbol. A symbol is a Resource Element (RE) and MCS is the number of useable bits per RE. MCS depends on radio signal quality in a wireless link; higher quality means more usable bits can be delivered per symbol. BLER affects MCS (BLER). 10% BLER. In diverse radio situations, gNB's link adaptation algorithm allocates MCS to maintain BLER. UE is signaled by DCI over PDCCH, e.g. DCI 1_0, DCI 1_1."
116,"Modulation defines how many bits can be carried by a single RE  irrespective of whether it’s useful bit or parity bits. 5G NR supports QPSK, 16 QAM, 64 QAM and 256 QAM modulation . With QPSK there are 2 bits can be transmitted per RE, with 16QAM  it can be 4 bits, with 64QAM it can be 6 bits and with 256QAM it can 8 bits. These 16, 64 and 256 are know as modulation order of QAM Modulation.","Modulation defines how many bits a single RE may carry, useful or parity. 5G NR uses QPSK, 16 QAM, 64 QAM, and 256 QAM. QPSK can broadcast 2 bits per RE, 16QAM 4, 64QAM 6, and 256QAM 8 bits. QAM modulation order is 16, 64, and 256."
117,"Code rate can be defined as the ratio between useful bit and total transmitted bit (Useful + Redundant Bits).  These Redundant bits are added for Forward Error Correction (FEC). In other words we can it is the ratio between the number of information bits at the top of the Physical layer and the number of bits which are mapped to PDSCH at the bottom of the Physical layer. We can also say, it  a measure of the redundancy which is added by the Physical layer. A low coding rate corresponds to increased redundancy.",Code rate is the ratio of useful bits to total bits (Useful + Redundant). Forward Error Correction uses redundant bits (FEC). It's the ratio of information bits at the top of the Physical layer to bits mapped to PDSCH at the bottom. It measures the Physical layer's redundancy. Low coding rate equals redundancy.
118,"Once the UE has transmitted Msg1 RACH preamble, it does perform following procedure for Msg2 RAR. The downlink transport block (PDSCH) contains the MAC PDU. The UE MAC PDU consists of one or more MAC subPDUs. Since multiple UEs may send a Preamble in the same RACH opportunity, they will all be addressed by the same RA-RNTI. Thus, multiple Random Access Responses (RAR) may be carried in a single MAC PDU (They correspond to different UEs that initiated the random access procedure in the same RACH opportunity).","After Msg1 RACH preamble, UE sends Msg2 RAR. PDSCH has MAC PDU. UE MAC PDU comprises of MAC subPDUs. Multiple UEs sending a Preamble in the same RACH opportunity will have the same RA-RNTI. Thus, a single MAC PDU can carry many RARs (They correspond to different UEs that initiated the random access procedure in the same RACH opportunity)."
119,"In any telecommunication technology starting from 2G to 5G, Neighbor relation or to say Neighbor planning is an important activity. Neighbor relation information is very critical for cell re-selection while mobile device is in IDLE mode and for handovers when is it in mobility. In older days, Radio Network Planner and Optimization engineer used to maintain neighbor relation manually with single RAT neighbor, configured during the system initial provisioning and bring-up. Many time neighbors configuration is missed and identified while doing network drive tests. As technology evolved, 2G start having 3G nodes as neighbors and 4G use to have 3G/2G for Inter rate Mobility management. Thanks to Self Organizing Network (SON) features which make neighbor relation configuration easy and efficient. SON features adds neighbor automatically using network sniffing during bring up and later UE assisted and X2 neighbor update procedures.","2G to 5G telecommunications require neighbor planning. Neighbor relation information is critical for IDLE cell reselection and mobility handovers. Engineers used to manually maintain a single RAT neighbor during system provisioning and bring-up. Tests miss neighbors' network settings. 2G nodes became neighbors of 3G nodes, and 4G utilised 3G/2G for IRM. SON simplifies neighbor configuration. During bring up, UE-assisted, and X2 neighbor update, SON adds neighbors."
120,"As a first level , the NBRs relation can be generated manually or RF planning tool. A general guideline, while defining the neighbor relations, the planning engineer should perform a check of Physical cell IDs for adjacent neighbor to avoid PCI collision and PCI confusion situations, these can impact the Handover and Throughput KPIs of network. The first level of NBRs relation can be provisioned in the initial configuration of system. Some system support sniffing of surrounding network (specifically small cells), where it can scan and get the NBRs information of already on-air cells by decoding broadcast information. One the system is up and operation, the further NBRs can be added through UE assisted ANR and eNB config update procedures over X2AP.","NBR relations can be generated manually or with RF software. Planning engineers should ensure Physical cell IDs while designing neighbor relations to minimize PCI collision and confusion, which can affect Handover and Throughput KPIs. System initialization comprises NBRs. Some systems can sniff small-cell networks to decode NBRs. New NBRs can be added via UE-assisted ANR and eNB config update over X2AP once the system is operational."
121,"UE assisted ANR helps SON to populate NBRs relation based on measurement reports from UE, Whenever UE reports an PCI SON function checks if the PCI is available in the NBR relation table, if it is not available then it may ask UE to report CGI (Cell Global Identifier), where UE read the SIB#1 information of NBR cell and report to serving base station. UE assisted ANR can be configure based on measurement Event or can be periodic, the periodicity can defined by operation as it may impact the overall cell average throughput KPIs because, every time UE is measuring and decoding NBRs cell information, it needs to go into measurement gap period and data scheduling during gap period is  not allowed.","UE-assisted ANR populates NBRs based on UE measurement reports. When UE reports a PCI, SON checks if it's in the NBR relation table; if not, it may ask UE to provide a CGI (Cell Global Identifier), where UE reads SIB#1 from NBR cell and reports to serving base station. UE-assisted ANR might be event- or period-based. The periodicity can be defined by operation as it may effect total cell average throughput KPIs. When UE is measuring and decoding NBRs cell information, it must go into measurement gap period and data scheduling is not allowed."
122,"If the periodicity of UE assisted ANR is too frequency, then UE will go in measurement gap very frequency which may impact the User experiences. The UE assisted ANR may not be possible for NSA deployments because  in EN-DC configuration NR base station does not broadcast the SIB#1 information which result in UE will not be able to decode and report the CGI information. Additionally, if NR base station is not connected to MME (only user plane connected) then the transport layer information to setup X2 between LTE and NR will not be available via tunnel discovery procedure.","If UE-assisted ANR is too frequent, measurement gaps will harm user experience. In EN-DC configuration, NR base stations don't broadcast SIB#1, therefore UE can't decode and report CGI information. Tunnel discovery won't be able to set up X2 between LTE and NR if the NR base station isn't linked to MME (only the user plane)."
123,"5G network deployments are expected to be very dense and there can be situations where some of the base station go-off the air and become on-air. This requires the NBR relation to be dynamic, the NBR which are not used for long period can be delete and new NBRs reported via UE assisted ANR and X2 assisted ANR be added to make a clean NBR relation table.","Some 5G base stations may go off- and on-air, leading to dense network installations. Old NBRs can be erased and new NBRs reported via UE assisted ANR and X2 assisted ANR to establish a clean NBR relation table."
124,"Exynos Modem 5100 is making 5G a reality . EXYNOS 5100 is fully compliant with 5G NR (New Radio) standard to support new spectrums including sub-6GHz and mmWave for faster data speed of up to 6Gbps. Furthermore, the Exynos  5100 is the industry’s first multi-mode modem that supports 5G NR with the legacy modes from 2G to 4G LTE. The modem is built on 10LPP process for low power, and is delivered as a single chipset that consists of modem, RF IC, ET (Envelop Tracking) and power management IC for faster time-to-market. With the Exynos 5100, 5G NR enables various brand new experiences through enhanced broadband (eMBB) and massive connection with ultra-reliable and low latency (URLLC). The Exynos Modem 5100, built on the advanced 10nm FinFET process with low-power design, features better power efficiency. The Exynos Modem 5100 is delivered with the Envelope Tracking IC that efficiently determines the power supply voltage needed by tracking and optimizing signal level in real-time.","Exynos 5100. EXYNOS 5100 supports 6Gbps sub-6GHz and mmWave. Exynos 5100 is the first 5G NR/2G-4G LTE modem. The low-power 10LPP modem is a single chipset with RF, ET, and power management ICs. Exynos 5100 5G NR supports eMBB, large connectivity, and low latency (URLLC). Exynos Modem 5100's 10nm FinFET and low-power architecture boost efficiency. Envelope Tracking IC enhances signal level to calculate power supply voltage."
125,"Many of the operator across the global has started providing 5G services using NSA mode with Option 3.x . In NSA mode the network topology consist of a LTE cell, NR cell both connected to 4G Core Network. To get access to the 5G services UE has to first connect to 4G LTE cell as LTE is the master cell and then later based on the measurement a suitable 5G NR cell is added to UE","Many carriers offer 5G services using NSA mode with Option 3.x. NSA mode connects LTE and NR to 4G Core Network. Before adding a 5G NR cell, UE must connect to a 4G LTE master cell."
126,"In any wireless system, for accurate, efficient coordination and intercommunication base station must know the all capability about the UE.  The base station enquires the UE Capability and UE report all information. After knowing the UE capability, the base station can make correct scheduling for the UE. If the UE  supports a certain feature or function, the base station shall configure UE for it and if the UE does not support a certain feature, the base station shall not configure the function for the UE.","For exact coordination and intercommunication, a wireless system's base station must know UE capabilities. Base station asks about UE capability; UE responds. Knowing UE's capabilities helps the base station schedule it effectively. UE provides a feature or function, thus the base station configures it."
127,"The physical downlink control channel (PDCCH) in NR carries Downlink Control Information (DCI). In this post we will understand how PDCCH operates by describing its physical layer structure, and the carried information.  PDCCH channel is  referred to as the heart of NR air interface.",The NR PDCCH carries DCI (DCI). This post describes PDCCH's physical layer structure and information carried. PDCCH is NR's air interface heart.
128,"Each 5G NR cell corresponds to a Physical Cell ID (PCI) and it is used to distinguish cells on the radio side. The PCI planning for 5G NR is very much similar to PCI planning for LTE and scrambling code planning for 3G UMTS. Bad or wrong planning can affect the synchronization procedure , demodulation, and handover signalling and degrade the network performs. PCI Planning should be simpler for NR compare to LTE because there are double as many PCIs available for allocation.","Radio-side Physical Cell ID (PCI) differentiates 5G NR cells. PCI planning for 5G NR is similar to LTE and UMTS. Bad planning affects network synchronization, demodulation, and handover. The double number of NR PCIs should make planning easier than LTE."
129,"3GPP New Radio (NR) will be primary 5G standard moving forward. Cellular networks are no longer fixed to provide commercial  services only, these are also being used to emergency service, natural disasters, public safety and military communications. As it was with LTE, despite being designed for commercial network, it is often utilized for public safety and military communications. It is very likely that soon 5G NR can be used for similar communication service. NR technology must ensure to be secure and available when and where it is needed. Unfortunately, like any wireless technology, disruption through deliberate radio frequency (RF) interference, or jamming, is possible. The objectives of this article are to outline the physical (PHY) layer vulnerabilities of 5G NR.","3GPP New Radio will power 5G. (NR). Cellular networks now provide emergency, public safety, and military communications. Despite being a commercial network, it's used for public safety and military communications. Similar communications could soon use 5G NR. NR must be prepared. RF jamming is possible with every wireless technology. 5G NR's PHY-layer vulnerabilities are discussed."
130,"5G NR uses several reference signals (RSs) which act as pilots. NR use DM-RS which are separated by physical channel, because 5G NR does not include cell specific reference signals. There is a separate DM-RS for the PDSCH, PUSCH, PDCCH, PUCCH, and PBCH. In addition, there is the Phase-tracking RS (PT-RS) for the PDSCH and PUSCH, Channel state information RS (CSI-RS) for the downlink, and Sounding RS (SRS) for the uplink.","RSs pilot 5G NR. DM-RS replaces cell-specific reference signals in 5G NR. Different DM-RSs exist for PDSCH, PUSCH, PDCCH, PUCCH, and PBCH. CSI-RS for downlink, PT-RS for PDSCH and PUSCH, and SRS for uplink."
131,"From jammer perspective, the best RS to jam would be the one that requires the least amount of energy to jam (i.e. least number of REs per frame), but also be essential to the operation of the link. The DM-RS for the PBCH fits the bill, because it is in the same spot every frame and only requires knowledge of the cell ID and where the PBCH is located, which can easily be known if the jammer is already able to time-synchronize to the frame. The DM-RS for the PBCH occupies one fourth of the REs assigned to the PBCH. It is also possible to jam the DM-RS for the PBCH without needing to synchronize to the cell, by jamming the correct 60 sub-carriers. Phase-tracking RS for the PDSCH are only used when the higher layer parameter Downlink-PTRS-Config is set to ON, and even then the mapping is a function of parameters timeDensity and frequencyDensity. The effectiveness of a downlink PT-RS jamming attack is not clear using the information currently available, because it needs to know how often PT-RS are enabled in practice, and what density the gNB vendors decide to use as a default.","The best RS to jam would need the least energy (i.e. the fewest REs per frame) but be critical to the link's functionality. The PBCH DM-RS fits the definition because it's in the same place every frame and only requires cell ID and PBCH position, which a time-synchronized jammer knows. 25% of PBCH's REs work for DM-RS. PBCH DM-RS can be jammed without cell synchronization by jamming 60 sub-carriers. When Downlink-PTRS-Config is ON, phase-tracking RS for PDSCH are used, and the mapping relies on timeDensity and frequencyDensity. Downlink PT-RS jamming efficacy depends on how often it's used and what density gNB providers employ by default."
132,"5G NR contains PSS and SSS which together are used for frame/slot/symbol timing as well as conveying the Physical Cell ID. There are 1008 unique Physical Cell IDs in 5G NR, the PSS has 3 possible combinations and the SSS has 336 combinations. The PSS is an m-sequence of length 127, mapped to a contiguous set of 127 sub-carriers within the same OFDM symbol. The SSS is also a sequence of length 127, mapped to the same sub-carriers as the PSS but a different OFDM symbol. The SSS uses a Gold sequence, which is formed by combining two m-sequences. Gold sequences within the same set have low cross-correlation, allowing a UE to distinguish between several nearby base stations on the same carrier at low SINR making them resilient to jamming.","5G NR uses PSS and SSS for frame/slot/symbol timing and Physical Cell ID. 5G NR has 1008 Physical Cell IDs, 3 for PSS and 336 for SSS. PSS is a 127-bit m-sequence mapped to 127 OFDM subcarriers. The SSS is similarly a 127-bit sequence, however it uses a different OFDM symbol than the PSS. SSS employs a Gold sequence made from two m-sequences. Low cross-correlation gold sequences allow UEs to distinguish between close base stations on the same carrier at low SINR, making them jamming-resistant."
133,"In 5G NR, PSS and SSS are not always mapped to the downlink resource grid in the same location, it depends on the cell’s sub-carrier spacing, carrier frequency, and the parameter offset-ref-low-scs-ref-PRB. There are three different options for sub-carrier spacing below 6 GHz (15, 30, 60 kHz), and for all three options the PSS and SSS are mapped to the first two slots for carriers below 3 GHz, and the first four slots for those above 3 GHz.","PSS and SSS are not always mapped to the downlink resource grid in 5G NR. It relies on the cell's sub-carrier spacing, carrier frequency, and offset-ref-low-scs-ref-PRB. For sub-carrier spacing below 6 GHz (15, 30, 60 kHz), the PSS and SSS are mapped to the first two slots for carriers below 3 GHz and the first four slots for those above 3 GHz."
134,"A jammer designed to jam the PSS and/or SSS  has to synchronize to the cell in time, and identify the sub-carrier spacing, which might already available from publicly available band plans. This is only a little more complicated than PSS/SSS jamming in LTE. However, for a jammer it may be more effective for an adversary to transmit fake PSS/SSS signals rather than attempt to inject noise on top of the existing PSS/SSS, because it does not have to synchronize to a cell. It also uses less power because the PSS and SSS are designed to be detected at low signal-to-noise ratio (SNR), thus requiring more jammer power to successfully jam the signal.","A PSS or SSS jammer must synchronize to the cell and detect the sub-carrier spacing, which may be accessible from band planning. This is similar to LTE PSS/SSS jamming. For a jammer, it may be more effective to send bogus PSS/SSS signals than to inject noise on top of the current PSS/SSS, because it does not have to synchronize to a cell. PSS and SSS are designed to be detected at low signal-to-noise ratio (SNR), needing higher jammer power."
135,"Although it depends on the Mobile chipset and whether any PSS/SSS blacklisting algorithm exists, it may only be necessary to spoof the PSS. Spoofing the PSS and SSS involves the attacker transmitting several fake signal,asynchronous to the target 5G NR frame(s) i.e., not overlapping in time with the real PSS/SSS and at higher power. PSS/SSS spoofing can cause denial of service (DoS), which would likely occur during initial cell search.","Depending on the Mobile chipset and PSS/SSS blacklisting method, spoofing the PSS may be enough. Spoofing the PSS and SSS includes delivering bogus signals asynchronous to the target 5G NR frame(s) and at higher strength. PSS/SSS spoofing can cause DoS during cell search."
136,"The symbols assigned to the PBCH region are all within two or four slots of each other (depending on whether the carrier is below or above 3 GHz respectively), so a jammer selectively targeting the PBCH will appear to have a very low duty cycle, especially at the higher sub-carrier spacings where the duration of one slot is lower. By jamming the PBCH, UEs will not be able to access critical information they need to connect to a cell, thus preventing new UEs from accessing one or more cells. PBCH jamming can be performed in a time-selective manner if the jammer can synchronize to the target cell. Otherwise, the jammer could simply jam the subcarriers the PBCH is on using 100% duty cycle. This latter approach involves jamming 240 subcarriers, and to provide some perspective, a 20 MHz downlink using 15 kHz subcarrier spacing has 1272 subcarriers. Thus, it would involve jamming 19% of the downlink signal, leading to a jamming gain around 7 dB w.r.t. barrage jamming.","PBCH symbols lie within two or four slots of each other (depending on whether the carrier is below or above 3 GHz), hence a jammer targeting the PBCH will have a low duty cycle, especially at greater sub-carrier spacings when one slot is shorter. By jamming the PBCH, new UEs won't be able to reach one or more cells. PBCH jamming can be time-selective if synchronized to the target cell. The jammer might jam all PBCH subcarriers otherwise. 20-MHz downlink with 15-kHz subcarrier spacing has 1272 subcarriers. 19% of the downlink signal would be blocked, a 7 dB boost over barrage jamming."
137,"Despite the large number of changes in the PHY layer of 5G NR, most of the underlying protocols are very similar to those of LTE e.g. MIB and SIB messages maintain a similar structure and payload to LTE. MIB message contains essential PHY layer configuration necessary by the UE to establish a radio link with a cell, the SIB messages contain detailed information on the configuration of the cell and overall network. The SIB messages provide information such as the idle timer configuration of the network, unique cell identifiers, and the RB mapping of critical control channels. This information is always broadcasted in the clear without any encrypted. Considering these messages occur prior to authentication and are not protected, it is likely that some of these fields could potentially be leveraged for security exploits against the 5G NR. This could be achieved, for example, by spoofing SIB messages or impersonating a base station during the RRC handshake. The 5G NR has very similar RRC and Non-Access Stratum (NAS) protocol architecture as LTE where a number of pre-authentication messages implicitly trusted by both the UE and the base station. By both impersonating a UE or a base station, an adversary can leverage exploits.","Despite 5G NR's PHY layer changes, most underlying protocols are similar to LTE's. MIB and SIB messages' structures and payloads are comparable. SIB messages detail cell and network setup. MIB messages contain PHY layer configuration needed by UE to establish a radio link with a cell. SIB messages include network idle timer, cell IDs, and RB channel mapping. Always unencrypted. Since these messages aren't encrypted before authentication, they could be utilized for 5G NR security threats. SIB spoofing and RRC base station impersonation are examples. UE and base station inherently trust pre-authentication communications in 5G NR's RRC and NAS protocol architectures. Both UE and base station impersonation are possible."
138,"The PDCCH channel is used to send control information to the UEs on a per-slot basis. It is used to schedule downlink transmissions, uplink transmissions, MCS of those transmissions, and HARQ information. The PDCCH can appear on any subcarrier; so the jammer must decode the parameter CORESET freq-domain. The parameter CORESET-time-duration, which can take on values 1, 2, or 3, indicates how many OFDM symbols the PDCCH occupies each slot. The PDCCH always starts in the first symbol of each slot, is QPSK modulated and uses polar coding.","PDCCH sends per-slot control information to UEs. Schedules downlink, uplink, MCS, and HARQ transmissions. PDCCH can exist on any subcarrier; the jammer must decode CORESET freq-domain. The CORESET-time-duration parameter shows how many OFDM symbols the PDCCH occupies each slot. The PDCCH starts at the first symbol of each slot and uses polar coding."
139,"In order to jam all possible locations the PDCCH might reside in, assuming knowledge of CORESET-freq-domain, the jammer would have to jam every sub-carrier, using a duty cycle of either 7%, 14%, or 21% depending on the value of CORESET-time-duration. This type of pulsed jamming attack can also act as a form of automatic gain control jamming.","To jam all feasible PDCCH locations, assuming knowledge of CORESET-freq-domain, the jammer must jam every sub-carrier with a duty cycle of 7%, 14%, or 21%, depending on CORESET-time-duration. This pulsed jamming attack can also be AGC jamming."
140,"The Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) are used to transmit user data from the gNB to the UE and vice versa, and represent the bulk of the frame. While surgically jamming these channels is possible, the adversary might as well jam the entire uplink or downlink signal. Thus, PDSCH and PUSCH jamming are two of the least important threats to consider.","Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) transport user data from gNB to UE and vice versa. The enemy could jam these channels surgically or the entire uplink or downlink signal. Thus, PDSCH and PUSCH jamming are minor dangers."
141,"The  PUCCH is used by UE to send gNB a variety of control information, including HARQ ACKs, SRs, and CSI. There are different PUCCH formats, and there are a variety of parameters provided by the higher layer to inform the UE about which subcarriers and symbols to transmit each PUCCH message. The PUCCH has an option for intra-slot hopping, which acts as a great defense mechanism. The PUCCH is modulated with either BPSK or QPSK and uses either repetition code, or polar code (depending on the number of bits to transmit). The uplink control information can also be carried on the PUSCH, meaning jamming just the PUCCH will not block all uplink control information. All of these factors make the PUCCH an extremely complicated physical channel to jam.","UE uses PUCCH to send gNB HARQ ACKs, SRs, and CSI. Higher-layer parameters tell the UE the subcarriers and symbols to use for each PUCCH transmission. PUCCH's intra-slot hopping is a strong defense. PUCCH uses BPSK or QPSK modulation with repetition or polar code (depending on the number of bits to transmit). Uplink control information is also carried on the PUSCH, therefore jamming it won't block all uplink control information. These qualities make PUCCH difficult to jam physically."
142,"5G NR random access procedure for regular UEs is very similar to that of LTE. When a UE wants to connect to a cell, it first receives the PSS, SSS, and PBCH. After synchronizing to the cell in time and frequency, it transmits a preamble over the Physical Random Access Channel (PRACH), which takes the form of a Zadoff-Chu sequence that embeds a value used to temporarily identify the UE. The gNB broadcasts the candidate locations of the PRACH (in time and frequency) in case a UE wants to connect. The large number of possible locations, and the complexity required to decode the positions in real time, makes the PRACH an unlikely target for a jammer. On the other hand PRACH spoofing, where the UEs flood the PRACH might be feasible, but the 5G NR specifications do not specify the behavior of the gNB when encountering a large number of invalid preambles.","5G NR UE random access is similar to LTE. UEs receive PSS, SSS, and PBCH before connecting to a cell. After synchronizing to the cell in time and frequency, it transmits a preamble over the Physical Random Access Channel (PRACH) that contains a temporary UE identifier. In case a UE wants to connect, the gNB broadcasts PRACH candidate locations (in time and frequency). The PRACH is unlikely to be jammed due to the amount of possible sites and the challenge of decoding them in real time. PRACH spoofing, where UEs flood the PRACH, may be possible, although 5G NR specifications do not specify the gNB's action when encountering several erroneous preambles."
143,"Quality of service (QoS) refer to the measurement of the overall performance of a service experienced by the users of the network. To quantitatively measure the QoS packet loss, bit rate, throughput, transmission delay, availability, jitter, etc.  related aspects of  service are considered. Following figure show the performance of channel Bandwidth (BW) with and without QoS.","Quality of service (QoS) measures network users' overall service performance. Quantifying QoS packet loss, bit rate, throughput, transmission delay, availability, jitter, etc. Figure shows channel BW with and without QoS."
144,"In 5G NR, QoS is enforced at the QoS flow level. Each QoS  flow packets are classified and marked using QoS Flow Identifier (QFI). The 5G QoS flows are mapped in the Access Network to DRBs (Data Radio Bearers) unlike in 4G where mapping is one to one between EPC and Radio Bearers. 5G QoS architecture supports following QoS flow types.","In 5G NR, QoS is at the flow level. Each QoS flow packet has a QoS Flow Identifier (QFI). The 5G QoS flows are mapped in the Access Network to DRBs (Data Radio Bearers), unlike in 4G where EPC and Radio Bearers are mapped one to one. The 5G QoS architecture supports the following QoS flows."
145,"QoS flow is identified by QFI within PDU session. This QFI is carried in an encapsulation header over N3. For each UE, 5GC establishes one or more PDU sessions and 5G-RAN establishes at least one DRB together with PDU session. Additional DRBs are configured for QoS flows of that PDU session consecutively. 5G-RAN maps packets which belong to the different PDU sessions to different DRBs.","PDU session QFI identifies QoS flow. This QFI is encapsulated over N3. 5GC creates one or more PDU sessions for each UE, while 5G-RAN creates at least one DRB. Additional DRBs are specified for QoS PDU flows. 5G-RAN maps PDU packets to DRBs."
146,"The 5G QoS characteristics should be understood as guidelines for setting node specific parameters for each QoS Flow e.g. for 3GPP radio access link layer protocol configurations. Standardized or pre-configured 5G QoS characteristics, are indicated through the 5QI value, and are not signalled on any interface, unless certain 5G QoS characteristics are modified.","5G QoS characteristics are suggestions for configuring node-specific settings for each QoS Flow, such as 3GPP radio access link layer protocol setups. Standardized or pre-configured 5G QoS characteristics are denoted by the 5QI value and are not signaled on any interface unless adjusted."
147,GBR QoS Flows are typically authorized “on demand” which requires dynamic policy and charging control. A GBR QoS Flow uses either the GBR resource type or the Delay-critical GBR resource type. The definition of PDB and PER are different for GBR and Delay-critical GBR resource types and Maximum Data Burst Volume (MDBV) parameter applies only to the Delay-critical GBR resource type. A Non-GBR QoS Flow may be pre-authorized through static policy and charging control. A Non-GBR QoS Flow uses only the Non-GBR resource type.,"GBR QoS Flows are approved ""on demand,"" requiring dynamic policy and billing management. GBR QoS Flow employs GBR or Delay-critical GBR. PDB and PER are defined differently for GBR and Delay-critical GBR resources, while MDBV only applies to the latter. Static policy and charge control can pre-authorize Non-GBR QoS Flow. Non-GBR QoS Flow uses Non-GBR resources."
148,"The QoS parameter ARP contains information about the priority level, the pre-emption capability and the pre-emption vulnerability. The ARP priority level defines the relative importance of a resource request to allows in deciding whether a new QoS Flow may be accepted or needs to be rejected in the case of resource limitations (typically used for admission control of GBR traffic). It may also be used to decide which existing QoS Flow to pre-empt during resource limitations.","ARP includes information on priority level, pre-emption capacity, and pre-emption vulnerability. The ARP priority level determines whether a new QoS Flow can be accepted or rejected due to resource restrictions (typically used for admission control of GBR traffic). It can also pick which QoS Flow to pre-empt amid resource limits."
149,"The  RQA is an optional parameter which indicates that certain traffic (not necessarily all) carried on this QoS Flow is subject to Reflective QoS. Only when the RQA is signalled for a QoS Flow, the RAN/AN enables the transfer of the RQI for AN resource corresponding to this QoS Flow. The RQA may be signalled to NG-RAN via the N2 reference point at UE context establishment in NG-RAN and at QoS Flow establishment or modification.",The RQA parameter specifies that some (but not all) traffic on this QoS Flow is subject to Reflective QoS. RAN/AN only transfers the RQI for a QoS Flow's AN resource when the RQA is signaled. The RQA can be signaled to NG-RAN via the N2 reference point during UE context construction and QoS Flow creation or change.
150,The QoS Parameter Notification control indicates whether notifications are requested from the NG-RAN when the GFBR can no longer (or can again) be guaranteed for a QoS Flow during the lifetime of the QoS Flow. Notification control may be used for a GBR QoS Flow if the application traffic is able to adapt to the change in the QoS (e.g. if the AF is capable to trigger rate adaptation).,The QoS Parameter Notification control determines whether NG-RAN alerts are required when GFBR cannot be ensured for a QoS Flow. GBR QoS Flow can employ notification control if application traffic can respond to QoS changes (e.g. if the AF is capable to trigger rate adaptation).
151,"For GBR QoS Flows only, the additional QoS parameters are Guaranteed Flow Bit Rate (GFBR) and Maximum Flow Bit Rate (MFBR) applicable for Uplink  and Downlink. Bit rates above the GFBR value and up to the MFBR value, may be provided with relative priority determined by the Priority Level of the QoS Flows. GFBR and MFBR are signalled to the (R)AN in the QoS Profile and signalled to the UE as QoS Flow level QoS parameter for each individual QoS Flow.","Guaranteed Flow Bit Rate (GFBR) and Maximum Flow Bit Rate (MFBR) are extra QoS parameters for GBR QoS Flows alone.
Bit rates exceeding GFBR and up to MFBR may be given relative priority based on QoS Flow Priority Level. GFBR and MFBR are signaled to the (R)AN in the QoS Profile and to the UE as QoS Flow level QoS parameters."
152,"For each PDU Session Setup, the SMF retrieves the subscribed default values for the 5QI and the ARP priority level and optionally, the 5QI Priority Level, from the UDM. The subscribed default 5QI value shall be a Non-GBR 5QI from the standardized value range.","For each PDU Session Setup, the SMF receives the subscribed default settings for the 5QI and ARP priority levels from the UDM. The default 5QI must be a non-GBR value from the normal range."
153,"The Maximum Packet Loss Rate (UL, DL) indicates the maximum rate for lost packets of the QoS flow that can be tolerated in the uplink and downlink direction. . This is provided to the QoS flow if it is compliant to the GFBR.","Maximum Packet Loss Rate (UL, DL) shows the maximum rate of lost QoS packets in the uplink and downlink. GFBR-compliant QoS flows receive this."
154,"Two signals transmitted from same antenna port shall experience the same radio channel, where as transmitting it from two different antenna ports shall experience different radio conditions. But there can be some cases where transmitting signals from two different antenna ports experience radio channels having common properties. In such cases the antenna ports said to be Quasi-Colocation (QCL).","Two transmissions from the same antenna port will have the same radio channel, while two from different ports will have distinct radio conditions. Transmitting signals from two distinct antenna ports might share radio channels. Quasi-Colocated antenna ports (QCL)."
155,"3GPP has introduced Quasi- Colocation (QCL) concept to help the UE with channel estimation, frequency offset error estimation and synchronization procedures. For example, if UE knows that the radio channels corresponding to two different antenna ports is QCL in terms of Doppler shift  then UE can determine Doppler shift for one antenna port and then apply the result on both antenna ports for channel estimation. This avoids the UE to calculate doppler for both antenna port separately.","3GPP introduced Quasi- Colocation (QCL) to aid UE channel estimate, frequency offset error estimation, and synchronization. UE can determine Doppler shift for one antenna port and use the result to both antenna ports for channel estimation if two radio channels are QCL in terms of Doppler shift. This eliminates calculating doppler for both antenna ports."
156,"5G NR have support for  multi-antenna transmission, beam-forming, and simultaneous transmission from multiple geographically separates sites (CoMP). In such cases, the channels of different antenna ports relevant for a UE may differ even in terms of radio channel properties and QCL antenna port may be geographically separated.","5G NR supports multi-antenna transmission, beam-forming, and transmission from several sites (CoMP). In such instances, multiple antenna ports relevant to a UE may have different radio channel attributes, and the QCL antenna port may be geographically distant."
157,"QCL can be used to support reception of both PDSCH and PDCCH at UE. In both cases, the gNB can indicate the antenna port used by a specific SS/PBCH block is QCL with the antenna port used by the PDSCH and PDCCH.  Also gNB can indicate that the antenna port used by specific CSI Reference signal is QCL with the antenna port used by PDSCH or PDCCH transmission. gNB use a combination of RRC signalling, MAC CE signalling and PDCCH to indicate UE about which SS/PBCH or CSI RS are QCL with PDSCH and PDCCH.","QCL supports UE's PDSCH and PDCCH reception. In both circumstances, the gNB can signal the SS/PBCH antenna port is QCL with the PDSCH and PDCCH antenna port. gNB can also indicate that a CSI Reference signal's antenna port is QCL with PDSCH or PDCCH transmission.
gNB employ RRC, MAC CE, and PDCCH to tell UE which SS/PBCH or CSI RS are QCL using PDSCH and PDCCH."
158,"A preamble is send by UE to gNB over PRACH channel to obtain the UL synchronization. Similar to LTE, in 5G NR there are 64 preambles defined in each time-frequency PRACH occasion. The preamble consists of two parts cyclic prefix (CP) and Preamble Sequence. In 5G NR, there are 13 types of preamble format supported known as Format 0, Format 1, Format 2,Format 3,Format A1,Format A2,Format A3,Format B1, Format B2, Format B3, Format B4, Format C0, Format C1. These 13 types of preamble format can be grouped into two categories.","UE sends PRACH preamble to gNB to synchronize UL. In 5G NR, each time-frequency PRACH event has 64 preambles, like LTE. CP and Preamble Sequence make up the preamble. 5G NR supports 13 preamble formats: 0, 1, 2, 3, A1, A2, A3, B1, B2, B3, B4, C0, C1. Two categories categorize these 13 preamble formats."
159,"RNTI stands for Radio Network Temporary Identifier. RNTIs are used to differentiate/identify a connected UE in the cell, a specific radio channel, a group of UEs in case of paging, a group of UEs for which power control is issued by the eNB, system information transmitted for all the UEs by 5G gNB. RNTI is an 16-bit identifier and its value depends on type of RNTI. The value is discussed in subsequent section of this post.","Radio Network Temporary Identifier. RNTIs are used to identify a connected UE in the cell, a specific radio channel, a group of UEs in paging, a group of UEs for which the eNB issues power control, and system information transmitted for all UEs by 5G gNB.
RNTI's 16-bit value depends on its kind. Next part discusses value."
160,"5G-NR User plane contains Phy, MAC, RLC, and PDCP same as LTE and has introduced a new layer named as SDAP (Service Data Adaptation Protocol). On another side, the control plane of 5G-NR is identical to LTE, here MME equivalent node named as AMF (Access and Management Mobility Function).","5G-NR User plane has Phy, MAC, RLC, and PDCP like LTE and SDAP (Service Data Adaptation Protocol). 5G-control NR's plane is identical to LTE's MME node, called AMF (Access and Management Mobility Function)."
161,"3GPP has released specification 38.300 V1 this month about NR and NG-RAN Overall Description: Stage 2, This standard comes with the detailed descriptions about 5G NR network and Protocol architecture. In this post, we have come with the detailed information about the User plane and providing information what new we can expect/Enhancements proposed from NR to meet the requirements of eMBB (enhanced Mobile Broadband), Massive IoT (Internet of things) and URLLC (Ultra reliable Low latency communication).","3GPP issued NR/NG-RAN Spec 38.300 V1 this month. Stage 2 describes 5G NR network and protocol architecture. In this post, we discussed the User plane and proposed enhancements from NR to address the needs of eMBB, Massive IoT, and URLLC (Ultra reliable Low latency communication)."
162,"A 5G UE picks a random preamble for RACH procedure to get the uplink synchronisation. The preamble is referenced with an ID know as  RAPID (Random Access Preamble ID). 5G preamble is also use Zadoff-Chu sequence. Each preamble transmission is associated with an RA-RNTI. Random Access RNTI (RA-RNTI) is used during Random Access procedure, the gNB’s MAC generates Random Access Response (RAR) as a response to the Random Access Preamble transmitted by the UE. RAR is transmitted on DL-SCH transport channel which intern is mapped to PDSCH. The gNB scrambles PDCCH’s CRC with RA-RNTI for transmission of PDSCH that carries RAR(s). RA-RNTI can be addressed to multiple UEs, i.e., multiple UEs might decode PDCCH scrambled by the same.","5G UE chooses a random RACH preamble to synchronize the uplink. RAPID identifies the prelude (Random Access Preamble ID). 5G uses Zadoff-Chu preamble. RA-RNTIs accompany each preamble emission. gNB's MAC creates Random Access Response (RAR) in response to the UE's Random Access Preamble. RAR uses DL-SCH, which is mapped to PDSCH. gNB scrambles PDCCH's CRC with RA-RNTI for RAR-carrying PDSCH transmission (s). Multiple UEs can decode PDCCH scrambled by the same RA-RNTI."
163,"The DMRS is specific for specific UE, and used to estimate the radio channel. The system can beamform the DMRS, keep it within a scheduled resource, and transmit it only when necessary in either DL or UL. Additionally, multiple orthogonal DMRSs can be allocated to support MIMO transmission. The network presents users with DMRS information early on for the initial decoding requirement that low-latency applications need, but it only occasionally presents this information for low-speed scenarios in which the channel shows little change.  In high-mobility scenarios to track fast changes in channel , it might increase the rate of transmission  of DMRS signal (called “additional DMRS”).","DMRS estimates the radio channel for a certain UE. The system can beamform DMRS, retain it inside a planned resource, and only broadcast it DL or UL when needed. MIMO transmission can use several orthogonal DMRSs. The network provides DMRS information early for low-latency applications' initial decoding, but only seldom for low-speed scenarios with little channel shift. In high-mobility situations to follow fast channel changes, it may boost DMRS signal transmission rate (""additional DMRS"")."
164,"The phase noise of a transmitter increases as the frequency of operation increases. The PTRS plays a crucial role especially at mmWave frequencies to minimize the effect of the oscillator phase noise on system performance. One of the main problems that phase noise introduces into an OFDM signal appears as a common phase rotation of all the sub-carriers, known as common phase error (CPE).",A transmitter's phase noise grows with frequency. PTRS minimizes oscillator phase noise at mmWave frequency to improve system performance. Common phase error is one of the main problems phase noise causes in OFDM signals (CPE).
165,"As a UL-only signal, the SRS is transmitted by the UE to help the gNB obtain the channel state information (CSI) for each user. Channel State Information describes how the NR signal propagates from the UE to the gNB and represents the combined effect of scattering, fading, and power decay with distance. The system uses the SRS for resource scheduling, link adaptation, Massive MIMO, and beam management.","The UE transmits the UL-only SRS to help the gNB obtain CSI for each user. Channel State Information explains how the NR signal propagates from the UE to the gNB and represents scattering, fading, and power decay. The SRS manages resources, links, Massive MIMO, and beams."
166,"As a DL-only signal, the CSI-RS the UE receives is used to estimate the channel and report channel quality information back to the gNB. During MIMO operations, NR uses different antenna approaches based on the carrier frequency. At lower frequencies, the system uses a modest number of active antennas for MU-MIMO and adds FDD operations. In this case, the UE needs the CSI-RS to calculate the CSI and report it back in the UL direction.","As a DL-only signal, CSI-RS is utilized to evaluate the channel and report channel quality to the gNB. NR uses several antenna methods for MIMO according on carrier frequency. At lower frequencies, MU-MIMO and FDD use a small number of active antennas. UE needs the CSI-RS to calculate CSI and report it to UL."
167,"To transmit and recieved data in downlink and uplink UEs need bandwidth resource allocated and this allocation provided by gNB. In 5G NR, similar to 4G the resource allocation is done in Time domain and frequency domain. Time domain resource allocation defines which symbols are allocated to UE and frequency domain allocation defines which RBs are allocated to the UE.","UEs need gNB's bandwidth allocation to transmit and receive downlink and uplink data. 5G NR allocates resources in time and frequency domains, like 4G. Time domain resource allocation determines which UE symbols and RBs are allocated."
168,"While allocating the resource blocks (RBs) within different RBG, it is not neccessarly tha all the RBGs will have equal no. of RBs, the First and the Last RBGs in can have less number of RBs than specified for that particulator BWP. The bitmap is of size NRBG and varies depending upon the size of the bandwidth part and the position of the bandwidth part within the Common Resource Block (CRB) grid, and RBG size (P).","When assigning resource blocks (RBs) within distinct RBGs, the First and Last RBGs can have fewer RBs than requested for that particulator BWP. The bitmap's NRBG size depends on the bandwidth's position in the CRB grid and RBG size (P)."
169,"The number of RLC PDU(s) are transmitted according to the MAC TB size. If the MAC TB size is not sufficient enough to transmit the Complete RLC PDU, then the RLC PDU is segmented. MAC TB size depends upon the scheduled bytes – which is based on the radio condition.","RLC PDUs are sent based on MAC TB size. If the MAC TB size isn't adequate to send the complete RLC PDU, it's fragmented. MAC TB size is determined on scheduled bytes and radio status."
170,"In AM mode, every RLC PDU is sent with sequence number in ascending order and stored in Re-transmission buffer. As RLC AM supports ARQ to ensure reliable delivery, therefore RLC STATUS PDU message is sent by UE to indicate the current status of RLC PDUs received at UE.","In AM mode, RLC PDUs are delivered with ascending sequence numbers and stored in Re-transmission buffer. As RLC AM supports ARQ to enable reliable delivery, UE sends RLC STATUS PDU to indicate RLC PDU status."
171,"If STATUS PDU is dropped, then post expiry of Poll Retransmission timer, a RLC PDU with SN=2 is retransmitted – which is latest RLC PDU that is transmitted from DU. If the Poll Retransmit timer expiry count exceed the maxRetxThreshhold value then RLF (Radio Link Failure) is triggered and the UE is released.","If STATUS PDU is dropped, an RLC PDU with SN=2 is retransmitted after the Poll Retransmission timer expires. UE is released if the Poll Retransmit timer expiry count exceeds maxRetxThreshhold."
172,"Status Report is sent periodically to share the reception status of UL packets to the UE. Next two figure below  depicts the updation of RLC UL State Variable according to the processing done for the RLC packets in t-reassembly (t1,t2,t3) timer. It is assumed that in each t-reassembly, 50 RLC PDUs are received and in each t-reassembly timer duration STATUS PDU is sent. RLC SN Reception missed as TB (MAC Transport Block) not received from UE.","Periodically, UE receives a Status Report on UL packet reception. Next two figures illustrate the update of RLC UL State Variable in t-reassembly (t1,t2,t3) timing. Each t-reassembly assumes 50 RLC PDUs and a timed duration STATUS PDU. UE's MAC Transport Block (TB) prevented RLC SN reception."
173,"The Radio Resource Control (RRC) protocol is used in on the Air Interface. The major functions of the RRC protocol include connection establishment and release functions, broadcast of system information, radio bearer establishment, reconfiguration and release, RRC connection mobility procedures, paging notification and release and outer loop power control.By means of the signaling functions, the RRC configures the user and control planes according to the network status and allows for Radio Resource Management strategies to be implemented.","Air Interface uses RRC protocol. RRC protocol functions include connection setup and release, system information broadcast, radio bearer establishment, reconfiguration, and release, connection mobility, paging notification and release, and outer loop power control. The RRC configures the user and control planes based on network state and implements Radio Resource Management techniques using signaling functions."
174,The operation of the RRC is guided by a state machine which defines certain specific states that a UE may be present in. The different RRC states in this state machine have different amounts of radio resources associated with them and these are the resources that the UE may use when it is present in a given specific state.,The RRC is led by a state machine that defines UE states. The different RRC states in this state machine have varied quantities of radio resources that the UE can consume in that state.
175,"Appart form RRC connected and RRC IDLE state, 5G NR has introduced a new RRC state names as RRC Inactive state. When UE is power up it is in Disconnected mode/Idle mode, It can move  RRC connected with initial attach or with connection establishment. If there is no activity from UE for a short time, It can suspend its session by moving to RRC Inactive and can resume its session moving to RRC connected mode. A UE can move to RRC Idle mode from RRC connected or RRC Inactive state.","5G NR introduces a new RRC status called RRC Inactive. When UE is powered on, it is in disconnected/idle mode. RRC can be linked during first attach or connection formation. If UE is inactive for a brief time, it can suspend its session by switching to RRC Inactive and resuming in RRC Connected. A UE can go from RRC Connected to RRC Idle."
176,"The RRC States is a solution to the system access, power saving, and mobility optimization. 5G has to support eMBB, URLLC, and Massive IoT services at same cost and energy dissipation per day per area. 5G system access and requested services have different characteristics => Control of connectivity for future services need to flexible and programmable. To meet these different services characteristics it requires new RRC state model.","RRC States optimizes system access, power consumption, and mobility. 5G must offer eMBB, URLLC, and Massive IoT with same cost and energy dissipation per day per region.
5G system access and required services varies, therefore future connectivity control must be flexible and customizable. New RRC state model needed to match service characteristics."
177,"5G NR radio resource control (RRC) has introduced following listed timers, counters and constant for reliable functioning of procedures like RRCsetuprequest, RRCreestablishment, RRCresume, RRCsuspend etc. RRC timer indicates the timer duration and event when to start, event when to stop and actions to be taken if the timer is expired. These timers are denoted by  letter “T” followed by 3 digit number e.g. T300. Each timer start we zero value and  when the UE applies zero value for a timer, the timer shall be started and immediately expire unless explicitly stated otherwise. RRC constant and counter defines the count or no. of attempts for particular event. Counter are denoted by letter “N” and followed by 3 digit number e.g. N310.","5G NR radio resource control (RRC) has incorporated timers, counters, and constants for processes like RRCsetuprequest, RRCreestablishment, RRCresume, RRCsuspend, etc. RRC timer indicates duration, when to start, when to stop, and what to do if timer expires. ""T"" followed by 3 digits denotes these times, e.g. T300. When the UE sets a timer to 0, it will start and expire instantly unless otherwise stated. RRC constant and counter define event attempts. Counters are designated by ""N"" followed by 3 digits, e.g. N310."
178,"In 5G NR, the Sync Signal/PBCH block (SSB) burst is consists of multiple SSBs. These multiple SSBs are associated with the different SSB indexes and with the different transmission beams other than CSI-RS signals can also be configured for beam management and measurement. The measurement procedure is a UE power consuming procedure and to reduce UE power consumption, 5G NR has introduced SSB based measurement timing configuration also known as SMTC. The SMTC defines a duration and periodicity that can be used to restrict the UE measurement on the certain resources. Within SMTC period and on the configured SSB and/or CSI-RS, UE will conduct the Radio Link Monitoring /Radio Resource Management measurement.",5G NR uses multiple Sync Signal/PBCH block (SSB) bursts. Multiple SSBs can be established for beam management and measurement with different SSB indexes and transmission beams other than CSI-RS signals. 5G NR has incorporated SSB-based measurement timing configuration (SMTC) to minimize UE power consumption. SMTC defines a duration and periodicity to limit UE measurement on particular resources. UE will measure RLM/RRM during SMTC on the configured SSB and/or CSI-RS.
179,"For LTE-NR Dual Connectivity (EN-DC) the initial access and mobility are done on LTE Primary Cell (PCell) and NR Carrier Component (NR CC) will be added or released as Secondary Cell (SCell) as part of Non Standalone (NSA) operation, while in Stand Alone (SA) mode all the operations will be done directly on NR Primary Cell. Considering this, RRM requirements for LTE-NR DC (NSA) and SA are partially different. Below tables summarizes the RRM requirements. These requirements guarantee the initial access and mobility performance for the LTE-NR DC, Supplemental Uplink (SUP), and NR-NR Carrier Aggregation (CA). These measurement can be divided into three category based on applicability i.e. Measurements Specific to NSA Mode only, Measurement Specific to SA mode Only and Measurement Common to both (NSA and SA).","For LTE-NR Dual Connectivity (EN-DC), initial access and mobility are done on LTE Primary Cell (PCell) and NR Carrier Component (NR CC) is added or released as Secondary Cell (SCell) as part of Non Standalone (NSA) operation. In Stand Alone (SA) mode, all operations are done directly on NR Primary Cell. LTE-NR DC (NSA) and SA have distinct RRM needs. RRM requirements are summarized here. These standards guarantee LTE-NR DC, SUP, and NR-NR Carrier Aggregation access and mobility (CA). These measurements can be separated into three categories, NSA-only, SA-only, and common (NSA and SA)."
180,"The RSRQ (Referece Signal RecivedQuality) is a measurement performed by the UE to know the Quality of recieved Reference Signals. In 5G NR, RSRQ can be measurement for SS-Reference Siganls and CSI-Reference Signals. The SS-RSRQ measurements can be used for cell selection, cell reselection and mobility procedures where as CSI-RSRQ measurements can be used for mobility procedures only.","RSRQ (Reference Signal RecivedQuality) measures the quality of received Reference Signals. 5G NR measures RSRQ for SS-Reference and CSI-Reference signals. SS-RSRQ can be used for cell selection, reselection, and mobility, while CSI-RSRQ can only be used for mobility."
181,"A 5G Stand Alone also know as Option 2, architecture includes 5G UE, gNB and 5G Core Network. In this post we will discuss about 5G SA Registration Call Flow for OTA messages (b/w UE and gNB) and NGAP messages (b/w gNB and 5GC AMF ). In 5G SA mode term Registration is equal to Attach in 4G LTE.","Option 2 comprises 5G UE, gNB, and 5G Core Network. This post discusses 5G SA Registration Call Flow for OTA (UE-gNB) and NGAP (gNB-5GC AMF) communications. 5G SA Registration equals 4G LTE Attach."
182,"For the purpose of Radio Link Failure (RLF), the UE physical layer monitors the downlink radio link quality of the primary cell for indicating out-of-sync / in-sync status indications to the higher layers. In 5G NSA EN-DC mode, RLF is declared separately for the MCG (E-UTRA LTE Cell) and for the SCG cells (NR). If radio link failure is detected for MCG (LTE eNB), the UE initiates the RRC connection re-establishment procedure, but when RLF is detected for SCG (NR cell) failure, the UE suspends SCG transmissions for all radio bearers and reports the SCG Failure Information to the eNB, instead of triggering re-establishment.","The UE physical layer monitors the downlink radio connection quality of the primary cell for Radio Link Failure (RLF) to indicate out-of-sync/in-sync status to upper layers. In 5G NSA EN-DC mode, MCG and SCG RLF are announced individually (NR). If radio link failure is detected for MCG (LTE eNB), the UE commences the RRC connection re-establishment procedure. When RLF is detected for SCG (NR cell), the UE suspends SCG transmissions for all radio bearers and reports SCG Failure Information to the eNB."
183,"The User Equipment is configured with various parameters related to RLF on the SCG SpCell (Special Cell). Following figure shows the key RLF configuration parameters, which includes the timers and counters. The Radio Link Monitor configuration indicates whether the UE should be monitoring based on the SSB-RS or CSI-RS. In addition, the failureDedectionResources parameter also includes a “purpose” parameter, which can indicate: RLF, Beam Failure or both. There can be multiple instances of the failureDedectionResources parameter.","User Equipment RLF parameters on SCG SpCell are configured (Special Cell). Figure depicts RLF timers and counters configuration options. Radio Link Monitor setting indicates whether UE should monitor SSB-RS or CSI-RS. The failureDedectionResources parameter has a ""purpose"" parameter that can indicate RLF, Beam Failure, or both. failureDedectionResources can be repeated."
184,"The measurements of the RS (Reference Signal) BLER can be configured for the SSB-RS or CSI-RS. The measurement evaluation time will also vary depending on whether DRX is configured or not, as well as the Frequency Range (FR1 or FR2). Upon receiving n310 consecutive “out-of-sync” indications for the PSCell (NR cell) from lower layers the UE starts timer t310. Assuming the UE receives n311 In-Sync indication prior to the timer expiring, the t310 timer will stop. If not, the timer expires and the UE triggers a RLF.","The RS BLER can measure SSB-RS or CSI-RS. Whether DRX is configured and the frequency range affect the measurement assessment time (FR1 or FR2). UE starts timer t310 after n310 successive ""out-of-sync"" PSCell (NR cell) indications from lower layers. UE receives n311 In-Sync before timer expires, t310 timer stops. UE triggers an RLF if the timer expires."
185,The 5G NR has introduce new mechanism to manage the Quality of Service via QoS flow and to handle QoS flow specifications has introduced a new Sublayer SDAP in air-interface procotols stack both at UE and gNB side.  The SDAP (Service Data Adaption Protocol) layer is the topmost L2 sublayer at 5G NR protocol stack Standalone Architecture (SA) where gNB connects to 5G Core network. It interfaces to 5GC UPF using NG-U interface via QoS flows and to the PDCP lower layer via Data Radio Bearers (DRBs). SDAP’s essential role is to map traffic from QoS flows to suitable DRBs. SDAP layer doesn’t exist in 4G/LTE since QoS flows were introduced only in 5G.,"5G NR introduces a new way to control QoS via QoS flow and a new Sublayer SDAP in air-interface protocols stack at both UE and gNB. SDAP (Service Data Adaptation Protocol) is the top L2 sublayer of 5G NR's Standalone Architecture (SA), where gNB interfaces to 5G Core. It interfaces with 5GC UPF via NG-U and PDCP via Data Radio Bearers (DRBs). SDAP maps QoS traffic to DRBs. 5G added QoS flows, hence 4G/LTE lacks SDAP."
186,"The SDAP sublayer can have multiple SDAP entities, one for each PDU session on the gNB–UE Uu interface. An SDAP entity establishment or release are initiated by RRC. The SDAP layer receives downlink data from the User Plane Function over NG-U interface. On NG-U interface DL user plane data is linked to a specific QoS Flow belonging to a specific PDU Session. This QoS Flow is identified using an identity within the ‘PDU Session Container’ which is included within the GTP-U header. The PDU Session is identified using the GTP-U Tunnel Endpoint Identifier (TEID). The SDAP layer maps each QoS Flow onto a specific Data Radio Bearer (DRB) as shown in below figure. In this illustration, we can see that multiple QoS Flows can be mapped onto a single DRB:, or a single QoS Flow can be mapped onto a single DRB. QoS Flows belonging to different PDU Sessions arc mapped onto different DRB.","Each PDU session on the gNB–UE Uu interface has its own SDAP entity. RRC creates or releases SDAP entities. SDAP gets downlink data from UPF over NG-U interface. On the NG-U interface, DL user plane data is tied to a PDU Session's QoS Flow. This QoS Flow is identified in the GTP-U header's 'PDU Session Container' GTP-U Tunnel Endpoint Identifier identifies PDU Session (TEID). The SDAP layer maps each QoS Flow to a Data Radio Bearer (DRB). In this instance, numerous QoS Flows can be mapped onto a single DRB. Various PDU Sessions' QoS Flows map to different DRB."
187,"With Reflective QoS, the uplink DRB mapping is omitted, UE monitors the equivalent downlink mapping and applies the same to the uplink. When reflective QoS is enabled, SDAP layer adds header information to the downlink data packets at either the Access Stratum or Non-Access Stratum layers. Reflective QoS allows the UE to deduce the uplink mapping rules from the downlink mappings, i.e. the uplink rules are copied from the downlink. Downlink data packets can be sent without a header when reflective QoS is not used.","Reflective QoS omits the uplink DRB mapping and monitors the comparable downlink mapping. SDAP layer adds header information to downlink data packets when reflective QoS is enabled at the Access Stratum or Non-Access Stratum layers. Reflective QoS allows the UE to copy the downlink uplink mapping rules. Without reflective QoS, downlink packets can be delivered without a header."
188,The DRB is linked to a specific PDU Session and the UE is informed whether or not SDAP headers are to be included in the uplink and downlink directions. There is also a flag to indicate whether or not the DRB is to be used as a ‘Default DRB’ for the PDU Session. Only a single DRB can be configured as the ‘Default DRB’ for each PDU Session. A PDU is mapped onto the ‘Default DRB’ ifthere is no rule to map the packet onto a specific DRB. An uplink SDAP header is always included when mapping a PDU onto the ‘Default DRB’.,"The DRB is tied to a specific PDU Session, and the UE is told whether to include SDAP headers in the uplink and downlink directions. A flag indicates whether the DRB will be utilized as the PDU Session's 'Default DRB.' Each PDU Session can only have one 'Default DRB.' If there's no rule to map a PDU to a specified DRB, it's mapped to the 'Default DRB.' A PDU's 'Default DRB' mapping includes an uplink SDAP header."
189,"SINR is Singal to Interference Noise Ratio is a measure of signal quality. It can be defined as the ratio of  wanted signal strength and the unwanted interference plus noise.  Good SINR can help to achieve higher spectral efficiency as it enable to decode higher Modulation Conding Scheme (MCS). The network operator always seeks to maximize SINR at all sites to deliver the best possible User Experience, either by transmitting at a higher power, or by minimizing the interference and noise. As per the Shannon’s Channels Capacity (C), the theoretical Channel Capcity is a function of  bandwidth (B) and is a function of the SINR.  Thus, optimizing SINR can  helps to achieve high Cell Capacity, allows higher order QAM modulation, resulting in higher peak data rates, fewer dropped calls, and ultimately improved User Experience.","SINR sings interference Noise Signal ratio measures quality. It's the ratio of signal strength to interference and noise. Good SINR allows decoding of higher Modulation Conding Schemes, which boosts spectral efficiency (MCS). The network operator maximizes SINR at all sites to give the optimum User Experience, either by broadcasting at higher power or by avoiding interference and noise. Shannon's Channel Capacity (C) is a function of bandwidth (B) and SINR. Optimizing SINR helps achieve high Cell Capacity, enabling higher order QAM modulation, resulting in greater peak data rates, fewer missed calls, and improved User Experience."
190,"UE does measurement of SS-RSRP and use it for cell selection, cell reselection, power control, mobility procedures and beam management procedures. RSRP measurement generated and reported at both Layer 1 (Phy) and Layer 3 (RRC). For example, a UE can measure SS-RSRP at Layer 1 when sending CSI to the gNB and provides results at Layer 3 when sending Measurement Reports. UE is allowed to use measurements from the PBCH-DMRS when generating SS-RSRP results. The DMRS and SS-Signal are transmitted with equal power so results can be averaged directly. When UE is measuring SS-RSRP for Layer 1 reporting, then a UE can be configured to use CSI-RS measurements as an additional input. CSI-RS may have a different transmit power compared to the SS-Signals and PBCH DMRS. The gNB provides offset information to the UE so it can be taken into account during the measurement procedure.","UE measures SS-RSRP for cell selection, reselection, power control, mobility, and beam management. Both Layer 1 (Phy) and Layer 3 report RSRP measurements (RRC). UEs can test SS-RSRP at Layer 1 when sending CSI to the gNB and report results at Layer 3. UE can use PBCH-DMRS measurements for SS-RSRP. DMRS and SS-Signal have similar power, hence results can be averaged directly. UEs can employ CSI-RS measurements when measuring SS-RSRP for Layer 1 reporting. CSI-RS transmit power may differ between SS-Signals and PBCH DMRS. The gNB gives the UE offset information for measurement."
191,Standardized 5G QoS Identifier (5QI) values are specified for services that are assumed to be frequently used in 5G networks and thus benefit from optimized signalling by using standardized QoS characteristics. Dynamically assigned 5QI values which require a signalling of QoS characteristics as part of the QoS profile can be used for services for which standardized 5QI values are not defined.,"5G QoS Identifier (5QI) values are given for regularly utilized services that benefit from efficient signalling utilizing standardized QoS characteristics. For services without conventional 5QI values, dynamically assigned values that require QoS signaling can be employed."
192,"System information is downlink broadcast information transmitted periodically by base station. it is very critical information for a mobile (UE) to connection the Base station (gNB in 5G) in any technology. In 5G, UE reads system information for cell camping when it is powered on, for cell selection and re-selection when it is in RRC IDLE mode. System information basically provides all necessary details like System frame number, System bandwidth, PLMN, cell selection and re-selection thresholds etc. to access network.","Base station regularly sends downlink system information. It's crucial information for a mobile (UE) to connect to a base station (gNB in 5G). 5G UE reads system information for cell camping while switched on and for cell selection and reselection in RRC IDLE mode. System information includes System frame number, System bandwidth, PLMN, cell selection and re-selection thresholds, etc."
193,"At high level in 5G New Radio, this system information can be divided into three categories. These categories include Master Information Block (MIB) and 9 System Information Blocks (SIBs). The MIB information is transmitted via BCH and PBCH channels while SIBs are transmitted via DL-SCH and PDSCH channels.",5G New Radio system data is divided into three areas. These categories contain MIB and 9 SIBs (SIBs). MIBs are sent over BCH and PBCH while SIBs use DL-SCH and PDSCH.
194,"The Minimum Information block includes of MIB and Remaining System information. RMSI includes SIB1 and Other System Information (OSI) includes SIB2 to SIB9. MIB and SIB1 has is own RRC Message “MasterInformationBlock” and “SystemInformationBlock1” respectively where as SIB2 to SIB9 are wrapped within a generic RRC message known as “SystemInformation”. Minimum system information is broadcast periodically, while other system information may either be broadcast, or provisioned in a dedicated manner, either triggered by the network or upon request from the UE.","The Minimum Information block provides MIB and RS information. Other System Information (OSI) contains SIB2 through SIB9. MIB and SIB1 have their own RRC messages, ""MasterInformationBlock"" and ""SystemInformationBlock1,"" while SIB2 to SIB9 use ""SystemInformation."" Minimum system information is periodically broadcast, while other system information may be broadcast or provided in a dedicated manner, prompted by the network or upon UE request."
195,"When other System Information is required by the UE, before the UE sends the OSI request, UE needs to know whether it is available in the cell and whether it is broadcast or not. The UE in RRC_IDLE or RRC_INACTIVE should be able to request the OSI without requiring a state transition. For the UE in RRC_CONNECTED, dedicated RRC signaling can be used for the request and delivery of the OSI. The other SI may be broadcast at configurable periodicity and for certain duration. It is network decision whether the OSI is broadcast or delivered through dedicated UE specific RRC signaling.","Before sending an OSI request, the UE must know if Other System Information is available in the cell and broadcast. UE in RRC IDLE or RRC INACTIVE should request OSI without state transition. UEs under RRC CONNECTED can employ RRC signaling for OSI request and delivery. Other SI can be broadcast with variable frequency and duration. The network decides whether to broadcast OSI or use UE-specific RRC signaling."
196,"When a UE is powered on, it performs a cell search procedure and decode the PSS and SSS information to get the Physical cell ID. Then UE scan for the MIB at set GSCN and acquires a suitable SS/PBCH block. MIB information is directly available on PBCH channel. After successful MIB decode UE get the information regarding Control Resource Set (CORSET) and PDCCH Search space required for SIB1 decoding. SIB1 provide network access parameters along with scheduling information about all other system information. The system information is scrambled with SI-RNTI and DCI format 1_0 is used during allocated PDSCH resources for transmission at gNB.","A UE does a cell search and decodes PSS and SSS to retrieve the Physical cell ID when powered on. UE scans for MIB at set GSCN and acquires an SS/PBCH block. PBCH channel provides MIB information. After successful MIB decoding, UE gets CORSET and PDCCH Search space information for SIB1 decoding. SIB1 provides network access settings and system scheduling. SI-RNTI and DCI format 1_0 scrambling system information for gNB PDSCH transmission."
197,"System Information is downlink broadcast information transmitted periodically by base station. SIB#8 is used to provide a Commercial Mobile Alert Service (CMAS) notification. CMAS is used as Public Warning System (PWS) to deliver multiple, concurrent warning text messages. The FCC established CMAS to allow operators to send emergency alerts as text messages to their users. This emergency alerts broadcast can be either within the whole network or within certain geographical areas, down to the size of a single cell. The Emergency alret messages are basicaly generated by an entity named as Cell Broadcast Entity (CBE) managed by national authorities, dealing with public safety or crime prevention or both in that country where network is deployed. ","Downlink System Information is periodically broadcast by the base station. SIB#8 is used to notify CMAS. CMAS is used as a PWS to send several, concurrent warning texts. FCC created CMAS to allow operators to SMS emergency alerts to users. This emergency warnings broadcast might be network-wide or to a single cell. Cell Broadcast Entity (CBE), governed by national authorities dealing with public safety or crime prevention in the country where the network is implemented, generates emergency alret messages."
198,"In 5G NR, System Information Block Type 2 or SIB2  provides information which is common to intra frequency,  inter frequency and inter-system cell (NR – LTE) reselection. It also provides information which is specific to intra-frequency cell reselection. In 5G, Cell reselection can be based upon a cell level and beam level measurements. When the gNB transmits multiple beams, a UE is required to generate a cell level measurement from one or more beam level measurements.","SIB2 provides common information for intra-frequency, inter-frequency, and inter-system cell reselection in 5G NR. It also gives intra-frequency cell reselection-specific information. 5G cell reselection uses cell and beam level data. UEs must create a cell level measurement from one or more beam level measurements when the gNB transmits multiple beams."
199,"Timing Advance (TA) is a command sent by Base Station (BS) to UE to adjust its uplink transmission means that the UE sends UL symbols in advance according to command for i.e. PUSCH, PUCCH and SRS transmission. Timing Advance Command (TAC) informs the UE  the amount of time that it needs to advance the UL transmissions.","Timing Advance (TA) is a Base Station (BS) signal to UE to adjust its uplink transmission, which means the UE sends UL symbols in advance for PUSCH, PUCCH, and SRS transmission. TAC tells the UE how long to forward UL transmissions."
200,"In wireless system, it is required to adjust the timing of the uplink frame in order to have alignment with the downlink frame in time domain. Uplink frame is transmitted by UE towards gNB whereas the downlink frame is transmitted by gNB towards UE. The timing control procedure is initiated by the MAC layer and conveyed to the PHY layer for time adjustment. See the figure below for the uplink and downlink transmission time relationship.","In wireless systems, the uplink frame must be time-aligned with the downlink frame. UE sends uplink frames to gNB, while gNB sends downlink frames to UE. MAC initiates the timing control mechanism and sends it to PHY for correction. Uplink and downlink transmission times are shown below."
201,"Transmitted signal quality specify how much the transmitted signal deviated from an ideal signal  in terms of frequency domain, timer domain or modulation property. The impairments on the transmitted signal are introduced by the transmitter radio parts having nonlinear properties e.g power amplifier, Digital Front End (DFE) and Analog Front End (AFE) etc.","Transmitted signal quality describes how far the signal strayed from an ideal signal in frequency, timing, or modulation. Nonlinear transmitter radio parts, such as power amplifiers, DFE, and AFE, degrade the broadcast signal."
202,"Frequency error is the measure of the difference between the actual BS transmit frequency and the assigned frequency.  The same source shall be used for RF frequency and data clock generation. 3GPP specification has set the minimum requirement for frequency error for different classes of Base stations considering Macro, Micro and Pico cell deployments. The requirement is applied at the reference points defined for difference BS types e.g. for Type 1-C Base station requirement shall be applied at the antenna connector supporting transmission in the operating band and for Type 1-H this requirement shall be applied at each TAB connector supporting.","Difference between actual BS transmit frequency and designated frequency called frequency error. The same source must generate RF and data clocks. 3GPP specifies minimal frequency error for Macro, Micro, and Pico base stations. The requirement is applied at the reference locations provided for different BS types, such as Type 1-C Base station antenna connector supporting transmission in the operating band and Type 1-H TAB connection supporting. 3GPP TS 38.104 specifies ppm frequency error requirements (parts per million)."
203,"NR Base station transmits signal from two or more antennas e.g. transmitter diversity and MIMO. For carrier aggregation, the carriers may also be transmitted from different antennas. For mobile device to properly receive and decode the signals from multiple antennas, it is required the signal frames must aligned in time with the defined range.×Drag and DropThe image will be downloaded",NR Base stations use many antennas for transmitter diversity and MIMO. Carrier aggregation uses many antennas. Signal frames must be aligned with the stated range for mobile devices to receive and decode signals from multiple antennas.
204,"Frame Timing relation between any two transmitter branches is specified in terms of a maximum time alignment error between transmitter branches. The maximum allowed error depends on the feature or combination of features in the transmitter branches e.g. Transmit Diveristy, MIMO, Carrier Aggression etc. The purpose is to measure this error to find the delay between signal from two transmit Antennas. Frames of the NR signals present at the BS transmitter antenna connectors or TAB connectors are not perfectly aligned in time. The RF signals present at the BS transmitter antenna connectors or transceiver array boundary may experience certain timing differences in relation to each other.","Frame Timing relation between two transmitter branches is specified by maximum time alignment error. Maximum error relies on transmitter properties, such as Transmit Diversity, MIMO, Carrier Aggression, etc. It's used to measure the latency between two transmit antennas. NR frames at BS transmitter antenna connectors or TAB connectors aren't exactly timed. RF signals at BS transmitter antenna connections or transceiver array boundaries may have different timing."
205,"As telecom is evolving to next generations and new use cases, 3GPP has added new Power Class Categories. As per the definition, UE Power Class can be defines as the maximum transmit power over NR channel bandwidth. The link budget is always uplink limited due to low tx power from UE and defines the cell range.  When UE power is high it can make call from longer distance. 5G NR works within FR1 and FR2 frequencies ranges and 3GPP has defined UE power classes for both.","3GPP has incorporated additional Power Class Categories as the telecom industry evolves. UE Power Class is the maximum transmit power over NR channel bandwidth. Due to low UE tx power, the uplink link budget limits cell range. High UE power allows longer calls. 3GPP has defined UE power classes for both FR1 and FR2 frequency ranges."
206,"Open RAN network architecture is needed to address the specific needs of different mobile operators around the world and it is expected that vendors will interoperate to create customized Open RAN solutions to meet these requirements. The 5G NR with respect to 3GPP Release 15 and later, the specifications require the RAN to become disaggregated  grouping of functional elements.","Open RAN network architecture is needed to suit the needs of mobile operators around the world, and suppliers will interoperate to provide customized solutions. 5G NR 3GPP Release 15 and later specifications demand a disaggregated RAN."
207,"In 5G System, the one of the key task for the networ is to provide the connectivity to UE towards  a Data Network (DN) know as 5G DNN which is similar to 4G APN. The Data Network (DNN) can be Internet,  or an IMS or any other DNN dedicated to a Industry or Factory. 5G NAS-SM (Session Management) is responsible for setting up and managing the PDU session for user-plane connectivity between UE and Data Networks. The 3GPP specifications kept Session Management design flexible to support diverse 5G use cases e.g. Session Management supports different PDU Session protocol types, different options for how to handle session and service continuity, as well as a flexible User Plane architecture.","In 5G, the network must link UE to a Data Network (DN) called 5G DNN, similar to 4G APN. The Data Network (DNN) can be the Internet, IMS, or a factory-specific DNN. 5G NAS-SM (Session Management) sets up and manages PDU sessions for UE-to-Data Network communication. 3GPP kept Session Management flexible to suit varied 5G use cases. Session Management supports various PDU Session protocol types, session and service continuity options, and a customizable User Plane architecture."
208,"While comparing with 4G EPS, we had IP based PDU Session types, indeed have similar properties also in 5GS, with some additional features for IPv6  in 5GS. Unstructured PDU Session type in 5GS is similar to non-IP PDN type in 4G EPS while Ethernet PDU Session type did not have any counterpart in 4G EPS initially but has later been added. As 5G Core can not interpret the PDUs carried over Unstructured PDU Session, it also does not allocate any protocol addresses or other protocol parameters to the UE. Additionally, UE traffic can carried with single QoS flow  as there is no mechanism to differentiate traffic within the PDU Session based on packet filters. This QoS flow shall be the default QoS class. The SSC mode 1 and SSC mode 2 is supported for PDU Sessions with PDU Session type Unstructured and SSC mode 3 is not supported.","Comparing to 4G EPS, 5GS IP-based PDU Session kinds have similar properties, with certain IPv6 additions. Unstructured PDU Session in 5GS is identical to non-IP PDN in 4G EPS, whereas Ethernet PDU Session was added to 4G EPS later. As 5G Core can't comprehend Unstructured PDU Session PDUs, it doesn't allocate UE protocol addresses or other protocol parameters. UE traffic can be transmitted with a single QoS flow because packet filters cannot differentiate across PDU Sessions. This QoS class is default. Unstructured PDU Sessions support SSC modes 1 and 2, but not 3."
209,Network Slicing is considered as one of the key feature by 3GPP in 5G.  A network slice can be looked as a logical end-to-end network that can be dynamically created. A UE may access to multiple slices over the same gNB. Each slice may serve a particular service type with agreed upon Service-level Agreement (SLA).,3GPP considers Network Slicing a crucial 5G functionality. Network slices are dynamically formed logical end-to-end networks. A UE can use several gNB slices. Each slice serves a SLA-agreed-upon service type (SLA).
210,"S-NSSAI is an identifier for a Network Slice across the 5GC, 5G-RAN and the UE. The S-NSSAI may be associated with a PLMN (e.g., PLMN ID) and have network-specific values or have standard values. A S-NSSAI is used by the UE in access network in the PLMN that the S-NSSAI is associated with. A S-NSSAI is Consist of Slice/Service type (SST) and Slice Differentiator (SD). SST ID is Mandatory and its length is 8 bits where as SD is Optional SD to differentiates slices with same SST and having a total length of  24 bits. Standardized S-NSSAI has only SST and no SD, while non-standard S-NSSAI can be defined as either SST alone (Non-standard) or SST + SD.","S-NSSAI identifies a 5GC, 5G-RAN, and UE Network Slice. The S-NSSAI may be coupled with a PLMN and contain network-specific or standard settings. UEs employ S-NSSAIs in PLMN access networks. A S-NSSAI includes Slice/Service type (SST) and Slice Differentiator (SD). Mandatory SST ID is 8 bits long, whereas optional SD is 24 bits long and differentiates slices with the same SST. Standardized S-NSSAI has only SST and no SD, while non-standard S-NSSAI can be SST alone or SST + SD."
211,"SDN enables possibilities to combine the capabilities in order to enable configuration, optimization and control from centralized location or aggregation points for the underlying RAN infrastructure. This way now 4G eNB or 5G gNB functionalities like mobility management, admission control, interference management can be exposed as Software Apps to be available at northbound interface. The Software Apps can be used as plug-ins with the help RAN controller, and their policies can be enforced via southbound interface towards eNB/gNB. Such architecture enables unprecedented means for controlling radio resources in comprehensive way. So we can say that RAN Intelligent Control aka  RIC  is a suite of Software Apps to enable SDN functionalities in open RAN networks.","SDN offers configuration, optimization, and control from centralized locations or aggregation points for RAN infrastructure. 4G eNB or 5G gNB capabilities like mobility management, admission control, and interference management can be offered as Software Apps at northbound interface. Software Apps can be utilized as plug-ins with RAN controller, and their policies can be enforced via southbound interface to eNB/gNB. Such design offers remarkable radio resource control. RIC is a set of Software Apps that enables SDN in open RAN networks."
212,"RIC is basically responsible for all RAN operation and optimization procedure like radio connection management, mobility management, QoS management, edge services, and interference management, radio resource management, higher layer procedure optimization, policy optimization in RAN, and providing guidance, parameters, policies and AI/ML models to support the best effective network operation.","RIC is basically responsible for all RAN operation and optimization procedure in RAN, and providing guidance, parameters, policies and AI/ML models to support the best effective network operation."
213,"The O-RAN reference architecture provides next generation RRM with embedded intelligence,while optionally accommodating legacy RRM. This resides within the RIC Near RT function layer. The RIC near-RT is completely compatible with legacy RRM and its design is started to enhancing the operational challenging functions such as per-UE controlled load-balancing, RB management, interference detection and mitigation.","The O-RAN reference architecture, residing within the RIC Near RT function layer, provides next generation RRM with embedded intelligence.  It is also completely compatible with legacy RRM and its is design is started to enhance the operational challenging functions."
214,"Large amount of data, counters, statistics, failure information are available with L1/L2/L3 protocols stack of eNB/gNB (including CU/DU) which be collected and used for data features and models can be learned or abstracted to empower intelligent management and control the RAN using Data Analytics/Artificial Intelligence (AI)/Machine Learning (ML). Some of the example models includes, network spatial-temporal traffic patterns, user mobility patterns, service type/patterns along with the corresponding prediction, network quality of service (QoS) prediction patterns, massive MIMO parameters configuration, and more can be reused, abstracted or learned. This abstracted or learned information can then be combined with additional network-wide context and policies can be framed to drive fine-grained network operations i.e. radio resource management, load-balancing, ID allocations, handover decisions, etc.",L1/L2/L3 protocols stack of eNB/gNB has large amount of data which can be collected and used to control the RAN using Artificial Intelligence/Machine Learning. The learned information by the models can be combined with additional network-wide context and used to frame policies to drive fine-grained network operations.
215,"The core algorithms used by AI/ML can be developed and owned by network service provider (operators), some aspects of which may be proprietary. This provides the capability to modify the RAN behaviors by deploying different policies and models optimized to individual operator intents and objectives.",The network service providers can develop and own the core algorithms of AI/ML which will provide the capability to modify the RAN behaviors to operator intents and objectives.
216,"When a UE  is connected to the network, it requires to continuously monitor the Radio link for reliable communication, the process is know as Radio Link Monitoring (RLM). The UE monitor’s the downlink link quality based on the reference signal to measure the downlink radio link quality for the serving cell. In 5G NR, Radio Link Monitoring is applicable for  both Standalone (SA) and Non-standalone (NSA) architecture. UE performs RLM on active DL BWP of the Primary serving cell (PCell) of the Master Cell Group (MCG). If the UE is configured with a Secondary Cell Group (SCG), then the UE also monitors downlink radio link quality on the active DL BWP of the Primary SCG Cell (PSCell).","When connected to a network, UE needs to monitor the Radio link for reliable communiaction contiuously which is know as Radio Link Monitoring (RLM). It uses reference signal for this purpose and is applicable to both  Standalone (SA) and Non-standalone (NSA) architecture. If configured with a Secondary Cell Group (SCG), then the UE also monitors downlink radio link quality on the active DL BWP of the Primary SCG Cell (PSCell), otherwise it only performs RLM on active DL BWP of the Primary serving cell (PCell) of the Master Cell Group (MCG)"
217,"UE monitor’s the downlink radio link quality based on the reference signal configured as RLM-RS resources to detect the downlink radio link quality of the PCell and PSCell in 5G NR. When no RLM-RS resources are configured then, the UE will monitor the current SSB for the downlink radio link quality.",When no RLM-RS resources are configured the UE monitors the cureent SSB for the downlink radio quality of the PCell and PSCell in 5G NR. Otherwise it uses reference signal configured as RLM-RS resources.
218,"When a UE monitors the reference signals RLM-RS as configured by the network, it needs to determine whether the quality of the measured signal is good or worse. So a criteria or threshold definition is required to determine when the signal is above the worse threshold and when it is below the worse threshold. 3GPP specification has defined two thresholds for entry and exit criteria when a UE can declare radio link failure and when it can exit the RLF. The same thresholds are defined for 4G LTE and 5G-NR, but the reference signals measured for RLM are different in LTE and NR.",UE needs to determine the quality of the measured signal when monitoring the reference signals RLM-RS. 3GPP specifiaction has defined two thresholds for this purpose. 
219,"The no. of RLM-RS, UE that needs to monitor per frequency range (FRs) because the no. of SSB varies per frequency range. UE shall be able to monitor up to N-RLM RLM-RS resources of the same or different types in each corresponding carrier frequency range, depending on a maximum number Lmax of SSBs per half frame.",UE shall be able to monitor up to N-RLM RLM-RS resources because of the varying no. of SSB per frequency page.
220,"A 5GS session management (5GSM) message is piggybacked in specific 5GS mobility management (5GMM) transport messages. To this purpose, the 5GSM messages can be transmitted in an information element in the 5GMM transport messages. In this case, the UE, the AMF and the SMF execute the 5GMM procedure and the 5GSM procedure in parallel. The success of the 5GMM procedure is not dependent on the success of the piggybacked 5GSM procedure.",A 5GS message is sent together with 5GS transport message.
221,"The use of ciphering in a network is an operator option. In this subclause, for the ease of description, it is assumed that ciphering is used, unless explicitly indicated otherwise. Operation of a network without ciphering is achieved by configuring the AMF so that it always selects the ""null ciphering algorithm"", 5GEA0. ",Ciphering is operator dependent and operation of a network without ciphering is achieved by configuring the AMF.
222,"Before security can be activated, the AMF and the UE need to establish a 5G NAS security context. Usually, the 5G
NAS security context is created as the result of a primary authentication and key agreement procedure between the
AMF and the UE. A new 5G NAS security context may also be created during an N1 mode to N1 mode handover.
Alternatively, during inter-system change from S1 mode to N1 mode, the AMF not supporting interworking without
N26 and the UE operating in single-registration mode may derive a mapped 5G NAS security context from an EPS
security context that has been established while the UE was in S1 mode 4.",Before security the AMF and UE needs to do the authentication and key agreement procedure.
223,"The 5G NAS security context is taken into use by the UE and the AMF, when the AMF initiates a security mode control procedure, during an N1 mode to N1 mode handover, or during the inter-system change procedure from S1 mode to N1 mode. The 5G NAS security context which has been taken into use by the network most recently is called current 5G NAS security context. This current 5G NAS security context can be of type native or mapped, i.e. originating from a native 5G NAS security context or mapped 5G NAS security context.",The security context used by the network is called current 5G NAS security context.
224,"If the UE is capable of registration over both 3GPP access and non-3GPP access, the UE shall store the current native 5G NAS security contexts of the 3GPP access and the non-3GPP access as specified in annex C and mark them as valid only when the UE enters state 5GMM-DEREGISTERED from any other state except 5GMM-NULL over both the 3GPP access and non-3GPP access or only when the UE aborts the initial registration procedure without having left 5GMM-DEREGISTERED over both the 3GPP access and non-3GPP access. Otherwise, the UE shall store the current native 5G NAS security context as specified in annex C and mark it as valid only when the UE enters state 5GMMDEREGISTERED from any other state except 5GMM-NULL or when the UE aborts the initial registration procedure without having left 5GMM-DEREGISTERED. ","If the UE is capable of registration over both 3GPP access and non-3GPP access, the UE shall mark the 
current native 5G NAS security as valid only when the UE enters state 5GMM-DEREGISTERED."
225,"When a new 5G NAS security context is created from a new KAMF, the target AMF includes the 8 least significant bits of the downlink NAS COUNT in the Intra N1 mode NAS transparent container IE and indicates that a new KAMF shall be derived. The AMF shall then set both the uplink and downlink NAS COUNT counters of this 5G NAS security context to zero. The AMF shall increment the downlink NAS COUNT by one after creating the Intra N1 mode NAS transparent container IE. ","When a new 5G NAS security context is created from a new KAMF, then the AMF set both the uplink 
and downlink NAS counters to zero."
226,"Secure exchange of NAS messages via a NAS signalling connection is usually established by the AMF during the registration procedure by initiating a security mode control procedure. After successful completion of the security mode control procedure, all NAS messages exchanged between the UE and the AMF are sent integrity protected using the current 5G security algorithms, and except for the messages specified in subclause, all NAS messages exchanged between the UE and the AMF are sent ciphered using the current 5G security algorithms. ","Secure exchange of NAS messages via a NAS signalling connection is usually established by the AMF
during the registration procedure by initiating a security mode control procedure."
227,"For the case when the UE has two records of NAS security context stored and is attempting registration to the PLMN associated with the 5G-GUTI (or an equivalent PLMN) for that access, the UE uses the first NAS security context of that access to protect the initial NAS message. For the case when the UE has two records of NAS security context stored and is attempting registration to the PLMN associated with the second record (or an equivalent PLMN) of that access, the UE uses the second NAS security context of that access to protect the initial NAS message. For other cases when the UE has two records of NAS security context stored and is attempting registration to a PLMN which is not associated with any NAS security context record, the UE uses either record of the NAS security context of that access to protect the initial NAS message. ","When the UE has two records of NAS security context stored and is attempting registration, the UE
uses the first NAS security context of that access to protect the initial NAS message."
228,"Both UE and AMF shall continue to use the current 5G NAS security context, until the AMF initiates a security mode control procedure. The SECURITY MODE COMMAND message sent by the AMF includes the ngKSI of the new 5G NAS security context to be used. The AMF shall send the SECURITY MODE COMMAND message integrity protected with the new 5G NAS security context, but unciphered. When the UE responds with a SECURITY MODE COMPLETE message, it shall send the message integrity protected and ciphered with the new 5G NAS security context. ","UE and AMF shall continue to use the current 5G NAS security context, until the AMF initiates a new 
secuity mode control procedure."
229,"Each 5G NAS security context shall be associated with two separate counters NAS COUNT per access type in the same PLMN: one related to uplink NAS messages and one related to downlink NAS messages. If the 5G NAS security context is used for access via both 3GPP and non-3GPP access in the same PLMN, there are two NAS COUNT counter pairs associated with the 5G NAS security context. The NAS COUNT counters use 24-bit internal representation and are independently maintained by UE and AMF. The NAS COUNT shall be constructed as a NAS sequence number (8 least significant bits) concatenated with a NAS overflow counter (16 most significant bits).","Each 5G NAS security context has two separate NAS COUNT, with a NAS sequence number (8 least
significat bits) and NAS overflow counter (16 most significant bits)."
230,"The NAS sequence number part of the NAS COUNT shall be exchanged between the UE and the AMF as part of the NAS signalling. After each new or retransmitted outbound SECURITY PROTECTED 5GS NAS MESSAGE message, the sender shall increase the NAS COUNT number by one, except for the initial NAS messages if the lower layers indicated the failure to establish the RRC connection. Specifically, on the sender side, the NAS sequence number shall be increased by one, and if the result is zero (due to wrap around), the stored NAS overflow counter shall also be incremented by one. If, through implementation-dependent means, the receiver determines that the NAS message is a replay of an earlier NAS message, then the receiver handles the received NAS message as described in subclause. ","NAS sequence number part of the NAS COUNT shall be exchanged between the UE and the AMF and
after each new or retransmitted outbound SECURITY PROTECTED 5GS NAS MESSAGE message, 
the counter will be incremented."
231,"If for some reason a new KAMF has not been established using primary authentication and key agreement procedure before the NAS COUNT wraps around, the node (AMF or UE) in need of sending a NAS message shall instead release the NAS signalling connection.","If a new KAMF not established before the NAS COUNT wrap around, then the connection will be
released."
232,"For the UE, integrity protected signalling is mandatory for the 5GMM NAS messages once a valid 5G NAS security context exists and has been taken into use. For the network, integrity protected signalling is mandatory for the 5GMM NAS messages once a secure exchange of 5GS NAS messages has been established for the NAS signalling connection. Integrity protection of all NAS signalling messages is the responsibility of the NAS. It is the network which activates integrity protection. ","For the UE, integrity protection is mandatory after a valid security context."
233,"The REGISTRATION REQUEST message is sent by the UE without integrity protection, if the registration procedure is initiated due to an inter-system change in 5GMM-IDLE mode and no current 5G NAS security context is available in the UE. The other messages are accepted by the AMF without integrity protection, as in certain situations they are sent by the UE before security can be activated. ",The REGISTRATION REQUEST is sent without integrity protection.
234,"A conference ID would be assigned by the MRFC and would be used by the AS in subsequent interactions with the MRFC in INVITE messages connecting other transcoding services. That is, the AS will send an INVITE to the MRFC with an indication of the capability being requested and with additional information related to the specific service such as identification of the announcement to be played or identification of the specific transcoding. Interactions for services using both the Ut interface and MRFC Network services hosted on an AS and configurable by the user via the Ut interface may also use the capabilities provided by the MRFC. For this case, the AS either supports MRFC capabilities, or communicates with an Communications across the Ut interface between the UE and the AS allow the UE to securely manage and configure data for such services (e.g. conference type services).",The AS will send an INVIE to the MRFC with an indication of the capability being requested and with additional information related to the specific service such as identification of the announcement to be played or identification of the specific transcoding.
235,"Means for the AS to propagate this management and configuration information to the MRFC is not standardized in this Release. Transcoding services involving the MRFC/MRFP Network services involving MRFC and MRFP are not limited to conferencing and announcements, but also involve transcoding support for interworking between IMSs or inter-domain sessions, and intra-domain sessions between access technologies supported in an IMS (e.g.wireline wireless interworking, or interworking with non-3GPP wireless technologies).",AS propagation of management and configuration to the MRFC is not standardized and transcoding services involving the MRFC/MRFP Network services involving MRFC and MRFP are not limited to conferencing and announcements.
236,"For the access bearer termination, the exchange of IP addresses via call control procedures as described in applies with the following exception. The Prepare_IP_Transport procedure is used after the MSC Server receives the RANAP Enhanced Relocation Complete Request. If the bearer transport is IP and IuUP mode is Transparent, when the MSC Server receives the RANAP Enhanced Relocation Complete Response, it shall send the RNC IP address and UDP Port to the MGW Access bearer termination. Enhanced SRNS Relocation with Iu on IP In the context of the following clauses, the terms RNS or RNC refer also to a GERAN BSS or BSC (respectively) when serving an UE in Iu mode Intra-MSC UMTS to GSM Handover from UMTS to GSM"" shall be followed.","If the bearer transport is IP and IuUP mode is Transparent, when the MSC Server receives the RANAP Enhanced Relocation Complete Response, it shall send the RNC IP address and UDP Port to MGW Access bearer termination."
237,"The BM-SC initiates the MBMS Session Start procedure when it is ready to send data. This is a request to activate all necessary bearer resources in the network for the transfer of MBMS data and to notify interested UEs of the imminent start of the transmission. Through this procedure, MBMS session attributes such as QoS, MBMS service Area, estimated session duration, are provided to the registered GGSN(s) and SGSN(s), to all BSCs/RNCs that are connected to a listed SGSN and to the registered MBMS GW(s) and MME(s). In addition the procedure allocates the bearer plane to all registered GGSNs, all registered SGSNs and all registered MBMS GWs, to BSCs/RNCs and E-UTRAN that respond to the session start request message.",The MBMS session start request to activae all necessary bearer resources in the network for the transfer of MBMS data and to notify interested UEs of the imminent start of the transmission.
238,"When a WLAN AN providing direct Internet access has connections to multiple correct VPLMN whilst Internet traffic is routed directly to the Internet. The VPLMN identity is known to the WLAN AN at initial user authentication/authorisation, since the AAA signalling is routed to that VPLMN, and the Access-Accept received from that VPLMN. Therefore, for each VPLMN there must be a separate (logical) router in the WLAN AN which has a connection to that VPLMN and also to the Internet from WLAN UEs that are authenticated through that VPLMN.","The VPLMN identity is known to the WLAN AN at initial user authentication/authorisation, since the AAA signaling is routed to that VPLMN, and the Access-Accept received from that VPLMN."
239,"If explicit APN AMBR values are not received by the MME, a local UE-AMBR shall be ""Data forwarding not possible"" indication per bearer shall be included corresponding bearer will not be subject to data forwarding parameters received from the SGSN from the RNC ID received from old SGSN an eNodeB address. The target eNodeB allocates the requested resources and returns the applicable parameters to the target MME in the message Handover Request Acknowledge (Target to Source Transparent Container, EPS Bearers setup list, EPS Bearers failed to setup list, Cause).","If explicit APN AMBR values are not received by the MME, an indication per bearer shall be included corresponding bearer will not be subject to data forwording parameters received from the SGSN from the RNC ID received from old SGSN and eNodeB address."
240,"For downlink transfers the MTC-IWF determines the serving node address by resolving the receiver ID of the SDT-PDU via HSS interrogation. The header of an SDT-PDU identifies the ""SENDER"" and the ""RECEIVER"" of the PDU. For M2M messaging MO case the sender is the UE (UE internal ID e.g IMSI, MSISDN, or UE external ID) and the receiver is the SCS or AS. For M2M messaging MT it is vice versa.",In downlink transfers the MTC-IWF determines the serving node address by resolving the receiver ID of the SDT-PDU via HSS interrogration .
241,"The introduction of the timer permits to avoid signalling overloading while MS is switching back and forth between the GAN. An ACTIVE Access Termination with the SLAVE role enters MASTER upon receiving either a create PDP context or an update PDP context request. Note that in the case of the update PDP context, the PCO should explicitly contain the MASTER_REQ container. When receiving an update PDP request without MASTER_REQ container on an access termination in ACTIVE-SLAVE state the request is processed locally no procedure is initiated on the Network Termination.",The timer permits are used to avoid signalling overloading while MS is switching back and forth between the GAN.
242,"The terrestrial resource for the group call channel is not A-interface link sharing used or group call re-establishment by Uplink release for the talker on group call channel after equipment. If A-interface link sharing is used or group call re-establishment by the BSS is supported, the BSC shall send the message UPLINK RELEASE INDICATION with cause value ""equipment failure"" or another appropriate cause value, if a failure concerning the cell that is serving the talker was detected.","If A-interface link sharing is used or group call re-establishment by the BSS is supported, the BSC shall send the UPLINK RELEASE INDICATION request."
243,"To model the information exchange between BSCs, an inter-BSC connection should be defined. This is done in a vendor specific way, but the assumptions on the inter-BSC connection will be declared. Such assumptions will cover parameters e.g. delay, bandwidth and reliability. It is expected that the ENHVAMOS study as an output will give recommendation on the above mentioned parameters.","To model the information exchange between BSCs, a vendor specific inter-BSC connection should be defined."
244,"The real time data flow is always aiming at a live (human) destination. It is a one way transport. This scheme is one of the newcomers in data communication, raising a number of new requirements in both telecommunication and data communication systems. It is characterised by that the time relations (variation) between information entities (i.e. a server), this scheme applies. Examples of human interaction with the remote equipment are: web browsing data base retrieval, server access. At the message destination there is an entity expecting the message (response) within a certain time. Round trip delay time is therefore one of the key attributes. The scheme is thus more or less delivery time insensitive.","The real time dataflow aiming at a live human is a newcomer in data communication, raising a number of new requirements in both telecommunication and data communication systems."
245,"To request a concurrent AMR and redundancy mode adaptation, the decoder (speech receiver) signals the encoder (speech sender) the new AMR mode it prefers in Codec Mode Request (CMR). The redundancy mode for each mode of the Active Codec Set is signaled in the Redundancy Configuration IE. This way the preferred redundancy mode is also implicitly requested with the CMR. The frame loss rate for the received speech data is continuously monitored by the MS and the network.","For concurrent AMR and redundancy mode adaptation, the decover signals the enoder the new AMR mode it prefers in CMR."
246,"In the Local Breakout case, the vPCRF forwards messages between the PDN GW and the hPCRF. The optional interaction steps between the gateways and the PCRF in the deployed. Otherwise policy may be statically configured with the gateway A. The Serving GW initiates the Gateway Control and QoS Policy Rules provides the content of the Traffic Aggregate Description (TAD) and the requested QoS change to the PCRF as an Event Report. The PCRF makes a PCC decision as a result of the Gateway Control and QoS policy request and provides the updated QoS Rules to the Serving GW.","The vPCRF forwards messages between the PDN GW and the hPCRF in local breakout case, otherwise the policy may be statically configured with the gateway."
247,"An MSC area may consist of several location areas. A location area is an area in which, after having performed a location update once, MSs may roam without being required to perform subsequent location updates for reason of location change.
The Location Area Identification (LAI) plan is part of the base station identification plan. The base stations are identified uniquely (see 3GPP TS The support of IMSI detach/attach operation is mandatory in MSs.",MAC area may consist of several location areas. Location are areas where MSs may roam without being required to perform subsequent location updates.
248,"The BSS shall not negotiate BSS packet flow contexts for these pre-defined packet flows with the SGSN. One pre-defined packet flow is used for best-effort service, one is used for SMS, one is used for TOM (Tunnelling of Messages) and one is used for signalling.
The SGSN can assign the best-effort or SMS packet flow identifier to any PDP context. In the SMS case, the BSS shall handle the packet flow for the PDP context with the same QoS with which it handles SMS.","BSS shall not negotiate BSS packet flows for pre-defined flows with the SGSN such as flows used for best-effort service, flows for TOM etc."
249,"When generating a peer list, the Tracker AS, and/or other network entities need to be mindful of the access type or even actual uplink/downlink bandwidth, a peer is A. Battery powered device Mobile devices normally rely on a battery for their power source, rather than connected to the mains electricity. Thus, it is not often ""fair"" to assign such a peer as a resource provider, even though the mobile device may be used for the downloading of content. Therefore, when generating a peer list, the Tracker AS, and/or other network entities need to be mindful of the power limitations that a peer may have.","As battery powered device Mobile  devices normally rely on a battery for their power source, it is not often fair to assign such a peer as a resource provider, even though the mobile device may be used for the downloading of the content."
250,"CBS messages are broadcast to defined geographical areas known as cell broadcast areas. These areas may comprise of one or more cells, or may comprise the entire PLMN. Individual CBS messages will be assigned their own geographical coverage areas by mutual agreement between the information provider and the PLMN operator. CBS messages may originate from a number of Cell Broadcast Entities (CBEs), which are connected to the Cell Broadcast Centre. CBS messages are then sent from the CBC to the cells, in accordance A CBS page comprises of 82 octets, which, using the default character set concatenated to form a CBS messagee. Each page of such CBS message will have the same message identifier (indicating the source of the message) and the same serial number.","CBS messages are broadcast to defined geographical areas known as broadcast areas which may comprise of one or more cells, or may comprise of entire PLMN. CBS messages may originiate from a number of CBEs, which are connected to to the Cell Broadcast Centre."
251,"For each PDN connection, the H1 PDN Attach has to be performed separately a UE and a HA context to GGSN from which the discovered HA can be reached via H When connected over the UE home link (e.g. 3GPP access), the UE may be configured not to trigger the establishment of IKEv2 SA. In this case, H1 PDN Attach is triggered when the UE moves to I-WLAN. During the Handover the UE keeps using the source 2G/3G) access. A security association is established between UE and HA to secure the DSMIPv6 messages related to this PDN connection between the UE and the HA. The UE initiates the establishment of the security association authentication purposes. After the IPv6 home network prefix is assigned, UE constructs a home address from it via auto In this step, the HA may be either in the HPLMN or in the VPLMN.","For PDN connection, the H1 PDN Attach has to be performed separately a UE and a HA context to GGSN from which the discovered HA can be reached and H1 PDN Attach is triggered when the UE moves to I-WLAN."
252,"The Functions subclause describes the CUG service logic and how CUG information is used. The flow of CUG information Handling of Closed User Group A GSM PLMN supporting the CUG supplementary service must guarantee the integrity of any CUG which it handles. It is not however mandatory for a PLMN to support the CUG supplementary service. A CUG is uniquely identified within a network by a CUG Interlock Code. The Interlock Code is transferred between terrestrial network entities to indicate a CUG call A user identifies a CUG by a CUG Index. A CUG Index is used to select or indicate the use of a specific CUG in relation to a call. This is termed Explicit CUG invocation Alternatively, if the subscription allows, some default characteristic of a CUG may be invoked automatically if no CUG information is provided.","The flow of CUG information handling of Closed User Group A GSM PLMN supporting the CUG supplementary service must guarantee the integrity of any CUG which it handles, but it is not mandatory for a PLMN to support the CUG supplementary service."
253,"An E-UTRAN Sharing architecture allows different core network operators to connect to a shared radio access network. The operators do not only share the radio network elements, but may also share the radio resources themselves. In addition to this shared radio access network the operators may or may not have additional dedicated radio access networks, like for example, 3G or 2G radio access networks. For E-UTRAN both Multi-Operator Core Network (MOCN) configuration and Gateway Core Network (GWCN) reference point. E-UTRAN terminals shall support shared networks and hence functionality for emergency bearer services in a single clause.","E-UTRAN sharing architecture allows different core networ operators to connect to a shared radio access network. The operators can share radio network elements, radio resource and additonal dedicated radio access networks."
254,"When the S9a session is initiated by BPCF, PCRF must perform the session binding between the S9a session and the Gx session according to the UE Local IP address, if available, and UE identity. Similarly, the PCRF may be served by one or more BPCF nodes in the fixed network For BPCF-initiated S9a session case, PCRF selection procedure, including by BPCF. For a roaming scenario the BPCF is configured with the relation of HPLMN-Id reachable via a particular VPLMN-Id. The BPCF selects given a certain IMSI the correct DRA in the VPLMN. The vPCRF finds the DRA in the For PCRF-triggered S9a session establishment, the PCRF is configured with IP address range mappings. For WLAN scenario the PCRF selects the correct BBF network entry point based on UE Local IP address. From H(e)NB scenario the PCRF selects the correct BBF network entry point based on H(e)NB Local IP address and/or FQDN of BBF access network at which the H(e)NB is connected to.","With the S9a session initiated by BPCF, PCRF must perform the session binding between the S9a session and the Gx session. Similarly the PCRF may be served by one or more BPCF nodes in the fixed network for BPCF-initiated S9a session care."
255,"Originating sessions that use PS media When the ICS UE has access to a PS network that supports the full duplex speech component of an IMS service, the originating IMS procedures. The S-CSCF shall insert the SCC AS in the IMS session path using originating initial filter criteria. The SCC AS shall be the first AS inserted into the session path Originating sessions that use CS media Non ICS UE originating sessions that use CS media. Originating sessions that use CS media made by non ICS UEs that have been successfully registered in IMS by the MSC Server can utilize IMS service control.",Originating sessions that use CS media made by non ICS UEs that use CS media made by non ICS UEs that have been succesfully registered in IMS by the MSC server can utilize IMS service control.
256,"There are a number of PSTN features which should be avoided from such connections 1) echo control devices in the international network. If present, and not disabled, these devices will be in tandem with PLMN echo cancellers and 2) satellite routeings. The delay inherent in the connections when added to the PLMN delay, may result in conversational difficulties. Double satellite links are likely to cause severe difficulties and special precautions should be taken to avoid this situation under call 3) Digital Speech Interpolation systems (DSI). There is likely to be an adverse interaction between DSI and DTX 4) ADPCM. The resulting phase roll and slips are likely to degrade the performance of the PLMN echo canceller 6) those analogue FDM routeings which exhibit phase roll.",The delay inherent in the connections when added to the PLMN delay may result in conversational difficulties.
257,"Optionally, the GANC may initiate the standard BSSGP GPRS resume procedure. The GANC sends a GAN-RR RR RELEASE message to instruct the MS to release the RR connection. The message includes GPRS resume indication IE as per standard GSM/GPRS to indicate whether the network successfully resumed GPRS service or not. The MS replies with a GAN-RR RR RELEASE COMPLETE message and resumes GPRS service internally. This allows the MS to obtain all GSM services that it receives through a GSM BSS, through the GAN - GSM-RR protocol is replaced with a GAN-RR protocol.",The GANC may initiate the resume procedure by sending a release message to instruct the MS to release the RR connection. The MS replies with RR Release complete message and resumes service internally.
258,Using CMPv2 a request for a certificate is sent to the RA/CA. The network authenticates the messages from the base station based on the vendor-signed certificate of the base station and the vendor root certificate pre-installed in the network. The base station shall check the integrity protection on the messages from the RA/CA based on the operator root certificate provisioned in the base station. In a response message the base station receives the operator-signed certificate.,The network authenticates the message from the base station based on the vendor-signed certificate of the base station and the vendor root certificate pre-installed in the network.
259,"In particular, the stored NAS downlink COUNT shall never be decreased UE and MME shall assign the value of eKSI to KSI. MME shall transfer CKSRVCC, IKSRVCC with KSI and the UE security capability to the MSC server enhanced for SRVCC. The MSC server enhanced for SRVCC shall replace all the stored UTRAN CS key parameters CK, IK, KSI, if any, with CKSRVCC, IKSRVCC KSI received from the MME when the SRVCC handover is successful. The UE shall replace all the stored UTRAN CS key parameters CK, IK, KSI, if any with CKSRVCC, IKSRVCC, KSI in both ME and USIM. STARTCS shall comply with The ME shall use CKSRVCC and IKSRVCC to derive the GSM CS Kc using the c3 function. The ME shall assign the eKSI value (associated with CKSRVCC and IKSRVCC) to the GSM CS CKSN (associated with the GSM CS Kc).","MME shall transfer CKSRVCC, IKRVCC with KSI and the UE security capability to the MSC server enhanced for SRVCC and the MSC server enhanced for SRVCC shall replace all the stored UTRAN CS key parameters CK, IK, KSI, if any, with CKSRVCC, IKSRVCC KSI received from the MME when SRVCC handover is successful. "
260,Using CMPv2 a request for a certificate is sent to the RA/CA. The network authenticates the messages from the base station based on the vendor-signed certificate of the base station and the vendor root certificate pre-installed in the network. The base station shall check the integrity protection on the messages from the RA/CA based on the operator root certificate provisioned in the base station. In a response message the base station receives the operator-signed certificate.,The network authenticates the certificate from the base station based on the vendor-signed certificate of the base station and the vendor root cerificiate pre-installed in the network.
261,"The conference bridge then has the shared secrets it needs to communicate securely with IMS UE-A, IMS UE-B and IMS UE-C respectively communicate securely with the KMS. This solution does not apply to the case where the protection is required between the end user and the access edge. User A bootstraps with KMS to establish a shared key Ka. If GBA is not support, User A can use other authentication method to get shared 1sg. Secure Gateway(SGW) establish a secure connection with KMS by Ipsec TLS or any other authentication method by which KMS and SGW can have a 1sm.","The conference bridge has the shared secrets it needs to communiate securely with IMS. If GBA is not supported, an user can use other authentication method to get shared 1sg."
262,"Another contributor to the error budget is unmodeled atmospheric delay.
The techniques used to correct these error sources are collectively known as differential GPS (DGPS).
These methods involve locating one or more reference receivers at known locations and observing the visible satellite signals.
These receivers essentially solve the inverse GPS problem - find differences from the expected measurements at the known position.
The accuracy of the DGPS corrections is inversely proportional to the distance from the reference location.
The inaccuracy is caused by changes in the geometry and visibility of the satellite constellation.",The accuracy of the DGPS corrections is inversely proportional to the distance from the reference location. There can be errors and inaccuracy.
263,"To deliver the entire data set within broadcast at a much slower rate.
The SMSCB used for LCS uses the basic CBCH or extended CBCH.
The support of E-OTD and/or DGPS broadcast needs capacity related to broadcast message characteristics (RTD/DGPS validity).
The SMSCB DRX service also needs to schedule a message that is sent once per schedule period.
The maximum schedule period is 48 SMSCB message slots Example of capacity scenario - The basic CBCH uses the same physical resource as SDCCH/4 (sub channel 2) or SDCCH/8 (sub channel 2).",The SMSCB used for LCS uses the basic CBCH or extended CBCH. The support of E-OTD and/or DGPS broadcast needs capacity related to broadcast message characteristics.
264,"On a full duplex control channel (DCCHs) or on the BCCH/CCCH in the network, the data link layer will offer physical blocks to be transmitted in PH-DATA-REQUEST primitives.
On a packet data physical channel (A/Gb mode) or shared basic physical subchannel (Iu mode), the RLC/MAC layer will offer physical blocks to be transmitted in PH-DATA REQUEST primitives.
In the MS in idle mode or in packetidle mode, random accesses on RACH or on PRACH can be offered in PH-RANDOM ACCESS-REQUEST primitives.
The physical layer of the MS will perform a random access as soon as possible.
The physical layer of the MS will confirm the data link layer or the RLC/MAC layer, the one which is applicable, the transmission of the random access attempt in a PH-RANDOM ACCESS-CONFIRM.
This confirmation contains the absolute frame number in which the random access is transmitted.
The physical layer of the BS offers correctly received random accesses to the data link layer or the RLC/MAC layer, the one which is applicable, in a PH-RANDOM ACCESS-INDICATION.
This indication contains the absolute frame number in which the random access is received.","On a full duplex control channel, the data link layer will offer physical blocks to be transmitted in PH-DATA-REQUEST primitives. On a packet data physical channel or shared basic physical channel, the RLC/MAC layer will offer physical blocks to be transmitted in PH-DATA REQUEST primitives."
265,"Entities in the same layer, but in different systems which must exchange information to achieve a common objective are called ""peer entities"".
Entities in adjacent layers interact through their common boundary.
The services provided by the (N + 1)-layer are the combination of the services and functions provided by the (N)-layer and all layers below the (N)-layer Management functions may also be required.
They may include functions which are common for several layers and are not supported by the services provided by a specific layer.
Examples of such functions are error reporting, status reporting and management of the operation of certain layers.
Such management functions do not require that peer-to-peer messages are sent across the MS-BSS interface. For signalling on the MS-BSS interface three layers are required.
Layering on the MS-BSS interface - PHYSICAL LAYER which corresponds to the lowest layer.
The functions and protocols of the physical layer are defined in Technical Specification 3GPP TS 40 - DATA LINK LAYER.","Entities in the same layer, but in different systems which must exchange information to achieve a common objective are called peer entities."
266,"Report Priority information can be received in one instance of the MEASUREMENT INFORMATION message.
The Report Priority information is associated with the Neighbour Cell list (see\) having the same BA_IND value and 3G_BA_IND value.
Each REP_PRIORITY bit of this field relates to indices of the Neighbour Cell list, starting with index. The Report Priority information may be received before the corresponding Neighbour Cell list.
When the BA_IND or 3G_BA_IND are changed the MS shall re-read the REP_PRIORITY parameters in all instances Indices exceeding the value 95 shall be ignored.",Report Priority information can be received in one instance of the MEASUREMENT INFORMATION message. The report priority information is associated with the neighbour cell list having the same values.
267,"Comfort breaks should be provided to reduce the effects of subject fatigue.
The question asked of the subject is according to the Paired-Comparison binary scale.
The specific wording is designed to evaluate the relative quality of the test sample in relation to the reference sample.
In order to minimise presentation bias, the samples will be presented in both the A/B and B/A directions within the experiment.
The subjects will listen to each pair of samples, and after presentation is completed, they will be asked to give their opinion.",The question asked of the subject is according to paired-comparison binary scale amd the specific wording is designed to evaluate the relative quality of the test sample in relation to the reference sample.
268,"Video receivers should implement an adaptive video de-jitter buffer.
The overall design of the buffer should aim to minimize delay, maintain synchronization with speech, and minimize dropping of late packets.
The exact implementation is left to the implementer.
Conversational quality of real-time text is experienced as being good, even with up to one second end-to-end text delay.
Strict jitter buffer management is therefore not needed for text.
Basic jitter buffer management described for the time allowed before an extra delayed text packet may be regarded to be lost.
This clause specifies some methods to handle conditions with packet losses Packet losses in general will also trigger adaptation.","Video receivers should implement a video de-jitter buffer, the overall design of which should minimize delay but the exact implementation is left to the implementer."
269,"Thus the memory requirement in the present algebraic structure is 1088 words instead of 64(64=4096 words. The search procedures at the different bit rates modes are similar.
The difference is in the number of pulses, and accordingly, the number of levels in the tree search.
In order to keep a comparable search complexity across the different codebooks, the number of tested positions is kept. The search in the 15 kbit/s mode will be described as an example.
In this mode, 2 pulses are placed in each track giving a total of 8 pulses per subframe of length 6. Two pulses are searched at a time, and these two pulses always correspond to consecutive tracks.","The memory requirement in the present structure is 1088 words. In order to keep a comparable search complexity across the different codebooks, the number of tested positions is kept."
270,"A 3GP file may include an extended presentation that consists of media files in addition to tracks for audio, video and text.
Examples of such media files are static images, e.g. JPEG files, which can be stored in a presentation must include a scene description that governs the rendering of all parts of the 3GP file at the top level of the file as defined in .
The Meta box shall include - Primary item box or XML box identifying the scene description - Item information box - Item location box. A scene description (e.g. an SVG scene, in the case of DIMS, or a SMIL file) shall be included either in an XML box or as an item located by the Item location box.","A 3GP file may include extended presentation that consists of media files such as JPEG in addition to tracks for audio, video and text."
271,"ID3 tag must not contain any footer information, because it is never needed Both ID3v2 tag format and its native frames must use the same version of the specification.
Size of this field can be derived from the box size The version of the ID3 data may be found by inspecting it The ID3v2 box contains a complete ID3 version x.x data.
It should be parsed according to ID3v2 specifications for v.x.x tags.
There may be multiple ID3v2 boxes using different language codes.
A 3GP file can include video-buffer parameters associated with video streams.
For the case when only one set of parameters is associated to an entire video stream, these can be included in the corresponding media-level SDP fragment.
However, in order to provide buffer parameters for different operation points, as defined below, and for different synchronization points, a track can contain a video buffer sample grouping.
The type of sample grouping depends on which video-buffer model that is used for a For H.263 and MPEG-4 visual, the PSS buffering model, defined in Annex G of TS 234 (PSS Annex G), is used.","A 3GP file can include video-buffer parameters associated with video streams. For the case when only one set of parameters is associated to an entire video stream, these can included in the corresponding media-level fragment."
272,"The new interpolated spectrum is built by reusing the spectrum of the older frame n-2 multiplying a factor to each spectral coefficient.
An exception is made in the case of a short window sequence in frame n-2 and a long window sequence in frame n here the spectrum of the actual frame n is modified by the interpolation factor.
This factor is constant over the range of each scalefactor band and is derived from the scalefactor band energy differences of frames n-2 and n.
Finally the sign of the interpolated spectral coefficients will be Fade out and in A complete fading out takes 5 frames.",A new interpolated spectrum is built by reusing the spectrum of the older frame n-2 multiplying a factor to each spectral coefficient with exception in the case of a short window sequence in frame n-2 and a long window sequence in frame n.
273,"If received in the DCS 1800 or PCS 1900 bands, those ARFCN numbers shall be interpreted as frequencies in the same band. The BAND_INDICATOR is broadcast on BCCH PBCCH and SACCH. The most recently received value shall be applied by the mobile station. If the parameter is not broadcast, the default value is DCS The reference configuration for the radio subsystem is described in 3GPP. The micro-BTS is different from a normal BTS in two ways. Firstly, the range requirements are much reduced whilst the close proximity requirements are more stringent. Secondly, the micro-BTS is required to be small and cheap to allow external street deployment in large numbers. Because of these differences the micro-BTS needs a different set of RF parameters to be specified. Where the RF parameters are not different for the micro-BTS the normal BTS parameters shall apply. The pico-BTS is an extension of the micro-BTS concept to the indoor environments.","The reference configuration for the radio subsystem is described in 3GPP, the micro-BTS is different from a normal BTS in two ways: (i) the range requirements are much reduced whilst the close proximity requirements are more stong; (ii) the micro-BTS is required to be small and cheap to allow external street deployment in large numbers."
274,"With FLO, the physical layer offers transport channels to upper layers.
In each direction, one or several transport channels can be processed and multiplexed together by the same coding and multiplexing unit.
The detailed functions of the coding and multiplexing unit are defined in 3GPP TS. The offered transport channels are Dedicated CHannels (DCHs).
DCHs are unidirectional and used to carry user or control data on DBPSCH.
Depending on the channel mode of the DBPSCH on which they are used, two general forms of DCH are defined i) Full rate DCH (DCH/F).
This channel carries information at a maximum gross rate of 6 kbit/s and shall only be used on DBPSCH/F ii) Half rate DCH (DCH/H).
This channel carries information at a maximum gross rate of 3 kbit/s and shall only be used on DBPSCH/H.
The single output data block from the coding and multiplexing unit is called a radio packet and it shall be mapped onto one and only one DBPSCH.
It should be noted that any allocated channel Cx within CA could be any radio frequency channel, and that no ordering of radio frequency channel number is implied.","The physical layer offers transprt channels to upper layers. In each direction, one or several transport channels can be processed and multiplexed together by the same coding and multiplexing units."
275,A valid combination is called a Transport Format Combination (TFC). The set of valid TFCs on a basic physical subchannel is called the Transport Format Combination Set (TFCS). The TFCS is signalled through the Calculated Transport Format Combinations (CTFC). In order to decode the received sequence the receiver needs to know the active TFC for a radio packet. This information is transmitted in the Transport Format Combination Indicator (TFCI) field. This field is basically a layer 1 header and has the same function as the stealing bits in GSM. Each of the TFC within a TFCS are assigned a unique TFCI value and when a radio packet is received this is the first to be decoded by the receiver.,A valid combination is called a Transport Format Combination; set of valid TFCs on basic physical subchannel is caled the TFCS. The TFCS is signalled through the CTFC.
276,"Single-user cases have been analysed with simulations for Ping, VoIP and e mail sending and receiving. Single-user means, in this context, that there is only one mobile reserved per packet channel.
For the VoIP cases, this is applicable to both the talker and the listener. For the RTTI cases, Dual-carrier is used in the downlink, whereas Dual-timeslot is used in the uplink to achieve the 10ms TTI.
Thus a two TDMA frame interleaving scheme is applicable. The only used Ack/Nack enhancement is a shorter RRBP. Neither event based Ack/Nack nor piggy-backing of Ack/Nacks are included in the simulations.
RLC/MAC control signalling is transmitted with the same TTI as the data blocks. Since the RTT mode is ""Active RTT"", only non-distribution RLC/MAC control signalling is applicable.
End-to-end latency is typically benchmarked with a Ping traffic case. The default Ping size is 32 bytes which typically ends up with 70 bytes of RLC data: 32 bytes ICMP payload, 8 bytes ICMP header, 20 bytes IP header and 10 bytes LLC/SNDCP header.","Cases where there is only one mobile reserved per packet channel has been analyzed for Ping, VoIP and email sending and receiving. For VoIP this is applicable to both the talker and listener. For RTTI, dual carrier is used in the downlink, whereas dual-timeslot is used in uplink to achieve the TTI."
277,"The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415) if not otherwise. The Visited-Network-Identifier AVP is of type OctetString.
This AVP contains an identifier that helps the home network to identify the visited network (e.g. the visited network domain name). The Public-Identity AVP is of type UTF8String. This AVP contains the public identity of a user in the IMS.
The syntax of this AVP corresponds either to a SIP URL (with the format defined in IETF RFC 3261 and IETF RFC 2396 ) or a TEL URL (with the format defined in IETF RFC 3966\). Both SIP URL and TEL URL shall be in canonical form, as described in 3GPP TS 203. The Server-Name AVP is of type UTF8String. This AVP contains a SIP-URL (as defined in IETF RFC 3261 and IETF RFC 2396\), used to identify a SIP server (e.g. S-CSCF name). The Server-Capabilities AVP is of type Grouped. This AVP contains information to assist the I-CSCF in the selection of an S-CSCF.","For all AVPs, vendor-ID header shall be set to 3GPP (10415) if not otherwise. This AVP contains an identifier that helps the home network to identify the visited network."
278,"The following attributes are used on the break strength: ""none"", ""x-weak"", ""weak"" ""medium"", ""strong"", or ""x-strong"".
It indicates the strength of the prosodic break in the speech output.
For example, the breaks between paragraphs are typically much stronger than the breaks between words within a sentence.
The time attribute is an option attribute indicating the duration of a pause to be inserted in the output in seconds or milliseconds.
The prosody element permits control of the pitch, Optional speaking rate and volume of the speech output.","The attributes, none, x-weak, weak, medium,  strong, x-strong indicates the strength of the prosodic break in the speech output."
279,"The use of stateful or stateless is configured per W-APN. The transparent case provides at least a basic ISP service.
As a consequence of this it may therefore provide a bearer service for a tunnel to a private Intranet. The WLAN UE is given an address belonging to the Intranet/ISP addressing space.
The address is given either at subscription in which case it is a static address or at the WLAN session authorization in which case it is a dynamic address.
This address is used for packet forwarding within the PDG and for packet forwarding on the Intranet/ISP.","The use of stateful or stateless is configured per W-APN, the transparent case provides at least a basic ISP service."
280,"If notifications on changes of repository data are requested, Service-Indication shall be present in the request.
If notifications on changes of filter criteria are requested, the Server-Name AVP shall be used as key to the filter criteria.
If the request contains a specific Public Service Identity matching a Wildcarded PSI, the HSS shall interpret that the subscription refers to the information associated to the Wildcarded PSI.
The Server-Name AVP shall contain the SIP URL of the AS sending the request.","If notifications on changes of repository data are requested, service indication shall be presented in the request. If notifications on changes of filter criteria are requested, the Server-Name AVP shall used. If the request contains a specific Public Service Identity matching a wildvarded PSI, the HSS shall interpret that the subscription refers to the information associated with the wildcarded PSI."
281,"Because the real time applications have the tightest connection with the lower layers, the real time scenarios are studied more in detail.
Other scenarios can be derived as combinations of these basic scenarios. Even though these scenarios are for IMS, they are applicable also for non IMS PS scenarios.
The differences between IMS and non-IMS are small in RAN level: Usually, the difference is that in non-IMS cases the IMS signalling stream is left out or replaced by non-IMS signalling stream.","As real time applications have the tightest connection with the lower layers, the real time scenarios are studied more in detail. Other scenarios can be derived as combinations of these basic scenarios."
282,"The GAA/GBA Bootstrapping procedure is initiated by the UE after a successful IMS registration and Service discovery.
 It is necessary before any service description retrieval and session initiation GBA is used to generate a master key Ks from which NAF specific keys (e.g. Ks_NAF for ME based key management) can be derived when needed.
 It is also used to authenticate the user for signaling that is not performed via the IMS core network (e.g. HTTP based service GBA is also used to generate and provision the NAF keys (e.g.  Ks_NAF for ME based key management) - which is the Long Term Key that is used in content corresponding bootstrapping transaction identifier.
 ",After successful IMS registration and service discovery the GAA/GBA Bootstraping procedure is initiated by the UE. It is necessary before any service description retrival and session initiation GBA is used to generate a master key KS.
283,"Physical channels with beacon characteristics are called beacon channels.
 The locations of the beacon channels are called beacon locations.
 The ensemble of beacon channels shall provide the beacon function, i.e. a reference power level at the beacon locations, regularly existing in each radio frame.
 Thus, beacon channels must be present in each radio frame, the only exception is when idle periods are used to support time difference measurements for location services .
 Then it may be possible that the beacon channels occur in the same frame and time slot as the idle periods.
 ","Physical channels with beacon characteristics are called beacon channels. The locations of the beacon channels aer called becon locations. The ensemble of beacon channels shall provide the beacon function. Thus, beacon channels must be present in each radio frame, with only exception when idle periods are used to support time difference measurement for location services."
284," The value is compared against the XMAC-I value computed by - RRC Message sequence number. This IE is checked to see if it is present.
 The value is used by SS to compute the XMAC-I value. The presence of this IE is dependent on IXIT statements in TS 32.
 If integrity protection is indicated to be active, this IE shall be present with the values of the sub IEs.
 ",The message authentication coe value is compared against the XMAC-I value computed by RRC message sequence number IE.
285,"Three scenarios of desensitization are identified for this combination.
 Firstly, B41 Rx is also affected due to n77 Tx leakage (dB).
 Secondly, n77 Rx is affected by B41 Tx wideband noise leakage that causes MSD = dB when 2x n77 Tx = 3x B41 Rx is satisfied.
 Thirdly, 3rd order harmonic mixing at B41 Rx would be caused by the leakage of 2nd harmonics of n77 Tx, which happens when 2x n77 Tx = 3x B41 Rx is satisfied. ","Three scenarios of desensitization are identified: (i) B41 Rx is also affected due to n77 Tx leakage, (ii) n77 Rx is affected by B41 Tx wideband noise leakage; (iii) 3rd order harmonic mixing at B41 Rx would be caused by the leakage of 2nd harmonics of n77 Tx."
286,"The concept of network assistance is based on a general query/response approach. A video client may send a query for assistance, typically prior to a buffer filling occasion.
Within the query message assistance information is provided, such as the available media rates and current media buffer status at the client. The network responses to the query with relevant information to the video client and the network may take actions to assist the video client to better QoE. The query/response procedure is repeated when the video client needs assistance.
 ","A video client may send a query for assitance, typically prior to a buffer filling occasion. With this query message assitance information is provided, such as the available media rates and current mida buffer status at the client."
287,"The UE stores the information on the new WLCP bearer and responds with WLCP Bearer Creation Response to the TWAN. For uplink packets that match bearer TFT according to same principles as for 3GPP access, the UE applies Bearer QoS and send packet on that bearer i.e. on the user plane connection ID (MAC address) associated with the bearer. A TWAN specific resource allocation/modification procedure may be executed in this step. The A TWAN specific resource allocation/modification procedure may be The TWAN selects an EPS bearer Identity, which has not yet been assigned to the UE. The TWAN then stores the EPS bearer Identity and links the dedicated bearer to the default bearer indicated by the Linked Bearer Identity (LBI). The TWAN uses the uplink packet filter (UL TFT) to determine the mapping of uplink traffic flows to the S2a bearer. The TWAN then acknowledges the S2a bearer activation to the PGW by sending a Create Bearer Response (EPS bearer Identity, TWAN Address for the user plane, TWAN TEID of the user plane) message.
 ","After storing the information on the new WLCP bearer, the UE responds with WLCP Bearer Creation Response to the TWAN. A TWAN specific resource allocatication/modification procedure selects and EPS bearer identity which has not assigned to the UE. The TWAN then stores the EPS bearer identity and links the dedicated bearer to the default bearer indicated by the Linked Bearer Identity (LBI)."
288,"Ciphering is done by producing a mask bit stream, which is then ""XORed"" bit-by-bit to the plain-text data to obtain the cipher-text data.
 First, the Initialisation Vector (IV) is concatenated with bits in order to achieve a 6bit block I This block is then encrypted by the DES algorithm using the key K.
 Output is a 6bit block I This constitutes the first 64 bits of the mask bit stream.
 If the message is longer than 64 bits, then more bits are needed.
 These are produced by encrypting I2 again by the DES algorithm using the key K.
 The output is a 6bit block I This is the next 64 bits of the mask bit stream.
 This iteration is continued until enough bits are produced.
 The unnecessary bits from the last 6bit block Ij are discarded.
 The figure below illustrates the first two mask bit generations and the two ciphered 6bit blocks.
 Data Assistance Ciphering Algorithm Deciphering is done similarly.
 The same mask bit stream is produced and these are XORed, bit-by-bit, to the cipher-text data bits.
 ","Ciphering is done by producing a mask bit stream, which is XORed to the plai-text. First, the IV is concatenated with bits in order to achieve a 6bit block. This block is then encrypted by the DES algorithm using the key K."
289,"Reason for this is that when OFDM becomes clipped by the PA, the caused IBE spikes are basically impulsive noise.
 Hence the IBE of a single slot is quite noisy and vary between the slots.
 When multiple slots are measured and average value is calculated this instantaneous variation between the slots is averaged out.
 Impact of using 10 subframe test time vs one slot test time shows the histogram of in-band emission at a single RB as offset from the limit value.
 Hence, positive values indicate violation of the in-band limit.
 Without averaging, the standard deviation of the measurement result is large, and the measurement is unreliable.
 Therefore, NR Range 1 in-band emission measurement period is specified to be 10 sub-frames.
 ","IBE of a single slot is quite noisy because when OFDM becomes clipped by the PA,  this causes IBE spkies to become impulsive noise. When multiple slots are measured and average value is calculated this instantaneous variation between the slots is averaged out."
290," If the GPSI is available, this IE shall be present.
 If present, this IE shall contain the priority of the LCS client issuing the positioning request.
 If present, this IE shall contain the quality of service requested, such as the accuracy of the positioning measurement and the response time of the positioning operation. 
 If present, this IE shall contain an indication of whether or not the Velocity of the target UE is requested.
 If present, this IE shall contain one GAD shape supported by the LCS client.
 ","If the GPSI is available then this IE shall be present. The IE contains the priority of the LCS client issuing the positioning request, the quality of service requested, an indication of whether or not the velocity of the target UE is requested, and one GAD shape supported by the LCS client."
291,"The ATSSS rules are sent to UE with a NAS message when the MA PDU Session is created or updated by the SMF, e.g. after receiving updated/new PCC rules from the PCF.
 Similarly, the N4 rules are sent to UPF when the MA PDU Session is created or updated by the SMF. The 5G QoS model for the Single-Access PDU Session is also applied to the MA PDU Session, i.e. the QoS Flow is the finest granularity of QoS differentiation in the MA PDU Session.
 One difference compared to the Single-Access PDU Session is that in a MA PDU Session there can be separate user-plane tunnels between the AN and the PSA, each one associated with a different access.
 However, the QoS Flow is not associated with specific access, i.e. it is access agnostic, so the same QoS is supported when the traffic is distributed over 3GPP and non-3GPP accesses.
 ","The ATSSS rules are sent to UE with a NAS message when the MA PDU Session is created or updated by the SMF, e.g., after receiving updated PCC rules from the PCF. Similarly, the N4 rules are sent to UPF when the MA PDU session is created or updated."
292,"This AVP contains the public identity of a user in the IMS.
 The syntax of this AVP corresponds either to a SIP URL or a TEL URL.
 Both SIP URL and TEL URL shall be in canonical form. The Server-Name AVP is of type UTF8String.
 This AVP contains a SIP-URL, used to identify a SIP server (e.g. S-CSCF name). The Server-Capabilities AVP is of type Grouped.
 This AVP contains information to assist the I-CSCF in the selection of an S-CSCF.
 ",The syntax of this AVP corresponds either to a SIP URL. Both SIP URL and TEL URL shall be in canonical form as described in the specification.
293,"As depicted, the terminal connects to the IPv4 device directly using an IPv4 PDP or EPS Bearer Context.
 Hence, the UE appears to be a standard IPv4 node to the external IPv4 network.
 This scenario does not need any specific transition support from the network.
 However, it requires both versions of IP at the UE.
 The GGSN/P-GW in this scenario may be different for the IPv6 and the IPv4 connections unless IPv4/v6 PDP or EPS Bearer Contexts are used.
 ","The terminal connects to the IPV4 device directly using an IPv4 PDP. Hence, the UE appears to be a standard IPv4 node to the external IPv4 network."
294,"This information element is used to allow service logic running in an Anchor MSC to mute a VGCS talker even when the talker is served on a Relay MSC.
 The IE is used to build a GCC message that provides a mechanism to induce the VGCS talker terminal to mute/unmute the downlink at the Anchor MSC.
 Emergency Mode Reset Command is used between the Relay MSC and the Anchor MSC.
 When the VGCS/ VBS calling service subscriber is in the Relay MSC area the MAP_SEND_GROUP_CALL_END_SIGNAL indicates that at least the downlink channel in the originating cell is established.
 ",The IE is used to build a GCC message that provides a mechanism to induce the VGCS talker terminal to mute/unmute the downlink at the Anchor MSC.
295,"Downlink and uplink transmissions are organized into frames with 10ms duration, consisting of 10 subframes, 1ms each.
 Each frame is divided into 2 equally-sized half-frames of 5 subframes each. Other than the first OFDM symbol in every ms, all OFDM symbols within ms have the same size.
 SIB4 contains information relevant only for inter-frequency cell re-selections i.e. information about other NR frequencies and inter-frequency neighbouring cells relevant for cell re-selection.
 It includes cell re-selection parameters common for a frequency as well as cell specific re-selection parameters.
 SIB4 is mapped to BCCH logical channel and is either broadcast periodically on DL-SCH or broadcast on-demand on DL-SCH.","Downlink and uplink transmissions are organized into frames with 10ms duration, consisting of 10 subframes, 1 ms each. Each frame is divided into 2 equally-sized half-frames of 5 subframes each."
296,"All data variables in this specification are presented with the most significant substring on the left hand side and the least significant substring on the right hand side.
 A substring may be a bit, byte or other arbitrary length bitstring.
 Where a variable is broken down into a number of substrings, the leftmost (most significant) substring is numbered 0, the next most significant is numbered 1, and so on through to the least. 
 MBMS introduces the concept of a point-to-multipoint service into a 3GPP system.
 A requirement of a MBMS User Service is to be able to securely transmit data to a given set of users.
 ",All data variables in the specification are presented with the most significant substring on the left hand side and the least significant substring on the right hand side. MBMS introduces the concept of a point-to-multipoint service into a 3GPP system.
297,"Device maintenance may happen in parallel to the actual production process and other communication services performed at the device side without any negative impact on these Table A.
Service performance requirements for remote access and Use Characteristic parameter Influence quantity Transmission of non-deterministic messages in parallel to other interactions. ",Device maintenance may happen in parallel to the actual production process and other communication services performed at the device side without any negative impact. Service performance requirements for remote access and use characteristic paramter influence quantity transmission of non-deterministic messages.
298,"Each of these service elements can contain an ""active"" attribute that indicates whether the service is activated or not.
 When the ""active"" attribute is absent on a service element, it indicates that the service is activated.
 Elements and attributes from different namespaces can be present as well.
 Services may also include capability elements that are read-only.
 These elements indicate which capabilities the network has provisioned for a user XCAP requires application usages to fulfil a number of steps in the definition of such application usage.
 ","When the active attribute is absent on a service element, it indicates that the service is activated. Elements and attributes from different namespaces can be present as well."
299," The Multicast traffic handling affects the GGSN by the introduction of the IP-Multicast proxy and the support for an Inter-Router Multicast protocol and a host-router multicast protocol.
 If the protocol configuration for handling Multicast traffic (control plane) is applied for SGi (i.e EPC based packet domain) the P-GW has the functionality of GGSN and SGi corresponds to the Gi in
 Protocol configuration for IP-Multicast handling (control plane) networks based on the point-to-point protocol (PPP), as well as with networks based on any protocol supported by PPP through one of its Network Control Protocols (NCPs).
 All protocols currently supported by PPP NCPs are interworking by means of tunnelled PPP, by e.g. the Layer Two Tunnelling The interworking point is at the Gi reference point.
 The GGSN for interworking with the ISP/PDN is the access point of the Packet Domain.
 The GGSN will either terminate the PPP connection towards the MS or may further relay PPP frames to the PDN.
 ",Multicast traffic handling affects the GGSN by the introduction of the IP-Multicast proxy and the support for an Inter-Router Multicast Protocol and a host-router multicast protoocl. All protocols supported by PPP NCPs are interworking by means of tunnelled PPP.
300," The ""IMMEDIATE ASSIGNMENT EXTENDED"" Message contains assignment information for two mobiles.
 If the establishment cause is identical for the two mobile stations, the counter shall be incremented by two.
 Otherwise the affected counters shall be incremented by one NOTE: System implementation will allow the establishments causes of PS *** Att IMM ASS Poc can be incorporated in this measurement E.
 ","If the established cause is identical for the two mobile stations, the counter shall be incremented by two otherwise the affected counters shall be incremented by one."
301,"The CAT service is an operator specific service by which an operator enables the subscriber to customize the media which is played to the calling party during alerting of the called party.
 The media can consist of favourable songs, multi-media clips or other customized alerting tones.
 The service user is able to subscribe to the CAT service, activate (or de activate) the service, and update the settings, e.g., to change by configuration the active CAT media.
 The media can consist of favourable songs, multimedia clips or other customized alerting tones.
 The CAT subscriber is able to refine the CAT media selection behaviour with location, the identity of the calling and called party.
 The CAT service is able to select the appropriate CAT media according to the rules CAT is a terminating network service, but can also have an originating network functional component.
 That is, CAT media can be selected on behalf of the called subscriber for playback to the calling party, but the calling (IMS) subscriber can also subscribe to and activate the CAT service.
 In such a case, the CAT media selected by the calling party takes precedence for playback purposes over that selected by the called party.
 Whether or The start of playback of the selected CAT media toward the calling party occurs some time following the initiation of a session, but prior to session answer.
 When the called party answers, playback of the CAT media either stops or continues to play during the conversation, depending on operator or user preferences.
 When the CAT media is playing, the calling party is able to stop.
 ",The CAT service is an operator specific service by which an operator enables the subscriber to customize the media which is played to the calling party during alterting of the called party. CAT service should not negatively affect the conversation between calling and the caller.
302,"The O&M may configure the UTRAN to collect and report volume reports on a per cell.
 The structure is based on the principle that the layers and planes are logically independent of each other.
 Therefore, as and when required, the standardisation body can easily alter protocol stacks and planes to fit future requirements General Protocol Model for UTRAN Interfaces. 
 The Protocol Structure consists of two main layers, Radio Network Layer and Transport Network Layer.
 ",The Q&M may configure the UTRAN to collect and report volume reports on a per cell and described detail. The structure is based on the principle that the layers and planes are logicially indenpdent of each other.
303,"Action command Extended Error Report (+CEER) does not have any subparameters, and it returns the cause of the latest call setup failure.
 This information may be the textual presentation of the other information defined by the TA manufacturer.
 This clause describes GSM/UMTS network related commands, which are not covered in call control clause of the present document.
 Commands include GSM/UMTS supplementary service handling, MSISDN query, MT and network facility locking, and network registration information query.
 Action command returns the MSISDNs related to the subscriber (this information can be stored in the SIM/UICC or in the MT).
 When storing information in the SIM/UICC, if the currently selected card slot contains a SIM card or a UICC with an active GSM application, the information is stored in the EFMSISDN under DFTelecom.
 If the currently selected card slot contains a UICC with an active USIM application, the information is stored in the EFMSISDN under ADFUSIM).
 If subscriber has different MSISDN for different services, each MSISDN is returned on a separate line.
 ","Action command extend error report does not have any subparameters, and it returns the cause of the latest call setup failure. This information may be the textual presentation of the other information defined by the TA."
304,"The Sequence Number shall be unique for each outstanding request message sourced from the same IP/UDP endpoint.
 A GSN or RNC may have several outstanding requests while waiting for responses. The TRESPONSE timer shall be started when a signalling request message (for which a response has been defined) is sent.
 A signalling message request or response has probably been lost if a response has not been received before the TRESPONSE timer expires.
 The request is then retransmitted if the total number of request attempts is less than N3REQUESTS times.
 The timer shall be implemented in the control plane application as well as user plane application for Echo Request / Echo Response.
 The wait time for a response (TRESPONSE timer value) and the number of retries (NREQUESTS) shall be configurable per procedure.
 ",The sequence number shall be unique for each outstanding request message sourced from the same IP/UDP endpoint. A signaling message request or response has probably been lost if a response has not been received before the timer expires.
305,"If a user chooses to access the Internet directly using the local IP network, no service selection information is passed to the PLMN.
 In all other cases, where WLAN 3GPP IP Access is desired, the service selection information shall contain the name of the W-APN to which access is requested.
 The 3GPP AAA Server in the Home network shall verify the users subscription to the indicated W-APN against the subscriber profile retrieved from HSS.
 The 3GPP AAA Server selects a W-APN based on the requested W-APN. The service request shall be indicated by a tunnel establishment request from the WLAN UE to the PDG.
 The PDG shall then seek authentication/authorisation from the 3GPP AAA Proxy or Server. The results of the authorisation decision shall be communicated to the Visited Network.
 ","If a user chooses to access the Internet directly using the local IP network, no service selection information is passed to the PLMN. In other cases, where WLAN 3GPP IP Access is desired, the service selection information shall contain the name of the W-APN to which access is requested."
306,"The total number of RBGs for downlink system bandwidth of is given by where of the RBGs are of size P.
 The bitmap is of size bits with one bitmap bit per RBG such that each RBG is addressable.
 The RBGs shall be indexed in the order of increasing frequency and non-increasing RBG sizes starting at the lowest frequency.
 The order of RBG to bitmap bit mapping is in such way that RBG 0 to RBG are mapped to MSB to LSB of the bitmap.
 The RBG is allocated to the UE if the corresponding bit value in the bitmap is 1.
 ","The RBGs shall be indexed in the order of increasing frequency and non-increasing RBG sizes starting at the lowest frequency and the order of RBG to bitmap bit mapping is in such way that RBG 0 to RBG are mapped to MSB to LSB of the bitmap.
"
307,"CT10 ON condition towards MT is a basic requirement to allow speech/data transition because of a correct tone handling.
 The DCD identifies the call direction from the calling to the called station according to ITU-T T.30 phase ""A"". The DCD is derived from the evaluation of the behaviour of the mobile Fax machine.
 No later than 3 sec after connecting the Fax apparatus to the line the FA/MT is able to determine the DCD.
 If a CNG tone or nothing is detected by the FA/MT the mobile Fax station is the calling station, if a CED tone or a BCS signal is detected by the FA/MT the mobile Fax station is the called station.
 The FA/MT indicates this towards the MT by means of CT105: CT105 OFF condition indicates ""mobile terminated"", CT105 ON condition indicates ""mobile originated"".","CT10 ON is required to allow speech and data transmission. DCD is derived from the behavior evaluation of the mobile Fax machine and it identifies the call direction between the calling and the called based on ITU-T T.30 phase ""A"". If FA/MT detects a CNG tone or nothing then the calling station is the mobile Fax station. Otherwise if it detects a CED tone or a BCS signal the mobile Fax Station is the called station. "
308,"PGW may include its Load Information towards peer SGW. In either SGW initiated messages (e.g. Downlink Data Notification) or response messages to MME/SGSN (e.g. Create Session Response) SGW may include its Load Information towards peer MME/SGSN. The transfer of the load Information shall not add significant additional load to each peer node.
 ",PGW may include Load information towards peer SGW. Initiated or response messages from SGW to MME/SGSN may include load information towards peer MME/SGSN.
309,"AccessIds in numerical format shall be encoded as character string.
The AccessId be represented by Unicode characters encoded as UTF-8. The SecondaryAccessId leaf represents a secondary access network. 
The SecondaryAccessId contains an identifier for a specific radio access network.
 Only HESSID for WLAN radio access network is contained in this leaf.
 The SecondaryAccessId leaf may only be present when the corresponding AccessId leaf for a WLAN radio access network is present.
 The format of the The AccessNetworkPriority leaf represents an access technology priority.
 ",AccessId is represented using Unicode characters (UTF-8) and encoded in character strings. The SecondaryAccessId leaf represents a secondary access network and contains an identifier for a specific radio access network. The SecondaryAccessId leaf may only be present when the corresponding AccessId leaf for a WLAN radio access network is present. The format of the The AccessNetworkPriority leaf represents an access technology priority 
310,"The MN NAI identifies the UE for whom the message is being sent.
 The Lifetime field must be set to a nonzero value in the case of a registration.
 Access Technology Type is set to indicate 3GPP access to EPS.
 Handover Indication option is set to indicate attachment over a new interface as no Handover indication is received from the MME.
 The APN may be necessary to differentiate the intended PDN from the other PDNs supported by the same PDN GW.
 The Serving GW includes the EPS bearer identity of the default bearer received from the MME if multiple PDN connections to the same APN are supported.
 The optional Additional Parameters may contain information, for example, protocol configuration options.
 The UE Address Info IE is used to request an IPv6 prefix, IPv4 address, or both IPv4 address and IPv6 prefix.
 ","The MN NAI identifies the UE for whom the message is being sent and the Lifetime field must be set to a nonzero value when registering. Access Technology Type is set to indicate 3GPP access to EPS. Handover Indication option is set to indicate attachment over a new interface when no Handover indication is received from the MME. The APN may be necessary to differentiate the intended PDN from the other PDNs supported by the same PDN GW. The Serving GW includes the EPS bearer identity of the default bearer received from the MME if multiple PDN connections to the same APN are supported. The optional Additional Parameters may contain protocol configuration options. The UE Address Info IE is used to request an IPv6 prefix, IPv4 address, or both IPv4 address and IPv6 prefix."
311," Multiple SIM/USIM applications are stored on the MT on a single UICC.
 Each application (that may be associated with its own unique user) has its own unique SIM/USIM associated with it.
 It allows multiple USIMs stored to be stored on a UICC but they cannot be all active at the same time.
 ",Multiple SIM/USIM applications are stored on the MT on a single UICC. Each application (that may be associated with its own unique user) has its own unique SIM/USIM associated with it.
312,"The interior node is mandatory if the UE supports one or more IMS conferencing capabilities.
 Support for a UE is defined by the related roles as defined by the related IMS conferencing service. One node is normally used.
 The Name leaf is a name for the conferencing settings.
 The Ext is an interior node for where the vendor specific information about the IMS conferencing management is being placed (vendor meaning application vendor, device vendor etc.).
 Usually the vendor extension is identified by vendor specific name under the ext node.
 The tree structure under the vendor identified is not defined and can therefore include one or more.
 ","The interior node is mandatory if the UE supports one or more IMS conferencing capabilities. The Name leaf is a name for the conferencing settings. 
 The Ext is an interior node for where the vendor specific information about the IMS conferencing management is being placed (vendor meaning application vendor, device vendor etc.). The tree structure under the vendor identified is not defined and can therefore include one or more.
 "
313,"The MCPTT client may indicate to the MCPTT user that the LMR user has been notified, e.g. by producing ringback audio. Once the call has been accepted by the called user, the IWF sends an IWF private call response to the MCPTT server.
 The IWF private call response indicates that the IWF does support one of the requested media. The MCPTT server forwards the MCPTT private call response to the MCPTT client.
 The MCPTT client may indicate to the MCPTT user that the call is connected, e.g. by stopping the ringback audio 1. The MCPTT client has successfully established media plane for communication to the IWF.
 ","The MCPTT client may indicate to the MCPTT user that the LMR user has been notified. IWF sends an IWF private call response to the MCPTT server, when the call is accepted. The IWF private call response indicates that the IWF does support one of the requested media. The MCPTT server forwards the MCPTT private call response to the MCPTT client. The MCPTT client may indicate to the MCPTT user that the call is connected
 "
314," In OpenID an association session is established between a Relying Party (RP) and the OpenID Provider.
 A shared secret is established, which is used to verify the subsequent protocol messages.
 The association session is initiated by a direct request from a RP to an OP using the OP Endpoint URL. The establishment of an association session between the RP and the OP Endpoint URL is optional.
 It allows optimization of the traffic processing. The RP sends an Association Session Request to the OP Endpoint URL.
 ","In OpenID an association session is established between a Relying Party (RP) and the OpenID Provider. A shared secret is established, which is used to verify the subsequent protocol messages. The association session is initiated by a direct request from a RP to an OP using the OP Endpoint URL. The establishment of an association session between the RP and the OP Endpoint URL is optional. It allows optimization of the traffic processing. The RP sends an Association Session Request to the OP Endpoint URL."
315,"Like other physical channels when the data is transferred then it needs to be on a certain power for reaching to the destination.
 High transmit power can cause interference and fast UE battery drain, in opposite way with extreme low power may cause for undelivered data to the network.
 So, transmit power needs to be controlled But how the UE will be aware of the power control mechanism? The answer is serving cell itself.
 It will instruct the UE about the transmit power through PDCCH.
 The serving cell sends scheduling information to the UE over PDCCH, then the UE starts to transmit user data on PUSCH.
 The UE already knows which subframe, MCS and how many resource blocks will be used with the instruction.
 ","High transmit power can cause interference and fast UE battery drain. Extreme low power may cause for undelivered data to the network.
Transmit power needs to be controlled by the serving cell itself. It will instruct the UE about the transmit power through PDCCH.
 The serving cell sends scheduling information to the UE over PDCCH, then the UE starts to transmit user data on PUSCH.
 The UE already knows which subframe, MCS and how many resource blocks will be used with the instruction.
 "
316,"When present, the TWAN Operator Name shall indicate the identifier of the TWAN. The LAII flag in octet 5 indicates whether the Logical Access ID information is present in the TWAN Identifier IE.
 The Logical Access ID is information and the Circuit-ID information shall be present if the LAII IETF RFC 3046 .
 The Relay Identity Type indicates the type of the Relay Identity as described in Table 0.
 The Relay Identity Length indicates the length of the Relay Identity.
 In case the Relay Identity Type indicates an IP address, the length indicates if it is IPv4 or IPv6 address of the Relay.
 The length is 4 octets for IPv4 and 16 octets for IPv If the Relay Identity type is set to 1 (i.e.an FQDN), it is encoded as described in section of IETF RFC 1035 but excluding the trailing zero byte.
 The Circuit-ID length indicates the length of the Circuit-ID.
 The Circuit-ID is as defined in IETF RFC 3046 , it is encoded as an Octetstring and provided by the Relay.
 ","The TWAN Operator Name indicates the identifier of the TWAN when present. The LAII flag in octet 5 indicates whether the Logical Access ID information is present in the TWAN Identifier IE. The Logical Access ID is information and the Circuit-ID information shall be present if the LAII IETF RFC 3046. The Relay Identity Type indicates the type of the Relay Identity. The Relay Identity Length indicates the length of the Relay Identity.  In case the Relay Identity Type indicates an IP address, the length indicates if it is IPv4 or IPv6 address of the Relay. The length is 4 octets for IPv4 and 16 octets for IPv6. When the Relay Identity type is set to 1 (i.e. an FQDN), it is encoded as described in section of IETF RFC 1035 but excluding the trailing zero byte. The Circuit-ID length indicates the length of the Circuit-ID. The Circuit-ID is as defined in IETF RFC 3046 , it is encoded as an Octetstring and provided by the Relay  
 "
317," Information elements are shown as Mandatory (M), Conditional (C) or Optional (O).
 A mandatory information element shall always be present.
 A conditional information element shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent.
 An optional element may be present or absent, at the discretion of the application at the sending entity.","Information elements could be either Mandatory (M), Conditional (C) or Optional (O). Mandatory information elements are always present while conditional ones are present only if certain conditions are satisfied. An optional element may be present or absent, at the discretion of the application at the sending entity.
 "
318,"Multiple media components may be used in the same session to send multiple media types.
 For the purposes of the present document, the abbreviations given in present document takes precedence over the definition of the same CRS Customized Ringing Signal.
 The CRS service is an operator specific service by which an operator enables the subscriber to customize the media which is played to the called party during alerting of the called party.
 The media can consist of music voice, text, video or other customized ringing signals.
 The service user is able to subscribe to the CRS service, activate (or de activate) the service, and update the settings, e.g., to change by configuration the active CRS media.
 The media can consist of favourable songs, multimedia clips or other customized ring signals.
 The CRS subscriber is able to refine the CRS media selection behaviour with location, the identity of the calling and called party.
 The CRS service is able to select the appropriate CRS media according to the rules CRS is an originating network service, but can also have a terminating network functional component.
 That is, CRS media can be selected on behalf of the calling subscriber, but the called (IMS) subscriber can also subscribe to and activate the CRS service.
 ","Multmedia components can be used in the same session to send multiple media types. The Customized Ringing Signal (CRS) service is an operator specific service where an operator enables the subscriber to customize the media which is played to the called party during alerting of the called party. The media could be music voice, text, video or other customized ringing signals. The service user can subscribe to the CRS service, activate (or de activate) the service, and update the settings. The media could be favourable songs, multimedia clips or other customized ring signals. Also, the CRS subscriber is able to refine the CRS media selection behaviour based om location and the identity of the calling and called party. The CRS service is able to select the appropriate CRS media according to the rules CRS is an originating network service, but can also have a terminating network functional component. Thus, CRS media can be selected on behalf of the calling subscriber, but the called IMS subscriber can also subscribe to and activate the CRS service."
319,"PFI (7 bit field) This field contains the PFI parameter identifying a Packet Flow Context relating to the resource request specified in the Channel Request Description IE.
 The PFI parameter is encoded as the contents of the PFI if the network supports packet flow context procedures and if a Channel Request Description IE is included in the message.
 If this field is included but the Channel Request Description IE is omitted, this field shall be RB Id (5 bit field) bearer for which the downlink data transfer on SFACCH is acknowledged.
 This field is not included when the EGPRS PACKET DOWNLINK ACK/NACK message is sent on DBPSCH.
 This field is encoded as a binary number with range Timeslot Number (3 bit field). It contains the timeslot number of the timeslot on which the corresponding RRBP was received.
 ","PFI is  a 7 bit field that contains the PFI parameter identifying a Packet Flow Context relating to the resource request specified in the Channel Request Description IE. The PFI parameter is encoded as per the contents of the PFI if the network supports packet flow context procedures and if a Channel Request Description IE is included in the message. If this field is included but the Channel Request Description IE is omitted, this field shall be RB Id (5 bit field) bearer for which the downlink data transfer on SFACCH is acknowledged. This field is not included when the EGPRS PACKET DOWNLINK ACK/NACK message is sent on DBPSCH. This field is encoded as a binary number with range Timeslot Number, a 3 bit field) and contains the timeslot number of the timeslot on which the corresponding RRBP was received.
 "
320,"Many of the possible leakage points arise from the initial provisioning process.
 This solution involves a key exchange protocol being run between the UICC and the home network HSS, in order to create a newly agreed Ki value to replace the existing one.
 Elliptic Curve Diffie Hellman would be a suitable key exchange algorithm Exposing the HSS to update may in itself introduce new risks, and so should be handled with great care.
 One might consider running the key exchange protocol with a proxy for the HSS rather than with the HSS directly.
 However, the benefits of doing this are not entirely clear.
 ","Leakage points may arise from the provisioning process. A solution involves a key exchange protocol being run between the UICC and the home network HSS, in order to create a newly agreed Ki value to replace the existing one. HSS updates may in itself introduce new risks, and so should be handled with great care.
 "
321,"The peak EVM is the peak error deviation within a burst, measured at each symbol interval averaged over at least 200 bursts.
 The bursts shall have a minimum distance in time of 7 idle timeslots between them.
 The peak EVM values are acquired during the useful part of the burst, excluding tail bits 5) The 95: th percentile EVM shall be measured and calculated.
 The 95: th percentile EVM is the point where 95% of the individual EVM, measured at each symbol interval, is below that point.
 That is, only 5% of the symbols are allowed to have an EVM exceeding the 95: th-percentile point.
 The EVM values are acquired during the useful part of the burst excluding tail bits, over 200 bursts.
 ","The peak EVM is the peak error deviation within a burst, measured at each symbol interval averaged over at least 200 bursts. The bursts should have a minimum distance in time of 7 idle timeslots between them. The peak EVM values are acquired during the useful part of the burst, excluding tail bits. The 95th percentile EVM shall be measured and calculated and is the point where 95% of the individual EVM, measured at each symbol interval, is below that point.  That is, only 5% of the symbols are allowed to have an EVM exceeding the 95th-percentile point. The EVM values are acquired during the useful part of the burst excluding tail bits, over 200 bursts.
 "
322,"If all serving nodes successfully answer to the T-ADS request from the HSS, the HSS shall provide the most recent IMS Voice over PS Sessions support indication as indicated by the serving nodes 4b.
 If CSRN is requested but roaming number retrieval from the MSC/VLR fails, the HSS shall include an empty CSRN element in the xml document returned to the AS.
 In addition, if MTRR is applicable (see The HSS shall include the data pertinent to the requested Data Reference in the User-Data AVP.
 The HSS shall set the Result-Code to DIAMETER_SUCCESS.
 This includes cases where the data is not available to the HSS.
 The pertinent data included shall refer to the received IMPU/MSISDN and Private Identity (if present) NOTE 4: Data referred to a Private Identity (e.g. IMS Private User Identity) implies that only the data (e.g.Location Information) specific for that Private Identity is included, regardless of the type of User Identity received.","If all serving nodes successfully answer to the T-ADS request from the HSS, the HSS shall provide the most recent IMS Voice over PS Sessions support indication as indicated by the serving nodes 4b. If CSRN is requested but roaming number retrieval from the MSC/VLR fails, the HSS should include an empty CSRN element in the XML document returned to the AS. In addition, if MTRR is applicable, the HSS shall include the data pertinent to the requested Data Reference in the User-Data AVP. The HSS shall set the Result-Code to DIAMETER_SUCCESS which includes cases where the data is not available to the HSS. The pertinent data included shall refer to the received IMPU/MSISDN and Private Identity (if present)."
323,"Thus once the CTS-MS has determined the correct setting of these first counters the CTS-MS is able to attach to the current serving CTS-FP.
 In addition during CTS-MS attachment, the CTS-FP sends to the CTS-MS the remaining counters for SACCH and TCH frames.
 Then, all processes of the CTS-MS are synchronized to the current serving CTS-FP The CTS-MS times its transmissions to the CTS-FP in line with those received from the CTS-FP.
 The timing advance parameter is set to zero for Additionally, the CTS-FP may be assisted by a CTS-MS to adjust its frequency source.
 When required by the CTS-FP, the CTS-MS estimates if possible and reports the Observed Frequency Offset of the CTS-FP with a specified BTS.
 ","During CTS-MS attachment, the CTS-FP sends to the CTS-MS the remaining counters for SACCH and TCH frames. Then, all processes of the CTS-MS are synchronized to the current serving CTS-FP. The CTS-MS times its transmissions to the CTS-FP in line with those received from the CTS-FP.
The timing advance parameter is set to zero for Additionally, the CTS-FP may be assisted by a CTS-MS to adjust its frequency source. When required by the CTS-FP, the CTS-MS estimates if possible and reports the Observed Frequency Offset of the CTS-FP with a specified BTS.
 "
324,"CT105 and CT133 are assigned to the same connector pin on both the standard 25 pin pin connector.
 When this pin is used for CT133 then on the MT side of the interface CT 105 is treated as being always in the ON condition.
 SB towards the IWF shall therefore also always be ON.
 Similarly, when this pin is being used for CT105 then on the MT side of the interface CT condition.
 X towards the IWF shall therefore also always be ON.
 As circuit 133 is used only in duplex operation and circuit 105 is used only in half duplex operation (which is not supported by GSM or UMTS) there should be no conflict.
 ","CT105 and CT133 are assigned to the same connector pin on both the standard 25 pin pin connector. When this pin is used for CT133 then on the MT side of the interface CT 105 is treated as being always in the ON condition. SB towards the IWF should always be ON. Similarly, when this pin is being used for CT105 then on the MT side of the interface CT condition. X towards the IWF shall therefore also always be ON.
 As circuit 133 is used only in duplex operation and circuit 105 is used only in half duplex operation there should be no conflict.
 "
325,"Invoke with explicit indication An Invoke component may be segmented into several Invoke components sent in acknowledged mode.
 Each component contains at the MAP level an indication of whether or not subsequent components will follow.
 The receiving node terminates the dialogue when the last component is received.
 The MAP user parameter shall be split so that each segment is compatible with the type defined for the parameter of the invoke of the associated operation.
 A Result (last) component may be segmented into several Result (last) components sent in acknowledged mode where a new (empty) Invoke component serves as an acknowledgment.","An Invoke component may be segmented into several Invoke components sent in acknowledged mode. Each component contains at the MAP level an indication of whether or not subsequent components will follow. The receiving node terminates the dialogue when the last component is received. The MAP user parameter shall be split so that each segment is compatible with the type defined for the parameter of the invoke of the associated operation. A Result (last) component may be segmented into several Result (last) components sent in acknowledged mode where a new (empty) Invoke component serves as an acknowledgment.
 "
326,"The ""Type"" element of the OMA DM generic alert message shall be set to ""urn: oma: at: ext-3gpp-andsf:: provision-disc-info"". The ANDSF server shall include at least one of the leaves (i.e. HESSID SSID or BSSID) to be present in a single instance of WLAN_Location interior node of the AccessNetworkArea of the DiscoveryInformation node. The MO has a node indicating the position of the UE.
 The trigger for updating the value of this node is that the location information it contains is no longer valid (i.e. the UE has changed its position) or some other manufacturer specific trigger.
 The update of the information The ISRP information consists of a set of one or more ISRP rules.
 Each ISRP rule contains indication on traffic distribution for UEs that are configured for IFOM, MAPCON or non-seamless WLAN offload Each ISRP rule has a PLMN leaf and an optional Roaming leaf.
 Roaming and PLMN leaves are used by the UE to determine if an ISRP rule is applied.
 ","The ""Type"" element of the OMA DM generic alert message shall be set to ""urn: oma: at: ext-3gpp-andsf:: provision-disc-info"". The ANDSF server shall include at least one of the leaves (that is, HESSID SSID or BSSID) to be present in a single instance of WLAN_Location interior node of the AccessNetworkArea of the DiscoveryInformation node. The MO has a node indicating the position of the UE. The trigger for updating the value of this node is that the location information it contains is no longer valid (that is, the UE has changed its position) or some other manufacturer specific trigger.
The ISRP information consists of a set of one or more ISRP rules. Each ISRP rule contains indication on traffic distribution for UEs that are configured for IFOM, MAPCON or non-seamless WLAN offload and each ISRP rule has a PLMN leaf and an optional Roaming leaf. Roaming and PLMN leaves are used by the UE to determine if an ISRP rule is applied.
 "
327,"The Remote UE communicates with the ProSe UE-to-Network Relay over PC5 reference point.
The Prose UE-to-Network Relay uses layer-3 packet forwarding - Exchange of control information between ProSe-UEs over PC5 reference point, e.g. for UE-to-Network Relay Discovery and Group Member.
Exchange of ProSe control information between another ProSe-enabled UE and the ProSe Function over PC3 reference point.
In the ProSe UE-to Network Relay case the Remote UE will send this control information over PC5 user plane to be relayed over the LTE-Uu interface towards the - Configuration of parameters (e.g. including IP addresses, ProSe Layer 2 Group IDs, Group security material, radio resource parameters).
 ","The Remote UE communicates with the ProSe UE-to-Network Relay over PC5 reference point. The Prose UE-to-Network Relay uses layer-3 packet forwarding, that is, Exchange of control information between ProSe-UEs over PC5 reference point, e.g. for UE-to-Network Relay Discovery and Group Member. In the ProSe UE-to Network Relay case, the Remote UE will send this control information over PC5 user plane to be relayed over the LTE-Uu interface towards the configuration of parameters (such as IP addresses, ProSe Layer 2 Group IDs, Group security material, radio resource parameters).
 "
328," All data rates which are used in clause 8 Performance requirement testing shall be used in verification testing.
 This test is performed by feeding measurement signal with known BLER to the input of the receiver.
 Locations of the erroneous blocks shall be randomly distributed within a frame.
 Erroneous blocks shall be inserted into the UL signal as shown in figure BLER insertion to the output data generated by the RF signal source.
 Measurement shall be repeated for each data rate.
 ","All data rates which are used in clause 8, Performance requirement testing, should be used in verification testing. This test is performed by feeding measurement signal with known BLER to the input of the receiver. The locations of the erroneous blocks should be randomly distributed within a frame.  Erroneous blocks shall be inserted into the UL signal as shown in figure BLER insertion to the output data generated by the RF signal source. 
 "
329,"The MExE user downloads whichever services he desires from the remote servers, and installs, provisions and configures them on the MExE client.
 These services execute directly on the handset without necessarily relying on servers to support the service.
 An example of such a service would be a game MExE handset to MExE handset services MExE handsets may wish to establish connections with each other to provide, receive and use interactive services.
 This direct MExE client to MExE client interaction of MExE services and any combination of the preceding scenarios may have been used to download services to the MExE client.
 These services may execute directly on the handset, without necessarily relying on servers to support the service.","The MExE user downloads whichever services he desires from the remote servers, and installs, provisions and configures them on the MExE client.
 These services execute directly on the handset without necessarily relying on servers to support the service. MExE handsets may wish to establish connections with each other to provide, receive and use interactive services. This direct MExE client to MExE client interaction of MExE services and any combination of the preceding scenarios may have been used to download services to the MExE client. These services may execute directly on the handset, without necessarily relying on servers to support the service.
 "
330,"Therefore, no physical channel (HS-DPCCH) is If the E-DCH is applicable, there can only be one E-DCH TrCH and no other TrCH in an E-DCH CCTrCH per activated uplink frequency.
 For FDD, the E-DCH CCTrCH is carried on E-DPDCH(s) physical channel(s).
 E-DCH TFCI and E-DCH HARQ information are carried on an E-DPCCH physical channel.
 For FDD, a single bit is transmitted on the E-DPCCH physical channel per activated uplink frequency to indicate whether the UE could use more resources or not.
 For TDD, the E-DCH is carried on the E-PUCH physical channel(s).
 ","If the E-DCH is applicable, there can only be one E-DCH TrCH and no other TrCH in an E-DCH CCTrCH per activated uplink frequency. For FDD, the E-DCH CCTrCH is carried on E-DPDCH(s) physical channel(s). E-DCH TFCI and E-DCH HARQ information are carried on an E-DPCCH physical channel. For FDD, a single bit is transmitted on the E-DPCCH physical channel per activated uplink frequency to indicate whether the UE could use more resources or not. For TDD, the E-DCH is carried on the E-PUCH physical channel(s).
 "
331,"A bootstrapping session established using a bootstrapping procedure (cf clause 4 and annex A) is used between a UE and a NAF.
 The BSF provides to the NAF a NAF specific key material (Ks_NAF or Ks_ext_NAF and optionally Ks_int_NAF) which is derived from the key material (Ks).
 The NAF uses this key to authenticate and optionally secure (i.e. integrity protect and encrypt) the communications between it and the UE.
 The BSF will also provide the NAF the expiration time of the bootstrapping session.","A bootstrapping session between a UE and a NAF is established using a bootstrapping procedure. The BSF provides to the NAF a NAF specific key material (Ks_NAF or Ks_ext_NAF and optionally Ks_int_NAF) which is derived from the key material (Ks). The NAF uses this key to authenticate and optionally secure (that is, integrity protect and encrypt) the communications between it and the UE. The BSF will also provide the NAF the expiration time of the bootstrapping session.
 "
332,"However the UE is not required to monitor every PO, but only the POs that belong to the Paging Transmission Window (PTW) Extended DRX in Idle mode The eDRX parameter in Idle mode values, i.e. timer values for TeDRX and TPTW are negotiated and configured during ATTACH and RAU procedure.
 Timer TeDRX is (re-)started when upper layers indicate successful completion of the ATTACH/RAU procedure, including eDRX parameters in Idle mode.
 When timer TeDRX expires, the UE wakes-up from sleep, it checks the MIB for any system information changes and it starts monitoring the paging occasions in the PS DRX in Idle mode.
 When timer TeDRX expires it is re started, and timer TPTW is started.
 When timer TPTW expires the UE stops monitoring paging occasions in the PS DRX in Idle mode.
 The timer TeDRX and TPTW do not stop/reset when the UE transitions from Idle to Connected or transitions from Connected to Idle.
 The timers TeDRX and TPTW are stopped if running, when upper layer indicates that the eDRX parameters in Idle mode are not included in the ATTACH/RAU complete.
 The timers TeDRX and TPTW are reset when upper layer indicates that a new value is configured in ATTACH/RAU for timer T331 in RRC .
 The value of TPTW is signaled in The retrievable configurations feature allows the UE to store configurations together with an identity.
 When the network invokes a retrievable configuration, it needs to signal only its identity.
 A retrievable configuration can be signalled to a UE in any state except for idle.
 ","The UE is not required to monitor every PO; only the POs that belong to the Paging Transmission Window (PTW). The eDRX parameter in Idle mode values, i.e. timer values for TeDRX and TPTW, are negotiated and configured during ATTACH and RAU procedure. Timer TeDRX is (re-)started when upper layers indicate successful completion of the ATTACH/RAU procedure, including eDRX parameters in Idle mode. When timer TeDRX expires, the UE wakes-up from sleep, it checks the MIB for any system information changes and it starts monitoring the paging occasions in the PS DRX in Idle mode. When timer TeDRX expires it is re started, and timer TPTW is started. When timer TPTW expires the UE stops monitoring paging occasions in the PS DRX in Idle mode. The timer TeDRX and TPTW do not stop/reset when the UE transitions from Idle to Connected or transitions from Connected to Idle. The timers TeDRX and TPTW are stopped if running, when upper layer indicates that the eDRX parameters in Idle mode are not included in the ATTACH/RAU complete. The timers TeDRX and TPTW are reset when upper layer indicates that a new value is configured in ATTACH/RAU for timer T331 in RRC . The value of TPTW is signaled in The retrievable configurations feature allows the UE to store configurations together with an identity.
 When the network invokes a retrievable configuration, it needs to signal only its identity. A retrievable configuration can be signalled to a UE in any state except for idle.
 "
333,"The UTRAN may repeat the MCCH information following a scheduled transmission in order to improve reliability.
 The MCCH schedule will be common for all services The entire MCCH information will be transmitted periodically based on a ""repetition period"".
 The ""modification period"" will be defined as an integer multiple of the repetition period.
 The MBMS ACCESS INFORMATION may be transmitted periodically based on an ""access info period"".
 This period will be an integer divider of the ""repetition period"" MCCH information is split into critical and non-critical information.
 The critical information is made up of the MBMS NEIGHBOURING CELL INFORMATION MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION.
 The non critical information corresponds to the MBMS ACCESS INFORMATION.
 ","The UTRAN can repeat the MCCH information following a scheduled transmission in order to improve reliability and the MCCH schedule will be common for all services The entire MCCH information will be transmitted periodically based on a ""repetition period"". The ""modification period"" will be defined as an integer multiple of the repetition period. The MBMS ACCESS INFORMATION may be transmitted periodically based on an ""access info period"". This period will be an integer divider of the ""repetition period"" MCCH information is split into critical and non-critical information. The critical information is made up of the MBMS NEIGHBOURING CELL INFORMATION MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION. The non critical information corresponds to the MBMS ACCESS INFORMATION.
 "
334,"In case one cell is detected in outage, COC will try to compensate the outage cell by reconfiguring the RF configuration of some compensation candidate cells.
 As a result of this, there will be new NRs (neighbour relations) which reflect the new topology relations. For a stable network, ANR could be deactivated for the purpose of system resource saving.
 If ANR is deactivated, the new NRs cannot be captured in NRT by ANR.
 Network performance, for example, handover will be impacted negatively by the NRT which lacks of the new NRs.
 Prevention is hardly possible, except making the cells as outage proof as possible.
 But cell outages can happen even to the most stable cell.
 The ANR function should monitor if a cell outage or cell outage compensation takes place within its area.","In case one cell is detected in outage, COC will try to compensate the outage cell by reconfiguring the RF configuration of some compensation candidate cells. Then, there will be new NRs (neighbour relations) which reflect the new topology relations. For a stable network, ANR could be deactivated for the purpose of system resource saving. If ANR is deactivated, the new NRs cannot be captured in NRT by ANR. Network performance, for example, handover, will be impacted negatively by the NRT which lacks of the new NRs. Prevention is difficult, except making the cells as outage proof as possible. The ANR function should monitor if a cell outage or cell outage compensation takes place within its area."
335,"For LTE TDD, the inter-cell interferences of eNB (HeNB) to eNB (HeNB) and UE to UE are related to the cell synchronization.
 In order to overcome the above interferences, strict synchronization is required.
 For HeNB, the interference case of UE to UE at the uplink-to-downlink switch point is the crucial factor to the synchronization requirement because of the limited coverage.
 At the switch point, two kinds of interferences should be taken into account.
 One is MUE downlink disturbed by HUE uplink, the other is HUE downlink disturbed by MUE uplink If the HeNB coverage is up to tens meters, the synchronization error should be smaller than 1us.
 For the network listening scheme, such strict requirement will increase the implementation difficulty and synchronization overhead.
 ","The inter-cell interferences of eNB (HeNB) to eNB (HeNB) and UE to UE, for LTE TDD, are related to the cell synchronization.
Strict synchronization is required to overcome the above interferences. For HeNB, the interference case of UE to UE at the uplink-to-downlink switch point is the crucial factor to the synchronization requirement because of the limited coverage. At the switch point, two kinds of interferences should be taken into account: 1) MUE downlink disturbed by HUE uplink, and 2) HUE downlink disturbed by MUE uplink. If the HeNB coverage is up to tens meters, the synchronization error should be smaller than 1us. 
 "
336,"Standard procedures are used to initiate a SIP session from the UE towards the remote end.
 The remote end is either alerting the user for the incoming voice or video-call session or the call is in pre-alerting state and announcements may be played to the UE.
 Access bearer for voice or video is setup for the UE during this step with an STN-SR indicating use of Single Radio VCC procedures for Access Transfer to CS access.
 If the user is not IMS registered by the MSC Server, the MSC Server enhanced for (v)SRVCC includes the C-MSISDN as calling party number.
 If the user is registered in the IMS by the MSC Server, then the MSC Server includes the GRUU into the session transfer request.
 The MSC Server indicates its capability to support mid-call services during session transfer.","To initiate a SIP session from the UE towards the remote end, the remote end is either alerting the user for the incoming voice or video-call session or the call is in pre-alerting state and announcements may be played to the UE. Access bearer for voice or video is setup for the UE during this step with an STN-SR indicating use of Single Radio VCC procedures for Access Transfer to CS access. If the user is not IMS registered by the MSC Server, the MSC Server enhanced for (v)SRVCC includes the C-MSISDN as calling party number. If the user is registered in the IMS by the MSC Server, then the MSC Server includes the GRUU into the session transfer request. The MSC Server indicates its capability to support mid-call services during session transfer.
 "
337,"Information Elements are classified into 3 categories as described below It is permissible for certain IEs to be repeated within a short message, or within a concatenated message.
 There is no restriction on the repeatability of IEs in the EMS Content classification.
 The repeatability of SMS Control and EMS Control IEs is determined on an individual basis.
 See the IE table below for the repeatability of each IE In the event that IEs determined as not repeatable are duplicated, the last occurrence of the IE shall be used.
 In the event that two or more IEs occur which have mutually exclusive meanings. ","It is permissible for certain IEs to be repeated within a short message, or within a concatenated message. There is no restriction on the repeatability of IEs in the EMS Content classification. The repeatability of SMS Control and EMS Control IEs is determined on an individual basis. In the event that IEs determined as not repeatable are duplicated, the last occurrence of the IE shall be used.  In the event that two or more IEs occur which have mutually exclusive meanings. "
338,"The MSC maps the eMLPP priority on these priority levels In addition, the eMLPP priority shall be explicitly indicated to the RNC in the RAB assignment request.
 Values for radio access bearer service attributes defined in TS 207 should be taken into account for mapping from eMLPP priority into priority related information element in RANAP.
 The RNC shall store the priority level in order to decide on later actions.
 If an appropriate radio channel is available the BSC (for GSM) or the RNC (for UMTS) shall assign it as normal.
 If no channels are available then the BSC (for GSM) or the RNC (for UMTS) shall perform queuing according to the priority levels.","The eMLPP priority shall be explicitly indicated to the RNC in the RAB assignment request. Values for radio access bearer service attributes defined in TS 207 should be taken into account for mapping from eMLPP priority into priority related information element in RANAP. The RNC shall store the priority level in order to decide on later actions.
 If an appropriate radio channel is available the BSC (for GSM) or the RNC (for UMTS) shall assign it as normal. If no channels are available then the BSC (for GSM) or the RNC (for UMTS) shall perform queuing according to the priority levels.
 "
339,"Entities in the same layer, but in different systems which must exchange information to achieve a common objective are called ""peer entities"".
 Entities in adjacent layers interact through their common boundary.
 The services provided by the (N + 1)-layer are the combination of the services and functions provided by the (N)-layer and all layers below the (N)-layer Management functions may also be required.
 They may include functions which are common for several layers and are not supported by the services provided by a specific layer.
 Examples of such functions are error reporting, status reporting and management of the operation of certain layers.
 Such management functions do not require that peer-to-peer messages are sent across the MS-BSS interface For signalling on the MS-BSS interface three layers are required.
 Layering on the MS-BSS interface Layer-to-layer interactions are specified in terms of service primitives.
 The primitives represent, in an abstract way, the logical exchange of information and control between adjacent layers.
 They do not specify or constrain implementation Primitives are also used to describe information exchange between layers and the mobile management entity (N + 1)-layer (N + 1)-layer.
 ","Peer entities are entities in the same layer, but in different systems which must exchange information to achieve a common objective. Entities in adjacent layers interact through their common boundary. The services provided by the (N + 1)-layer are the combination of the services and functions provided by the (N)-layer and all layers below the (N)-layer Management functions may also be required. They may include functions which are common for several layers and are not supported by the services provided by a specific layer.
Examples of such functions are error reporting, status reporting and management of the operation of certain layers.Such management functions do not require that peer-to-peer messages are sent across the MS-BSS interface For signalling on the MS-BSS interface three layers are required as layering on the MS-BSS interface Layer-to-layer interactions are specified in terms of service primitives. The primitives represent, in an abstract way, the logical exchange of information and control between adjacent layers. They do not specify or constrain implementation Primitives are also used to describe information exchange between layers and the mobile management entity (N + 1)-layer (N + 1)-layer 
 "
340,"As the switch-off of the RAN and the configuration change cannot be assumed to be perfectly synchronized, a small time safety margin needs to be applied broadcast PLMN information for both PLMNs.
 Subsequently the behaviour differs for supporting and non-supporting UEs able to decode the multiple PLMN information in the system broadcast information and select the PLMN on their own.
 The RPLMN should again be broadcast in the shared state, so no additional PLMN selection is are not able to decode the multiple PLMN information and consequently cannot control network selection.
 Instead, the RAN and core network perform this task by initial routing and potential re-direction.
 The impact on NAS signalling is that for these UEs additional registration updates.
 This solution allows to save the energy consumption of the RAN of at least one operator completely during off-peak time 
 ","A small time safety margin needs to be applied broadcast PLMN information for both PLMNs since the switch-off of the RAN and the configuration change cannot be assumed to be perfectly synchronized. The behaviour differs for supporting and non-supporting UEs able to decode the multiple PLMN information in the system broadcast information and select the PLMN on their own. The RPLMN should again be broadcast in the shared state, so no additional PLMN selection is not able to decode the multiple PLMN information and consequently cannot control network selection. Instead, the RAN and core network perform this task by initial routing and potential re-direction.
 "
341,"In addition the mobile station shall add to the stored list the PLMN code of the registered PLMN that sent the list.
 All PLMNs in the stored list shall be regarded as equivalent to each other for PLMN selection, cell selection/re-selection and handover.
 The stored list in the mobile station shall be replaced on each occurrence of the ROUTING AREA UPDATE ACCEPT message.
 If no list is contained in the message, then the stored list in the mobile station shall be deleted.
 An MS attached for emergency bearer services only shall delete the stored list when the MS enters the state GMM-DEREGISTERED.
 ","The mobile station shall add to the stored list the PLMN code of the registered PLMN that sent the list. All PLMNs in the stored list should be considered as equivalent to each other for PLMN selection, cell selection/re-selection and handover. The stored list in the mobile station shall be replaced on each occurrence of the ROUTING AREA UPDATE ACCEPT message and if no list is contained in the message, then the stored list in the mobile station shall be deleted. An MS attached for emergency bearer services only shall delete the stored list when the MS enters the state GMM-DEREGISTERED.
 "
342,"The GAA/GBA Bootstrapping procedure is initiated by the UE after a successful IMS registration and Service discovery.
 It is necessary before any service description retrieval and session initiation GBA is used to generate a master key Ks from which NAF specific keys (e.g. Ks_NAF for ME based key management) can be derived when needed. It is also used to authenticate the user for signaling that is not performed via the IMS core network. HTTP based service GBA is also used to generate and provision the NAF keys (e.g. Ks_NAF for ME based key management) - which is the Long Term Key that is used in content corresponding bootstrapping transaction identifier.","The GAA/GBA Bootstrapping procedure is initiated by the UE after a successful IMS registration and Service discovery.  Before any service description retrieval and session initiation, GBA is used to generate a master key. 
The key is also used to authenticate the user for signaling that is not performed via the IMS core network."
343,"The UE policy consists of - UE Access Network discovery and selection policies (ANDSP).
 It is used by the UE for selecting non-3GPP accesses network.
 The encoding of - UE Route Selection Policy (URSP).
 This UE policy is used by the UE to determine how to route outgoing traffic.
 Traffic can be routed to an established PDU Session, can be offloaded to non-3GPP access outside a PDU Session, or can trigger the establishment of a new PDU Session.
 ","The UE policy is used by the UE for selecting non-3GPP accesses network.
 "
344,"Entities in the same layer, but in different systems which must exchange information to achieve a common objective are called ""peer entities"".
 Entities in adjacent layers interact through their common boundary.
 The services provided by the (N + 1)-layer are the combination of the services and functions provided by the (N)-layer and all layers below the (N)-layer Management functions may also be required.
 They may include functions which are common for several layers and are not supported by the services provided by a specific layer.
 Examples of such functions are error reporting, status reporting and management of the operation of certain layers.
 Such management functions do not require that peer-to-peer messages are sent across the MS-BSS interface For signalling on the MS-BSS interface three layers are required.
 Layering on the MS-BSS interface - PHYSICAL LAYER which corresponds to the lowest layer.
 The functions and protocols of the physical layer are defined in Technical Specification 3GPP TS 40 - DATA LINK LAYER.","Management functions may also be required for all layers below the N-layer and they are common for several layers. 
 "
345," The handling of an absence or erroneous such IEs shall be treated as Optional IEs as specified in subclause - that the IE shall be included as a service option.
 Therefore, the IE may be included or not in a message.
 The handling of an absent optional IE, or an erroneous optional IE is specified in subclause.
 For conditional IEs, the clause describing the GTP-PDU explicitly defines the conditions under which the inclusion of each IE becomes mandatory or optional for that particular GTP-PDU.
 These conditions shall be defined so that the presence of a conditional IE only becomes mandatory if it is critical for the receiving entity.
 ","The handling of an absent optional IE, or an erroneous optional IE is specified in subclause."
346,"The GAA server also functions as a public API towards the GAA clients in the terminal Master Secret: The Master Secret is a master secret that servers as a basis for later key derivations.
 The Master Secret is established between the terminal (i.e., Persephone Server) and the network.
 The master secret is used as a key to derive further application specific credentials that can be used between the Orpheus clients and the application.
 Not every application derives its credentials from a Orpheus Client: A software component in the terminal that communicates with an application in the network.
 The Orpheus client application specific credentials to perform security functionalities.
 ","The Master Secret is a master secret which will be used as a key to derive further application specific credentials that can be used between the Orpheus clients and the application.
 
 "
347,"Typically the owner or beneficiary of the operator subscription.
 The M2M terminal user will manage the application activation of the M2M terminal to distinguish user and subscriber.
 But, for M2M terminals, there M2M terminal is typically unattended.
 It should therefore be reconsidered how to precisely define the roles of M2M terminal user and M2M terminal subscriber, and whether they really are two The manufacturer of the M2M terminal.
 The manufacturer may be a business stakeholder in the initial connectivity service or in the application The network operator providing connectivity in the operational state of the M2M terminal.
 In some activation scenarios, a separate initial connectivity provider can be identified.", It should therefore be reconsidered how to precisely define the roles of M2M terminal user and M2M terminal subscriber.
348,"A DNS server might provide the A/AAAA records together with the SRV resource records as per IETF RFC 2782 .
 The length of the NAPTR resource record indirection chain enabled using the """" flag is unbounded and may lead to a deep chaining of resource records over time in the DNS configuration.
 Additional layer of indirection and possible deep chaining both grows the DNS configuration significantly in size and complexity, and also makes the configuration prone to hard to trace errors.
 The use of NAPTR resource record """" flag pointing to other NAPTR resource records with flag """" is strongly discouraged.
 Specifically, NAPTR resource flag """" should only be provisioned to point to terminal NAPTR records (i.e., flag ""a"" or flag ""s"").
 ","

Additional layer of indirection and possible deep chaining both grows the DNS configuration significantly in size and complexity, and also makes the configuration prone to hard to trace errors.
 "
349,"The AVP header bit denoted as ""M"", indicates whether support of the AVP is required.
 The AVP header bit denoted as ""V"", indicates whether the optional Vendor-ID field is present in the AVP header.
 If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection.
 If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP.
 If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit.
 ","The AVP header bit value has different meanings. 
If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. 
If the M-bit is not set for an AVP, the receiver shall not return a rejection. 
If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit"
350,"The timing information allows the UE to determine the L1 combining period that applies to each S-CCPCH.
 The information also identifies the S-CCPCHs and the RLs that can be soft combined.
 The set of S-CCPCHs that can be combined does not change during an L1 combining period.
 When S-CCPCHs can be soft combined, all S-CCPCHs shall contain identical bits in their data fields, although the TFCI fields of the S-CCPCHs may be different.
 The maximum delay between S-CCPCHs that the UE may combine is set by UE performance requirements.
 ",The timing information allows the UE to determine the L1 combining period. The timing information also identifies the S-CCPCHs and the RLs that can be soft combined.
351,"The UE will use its IP address used in 3GPP access as its Home Address.
 This address will be preserved unless further indication from the 3GPP access.
 The UE uses the address configured from the PDG as the care-of address.
 The care-of address may be an IPv4 or IPv6 address The Home Agent responds with a binding acknowledgement if the binding update process was successful.
 The Home Agent also creates the binding cache entry with the new care-of address of the UE.
 ","The UE will use its IP address used in 3GPP access as its Home Address, which will be preserved unless further indication from the 3GPP access.
 "
352,"The value of the Message-ID field is composed of a unique transaction-id identifier followed by two numeric characters for message index within the transaction.
 The SFR enabled Feed Reader can find e.g. the response to a certain request message based on the transaction-identifier.
 All messages belonging to the same transaction shall use the same transaction identifier value in the Message id = 01178AC3200 for the first message, and message id = SFR is a profile of the DCD enabler dedicated to ATOM, RSS content.
 Syndicated feed discovery refers to methods for the UE to obtain a list of available syndicated feeds with the intent to activate the reception of one or more syndicated feeds.
 ","The value of the Message-ID field is composed of a transaction-id identifier followed by message index.
 The transaction identifier is the same for all related messages of a transaction.
 "
353," Although Compressed Data Stream Length (CDSL) - the total number of octets that contain the CDS - is known, the CD element of the CDS is a bit stream and therefore may not end on an octet boundary.
 The Compression Footer (CF) is used to indicate the end of the CD as follows - Calculate the number of meaningful bits in the last octet of the CD (i.e. total CD bits modulo 8) - If the number of meaningful bits is >0 and <6 store the number of meaningful bits in bits 2 to 0 of the last octet.
 Otherwise extend the CD by adding 1 octet and store the number of meaningful bits in bits 2 to 0 of this new octet.
 ",The CD element of the CDS is a bit stream and therefore may not end on an octet boundary. The Compression Footer (CF) is used to indicate the end of the CD. 
354,"The Requested W-APN may also indicate a point of interconnection to the external IP network (i.e. PDG). A W-APN is indicated by the WLAN UE in the tunnel establishment procedure between the WLAN UE and a PDG.
 It is then forwarded to the 3GPP AAA server/proxy in the same network as the PDG IP Connectivity for WLAN 3GPP IP Access.
 The WLAN UE initiates the establishment of tunnels and is involved in packet encapsulation/decapsulation.
 The tunnel shall reside between the WLAN UE and the PDG.
 ","The  W-APN may also indicate a point of interconnection to the external IP network. A W-APN is indicated by the WLAN UE in the tunnel establishment procedure. It is then forwarded to the 3GPP AAA server/proxy. The WLAN UE initiates the establishment of tunnels and is involved in packet encapsulation/decapsulation.
 "
355,"In this case, the operator advertises the name of one or more MRFCs and a UE will invite an MRFC to a session.
 The session invitation would need to contain additional information indicating the specific capabilities (e.g., multi-party) desired.
 A conference ID would be assigned by the MRFC and returned to the UE.
 This would then be used by the UE in subsequent interactions with the MRFC and other UEs participating in the session There are two approaches to invite new participants to the multiparty session.
 In the first, a UE directs other UEs to join the multiparty session based on the use of the SIP REFER method.
 This allows session invitations with consultation.
 In the second method, the MRFC uses information received from a UE e.g. within a list of session participants to invite other UEs to the multiparty session.","
 A conference ID would be assigned by the MRFC to the UE, which would then be used by the UE to invite new participants. "
356,"As depicted, the terminal connects to the IPv4 device directly using an IPv4 PDP or EPS Bearer Context.
 Hence, the UE appears to be a standard IPv4 node to the external IPv4 network.
 This scenario does not need any specific transition support from the network.
 However, it requires both versions of IP at the UE.
 The GGSN/P-GW in this scenario may be different for the IPv6 and the IPv4 connections unless IPv4/v6 PDP or EPS Bearer Contexts are used.
 ","The UE appears to be a standard IPv4 node to the external IPv4 network. This scenario does not need any specific transition support from the network. However, it requires IPV6 and IPV4 at the UE. "
357,"This feature is applicable for the SAR/SAA and If both the HSS and the S-CSCF support this feature, different aliases groups may be sent within the same service profile.
 Identities within the same service profile that are aliases shall be sent with identical alias group ID.
 If the S-CSCF does not support this feature, the HSS shall send within the service profile only those identities that are aliases.
 Public User Identities that are not aliases of each other shall be sent in different service profiles even if these service profiles have exactly the same.
 Core Network Service Authorization, Initial Filter Criteria, and Shared iFC Set information and these service profiles only differ in the contained Public User Identities.
 ",Identities within the same service profile that are aliases shall be sent with identical alias group ID. Public User Identities that are not aliases of each other shall be sent in different service profiles. 
358,"There are no provisions for the statistical variations that will occur when the parameter is tested.
 The test will result in an outcome of a test variable value for the device under test (DUT) inside or outside the test limit.
 Overall, the probability of a ""good"" DUT being inside the test limit(s) and the probability of a ""bad"" DUT being outside the test limit(s) should be as high as possible.
 For this reason, when selecting the test variable and the test limit(s), the statistical nature of the test is accounted for. The statistical nature depends on the type of requirement.
 Some have large statistical variations, while others are not statistical in nature at all. When testing a parameter with a statistical nature, a confidence level is set.
 This establishes the probability that a DUT passing the test actually meets the requirements and determines how many times a test has to be repeated and what the pass and fail criteria are.
 ","
 The test will result in an outcome of a test variable value for the device under test inside or outside the test limit.
 A confidence level indicates the probability that a DUT passing the test actually meets the requirements and determines how many times a test has to be repeated and what the pass and fail criteria are."
359,"ECSD Multi Slot class is an MS that supports ECSD shall include this field to indicate its ECSD capability.
 Whether the MS is capable of PSK modulation in uplink is indicated by the value of the Modulation Capability field in the PSK struct.
 The ECSD Multi Slot Class field is coded as the binary representation of the multislot class.
 The MS shall include the PSK struct if it supports ECSD or DTM EGPRS.
 The Modulation Capability field indicates the modulation scheme the MS supports in addition to GMSK.
 ","An MS that supports ECSD shall include this field to indicate its ECSD capability.
The MS shall include the PSK struct if it supports ECSD or DTM EGPRS 
."
360,"This chapter presents a selection of service scenarios, which are used as a basis for the RAB scenarios.
 Only the basic scenarios having impact on the lower layers are considered.
 Because the real time applications have the tightest connection with the lower layers, the real time scenarios are studied more in detail in this document.
 Other scenarios can be derived as combinations of these basic scenarios. Even though these scenarios are for IMS, they are applicable also for non IMS PS scenarios.
 The differences between IMS and non-IMS are small in RAN level: Usually, the difference is that in non-IMS cases the IMS signalling stream is left out or replaced by non-IMS signalling stream.
 ","This chapter presents a selection of service scenarios which have impact on the lower layers. In particular, the real time scenarios are studied more in detail since the real time applications have the tightest connection with the lower layers. "
361," Reference Configurations are conceptual configurations useful in identifying access arrangements to a network.
 Two concepts are used in reference points and functional groups.
 Functional Groups are sets of functions which may be needed in network access arrangements.
 In a particular access arrangement, specific functions in a functional group may or may not be present.
 Specific functions in a functional group may be performed in one or more pieces of equipment.
 Reference Points are the conceptual points dividing functional groups.
 ","
 Functional Groups are sets of functions which may be needed in network access arrangements.
 Reference Points are the conceptual points dividing functional groups."
362,"Information Need Multi Type and Semantics Version WLAN Threshold MP EnumerateValue in REL-12.
 The following table includes constants that are either used as multi bounds (name starting with ""max"") or as high or low value in a type specification (name starting with ""lo"" or ""hi"").
 Constants are specified only for values appearing more than once in the RRC specification.
 In case a constant is related to one or more other constants, an expression is included in the ""value"" column instead of the actual value.
 Constant Explanation Value Versio maxCNdomains Maximum number of CN domains 4 maxRAT Maximum number or Radio Access maxOtherRAT.
 ","
Constants are specified only for values appearing more than once in the RRC specification. An expression is included in the ""value"" column if  a constant is related to one or more other constants. "
363,"An interface is a named set of operations that characterize the behaviour of an element.
 In the metamodel, an Interface contains a set of Operations that together define a service offered by a Classifier realizing the Interface.
 A Classifier may offer several services, which means that it may realize several Interfaces, and several Classifiers may realize the same
 Interfaces may not have Attributes, Associations, or Methods.","An interface contains a set of Operations that together define a service offered by a Classifier realizing the Interface.  Classifier may realize several Interfaces, and several Classifiers may realize the same Interface
 "
364,"Each MC logging client is identified by a service specific identity, namely the MCPTT ID, MCVideo ID or MCData ID of the client.
 Call related information concerning the targets of logging are sent to the MC logging function via MClog-1, which is based on the MCservice-1 reference points (i.e. MCPTT-1, MCVideo-1 etc) but does not permit calls to be initiated by the MC logging function.
 Media plane communications content is provided to the media reception function of the MC logging client via MCLog-2, which is based on unicast media distribution reference points MC service-7 (i.e.MCPTT-7, MCVideo-7 etc), and floor control or media control information provided during calls.
 The MC logging equipment will require configuration to determine which MC service users and which MC servive groups are required by that MC logging equipment.
 It is expected that the MC logging equipment configuration will not be added into existing MC service user configuration tables, but will have a unique configuration will be needed.","Each MC logging client is identified by a service specific identity. 
 Call related information concerning the targets of logging are sent to the MC logging function via MClog-1. 
 Media plane communications content is provided to the media reception function of the MC logging client via MCLog-2.
 The MC logging equipment will require configuration to determine which MC service users and which MC servive groups are required by that MC logging equipment.
 "
365,"In case of MTC, the MTC Server may reside in the same private IPv4 address space as the UE, or the MTC Server may reside in public IPv4 address space.
 In the first case, the UE used for MTC and the MTC Server are in the same routable address space.
 In the latter case, the UE used for MTC and the MTC Server are located in different private IP Application Server.","The MTC Server may reside in the same private IPv4 address space as the UE, or the MTC Server may reside in public IPv4 address space.
"
366,"The level of orthogonalization is controlled by tuning the jamming graph threshold, i.e., the channel gain difference between interfering and serving link.
It can be seen that distributed FFR schemes eliminate system outage and significantly improve the system fairness.
 ","The level of orthogonalization is controlled by tuning the channel gain difference between interfering and serving link.

 "
367,"It should be possible for the mobile operator to control the access to the videotelephony service by means of a subscription to the service. 
 Inter-system handover between UMTS and GSM is not supported for 64 kbps UDI calls.
 In the case of a user moving out of 3G coverage, the video call will be released.
 The user has to establish a voice call either manually or the handset provides a voice call set up automatically.
 In the early days of UMTS this is an especially likely scenario.
 ","
 Inter-system handover between UMTS and GSM is not supported for 64 kbps UDI calls.
 The user has to establish a voice call either manually or the handset provides a voice call set up automatically.

 "
368,"A transport channel is used to transmit one data flow with a given QoS over the radio interface.
 A number of transport channels can be active at the same time and multiplexed at the physical layer.
 The transport channels are configured at call setup by the network. With FLO, the concept of transport channels used in UTRAN can be reused in GERAN. With FLO, the physical layer of GERAN offers one or several transport channels to the MAC sublayer.
 Each of these transport channels can carry one data flow providing a certain Quality of Service (QoS).
 A number of transport channels can be multiplexed and sent on the same basic physical subchannel at the same time. The configuration of a transport channel i.e. the number of input bits channel coding, interleaving etc.
 ","A transport channel is used to transmit one data flow with a given QoS over the radio interface.
 A number of transport channels can be active at the same time and multiplexed at the physical layer.
 "
369,"If the operation has been attempted SNS-SIZE-RETRIES times without acknowledgement from the peer NS entity, then the NS entity may notify the O&M system and abort the procedure.
 Whether the NS entity would restart the size procedure using any pre-configured SGSN IP endpoints after abortion is left implementation dependent.
 The configuration procedure is used on the Gb interface to exchange configuration information between an NSE and its peer NSE.
 To start the configuration procedure, the client/server principle is used, with the BSS as the client.
 Upon start-up/restart of a BSS NSE or following the detection of a restart of a peer SGSN NSE.
 ","If the operation has been attempted SNS-SIZE-RETRIES times without acknowledgement from the peer NS entity, then the NS entity may notify the O&M system and abort the procedure.
 Whether the NS entity would restart the size procedure using any pre-configured SGSN IP endpoints after abortion is left implementation dependent.
 "
370," The parameter specifies the periodicity for storing MDT measurement results.
 It should be configured in seconds in multiples of the applied IDLE mode DRX, i.e.multiples of 8s which is either a factor or multiple of the IDLE mode DRX.
 The UE behaviour is unspecified when the UE is configured with a DRX cycle larger than the - configuration of the logging duration.
 This configuration parameter defines a timer activated at the moment of configuration, that continues independent of state changes, RAT or RPLMN change.
 ","The logging interval specifies the periodicity for storing MDT measurement results.
 It should be configured in seconds in multiples of the applied IDLE mode DRX.
The UE behaviour is unspecified when the UE is configured with a DRX cycle larger than the  configuration of the logging duration.
 This configuration parameter defines a timer activated at the moment of configuration, that continues independent of state changes, RAT or RPLMN change."
371,"Most of the suburban area could obtain enough spectrum by sharing it from GSM/UMTS with much less investment.
 Large-Scale Averages needs to be put in perspective with respect to local averages.
 For example the possible gain due to dynamic spectrum reallocation may vary significantly according to the particular area, due to the various traffic patterns.
 In particular, with respect to a coverage area, if we consider e.g. a border region between the coverage areas of different RATs, the than if we were to consider a larger multi-RAT coverage area.
 In the same time frame with respect to the traffic pattern and the available spectrum resources.
 ","Most of the suburban area could obtain enough spectrum by sharing it from GSM/UMTS with much less investment.
 "
372,"The ""location abort"" message shall contain the reason for the location procedure cancellation.
 The MME shall then return an error response to the client or network entity (e.g. GMLC) from which the location request was originally received.
 The MME shall also release all resources specifically allocated for the location attempt. The following table indicates the appropriate error recovery procedure for certain events.
 For events not listed, the MME need take no action Table .a: LCS Error Recovery Procedures in the MME for certain Events.
 ","The ""location abort"" message shall contain the reason for the location procedure cancellation.
 The MME shall then return an error response to the client or network entity from which the location request was originally received.
 The MME shall also release all resources specifically allocated for the location attempt.
 "
373,"From release 8 onwards, the normative specification of the user plane of GTP version 1 is 3GPP TS 281.
 All provisions about GTPv1 user plane in the present document shall be superseded by 3GPP TS 281. The present document defines the GPRS Tunnelling Protocol (GTP), i.e. the protocol between GPRS Support Nodes (GSNs) in the UMTS/GPRS backbone network.
 It includes both the GTP control plane (GTP-C) and data transfer (GTP-U) procedures.
 GTP also lists the messages and information elements GTP (GTP-C and GTP-U) is defined for the Gn interface, i.e. the interface between GSNs within a PLMN, and for the Gp interface between GSNs in different PLMNs.
 ","From release 8 onwards, the normative specification of the user plane of GTP version 1 is 3GPP TS 281.  The present document defines the GPRS Tunnelling Protocol (GTP), the GTP control plane (GTP-C) and data transfer (GTP-U) procedures. GTP also lists the messages and information elements GTP (GTP-C and GTP-U) is defined for the Gn interface."
374,"When the validity timer expires then the ProSe App Code is no longer valid - Time stamp or time value The Second parameter could make it difficult to forge tokens.
 Example of parameter which could be used - Discovery security key.
 The Discovery security key can be shared by the Discoverer UE and the ProSe Function in the network The Third parameter could make the token unique per Discoveree UE.
 Example of parameter which could be used - Discoveree UE identity as ProSe UE identity The Fourth parameter could map the Direct Discovery Response to the Direct Discovery Request.
 Example of parameter which could be used - ProSe App Code.
 The ProSe App Code included in the Direct Discovery Request message.
 Note that if ProSe App Code has been used in the First parameter then it would not be needed to include it twice Solution #: Security for proximity request authentication.","The Discovery security key can be shared by the Discoverer UE and the ProSe Function in the network.The Third parameter could make the token unique per Discoveree UE.
 "
375," The Dual Symbol Rate could apply the existing 8PSK parameters excluding symbol rate and shaping filter.
 The Modified Dual Symbol Rate uses 16QAM modulation at 3/2 times higher symbol rate compared to GSM.
 QPSK is considered optionally for coverage extension.
 MDSR modulator could produce middle of two GSM channels. ", The Modified Dual Symbol Rate uses 16QAM modulation at 3/2 times higher symbol rate compared to GSM. QPSK is considered optionally for coverage extension. MDSR modulator could produce middle of two GSM channels.
376,"The term service is used here in its common meaning.
 A service is something that a MNO offers to subscribers.
 GAA Services are identified by GAA Service Identifier (GSID).
 In stage 2 documents ( , and\) the term application is used in the same meaning i.e MNOs offer applications to subscribers.
 There is a reason to avoid the usage of the term application here.
 The application is an already reserved term in Diameter. ","A service is something that a MNO offers to subscribers. GAA Services are identified by GAA Service Identifier (GSID). In stage 2 documents , the term application is used in the same meaning.  We avoid the usage of the term application here because it is reserved in Diameter. "
377,"The two experiments were conducted by the same LL and used the same music samples, the same experimental design, and some of the same listeners (11 of 32 listeners participated in both experiments).
 A comparison of the F-Ratios (""Conditions"" / ""Conditions x Listeners"") for the two test methodologies in effect provides a comparison of the relative resolving power of the methodologies.
 The F-Ratio for the ACR (F=106) is in fact higher than that for the DCR (F=98).
 This result would indicate that the ACR has equivalent or possibly even better resolving power than the DCR for these experiments.
 This finding has important implications for the design of tests of Music quality and suggests additional research into the relative resolving power of various test methodologies.
 ","The two experiments were conducted by the same LL and used the same music samples, the same experimental design, and some of the same listeners. 
 A comparison of the F-Ratios for the two test methodologies in effect provides a comparison of the relative resolving power of the methodologies. ACR has equivalent or possibly even better resolving power than the DCR, which has important implications for the design of tests of Music quality and suggests additional research into the relative resolving power of various test methodologies. "
378,"This information is extracted in the TTCN-3 and used in subsequent responses sent by the SS For SIP requests originated by the SS in DL UDP is used as transport protocol at the test.
 For the purpose of test coverage, TCP is used in the specific test cases as specified. The ""Enabler for IP multimedia applications testing"" is described in TS 32.
 In general IMS CC test cases can be run on this test model too as test case implementation - in general - is independent of the test model.
 The TTCN code for IMS and HTTP PTC is the same for TS 32 and TS 32 implementations whereas the MTC implementation is model specific.
 The implementation of the MTC, the IP-CAN/IP adaptor and the MMI system interface is part of TS 32 and out of scope for this document."," For SIP requests originated by the SS in DL UDP is used as transport protocol at the test.
 For the purpose of test coverage, TCP is used in the specific test cases.
 The TTCN code for IMS and HTTP PTC is the same for TS 32 and TS 32 implementations whereas the MTC implementation is model specific.
The implementation of the MTC, the IP-CAN/IP adaptor and the MMI system interface is part of TS 32 and out of scope for this document.
 "
379," The handling of UP integrity check failures by an RN is an implementation issue.
 TS 323 intentionally does not mandate any action for a failed integrity check (not even sending an indication of failure to higher layers).
 Consequently, depending on the implementation, the message failing integrity check is, or is not, silently discarded.
 This is in contrast to the handling of a failed RRC integrity check by a UE, cf.
 the NOTE in clause of RRC integrity protection shall be provided by the PDCP layer between UE and eNB and no layers below PDCP shall be integrity protected.
 Replay protection shall be activated when integrity protection is activated (except for when the selected integrity protection algorithm is EIA0).
 ","The message failing integrity check is, or is not, silently discarded.
This is in contrast to the handling of a failed RRC integrity check by a UE.
 "
380,"The display height for a Character Size WVG object is decided by the terminal implementation.
 Recommended Character Size WVG of a Character Size WVG object is variable depending on the aspect ratio defined in the object.
 Character Size WVG objects can appear more than one time in one message.
 In the above example, there are 4 Character Size WVG objects, each representing a Chinese character.
 The Extended Object allows an extended code range for format types.
 The Extended Object may extend across segment boundaries of a concatenated short message.
 Octets 1 through 7 of the first Extended Object IE shall be contained in a single segment.
 ",The display height for a Character Size WVG object is decided by the terminal implementation. Recommended Character Size WVG of a Character Size WVG object is variable depending on the aspect ratio defined in the object. Character Size WVG objects can appear more than one time in one message 
381,"The index of the first stage codevector is retrieved and the codevector components are obtained from the 1dimensional codebook of and the corresponding multiple scale lattice codevector is obtained.
 If the codevector index from the first stage has one of the values 0, 1, 2, 3, 7, 9, 12, 13, 14, 15 the permutations specified in subclause are applied to the decoded codevector.
 The resulting codevector is added to the codevector obtained in the first stage and the result corresponds to the decoded LSF vector.
 The sampling frequency of the LP-CNG frame can be determined by checking the value of the highest order LSF coefficient (last coefficient).
 If the last decoded LSF coefficient is larger than 6350 the decoded frame has sampling rate of 16 kHz, otherwise it is sampled at 1kHz and contains either NB or WB LSF data.
 ","
 If the codevector index from the first stage has certain values, the permutations specified in subclause are applied to the decoded codevector. The resulting codevector is added to the codevector obtained in the first stage and the result corresponds to the decoded LSF vector.
 
 "
382,"These frames include a PPPoE session ID which differentiates traffic between different PDN connections. The TWAG binds a PPPoE session ID with a PDN connection.
 Traffic arrived from a certain PPPoE session ID is forwarded to the linked PDN connection and vice versa. The TWAG behaves as an Access Concentrator that terminates both PPP and PPPoE protocols.
 It is very similar to a Broadband Remote Access Server (BRAS) function used in fixed broadband networks. The UE needs to implement the PPP and PPPoE protocols only when it is multi-PDN capable.
 Both of these protocols are already available in most smartphone platforms.","These frames include a PPPoE session ID.  The TWAG binds a PPPoE session ID with a PDN connection.
Traffic arrived from a certain PPPoE session ID is forwarded to the linked PDN connection and vice versa. The UE needs to implement the PPP and PPPoE protocols only when it is multi-PDN capable."
383," A Non-Seamless WLAN Offload (NSWO) connection does not use PPP or PPPoE.
 So, NSWO traffic is transmitted directly over WLAN without any Since NSWO traffic does not use PPPoE, it does not necessarily need to be routed through TWAG.
 Instead, it can be optimally routed without going through TWAG.
 This allows TWAG to be offloaded from NSWO traffic. It also allows the WLAN network and the UE to support NSWO traffic with the currently deployed means."," NSWO traffic does not use PPPoE, it can be optimally routed without going through TWAG. This allows TWAG to be offloaded from NSWO traffic. "
384,"The BEGIN record is used to convey the first event of MBMS service. The BEGIN record shall be triggered when interception is activated for the target but the MBMS UE has successfully joined an MBMS service prior to the start of interception (Start of intercept with MBMS Service Active).
 Event Type M Provide MBMS Service Joining event type Event Time M Provide the time the event is detected.
 Event Date M Provide the date the event is detected.
 ",The BEGIN record is used to convey the first event of MBMS service. The BEGIN record shall be triggered when interception is activated for the target but the MBMS UE has successfully joined an MBMS service prior to the start of interception. 
385,"However, any request targeted to either UE will be sent to the respective P-CSCF, hence not causing any ambiguity at the P-CSCF when forwarding the request via  F.4 P-CSCF usage of SIP in case UDP encapsulated IPsec is not employed.
 The subclause F.4 describes the SIP procedures for supporting hosted NAT scenarios in case UDP encapsulated IPsec is not employed.
 In these scenarios the procedures for NAT traversal must take into account that all SIP requests and responses are not protected by an IPsec security association.
 This subclause also assumes that the UE transmits the SIP messages from the same IP address and port on which the UE expects to connect.
 ","The procedures for NAT traversal must take into account that all SIP requests and responses are not protected by an IPsec security association.
 
 "
386,"In CSI measurement configuration, UE is indicated to perform LRSRP measurement on the SSBs and report periodically.
 The test consists of two successive time periods, with time duration of T1 and T2 respectively.
 The test has higher layer parameter timeRestrictionForChannelMeasurements configured.
 There is no measurement gap configured in the test.
 Before the test, UE is configured to perform RLM, BFD and LRSRP measurement based on the SSBs.
 ",UE is indicated to perform LRSRP test on the SSBs and report periodically.
387,"Each service consists of a user defined part and an operator defined part.
 The user defined data is found in each of the MMTEL supplementary service specifications.
 The operator defined part consists of authorization of the service, and of the subscription options for each of the services.
 A dedicated Service Indication shall be used within the XML option for MMTel services.
 The value of the Service Indication shall be ""MMTEL.
 Proprietary extensions shall use not standardized Service Indications. There is no constraint for the data structure of the proprietary Service.
 ","Each service consists of a user defined part and an operator defined part.
 The user defined data is found in each of the MMTEL supplementary service specifications.
 The operator defined part consists of authorization of the service, and of the subscription options for each of the services 
 A dedicated Service Indication shall be used within the XML option for MMTel services.
 
 "
388,"The peak EVM is the peak error deviation within a burst, measured at each symbol interval averaged over at least 200 bursts.
 The bursts shall have a minimum distance in time of 7 idle timeslots between them.
 The peak EVM values are acquired during the useful part of the burst, excluding tail bit. The 95: th percentile EVM shall be measured and calculated.
 The 95: th percentile EVM is the point where 95% of the individual EVM, measured at each symbol interval, is below that point.
 That is, only 5% of the symbols are allowed to have an EVM exceeding the 95: th-percentile point.
 The EVM values are acquired during the useful part of the burst excluding tail bits, over 200 bursts.
 ","The peak EVM is the peak error deviation within a burst, measured at each symbol interval averaged over at least 200 bursts.
The peak EVM values are acquired during the useful part of the burst.  The 95 percentile EVM shall be measured and calculated.

 "
389,"A cell reselection does not lead to new keys being provided to the new eNB.
 However, a new MME selected upon idle mode mobility has to be provided with keys.
 A new MME can be provided with keys by one of the three alternatives described for inter MME handover.
 However, in case of idle mode mobility, new keys could also be provided to the MME by a new run of AKA. In this case, a location update would always result in a new run of AKA during which MME obtains a new KASME from the HSS.
 However, a new run of AKA is not required in order to provide key separation between MMEs.
 For key separation between MMEs it would be sufficient to provide the new MME with a KASME which HSS derived from CK IK with help of PLMN-ID, and RAT type as input.
 ","A new MME selected upon idle mode mobility has to be provided with keys by one of the three alternatives described for inter MME handover.
 "
390,"The SCC AS creates an INVITE containing the SDP received from MGCF, indicating CS voice or voice and video media.
 The original called number and the calling party number are used to setup the outgoing call leg to party-B in accordance (e.g. CGI or SAI) and/or UE Time Zone Information to the INVITE.
 The SCC AS sends the INVITE back to S-CSCF party number at the SCC AS if ISUP does not provide this information is implementation dependant.
 This can be realized by interactions between the SCC AS and the SCF. ","The SCC AS creates and sends an INVITE containing the SDP received from MGCF indicating CS voice or voice and video media back to S-CSCF. Call set up with original called/calling parties' numbers and information (e.g., CGI, SAI, UE Time Info)."
391,"The ability to switch the bit rate at every 2ms frame allows the codec to easily adapt to changes in channel capacity.
 The codec features discontinuous transmission (DTX) with algorithms for voice/sound activity detection (VAD) and comfort noise generation (CNG).
 An error concealment mechanism mitigates the quality impact of channel errors resulting in lost packets.
 A system for jitter buffer management (JBM) is included.
 The codec also features a channel-aware mode to further improve frame/packet error resilience.
 ",Bit rate swtching at every 2ms frame allows the codec to adapt to changes in channel capacity. The codec (DTX) also provides algorithms and mechanisms to improve the channel quality and reduce the impact to channel errors.
392,"USIM, ISIM, CAT applications) inside the UICC can not tolerate the suspension of the UICC in a specific state or might need to perform specific operations before the UICC is suspended.
 For this reason, the solution should have a mechanism to inform the applications in the UICC about the SUSPEND command and allow each interested application to return a temporary error or reject it.
 A temporary error gives to the ME the indication that SUSPEND can be retried later.
 A mechanism to avoid a repeated trial and error approach by the ME should be considered e.g.by allowing the UICC to indicate a period of time after which the ME may retry successfully to issue a SUSPEND command or a mechanism for the UICC to explicitly state it is ready.
 It is considered useful for the UICC to know the estimate of the duration of the suspension.
 ","Before suspended, a applications in UICC must be informed of the SUSPEND command and allowed to return a temporary error or reject it. To avoid repeated trial and error, the UICC can indicate a waiting time for the ME to re-issue a SUSPEND command, or the UICC can explicitly state when it's ready. "
393,"The different music items have been processed using the floating point V of AMR-WB and also using the fixed point V of AMR-WB.
 In order to have a comparison, G.72 at 24 kbps was included in the test The test has been performed by informal listening including trained listeners.
 The result of the test was that the floating point V did not perform worse than the fixed point V of AMR-WB.
 The G72 at 24 kbps was scored better than AMR-WB for most of the music files.
 For each mode and each music signal, the bit exactness of the fixed point decoder and the floating point decoder has been verified.
 No exception of bit exactness between fixed point decoder V and floating point decoder V has been found during the test.
 The floating point V of AMR-WB did not perform worse than the fixed point version B.3 Bit-Exactness, Idle-Channel Behaviour and Long-Term Stability.
 For all the tests, the V of the AMR-WB fixed-point code and the V of the AMR-WB floating-point code were used.
 The compilation was on Linux workstation and GNU C compiler Idle channel behavior (output signal when low noise input signal) and decoded by the AMR-WB floating point coder in all 9 modes.
 The output files were listened by experts and no strange behavior or annoying artefacts was recognized.
 ","Music items were processed and tested with all mode 9 AMR-WB modes (e.g., floating point, fixed point) and decoding options (e.g., fixed point decoder, floating point decoder) and listened by experts who reported no anomalies."
394,"After the first check of all trunk groups in a routing chain, if an idle trunk is not found in a trunk group on which trunk queuing has been provisioned, the call is entered into a queue.
 The MSC recognizes Priority Service calls and separates them from all other calls.
 All non-Priority Service calls that overflow to a busy trunk group on which Priority Service trunk queuing is active are sent to the next call treatment.
 A Priority Service call held in queue seizes the first trunk that becomes idle or, if the maximum queuing time interval expires, is sent to the next call treatment.
 Trunk queuing can be provided on network routable trunk types served by the MSC.
 ",Idle trunks not found in the related trunk groups are entered into a queue. The MSC recognizes and separate Priority Service calls. Non-Priority Service calls overflowing the trunk group queue are sent to the next call treatment. A Priority Service call is sent to the next call treatment when the maximum queuing time interval expires.
395,"Scaling can be applied every slot, in line with TPC command frequency.This procedure aims at preserving DPCCH and other signaling channels power, at the expense of EDPDCH.
 E-DPDCH is protected by HARQ retransmission and data can still be recovered at low power.
 However, the procedure also results with an unbalanced performance expense of the other. The procedure is expected to hold for DC-HSUPA.
 However for DB-DC-HSUPA the results should be verified as the imbalance in power between the carriers may break the algorithm.
 For example, in DB-DC-HSPA, the higher band requires more transmit power for equal performance and therefore the algorithm will most likely always target the higher band in power limited case.
 For that reason, power scaling is very sensitive in DB-DC HSPA One way to avoid the issue of power scaling for DB-DC HSPA would be to fall back to single carrier when DB-DC-HSUPA is power limited.
 ","Power scaling can be applied to preserve DPCCH and other signaling channels power, at the expense of E-DPDCH, since E-DPDCH is protected by HARQ retransmission and data can be recovered at low power."
396,"LCS client Requestor: the originating entity which has requested the location of the target UE from the LCS client. Requestor Identity: This identifier is identifying the Requestor and can be e.g. MSISDN or logical name. Response method: method how a GMLC, which receives a location request message from another entity (i.e. LCS client or GMLC), responds to the location request.
 There are two methods, synchronous (SYNC) and asynchronous (ASYNC).
 When the requesting entity wishes multiple responses request the procedure is ASYNC and when the requesting entity wishes a single response the procedure is SYNC.
 ","LCS client Requestor: originating entity which has requested the target UE location from the LCS client. Requestor Identity: identifier of the Requestor. Response method: ASYN when the requesting entity wishes multiple responses, SYNC when it wishes a single response."
397,"For the purposes of the present document, the terms and definitions given in TR 205 and the following apply.
 A term defined in the present document takes precedence over the definition of the same term, if any, in Elementary Procedure: LPPa protocol consists of Elementary Procedures (EPs).
 An LPPa Elementary Procedure is a unit of interaction between the eNB and the E-SMLC.
 An EP consists of an initiating message and possibly a response message.
 Two kinds of EPs are used - Class 1: Elementary Procedures with response (success or failure) - Class 2: Elementary Procedures without response Cell Portion: A geographical part of a cell.
 A cell portion is semi-static and identical for both the UL and the DL.
 ","LPPa protocol consists of Elementary Procedures (EPs). An LPPa Elementary Procedure is a unit of interaction between the eNB and the E-SMLC, and consists of an initiating message and possibly a response message. EPs Class 1 includes a response (success or failure), EP Class 2 does not."
398,"The set group names may be empty or may contain one or more group names.
 If the set is empty then all groups under the relevant policy domain are to be considered in the evaluation.
 ",The set group names may be empty or may contain one or more group names. If empty consider all. 
399," It shall be possible to indicate to the UE that an MM needs to receive special treatment.
 When a MM has been marked with this indication, means shall be provided to protect the MM from accidental deletion e.g. by asking for additional confirmation to the user.
 The use of this indication shall be under the control of the HPLMN.
 ",UE can be informed that MM needs to receive special treatment and means shall be provided to protect the MM from accidental deletion. Indication under the control of the HPLMN
400,"It is used by an RLP entity to indicate that it is temporarily not ready to receive numbered information frames.
 In that case, the RLP entity is said to be in the busy condition.
 All frames up to and including N(R)-1 shall be considered acknowledged.
 Subsequent frames, if any, shall not be considered confirmed.
 The acceptance status of those is a matter of further status Selective reject, SREJ (11) The SREJ encoding can be used either as command or response.
 The SREJ command/response is used to request retransmission of a single frame, thus under certain circumstances, providing for more efficient error recovery than by REJ.
 ",RPL in busy condition is temporarily not ready to receive numbered information frames. Only frames up to and including N(R)-1 shall be considered acknowledged. The SREJ command/response is used to request retransmission of a single frame providing more efficient error recovery than by REJ.
401,"The SCC AS creates an INVITE containing the SDP received from MGCF, indicating CS voice or voice and video media.
 The original called number and the calling party number are used to setup the outgoing call leg to party-B in accordance (e.g. CGI or SAI) and/or UE Time Zone Information to the INVITE.
 The SCC AS sends the INVITE back to S-CSCF party number at the SCC AS if ISUP does not provide this information is implementation dependant.
 This can be realized by interactions between the SCC AS and the SCF (e.g. gsmSCF); however this interaction is outside the scope of this specification or SAI) and/or UE Time Zone Information at the SCC AS is implementation dependant.
 This can be realized by interactions between the SCC AS and the SCF.
 ","The SCC AS creates and sends an INVITE containing the SDP received from MGCF indicating CS voice or voice and video media back to S-CSCF. Call set up with original called/calling parties' numbers and information (e.g., CGI, SAI, UE Time Info)."
402,"The mapping from service area identity or cell ID and location area to location number is network-specific and outside the scope of the UMTS and GSM standards.
 Service area ID C Service area identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact.
 Shall be present if the MS uses UMTS radio access and the subscriber record is marked as confirmed by radio contact; otherwise shall be absent.
 See Cell ID C Cell global identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact.
 Shall be present if the MS uses GSM radio access and the subscriber record is marked as confirmed by radio contact; otherwise shall be absent.","The mapping from service area identity or cell ID and location area to location number is network-specific. See Service area ID C Service if the the MS uses UMTS, see Cell ID C Cell global identity if the MS uses GSM."
403,"First container includes initial QoS values and corresponding volume counts.
 Second container includes new QoS values and corresponding volume counts before tariff time change.
 Third container includes the indication of location change and corresponding volume counts before the location change and after the tariff time change.
 Fourth container includes volume counts after the location change and contains the indication of Direct Tunnel establishment.
 Last container includes no volume count as it refers to Direct Tunnel establishment. ","The containers includes different information about QoS values, volume counts according to location changes and tariff time changes, and Direct Tunnel establishment indications."
404,"All the changes indicated in one Change HW Configuration message must be successfully conducted or the procedure must fail otherwise.
 The HW Description Position Index, an octet Configuration attribute to which the change operation indicated by the associated Operation Code must be applied.
 In case of multiple entries, all the position indices shall be interpreted against the initial HW Configuration sequence.
 There are three possible operations as listed By a deletion operation, the indexed HW Description is deleted from the HW Configuration attribute.
 A deletion operation requires no associated Modification Data.
 An insertion or modification operation requires an associated Modification Data which specifies the new data for the operation.
 ","All changes indicated in one Change HW Configuration message must be successfully conducted or the procedure must fail otherwise. An Operation Code must be applied to indicate the operation type (deletion, insertion, modification)."
405," This clause introduces the set of Information Object Classes (IOCs) that encapsulate information within the IRPAgent.
 The intent is to identify the information required for the delta synchronization IRP Agent implementation of its operations and notification emission.
 This clause provides the overview of all support object classes in UML.
 Subsequent clauses provide more detailed specification of various aspects of these support object Information Object Class (IOC) UML Diagram.
 DeltaSynchronizationIRP is the representation of the delta synchronization capabilities specified by the present document.
 ","Information Object Classes (IOCs) encapsulates information within the IRPAgent to identify the information required for the delta synchronization IRP Agent implementation of its operations and notification emission.  This clause provides the overview of support object classes in UML, and subsequent clauses provide more detailed specification of various aspects of these support object Information Object Class (IOC) UML Diagram. "
406,"All other call set up requests shall proceed as a normal call set up, and the dialled digits offered by the SAT/USAT shall not be altered.
 Provided a roaming agreement for the necessary transport/bearer service(s) (e.g.SMS, GPRS) is currently valid, the USAT execution environment shall be supported when roaming. 
 This subclause defines the interaction between PLMN supplementary services and the USAT feature.
 PLMN supplementary services shall not have any knowledge of USAT based services.","Other call set up requests shall proceed as a normal call set up, and the SAT/USAT dialled digits shall not be altered. USAT execution environment shall be supported when roaming. PLMN supplementary services shall not have any knowledge of USAT based services."
407,"The open loop gain is given by where dmax is the pitch delay that maximizes C(d).
 The median filter is updated only during voiced speech frames.
 The weighting depends on the reliability of the old pitch lags.
 The impulse response, h(n), of the weighted synthesis filter is computed each subframe.
 This impulse response is needed for the search of adaptive and fixed codebooks.
 ",The open loop gain is given by where dmax is the pitch delay that maximizes C(d). Median filtering and weighting depends of frames content.
408,"The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415) if not otherwise.
 This AVP contains an identifier that helps the home network to identify the visited network (e.g. the visited network domain name). The Public-Identity AVP is of type UTF8String.
 This AVP contains the public identity of a user in the IMS.
 The syntax of this AVP corresponds either to a SIP URL (with the format defined in IETF RFC 3261 and IETF RFC 2396 ) or a TEL URL (with the format defined in IETF RFC 3966).
 Both SIP URL and TEL URL shall be in canonical form, as described in 3GPP TS 203 The Server-Name AVP is of type UTF8String.
 This AVP contains a SIP-URL (as defined in IETF RFC 3261 and IETF RFC 2396), used to identify a SIP server (e.g. S-CSCF name). The Server-Capabilities AVP is of type Grouped.
 This AVP contains information to assist the I-CSCF in the selection of an S-CSCF.
 ","The Vendor-ID header of all AVPs shall be set to 3GPP (10415) if not otherwise. This AVP contains an identifier to identify the visited network, the public identity of a user in the IMS, SIP URL (used to identify a SIP server) and TEL URL in canonical form, and information to assist the I-CSCF in the selection of an S-CSCF."
409,"The entity performing the manager role Network Operations Staff.
 During open loop operation, personnel who manually review the results of the SON function at intermediate steps in the particular SON process.
 The network operations staff decide upon and manually initiate the appropriate next step in the SON process.
 The particular equipment and the need for any SON function(s) within it will be specific to each individual use case.
 The location of any SON function(s) within the OAM system will also be specific to each individual use case SON Function.
 ","This AVP contains an identifier that helps the home network to identify the visited network, the public identity of a user in the IMS. a SIP-URL used to identify the server, and information to assist the I-CSCF in the selection of an S-CSCF. This AVP syntax corresponds either to a SIP URL or a TEL URL in canonical form."
410,"Then the MS shall establish a signalling link indicating the correct timing advance and power level and send a HANDOVER COMPLETE message.
 The MS shall be ""ready to transmit"" the HANDOVER COMPLETE message before ""x"" ms after the end of the HANDOVER COMMAND message, but not before a UA frame has been sent by the SS.
 The MS shall then again send the SETUP message to the SS, using the same value in the N(SD) field.
 Finally the SS sends a CHANNEL RELEASE to end the test depends upon the target channel and is specified in the specific message Maximum Duration of Test.
 This procedure is repeated for execution counter M = 1, 2, 3, 4 (unless a particular TCH is not supported).
 ","Then the MS shall establish a signalling link, send the HANDOVER COMPLETE message and the SETUP message to the SS. 
Finally, SS sends a CHANNEL RELEASE message."
411,"This function interfaces with the PSMF, the PRRM and the PCF.
 The PRCF determines the location method to be used based on the capabilities.
 The PRCF also manages the needed radio resources through the PRRM.
 It determines which PSMFs are to be involved, what to measure, and obtains processed signal measurements from the PSMF Some location methods may involve measurements made at the MS.
 In this case the PRCF interfaces with the MS to obtain the measurements (or the location results if they have been determined by the MS).
 ","The PRCF determines location method, needed radio resources through the PRRM, which PSMFs to involve, what to measure, and interfaces with the MS to obtain processed signal measurements from the PSMF."
412,"Measurement packages are present in the Measurement Function Object (e.g.BSC Measurement Function), if the Network Element Function (e.g.BSC) containing the Measurement Function Object supports the required number of instances of the measurement included in the package according to the number of instances of the Measurement Function.
 The simple scanner has been designed to read the values of the attributes according to a given C. ",Measurement packages are present in the Measurement Function Object if to the Network Element Function containing the Measurement Function Object supports the required measurement instances number.
413,"The SIP response may include additional information about the cause to reject/release the IMS service.
 The presence of this additional error information in the response shall be operator configurable. The additional information included in the SIP response may contain a SIP URI.
 The UE may treat the SIP URI as if it were a Contact in a redirect and generate a new SIP INVITE, resulting, for example, in a recorded announcement session being established.
 If announcement information is present in the Debit / Reserve Units Response message then a SIP URI should not be provided in the SIP response B). The IMS-GWF generates a SIP request (e.g. SIP BYE or SIP CANCEL) as a result of the IMS Service Termination procedure request which provides additional information about the cause to reject/release the IMS service.
 ","As a result of the IMS Service Termination procedure request a SIP request and response may include additional information about the IMS service reject/release cause.
The SIP reponse may include the SIP URI if the announcement information is not present in the Debit / Reserve Units Response message."
414,"At HI3 interface FTP is used over the internet protocol stack for the FTP supports reliable delivery of data.
 The data may be temporarily buffered in the sending node (MF) in case of link failure.
 FTP is independent of the payload data it carries C.
 Usage of the FTP In the packet data LI the MF acts as the FTP client and the receiving node (LEMF) acts as the FTP server .
 The client pushes the data to the server The receiving node LEMF stores the received data as files.
 ",At HI3 interface FTP is used over the internet protocol stack for the FTP supports reliable delivery of data.
415," If no such information is present, the ciphering mode is the same as on the previous channel.
 In either case the ciphering key shall not be changed as long as the key length remains unchanged.
 However, in case of a switch between ciphering algorithms requiring different key lengths, i.e. 64 or 128 bits, a change from the 64 bit key to the 128 bit key or vice versa. Downlink SACCH shall be able to decode both ciphered and not-ciphered SACCH blocks.
 ","If no such information is present, the ciphering mode is the same as on the previous channel.
In either case the ciphering key shall not be changed as long as the key length remains unchanged."
416," The PPI flag in octet 5 indicates whether the Paging Policy Indication value in octet ""m"" shall be present.
 If PPI is set to ""1"", then the Paging Policy Indication value shall be present.
 If PPI is set to ""0"", then octet ""m"" shall not be present. The QFII flag in octet 5 indicates whether the QFI value in octet ""p"" shall be present.
 If QFII is set to ""1"", then the QFI value shall be present.
 ","These octet(s) is/are present only if explicitly specified and provide(s) downlink data service information (e.g, Paging Policy Indication)."
417,"This AVP shall contain the information about the network node serving the targeted user Result-Code AVP and Experimental-Result AVP Values. 
 This section defines result code values that shall be supported by all Diameter implementations that conform to this specification.
 Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed.
 The Result-Code AVP values defined in Diameter Base Protocol RFC 3588 shall be applied.
 Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again.
 ",The AVP shall contain the information about the network node serving the targeted user. Specific Result-Code AVP values shall be supported by all Diameter implementations that conform to this specification.
418,"Bits 1 to 4 of the third octet in the message header contain the Protocol Discriminator (PD) information element.
 The PD identifies the upper layer protocol to which the message belongs. 
 Bits 5 to 8 of the third octet in the message header contain the Skip Indicator information element.
 A message received with Skip Indicator different from 0000 shall be ignored.
 A message received with Skip Indicator encoded as 0000 shall not be ignored (unless it is ignored for other reasons).
 A protocol entity sending any message shall encode the Skip.
 The Message Type IE is the fourth octet in the message header.
 ","4 bits in the message header indicate the PD, which identifies the upper layer protocol to which the message belongs. Any message shal encode the Skip Indicator which determines whether the message shall be ignored or not."
419," For authentication vectors with the Separation bit set to 1, the secret keys CK and IK generated during AKA do never leave the HSS.
 The proposed procedure does not require any changes to current USIMs and keeps AuC changes small.
 Furthermore, we assume that the changes amount to a configuration of the AuC.
 The mechanism assumes that not all bits of the AMF are already in use for proprietary purposes.
 There is some evidence that, in fact, AMF is currently not used at all. The 16 bit Authentication Management Field AMF is inserted into the authentication token AUTN in an authentication vector (AV) by the AuC during AKA in the clear.
 ",The Separation bit determines whether the authentication vector is usable in an SAE context or a non-SAE context only. The mechanism assumes that not all bits of the AMF are already in use for proprietary purposes.
420,"A UE may be in communications with multiple SCSs in an HPLMN which can be made up of a combination of operator controlled and MTC service provider controlled SCSs.
Though not illustrated, it is also possible that the deployment of an AS may be inside the operator domain and under operator control.
The MTC-IWF uses the UE capabilities, serving CN node(s) capabilities retrieved from the HSS to select a suitable serving CN node capable of T5 triggering.","A UE may communicates with multiple SCSs in an HPLMN, both operator controlled and MTC service provider controlled. The deployment of an AS may be inside the operator domain and under operator control."
421,"It is a challenge response protocol and the AuC in the Home Stratum derives the challenge.
 A Quintet containing the challenge is sent from the Home Stratum to the Serving Network.
 The Quintet contains the expected response XRES and also a message authentication code MAC.
 The Serving Network compares the response from the UE with the XRES and if they match the UE has been authenticated.
 The UE calculates an expected MAC, XMAC, and compares this with the received MAC.",It is a challenge response protocol and the AuC in the Home Stratum derives the challenge. The challenge is sent from the Home Stratum to the Serving Network which compares the response from the UE with the XRES. If they match the UE has been authenticated.
422,"From SIB2 UEs get information about configuration about After getting RACH configuration UE sends RACH Preamble, the UE first calculates its RA-RNTI from the transmission time.
 It looks then in the NPDCCH for the DCI N1 scrambled with the RA-RNTI to get the Random Access Response.
 The UE expects this message within the Response Window, which starts 3 SFs after the last preamble SF If Random Access Response message is not received, the UE transmits another Preamble.
 This is done up to a maximum number of attempted depending on the CE level.
 If the total number of access attempts is reached, an associated failure is reported to the RRC Layer.
 If RACH is successful, the UE gets in a temporary C-RNTI, timing advance command in RAR.
 Further, the RAR provides the UL grant for msg3, containing all relevant data for msg3 transmission.
 The remaining procedure is done like in conventional LTE.","After getting RACH configuration UE sends RACH Preamble. The UE first calculates its RA-RNTI and then waits to get the Random Access Response within the Response Window. After attempting this a maximum number of times, an associated failure is reported to the RRC Layer. If RACH is successful, the UE gets in a temporary C-RNTI. The RAR then provides the UL with all relevant data for msg3 transmission. The procedure continues as in conventional LTE."
423,"Two cases exist i) the initial or standalone request contains a P-Asserted-Identity header field.
 This is typically the case when the user is located the AS is aware of the identity of the user and no extra actions are needed.
 The AS shall consider the request as authenticated; and ii) the initial or standalone request does not contain a P-Asserted Identity header field.
 This is typically the case when the user is case, the AS does not have a verified identity of the user.
 The AS shall check the From header field of the initial or standalone request.
 If the From header field value in the initial or standalone user and the request are considered as anonymous and no further actions are required.
 ","Two cases exist for the initial or standalone request:
i) it contains a P-Asserted-Identity header field and it's considered authenticated.
ii) it does not contain a P-Asserted Identity header field and the AS shall verify the user identity (can be considered as anonymous)."
424," High reliability is about providing high likelihood of delivering error free packets through the 3GPP system within a bounded latency.
 A performance metric for high reliability is the ratio of successfully delivered error free packets within a delay bound over the total number of packets.
 The required ratio and latency bound may be different for different URLLC use cases.
 High availability is related to a communication path through the 3GPP system providing reliable services.
 This communication path between the communication end points is made up of radio links as well as transport links and different HW and SW functions.
 The NR should provide high availability, in addition to deploy redundant components and links for these radio, transport and HW/SW.
 ",The NR should provide high availability and high reliability.
425," The number of carriers per operating band the AAS BS is capable of generating at maximum TRP declared each RAT (and multi-RAT) for every beam identified in D.
 Declared if an operating band is generated using transceiver units supporting operation in multiple operating bands through common active RF components.
 Operating bands with multi-band dependencies List operating bands which are generated by multi-band transceiver units.
 Declared for each operating band for which multi-band transceiver units (D5) have been declared.
 Maximum radiated Base Station RF Bandwidth Maximum Base Station RF Bandwidth in the operating band, declared for each supported operating band identified in D.
 Maximum radiated Base Station RF Bandwidth for contiguous operation Largest Base Station RF Bandwidth for contiguous spectrum operation, declared for each supported operating band (D).
 Maximum radiated Base Station RF Bandwidth for non- contiguous operation Maximum Base Station RF Bandwidth for non-contiguous spectrum operation, declared for each supported operating band (D).
 Declared inter-band CA bands supported per operating band (D).","Information about number of carriers per operating band the AAS BS is capable of generating at maximum TRP, and maximum radiated Base Station RF Bandwidth."
426,"The goal is to make the ANR function in the gNB is disabled.  The Use Case begins when the MnS consumer decides to disable the ANR function in a gNB. 
 The MnS consumer disables the ANR function in the gNB Ends when all steps identified above are completed or when an exception occurs.
 One of the steps identified above fails and retry is unsuccessful.
 The ANR function in gNB is successfully disabled by the MnS consumer, or if unsuccessful, still enabled.
 All existing NCRs, whether created by ANR or otherwise are unaltered.","To disable gNB ANR. Use Case begins when MnS consumer disables gNB ANR.
MnS inhibits gNB ANR. When all steps are finished or an exception occurs.
One of the steps fails, and retrying fails.
MnS consumer disables gNB ANR or leaves it on if unsuccessful.
Existing NCRs, produced via ANR or otherwise, are unaffected."
427,"The vendor-specific MOCs may support new types of attributes. The standardised notifications may be issued referring to the vendor specific MOCs and vendor-specific attributes.
 New MOCs shall be distinguishable from standardised MOCs by name.
 Standardised and vendor specific attributes may be used in vendor-specific MOCs.
 Vendor-specific attribute names shall be distinguishable from existing attribute names MOCs may be subclassed.
 Subclassed MOCs shall maintain the specified behaviour of the superior classes.
 They may add vendor-specific behaviour with vendor-specific attributes.
 When subclassing, naming attributes cannot be changed.
 The subclassed MOC shall support all attributes of its superior class.
 ","Vendor-specific MOCs can add characteristics. Typical warnings include vendor-specific MOCs and characteristics.
New MOCs need unique names.
Vendor-specific MOCs use vendor-standard characteristics.
Subclassing MOCs requires separating vendor-specific from existing attribute names.
Subclassed MOCs must behave well.
Vendor-specific features may be added.
Subclassing stops attribute renaming.
Subclassed MOCs must support superior-class attributes."
428,"In case of E-UTRAN this is the point in time when a corresponding dedicated EPS bearer is established / modified.
 QCI could be used for the prioritization of non real-time data.
 Also at the point in time when the SDF aggregate is authorized.
 Alternatively, this QCI could be used for the default bearer of a UE/PDN for ""premium non privileged subscribers.
 Note that AMBR can be used as a ""tool"" to provide subscriber differentiation between subscriber groups connected to the same PDN with the same QCI on the default bearer located ""close"" to the radio base station (roughly 10 ms) and is not normally used in a long distance, home routed roaming situation.
 ","In case of E-UTRAN, when a corresponding dedicated EPS bearer is established / modified, QCI could be used for non real-time data prioritization and the SDF aggregate can be authorized.
AMBR can differentiate between subscriber groups connected to the same PDN with the same QCI on the default bearer ""close"" to the radio BS."
429,"The MIPv4 initial attach is performed by the UE to establish a MIPv4 connection with the node acting as the HA.
 The initial attach involves the - Discovery of the HA address.
 The UE needs to discover the IPv4 address of the node acting as the HA - Discovery of FACoA.
 The UE needs to discover the IPv4 care-of address provided by the FA - IPv4 home address assignment.
 The UE needs to be assigned an IPv4 address to be used as the home address in Mobile IPv4 FACoA mode.
 The HA is responsible of assigning the home address to the UE - Security association establishment.
 The UE needs to establish a security association with the node acting as the HA in order to secure the MIPv4 signalling.
 ",The MIPv4 initial attach is performed by the UE to establish a MIPv4 connection with the node acting as the HA. The UE needs to discover the information of HA node and establish a security association with it. The HA is responsible of assigning the home address to the UE.
430,"After Iu release the MS and SGSN shall modify the PDP contexts according to the rules defined in clause ""RNC-Initiated PDP Context.
 An RNC can request the release of a radio access bearer.
 After RAB release the MS and the SGSN shall locally modify the corresponding PDP context according to rules defined in the clause ""RAB Release-Initiated Local PDP.
 A trace may be activated while a PDP context is active.
 To enable trace activation in a GGSN, the SGSN shall send an Update PDP Context Request message to the GGSN.
 To enable trace activation in a P-GW, the SGSN shall send an Update Bearer Request message to the S-GW.
 ","After Iu release and RAB release the MS and SGSN shall modify the PDP contexts according to the related rules. For trace activation in a GGSN, the SGSN shall send an Update PDP Context Request message to the GGSN. In a P-GW, the SGSN shall an Update Bearer Request message to the S-GW."
431,"Definition Cell sync burst timing is the time of start (defined by the first detected path in time) of the cell sync burst of a neighbouring cell.
 This measurement is applicable for 4Mcps TDD and 8Mcps TDD.
 For 8 Mcps TDD the DwPCH represents the cell sync burst.
 Type 1 is used for the initial phase of Node B synchronization.
 Type 2 is used for the steady-state phase of Node B synchronization.
 Both have The reference point for the cell sync burst timing measurement shall be the Rx antenna connector.
 ",A cell sync burst timing is the time of start (defined by the first detected path in time) of the cell sync burst of a neighbouring cell. The reference point fo the timing measurement shall be the Rx antenna connector.
432,"The remote locations make these devices more susceptible to tampering by unauthorized persons.
 The tampering of the MTC Device is often accompanied by damage to the metering device.
 The network has security mechanisms for protection for this type of activity which may not be effective for MTC Devices.
 The network can not prevent it but can detect it as early as possible in order theft/vandalism vulnerable MTC Devices are stationary after initial installation and activation.
 The stationality of the MTC Device can be utilized to improve the detection of theft.
 ",The remote locations make MTC devices more susceptible to tampering and metering device damaging by unauthorized persons. The network can detect theft/vandalism as vulnerable MTC Devices are stationary.
433,"The Prohibit Payload Compression indicates that the SGSN should negotiate no data compression for this PDP context.
 If the to add, modify or delete the TFT related to the PDP Context. Configuration Options may contain the BCM as well as optional PDP parameters that the GGSN may transfer to the MS.
 BCM shall also be sent as a separate IE to the SGSN.
 BCM indicates the Bearer Control Mode applicable to all PDP Contexts within the activated PDP Address/APN pair.
 The GGSN shall only indicate Bearer Control Modes allowed according to the NRSN and NRSU previously indicated by the SGSN and MS respectively.
 The SGSN may restrict a desired QoS profile given its capabilities, the current load, the current QoS profile, and the subscribed QoS profile.
 The SGSN shall apply a Negotiated Evolved ARP even if it is different from the Subscribed Evolved ARP.
 The BCM is used by the SGSN to handle unexpected session management signalling.
 If the GGSN determines the active APN-AMBR needs to be modified, the APN AMBR is included in the request message.
 If the modification is triggered by a change of the APN-AMBR only, then only one PDP context associated with that APN shall be modified.
 ","The Prohibit Payload Compression indicates no data compression negotiation for this PDP context. The BCM indicates the applicable Bearer Control Modes, whereas thr GGSN only indicates allowed Bearer Control Modes. The SGSN may restrict a desired QoS profile and apply a Negotiated Evolved ARP even regardless the Subscribed Evolved ARP. The APN AMBR is included in the request message if it requires modifications. Modifications only apply to the associated PDP context."
434,"In the past, operators within a country or a region deployed single system networks and, consequently, users got service from a single system terminal.
 Multi mode terminals were sometimes deployed to maximise coverage, particularly during times of transition between radio access technologies (e.g. cdma/AMPS), but the same core network was always used. In the future it is likely that operators will operate more than one system and the core networks will be different.
 This may happen either through choice or company merger/acquisition.
 There will be cases where operators have different systems in the same geographic area and cases where operators use different systems in different regions.
 It is also likely that there will be roaming agreements between operators of different systems.
 ","In the past, operators deployed single system networks. Multi mode terminals were sometimes deployed to maximise coverage, but the same core network was always used. In the future it is likely that operators will operate more than one system and have different core networks, and there will be roaming agreements between operators of different systems."
435,"After establishing a security association, more services can be advertised which are only available to certain, trusted CCNs.
In order to allow flexibility and efficiency, it is also possible to update the security association after determining the details of the Composition Agreement (CA).
Also, an established Composition Agreement can later be renegotiated. ",Services can be advertised to trusted CCNs accroding to the security association. Composition Agreements (CA) can be renegotiated and the related security association updated. 
436,"Note that there are cases in which the current CA The ASSIGNMENT COMMAND message may contain a cipher mode setting IE.
 In that case, this ciphering mode has to be applied on the new channel.
 If no such information is present, the ciphering mode and the use of Selective Ciphering of Downlink SACCH (see sub-clause a) are the same as on the previous channel.
 In either case the ciphering key shall not be changed as long as the key length remains unchanged.
 However, in case of a switch between ciphering algorithms requiring different key lengths.
 ","The ASSIGNMENT COMMAND message may contain a cipher mode setting IE to be applied on the new channel. If not, the ciphering mode and the use of Selective Ciphering of Downlink SACCH are the same as on the previous channel. The ciphering key shall not be changed as long as the key length is unchanged."
437,"If SRVCC with priority is supported, and the MSC Server receives the priority indication (i.e. ARP) in the SRVCC PS to CS Request, the MSC server/MGW sends Prepare Handover Request message to the Target MSC with priority indication mapped from the ARP.
The MSC Server maps the ARP to the priority level, pre-emption capability/vulnerability for CS services based on local regulation or operator settings.
The priority indication indicates the CS call The MSC Server assigns a default SAI as Source ID on the interface to the target BSS and uses BSSMAP encapsulated for the Prepare Handover. ","When SRVCC with priority is supported, the MSC Server receives the priority indication (i.e. ARP) in the SRVCC PS to CS Request and sends a Prepare Handover Request message to the Target MSC with accoring priority. The MSC Server assigns a default SAI as Source ID to the target BSS interface and uses BSSMAP encapsulated for the Prepare Handover."
438,"The present document describes the functionality of the PDCP Overview on sublayer architecture.
 The radio interface protocol architecture is defined in Every PS domain RAB is associated with one RB, which in turn is associated with one PDCP entity.
 Each PDCP entity is associated with one or two (one for each direction) RLC entities depending on the RB characteristic (i.e.uni-directional or bi-directional) and RLC mode.
 The PDCP entities are located in the PDCP sublayer Every PDCP entity uses zero, one or several different header compression protocols.
 Each individual PDCP entity uses at most one instance of each header compression protocol.
 Several PDCP entities may be defined for a UE with each using the same or a different set of header compression protocols.
 ","The radio interface protocol architecture is defined in Every PS domain. RAB is associated with one RB, which in turn is associated with one PDCP entity. Each PDCP entity is associated with one or two (one for each direction) RLC entities depending on the RB characteristic and RLC mode. PDCP entities are located in the PDCP sublayer Every PDCP entity can use different header compression protocols and at most one instance of each of them. Several PDCP entities may be defined for a UE."
439,"When the list is full and a new PLMN identity has to be inserted, the UE shall delete the oldest PLMN The UE shall store a list of equivalent PLMNs.
 These PLMNs shall be regarded by the UE as equivalent to each other for PLMN selection and cell selection/re-selection.
 The same list is used by EMM, GMM and MM The UE shall update or delete this list at the end of each attach or combined attach or tracking area updating or combined tracking area updating procedure.
 The stored list consists of a list of equivalent PLMNs as downloaded by the network plus the PLMN code of the registered PLMN that downloaded the list.
 When the UE is switched off, it shall keep the stored list so that it can be used for PLMN selection after switch on.
 The UE shall delete the stored list if the USIM is removed or when the UE attached for emergency bearer services enters the state EMM-DEREGISTERED.
 ","The US shall store a list of PLMNs for PLMN selection and cell selection/re-selection. When the list is full, new PLMNs can replace the oldest ones. The UE shall keep the list when switched off, but delete it if the USIM is removed or when the UE attached for emergency bearer services enters the state EMM-DEREGISTERED. The same list is used by EMM, GMM and MM."
440,"The default configuration for a newly deployed gNB is for the ANR function in a gNB to be active for all its cells.
 As ANR might not be wanted for a cell in a gNB, the ANR function can be switched off for that cell. The ANR function, residing in the gNB, automatically adds NCRs to the internal list of NCRs.
 It also has the ability to remove an NCR, for example when the NCR has not been used for handover for a certain amount of time.
 The MnS producer has the possibility to send notifications when an NCR has been added.
 The MnS consumer, receiving this notification might find out that this NCR is not wanted.
 In this case, the MnS consumer can blacklist that NCR.
 Blacklisting consists of marking the NCR as not to be used for handover and marking it sticky, i.e. the ANR function will not time out and not remove the NCR. Conversely, the MnS consumer might find that the ANR function fails to add a wanted NCR.
 In this case the MnS consumer can whitelist that NCR. Whitelisting consists of creating the NCR from the MnS consumer, marking it to be used for handover and marking it sticky.","The ANR function can add and remove NCRs to/from the internal list of NCRs. It is active in newly deployed gNB by default, but can be switched off for each cell. The MnS producer can notify the MnS consumer when an NCR is added. The MnS consumer can whitelist and blacklist NCRs."
441,"If more than 1 uplink and/or 1 downlink TDD timeslot are used for data traffic, that means it will occupy at least 3 time slots, equal to 75*3=05ms.
 And more time slots for traffic data means more switching point are needed to switch between the GSM and the 8Mcps TDD.
 As it was mentioned above, each switching will take ms.
 As a result, the idle time left for monitoring the GSM will be very little.
 So monitoring GSM from 8Mcps TDD under this situation will be considered in the future. ","With more than 1 uplink and/or 1 downlink TDD timeslot for data traffic, it occupies at least 3 time slots (5 ms). More time slots for traffic data means more switching point to switch between the GSM and the 8Mcps TDD, reducing the idle time left for monitoring the GSM."
442," For efficiency reasons, IRPAgent may send multiple notifications using one single push operation.
 To pack multiple notifications into one push operation, IRP Agent may wait and not invoke the push operation as soon as notifications are available.
 To avoid IRPAgent to wait for an extended period of time that is objectionable to IRPManager, IRPAgent shall implement an IRPAgent wide timer configurable by administrator.
 On expiration of this timer, IRPAgent shall invoke push if there is at least one notification to be conveyed to IRPManager.
 This timer is re-started after each push invocation OMG CORBA. Notification push operation is used to realise the notification of Test Management IRP Notifications.
 All the notifications in this interface are implemented using this push_structured_event method A.
 ","For efficiency reasons, IRPAgent may wait and not push notifications as soon as available to later send multiple notifications at once. A timer controls the waiting period. When the timer expires, IRPAgent shall push the notifications if there is any available and reset the timer."
443,"Any HLR/ AuC will deliver triplets to the 3G VLR/SGSN.
 The 3G BSS requires CK and IK, so the VLR/SGSN applies conversion function c3 to generate them from Kc.
 The SIM can only perform 2G AKA and returns SRES, Kc to the ME which also applies c3 to generate CK, IK.
 Despite the usage of CK and IK, security is based on Kc.
 ","Any HLR/AuC will deliver triplets to the 3G VLR/SGSN. The 3G BSS requires CK and IK, the SIM can only perform 2G AKA and returns SRES, Kc to the ME which. Regardless of CK and IK, security is based on Kc."
444,"The CM actions are initiated either as single actions on single NEs of the 3G network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs. 
 The present document defines, in addition to the requirements defined in , and , the requirements for the present IRP: Kernel Configuration Management IRP.
 It is the intent of Kernel Configuration Management to provide an IRP that contains the configuration management functionality that is basic and minimal.
 It is the functionality that is common to and required by both Basic CM and Bulk CM.
 While neither the Basic CM IRP nor Bulk CM IRP requires the other.
 ","The CM actions are initiated either as single actions on single NEs of the 3G network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs. The Kernel Configuration Management provides an IRP that contains the configuration management functionality that is basic and minimal."
445,"The Prefix is contained in the Prefix Information Option of the Router Advertisements and shall have the A-flag set (""Autonomous address configuration flag"") and the L-flag cleared (i.e. the prefix should not be used for on-link determination).
 The lifetime of the prefix shall be set to infinity.
 In practice, the lifetime of a Prefix will be the lifetime of its PDP Context.
 There shall be exactly one Prefix included in the Router.
 The handling of Router Advertisements shall be consistent with what is handling shall apply.
 The randomisation part to determine when Router Advertisements shall be sent may be omitted since the GGSN is the only router on the link.
 Furthermore, some 3GPP specific protocol constants and default values shall apply (see subclause ""Ipv6 Router Configuration Variables in the GGSN"").
 ",A router advertisement can contain one prefix information options. Each prefix information option contains flags that indicate how the prefix can be used. GGSN is the only router on the link which doesnot require any randomisation for sending router advertisemnets.
446," The synchronised procedure is applied in the case when the old and new configurations are not compatible e.g. change of After the CPHY-RL-Modify requests have been confirmed, an activation time is chosen by NW-RRC.
 After deciding upon the activation time, the NW-RRC sends a PHYSICAL CHANNEL RECONFIGURATION message as acknowledged data transfer to the UE.
 In both uplink and downlink this message is sent on DCCH mapped on DCH After reception the UE reconfigures L1 and L2 to DCH resources.
 If a complete message is used it would be sent on DCCH mapped on DCH.
 ",The reconfiguration of L1 and L2 is done by UE based on the activation time chosen by NW_RRC and sending reconfiguration message to UE on DCCH mapped on DCH. 
447,"The same set of services provided by GPRS is available in HSDPA is an enhancement to Packet data services for UTRAN allowing higher data rates on the radio interface downlink.
 The same set of services provided by GPRS is available with GPRS using HSDPA.
 The GPRS can be described using the simplified reference model. GPRS provides data transfer capabilities between a sending entity and one or more receiving entities.
 These entities may be an UE or a Terminal Equipment, the latter being attached either to a GPRS network or to an external data network.
 The base station provides radio channel access for UEs to the GPRS network.
 ",Base Station connects the UE's to the GPRS. The services provided by GPRS are also available in HSDPA which allows for higher data rates between entities.
448,"Measurement shall be performed on a GSM BCCH carrier.
 The reference point for the RSSI shall be the antenna connector of the UE. The received energy per chip divided by the power density in the band.
 If receiver diversity is not in use by the UE, the CPICH Ec/No is identical to CPICH RSCP/UTRA Carrier RSSI.
 Measurement shall be performed on the Primary CPICH.
 The reference point for the CPICH Ec/No shall be the antenna connector of the UE.","CPICH Ec/No is the ratio of the received energy per chip for the CPICH to the total received power spectral density at the UE antenna connector. If receiver diversity is not in use by the UE, the CPICH Ec/No is identical to CPICH RSCP/UTRA Carrier RSSI."
449,"RANAP protocol consists of Elementary Procedures (EPs).
 An Elementary Procedure is a unit of interaction between the RNS and the CN.
 These Elementary Procedures are defined separately and are intended to be used to build up complete sequences in a flexible manner.
 If the independence between some EPs is restricted, it is described under the relevant EP description.
 Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as stand alone procedures which can be active in parallel.
 ",RANAP protocol consists of Elementary Procedures (EPs) which is a unit of interaction between RNS and the CN. The EPs may be invoked independently and can be active in parallel. Any restrictions between EPs are described in relevant EP description.
450,"There are no provisions for the statistical variations that will occur when the parameter is tested.
 The test will result in an outcome of a test variable value for the DUT inside or outside the test limit.
 Overall, the probability of a ""good"" DUT being inside the test limit(s) and the probability of a ""bad"" DUT being outside the test limit(s) should be as high as possible.
 For this reason when selecting the test variable and the test limit(s), the statistical nature of the test is accounted for. The statistical nature depends on the type of requirement.
 Some have large statistical variations, while others are not statistical in nature at all. When testing a parameter with a statistical nature, a confidence level is set.
 This establishes the probability that a DUT passing the test actually meets the requirement and determines how many times a test has to be repeated and what the pass and fail criteria are.
 ",Annex A establishes the variable for the device under test (DUT) and whether it can be viewed as statistical in nature or not.
451,"The lists shall accommodate each 10 or more location area identifications.
 When the list is full and a new entry has to be inserted, the oldest entry shall be deleted In a shared network, the MS shall choose one of the PLMN identities as specified in 3GPP TS 222 .
The MS shall construct the Location Area Identification of the cell from this chosen PLMN identity and the LAC received on the BCCH.
 If the constructed LAI is different from the stored LAI, the MS shall initiate the location updating procedure.
 The chosen PLMN identity shall be indicated to the RAN in the RRC INITIAL DIRECT TRANSFER message.",The MS contructs the lists of Location area identifier of the cell based on PLMN identity and LAC recieved on BCCH. The PLMN identity as specified in 3GPP TS 22 is indicated to RAN in RRC INITIAL DIRECT TRANSFER MESSAGE. The constructed LAI is compared with the stored LAI and is updated accordingly.
452,"This may be based upon one or more default emergency call numbers stored in the ME.
It shall be allowed to establish an emergency call without the need to dial a dedicated number to avoid the mis linkage to a car air bag control.
Emergency calls shall be supported by the UE without a SIM/USIM/ISIM being present.
No other type than emergency calls shall be accepted without a SIM/USIM/ISIM. Emergency calls shall be supported by UEs that are subject to service restrictions, e.g. for UEs camping on a cell in a forbidden PLMN or in a forbidden LA (see 3GPP TS 211\), or on a CSG cell without the subscriber being a member of that CSG.
 ",Only the emergency calls subjected to service restrictions shall be supported by UEs without a need of SIM/USIM/ISIM and dialing a dedicated number.
453,"A broadcast bearer service is efficient when a large number of receivers are expected and the receivers are spread in many cellular areas.
 Major TV or Radio services are examples that may utilize such a broadcast bearer.
 UGC stream may also be transmitted using broadcast bearer if the population of receivers justifies cost for delivering the content.
 Private show of very popular celebrity or daily episodes of small production company may be a potential example.
 Another area of use case is localized broadcast in campus, theatre or theme park.
 Details of the use cases are presented in this document In contrast to broadcast bearer service, UGC will be delivered using multicast bearer service in many use cases.
 Content providers of Personal Broadcast Service may appear and disappear at any time.
 Content distribution may commence on an ad-hoc basis.
 Therefore, it will be inefficient to pre-allocate resources for such unpredictable content providers.
 New interfaces and requirements will be necessary to support such content providers.
 The communication may occasionally be bi directional.
 Interactive data generated by mobile receivers needs to be passed to content providers.",To handle the unpredictable content providers pre-allocating the resources is inefficient and require new interfaces. The use cases regarding the content providers are listed in this document.
454,"Downlink and uplink transmissions are organized into radio frames with 10 ms duration.
 Two radio frame structures are supported - Type 1, applicable to FDD - Type 2, applicable to TDD.
 Each 10 ms radio frame is divided into ten equally sized sub-frames.
 Each sub-frame consists of two equally sized slots.
 For FDD, 10 subframes are available for downlink transmission and 10 subframes are available for uplink transmissions in each 10 ms interval.
 Uplink and downlink transmissions are separated in the frequency domain.
 Each 10 ms radio frame consists of two half-frames of 5 ms each.",Two radio frame structures Type1-FDD and Type2-TDD are supported to handle downlink and uplink transmissions. The radio frames are of 10 ms duration divided into ten equal sized sub frames with each sub frame having a two equal sized slots.
455,"This option proposes to add a new IE ""LCLS-Capability"" in the Assignment Complete message.
 But this is a bit late in the process, the CN may have to do pro-active signalling for LCLS without knowing, if that would ever be This new IE needs to indicate: ""LCLS-Yes"" / ""LCLS-No"".
 Default is ""LCLS-No"" and this is assumed, if the IE is not present.
 oMSC may only start to employ the additional signalling for LCLS, if it knows that the oBSS supports it.
 tMSC may only apply signalling for LCLS, if it knows that tBSS.
 ",The access gateways oMSC and tMSC can accordingly be informed (e.g. by the IE “LCLS-Capability”) the local shortcut is possible and at an early point to employ signalling.
456," The Bearer Address is exchanged on the Nc and Mc interfaces to identify the termination point of the bearer control signalling within the peer Media.
 A Binding Reference is an identity, unique within the scope of one bearer control function, which identifies a bearer network connection.
 This information is exchanged on the Nc and Mc interfaces.
 ","A Binding Reference is an identity, unique within the scope of one bearer control function, which identifies a bearer
network connection. The bearer control function is identified by the Bearer Address being exchanged on the Nc and Mc interface."
457,"Traffic conditioning is performed by policing or by traffic shaping.
 The policing function compares the data unit traffic with the related QoS attributes.
 Data units not matching the relevant attributes will be dropped or marked as not matching, for preferential dropping in case of congestion.
 The traffic shaper forms the data unit traffic according to the QoS of the service. ",The role of traffic conditioner is to perform policing and traffic shaping according to the QoS of the service.
458,"The UE may discontinuously receive MTCH based on scheduling information indicated by the MTCH SCHEDULING INFORMATION.
 This signalling is transmitted on MSCH mapped on SCCPCH carrying MTCH.
 The MTCH SCHEDULING INFORMATION is signalled on each MSCH repetition period.
 The MSCH repetition period and the offset from the cell timing are indicated on MCCH.
 In case of soft combining, the MSCH repetition period is same for all soft combinable S-CCPCH.
 ",The purpose of the signalling flow is to enable UEs to perform discontinuous reception of MTCH.
459,"This primitive is used to send a T-PDU (DATA) by means of a specific GTP-U layer resource (tunnel) identified by the parameter TEID and the IP address where the tunnel is terminated.
 Other info may be conditionally present and transmitted together with T-PDUs A T-PDU (DATA) is received from a GPT-U peer entity and delivered to a user plane entity.
 The T-PDU is associated to the to the PDP or RNC context identified by TEID (that is the Tunnel Endpoint ID).
 Other info may be conditionally present and delivered together with T-PDUs.
 The GTP-U protocol is used to transmit T-PDUs between GSN pairs (or between an SGSN and an RNC in UMTS), encapsulated in G-PDUs.
 A G-PDU is a packet including a GTP-U header and a T-PDU.
 The Path Protocol defines the path and the GTP-U header defines the tunnel.
 Several tunnels may be multiplexed on a single path.
 ",GTP-U Tunnels are used to carry encapsulated T-PDUs and signalling messages between a given pair of GTP-U Tunnel Endpoints.
460,"This technique allows multiplexing of multiple users simultaneously on the same physical channel.
 Orthogonality between multiplexed users is achieved through orthogonal codes.
 More specifically each user repeats its blocks and applies an assigned code sequence that is orthogonal to code sequences assigned to other users.
 The code sequence elements are of unit amplitude and are applied burst-wise, i.e. they correspond to applying a phase shift to each transmitted burst.
 At the receiver side, the received blocks are phase shifted according to the complex conjugate of the same code sequence followed by addition of the received samples.
 This will result in coherent accumulation of the desired signal and cancellation of the others.
 By applying different code sequences on the receiver side, the signals from the different users can be separated.The overlaid CDMA technique is applied to the EC-PDTCH/U and its associated control channel, EC-PACCH/U, and on the EC-RACH.
 ","The overlaid CDMA Technique is used on dedicated channels (EC-PDTCH and EC-PACCH) and can support multiplexing on the same physical channel , simultaneously transmitting, using different orthogonal codes assigned by the network."
461," Some fields such as a name or a postal address may be composed of several sub-fields.
 Each field descriptor belongs to a unique contact manager A contact is composed of a collection of fields.
 Each field belongs to a unique contact, and defines the value assigned to this contact for a unique. The contact manager is also composed of a collection of groups.
 Each group belongs to a unique contact manager, and is an aggregation of contacts that belong to the same contact manager.
 ","The contact manager is composed of a collection of contacts and collection of field descriptors. Each field descriptor defines the properties of a field that all contacts belonging to the contact manager shall have. The contact field is described by its attributes (voice phone number) and its values (name, pnoe number)."
462," Lifecycle management of intent An intent is subject to lifecycle management.
 An intent request is mapped to an expression that can be interpreted by a computer and processed with some input parameters from the request and parameters from the system.
 The intent is an instantiation of the intent expression and the associated parameters.
 This is captured by the system and lifecycle managed.
 ",The intent is an instantiation of the expression and associated parameters from requests and systems. This is captured by system and lifecycle management of an intent.
463,"Table describes the Diameter AVPs defined for the Gx reference point, their AVP Code values, types, possible flag values, whether or not the AVP may be encrypted, what access types (e.g. 3GPP-GPRS, etc.) the AVP is applicable to, the applicability of the AVPs to charging control, policy control or both, and which supported features the AVP is applicable to.
 Bearer-Usage AVP (3GPP-GPRS and 3GPP-EPS access types) The Bearer-Usage AVP (AVP code 1000) is of type Enumerated, and it shall indicate how the bearer is being used.
 If the Bearer-Usage AVP has not been previously provided, its absence shall indicate that no specific information is available.
 If the Bearer-Usage AVP has been provided, its value shall remain valid until it is provided the next time.
 ","The AVP for Gx reference point is described in the table. The Bearer-Usage AVP is of type Enumerated, and it shall indicate how the bearer is being used."
464," The network shall not set the QFI value to Operation code.
 All other values are reserved E bit.
 If the E bit is set to ""parameters list is not included"", the number of parameters field has zero value.
 If the E bit is set to ""parameters list is included"", the number of parameters field has non-zero value.
 If the E bit is set to ""extension of previously provided parameters"" or ""replacement of all previously provided parameters"", the number of parameters field has non-zero value.
 ","The purpose of the QoS flow descriptions information element is to indicate a set of QoS flow descriptions to be used by the UE, where each QoS flow description is a set of parameters and their associated values."
465,"Basic IM CN subsystem originated session between an IM CN subsystem and a BICC CS network during session establishment for an IM CN subsystem originated session.
 The example applies to BICC forward bearer establishment.
 Similar procedures apply to the other four versions of bearer establishment procedure applicable to the BICC CS network.
 The exchange of codec information is identical in all five cases, but there are differences in the sequence of operations associated with bearer establishment within the BICC CS network B.
 BICC forward bearer establishment The MGCF shall select an IM-MGW for the bearer connection before it performs the CS network side bearer establishment.
 This may happen either before sending the IAM or after receiving the APM message.
 In the latter case, the IM-MGW selection may be based on a possibly received MGW-id from the succeeding node B.","The interworking of codec negotiation between a BICC CS network and an IM CN
subsystem during session establishment for a BICC CS network originated session happens through the MGCF – IM-MGW interaction during interworking of codec negotiation.  "
466,"After the UE-A received both the 200 OK response and the talk burst confirm message, UE-A may send media data to PoC AS (A) using a PDP context. The UE-A acknowledges the 200 OK.
 UE-A may establish an additional PDP context for media and talk burst control exchange with same IP address and APN as of the PDP contexts of step 3, e.g. a PDP context with traffic class streaming and bandwidth required for the negotiated media parameters.
 If the UE received an authorization token in step 19a, it inserts it in the PDP context signalling 23a.
 The IMS Core (A) forwards the acknowledgement to PoC AS (A) 24a.
 The PoC AS (A) buffers the received media until a positive response from UE-B is received 25a.","The steps for establishing PoC communication the UE-A sends media data only after it recieves the confirmations messages and OK response. For carrying this, out UE needs the authorisation token and then only build PDP comtext for media followed by IMS core (A) forwarding the acknowledgement to PoC."
467," This scenario describes the provision of capabilities of the NGN to support end users attached to an NGCN.
 In this case the NGCN operator has a service level agreement with the IMS operator.
 Services are provided to the private extensions behind the NGCN using the NGCN.
 The NGCN sites interface to the NGN using SIP as the control protocol Intelligent routeing tables at the routeing function are used to provided interface.
 ",This scenario describes the provision of capabilities of the NGN to support end users attached to an NGCN operator having service level agreement with IMS operator.  The NGCN sites interface to the NGN using SIP as the control protocol.
468," If no such information is present, the ciphering mode is the same as on the previous channel.
 In either case the ciphering key shall not be changed as long as the key length remains unchanged.
 However, in case of a switch between ciphering algorithms requiring different key lengths, i.e. 64 or 128 bits, a change from the 64 bit key to the 128 bit key or vice versa. Downlink SACCH shall be able to decode both ciphered and not-ciphered SACCH blocks.
 ","The ASSIGNMENT COMMAND message may contain a cipher mode setting IE which allows the ciphering to be unchanged when the key length remains same. In case of variable key lengths, Downlink SACCH shall be able to decode both ciphered and not-ciphered SACCH blocks."
469,"The end user subsequently requests the transfer of a video to UE-2 by interacting with UE- UE-2 then updates its status to inform the network that it solicits an IUT to be performed to itself.
 In this example, the notification includes the type of media that UE-2 expects to be transferred.
 Alternatively, any other kind of IUT could be requested the same way, e.g. transfer of Collaborative Session Control IUT solicited by a target UE without prior information. An IMS session or a Collaborative Session is set-up, involving at least UE-1 and a remote party.
 In case of a Collaborative Session, UE-1 is the Controller UE.",IUT solicited by a target UE without prior information about the existing sessions.
470,"This message is sent on the CCCH by the network and may identify up to two mobile stations.
 It may be sent to a mobile station in idle mode to trigger channel access.
 It may be sent to a mobile station in packet idle mode to transfer MM information (i.e. trigger of cell update procedure) or to perform an MBMS pre-notification or an MBMS notification.
 It may be sent to mobile stations in idle mode to transfer the segments of an ETWS Primary Notification message.
 The mobile stations are identified by their TMSI/P TMSI or IMSI.
 ",The mobile stations are identified by their TMSI/P TMSI or IMSI. The message sent on CCCH by the network can identify upto two mobile stations. The message can be sent to the mobile station in idle mode to perform different operations.
471,"The total number of RBGs for downlink system bandwidth of is given by where of the RBGs are of size P and if then one of the RBGs is of size.
 The bitmap is of size bits with one bitmap bit per RBG such that each RBG is addressable.
 The RBGs shall be indexed in the order of increasing frequency and non-increasing RBG sizes starting at the lowest frequency.
 The order of RBG to bitmap bit mapping is in such way that RBG 0 to RBG are mapped to MSB to LSB of the bitmap.","In resource allocations of type 0, resource block assignment information includes a bitmap indicating  a bitmap indicates the resource block groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive physical resource blocks (PRBs). Resource block group size (P) is a function of the system bandwidth."
472,"The monitoring key shall be provided in the Monitoring-Key AVP.
The PCRF may provide multiple usage monitoring control instances.
 The PCRF shall indicate if the usage monitoring instance applies to the IP-CAN session or to one or more PCC rules.
 For this purpose, the Usage-Monitoring-Level AVP may be provided with a value respectively set to SESSION_LEVEL or PCC_RULE_LEVEL.
 The PCRF may provide one usage monitoring control instance applicable at IP-CAN session level and one or more usage monitoring instances applicable at PCC Rule level.","In order to provide the applicable threshold for usage monitoring control, the PCRF shall include a Usage-Monitoring-Information AVP per monitoring key."
473,"
 For the purposes of the present document, the terms and definitions given document takes precedence over the definition of the same term, if any, in and the OpenID definitions are originated from .
 In case of conflict Attribute: An attribute is used in the OpenID Attribute Exchange service extension .
 This extension provides a mechanism for moving identity related information between sites.
 An attribute is associated with a Subject Identifier.
 ",An attribute is used in the OpenID Attribute Exchange service extension. The extension is used for exchanging the identity related information between the sites.
474,"Responses do not have replies except when a ""Context Acknowledge"" is required as a reply to ""Context Response"" message as specified in relevant Stage 2 procedures.
 Context Acknowledge is always triggered message and does not have a reply A message whose name ends in ""Command"" is always an initial message.
 If a ""Command"" message fails, the name of the reply message is constructed by replacing ""Command"" with ""Failure Indication"".
 Apart from ""Downlink Data Notification Failure Indication"" message, a ""Failure Indication"" is a Triggered message.
 The ""Failure Indication"" message does not have a reply.","The specifications of initial and triggered messages are defined on whether the messages are trigger message or a response message. The ""Context"" and the ""Failure indication"" are always the trigger messges."
475,"The GGSN(s) update the Address for User Plane and TEID for downlink data and return an Update PDP Context Response.
 The GGSN(s) shall not include a PCO in the Update PDP Context Response if the No QoS negotiation indication is set. The SGSN releases the Iu by sending the Iu Release Command (Cause) message to the RAN.
 This message may be triggered either by an Iu Release Request message, or by another SGSN event (e.g., authentication failure or detach).
 The SGSN shall take the responsibility to release the Iu interface when the UE has no active PDP context, either immediately or after some timeout.
 ","The GGSN update the PDP context response without pCO in case of No QoS negotiation. The PDP context response is generated for updating the Address for User Plane and TEID for downlink data. In case of SGSN, it releases the IU interface when the UE has no active PDP context."
476,"The ranges quoted are the maximum anticipated for DCS1800 operation.
 In rural areas, this implies relatively flat terrain with little foliage loss.
 In urban areas, up to 1 km cells should be supported.
 In each case, an allowance must be made for in-building penetration loss.
 In many situations, however, smaller cells may be used depending on the local conditions of terrain and traffic.","In many situtations, the smaller cells may be used depending on the local conditions of terrain and traffic."
477,"The response body includes the complete representation of the new resource.
This is necessary, since the MnS Producer may have modified or added attributes compared to those received in the creation request.
The name of the object class may or may not be present in the response.
When creating a new resource with POST the target URI identifies the parent resource of the new resource to be created.
The identifier of the new resource is created by the MnS Producer, hence the ""id"" is equal to ""null"" in the POST request.
 ","The identifier of the new resource is created by the MnS Producer and response body includes the complete representation. The resources created with POST, the target URI identifies the parent resource."
478,"If the UE response does not match with the response calculated by the S CSCF, the authentication of the user fails at the S-CSCF.
The S-CSCF shall send a 4xx Auth_Failure message to the UE, via the P-CSCF.
Afterwards both the UE and the P-CSCF shall close the TLS connection and delete the associated TLS session if one was established.
","If the UE response doesn't match the S- CSCF's, user authentication fails.
S-CSCF sends 4xx Auth Failure to UE via P-CSCF.
The UE and P-CSCF must then stop the TLS connection and erase any associated TLS session."
479,"Two cases exist i) the initial or standalone request contains a P-Asserted-Identity header field.
 This is typically the case when the user is located the AS is aware of the identity of the user and no extra actions are needed.
 The AS shall consider the request as authenticated ii) the initial or standalone request does not contain a P-Asserted Identity header field.
 This is typically the case when the user is case, the AS does not have a verified identity of the user.
 The AS shall check the From header field of the initial or standalone request.
 If the From header field value in the initial or standalone user and the request are considered as anonymous and no further actions are required.",The user identity verification at AS is done on the basis of initial and standalone requests with or without P-Asserted header field.
480,"The vendor-specific MOCs may support new types of attributes. The 3GPP SA specified notifications may be issued referring to the vendor specific MOCs and vendor-specific attributes.
 New MOCs shall be distinguishable from 3GPP SA5 MOCs by name.
 3GPP SAspecified and vendor specific attributes may be used in vendor-specific MOCs.
 Vendor-specific attribute names shall be distinguishable from existing attribute names NRM MOCs may be subclassed.
 Subclassed MOCs shall maintain the specified behaviour with vendor-specific attributes.
 When subclassing, naming attributes cannot be changed.
 The subclassed MOC shall support all attributes of its superior class.","The models and IDL definitions provided in the present document can be extended for a particular implementation, and still remain compliant with 3GPP SA5’s specifications."
481," The idea of locating DUT into center provides a possibility to create a radio channel environment where the signal can arrive from various possible directions simultaneously to the DUT.
 This is the key aspect of the wideband MIMO radio channel models implemented today.
 The proposed test setup is composed of a transmitter, a multidimensional radio channel emulator, an anechoic chamber equipped with OTA antennas and a DUT with multiple antennas.
 The crucial challenge is to generate realistic angular and polarization behavior within the anechoic chamber.
 The family of geometry-based stochastic channel models (GSCM) is well suitable for MIMO OTA testing.
 The GSCM include 3GPP SCM, SCME, WINNER and IMT-Advanced channel models.
 This angular and polarization behavior creates appropriate correlation at the DUT antennas.
 The correlation is defined implicitly via the per-path angle of arrival and real antennas.
 ","The MIMO OTA test setup is composed of a number of OTA chamber antennas, a multidimensional fading emulator, an anechoic chamber, communication tester / BS emulator and a device under test (DUT). The following figure depicts an example of the OTA concept."
482,"The UE shall find cell 2 to be more suitable for service and hence perform a cell reselection.
 After the completion of cell reselection the UE shall transmits a CELL UPDATE message to the SS on the uplink CCCH of cell 2 and set IE ""Cell update cause"" to ""Cell Reselection"".
 After the SS receives this message, it transmits a CELL UPDATE CONFIRM message, which includes the IE ""RRC State Indicator"" set to ""CELL_FACH"", to the UE on the downlink DCCH.
 UE shall verify that IE ""New C-RNTI"" is not included in the downlink message and shall send a CELL UPDATE message to SS again.
 SS shall then send a CELL UPDATE CONFIRM message which includes a valid IE ""New C RNTI"".
 SS verifies that the UE send UTRAN MOBILITY INFORMATION CONFIRM message.",The mobility test is conducted to confirm that the UE executes a cell update procedure after the successful reselection of another UTRA cell and to confirm that the UE send the correct uplink respond message when executing cell update procedure due to cell reselection.
483,"Several QoS subscriptions may be possible for one user.
 MExE is neither aware nor able to determine or modify the end Clause 9. ""Quality of Service"" defines the necessary functions for a MExE device to accommodate QoS management and provisioning.
 QoS management may be available directly to the MExE executables themselves, or to the MExE.
 Support of quality of service for MExE devices supporting bearers defined QoS aware MExE executables may be executing on the MExE device.
 To ensure correct operation with the QoS provisioning of the bearer network(s) the manager elements.",Quality of Service defines the necessary functions for a MExE device to accommodate QoS management and provisioning and is available in clause 9.
484,"The following clauses describe the additional requirements for the bearer independent CS core network.
 When the Relocation Required message is received, the MSC server requests the MGW to provide a binding reference and a bearer address, using the Prepare Bearer procedure.
 For speech calls, the MSC server shall provide the MGW with the speech coding information for the bearer.
 For non-speech calls the MSC server also provides the MGW with the same PLMN Bearer Capability as was provided at the last access bearer assignment.
 The MSC server uses the Change Flow Direction Procedure to request the MGW to set the Handover Device to initial state.",The requirement for the bearer independent core network starts when the Relocation Required Message is recieved. The requests are sent to MGW by MSC server for binding reference and bearer address. The information for the request and response from MGW are made using the bearer procedure.
485,"This chapter presents a selection of service scenarios, which are used as a basis for the RAB scenarios.
 Only the basic scenarios having impact on the lower layers are considered.
 Because the real time applications have the tightest connection with the lower layers, the real time scenarios are studied more in detail in this document.
 Other scenarios can be derived as combinations of these basic scenarios. Even though these scenarios are for IMS, they are applicable also for non IMS PS scenarios.
Usually, the difference is that in non-IMS cases the IMS signalling stream is left out or replaced by non-IMS signalling stream.",The basic scenarios have impact on the lower layers and real time applications have tight connections with lower layers. These scenarios are discussed in this chapter and use to derive other scenarios for IMS and Non-IMS cases.
486,"Performance requirements for the BS are specified for the measurement channels defined in Annex A and the propagation conditions in Annex B.
 The requirements only apply to those measurement channels that are supported by the base station.
 For FRC8 in Annex 9 and Annex 17 the Non E-DPCCH boosting and E-DPCCH boosting requirement only apply for the option supported by the base station.
 The performance requirements for the high speed train conditions which scenarios defined in Annex B.4A are optional Unless stated otherwise, performance requirements apply for a single cell only.
 Performance requirements for a BS supporting DC-HSUPA or DB-DC-HSUPA are defined in terms of single carrier requirements.
 The requirements in clause 8 shall be met with the transmitter(s) on NOTE: In normal operating conditions the BS is configured to transmit and receive at the same time.","Performance requirements for the BS are specified for the fixed reference channels defined in Annex A and the
propagation conditions in Annex B and only applies to measurement channel supported by BS. The performance requirement for FRC is described in Annex 9 and Annex 17. "
487,"This message contains an ordered list of allowed UIAs in order of preference, and the IK to be used.
 If ciphering shall be started, it contains the ordered list of allowed UEAs in order of preference, and the CK to be used.
 If a new authentication and security key generation has been performed, this shall be indicated in the message sent to the SRNC.
 The indication of new generated keys implies that the START value to be used shall be reset (i.e. set to zero) at start use of the new keys. Otherwise, it is the START value already available in the SRNC that shall be used.","The VLR/SGSN initiates integrity and ciphering by sending the RANAP message Security Mode Command to SRNC.  The message contains list of allowed UIAs and IK to be used, UE's capabilities and ciphering algorithm that is used."
488,"For UL, the best serving cell is chosen based on the least coupling loss.
For DL, due to the large Tx power imbalance (including antenna gains) between the Macro and LPN, the best serving cell is the one with maximum received signal power.
This UL/DL decoupled association is feasible for MTC traffic especially for services without tight delay requirements.
To enable UL/DL decoupled operation either in a UE-transparent or non-transparent manner macro serving cell and potential LPNs may need to exchange information for channel (e.g. RACH, PUSCH, SRS) configurations and to identify the suitable LPN.
 ","For deployments that already contain small cells, there may be a benefit to further allow decoupled UL and DL for delay tolerant MTC UEs. UL/DL decoupled association is feasible for MTC traffic especially for services without tight delay requirements. To enable UL/DL decoupled operation either in a UE-transparent or non-transparent manner, macro serving cell and potential LPNs may need to exchange information."
489,"The conference bridge then has the shared secrets it needs to communicate securely with IMS UE-A, IMS UE-B and IMS UE-C respectively communicate securely with the KMS, e.g. using NDS/IP Key distribution for conference calling.
 This solution does not apply to the case where the protection is required between the end user and the access edge.
 For the sake of simplicity the random number used in each message to prevent replay attack is omitted in the message diagram Message flow for end-to-middle scenario 1a.
 User A bootstraps with KMS to establish a shared key Ka.
 If GBA is not support, User A can use other authentication method to get shared 1sg.
 Secure Gateway(SGW) establish a secure connection with KMS by Ipsec TLS or any other authentication method by which KMS and SGW can have a 1sm.
 ","The message flow for end-to-middle scenario requires Secure Gateway(SGW) establish a secure connection with KMS by Ipsec, TLS or any other authentication method by which KMS and SGW can have a shared secret Key. A typical end-to-middle scenario where a call takes place between an IMS end user and a PSTN end user. This solution does not apply to the case where the protection is required between the end user and the access edge. "
490,"After processing this request the S-CSCF shall include the ICID and the charging function addresses received from the HSS in the outgoing message.
 The charging function addresses identify on-line, and off-line charging entities in the home network.
 It is implementation dependent how IMS related entities such as P-CSCF in the visited network get the local CCF or AAA addresses in the case that the P-CSCF is located in the visited network.
 Charging function addresses may be allocated as locally preconfigured addresses.
 If this message is sent outside the home network, S-CSCF shall include Inter Operator Identifier (IOI) that identifies the home network into the message.
 IOI is globally unique identifier for using inter operator accounting purposes.
 The response to the outgoing message may contain a separate IOI that identifies the home network of the called party.
 The S CSCF shall retain either IOI in the message when contacting the Application Servers.","In registration processing, a S-CSCF may send a third party REGISTER to an application server, where the ICID, IOI and charging function addresses are included in the message."
491,"Signaling information can be different on the up and down links. Frequency hopping: The greatest quality benefits of AMR will be achieved when frequency hopping is applied.
 Without it, the benefits may be reduced especially for slow moving or stationary mobiles. Power control: It shall be possible to operate power control independently of the AMR adaptation.
 However, operators may choose to optimize the AMR control according to the power control settings.
 Fast power control may also be introduced provided that the measurement reports are transmitted in band for AMR codec adaptation control. TFO: The AMR codec shall support Tandem Free Operation.
 TFO shall not decrease the capacity gain achievable using the AMR codec DTX: The AMR codec shall support DTX operation.
 ","A number of constraints to the AMR codec design have been identified including Codec signalling, Frequency hopping, power control, TFO and DTX."
492,"The averaged LSP vector is then calculated as where is the length of CN averaging period.
 The outlier-removed LSP vector average is considered the best representation of the short-term spectral envelope of the background noise.
 It is converted to the LSF representation LP-CNG CNG-LSF quantization for low-band signal. The quantization of the LSF vector follows the procedures used for the LSF vector within the ACELP block.
 They are described in subclause The quantization is done with a two stage quantizer.
 The first stage consists of a non-predictive, non-structured, optimized VQ codebook.
 "," The quantization of the LSF vector follows the procedures used for the LSF vector within the ACELP block hat are described on subclause. The outlier in the LSP vector is removed for best representation of the short-term spectral envelope of the background noise, this is converted to LSF representaion."
493,"Each fill bit shall be set to a random value when sent by the mobile station.
 Except for the first octet containing fill bits which shall be set to the binary value ""00101011"", each fill bit should be set to a random value when sent by the network.
 Otherwise, the network shall set all octets containing fill bits to the binary value ""00101011"". The address field may consist of a variable number of octets.
 However, for applications on control channels the field consists of only one octet.
 The address field identifies the SAP for which a command frame is intended and the SAP transmitting a response frame.
The control field consists of one octet.
The length indicator field may consist of a variable number of octets. However, for applications on control channels the field consists of only one octet.","The frame structure for peer communication consists of frame delimination fill bits and address fields. The value of the first octet is filled with binary value ""00101011"" by the network if no random value is filled. The address field contains variable number of octets which decides the type of frame and its purpose."
494,"In this case each cell may be associated to 0 or 1 Real Time Difference parameter.
 The Real Time Difference parameters may be received before the corresponding GSM Neighbour Cell list.
 The parameter Cell_Index_Start_RTD in each structure indicates the index of the cell in the GSM Neighbour Cell list to be taken as a starting reference.
 A sub-structure is included for each GSM Neighbour Cell referenced.
 Each of those sub-structures indicate if 0 or 1 RTD parameter is present for this GSM Neighbour Cell.
",GPRS real time difference is associated with the GSM Neighbour Cell list. The starting index is take as a starting reference for GSM neighbour cell list. The value in all structure or sub-structure decides the presence of a parameter for the GSM neighbour cell.
495,"Depending on the particular deployment scenario (e.g., suburban, urban, dense-urban), the HNB can have different coverage radius (i.e., link budget).
 For example, in a suburban scenario, the HNB coverage can be 100dB whereas a lower HNB coverage radius (e.g., 70dB) may be more suitable for dense-urban deployments.
 It is seen that in the cell edge scenario, using high HNB Tx power results in poor CPICH Ec/No for the MUE.
 On the other hand, when HNB is close to the macrocell site, a low HNB Tx power results in poor CPICH Ec/No for the HUE.
 As the HNB Tx power increases, the MUE CPICH Ec/No degrades.
 ",The HNB transmit power needs to be adjusted properly to maintain an acceptable performance for HNB which is dependent of the deployment scenarios.
496,"The value of the length gives the number of octets in the IE following the length and element identifier.
 Where the length is encoded using more than one octet, the high order bit is bit 8 of the first (lowest numbered octet) and the low order bit is bit 1 of the last (highest numbered octet).
 When a length has a range of M to N octets, the notation ""M-N"" is used.
 The symbol ""n"" represents the maximum of a range when indefinite c) sub-clauses specifying conditions for IEs with presence requirement C or O in the relevant message.
 Together with other conditions specified what non-presence of such IEs means, and (for IEs with presence requirement C) the static conditions for presence and/or non-presence. "," It defines the structure of the messages of the SMLC-BSS layer including the information of octet, conditions for presence of IEs, messages and more information that is described in sub-clause. The SMLC and BSS also exchange the location related message."
497," The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415) if not otherwise.
 The Visited-Network-Identifier AVP is of type Octet String.
 This AVP contains an identifier that helps the home network to identify the visited network (e.g. the visited network domain name). The Public-Identity AVP is of type UTF8String.
 This AVP contains the public identity of a user in the IMS.
 The syntax of this AVP corresponds either to a SIP URL (with the format defined in IETF RFC 3261 and IETF RFC 2396 ) or a TEL URL (with the format defined in IETF RFC 3966).
 Both SIP URL and TEL URL shall be in canonical form, as described in 3GPP TS 203 The Server-Name AVP is of type UTF8String.
 This AVP contains a SIP-URL (as defined in IETF RFC 3261 and IETF RFC 2396), used to identify a SIP server (e.g. S-CSCF name). The Server-Capabilities AVP is of type Grouped.
 This AVP contains information to assist the I-CSCF in the selection of an S-CSCF.
 ","In the specification Diameter AVPs defined by 3GPP for the Cx interface protocol, their AVP Code
values, types, possible flag values and whether or not the AVP may be encrypted are listed."
498,"It then pages the MS using the GA-RRC PAGING REQUEST message.
 The message includes the TMSI, if available in the request from the MSC; else it includes only the IMSI of the MS.
 The message includes the CN Domain identity (CS or PS) The MS responds with a GA-RRC INITIAL DIRECT TRANSFER message containing the Paging Response message.
 The message includes the CN Domain identity (CS or PS).
 The CS domain GA-RRC sublayer entity in the MS transitions to the GA-RRC-CONNECTED state The GANC establishes an SCCP connection to the MSC.
 The GANC then forwards the paging response to the MSC using the RANAP Initial UE Message.
 ","The procedure in this clause assumes the MS is in GAN Iu mode, i.e.,it has successfully registered with the GANC and GA-RRC is the serving RR entity for CS services in the MS. "
499,"Alarm filtering can be applied in the following cases - It is applicable to alarms emitted by IRPAgent via AlarmIRPNotifications.
 IRPManager supplies alarm filter constraint via the subscribe method.
 This filter is effective during the period of - It is applicable to alarms returned by IRPAgent via the out parameter of get_alarm_list method.
 IRPManager supplies alarm filter constraint via the get_alarm_list method.
 This filter is effective only for this - It is applicable to the calculation of alarm counts returned by IRPAgent via the out parameters of get_alarm_count method.
 IRPManager supplies alarm filter constraint via the get_alarm_count method.
 This filter is effective only for this method invocation. This SS shall use of filter constraint grammar specified by reference OMG Notification Service.
 The name of the grammar is called ""EXTENDED_TCL"".
 ",IRPAgent shall optionally support alarm filtering based on IRPManager’s supplied alarm filter constraints. Alarm filtering is applicable for cases where i) alarms emitted by IRPAgent via AlarmIRPNotifications ii)  alarms returned by IRPAgent via the out parameter of get_alarm_list method iii) calculation of alarm counts returned by IRPAgent via the out parameters of get_alarm_count method.
500,"The maximum is with respect to channel length and time lag due to an unsynchronized interfering training sequence.
 Consider the received signal during the training period from user ""k"" and interferer ""p"" where hk and hp denotes the channel of interest and interfering channel respectively.
 Given the received vector R, the least squares estimate of hk is given by where the error includes the contribution not captured by the model, i.e thermal noise, model error, etc.
 The training sequences should be selected such that the energy leaked from an interfering signal is minimized.
 Assume a one branch receiver and that the covariance of the channel hp is equal to identity (corresponding to independent and identically distributed taps).
 The expression is normalized with respect to the channel length and scaled in the same way as the SNR-degradation.
 If the interfering signal is unsynchronized, the sequences do not completely overlap.
 The error due to the interfering training sequence only depends on the overlapping part. This means that the non-overlapping parts of the sequences need to be between user ""k"" and interferer ""p"".
 Note that the least squares algorithm still remains the same, therefore the factors are unchanged.
 ","The training sequence must be selected based on energy leakage , SNR degradation, training period and the interferer. The errors in the training sequences are affected by the overlapping and non-overlapping of sequences between user and interferer. "
501,"One SA pair is for traffic between a client port at the UE and a server port at the P-CSCF and the other SA is for traffic between a client port at the P-CSCF and a server port at the UE.
 The integrity key IKESP is the same for the two pairs of simultaneously established SAs.
 The integrity key IKESP is obtained from the keying material established as a result of the AKA procedure. The integrity key expansion on the user side is done in the UE.
 The integrity key expansion on the network side is done in the P-CSCF. The anti-replay service shall be enabled in the UE and the P-CSCF on all. The Hiding Mechanism is optional for implementation.
 All I-CSCFs/IBCFs in the HN shall share the same encryption and decryption key Kv.",Security mechanism between UE and P-CSCF includes Integrity and hiding mechanism. Hiding mechanism is optional for implementation while integrity mechanism is maintained by generation of integrity key for the two pairs of simultaneously established SAs. 
502,"An authorized MCData user at any time during an ongoing MCData communication decides to release communication.
 The authorized user may decide to release MCData communication with prior indication to the initiator MCData client.
 A prior indication allows initiator MCData client to request for extension for the MCData communication.
 An authorized MCData user is part of the ongoing MCData communication.
 ",The session of MCData Communication can be called for release by authorised user at any time with prior indication to the MCData Client.
503," In soft handovers where the Serving RNS and Iu are relocated, any ongoing positioning process is also aborted on Iu level.
 The MSC, MSC Server or SGSN shall restart the Iu aborted location requests with the new Serving RNC.
 The new SGSN, however shall not restart the location request after inter SGSN Routing Area Update or inter SGSN relocation.
 During intra and inter RNC soft and softer handovers the existing RRC connection can normally be used without any need to abort the on-going positioning process on Iu level.","Soft handovers send RNS and Iu and stop positioning.
MSC, MSC Server, or SGSN restart Iu location requests with the new Serving RNC.
After inter SGSN Routing Area Update or relocation, the new SGSN cannot restart the location request.
Soft handovers can use the existing RRC connection without aborting Iu placement."
504,"If the security functions do not authenticate the MS correctly, the routeing area update shall be rejected, and the new SGSN shall send a reject indication to the old SGSN.
 Only old Gn/Gp SGSNs may forward data to a new SGSN.
 An old Gn/Gp SGSN duplicates the buffered N-PDUs and starts tunnelling them to the new SGSN.
 Additional N-PDUs received from the GGSN before the timer new SGSN.
 N-PDUs that were already sent to the MS in acknowledged mode and that are not yet acknowledged by the MS are tunnelled together with the SNDCP N-PDU number.
 ",The SGSN routing area update is rejected in case security functions do not authenticate. The new SGSN sends rejection indication to old SGSN. The old SGSN duplicates the buffered N PDUs and starts tunnelling them to the new SGSN. The acknowledged and unacknowledged N-PDUs are tunnelled together with the SNDCP N PDU number.
505," The AS can 1) Send the announcement as in-band information 2) Include a reference to the announcement in a 3xx, 4xx, 5xx and 6xx A.
  The network can generate announcement using one of the following 1) using early media i.e. the AS establish an early session and uses that early session to send the in-band announcement; or 2) using an established session i.e. the AS accepts the INVITE request and uses the established session to send the in-band announcement A.
 ",The network can generate announcement as in-band or add reference to announcement using one of the following 1) using early media  or 2) using an established session .
506,"As a network option, the operator may refuse to provide the requested information. When gsmSCF processing is complete the call control is returned to the GMSC server .
 The GMSC server interrogates the HLR in order to determine his current location.
 The HLR shall create an HLR interrogation record. The GMSC server routes the call to the VPLMN in which subscriber ""B"" is currently located.
 The GMSC server shall create an outgoing gateway record for accounting purposes.
 The GMSC server shall also create a roaming record.
 ","The incoming call to a roaming subscriber is handled by CAMEL in several steps that involves the call control handled by GSm server after the gsmSCF processing is complete. The GSM server generates terminating CAMEL record, interrogates HLR for current location, routes the call to VPLMN, creates an outgoing record and create a roaming record."
507,"Each of the types - First, Subsequent and Last segment - is used to transfer segments of a master information block, scheduling block or a system information block.
 The segment type, Complete, is used to transfer a complete master information block and complete scheduling block. Each segment consists of a header and a data field.
 The data field carries the encoded system information elements.
 The header contains the following - The number of segments in the system information block (SEG_COUNT). This parameter is only included in the header if the segment type is - SIB type.
 The SIB type uniquely identifies the master information block, scheduling block or a system information block - Segment index.
 ","Three types, i.e., First, Subsequent and Last segment, are used to transfer segments of a block and each segment consists of two parts, i.e., a header and a data field."
508,"The SL-DCH physical-layer model is described based on the corresponding SL-DCH physical-layer-processing chain.
 Processing steps that are relevant for the physical-layer model.
 in the sense that they are configurable by higher layers, are highlighted in blue.
 It should be noted that, in case scheduled resource allocation of SL-DCH, the scheduling decision is fully done by network side.
 The sidelink transmission control in the UE configures the sidelink physical-layer processing, based on sidelink transport-format and resource-assignment information received on the downlink.
 In case UE autonomous resource selection of SL-DCH, the scheduling decision is done by UE side.
 ","The scheduling decision is done by the network side in case of scheduled resource allocation of SL-DCH, but by UE side in case of UE autonomous resource selection. "
509,"Thereafter based on the measurement reports and network selection criteria the E-UTRAN network would indicate to the UE to initiate the handover procedure to switch over to the target WiMAX network.
 This message could include target WiMAX network information and any other specific parameters required by UE to conduct the handover procedure.
 The UE would then initiate WiMAX specific handover signaling to prepare the target network while continuing to maintain the current connections and send and receive data over the E-UTRAN radio.
 The WiMAX handover signalling is transparent to E-UTRAN.
 The E_UTRAN network may receive the status of ongoing handover operation.
 Once the target preparation is complete the UE would receive the Handover Preparation Complete indication from WiMAX ASN over the tunnel.
 This would then be an indication to turn off the E-UTRAN radio and switch over to WiMAX radio.","To switch over from E-UTRAN network to WiMAX network, the UE first initiates WiMAX specific handover signaling and then receives the Handover Preparation Complete indication to turn off the E-UTRAN radio and switch to WiMAX radio."
510,"In the TDD mode the physical channels are also characterized by the timeslot and additionally, the E-HICH is further defined by a specific orthogonal signature sequence.
 For 8Mcps TDD, the E-HICH can be also further defined by a group of orthogonal signature sequences.
 The physical layer is Service provided to higher layers. The physical layer offers data transport services to higher layers.
 The access to these services is through the use of transport channels via the MAC sub-layer.
 The physical layer is expected to perform the following functions in order to provide the data transport service.
 ","The physical layer is used to offer data transport services to higher layers. In the TDD mode,  the physical channels are characterized by the time slot. The E-HICH is defined by a specific orthogonal signature sequence and also by a group of orthogonal signature sequences in 8Mcps TDD. "
511,"An UpLink Traffic Flow Template (UL TFT) is the set of uplink packet filters in a TFT.
 A DownLink Traffic Flow Template (DL TFT) is the set of downlink packet filters in a TFT.
 Every dedicated EPS bearer is associated with a TFT.
 A TFT may be also assigned to the default EPS bearer.
 The UE uses the UL TFT for mapping traffic to an EPS bearer in the uplink direction.
 The PCEF (for GTP-based S5/S8) or the BBERF (for PMIP-based S5/S8) uses the DL TFT for mapping traffic to an EPS bearer in the downlink direction.
 The UE may use the UL TFT and DL TFT to associate EPS Bearer Activation or Modification procedures to an application and to traffic flow aggregates of the application.
 Therefore the PDN GW shall, in the Create Dedicated Bearer Request and the Update Bearer Request messages, provide all available traffic flow description information.
 ",The PDN GW should provide all available traffic flow description information as the TFT can be used for multiple purposes in multiple situations.
512,"In the case of a radio link failure, the release time is the time at which the failure was detected by the MSC. For unsuccessful call attempts the Seizure time is mandatory.
The Release time is optional and the call duration recorded is the call holding time i.e. the difference between the two. For successful calls the Answer time is mandatory and both the Seizure and Release times are optional.
The call duration recorded is the chargeable duration i.e. the difference between the Answer and Release time stamps.","For unsuccessful call attempts, the Seizure time is mandatory, the release time, which is optional, is the time at which the failure was detected by the MSC, and the call duration is the call holding time. For successful calls, the answer time is mandatory and both Seizure and Release time are optional, in which the call duration is the chargeable duration. "
513,"Similarly, if the AOC parameters are changed during the call then the change time recorded for a subscriber with AOC charging level is the receipt of the FACILITY message from the MS.
 For a subscriber with AOC information level the change time recorded is the time at which the FACILITY is sent to the MS.
 Finally, in case of call re establishment the answer time is the time at which the new traffic channel is allocated by the MSC.","If the AOC parameters are changed during the call, the change time for a subscriber with AOC charging level is the time at which the FACILITY message is received from the MS, the change time  for a subscriber with AOC information level is the time at which the FACILITY is sent to the MS, and the answer time for call re-establishment is the time at which the new traffic channel is allocated by the MSC."
514,"Other AVPs from existing Diameter Applications except for the AVPs from Diameter Base Protocol, do not need to be supported.
The AVPs from Diameter Base Protocol are not included in table , but they are re-used for the Rx protocol.
Unless otherwise stated translated to Diameter AVPs as described in RFC 4005 with the Table : Rx re-used Diameter AVPs.
Attribute Name Reference Comments Applicab Called-Station-IRFC 4005 The PDN the user is connected Rel8 Final-Unit-ActioRFC 4006 The action applied by the PCEF Rel8 cover the service cost.
Framed-IP-AddresRFC 4005 The valid routable IPv4 address s that is applicable for the IP Flows towards the UE at the PCEF.
The PCRF shall use this address to identify the correct binding.
","Other AVPs from existing Diameter Applications are optional.
Diameter Base Protocol AVPs are used for Rx.
Rx reused Diameter AVPs from RFC 4005.
Called-Station-IRFC 4005 Final-Unit-ActioRFC 4006 PCEF Rel8 covers fees.
Framed-IP-AddressRFC PCEF UE IP Flows routable IPv4 addresses.
This address helps the PCRF bind."
515," The MCE initiates the procedure by sending the MBMS SCHEDULING INFORMATION message to the eNB.
 If PMCH configuration information is contained in this message, the eNB shall do PMCH transmission according to the PMCH configuration information.
 If PMCH configuration information for an existing PMCH is not contained in this message, the eNB should stop PMCH transmission for the PMCH.
 The eNB shall store the MBSFN Area Configuration Item IE, and apply the MCCH update from the modification period defined in the MCCH Update Time IE.
 The eNB shall schedule the MBMS services in the MCCH according to the order defined in the MBMS Session List per PMCH IE.
 ","The MCE initiates the procedure by sending the MBMS SCHEDULING INFORMATION message, and then the eNB decides to do PMCH transmissions based on the message, updates MCCH update time IE and schedules the MBMS services."
516,"Successful operation The eNB initiates the procedure by sending a PWS FAILURE INDICATION message to the MME.
 On receipt of a PWS FAILURE INDICATION message, the MME shall act as defined in TS 241.
 The purpose of the eNB Direct Information Transfer procedure is to transfer RAN information from the eNB to the MME in unacknowledged mode.
 The MME does not interpret the transferred RAN information. This procedure uses non-UE associated signalling eNB Direct Information Transfer ENB Direct Information Transfer procedure.
 ",The eNB initiates the procedure by sending a PWS FAILURE INDICATION message to the MME which will act as defined in TS 241.
517,"If a TRX is designated as being a dedicated BCCH, it shall be allocated to RF channel M.
 All remaining TRXs shall be allocated in the following order; first to RF channel B then to T, then distributed as evenly as possible throughout the BSS operating transmit band.
 Slow frequency hopping shall be disabled. In case of multicarrier BTS the maximum number of supported carriers are active and operating at maximum declared power.
 The carriers are distributed over the maximum supported RF BW as defined in subclause. Peak hold shall be enabled, and the video bandwidth shall be approximately three times the resolution bandwidth.
 If this video bandwidth is not available on the measuring receiver, it shall be the RMS detector mode applies instead.","If a TRX is designated as being a dedicated BCCH, it shall be allocated to RF channel M while the remaining TRXs shall be allocated in order. Moreover, slow frequency hopping shall be disabled."
518,"The operator can use NAT64/DNS64 capability to access to IPvonly services if access to IPv4 services is needed 
 Reference Scenarios for NAT in the EPC IPv6 migration may involve the use of NAT.
 The use of NAT in the EPC raises several issues, in particular as it relates to interactions with dynamic Policy and Charging Control (PCC).
 In this section examines these issues This annex only covers non-roaming scenarios.
 NAT related to roaming scenarios is not being considered in this TR.",The use of NAT in the EPC raises several issues so this annex only covers non-roaming scenarios.
519,"The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only.
 The level of a parameter within the hierarchy of the configuration data is denoted by use of the character "">"" in the parameter description field within each table, one per level.
 Parameters that are at the top most level within the hierarchy have no "">"" character.
 Parameters that have one or more "">"" characters are child parameters of the first parameter above them that has one less "">"" character.
 Parent parameters are parameters that have one or more child parameters.
 Parent parameters act solely as a ""grouping"" of their child parameters and therefore do not contain an actual value themselves.
 they are just containers for their child parameters Each parameter that can be configured online shall only be configured through one online reference point.
 Each parameter that can be configured offline shall only be configured through one offline reference point.
 ","The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only, in which the child parameters have one or more characters "">"" and parent parameters have one or more child parameters."
520,"Management interfaces provide, via specific communication protocols, for the interconnection of NEs and OSs through the DCN.
 Interactions between physical blocks, to exchange management information, are established dynamically at run time and are usually not defined statically at design time.
 In order for such dynamic interactions to occur, physical blocks must be connected by a communications path and each element must support compatible interfaces.
 It is useful to use the concept of an interface to simplify the communications problems arising from a multi-vendor, multi capability network.
 The interface defines the specific protocols, commands procedures, message formats and semantics used for the management communications between physical blocks.",Management interfaces provide for the interconnection of NEs and OSs through the DCN and are used for dynamic interactions between physical blocks.
521," It is inacceptable that the remote UE would change from the EVS AMR-WB IO mode to an EVS primary mode without explicit command by EVS-CMR or a SIP. After a while, the UE moves back into 3G coverage.
 The CS-network performs another Inter-RAT handover, selecting the UMTS_EVS (Set 1) as Target RAN3 Codec.
 Mode Control takes care that the remote end remains in the EVS AMR WB IO mode, until the UE safely landed in the 3G network.","After the UE moves back into 3G coverage, CS-network will perform another Inter-RAT handover and the remote end will remain in the EVS ARM WB IO mode until the UE safely landed in the 3G network."
522,"H4 reference point is similar to Mc reference point i.e. Serving Domain selection influences the termination of Iuh-UP.
 When the serving domain is IMS the Iuh-UP terminates at the HNB-UP-IWF.
 If the serving domain is CS then the Iuh-UP terminates at HNB-GW.
 Iuh-UP termination is a result of the completion of standard call setup - HNB-IM-IWF and HNB-UP-IWF are in the network domain.
 The HNB-IM-IWF is a logical function that terminates NAS control plane from the UE.
 It incorporates one or more of the following functions - Serving Domain Selection Function (S-DSF): S-DSF decides if chosen service domain is IMS or CS for a particular type of service.
 ","Serving Domain influences Iuh-UP termination, like H4 reference point.
IMS-serving Iuh-UP terminates at HNB-UP-IWF.
CS HNB-GW terminates Iuh-UP.
HNB-IM-IWF and HNB-UP-IWF in the network domain terminate Iuh-UP.
UE's NAS control plane is terminated by HNB-IM-IWF.
S-DSF assesses whether a service is IMS or CS."
523,"When the bits assigned for the band are above a pre-determined threshold, as described in subclause, an algorithm for band splitting is activated.
 First the input vector is split into uniform (or close to uniform) segments in a non-recursive way.
 Then angles, which represent the ratio between energies andof a left and a right level segment, are calculated recursively.
 At each iteration, the level segments consist of one or several of the pre-determined segments from the initial split of the input vector.
 The angles are calculated from the top level (full size of the band to be quantized), and continuing towards the levels of shorter sub-vectors, i.e. shorter level segments. The angle is determined from the energy ratio between one left and one right level segment.
 In case of an even number of splits, the left and right level segments will consist of an equal number of segments.
 ","Band bits exceed a threshold, activating a band-splitting algorithm.
Segment the input vector non-recursively.
Determine left-to-right energy ratio angles recursively.
Level segments are vector inputs each iteration.
Top-level (total band size to be quantized) to level segment angles are determined. Angle is determined by level energy ratio.
Even-numbered splits equalize left and right level segments."
524,"The first byte of the extension data gives the number of bytes of the remainder of the MMS notification in this record.
 The following bytes contain the extension of the MMS notification identifier of the next extension record (in EXT8) to enable longer storage of information 
 This EF contains values for Multimedia Messaging Connectivity Parameters as determined by the issuer, which can be used by the ME for MMS network connection.
 ",The first byte of the extension data indicates the number of bytes of the remainder of the MMS notification while the following bytes indicate the extension of the MMS notification.
525," The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement.
 For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRS results of both right and left hand phantom measurements.
 In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified . ",The average measured total radiated sensitivity (TRS) of each measured channel should be lower than the average TRS requirement.
526,"This function is used to explicitly release all resources related to one Iu connection - Requesting the release of all Iu connection resources.
 While the Iu release is managed from the CN, the RNC has the capability to request the release of all Iu connection resources from the corresponding Iu - SRNS context forwarding function.
 This function is responsible for transferring SRNS context from the RNC to the CN for intersystem change in case of packet forwarding - Controlling overload in the Iu interface.
 This function allows adjusting the load in the control plane of the Iu interface - Resetting the Iu.
 This function is used for resetting an Iu interface - Sending the UE Common ID (permanent NAS UE identity) to the RNC.","This function frees Iu connections.
RNC can request Iu connection resource release from the Iu-SRNS context forwarding function.
This function controls Iu interface overload by transferring RNC SRNS context to CN for packet forwarding.
This function resets Iu's control plane load.
Using the UE Common ID, this function resets an Iu interface."
527," This function enables to change the serving RNC functionality as well as the related Iu resources (RAB(s) and Signalling connection) from one RNC to another - Overall RAB management.
 This function is responsible for setting up modifying and releasing RABs - Queuing the setup of RAB.
 The purpose of this function is to allow placing some requested RABs into a queue, and indicate the peer entity - Requesting RAB release.
 While the overall RAB management is a function of the CN, the RNC has the capability to request the release of RAB - Release of all Iu connection resources.","This function moves the serving RNC functionality and Iu resources (RAB(s) and Signalling connection) from one RNC to another.
It queues RAB setup, revisions, and releases.
This function queues and identifies requested RABs.
RNC can seek RAB - Release of all Iu connection resources from CN."
528,"This service is supported by a signalling connection between RNC and CN domain.
 It shall be possible to dynamically establish and release signalling connections based on the need.
 Each active UE shall have its own signalling connection.
 Each MBMS Bearer Service during a given MBMS Session shall have one or several signalling connections.
 The signalling connection shall provide in sequence delivery of RANAP messages.
 RANAP shall be notified if the signalling connection breaks Connectionless data transfer service.
 RANAP shall be notified in case a RANAP message did not reach the intended peer RANAP entity RANAP protocol has the following functions - Relocating serving RNC.",The signalling connection between RNC and CN domain supports the MBMS Bearer Service and RANAP will relocate serving RNC if the signalling connection breaks connectionless data transfer service.
529,"The Barring of all outgoing calls supplementary service will be invoked.
 No CAMEL service for Mobile Originated SMS will be Any originating CAMEL based services shall be invoked before the Barring of outgoing international calls supplementary service. 
 For CAMEL phase 1 based services there shall be no interaction.
 In this case, the interaction between call forwarding and call barring is not modified by CAMEL.
 This means that the interaction is applied prior to the invocation of call forwarding.
 ","Extra service blocks outbound calls.
No mobile CAMEL CAMEL-based services must be invoked before international call barring.
CAMEL phase 1 services are non-interactive.
CAMEL doesn't effect call forwarding or blocking.
Before call forwarding"
530,"The correlation describes relations between network events (e.g. current alarms as those captured in AlarmList, historical alarms as those captured in NotificationLog, network configuration changes). 
 For a set of correlated alarms, one alarm may relate to the fault which is the root cause of all the correlated alarms and events.
 If possible, the OS should perfom a Root Cause Analysis to identify and indicate the Root Cause.
 Root Cause Analysis is a process that can determine and identify the network condition.","Network correlations (e.g. current alarms as those captured in AlarmList, historical alarms as those captured in NotificationLog, network configuration changes).
One alert may cover all associated alerts and incidents.
If possible, the OS should perform RCA.
RCA discovers network faults."
531,"This information is stored by the UE for use when in CELL_FACH state.
 The HS-DSCH DRX operation in CELL_FACH state is only possible when the UE has a dedicated H The HS-DSCH DRX operation in CELL_FACH state is initialized when the inactivity timer expires.
 The inactivity timer is triggered whenever no data transmission activities are ongoing.
 At this point, the UE is shall continuously receive HS-DSCH for the length of the inactivity time configured.
 Once the inactivity timer has expired, the UE may choose not to receive HS-DSCH for a given time within the period of the configured DRX Cycle.
 The UE shall receive HS-DSCH for the RX burst length of the DRX Cycle configured.","The inactivity time is triggered when there are no data transmission activities and when it expires, the HS-DSCH DRX operation in CELL_FACH state is initialized. "
532,"""Measured results"" can be used for both event trigger mode and periodical reporting mode.
 For intra frequency and inter-frequency measurements the list shall be in the order of the value of the measurement quantity (the first cell shall be the best cell).
 The ""best"" FDD cell has the largest value when the measurement quantity is ""Ec/No"" or ""RSCP"".
 On the other hand, the ""best"" cell has the smallest value when the measurement quantity is ""Pathloss"".
 The ""best"" TDD cell has the largest value when measurement quantity is ""Primary CCPCH RSCP"".
 For intra-frequency measurements, the ordering shall be applied to all cells included in the IE ""Measured results"".
 For inter-frequency measurements, the ordering shall be applied to all cells on the same frequency included in the IE ""Measured results"".","""Measured outcomes"" can trigger events and inform reports.
Intrafrequency and interfrequency amounts (the first cell shall be the best cell).
""Best"" FDD cell has high Ec/No or RSCP.
""Best"" cell has low ""Pathloss.""
""Best"" TDD cell has highest CCPCH RSCP.
Sort intra-frequency measurements in ""Measured results.""
""Measured results"" must rank same-frequency cells for inter-frequency measurements."
533,"There is no requirement to store non-retrieved data beyond 48 hours.
 In addition, all logged measurement configuration and the log shall be removed by the UE at switch off or detach. For Logged MDT the measurement reporting is triggered by an on-demand mechanism, i.e. the UE is asked by the network to send the collected measurement logs via RRC signalling.
 UE Information procedure defined in TS 231 and TS 331 and TS 331 is used to request UE to send the collected measurement logs.
 The reporting may occur in different cells than which the logged measurement configuration is signalled. Transport of Logged MDT reports in multiple RRC messages is supported.
 With every request, the network may receive a part of the total UE log.","The measurement reporting for logged MDT is triggered on demand, that is, the network asks the UE to send the collected measurement logs via RRC signalling."
534,"Reception of an OVERLOAD message after T1 but still during T2 will decrease the traffic by one more step and timers T1 and T2 are restarted.
 This step by step reduction of traffic is continued until maximum reduction is obtained. If T2 expires (i.e. no OVERLOAD message was received during T2), the traffic will be increased by one step and T2 restarted.
 This step by step increase of traffic will be continued until full load has been resumed. The number of steps and the method of reducing the load is considered to be implementation dependent.
 For example, the amount of random accesses and thereby access grants can be reduced by use of the RACH Control parameters.","The traffic will be decreased by one more step if an OVERLOAD message is received after T1 during T2, while the traffic will be increased by one step if T2 expires."
535,"MS Time ZoneOC: This field contains the MS Time Zone the MMS User Agent is currently located, if available.
 VAS-Id OC This field indicates the VAS that originated the MM.
 Only present in MM1 Retrieval and if the MM was received over an MM7 interface.
 VASP-Id OC This field indicates the VASP that originated the MM.
 Only present in MM1 Retrieval and if the MM was received over an MM7 interface.
 Record OC A set of network/manufacturer specific extensions to extensions the record.
 ","The MS Time ZoneOC field indicates the currently available MS Time Zone, and the VAS-Id OC field and VASP-Id OC field indicate the VAS and VASP originated the MM respectively."
536,"The SGSN includes this IE in the Update PDP Context Request if the associated Modify PDP Context Request from the MS includes protocol configuration options.
 The SGSN shall copy the content of this IE transparently from the content of the PCO IE in the Modify PDP. The presence of the Common Flags IE is optional.
 If the RAN Procedures Ready bit of the Common Flags IE is set to 1, then SGSN is ready to receive payload on the PDP Context indicated in the message.
 If RAN Procedures Ready bit of the Common Flags IE is set to 0 or the Common Flags IE is absent then the RAN procedures in the SGSN may or may not be ready.
 If the NRSN bit of the Common Flags IE is set to 1, the SGSN supports the network requested bearer control.
 If NRSN bit of the Common Flags IE is set to 0 or the Common Flags. IE is absent then the SGSN does not support network requested bearer control.
 Handling of the Common Flags IE (also the handling of ""No QoS negotiation"" bit in the Common Flags IE) by GGSN is specified in subclause ""Update PDP Context Response"".
 If the Upgrade QoS Supported bit of the Common Flags IE is set to 1, the SGSN supports the QoS upgrade in Response message functionality.","Update PDP Context Request contains Modify PDP Context Request options.
duplicates Change PCO PDP. IE options.
If RAN Procedures Ready is 1, SGSN can accept PDP payloads.
Common Flags IE's RAN Procedures Ready bit must be 1 for SGSN RAN procedures to be ready.
NRSN 1 controls SGSN-requested bearers.
SGSN doesn't manage network bearers if NRSN is 0 or absent.""
PDP-update ""Common IE Flags (including the ""No QoS negotiation"" bit).
Common Flags QoS Upgrade Response messages can be upgraded in IE 1."
537," Master information block is transmitted with updated MIB value tag.
 Then SS transmits a SYSTEM INFORMATION CHANGE INDICATION message to the UE with BCCH mapped on HS DSCH.
 The transmission of BCCH on HS-DSCH is performed by using BCCH specific H-RNTI on the specific HS-SCCH code indicated in system information broadcast.
 The SYSTEM INFORMATION CHANGE INDICATION message shall include the IE ""BCCH Modification Information"" indicating the value tag of the modified master information block.
 ",The SS first transmits the new SYSTEM INFORMATION BLOCK TYPE message and then transmits a SYSTEM INFORMATION CHANGE INDICATION message to the UE.
538,"The IMS Service Profile is a collection of service and user related data as Implicit Registration Set.
 Public User Identities with different Service Profiles may belong to the same Implicit Registration Set.
 Initial filter criteria in the service profile provide a simple service logic comprising of user / operator preferences that are of static nature i.e they do not get changed on a frequent basis.
 It shall be possible to Application servers will provide more complex and dynamic service logic that can potentially make use of additional information not available directly via SIP messages.
  The IMS service profile is defined and maintained in the HSS and its scope is limited to IM CN Subsystem.
 A Public User Identity shall be registered at a single S-CSCF at one time.
 All Public User Identities of an IMS subscription shall be registered at the same S-CSCF.
 The service profile is downloaded from the HSS to the S-CSCF.","IMS Service Profile contains service and user data.
Different Service Profiles may share an Implicit Registration Set.
Initial service filter criteria include static user/operator selections.
Application servers provide dynamic service logic that can use information not available via SIP.
The HSS maintains IM CN Subsystem's IMS service profile.
S-CSCF has one PUI.
The same S-CSCF must register all IMS PUIs.
S-CSCF receives HSS's service profile."
539,"The UE can remain in sleep mode for remaining duration within DRX cycle. For synchronization, one SSB-burst set is assumed for short paging cycle (e.g., 320ms).
 Further, it is assumed that synchronization signal can be located in the same slot as paging-on slot and UE can finish network synchronization before paging monitoring.
 For longer paging cycle, one SSB-burst can still be assumed.
 In addition, to improve synchronization accuracy, the case of two SSB-burst sets is also evaluated.
 In this case, UE needs additional time up to one SSB cycle for SSB reception.
 For paging monitoring, a paging occasion can consist of multiple time slots.
 In the evaluation, it is assumed that one paging occasion consists of one slot.
 On the other hand, one paging cycle consists of one or multiple Paging Frames.
 One Paging Frame may contain one or multiple paging occasion(s) or starting point of a PO.
 ","UE can finish network synchronization before paging monitoring if the synchronization signal is located in the same slot as paging-on slot, otherwise it will need additional time for the SSB-burst."
540,"This parameter is set by the sending application process.
 It represents the Invoke Id of an operation which was received from the remote AE for a specific TC dialogue to which the operation being invoked by the local AE is to be linked.
 This parameter is present only if the original operation invoked by the remote AE is defined as having linked operations.
 The type of local operation invoked must be the same type as one of the operations defined as being linked.
 The value of this parameter is associated with the CAP invocation in an implementation dependent manner.
 It represents the identity of the established TC dialogue which will carry the component services between the local AE and the remote AE.","This parameter, set by the sending application process, represents the Invoke Id of an operation received from the remote AE for a specific TC dialogue which will provide the component services between the local AE and local AE."
541,"To get sufficient statistics it is useful to simulate a system containing at least 9 clusters.
 In a 9 cluster system up to eight co-channel, eight adj.-plus and eight adj.-minus interferers may exist.
 Modelling all these interferers are however computational heavy, and make the simulation work impractical.
 It is hence desirable to minimize the number of modelled interferers, while not sacrificing result accuracy.","It's necessary not only to simulate a system containing at least 9 clusters to get sufficient statistics, but also to minimize the number of modeled interferers to make the simulation practical."
542," The adaptive post-filter is a cascade of three filters: a long-term post-filter, a short-term post-filter, and a tilt compensation filter, followed by an adaptive gain control procedure.
 The post-filter coefficients are updated in every subframe.
 The post-filtering process is organized as follows. First, the reconstructed signal, is inverse-filtered through to produce the residual signal.
 This signal is used to compute the delay and gain of the long-term post-filter.
 The signal is then filtered through the long-term post-filter and the synthesis filter.
 Finally, the output signal of the synthesis filter, is passed through the tilt compensation filter to generate the post-filtered reconstructed signal.","The adaptive post-filter is a cascade of three filters. In order to implement the post-filtering process, the reconstructed signal is first inverse filtered, then filtered through the long-term post-filter and synthesis filter, and finally passed through the tilt compensation filter to generate the post filtered reconstructed signal."
543,"In A/Gb mode, user data transmitted during attach, authentication, and routeing area update procedures may be lost and may therefore have to be retransmitted.
 In order to minimise the need for retransmission, the MS and SGSN should not transmit user data during attach and authentication procedures.
 In case of routeing area update procedures, the user data transfer is allowed with restriction specified in description.
 An MS shall perform a GPRS Attach to the SGSN in order to obtain access to the GPRS services.
 If the MS is connected in A/Gb mode, it shall perform an A/Gb mode GPRS Attach procedure.
 ","The user data transfer is allowed after routing area updates as user data transmitted during attach, authentication, and routing area update procedure may be lost and have to be retransmitted."
544,"System information may be transmitted a number of times with the same content within a modification period, as defined by its scheduling.
 The modification period boundaries are defined by SFN values for which SFN mod m= 0, where m is the number of radio frames comprising the modification period.
 The modification period is configured by system When the network changes (some of the) system information, it first notifies the UEs about this change, i.e. this may be done throughout a modification period.
 In the next modification period, the network transmits the updated system information. Upon receiving a change notification, the UE acquires the new system information immediately from the start of the next modification period.",The modification period is configured by the system throughout one modification period and the updated information will be transmitted in the next modification period.
545,"An ME+ that receives the RAU Accept with no indication to continue using the enhanced security context will fallback to a legacy context with CKS and IKS as keys.
 If the ME+ receives the indication then it continues to use the enhanced security Inter-working with GERAN procedures.
 The procedures for interworking with GERAN are nearly identical to the intra-UTRAN procedures with the two exceptions.
 Firstly at idle Idle mode mobility from UTRAN/GERAN to GERAN to a new SGSN, it is necessary to signal whether the UE ME shall use legacy or session keys as a RAU Complete can be protected.
 This is achieved by sending an Authentication and Ciphering Command using the new indication that was included for UTRAN.","If an ME+ receives the RAU Accept without the indication to use the enhanced security context, it will fallback to a legacy context; otherwise, it will continue to use the enhanced security Inter-working with GERAN procedures which are identical to the intra-UTRAN procedures with two exceptions."
546," On the uplink, the ALC is activated when the MS is transmitting at full power, at the minimum coupling loss.
 The repeater gain is reduced so that the output power is limited to 19 dBm.
 The received signal level at the BTS of -91 dBm is likely to be below the desired level which the MS power control algorithm seeks to maintain.
 Therefore, the MS is likely to remain powered up and the ALC will remain in operation continuously.
 ","After ALC is activated, it is likely to remain in operation continuously as the MS may remain powered up."
547,"An additional digit may be specified if more than one test case is used to achieve the test purpose.
 If an additional digit is required, this probably means that the test prose are not well defined.
 Test steps may optionally use the prefixes pr_ or po_ to indicate that the test step is a preamble or postamble respectively.
 Protocol abbreviations may optionally be used to clarify the scope of TTCN objects, or to resolve conflicts when the same name is required by multiple protocols within the ATS.
 The protocol abbreviation indicates that the object is related to a particular procedure.","If more than one test case is involved, an additional digit and protocol abbreviation can be used."
548,"The MIDP provides a mechanism for MIDlets to persistently store data and later retrieve it.
 The persistent storage mechanism is called Record Management System.
 Record stores are created in platform-dependent locations and are not exposed to MIDlets.
 The record store maintains a version number, which is incremented each time the content of the record store is modified.
 A record store is shared between all MIDlets in a Required and optional MExE APIs. Support of any other Java APIs besides CLDC and MIDP is not mandated in a Classmark 3 MExE device.
 ",The Record Management System is provided for MIDlets to persistently store data and later retrieve it.
549,"A new study item MUROS was agreed at GERAN#36 aiming to improve voice efficiency.
 In this section the orthogonal sub channel (OSC) concept is presented.
 It multiplexes two MSs simultaneously allocated on the same radio resource.
 OSC is applicable for low end handsets, since the concept is relying on GMSK capability of handsets.
 Sub channels are separated by using non-correlated training sequences.
 OSC can considerably increase voice capacity with low impact to handsets as well as to networks.","Orthogonal sub channel (OSC), applicable for low end handsets, multiplexes two MSs simultaneously and can increase voice capacity."
550,"UE A can then prompt the user to initiate a voice call to UE B 6a(Successful case). The RAB Assignment Request message is sent from MSC B to the RNC B, requesting the establishment of a RAB for a Video Call.
 The radio bearer is established between the RNC B and UE B.
 RNC B responds to MSC B with a RAB Assignment Response message.
 Following the allocation of the radio resources, UE B sends an Alerting message to 6b (Failure case). The video call fails because of lack of radio resources on the B side.
 ","In the failure case, the UE B sends an Alerting message because B side lacks enough radio resources requested in Assignment message."
551,"This LI-solution is that whenever the MSC-Servers are aware that a local call needs to be intercepted then they shall not allow the BSS to establish local switching in the BSS.
 There shall not be any specific or implicit indication in the signalling that local switching was stopped or not allowed for lawful interception reasons.
 There may be more than one MSC Servers in the call path and it could be that only one of them has the LI requirement set.
 In this solution the MSC Server with LI activated shall block LCLS from being established.
 For this LI solution there should be no need for the MSC Server to communicate the LI requirement as such to other MSC Servers involved in the call.",LI-solution requires that the BSS should not be allowed to establish local switching whenever the MSC-Servers are aware that a local call needs to be intercepted.
552,"The performance of a DARP Phase 1 receiver is evaluated via system simulations for the various configurations and working assumptions defined in this TR.
 The system simulator provides snapshot system performance using a 19 site, 3 cells/site wraparound layout.
 The simulator completely models both fast and slow fading between each receiver and transmitter.
 However the simulator does not model mobility and handoff.
 ","The system simulator used to evaluate the performance of a DARP Phase 1 receiver completely models both fast and slow fading, but not mobility and handoff."
553,"Termination of periodic reports on the location for one or several users.
TpMobilityStopAssignmentData Specifies how the assignment shall be stopped, i.e. if whole or just parts of the assignment should be stopped. 
 This method is used by the application to query the request set created with periodicLocationReportingStartReq.
 Since a lot of data can potentially be returned (which might cause problem in the middleware), this method must be used in an iterative way.
 Each method invocation may return part of the total set of requests if the set is too large to return it at once.
 ","With the termination method specified in TpMobilityStopAssignmentData, the application can query the request set to terminate periodic reports on the location for one or several users. Due to a large of data, this method should be used in an iterative way and may return part of data."
554,"The SS uses the close UE test loop procedure to start the UE Test Loop function in the UE.
 A prerequisite for UE test loop mode 1, UE test loop mode 2 and UE test loop mode 4 is that at least one bidirectional user plane radio bearer has been established between SS and UE.
 A prerequisite for UE test loop mode 3 is that at least one MTCH has been established.
 The UE shall provide for normal Uu layer 1, layer 2 and RRC functionality while the UE test loop function is active.
 This includes (but is not limited to) handover procedures and normal disconnection of the radio bearer.
 The loopback shall be maintained across handovers, but after radio bearer disconnection, the loopback shall cease to exist.
 ","The close UE test loop procedure is used to start the UE Test Loop function, in which different UE test loop mode has different prerequisites. After the UE test loop function is active, normal Uu layer 1, layer 2 and RRC functionality shall be provided and the loopback shall be maintained until radio bearer disconnection."
555," Information elements are shown as mandatory (M), conditional (C) or optional (O).
 A mandatory information element shall always be present.
 A conditional information element shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent.
 An optional element may be present or absent, at the discretion of the application at the sending entity 
 ","Information elements are shown as mandatory, conditional and optional. Mandatory information means being present, conditional ones means being presented when conditions are fulfilled, and optional information means being present or absent is decided by the application."
556," If an expiry time was included in the request, then the expiry time returned in the response should be less than or equal to that value.
 Once the subscription expires, if the NF Service Consumer wants to keep receiving notifications, it shall create a new subscription in the NF Service Producer.
 The NF Service Producer shall not provide the same expiry time (i.e. a future timestamp) for many subscriptions in order to avoid all of them expiring and recreating the subscription at the same time.","The expiry time in the response should be less or equal to the expiry time in the request. When the subscription expires, it should create a new subscription."
557,"The UE may discontinuously receive MTCH based on scheduling information indicated by the MTCH SCHEDULING INFORMATION.
 This signalling is transmitted on MSCH mapped on SCCPCH carrying MTCH.
 The MTCH SCHEDULING INFORMATION is signalled on each MSCH repetition period.
 The MSCH repetition period and the offset from the cell timing are indicated on MCCH.
 In case of soft combining, the MSCH repetition period is same for all soft combinable S-CCPCH.",MTCH SCHEDULING INFORMATION can indicate the UE receiving MTCH and is signalled on each MSCH repetition period.
558," Generally, the services used in one domain should still work if the user moves to another domain, however, the capabilities of the domain will dictate how the service performs.
 For example, the user will experience a much reduced data rate in moving from services defined for 2G/CSD have no equivalent in IMS (e.g some of the data services).
 It is not possible, therefore to define behaviour for these The UE state (e.g.free, busy, not available etc) should be handled consistently to ensure that incoming and outgoing communications are handled appropriately.
 ",The services used in one domain can work when the user moves to another domain and the capabilities of the domain will determine the service.
559,"In this scenario, there are some overlapped area between two neighbour cell A and cell B.
 This is the usual neighbour cells scenario in EUTRAN.
 The load balancing between cell A and Cell B may be considered.
 Load Balancing could only be carried out for UE located in the overlapping coverage of Cell A and Cell B.
In this scenario, cell-edge UEs like UE A and B belong to different cell and they are assigned the same physical resource block (PRB).
","When the area is between two neighbor cells, the load balancing between two cells may be considered. "
560,"The advantage of such resource limiting is that the traffic and the bandwidth of normal legitimate users is not affected.
 Additionally, mechanisms for identification of UC could be very useful for identifying the appropriate traffic to limit.
 The initial step in IMR-based unsolicited communication prevention is to identify that the given communication is unsolicited.
 Without identification no further action can be taken.
 Once a given communication is identified as unsolicited it should be marked appropriately Marking could be as simple as a means to notify that a given communication is unsolicited.
 Having identified and marked a communication as unsolicited the next step is to react on it.
 ",The resource limiting ensured that legitimate users is not affected. The identification of UC is very useful and ensures that further action can be taken.
561," This sub-clause defines the structure of the RLC/MAC control messages formats for the messages are valid only for the PDCH.
 The format for The RLC/MAC control messages defined in this sub-clause may be used also on DBPSCH and SBPSCH in Iu mode.
 A subset of these messages is used exclusively in Iu mode.
 Messages belonging to that subset are labelled as ""Iu mode only"" in this technical specification A subset of the Iu mode only messages is used exclusively on DBPSCH.
 These messages do not follow the general syntactical rules for the RLC/MAC control messages used on shared channels.
 The error handling defined for shared channels does not apply.
 ",The structure of the RLC/MAC formats is only valid for the PDCH and can be used for DBPSCH and SBPSCH in Iu mode.
562,"For BL/CE UEs, the same scrambling sequence is applied per subframe to the demodulation reference signal associated with MPDCCH for a given block of subframes.
 The subframe number of the first subframe in each block of consecutive subframes.
 For the block of subframes, the scrambling sequence generator shall be initialised with and is the absolute subframe number of the first downlink subframe intended for MPDCCH.
 The MPDCCH transmissions span consecutive subframes, including subframes that are not BL/CE DL subframes where the MPDCCH transmission is postponed.
 The quantities and are configured by higher layers.
 The MPDCCH set to which the MPDCCH associated with the demodulation reference signal belong is denoted.",The MPDCCH transmissions span consecutive subframes. The subframe number of the first subframe in each block of consecutive subframes satisfies that the quantities are configured by higher layers.
563,"Entities in the same layer, but in different systems which must exchange information to achieve a common objective are called ""peer entities"".
 Entities in adjacent layers interact through their common boundary.
 The services provided by the (N + 1)-layer are the combination of the services and functions provided by the (N)-layer and all layers below the (N)-layer Management functions may also be required.
 They may include functions which are common for several layers and are not supported by the services provided by a specific layer.
 Examples of such functions are error reporting, status reporting and management of the operation of certain layers.
 Such management functions do not require that peer-to-peer messages are sent across the MS-BSS interface.",The services provided by the (N + 1)-layer are the combination of the services and functions provided by the (N)-layer and all layers below the (N)-layer Management functions may also be required. Entities in adjacent layers interact through their common boundary.
564,"The DP criteria indicate whether the gsmSSF shall request instructions. The gsmSCF address indicates the address to be used to access the gsmSCF for a particular subscriber.
 The address shall be an E.164 number to be used for routeing.
 A gsmSCF address shall be associated with each DP.
 The Service Key identifies to the gsmSCF the service logic to be used.
 A Service Key shall be associated with each DP criteria.",The Service Key identifies to the gsmSCF the service logic to be used. The DP criteria indicate whether the gsmSSF shall request instructions from the gsmSCF address which indicates the address to be used to access the gsmSCF for a particular subscriber.
565,"The drop strategy may preferably be implemented media aware (i.e.favouring dropping predicted information over non-predicted information and similar techniques), or may be drop-head.
 If the buffer runs empty, the CS side should insert appropriate flag stuffing. A buffer shall be maintained in the direction from the CS to the IMS side.
 The size of the buffer should be kept small enough to allow for a low end-to-end delay, but large enough to conceal most network jitter on the CS side.
 If the buffer overflows, then video bits must be dropped, preferably in a media-aware fashion.
 ","If the buffer runs empty, the CS side should insert appropriate flag stuffing. The size of the buffer should be kept small enough and large enough for different conditions,"
566," If applicable for the IP-CAN type, it will also provide information to indicate whether NW-initiated bearer control procedures are supported, if available.
 The PCRF links the Gx session for the new IP-CAN session with the corresponding Gateway Control Session as defined in the PCEF and BBERF(s) as applicable for the case.
 For case 2a and if IP flow mobility is supported, the PCEF provides, when available, the IP flow mobility routing rules.
 For case 1 and if NBIFOM is supported, the PCEF provides, when available, the NBIFOM support and NBIFOM mode information.","For case 2a and if IP flow mobility is supported, the PCEF provides, when available, the IP flow mobility routing rules. If applicable for the IP-CAN type, it will also provide information to indicate whether NW-initiated bearer control procedures are supported, if available."
567,"This clause specifies the IP flow mobility procedures within a PDN connection.
 In these procedures the UE is assumed to simultaneously connect via a 3GPP access and a WLAN access.
 The UE is using both the accesses for the same PDN connection.
 Subsequently, the UE adds/modifies/deletes/moves between accesses IP flows using DSMIPv6 messages. Non-roaming, home routed roaming and Local Breakout cases are supported by this procedure.",The UE is using both the accesses for the same PDN connection. In these procedures the UE is assumed to simultaneously connect via a 3GPP access and a WLAN access.
568,"For bands where 2RX is supported, it is left to the UE declaration and AP configuration to decide which 2 of the 4 Rx ports are connected with data source from system simulator.
 The remaning 2 Rx ports shall be connected with zero input.
 No test parameters or requirements are modified. For bands where 4RX is supporetd, all 4 Rx are connected with data source from system simulator.
 The system simulator shall provide independent noise and fading (low correlation) for each antenna port.
 Except for the modifications to radio link monitoring theresholds described in sections A.
 ","No test parameters or requirements are modified for bands where 4RX is supporetd, all 4 Rx are connected with data source from system simulator. The remaning 2 Rx ports shall be connected with zero input."
569,"Otherwise the Remote UE shall use its IMSI in the Long Term ID.
 The Direct Communication Request contains the Relay Service Code that the Remote UE would like to access 4a.
 The UE-to-network relay sends a Key Request message to the PKMF.
 The message shall contain the PRUK ID or IMSI, the Relay Service Code and Nonce_1 (see subclause\) provided by the Remote UE.
 The PKMF identifies the UE by the PRUK ID or IMSI.
 The PKMF checks the context of the Remote UE to confirm whether it can connect to the network via the selected ProSe UE-to-network Relay for the given Relay Service.","The UE-to-network relay sends a Key Request message to the PKMF. The Direct Communication Request contains the Relay Service Code that the Remote UE would like to access 4a, and the PKMF identifies the UE by the PRUK ID or IMSI."
570," An MSC performing contention resolution shall select the service subscriber whose request was received first by the MSC and pre-empt the uplink use of the other service subscribers.
 Mobile stations shall support the reception of additional information related to the current talking service subscriber.
 The transmission of additional information is optional for the network.
 If additional information is provided, then it is periodically repeated by the network as long as the current talking service subscriber keeps the uplink.
 The additional information consists of a string of up to 17 octets and is stored in the HLR as part of the subscription data of the subscriber.
 The contents and the encoding of the additional information is operator. The release of the uplink is triggered by the user and indicated by the mobile station to the network.
 ",An MSC shall select the service subscriber and mobile station shall support the receptionof additional information. But the transmission of additional information is optional.
571," An MBMS user service may also be carried by more than one MBMS bearer service.
 In that case the MBMS user service part in the UE initiates the relevant MBMS bearer services. 
 Session Start is the point at which the BM-SC is ready to send data.
 This can be identified with the start of a ""Multicast session"" as defined in after Session Start.
 Session Start is the trigger for bearer resource establishment for MBMS data transfer.
 If an MBMS user service is carried by more than one MBMS bearer service, a Session Start message is sent for each MBMS bearer service.
 ",An MBMS user service may also be carried by more than one MBMS bearer service. Session Start is the point at which the BM-SC is ready to send data.
572,"The end-to-end QoS is controlled by the RSVP signalling.
 Although RSVP signalling occurs end-to end in the QoS model, it is not necessarily supported by all intermediate nodes.
 DiffServ is used to provide the QoS throughout the backbone IP network, although optionally each node may support RSVP signalling and allocation of resources per flow.
 An authorisation token may be included in the RSVP signalling and the PDP context establishment/modification.
 The GGSN may authorise the RSVP session and configure the Diffserv classifier. The GGSN supports the RSVP signalling and acts as the interworking point between RSVP and DiffServ.
 ",RSVP signalling is not necessarily supported by all intermediate nodes. And the GGSN supports the RSVP signalling and mayauthorise the RSVP session.
573," A PDP context is activated by the user and accepted by the SS.
 The MS initiates a PDP context modification by sending a MODIFY PDP CONTEXT REQUEST message.
 Then the SS initiates the PDP context modification by sending MODIFY PDP CONTEXT REQUEST message with the same TI.
 The MS shall reply to the SS initiated PDP context modification procedure by sending MODIFY PDP CONTEXT ACCEPT message with the same TI.",The MS initiates a PDP context modification by sending a MODIFY PDP CONTEXT REQUEST message. A PDP context is activated by the user and accepted by the SS.
574,"These scenarios were studied and deferred to a later release.
 They are not enabled by the requirements outlined in this TR.
 In this case, multiple SIM/USIM applications are stored on the MT on a single UICC.
 Each application (that may be associated with its own unique user) has its own unique SIM/USIM associated with it.
 The billing allows multiple USIMs stored to be stored on a UICC but they cannot be all active at the same time.
 ",The billing allows multiple USIMs stored to be stored on a UICC. Each application has its own unique SIM/USIM associated with it.
575," This timer specifies the amount of time that the network retains the communication information of the original communication which was not established successfully.
 After being informed that CC is possible the caller sends a CC invocation request before expiry of this timer.
 The minimum value of this timer is 15 seconds CC-T2 CC request operation timer.
 Supervision of response to a CC activation request sent from the originating AS to the terminating AS.
 CC-T2 will expire if signalling is not possible, at signalling failures, or if the terminating AS cannot respond.
 The minimum value of this timer is 10 seconds CC-T3 CC service duration timer.","The minimum value of this timer is 10 seconds CC-T3 CC service duration timer. CC-T2 will expire if signalling is not possible, at signalling failures. This timer specifies the amount of time that the network retains the communication information."
576,"This timer specifies the maximum time the service will remain activated for user A.
 The maximum value of this timer is 180 minutes. The value of the CC service duration timer can differ in the network dependent on the invoked CC service.
 CCBS can take one value and CCNR or CCNL can take another value CC-T4 CC recall timer.
 This timer specifies the maximum time the originating AS will wait for a response from user A to a CC recall. The maximum value of this timer is 20 seconds CCNR-T5 No-reply timer.
 This timer specifies the maximum time after which the originating AS will provide the announcement that CCNR is possible, and inband activation is possible.
 The maximum value of this timer is 20 seconds. Timers referring to the terminating AS the expiry of CC-T3 has not been notified to the terminating AS.
 ",The maximum value of this timer is 20 seconds Timers referring to the terminating AS the expiry of CC-T3 has not been notified to the terminating AS. CCBS can take one value and CCNR or CCNL can take another value CC-T4 CC recall timer.
577,"For UEs with more than one receiver antenna connector, identical interfering signals shall be applied to each receiver antenna port if more than one of these is used (diversity).
 The levels of the test signal applied to each of the antenna connectors shall be as defined in the respective sections below. These requirements apply to all UE categories unless stated otherwise.
 ","For UEs with more than one receiver antenna connector, identical interfering signals shall be applied to each receiver antenna port if more than one of these is used. With the exception of subclause , the requirements shall be verified with the network signalling value NS_01 configured."
578,"If a time interval is specified in Filter Data, the Notify Data procedure is invoked only after that time period has passed after the Subscribe element was received.
 In this case the Notify element shall contain the current values of all the changed data structures defined. The RAF entity creates and returns an InvokeID that shall be unique within the RAF.
 Once an InvokeID has been deleted because it is no longer required, another InvokeID with the same value can be created, without failing the uniqueness test.
 The InvokeID is used by the Notify Data procedure to link the notification to the Subscribe element. A Subscribe Response element is sent with the status information.
 If not otherwise stated above, the contents of the Status are as described in List of result codes. The following result codes may appear in responses - Invalid Filter Data where is defined.
 ","The InvokeID is used by the Notify Data procedure to link the notification to the Subscribe element A SubscribeResponse element is sent with the status information. Once an InvokeID has been deleted because it is no longer required, another InvokeID with the same value can be created, without failing the uniqueness test. "
579," In order to produce this data performance measurements are executed in the NEs, which comprise the network.
 The data can then be transferred to an external system, e.g. an Operations System (OS) in TMN terminology, for further evaluation.
 The purpose of the present document and the other related 3GPP TSs listed above is to describe the mechanisms involved in the collection of the data.","In order to produce this data performance measurements, the data can then be transferred to an external system. "
580,"See clause for scope and types of errors attempted to be detected Specifying an activation mode is optional.
 There can only be one activation mode for a session.
 If an activation mode is specified for the validate, it shall be when the first validate operation is requested.
 If an activation mode was specified for the first validate operation, it is not possible to change the activation mode initially specified with any subsequent validate retries.
 If another activation mode is required; a new session, download validate, preactivate and activate should be started.
 If no activation mode is specified for the first validate, it cannot be subsequently specified with any subsequent validate retries.
 ","If no activation mode is specified for the first validate, it cannot be subsequently specified with any subsequent validate retries. There can only be one activation mode for a session."
581,"This category of solutions enables the HPLMN, based on subscription, to configure UEs to perform disaster roaming following a disaster condition.
 Category B solutions depend only on SIB broadcast messages for informing UEs about PLMNs offering disaster roaming.
 This category of solutions offer more flexibility to the PLMNs to react according to the current disaster situation than Category A solutions where each UE has to be provided updated configurations.
 Category C solution is limited by support of PWS functionality in both PLMN and UE.
 Category D solution requires that AMF in PLMNs create, test and maintain redundant N2 and N3 links with at least one another NG-RAN node providing overlapping coverage.","This category of solutions enable the HPLMN to configure UEs to perform disaster roaming. And each Category has its own characteristics,"
582,"Security context limited to single call will not be reused.
Only if media stream protection provides integrity protection.
It is reliant on the MCPTT Server to provide implicit authentication and to ensure modification of private call keys is not allowed, which may not be acceptable to some user groups.
 ",Security context limited ri single call will not be used only if media stream protection provides integrity protection. It is reliant on the MCPTT Server to provide implicit authentication and to ensure modification of private call keys is not allowed.
583,"The warning type of this warning message is ""test"" Public key ID, NSUC and CBE-ID should also be included in the test warning message.
 When UE receives it, UE verifies the signature using the public key it saves.
 If successful, the public key UE saves is the latest.
 UE updates NSUC if greater than the NSUC stored on the UE.
 If signature verification is not successful, UE sends the public key ID and CBE ID in the next TAU/RAU request to the MME/SGSN.
 The MME/SGSN checks whether public key ID is what it has saved.
 If not, MME/SGSN sends the update public key, public key ID, NSUC and CBE ID it saves in TAU/RAU accept message.","UE updates NSUC if greater than the NSUC stored on the UE. If not, MME/SGSN sends the update public key, public key ID, NSUC and CBE ID it saves in TAU/RAU accept message."
584,"When a MeNB receives a SeNB UE X2AP ID it shall store it for the duration of the UE associated logical Xconnection for this UE.
 Once known to a MeNB this ID is included in all UE associated XAP signalling.
 The SeNB UE X2AP ID shall be unique within the eNB logical node eNB UE XwAP ID. An eNB UE XwAP ID shall be allocated so as to uniquely identify the UE over Xw interface within an eNB for LWA.
 When a WT receives an eNB UE XwAP ID, it shall store it for the duration of the UE-associated logical Xw-connection for this UE.
 Once known to a WT, this ID is included in all UE associated Xw-AP signalling.
 The eNB UE XwAP ID shall be unique within the eNB logical node WT UE XwAP ID. A WT UE XwAP ID shall be allocated so as to uniquely identify the UE over Xw interface within a WT for LWA.
 When an eNB receives a WT UE XwAP ID, it shall store it for the duration of the UE-associated logical Xw-connection for this UE.
 Once known to an eNB, this ID is included in all UE associated Xw-AP signalling.","The SeNB UE X2AP ID shall be unique within the eNB logical node eNB UE XwAP ID An eNB UE XwAP ID shall be allocated so as to uniquely identify the UE over Xw interface within an eNB for LWA. Once known to an eNB, this ID is included in all UE associated Xw-AP signalling."
585,"Database aspects of ENUM are outside the scope of the present document.
 An S-CSCF that implements the additional routeing functionality described in Annex I may forward the request without attempting translation.
 If this translation is in fact performed and it succeeds, the S-CSCF shall update the Request-URI with the globally routeable SIP URI returned by ENUM/DNS.
 If this translation fails, the request may be forwarded to a BGCF or any other appropriate entity (e.g a MRFC to play an announcement) in the response to the originator.
 When forwarding the request to a BGCF or any other appropriate entity, the S-CSCF shall leave the original Request-URI containing the tel URI unmodified.
 ","When forwarding the request to a BGCF or any other appropriate entity, the S-CSCF shall leave the original Request-URI containing the tel URI unmodified. An S-CSCF that implements the additional routeing functionality described in Annex I may forward the request without attempting translation."
586,"When an AS is used, then the IMS service control architecture is used to provide the chat service.
 Both signalling and user plane are then supported by the AS.
 In this case the intermediate chat server is addressed by the UE#1 using a PSI.
 It is assumed that UE#1 is the first UE entering the chat session NOTE: Interactions between MRFC and MRFP are not shown in the flows below since these interactions are not standardized.
 ","When an AS is used, then the IMS service control architecture is used to provide the chat service, and both signalling and user plane are then supported by the AS. In this case the intermediate chat server is addressed by the UE#1 using a PSI."
587,"An Iub DSCH data stream corresponds to the data carried on one DSCH transport channel for one UE.
 A UE may have multiple DSCH data streams Iub USCH data stream [TDD]. The Iub interface provides the means for transport of uplink shared channel, USCH, data frames between Node B and RNC.
 An Iub USCH data stream corresponds to the data carried on one USCH transport channel for one UE.
 A UE may have multiple USCH data streams Iub PCH data stream. The Iub interface provides the means for transport of PCH transport frames between RNC and Node B.
 An Iub PCH data stream corresponds to the data carried on one PCH transport channel Iub FDD TFCI2 data stream 
 The Iub interface provides the means for transport of high speed downlink shared channel, HS-DSCH, data frames between RNC and Node B.","An Iub DSCH data stream corresponds to the data carried on one DSCH transport channel for one UE, which may have multiple DSCH data streams. The Iub interface provides the means for transport of uplink shared channel, USCH, data frames between Node B and RNC."
588," The run length code words are of two types: terminating code words and make-up code words.
 Each run length is represented by either one terminating code word or one make-up code word followed by a terminating code word.
 Run lengths in the range 3 bits are encoded with their appropriate terminating code word.
 Run lengths greater than 63 bits are encoded first by the make-up code word which is equal to or shorter than that required.
 ",The run length code words are of two types: terminating code words and make-up code words. Each run length is represented by either one terminating code word or one make-up code word followed by a terminating code word.
589,"This external interface is outside of the control of 3GPP and existing standards may be used for part or all of the functionality of this interface.
 TVNP Group Management/ Communication and Affiliation MCVideo group communication aspects are very similar to MCPTT.
 Each user may be a member of several, even many, groups.
 Membership is determined by administration control and provides a user identity based level of authority to join a group.
 Each user chooses to affiliate to the groups that they want to receive video communication from.
 Once a user has successfully affiliated to a group they will begin to receive video communications directed to that group according to the video distribution approach used.
 ","Each user may be a member of several, even many, groups. Membership is determined by administration control and provides a user identity based level of authority to join a group. TVNP Group Management/ Communication and Affiliation MCVideo group communication aspects are very similar to MCPTT."
590," If the CRC check fails, the PSAP receiver continues sending NACK messages.
 If the CRC check succeeds, the PSAP transmitter changes the message to the link-layer or higher-layer ACK message.
 It is up to higher layer protocol requirements whether link-layer and/or higher-layer ACK messages are transmitted.
 From a modem protocol perspective, at least five ACK messages of one type (either link-layer or higher-layer) shall be transmitted consecutively for security.
 No higher-layer ACK message shall preceed a link-layer ACK message, and no link-layer ACK message shall succeed a higher-layer ACK message.
 For this purpose, the modem reference implementation transmits up to five link-layer ACK messages until a trigger from the higher-layer protocol is received.
 After the trigger, five higher layer ACK messages are transmitted.","If the CRC check succeeds, the PSAP transmitter changes the message to the link-layer or higher-layer ACK message. From a modem protocol perspective, at least five ACK messages of one type shall be transmitted consecutively for security. "
591," XML Signature Recommendation: This clause introduces the concept of XML Signature.
 It is used to transfer XML Signature over Itf-N to provide the File Integrity.
Data to be signed is canonicalized by using a specific method.
 The canonicalized data may be transformed before it is digested by using a specific method.
 The digest value is encrypted by using a specific signature method.",XML Signature is used to transfer XML Signature over Itf-N to provide the File Integrity. The canonicalized data may be transformed before it is digested by using a specific method.
592,"The originating S-CSCF forwards the SIP MESSAGE to the IP-SM-GW based on the iFC.
 The subscription of the transport level interworking and the service level interworking applies for different iFC.
 However, the SIP MESSAGE is forwarded to the IP-SM-GW if the user subscribes to one of the interworking services.
 If there is no subscription for the interworking service, the S-CSCF continues with the subsequent iFC check.
 After all the originating iFC triggers have been handled, the S-CSCF attempts to route the message to the terminating IMS network.
 If it fails an error is returned to the sender routed to it before going to the IP-SM-GW Request-URI.","If there is no subscription for the interworking service, the S-CSCF continues with the subsequent iFC check. After all the originating iFC triggers have been handled, the S-CSCF attempts to route the message to the terminating IMS network."
593,"It has been found that the noise is relatively stationary for quite long periods in a mobile environment.
 It is therefore possible to use an adaptive filter with coefficients obtained during noise, to remove much of the vehicle noise. The VAD is basically an energy detector.
 The energy of the filtered signal is compared with a threshold. The noise encountered in mobile environments may be constantly changing in level.
 The spectrum of the noise can also change, and varies greatly over different vehicles.
 Because of these changes the VAD threshold and adaptive filter coefficients must be constantly adapted.
 ",The noise is relatively stationary for quite long period so that it's possible to use an filter with coefficients obtained during noise. The VAD can be used to filter the noise by comparing with threshold.
594,"The functions interface with the requesting application and select the appropriate location method and speed of response.
 The functions co-ordinate the operations of the radio and measurement equipment to transmit the needed signals and to make the needed measurements.
 The functions may also access databases or other sources of information appropriate for the location method.
 The functions also provide the calculation functions appropriate for the location method to estimate the MS location and the accuracy of the report.
 The functions also may record information on the usage of the LCS that may be used for administrative purposes (e.g. forwarded to a billing function in the Core Network).
 If needed by the location method, the functions will ensure the broadcast of information and gather and update information concerning GERAN operating parameters.","The functions interface with the requesting application and co-ordinate the operations, and may also provide the calculation functions to setimate the MS location. "
595,"A detailed description of the RLC is given in Services provided to upper layer - Transparent data transfer.
 This service transmits higher layer PDUs without altering them nor adding any RLC protocol information - Acknowledged data transfer.
 This service transmits higher layer PDUs and guarantees delivery to the peer entity - Unacknowledged data transfer.
 This service transmits higher layer PDUs without guaranteeing delivery to the peer entity - Notification of unrecoverable errors.
 RLC notifies the upper layer of errors that cannot be resolved by RLC itself by normal exception - Notification of discard.
 RLC notifies the upper layer of the higher layer PDUs (RLC SDUs) it discards - A local suspend/resume function (FFS): RLC operation may be suspended/resumed if requested by RRC.
 This service is used when the ciphering parameters need to be changed - A stop/continue function (FFS): RLC operation may be stopped/continued if requested by RRC.
 This service is used at Serving BSS relocation in order to synchronise the PDCP entities in the MS and BSS to realise a - A reset function (FFS) There is a single Radio Bearer per RLC instance.
 RLC has no functionality when operating in transparent mode.
 The incoming SDUs are transferred to the MAC layer without being altered.
 ",RLC notifies the upper layer of the higher layer PDUs (RLC SDUs) it discards - A local suspend/resume function (FFS): RLC operation may be suspended/resumed if requested by RRC. The incoming SDUs are transferred to the MAC layer without being altered. RLC has no functionality when operating in transparent mode.
596,"The general principle is that the CDRs are always sent to a CGF residing in the same network as the CDF.
 In the case of roaming it is conceivable that some CDRs relating to the same service.
 The Node Alive Request message may be used to inform that a node in the network has started its service (e.g. after a service break due to software or hardware maintenance or data service interruption after an error condition).
 A node may send a different Node Address than its own in the Information Element, e.g. informing the ""next node in the chain"" that the ""previous node in the chain"" (which is located on the other side of the sender of this message) is now ready for service.",A node may send a different Node Address than its own in the Information Element. IPv6 address type is also supported in the case of roaming it is conceivable that some CDRs relating to the same service.
597,"This clause defines the interfaces, methods and parameters that form a part of the API specification.
 The Unified Modelling Language (UML) is used to specify the interface classes.
 This shows a UML interface class description of the methods supported by that interface, and the relevant parameters and types.
 The Service and Framework interfaces for client applications are denoted by classes with name Ip<name>.
 The callback interfaces to the applications are denoted by classes with name IpApp<name>.
 ",The Unified Modelling Language (UML) is used to specify the interface classes. The Service and Framework interfaces for client applications are denoted by classes with name Ip.
598," The UE has previously stored radio bearer and transport channel parameters for use in CELL_DCH.
 The SS transmits a TRANSPORT CHANNEL RECONFIGURATION message, which modifies the rate as compared to the stored configuration to the UE.
 The message also includes the physical layer parameters.
 IE ""Uplink DPCH info"" and IE ""Downlink DPCH info"" leading to a state transition from CELL_FACH to CELL_DCH in the same cell, to the UE.
 The UE shall reconfigure the new channel according to this message.
 Finally, the UE transmits a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message using AM RLC.","The UE has previously stored radio bearer and transport channel parameters for use in CELL_DCH and the UE shall reconfigure the new channel according to this message. Finally, the UE transmits a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message using AM RLC."
599,"Such requirements may be applied per antenna, per cell, or per base station.
 It shall be noted that the definition of BS or cell may differ between regulations.
 Where the regulator prescribes a method for EIRP calculation, that method supersedes the proposed assessment in this annex. The regulations set an EIRP limit considering a passive antenna BS.
 Although the gain of passive antennas may vary somewhat, the gain variation is in the order of a few dBs.
 The instantaneous gain of an AAS BS may be much larger.","The instantaneous gain of an AAS BS may be much larger, although the gain of passive antennas may vary somewhat, the gain variation is in the order of a few dBs. Such requirements may be applied per antenna, per cell, or per base station."
600,"The IWF(s) shall maintain a mapping table (session mapping table) between the MAP Dialogue Id and the Diameter Session Id The IWF shall then process messages.
 When the IWF receives a Diameter message from a Diameter node, it shall map the Diameter message to a MAP message.
 It shall obtain a MAP Dialogue Id from the Diameter Session Id in the received message according to the session mapping table.
 The IWF shall obtain the source/destination SS7 Number from the source/destination Diameter Identity in the received message according to the address mapping b.
 When the IWF receives an SS7 message from an SS7 node, it shall map the MAP message to a Diameter message.
 It shall obtain the Diameter Session Id from the MAP Dialogue Id in the received message according to the session mapping table.
 ","Although the gain of passive antennas may vary somewhat, the gain variation is in the order of a few dBs. Such requirements may be applied per antenna, per cell, or per base station."
601," The procedure for receiving MBMS control information is used by a UE to receive information from UTRAN concerning the way it provides MBMS services the UE has activated.
 The procedure applies to all UEs supporting MBMS irrespective of its state. Most MBMS control information is provided on the MCCH.
 The information on MCCH is transmitted using a fixed schedule, which is common for all services.
 MCCH information other than MBMS Access Information message is transmitted periodically based on a repetition period.
 ","The procedure for receiving MBMS control information is used by a UE to receive information from UTRAN concerning the way it provides MBMS services the UE has activated. The information on MCCH is transmitted using a fixed schedule, which is common for all services."
602,"UE IP address(es) assigned to the PDU Session if available.
 Shall be present if this IE is in the SMContextUpdateData, HsmfUpdateData or message sent to the SMF or the PDU Session Context or SM Context at the SMF.
 Indicates whether the PDU Session Modification being reported was due to a handover.
 Shall be present if this IE is in the SMContextUpdatedData or sent by the SMF.
 Contains the information for the User Plane GTP Tunnels for the PDU Session.",UE IP addresses shall be repsent under several conditions and contain the information for the User Plane GTP Tunnels. 
603,"The performance of CPC and the Lean cases are rather close.
 This result is not entirely Normally, the use of a very small DPCCH burst and a very long DTX gap could easily lead to power control instability due to the inability to track fast even worse.
 In the current scenario, however, the large 3slot data burst is able to correct any power control error.
 Had it not been the alternating arrangement of the data and DPCCH bursts, the power control error would have accumulated over time and led to instability.
 We will see some indication of this in the results that follow Note also that a 20ms burst at 5 Mbps will deliver 1 kB of data.","The performance of CPC and the Lean cases are rather close. In the current scenario, however, the large 3slot data burst is able to correct any power control error."
604,"The precision of the location shall be network design dependent, i.e an operator choice.
 This precision may vary from one part of a network to another.
 It may be chosen to be as low as hundreds of meters in some place and as accurate as 5 meters in other place.
 It is required that a minimum precision of around 50 meters can be achieved in all types of terrestrial radio environment.
 Technical issues may constrain the precision to be mobile state dependent as well (mobile idle / mobile in communication).",It may be chosen to be as low as hundreds of meters in some place and as accurate as 5 meters in other place. It is required that a minimum precision of around 50 meters can be achieved in all types of terrestrial radio environment.
605," Provisioning of communication between the unauthorised users, with access control interval application, leads to effective and efficient use of network resources.
 It can be confirmed of the effectiveness and efficiency in the traffic analysis in the 2005 Miyagi Earthquake.
 There are two types of the effectiveness and efficiency.
 One is that Congestion with access control interval application ceases earlier than that without them.
 It is efficient from the perspective of operation and management.
 The other is that the users can make sure of safety of their families, relatives, and friends.","Provisioning of communication between the unauthorised users, with access control interval application, leads to effective and efficient use of network resources. It is efficient from the perspective of operation and management."
606," For each common E-DCH resource, there is one reordering queue for the logical channel CCCH.
 The reordering is based on a specific TSN included in the MAC-is PDU.
 Additional mechanisms are up to Node B implementation and will not be standardised.
 Furthermore, the reordering entity detects and removes duplicated received MAC-is PDUs For 8Mcps TDD, when CCCH is transmitted on E-DCH, the re-ordering entity is part of a MAC-is in the CRNC.
 For each UE, there is one reordering queue for the logical channel CCCH.
 The reordering is based on a specific TSN included in the MAC-is PDU.
 Additional mechanisms are up to Node B implementation and will not be standardized.",Additional mechanisms are up to Node B implementation and will not be standardised. The reordering is based on a specific TSN included in the MAC-is PDU.
607,"The CP functions selects a new TUPF (TUPF2) that is geographically closer to the current UE location and configures TUPF2 as a new branch of the session.
 In the process a new IP address/prefix (IP@2) is allocated.
 At this point, the UE is not yet involved. The CP function configures one of the intermediate U-plane nodes as a branching point for the PDU Session.
 It is possible that the CP may insert a new U-plane node into the path to act as a branching point.
 The U-plane node acting as a branching point may be collocated with other entities. The network notifies the UE of the availability of the new IP address/prefix.
 The UE releases the old IP address/prefix as soon as it configures the use of the new IP address/prefix.",The CP functions selects a new TUPF (TUPF2) that is geographically closer to the current UE location and configures TUPF2 as a new branch of the session. It is possible that the CP may insert a new U-plane node into the path to act as a branching point.
608,"The IPDT has been shown as dotted to indicate it is not part of the IMS components.
 The IPDT may represent another IP application such as a web browser In this scenario important UMTS functions are located outside the MT.
 This means that the system aspects need to be understood.
 The most important of these are discussed in the following sections This scenario is intermediate between the other two.
 It recognises the fact that in the short-term the implementation of media codecs presents special problems for TE hardware.
 Also the location of codecs outside the MT may complicate the efficient management of the radio interface.
 ",The IPDT may represent another IP application such as a web browser in this scenario important UMTS functions are located outside the MT. It recognises the fact that in the short-term the implementation of media codecs presents special problems for TE hardware.
609,"The mapping from service area identity or cell ID and location area to location number is network-specific and outside the scope of the UMTS and GSM standards.
 Service area ID C Service area identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact.
 Shall be present if the MS uses UMTS radio access and the subscriber record is marked as confirmed by radio contact; otherwise shall be absent.
 See Cell ID C Cell global identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact.
 Shall be present if the MS uses GSM radio access and the subscriber record is marked as confirmed by radio contact; otherwise shall be absent.
 ", Service area ID C Service area identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact. The mapping from service area identity or cell ID and location area to location number is network-specific and outside the scope of the UMTS and GSM standards.
610,"It is used by an RLP entity to indicate that it is temporarily not ready to receive numbered information frames.
 In that case, the RLP entity is said to be in the busy condition.
 All frames up to and including N(R)-1 shall be considered acknowledged.
 Subsequent frames, if any, shall not be considered confirmed.
 The acceptance status of those is a matter of further status Selective reject, SREJ (11) The SREJ encoding can be used either as command or response.
 The SREJ command/response is used to request retransmission of a single frame, thus under certain circumstances, providing for more efficient error recovery than by REJ.
 ",All frames up to and including N(R)-1 shall be considered acknowledged. It is used by an RLP entity to indicate that it is temporarily not ready to receive numbered information frames.
611,"The ME shall read the allowed CSG Ids from EFACSGL in order to perform H(e)NB selection procedures.
 The lists in EFACSGL shall take precedence over the list stored in the ME non-volatile memory.
 The ME shall read the Operator CSG Ids from EFOCSGL in order to perform H(e)NB selection procedures.
 The list in EFOCSGL shall take precedence over the list stored in the ME non-volatile memory.
 In case of a manual CSG cell selection, the ME shall read EFAD and CSG Lists Display Indicators from EFOCSGL and display CSG Ids accordingly.",The lists in EFACSGL shall take precedence over the list stored in the ME non-volatile memory. The ME shall read the Operator CSG Ids from EFOCSGL in order to perform H(e)NB selection procedures.
612," The configuration in EFOCSGL shall take precedence over the configuration stored in the ME non-volatile memory.
 The ME shall discover the association between the selected CSG ID and a CSG Type from EFACSGL.
 If this association exists, the provided CSG Type shall be displayed.
 The ME shall discover the association between the selected CSG ID and either a CSG Type from EFACSGL or an Operator CSG Type from EFOCSGL.
 The Operator CSG Type has precedence The ME shall discover the association between the selected CSG ID and a HNB name from EFACSGL.
 If this association exists, the provided HNB name shall be displayed.
 The ME shall discover the association between the selected CSG ID and either a HNB Name from EFACSGL or an Operator HNB from EFOCSGL.",The ME can discover the association between the selected CSG ID and either a CSG Type from EFACSGL which configuration shall take precedence over the configuration stored in the ME non-volatile memory. 
613,"This mechanism can reduce the signalling traffic associated with mobility provided the HLR and serving network entity (i.e.MSC/VLR, SGSN, and UMSC) support the Super-Charger functionality. 
 The Super-Charger feature requires a mechanism using which the HLR can determine whether the subscription data retained by the serving network entity is valid.
 In this specification this parameter shall be referred to as the age indicator.
 The format of the age indicator is implementation specific since it shall be defined and used by the HPLMN.
 ",The format of the age indicator is implementation specific since it shall be defined and used by the HPLMN. This mechanism can reduce the signalling traffic associated with mobility provided the HLR and serving network entity support the Super-Charger functionality.
614,"In this case, another relaxation of the GSM specification could be required New multislot classes need to be implemented.
 In order to increase the uplink throughput, it is proposed that half-duplex MS use up to 6 uplink timeslots and that full-duplex MS use up to 8 uplink timeslots.
 Half-duplex EGPRS handsets with RLC/MAC uplink data rates of up to 355 kbit/s and full-duplex EGPRS handsets with RLC/MAC uplink data rates of up to 473 kbit/s will be feasible.
 Even legacy GPRS networks can benefit from the higher number of timeslots.
 Moreover, the coverage of PSK multislot uplink transmissions will become larger since multislot output power reduction usually need not be applied.
 This will help EGPRS extend the coverage of 3G services.","The coverage of PSK multislot uplink transmissions will become larger since multislot output power reduction usually need not be applied even legacy GPRS networks can benefit from the higher number of timeslots. In this case, another relaxation of the GSM specification could be required New multislot classes need to be implemented Since the standard already allows context: 3GPP TS 52."
615,"The RRC Connection Suspend message is protected in PDCP layer using the current AS security context.
 The eNB shall store the Resume ID together with the UE context including the AS security context.
 The UE ID part of the Resume ID assigned by the eNB shall be different in consecutive suspends of the same UE.
 This is to avoid tracking of UEs based on the Resume ID If the eNB has a fresh {NH, NCC} pair, the eNB shall keep KRRCint and delete other keys of the AS security context, i.e. keys KeNB, KRRCenc KUPenc shall be deleted after sending the RRC Connection Suspend message to the UE.
 ","The eNB shall store the Resume ID together with the UE context including the AS security context, where the UE ID part of the Resume ID assigned by the eNB shall be different in consecutive suspensions of the same UE."
616,"The network configures only non-negative (in dB) values Parameter ""SIntraSearchP"" in TS 304 Parameter ""SIntraSearchQ"" in TS 304 .
 If the field is absent, the UE applies the (default) value of 0 dB for SIntraSearchQ Parameter ""SnonIntraSearchP"" in TS 304.
 If this field is absent, the UE applies the (default) value of infinity for SnonIntraSearchP Parameter ""SnonIntraSearchQ"" in TS 304 .
 If the field is absent, the UE applies the (default) value of 0 dB for SnonIntraSearchQ Measurement timing configuration for intra-frequency measurement.
 If this field is absent, the UE assumes that SSB periodicity is 5 ms for the intra-frequnecy cells The set of SS blocks to be measured within the SMTC measurement duration.
 When the field is absent the UE measures on all SS-blocks Parameter ""TreselectionNR"" in TS 304 Parameter ""Speed dependent ScalingFactor for TreselectionNR"" in TS 304 .",The network is only configured with non-negative values in dB in the TS 304 parameter 'SIntraSearchQ'.
617,"In this case each cell may be associated to 0 or 1 Real Time Difference parameter.
 The Real Time Difference parameters may be received before the corresponding GSM Neighbour Cell list.
 The parameter Cell_Index_Start_RTD in each structure indicates the index of the cell in the GSM Neighbour Cell list to be taken as a starting reference.
 A sub-structure is included for each GSM Neighbour Cell referenced.
 Each of those sub-structures indicate if 0 or 1 RTD parameter is present for this GSM Neighbour Cell.",Each referenced GSM Neighbour Cell in the GSM Neighbour Cell list contains a substructure indicating whether the GSM Neighbour Cell has 0 or 1 RTD parameters
618,"The local label can then be used throughout the target specification instead of that which appears in the label reference.
 This first set of diagrams represents all classes defined in this IS with all their relationships and all their attributes, including relationships with imported information entities (if any).
 These diagrams shall contain class cardinalities (for associations as well as containment relationships) and may also contain role names.
 These shall be UML compliant class Characteristics (attributes, relationships) of imported information entities need not to be repeated in the diagrams.
 Allowable classes are Use this as the first paragraph: ""This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for this IRP.
 This clause provides an overview of the relationships between relevant classes in UML.
 Subsequent clauses provide more detailed specification of various aspects of these classes."" 
 This second set of diagrams represents the inheritance hierarchy of all classes defined in this specification.
 These diagrams do not need to contain the complete inheritance hierarchy but shall at least contain the parent classes of all classes defined in the present document.","The first set of diagrams represent all classes defined in this IS with all their relationships and all properties, and the second set of diagrams represent the inheritance hierarchy of all classes defined in this specification."
619,"The satellite simulator shall generate all signals supported by the UE.
 Signals not supported by the UE do not need to be simulated.
 The individual test scenarios in clause 5 define the reference signal power level for each satellite.
 The power level of each simulated satellite signal type shall be set to the reference signal power level defined in each test scenario in clause 5.
 ","The satellite simulator shall generate all signals supported by the UE, and the power level of each signal shall be set to the reference signal power level defined in each test scenario in Section 5."
620," This rolename provides a name allowing to navigate from an instance T of TesterObject to the associated instance of MORT.
 If to is an instance of TesterObject, the expression to.theMORT yields an object Relationship between TestInvocation and MORT. 
 This relationship defines an association between the IOC TestInvocation and the IOC MORT.
 Instead of roles this relationship has a role name Definition and legal Values.
 ","Definition and legal Values, as a role name of a relationship, allows navigation from an instance T of TesterObject to an associated instance of MORT."
621,"Therefore, no change of the delay profile during a burst has to be modeled and hence, only one sample of the delay profile is required for each burst.
 Since the channel model is only a function of position, moving vehicles can be easily simulated.
 For each burst a new channel impulse response is computed based on a given desired position.
 This allows also to simulate accelerating moving mobiles 
 The radio interface of GSM uses slow frequency hopping.
 ","Since the channel model is only a function of position, it is easy to simulate moving vehicles and accelerating mobile phones."
622,"The GGSN(s) update the Address for User Plane and TEID for downlink data and return an Update PDP Context Response.
 The GGSN(s) shall not include a PCO in the Update PDP Context Response if the No QoS negotiation indication is set.
 The SGSN releases the Iu by sending the Iu Release Command (Cause) message to the RAN.
 This message may be triggered either by an Iu Release Request message, or by another SGSN event (e.g. authentication failure, detach or the subscription to the CSG ID expires).
 The SGSN shall take the responsibility to release the Iu interface when the UE has no active PDP context, either immediately or after some timeout.
 ","The GGSN(s) is responsible for updating the Address of the User Plane and the TEID of the downlink data, and returns a response to update the PDP context, and the SGSN is responsible for releasing the Iu interface."
623," If they all pass, the SP code group(s) is (are) stored in the ME.
 If any fail, the personalisation process shall be terminated c) The SPCK is stored in the ME.
The SP personalisation indicator is set to ""on"" To de-personalise the ME, the correct SPCK shall be entered.
 It is optional whether or not a SIM/USIM is inserted in the ME.
 If a SIM/USIM is inserted then de-personalisation shall be offered whether or not the SP personalisation check passes or fails SP de-personalisation shall be possible by keypad entry.
 If there is no keypad, then an alternative ME-based solution shall be provided.","When depersonalizing the ME, the correct SPCK stored in the ME should be entered via the keyboard."
624,"The target SGSN shall not request resources for which the Activity Status Indicator within a EPS Bearer Context indicates that no active bearer exists on the source side for that PDP context.
 The Cause indicates the RAN Cause as received from the source MME.
 The Source RNC to Target BSS Transparent Container contains the value from the Source to Target Transparent Container received from the source MME.
 All EPS Bearer Contexts indicate active status because E-UTRAN does not support Based upon the ABQP for each PFC the target BSS makes a decision about which PFCs to assign radio resources.
 The algorithm by which the BSS decides which PFCs that need resources is implementation specific.
 Due to resource limitations not all downloaded PFCs will necessarily receive resource allocation.
 The target BSS allocates TBFs for each PFC that it can accommodate (NAS container for Handover) and the RN part.
 ","Cause indicates the RAN Cause received from the source MME, and the algorithm by which the BSS decides which PFCs need resources is implementation-specific."
625,"If the message contains an IMSI, the mobile station is not allocated any TMSI, and shall delete any TMSI accordingly.
 If the message contains a TMSI, the MS shall use this TMSI as the new temporary identity.
 The MS shall delete its old TMSI and shall store the new TMSI.
 In this case, an ATTACH COMPLETE message is returned to the network.
 If neither a TMSI nor an IMSI has been included by the network in the ATTACH ACCEPT message, the old TMSI, if any available shall be kept.
 ","Depending on whether the ATTACH ACCEPT message contains IMSI or TMSI, the MS will take different measures for updating or assigning TMSI."
626,"Each instance of this object represents an IMSI of a foreign subscriber to be traced i.e. if an instance for an IMSI exists then that means that the trace has been activated for that IMSI.
 This object class controls the equipment trace facility.
 Each instance of this object represents an IMEI to be traced i.e. if an instance for an IMEI exists then that means that the trace has been activated for that IMEI.
 ","This object class controls the device tracking facility, each instance of which represents an IMEI to be tracked."
627,"In this case, choosing which EPS bearer context to deactivate is implementation specific.
 The UE shall then include the EPS bearer context status IE in the TRACKING AREA UPDATE REQUEST UE requested PDN connectivity procedure. 
 The purpose of the UE requested PDN connectivity procedure is for a UE to request the setup of a default EPS bearer to a PDN.
 The UE requests connectivity to a PDN by sending a PDN CONNECTIVITY REQUEST message to the network.
 If accepted by the network, this procedure initiates the establishment of a default EPS bearer context.
 ","The UE requests a connection to the PDN by sending a PDN CONNECTIVITY REQUEST message to the network, the purpose of which is to establish a default EPS bearer."
628,"After processing this request the S-CSCF shall include the ICID and the charging function addresses received from the HSS in the outgoing message.
 The charging function addresses identify on-line, and off-line charging entities in the home network.
 It is implementation dependent how IMS related entities such as P-CSCF in the visited network get the local CCF or AAA addresses in the case that the P-CSCF is located in the visited network.
 Charging function addresses may be allocated as locally preconfigured addresses.
 If this message is sent outside the home network, S-CSCF shall include Inter Operator Identifier (IOI) that identifies the home network into the message.
 IOI is globally unique identifier for using inter operator accounting purposes.
 The response to the outgoing message may contain a separate IOI that identifies the home network of the called party.
 The S CSCF shall retain either IOI in the message when contacting the Application Servers.
 ",The outgoing message of the S-CSCF shall contain the ICID received from the HSS and the charging function address identifying the online and offline charging entities in the home network.
629," For DER and SI, the value of the counter will be calculated over the complete monitor granularity period.
 For SI, the counter will be sampled at regular time intervals and the mean value over the monitor granularity period will be calculated and compared with the threshold.
 For DER type the threshold is compared with the mean value of all observations collected during the monitor granularity period.
 For a DER type, if no observations are made during the monitor granularity period then the DER will have a value of NULL.
 No valid comparison with a threshold can be made in this case.
 ","For DER and SI, the value of the counter will be calculated over the entire monitoring granularity period."
630,"Other optional information elements within the message may also be included, if available.
 This is also valid for the case when the reporting is done with a response message.
 The latter is an exception to what is stated in subclause.
 A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message.
 Transfer syntax errors are always detected in the process of ASN.1 decoding.","A transport syntax error occurs when the receiver is unable to decode the received physical message, which is common in the ASN.1 decoding process."
631," The MnS consumer sends a HTTP GET request to the MnS producer. The query component may contain two optional parameters: ""alarmAckstate"" and ""filter"".
 Absence of the query component means all alarms shall be counted.
 The request message body shall be empty. The MnS producer sends a HTTP GET response to the MnS consumer On success ""200 OK"" shall be returned.
 The response message body shall carry the alarm count for all perceived severity values.
 The response format is defined by ""AlarmsCount"" On failure, an appropriate error code shall be returned.
 ",There are specific syntax rules for MnS consumers to send HTTP GET requests to MnS producers and for MnS producers to send HTTP GET responses to MnS consumers.
632," The MME shall set this bit on the basis of the UE capability information.
 The SGSN shall set this bit on the basis of the UE capability information and the access technology supported by the SGSN.
 Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving HSS.
 If the MME is registered for SMS then the HSS will download the SMS related data also for the standalone MME.
 The ULA-Flags AVP is of type Unsigned32 and it shall contain a bit mask.
 Indication HSS stores SGSN number and MME number in separate memory.","The MME shall set this bit according to the UE capability information, and the SGSN shall set this bit according to the UE capability information and the access technology supported by the SGSN."
633," This annex attempts to summarise all necessary background information for ""Error Patterns for Speech Codec Development"".
 The annex contains information on the file structure and the usage of given soft decision values.
 The number of test conditions have to be limited in order not to have to many subjective test conditions.
 Therefore pure rayleigh fading has been chosen as a propagation condition.
 This condition represents all multipath conditions which have a delay spread significant shorter than one bit period.
 Therefore the pure rayleigh fading statistics of bit errors is similar to those of TU and RAnpropagation conditions.
 Even for HT the energy of pathes with big delay is small compared to the energy transmitted in the first bit period.
 Therefore the HT bit error statistics is not so far away from pure rayleigh fading.
 Significant differences can be expected for EQ conditions or a real two path model with equal strength of both pathes.","This annex attempts to summarize all necessary background information on ""Error Modes of Speech Codec Development""."
634," The collaborative work between 3GPP and BBF resulted in a Workshop in February 2010 focusing on Fixed-Mobile Convergence.
 As a result of this work, it has been identified that several working groups in 3GPP will need to work on: requirements, architecture, security and OA&M.
 This TR focuses on the architecture aspects of this study.
 The work includes three building blocks containing specific aspects of the study which are to be conducted within this technical report 
 Based on requirements documented in the stage 1 specifications, this technical report addresses system architecture impacts to support BBF Access Interworking.","As part of 3GPP's work in cooperation with BFF, this technical report focuses on architectural research, addressing system architectural impacts to support BBF access interworking."
635,"Besides that, MSC1 shall also tell BSC1 its preferred/supported redundancy levels (RED-Levels MP1) by considering the link resource of MGW1 and the capability of BSC1 (RED-Levels BS1).
 The preference of MSC1 is indicated by the CSD Dummy Codec(s) included in MSC MSC1 sends MSC-PCL to BSC1 in the Assignment Request message.
 BSC1 will make the final decision of which A-interface will be used and which redundancy level will be used (RED-Level BD1).
 Only redundancy levels that are supported by both entities (BSS and MSC) may be used.
 BSC1 tells MSC1 its final decision by the Speech Codec (Chosen) included in the ASSIGNMENT COMPLETE message.","After MSC1 informs BSC1 of its preference, BSC1 finally decides which A interface to use and which redundancy level (RED-Level BD1) to use, which of course must be supported by both BSS and MSC.
 ."
636,"This optional procedure is based on measurements of DwPCHs from neighbouring cells according to an RNC schedule.
 The timing offset measurements are reported back to the RNC for processing.
 The RNC generates cell timing updates that are transmitted to the Node Bs and cells for implementation (common with the 4 Mcps TDD option).
 Alternatively the RNC may indicate that the NodeB shall autonomously adjust the cell timings.
 Two distinct phases can be distinguished for Node B synchronisation over the air, with a potential additional sub-phase involving late entrant cells.","The RNC may generate cell timing updates, which are transmitted to Node Bs and cells for enforcement, or indicate that Node B should adjust cell timing autonomously."
637," Early Warning Earthquake Early Warning (i.e. Primary wave indication) makes no sense unless it is delivered to users before Secondary wave arrives at the area where the users camp.
 The shorter delivery time over PWS is, the higher percentage of the notification area can be notified.
 The following describes importance of shortening PWS delivery time with actual data. The difference of speed between Primary wave and Secondary wave is about 3 km/sec.
 The distance from the earthquake epicentre to the area nearest to the epicentre in disaster areas is about 10 km.
 Therefore, arrival time interval at the area between Primary wave and Secondary wave is about 7 seconds.
 Whereas it takes about 5 seconds for earthquake detection system to send Earthquake Early Warning information to a mobile operator and it takes about seconds for users to take safety measures.
 Therefore, it is meaningful to shorten PWS delivery time by the second B. ","It makes sense to reduce the PWS delivery time by seconds B, because the shorter the delivery time on the PWS, the higher the notification percentage in the notification area."
638," When a subscriber (calling or called) receives a CS call when already engaged in another CS call, then she may act as follows. a) Reject the incoming call.
 This action does not affect the IMS session of the active call. b) Release the first CS call and answer the second CS call.
 The user may decide whether to keep the IMS session that was established in the context of the first CS call.
 The user may also decide to establish a new IMS session to be combined with the second CS call. c) Invoke Call Hold.
 The first call is placed on hold and the second call is answered.
 ","When a user (calling or called) receives a CS call while already participating in another CS call, she can take the following actions: a) reject the incoming call, b) release the first CS call and answer the second CS call, c) Invoke call hold."
639," The Iub interface may support the transport of Implementation specific O&M information.
 Further detail on this can be found in the UMTS technical specification on Implementation Specific O&M Transport.
 System Information is sent by the CRNC to a Node B.
 CRNC can also request the Node B to autonomously create and update certain Node B related system information.
 Scheduling of system broadcast information is carried out in the CRNC.
 Scheduling information is always sent by the CRNC to the Node B The Node B is responsible for transmitting the received system information according to the scheduling parameters provided.","The system information is sent to the Node B by the CRNC, and the scheduling of the system broadcast information is carried out in the CRNC."
640," This TLV shall be available if and only if the SendReferer bit in the attributes of the Submit Configuration TLV was set.
 It contains the page identification of the current page Each USAT Interpreter byte code is a TLV.
 Each byte code has its own byte code tag value, optional attributes and a list of arguments.
 Arguments, if present, shall appear in the order given The byte codes make use of the USAT Interpreter TLVs as follows.","Each USAT interpreter bytecode is a TLV, and each bytecode has its own bytecode tag value, optional attributes, and parameter list."
641,"  If network resources are not immediately available, the network places the priority service subscriber in queue for the next available resource.
 The queue is managed by priority level and (within each level) time of entry into the queue d.
 The network provides feedback to the priority service subscriber (either tones or short messages) on the status of their call.
 The user needs the ability to call with priority other mobile (3G and non-3G) subscribers, PSTN subscribers, and in the future, IP voice subscribers, regardless of their priority status.
 If, in the case of the US, users need the ability to interwork with GETS, a PSTN service.
 ","If network resources are not immediately available, the network will place priority service subscribers in a queue to wait for the next available resource."
642,"The UE id on the associated E-AGCH shall be used for identification. An E-PUCH may use QPSK or 16QAM modulation symbols and may or may not contain E-UCCH/TPC.
 The E-DCH Absolute Grant Channel (E-AGCH) on one carrier is a downlink physical channel carrying the uplink E-DCH absolute grant control information of the same carrier.
 The E-AGCH on one carrier uses two separate physical channels (E-AGCH1 and E-AGCH2).
 The term E-AGCH refers to the ensemble of these physical channels. ",The E-AGCH on one carrier is a downlink physical channel carrying the uplink E-DCH absolute grant control information of the same carrier.
643," For the DL, all PRBs used for transmission shall be included.
 For the UL, all PRBs allocated for transmission shall be included.
 Total number of PRBs available during For an eNB serving one or more RNs, all PRBs regardless of RN subframe configurations shall be counted.
 It is up to the eNB implementation how to calculate P(T) with respect to PRBs that may be considered not available. MBSFN subframes and subframes subject to restrictions due to TDM ICIC PRB usage per traffic class.This measurement is an aggregate for all UEs in a cell, and is applicable to Dedicated Traffic Channels (DTCH).
 The reference point is the Service Access Point between MAC and L The measurement is done separately for: - DL DTCH, for each QCI.
 ","The total number of PRBs available during an eNB serving one or more RNs, all PRBs shall be calculated regardless of RN subframe configuration."
644,"This parameter shall be ignored by the VLR if received. If the SGSN does not indicate support of the feature the HSS shall not send the parameter.
 It is included either at location updating or when it is changed.
 This parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it.
 It is included either at location updating or when it is changed. To apply, remove or update Operator Determined Barring Categories the Subscriber Status is set to Operator Determined Barring.
 In this case ODB General Data shall also be present.","To apply, delete, or update an operator-determined restriction category, the subscriber status is set to an operator-determined restriction."
645," In the originating network, a UE sends a SIP MESSAGE (Encapsulated Short Message or Instant Message).
 The originating S-CSCF forwards the SIP MESSAGE to the IP-SM-GW based on the iFC.
 The subscription of the transport level interworking and the service level interworking applies for different iFC.
 However, the SIP MESSAGE is forwarded to the IP-SM-GW if the user subscribes to one of the interworking services.
 If there is no subscription for the interworking service, the S-CSCF continues with the subsequent iFC check.
 After all the originating iFC triggers have been handled, the S-CSCF attempts to route the message to the terminating IMS network.
 If it fails an error is returned to the sender Messages are routed to it before going to the IP-SM-GW Request-URI.
 ","Describes interactions. UE sends network-originating SIP message (Encapsulated Short Message or Instant Message). S-CSCF forwards SIP over iFC. iFC uses transport-and service-level interworking.
Subscribers to interworking services send SIP MESSAGE to IP-SM-GW. If no interworking subscription exists, S-CSCF checks iFC. S-CSCF sends the message to the terminating IMS network after handling all iFC triggers. Notifies sender of failure. Receives messages before IP-SM-GW Request-URI."
646,"This chapter presents a selection of service scenarios, which are used as a basis for the RAB scenarios.
 Only the basic scenarios having impact on the lower layers are considered.
 Because the real time applications have the tightest connection with the lower layers, the real time scenarios are studied more in detail in this document.
 Other scenarios can be derived as combinations of these basic scenarios Even though these scenarios are for IMS, they are applicable also for non IMS PS scenarios.
 The differences between IMS and non-IMS are small in RAN level: Usually, the difference is that in non-IMS cases the IMS signalling stream is left out or replaced by non-IMS signalling stream.
 ",This chapter provides RAB scenarios. Lower-level scenarios only. This document focuses on real time applications because of their tight connection to lower layers. These basic scenarios can be combined. PS can use IMS scenarios. IMS and non-IMS RAN are similar. Non-IMS cases usually omit or replace the IMS signalling stream.
647,"In all cases the respective constraints of the service have been taken into account especially in the selection of video encoding tools.
 Purposely, some well known and recognized optimization features, for example for error resilience, have been excluded.
 It is obvious that these optimizations are possible and, at least to some extent, also expected in real-world. 
 The input to the encoding process is a source sequence in 3G file format. ","When choosing a video encoding tool, some well-established optimization features, such as error resilience, were deliberately excluded."
648,"The TDM circuit is identified by the termination Id in the Mc interface.
 Since TDM circuits are also grouped together, the physical termination Ids are structured in accordance with the grouping of TDM circuits.
 The MSC server also knows the termination Ids and the grouping of termination Ids.
 The physical termination exists as long as the TDM circuit(s) exists.
 The ""squared"" line represents the call control signalling and the ""dotted"" line represents the TDM circuits.
 ","Mc termination Id identifies TDM circuit. Since TDM circuits are grouped, physical termination Ids are too. MSC server knows termination Ids and groupings. Physical termination exists as long as TDM circuits do. The ""squared"" line represents call control signaling and the ""dotted"" line represents TDM circuits."
649,"These components can be truncated by the sender, i.e. the infrastructure, to fit into the rest octets information element.
 The truncation function was added to the PAGING REQUEST TYPE 1, PAGING REQUEST TYPE 2 messages and the SYSTEM INFORMATION TYPE 4 sent on BCCH.
 When the truncation function is used with the PAGING REQUEST TYPE 1 or PAGING REQUEST TYPE 2 messages, the receiver. Specifications prior to R99 is not able to handle correctly the messages in which the truncation function is used.","These components can be truncated by the sender, i.e. the infrastructure, to fit the remaining octet information elements."
650,"The transfer of RLC data blocks in RLC acknowledged mode uses retransmissions of RLC data blocks.
 The transmitting side numbers the RLC data blocks via the block sequence number (BSN).
 The BSN is used for retransmission and for reassembly.
 The receiving side sends acknowledgement in order to request retransmission of RLC data blocks.
 In TCH TBF mode, the transfer of RLC data blocks in RLC acknowledged mode numbering of the RLC data blocks.","In RLC acknowledged mode, the transmission of RLC data blocks uses retransmission of RLC data blocks."
651,"For the following discussion, it is assumed that the operations on IS level are kept the same and represent services to be mapped to the solution set level.
 Then on the solution set level we map the IS level to either a SOAP based representation or a RESTful representation SOAP uses the Internet as transport.
 SOAP can be transported in HTTP or another protocol.
 One can argue that in the case that SOAP uses HTTP, in this case SOAP uses the Web.
 But it is only HTTP POST that is used (for requests), not for example DELETE or PUT.","At the solution set level, we map the IS level to a SOAP based representation or RESTful representation SOAP using the Internet as the transport."
652," Purely based on the values , it could be true that a PV-owner might opt for CS104 (or even OPC-DA, Profinet) that is simpler and cheaper to deploy.
 But these protocols are less flexible to support PMU multicast mode.
 That is where IEC 61850 adds value to the WAN protection mechanisms.
 In this case, multicast PMU data could be transferred via routable sampled values (R-SV) profile (IEC 6185).",Where IEC 61850 adds value to WAN protection mechanisms is that multicast PMU data can be transported via a routable sampled value (R-SV) profile (IEC 6185).
653,"Furthermore, two thresholds are introduced for DER tripping to prevent it from happening prematurely, which would compromise the stability of the bulk power system.
 There are many available algorithms available for an IED to detect abnormal conditions and to further determine whether the tripping conditions are met.
 More algorithms are based on continuous measurements and comparison of local and remote measurement provided by PMUs.
 With renewables and DERs proliferating in the distribution networks, decisions on PCCs would need real-time measurements from multiple strategically chosen measurement points in the network.","Two thresholds were introduced for DER tripping to prevent it from happening prematurely, which would compromise the stability of bulk power systems."
654,"The CAP Operation that opens a TC dialogue shall be sent with a TC-BEGIN request primitive.
 This message shall contain the GPRS-ReferenceNumber assigned by the sender of this message in the originationReference.
 If the operation opens a subsequent TC dialogue, then this message shall contain also the previously received destinationReference.
 If an operation opens a GPRS dialogue, then the TC message reply shall contain the originationReference as assigned by the sender, i.e. the gsmSCF. The TC dialogue shall be closed for the idle periods.",A CAP operation to open a TC session shall be sent with the TC-BEGIN request primitive.
655,"Depending on operator configuration, the Proxy Function shall begin quota deduction and save the current time as start of charging time reachable.
 Upon encountering this event corresponding counts for the voice call are closed and a terminate Debit / Reserve Units Request message, indicating the end of the voice call, is triggered.
 If the operator configuration has indicated that charging has started prior to answer, the start of charging time is provided with the used service units (e.g., call forwarding on not reachable).
 Corresponding counts for the voice call are closed and an update Debit / Reserve Units Request message is triggered.
 If the operator configuration has indicated that charging has started prior to answer, the start of charging time is provided with the used service units.
 The subsequent response indicates if charging for terminating leg is to be maintained only (e.g., busy, no answer, not reachable, route select failure).
 Upon encountering this event, corresponding counts for the voice call are closed and a termination Debit / Reserve Units Request message indicating the end of the voice call, is triggered.
 If the operator configuration has indicated that charging has started prior to answer the start of charging time is provided with the used service units - End of voice call.
 Upon encountering this event, a terminate Debit / Reserve Units Request message, indicating the end of the voice call, is sent towards the OCS together with the final counts. ","When this event is encountered, the corresponding count for the voice call will be turned off and a Terminate Debit/Reservation Unit Request message will be triggered, indicating the end of the voice call."
656," The performance requirements in this clause shall apply when UE is used to provide fullband telephony, either as a stand-alone service, or as part of a multimedia service.
 The requirements in the clause apply only when the far-end terminal is also providing fullband telephony.
 When a fullband enabled terminal is providing narrowband telephony, the requirements in a fullband-enabled terminal is providing wideband telephony, the shall apply.
 When a fullband-enabled terminal is providing super-wideband.
 ",The requirements in this clause only apply when the far-end terminal also provides full-band telephony.
657,"Management interfaces provide, via specific communication protocols, for the interconnection of NEs and OSs through the DCN.
 Interactions between physical blocks, to exchange management information, are established dynamically at run time and are usually not defined statically at design time.
 In order for such dynamic interactions to occur, physical blocks must be connected by a communications path and each element must support compatible interfaces.
 It is useful to use the concept of an interface to simplify the communications problems arising from a multi-vendor, multi capability network.
 The interface defines the specific protocols, commands procedures, message formats and semantics used for the management communications between physical blocks.","For dynamic interaction between physical blocks, the physical blocks must be connected by a communication path, and each element must support a compatible interface."
658,"PLMN selection follows the rules specified in 3GPP TS Currently the BSS can be connected to only one CN node each in the CS and PS domains, both of which are associated with the same PLMN.
 Hence, it is assumed that one GAN is associated with one PLMN The identity of the PLMN associated with the GAN is made known to the MS on successful registration with the GAN.
 Hence, only the PLMN associated with the successfully registered GAN can be selected.
 The PLMN associated with the GAN the MS is registered on, is treated as an equivalent PLMN to the HPLMN.
 As a result, the concept of background scanning for higher priority PLMNs does not apply in GAN mode.",The background scan concept of higher priority PLMN does not apply to GAN mode.
659,"If the subscriber can be contacted, the VLR shall set up a transaction to the MSC and forward the operation unchanged.
 Any further information exchange between the HLR and MSC shall be transparent to the VLR.
 When one transaction is released, the VLR shall release the other The MSC may at any time receive an USSD operation from the VLR.
 If the subscriber can be contacted, the MSC shall set up a transaction to the MS and forward the operation unchanged.
 Any further information exchange between the VLR and MS shall be transparent to the MSC.
 ","Any further exchange of information between the HLR and the MSC shall be transparent to the VLR, and any further exchange of information between the VLR and the MS shall also be transparent to the MSC."
660,"The same set of services provided by GPRS is available in HSDPA is an enhancement to Packet data services for UTRAN allowing higher data rates on the radio interface downlink.
 The same set of services provided by GPRS is available with GPRS using HSDPA.
 The GPRS can be described using the simplified reference model in figure GPRS provides data transfer capabilities between a sending entity and one or more receiving entities.
 These entities may be an UE or a Terminal Equipment, the latter being attached either to a GPRS network or to an external data network.
 The base station provides radio channel access for UEs to the GPRS network.
 ",The same set of services provided by GPRS available in HSDPA is an enhancement to the UTRAN packet data service to allow higher data rates on the radio interface downlink.
661,"For each appropriate watcher, the PS sends a NOTIFY request that contains the updated state of presence information.
 The NOTIFY request may either contain the complete set of presence information, or only the information that has changed since the last notification.
 In this example, the watcher indicated preference for partial notification in the SUBSCRIBE request, so the NOTIFY request is formulated according that has changed since the last notification.
 ","For each appropriate observer, the PS sends a NOTIFY request containing updated state information, which may contain the full set of presence information, or only information that has changed since the last notification."
662," It is important to note that Service Use, Customer Service Negotiation, etc are roles, and that one Actor may adopt more than one role.
 For instance an individual may adopt the roles of both Service Use and Customer Service Negotiation.
 A Company may adopt the roles of Network Operator, SP.
 A user initiates a service by requesting it from the Service Provider, not the Network Operator.
 On receipt of a service request the Service Provider uses Network Operators and Third Party Service Providers to service the request in the best way possible.
 ","An actor may assume multiple roles, such as service usage, client-service negotiation, etc."
663,"Depending on the particular deployment scenario (e.g., suburban, urban, dense-urban), the HNB can have different coverage radius (i.e., link budget).
 For example, in a suburban scenario, the HNB coverage can be 100dB whereas a lower HNB coverage radius (e.g., 70dB) may be more suitable for dense-urban deployments.
 It is seen that in the cell edge scenario, using high HNB Tx power results in poor CPICH Ec/No for the MUE.
 On the other hand, when HNB is close to the macrocell site, a low HNB Tx power results in poor CPICH Ec/No for the HUE.
 As the HNB Tx power increases, the MUE CPICH Ec/No degrades.
 ","Depending on the specific deployment scenario (eg suburban, urban, dense city), HNBs can have different coverage radii (ie, link budgets)."
664," The exact meaning of priority is not defined further in this document, but is left to national regulation. The S-CSCF shall support the use of the Path and Service-Route header field.
 The S-CSCF shall also support the Require and Supported header fields.
 The Path header field is only applicable to the REGISTER request and its 200 (OK) response.
 The Service-Route header field is only applicable to the 200 (OK) response of REGISTER.
 The S-CSCF shall not act as a redirect server for REGISTER requests. The network operator defines minimum and maximum times for each registration.
 ","The S-CSCF shall support the use of the Path and Service Routing header fields, the Require and Supported header fields, and shall not act as a redirect server for REGISTER requests."
665," Encoding complexity of MDSR is 2 times higher per timeslot than for 8PSK, i.e. the same as for DSR To generate the MDSR modulation in the MS, it was proposed to apply an offset of 100 kHz in the baseband modulator.
 This means that the required baseband bandwidth will double although the symbol rate is only 50 % higher.
 The two different symbol rates and the doubled bandwidth may require a different, higher DAC sampling frequency and a wider filter bandwidth of the subsequent low-pass filters.
 ","To generate the MDSR modulation in the MS, which has twice the coding complexity of 8PSK per slot, it is recommended to apply an offset of 100 kHz in the baseband modulator."
666," Any originating CAMEL based services shall be invoked before the Barring of outgoing international calls supplementary service. 
 For CAMEL phase 1 based services there shall be no interaction.
 In this case, the interaction between call forwarding and call barring is not modified by CAMEL.
 This means that the interaction is applied prior to the invocation of call forwarding.
 ",Any CAMEL based service initiated should be invoked prior to restricting outgoing international calls supplementary service.
667,"For PCS 1900 for NA, Federal regulation mandates that a digit MNC shall be used.
 However a network operator may decide to use only two digits in the MNC in the RAI over the radio interface.
 In this case, bits 5 to 8 of octet 3 shall be coded as ""1111"".
 Mobile equipment shall accept RAI coded in such a way.
 In earlier versions of this protocol, the possibility to use a one digit MNC in RAI was provided on the radio interface.
 However as this was not used this possibility has been deleted.
 In earlier versions of this protocol, bits 5 to 8 of octet 3 were coded as ""1111"".",The network operator may decide to use only the two numbers in the MNC in the RAI on the wireless interface.
668,"Key Messages are associated to ISMACryp streams via SDP signalling R.
 RTP Transport of Encrypted AUs Content encryption modifies data before packetization of RTP packets, thus the various RFCs defining ways to encapsulate audio and video data do not apply.
 In addition, some signalling is necessary in the SDP in order to enable the decryption of the data.
 ISMACryp has defined encapsulation for some MPEG-4 codecs.
 For these codecs, the encapsulation as defined in shall be used.
 For any other encrypted media that has a defined mapping to the ISO Media File Format, the encapsulation as defined in section 7 of shall be used R.",The key message is associated with the ISMACryp stream via SDP signaling R.
669,"In addition the mobile station shall add to the stored list the PLMN code of the registered PLMN that sent the list.
 All PLMNs in the stored list shall be regarded as equivalent to each other for PLMN selection, cell selection/re-selection and handover.
 The stored list in the mobile station shall be replaced on each occurrence of the LOCATION UPDATING ACCEPT message.
 If no list is contained in the message, then the stored list in the mobile station shall be deleted.
 The list shall be stored in the mobile station while switched off so that it can be used for PLMN selection after switch on.",The mobile station shall add the PLMN code of the registered PLMN that sent this list to the stored list.
670,"One other value in both the type 3 & 4 and type 1 format is reserved.
 This leaves 133 information element identifier values available for assignment. It is possible to expand this structure to eight codesets of 133 information element identifier values each.
 One common value in the type 1 format is employed in each codeset to facilitate shifting from one codeset to another.
 The contents of this shift information element identifies the codeset to be used for the next information element or elements.
 The codeset in use at any given time is referred to as the ""active codeset"".
 ",A common value in type 1 format in each code set to facilitate conversion from one code set to another.
671,"A conflict could arise between energy saving and cell outage compensation in the following scenario. One or more candidate cells are configured to possibly take coverage of the original cell.
 The original cell is in energySaving state or is about to enter energySaving state.
 One or more candidate cells go into outage with the consequence that coverage of the original cell can not be provided.
 Prevention is hardly possible, except making the cells as outage proof as possible.
 But cell outages can happen even to the most stable cell.",There can be a conflict between power saving and battery interruption compensation in a number of situations.
672,"When operating in the linear region of a device (such as power amplifier, mixer etc.), gain through that device is constant. As the input power is increased, a point is reached when the output power of the device is not increased by the same amount as of input signal power, means there starts the compression of power at the output. A point where 1dB power is compressed at the output is known as 1dB compression point. In simple terms, if we plot the gain as a function of input power, we identify the point where the gain has dropped by 1dB. This is the 1dB compression point.","If we plot the gain as a function of input power, we can identify the point at which the gain drops by 1dB."
673,"LTE in unlicensed spectrum (LAA) feature goal is to enhance LTE to operate in unlicensed spectrum.While licensed spectrum remains 3GPP operators’ top priority to deliver advanced services and user experience, the opportunistic use of unlicensed spectrum is becoming an important complement to meet the capacity requirement. Licensed-Assisted Access will give operators the option to make use of unlicensed spectrum with a unified network, result in operational cost saving, improved spectral efficiency and a better user experience.The focus of the Release 13  is on the aggregation of a primary cell, operating in licensed spectrum to deliver critical information and guaranteed Quality of Service, with a secondary cell, operating in unlicensed spectrum to opportunistically boost data rate. A key objective of this feature is to ensure fair coexistence between LTE LAA and Wi-Fi.","While licensed spectrum remains a top priority for 3GPP operators to deliver advanced services and user experience, opportunistic use of unlicensed spectrum is becoming an important addition to meeting capacity requirements."
674,"The LTE CA  basic framework was standardized in Release 10, with the protocol allowing aggregation of up to 5 Component Carriers (CCs) in downlink and uplink. As operators have planned for deployments with the aggregation of more and more carriers, it has become necessary to expand the LTE CA framework to be able to aggregate more than 5 CCs. The goal in Release 13 is to expand LTE CA up to 32 CCs and to achieve high data rates for LTE as well as in the flexibility to aggregate large numbers of carriers in different bands. This enhanced framework will also be useful for LAA operation in unlicensed spectrum where large blocks of spectrum are available.","Release 10 of the protocol allows the LTE CA basic framework to aggregate up to 5 component carriers (CCs) in the downlink and uplink, while the goal of Release 13 is to expand this number to a maximum of 32."
675,"Beamforming and MIMO have been identified as key technologies to address the future capacity demand. But so far 3GPP evaluations for these features have mostly considered antenna arrays that exploit the azimuth dimension. So in Release 13,  3GPP RAN group is studying how two-dimensional antenna arrays can further improve the LTE spectral efficiency by also exploiting the vertical dimension for beamforming and MIMO operations. Also, while the standard currently supports MIMO systems with up to 8 antenna ports, Release 13 will look into high-order MIMO systems with up to 64 antenna ports at the eNB, to the use of higher frequencies in the future.",Beamforming and MIMO have been identified as key technologies to address future capacity needs and will be further investigated in Release 13 of the protocol.
676,"MTC work started in Release 12 to specify key physical layer and RF enablers to enhance LTE’s suitability for IoT market, the key focus for Release 13 is to define a new low complexity UE category type that supports reduced bandwidth, reduced transmit power, reduced support for downlink transmission modes, ultra-long battery life via power consumption reduction techniques and extended coverage operation. In terms of reduced bandwidth the goal is to specify 1.4 MHz operation at the terminal within any LTE system bandwidth, allowing operators to multiplex reduced bandwidth MTC devices and regular devices in their existing LTE deployments. For coverage, the goal is to improve by 15dB the coverage of delay-tolerant MTC devices, allowing operators to reach MTC devices in poor coverage conditions – such as meters located in basements.",The focus of MTC work in Release 13 of the protocol is to define a new low-complexity UE class type that enables ultra-long battery life and extended coverage operation through power reduction techniques.
677,"Release 15 targets improving the spectral efficiency for LTE small cell deployments using 10 bits per Resource Element and to achieve this 3GPP has introduce the support 1024 QAM support.
Original LAA/eLAA has been standardized within Release 13 and Release 14 respectively for purely unlicensed spectrum at 5GHz for coexistence with WiFi networks. As the CBRS specified by FCC for US, allows for 3-tier spectrum usage model (with incumbent, licensees and unlicensed uses).Release-15 aims at adjusting the frame structure 3 to operate in 3500-3700MHz band using the LAA and eLAA framework.",Release 15 of the protocol is designed to adapt the frame structure to operate in the 3500-3700MHz band using the LAA and eLAA frameworks.
678,"First time Narrow Band IoT baseline had been specified with the first release of LTE-Advanced Pro within Release 13. Release 14 is specifies the enhancements to the baseline that including positioning support, multi-cast and non-anchor carrier operations. Further Release 15 provides enhancement introduce NB-IoT small cell,TDD operation in in-band, guard-band and standalone operation modes.",The NB-IoT baseline was specified for the first time in the first release of Release 13 LTE-Advanced Pro and has been further enhanced in Releases 14 and 15.
679,"The initial 5G NR deployment are expect to be NSA (Non Standalone) where LTE system serves as primary cell for signaling anchoring and NR is added as secondary cell. In order to achieve this tight inter networking of LTE and 5G-NR , the EPC (Evolved Packet Core) required certain enhancements which includes extending the range of QoS parameters, handling of the UE capabilities, including 5G-NR parameters in the MME and controlling the access to 5G NR. On the other side of this inter-working between LTE and 5G-NR, requires the E-UTRA  (LTE cell) to be connected to 5G-CN (Core Network). This needs certain enhancements within LTE to support network slicing, flow based QoS framework, and mobility support where the handover between 5G-NR and LTE both connected to 5G-CN or where different LTE cells connected to EPC and 5G-CN.","In order to achieve the tight interconnection of LTE and 5G-NR, certain enhancements are required for EPC and the connection of E-UTRA to 5G-CN is required."
680,"UE Category information is used to allow the eNB to communicate effectively with all the UEs connected to it. The ue-Category defines a combined uplink performance capability and downlink performance capability. The UE devices like Mobile handset, dongle or other equipment are to be specified with the supported UE category, so that consumer has an idea of capability of the device before using that particular device.",The UE-Category defines the combined uplink and downlink performance capabilities to allow the eNB to communicate efficiently with all UEs connected to it.
681,"There is single UE category upto Rel 11 which defines both the DL throughput performance as well as UL throughput performance.  But in Rel 12, this single category definition got decoupled into two individual categories, where ue-CategoryDL defines the DL throughput performance and ue-CategoryUL defines the UL throughput performance. And different combinations of ue-CategoryDL and ue-CategoryUL are supported giving more flexibility in terms of choosing the DL and UL requirement.","In Release 12, the single UE category definition in Rel 11 is decoupled into two separate categories, where ue-CategoryDL defines DL throughput performance and ue-CategoryUL defines UL throughput performance."
682,"The fields DL ue-Category and UL ue-Category define downlink/uplink capability respectively. And there are defined combination set of DL ue-category and UL ue-category which are possible.
Below tables defines the only combinations for UE UL and DL Categories that are allowed to be signaled with ue-CategoryDL and ue-CategoryUL. It also defines which UE Categories a UE shall indicate in addition to the combinations for UE UL and DL Categories.","The DL ue-Category and UL ue-Category fields define downlink/uplink capabilities, respectively, and define a possible set of combinations of DL ue-category and UL ue-category."
683,"An Absolute Radio-Frequency Channel Number (ARFCN) is a code that specifies a pair of reference frequencies used for transmission and reception in radio system. In a FDD system one ARFCN number is required for downlink and another for uplink  as downlink and uplink frequencies are different while for TDD system only one ARFCN number is enough as downlink and uplink frequency remains same.
Term ARFCN started from GSM and evolved with the new technologies like it was know as UARFCN for UMTS/WCDMA, named as EARFCN for E-UTAR/LTE and now renamed as  NR-ARFCN for 5G/New Radio. NR-ARFCNs for 5G new radio are defined in 3GPP specification 38.101-1 and 38.101-2.",ARFCN is a code that specifies a pair of reference frequencies used for transmission and reception in radio system. 
684,"3GPP has proposed a Service Based Architecture for Core network with new network entities and new services to support a unified authentication framework. This framework makes 5G AKA procedure suitable for both open and access-network agnostic using three authentication methods namely 5G-AKA, EAP-AKA’, and EAP-TLS. The Frameworks allows multiple security contexts which can be established with one authentication execution, allowing the UE to move from a 3GPP access network to a non-3GPP network without having to be reauthenticated. The framework includes following network function within Core network relevant to 5G authentication.","3GPP has proposed a service based architecture for core network with new network entities and new service to support unified authentication framework. This makes 5G AKA procedure suitable for both open and access-netowork using three authentication methods, e.g., 5G-AKA, EAP-AKA'. and EAP-TLS."
685,Secure communication in any cellular network can be achieved with help of AKA procedure.  AKA is Authentication and Key Management procedure which involve mutual authentication between User Device and the network and derive crypto keys to protect the U-plane and C-plane data. Each  telecom “G” defines some authentication method to allow only legitimate users to access network and reject un-authorized users. 3GPP defined EPS-AKA for 4G LTE and similarly for 5G three authentication methods are defined.,AKA is Authentication and Key Management procedure which gives secure communication in any cellular network and involves mutual authentication between User Device and network and derive crypto keys to protect the U-plane and C-plane data.
686,"Carrier Aggregation (CA) increases the bandwidth by combining several carriers. Each aggregated carrier is referred to as a Component Carrier (CC). 5G NR CA supports up to 16 contiguous and non-contiguous CCs with different numerologies in the FR1 band and in the FR2 band. A Carrier aggregation configuration includes the type of carrier aggregation (intra-band, contiguous or not or inter-band), no. of bands and the bandwidth class. CA Bandwidth Class is a Series of Alphabets, which defines the minimum and maximum bandwidth along with the no. of  Componets Carriers. ",Carrier Aggregation (CA) increases the bandwidth by combining several carriers. 5G NR CA support upto 16 contiguous and non-contiguous CCs with different numerologies.
687,"5G cell phone baseband software expected to support 5G NR in both frequency bands i.e. sub-6 GHz and mm wave bands. Along with this, protocol software need to support 4G LTE, 3G WCDMA and 2G GSM/EDGE. Software shall also includes protocol support for non-3GPP technologies like Wi-FI, Bluetooth and NFC for short range communication. Protocol software specific at physical layer , it need to support advance baseband signal processing algorithms to enable Massive MIMO, Beam forming and interference suppression features.","5G cell phone baseband software expected to support 5G in both frequency bands. Among with this, porotocol software needs to support 4G, 3G, 2G. Software shall also includes protocol support for non-3GPP technologies like WiFi, Bluetooth, and NFC for short range communication."
688,"Next generation 5G cellular systems will operate in frequencies ranging from around 500 MHz up to 100 GHz. Till now with LTE and Wi-Fi technologies, we were operating below 6GHz and the channel models were designed and evaluated for operation at frequencies only as high as 6 GHz. The new 5G systems is to operate in bands above 6 GHz and existing channel models will not be valid, hence there is a need for accurate radio propagation models for these higher frequencies, hence it requires new channel models.
The requirements of the new channel model that can support 5G operation across frequency bands up to 100 GHz is based on the existing 3GPP channel models along with extensions to cover additional 5G modeling requirement.",5G will operate in frequencies randing from around 500 MHz upto 100 GHz. Upto now 4G and WiFi were operating below 6GHz and the channel models were designed and evaluated for operation at frequencies only as high as 6GHz.
689,"3GPP defines that 5G Core Network to have a decomposed network architecture with the introduction of a service-based interface (SBI) using HTTP/2 as a baseline communication protocol, and control plane and user plane separation (CUPS). This decomposition, SBI, and CUPS of 5G network function software strongly favoured cloud-native container-based implementation. Even though 5G network function can be built based on the legacy generation of architecture such as virtual machine based monolithic architecture, but the real benefits in terms of agility, fast innovation, hyper scalability, elasticity, and simplified operations and lifecycle management can be achieved, only when the 5G network functions (NFs) are designed and implemented on a cloud-native container-based micro services architecture.","5G core network has a decomposed network architecture with the introduction of a service-based interface. This decomposition, SBI, and CUPS of 5G network function strongly flavoured colud-native container-based implementation."
690,"3GPP standards has introduced stateless architecture for network optimization and better reliability and resiliency.
In general, a stateful network function/element must keep context information of subscriber information or transport layer association information. Hence this data must persist when the function encounters any sudden failure. On the other hand, stateless architecture is a prevalent design pattern in modern microservice-based software architecture, which necessarily has a decoupling of the application layer and the data storage layer using external data store.
For this purpose, 3GPP defines Unstructured Data Storage Function (UDSF) in TS 21.195.","3GPP introduces stateless architecture for network optimization and better reliability and resiliency, which necessarily has a decoupling of the application layer and data storage layer using external data store."
691,"In telecommunication systems, network operator allocate to each SIM card a unique identifier, known up to the 4G as an IMSI (International Mobile Subscriber Identity) and for the 5G as a  SUPI (Subscription Permanent Identifier). As authentication between a user and its  network provider is based on a shared symmetric key, it can only take place after user identification. However, if the IMSI/SUPI values are sent in plaintext over the radio access link, then users can be identified, located and tracked using these permanent identifiers.
To avoid this privacy breach, the SIM card is assigned temporary identifiers (called Temporary Mobile Subscriber Identity (TMSI) until 3G systems and GUTI for 4G and 5G systems) by the visited network. These frequently-changing temporary identifiers are then used for identification purposes over the radio access link. However, there are certain situations where authentication through the use of temporary identifiers is not possible e.g. when a user registers with a network for the first time and is not yet assigned a temporary identifier, another case is when the visited network is unable to resolve the IMSI/SUPI. from the presented TMSI/GUTI.","Network operator allocate to each SIM card a unique identifier, known up to the 4G as an IMSI and for the 5G as a SUPI. As authentication between a user and its network provider is based on a shared symmetric key, it only take place after user identification but if the IMSI/SUPI values are sent in plaintext over the radio access link, then users can be identified, located and tracked using these identifiers. To avoid this, the SIM card is assgined temporary identifiers."
692,"Carrier Aggregation (CA) increases the bandwidth by combining several carriers. Each aggregated carrier is referred to as a Component Carrier (CC). 5G NR CA supports up to 16 contiguous and non-contiguous CCs with different numerologies in the FR1 band and in the FR2 band. A Carrier aggregation configuration includes the type of carrier aggregation (intra-band, contiguous or not or inter-band), no. of bands and the bandwidth class.
CA Bandwidth Class is a Series of Alphabets, which defines the minimum and maximum bandwidth along with the no. of  Componets Carriers. ",Carrier Aggregation increases the bandwidth by combining several carriers and 5G NR CA supports up to 16 contiguous and non-contiguous CCs with different numerologies in the FR1 band and in the FR2 band.
693,"RF processing block is responsible to receive and transmit the baseband signals. This block is constitutes of a RF IC, front end module (FEM), LNA, Antennas Arrays and sensors.
RF IC enable co-existence for different radio access (Wi-FI, Cellular, GNSS etc) signals. 5G cell phone will have different antenna module to support wide range of frequency bands i.e. mm waves, sub-6 GHz bands and Low frequency bands.
RF section shall have some important sensors like Proximity Sensor,Light sensor,  Barometer,  Magnetometer, Accelerometer, Gyroscope,  Thermometer,Iris Scanner, Heart rate Monitor, Pulse Monitor.","RF processing block is responsible to receive and transmit the baseband signals. The block constitutes of a RF IC, FEM, LNA, Antennas, Arrays and sensors."
694,"A channel model is also known as radio wave propagation model, it characterizes radio wave propagation as a function of frequency, distance, environment, and other factors. In other words, we can say that channel model provides us rough idea how much distance a signal can travel in a certain environment (morphology like urban, suburban or rural etc.) with the known transmitter and receiver height.
A channel model is usually developed to predict the behavior of propagation of radio signal, for all similar channel under and similar constraints (environment, channel fading, multi-path etc). Channel models typical predict the path loss along a wireless link or effective coverage area of a transmitter.","A channel model is also known as radio wave propagation model, it characerizes wave propagation as a function of frequency, distance, environment and provides a rough idea how much distance a signal can travel in certain environment."
695,"At 3GPP TSG RAN #69 meeting the Study Item Description on “Study on channel model for frequency spectrum above 6 GHz” was approved. This study item covers the identification of the status/expectation of existing information on high frequencies e.g. spectrum allocation, scenarios of interest, measurements, etc, and the channel model(s) for frequencies above 6 GHz up to 100 GHz.
Next generation 5G cellular systems will operate in frequencies ranging from around 500 MHz up to 100 GHz. Till now with LTE and Wi-Fi technologies, we were operating below 6GHz and the channel models were designed and evaluated for operation at frequencies only as high as 6 GHz. The new 5G systems is to operate in bands above 6 GHz and existing channel models will not be valid, hence there is a need for accurate radio propagation models for these higher frequencies, hence it requires new channel models.","The 3GPP TSG RAN #60 covers the identification of the status/expectation of existing information on high frequencies e.g., spectrum allocation, scenarios of interest, measurement etc. 5G will operate in frequencies ranging from around 500 MHz up to 100 GHz, compared to LTE and WiFi which operate bellow 6GHz."
696,"5G Core Network inherits control and user plane separation (CUPS) architecture from 3GPP Release 14. In 4G EPC, S/PGWs are decomposed to S/PGW-C and S/PGW-U to provide an efficient scaling of services independently. This decomposition continues to 5G and therefore User Plane Function (UPF) plays a role only on packet processing of user traffic, while all other singling processing is done by all other Control Plane. Functions such as Session Management Function (SMF). The CUPS architecture in 5G Core can bring the benefit of cost-saving and scaling with  making Control Plane functions (SMFs) to be centralized  and User Plane Functions (UPFs) to be distributed  to the edge data centers.","5G core network follows control and user plane separation architecture from 3GPP Release 14. In 4G EPC, S/PGWs are decomposed to S/PGW-C and S/PGW-U to provide an efficient scaling of services independently. "
697,"The most outstanding change in the 5G Core Control plane is induction of Service based Interface (SBI) or Service based Architecture (SBA) from traditional Point-to-Point network architecture. With this new change, except for a few interfaces such as N2 and N4, almost every interface is now defined to use unified interface, using HTTP/2 protocol. This change made communication among NFs to be like a service mesh functions rather than serial chaining, which contributes to reduction in dependency between each interface and helps in independent scaling of each function. As a result, the agility of having new features and services across network functions is increased.","The biggest change in the 5G Core Control plane is induction of SBI or SBA from traditional point-to-point network achitecture. Expect for a few interfaces such as N2 and N4, almost every interface is now defined using HTTP/2 protocol."
698,"It is the probability that the user of a service after a request to a network receives the proceed-to-select signal within specified conditions. In 5G, successful registration to a network slice is the proceed-to-select signal to the UE. If users or subscribers cannot register to the network slice instance, they cannot access any network services in the network slice instance. This KPI is focusing on network view and following are the key matrix to measure accessibility KPI.","In 5G, successful registration to a network slice is the proceed-to-select signal to the UE. If users ot subscribers can not register to the network slice instance, they cannot access any network services in the network slice instance. There is KPI focusing on this network view."
699,"A Network Operator providing  5G NR and 4G LTE service, but it may not be possible to have 5G coverage everywhere and at some point when 5G coverage or service not available to 5G system (5GS) may attempt to fallback the RAT to 4G Evolved Packet System (4G-EPS). EPS Fallback can be defined as the mobility procedure where network trigger the procedure for UE to change Radio Access from 5G to 4G.","Network operator providing 5G NR and 4G LTE service, may not be able to have 5G coverage everywhere and at some point when 5G coverage or service is not available may attempt to fallback to 4G."
700,"5GS includes 5G RAN (Radio, DU, CU) connected to 5GC and 4G EPS includes 4G RAN (Radio, BBU) connected to 4G EPC. Individual 5G and 4G Core nodes also maintain the contol plane and user plane connectivity e.g. control plane AMF connectes to MME via N26 Interface and UPF connects to gateways via S5-U interface.",5GS includes 5G RAN connected to 5GC and 4G EPS includes 4G RAN connected to 5G EPC.
701,"FAPI is an interface, which originally meant Femtocell Application Programming Interface defines the interface between MAC-Layer#2 and PHY – Layer#1 for small cells. FAPI is specified by the Small Cell Forum and the original interface defined the interaction between a 3G MAC and PHY (SCF 048), Subsequently a version was defined between a 4G MAC and PHY (SCF 082), and recently the 5G version has been completed (SCF 222). For each wireless technology FAPI defines a set of control messages for configuring a PHY and a set of messages for exchanging data between MAC and PHY, and indicates the timing constraints of these messages.",FAPI is an interface between MAC-Layer#2 and PHY - Layer#1 for small cells. FAPI is specified by the Small Cell Forum and the original interface defined the interaction between a 3G MAC and PHY.
702," FAPI is defined between one instance of MAC and one instance of PHY. In scenarios such as CA there will be multiple instances of FAPI, one per carrier. There are two types of PHY  configuration messages are defined by the logical interface as P5 and P7. P5 Logical Interface is  for PHY control configuration which is semi-static and is being generated by a PHY control entity. The P7 logical interface is for PHY data plane messages, P7 interface data configuration is generated once per slot.","In scenarios such as CA there will be multiple instances of FAPI, one per carrier. There are two types of PHY configuration messages defined by logical interdaces P5 and P7."
703,"Once a PHY is operational the interaction between the MAC and PHY occurs at the periodicity of a slot. Since 5G supports several different subcarrier spacing these per-slot messages can be exchanged every 125 μs, 250 μs, 500 μs, or 1 ms. In fact, if a carrier is supporting several different bandwidth parts, with different subcarrier spacing, then the MAC may be exchanging FAPI messages with the PHY at different periodicities for different BWP. FAPI reduces this complexity by providing all per-slot control messages in a single downlink control message, DL_TTI.request, and all downlink MAC PDUs in a single downlink data message, TX_Data.request. Similarly, for the uplink there is a single uplink control message, UL_TTI.request, and all similar uplink is grouped together into one message, RX_Data.indication, UCI.indication, SRS.indication, and RACH.indication.","Once a PHY is operational the interaction between the MAC and PHY occurs at the periodicity of a slot. If a carrier is supporting several different bandwidth parts, with different subcarrier spacing, then the MAC may be exchanging FAPI messages with the PHY at different bandwidth parts, with different subcarrier spacing."
704,"The P7 – Data plance configuration procuedres serve two purposes for subframes procedures. Firstly, they are used to control the DL and UL frame structures. Secondly, they are used to transfer the subframe data between the L2/L3 software and PHY. ","The P7, data plane configuration serves two purposes (i) control the DL and UL frame structures (ii) used to transfer the subframe data between the L2/L3 software and PHY."
705,"When UEs tries to register first time, UE encrypt SUPI into SUCI and send a Initial Registration Requested with SUCI. AMF forward this SUCI to AUSF & UDM to retrieve the SUPI with Authentication Request. AUSF shall reply with Authentication Response with SUPI information. Further AMF generates a GUTI for this SUPI and keeps the GUTI to SUPI mapping for further registrations or PDU session requests.","UE sends a Initial Registation Request with SUCI, which is encrypted form of SUPI. AMF forwards this SUCI to AUSF and UDM to retrieve the SUPI with authentication request, then AUSF shall reply with Authentication response SUPI information."
706,"A SUPI is usually a string of 15 decimal digits. The first three digits represent the Mobile Country Code (MCC) while the next two or three form the Mobile Network Code (MNC) identifying the network operator. The remaining (nine or ten) digits are known as Mobile Subscriber Identification Number (MSIN) and represent the individual user of that particular operator. SUPI is equivalent to  IMSI which uniquely identifies the ME, is also a string of 15 digits.","SUPI is a string of 15 decimal digits consisting of the Mobile Country Code, Mobile Network Code, Mobile Subscriber Identification Number. SUPI is equivalent to IMSI which uniquely identifies the ME."
707,"IMSI – catching attacks have threatened all generations (2G/3G/4G) of mobile telecommunication for decades. As a result of facilitating backwards compatibility for legacy reasons, this privacy problem appears to have persisted. However, the 3GPP has now decided to address this issue, albeit at the cost of backward compatibility. In case of identification failure via a 5G-GUTI, unlike earlier generations, 5G security specifications do not allow plain-text transmissions of the SUPI over the radio interface. Instead, an Elliptic Curve Integrated Encryption Scheme (ECIES) – based privacy-preserving identifier containing the concealed SUPI is transmitted. This concealed SUPI is known as SUCI (Subscription Concealed Identifier ).","Unlike earlier generations, in case of identification failure via a 5G-GUTI, unlike earlier generations, 5G security specifications do not allow plain-text transmissions of SUPI over the radio interface. Instead, an Elliptic Curve Integrated Encryption Scheme (ECIES)- based privacy preserving identifier containing the concealed SUPI (also know as SUCI) is transmitted."
708,"The Buffer Status reporting (BSR) is a MAC layer procedure which is used by the UE to provide information about the amount of data available for transmission in the UL buffers to the serving gNB. In simple words, we can say that, BSR is a MAC layer message from UE to gNB informing that I have something to transmit, can you please give me a Grant to send this data?. Then gNB would allocate the bare minimum amount of UL Grant i.e. PUSCH resource in terms of RBs, if the resource is available.",The Buffer Status Reporting (BSR) is a MAC layer procedure which is used by the UE to provide information about the amount of data available for transmission. BSR is a MAC layer message from UE to gNB informing that it has something to transmit. The gNB would allocate the bare minimum amount of resource in terms of RBs.
709,"Buffer Status Reports are sent per ‘Logical Channel Group‘ (LCG) rather than per ‘Logical Channel‘ although it is possible for an LCG to include only a single Logical Channel. In general, Logical Channels with similar priority are linked to the same LCG. This allows the gNB to differentiate between the volume of highh priority data and the volume of lower priority data. E.g. Logical Channels used for signalling may be linked to a 1st LCG, while Logical Channels transferring Voice data could be linked to a 2nd LCG, and Logical Channels transferring web-browsing data could be linked to a 3rd LCG.  A UE can be configured with up to 8 LCG so the gNB has enough fllexibility when grouping the set of Logical Channels. A Logical Channel is linked to an LCG using the logicalChannelGroup IE within mac-LogicalChannelConfig.The remaining parameters associated with Buffer Stanis Reporting are configured using the BSR-Config.",Logical channels with similar priority are linked to the same LCG. This allows the gNB to differentiate between the volume of high prioity data and the volume of lower priority data.
710,"The combination of 5G NR technology and millimeter wave bands pioneer a new level of mobile performance with ultra-high speeds and low latencies. Momentum behind 28 GHz is growing, with the availability of commercial services, devices and  large bandwidth up to 850 MHz. The use of antenna arrays and beamforming enables the use of 28GHz band mmWave frequencies for wireless communication.",5G NR technology and milimeter wave bands pioneer a new level of mobile performance with ultra-high speeds and low latencies.
711,"From an operator’s point of view, the viability of any new technology depends on fulfilling the business case given by the business model. The business case is governed by two main factors: the required capital expenditure (CAPEX), followed by the cost to operate and maintain the network (OPEX).","The viability of any new technology depends on fulfilling the business case given by the business model and governed by two main factos: the required capital expenditure, followed by the cost to operate and maintain the network."
712,"mmWave allows beamforming that helps overcome the higher path loss, but coverage is still limited while compared to frequencies below 6 GHz, the primary spectrum being utilized by service operators. To ensure adequate coverage, a link budget analysis is essential.","mmWave allows beamforming to overcome higher path loss, but coverage is still limited. To resolve this a link budget analysis is essential."