36331 3GPP PDF

36331 3GPP PDF

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.

Author: Shakaran Fesar
Country: Azerbaijan
Language: English (Spanish)
Genre: Science
Published (Last): 9 June 2008
Pages: 142
PDF File Size: 11.73 Mb
ePub File Size: 6.40 Mb
ISBN: 644-7-72494-965-3
Downloads: 88281
Price: Free* [*Free Regsitration Required]
Uploader: Tautilar

System information may be transmitted a number of times with the same content within a modification period, as defined by its scheduling. The UE acquires the detailed time-domain scheduling and other information, e. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.

However, the UE only accepts a handover message when 3631 has been activated. Upon initiation of the procedure, the UE shall: Lower layers discard RRC messages for which the integrity check has failed and indicate the integrity verification check failure to RRC. The length of the SI-window is common for all SI messages, and is configurable. The cell in which the re-establishment procedure succeeds becomes the PCell while SCells, if configured, are released.

www.3gpp.org – /ftp/specs/archive/36_series/36.331/

Only in exceptional 3ypp, as specified within this specification, TS Such RN-specific aspects are not applicable to the UE. The number of warning messages that a UE can re-assemble 3vpp is a function of UE implementation. Unless explicitly stated otherwise in 33631 procedural specification, the system information acquisition procedure overwrites any stored system information, i.

Security mode command, failure The purpose of this procedure is to activate AS security upon RRC connection establishment. That is, the 3hpp to the message used to activate security is not ciphered, while the subsequent messages e.


Further details about the services provided by Packet Data Convergence Protocol layer e. The physical layer imposes a limit to the maximum size a SIB can take. 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. If this is not the case, i. The AS applies three different security keys: The RRC messages to activate security command and successful response are integrity protected, while ciphering is started only after completion of the procedure.

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.

If no paging message is received by the UE during g3pp modification period, the UE may assume that no change of system information will occur at the next modification period boundary.

No AS-parameters are exchanged to serve as inputs for the derivation of the new AS keys at connection establishment. The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

The UE may apply above failure handling also in case the RRCConnectionReconfiguration message causes a protocol error for which the generic error handling as defined in 5.

RRC handles the configuration of the security parameters which are part of the AS configuration: The UE applies the previously acquired system information until the UE acquires the new system information. Segmentation can be applied for the delivery of a CMAS notification. This connection resumption succeeds only if the accessed cell is prepared, i.

The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The use of integrity protection may be configured only upon DRB establishment and reconfigured only upon handover or upon the first reconfiguration following RRC connection re-establishment.


If the UE receives a Paging message including the systemInfoModification, it knows that the 3gpp information will change at the next modification period boundary.

For further details see TS The UE may discard SRB2 messages and data that it receives prior to completing the reconfiguration used to resume these bearers. This specification is organised as follows: There may 363331 multiple SI messages transmitted with the same periodicity. The network triggers the handover procedure e. The further details are specified in TS In addition, an overflow counter mechanism is used: Neither integrity protection nor ciphering applies for SRB0.

Normal measurement and mobility procedures are used to support handover to cells broadcasting a CSG identity.

– /ftp/specs/archive/36_series//

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. Correspondingly, the UE initially considers lists to be empty e. In addition to the state transitions shown in Figure 4.

The segmentation is fixed for transmission of a given CMAS notification within a cell i. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5. However, the UE needs to perform system information acquisition upon cell re-selection. Radio configuration is not just the resource configuration but includes other configurations like MeasConfig and OtherConfig.

Before 3ggpp the handover message to the UE, the source eNB prepares one or more target cells. References are either specific identified by date of publication, edition number, version number, etc.