The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the. 3GPP. (j). Service accessibility. Retrieved 21 September from Home page of 3GPP technical specification groups (TSGs). /htmlinfo/htm.
|Published (Last):||28 May 2016|
|PDF File Size:||9.48 Mb|
|ePub File Size:||8.82 Mb|
|Price:||Free* [*Free Regsitration Required]|
The present document has 3ggpp been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only.
www.3gpp.org – /ftp/specs/archive/36_series/36.331/
The Organizational Partners accept no liability for any use of this Specification. The copyright and the foregoing restriction extend to reproduction in all media. Release 8 and 9 AS feature handling Release 10 AS feature handling The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval.
Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: The scope of the present document also includes: References are either specific identified by date of publication, edition number, version number, etc.
For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document including a GSM documenta non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. A term defined in the present document takes precedence over the definition of the same term, if any, in TR Commercial Mobile Alert System: The individual contents of an information element are referred as fields. Mathematical function used to ’round down’ i. A structural element containing a single or multiple fields is referred as information element.
An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR Such RN-specific aspects are not applicable to the UE. This specification is organised as follows: If this is not the case, i. The RRC states can further be characterised as follows: Performs logging of available measurements together with location and time for logged measurement configured UEs. The details of the CDMA state models are out of the scope of this specification.
In addition to the state transitions shown in Figure 4. More specifically, the following three SRBs are defined: In downlink piggybacking of NAS messages is used only for one dependant i. Further details about the services provided by Packet Data Convergence 3gp; layer e.
The services provided by Radio Link Control layer e. Further details about the services provided by Medium Access Control layer e. The services provided by physical layer 3tpp. In addition sub-clause 5.
NAS dedicated information transfer, UE capability transfer, sub-clause 5. At each point in time, the UE keeps a single value for each field except for during handover when the UE temporarily stores the previous configuration so it can revert back upon handover failure. Correspondingly, the UE initially considers lists to be empty e. The MIB includes a limited number of most essential and most frequently transmitted parameters that are needed to acquire other information from the cell, and is transmitted on BCH.
There may be multiple SI messages transmitted with the same periodicity.
The physical layer imposes a limit to the maximum size a SIB can take. When DCI format 1C is used the maximum allowed by the physical layer is bits bytes while for format 1A the limit is bits bytessee TS The UE applies the system information acquisition and change monitoring procedures for the PCell only.
An RN configured with an RN subframe configuration does not need to apply the system information acquisition and change monitoring procedures. For RNs configured with an RN subframe configuration, the system information contained in this dedicated signalling replaces any corresponding stored system information and takes precedence over any corresponding system information acquired through the system information acquisition procedure.
The dedicated system information remains valid until overridden. The SystemInformationBlockType1 uses a fixed schedule with a periodicity of 80 ms and repetitions made within 80 ms. The SI messages are transmitted within periodically occurring time domain windows referred to as SI-windows using dynamic scheduling.
That is, within one SI-window only the corresponding SI is transmitted. The length of the SI-window is common for all SI messages, and is configurable. The UE acquires the detailed time-domain scheduling and other information, e. 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 is configured by system information. When the network changes some of the system information, it first notifies the UEs about this change, i.
In the next modification period, the network transmits the updated system information. These general principles are illustrated in figure 5. Upon receiving a change notification, the UE acquires the new system information immediately from the start of the next modification period. The UE applies the previously acquired system information until the UE acquires the new system information. If the UE receives a Paging message including the systemInfoModification, it knows that the system information will change at the next modification period boundary.
Although the UE may be informed about changes in system information, no further details are provided e. UEs may use systemInfoValueTag, e. Additionally, the UE considers stored system information to be invalid after 3 hours from the moment it was successfully confirmed as valid, unless specified otherwise.
If no paging message is received by the UE during a modification period, the UE may assume that no change of system information will occur at the next modification period boundary. Segmentation can be applied for the delivery of a secondary notification.
The segmentation is fixed for transmission of a given secondary notification within a cell i. Segmentation can be applied for the delivery of a CMAS notification.
The segmentation is fixed for transmission of a given CMAS notification within a cell i. Unless explicitly stated otherwise in the procedural specification, the system information acquisition procedure overwrites any stored system information, i.
The UE continues using the previously received system information until the new system information has been acquired. The number of warning messages that a UE can re-assemble simultaneously is a function of UE implementation. However, the UE only accepts a handover message when security has been activated. The RRC messages to activate security command and successful response are integrity protected, while ciphering is started only after completion of the procedure.
That is, the response to the message used to activate security is not ciphered, while the subsequent messages e.
The PCell is used to provide the security inputs and upper layer system information i. SCells are used to provide additional downlink and optionally uplink radio resources. Only in exceptional cases, as specified within this specification, TS RRC handles the configuration of the security parameters which are part of the AS configuration: The ciphering algorithm is common for all radio bearers i.
Neither 366331 protection nor ciphering applies for SRB0. RRC integrity and ciphering are always activated together, i. RRC integrity and ciphering are never de-activated. However, it is possible to switch to a ‘NULL’ ciphering algorithm eea0. Lower layers discard RRC messages for which the integrity check has failed and indicate the integrity verification check failure to RRC. The AS 36313 three different security keys: Upon connection establishment new AS keys are derived.
No AS-parameters are exchanged to serve as inputs for the derivation of the new AS keys at connection establishment.
The integrity and ciphering of the RRC message used to perform handover is based on the security configuration used prior to the handover and is performed by the source eNB. The integrity and ciphering algorithms can only be changed upon handover. In addition, an overflow counter mechanism is used: In order to avoid such re-use, the eNB may e.
The use of integrity protection may be 3gop only upon DRB establishment and reconfigured only upon handover or upon the first reconfiguration following RRC connection re-establishment. The network triggers the handover procedure e. To facilitate this, the network may configure the UE to perform measurement reporting possibly including the configuration of measurement gaps. The network may also initiate handover blindly, i.
Before sending the handover message to the UE, the source eNB prepares one or more target cells. The source eNB selects the target PCell. The source eNB may also provide the target eNB with a list of best cells on each frequency for which measurement information is available, in order of decreasing RSRP.
The source eNB may also include available measurement information for the cells provided in the list. The target eNB decides which SCells are configured for use after handover, which may include cells 3vpp than the ones indicated by the source eNB.
The source eNB transparently i.