Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan Moby Dick Consolidated System Integration Plan
D0103v1.doc Version 1 6.7.2003 4.3.4.4.1 Services provided to the upper layer • Transparent data transfer. This service transmits upper layer PDUs without adding any protocol information, possibly including segmentation/reassembly functionality. • Unacknowledged data transfer. This service transmits upper layer PDUs without guaranteeing delivery to the peer entity. The unacknowledged data transfer mode has the following characteristics: o Detection of erroneous data: By using the sequence-number check function. o Immediate delivery: Delivery of a SDU to the upper layer as soon as it arrives at the receiver. • Acknowledged data transfer. This service transmits upper layer PDUs and guarantees delivery to the peer entity. In case RLC is unable to deliver the data correctly, the user of RLC at the transmitting side is notified. For this service, only in-sequence delivery is supported. The acknowledged data transfer mode has the following characteristics: o Error-free delivery: Error-free delivery is ensured by means of retransmission. The receiving RLC entity delivers only error-free SDUs to the upper layer. o Unique delivery: The RLC sublayer delivers each SDU only once to the receiving upper layer using duplication detection function. o In-sequence delivery: RLC sublayer delivers SDUs to the receiving upper layer entity in the same order as the transmitting upper layer entity submits them to the RLC sublayer. o Out-of-sequence delivery: Alternatively to in-sequence delivery, the receiving RLC entity delivers SDUs to upper layer in different order than submitted to RLC sublayer at the transmitting side. • Maintenance of QoS as defined by upper layers. The retransmission protocol shall be configurable by layer 3 to provide different levels of QoS. This can be controlled. • Notification of unrecoverable errors. RLC notifies the upper layer of errors that cannot be resolved by RLC itself by normal exception handling procedures, e.g. by adjusting the maximum number of retransmissions according to delay requirements. There is a single RLC connection per Radio Bearer. 4.3.4.4.2 RLC Functions The RLC sub layer implements the following functions: • Segmentation and reassembly. • Concatenation • Padding. • Transfer of user data. • Error correction. • In-sequence delivery of upper layer PDUs. • Duplicate Detection. • Flow control. • Sequence number check. • Protocol error detection and recovery. • SDU discard. 4.3.4.5 PDCP Services and Functions This section provides an overview on services and functions provided by the Packet Data Convergence Protocol (PDCP). A detailed description of the PDCP is given in [25.324]. 4.3.4.5.1 PDCP Services provided to upper layers - PDCP SDU delivery. 4.3.4.5.2 PDCP Functions - Transfer of user data. Transmission of user data means that PDCP receives PDCP SDU from the NAS and forwards it to the RLC layer and vice versa. 4.3.4.6 RRC Specification The RRC sub-component is based on the 3GPP specification [25.331], but modified to fit the needs of the Moby Dick framework whenever needed. 4.3.4.6.1 Services provided to the Non Access Stratum • General Control The GC SAP provides an information broadcast service. It is used to enable the NAS entities (IP Network) to provide information and to give commands that do not relate to specific users. There is one D0103v1.doc 92 / 168
D0103v1.doc Version 1 6.7.2003 General Control SAP per Radio Gateway connection point. On the UE side, there is a single General Control SAP in an MS. This service broadcasts information to all UEs in the cell area. • Notification The Nt SAP provides paging and notification broadcast services. There is one Notification SAP per RG connection point. On the UE side, there is a single Notification SAP (a Paging SAP) in an MS. The paging service sends information to a specific UE(s). The information is broadcast in the cell area but addressed to a specific UE(s). • Dedicated Control The DC SAP provides services for establishment/release of a connection and transfer of messages using this connection. It should also be possible to transfer a message during the establishment phase. A connection is a relationship with a temporary context in the RG. The context in the RG is initiated at the establishment of the connection, and erased when the connection is released. There are typically a great number of Dedicated Control SAPs per RG connection point. SAPs are identified by a SAPI at the AS boundary. During the lifetime of a connection, the connection can be identified unambiguously by the SAPI of the associated SAP, and the SAPI is used as a reference in the exchanges at the AS boundary on the infrastructure side. On the UE side, there is a single dedicated control SAP. The information transfer service sends a signalling message using the earlier established connection. 4.3.4.6.2 RRC functions The Radio Resource Control (RRC) layer handles the control plane signalling of Layer 3 between the UEs and the RG. The RRC performs the following functions: • Broadcast of information provided by the non-access stratum. The RRC layer performs system information broadcasting from the network to all UEs. The system information is normally repeated on a regular basis. How it is repeated is controlled by the non-access stratum. The RRC layer performs the scheduling, segmentation and repetition. This function supports broadcast of higher layer (above RRC) information. This information may be cell specific or not. As an example RRC may broadcast Router Advertisement IP packets and/or the list of suitable neighbouring cells. • Broadcast of information related to the access stratum. The RRC layer performs system information broadcasting from the network to all UEs. The system information is normally repeated on a regular basis. The RRC layer performs the scheduling, segmentation and repetition. This function supports broadcast of typically cell-specific information, such as common channels parameters. • Establishment, re-establishment, maintenance and release of an RRC connection between the UE and RG. The establishment of an RRC connection is initiated by a request from RCF at the UE side to establish the first Signalling Connection for the UE. The establishment of an RRC connection includes a layer 2 signalling link establishment. The release of an RRC connection can be initiated by a request from RCF to release the Connection for the UE or by the RRC layer itself in case of RRC connection failure. In case of connection loss, the UE requests re-establishment of the RRC connection. In case of RRC connection failure, RRC releases resources associated with the RRC connection. • Establishment and release of Radio Bearers. The RRC layer can, on request from RCF, perform the establishment and release of Radio Bearers in the user plane. A number of Radio Bearers can be established to an UE at the same time. At establishment, the RRC layer performs admission control and selects parameters describing the Radio Bearer processing in layer 2 and layer 1, based on information from RCF. This function includes coordination of the radio resource allocation between multiple radio bearers related to the same RRC connection. RRC controls the radio resources in the uplink and downlink such that UE and Network can communicate using unbalanced radio resources (asymmetric uplink and downlink). • Paging/notification. The RRC layer can broadcast paging information from the network to selected UEs. Higher layers on the network side can request paging and notification. The RRC layer can also propagate paging during an established RRC connection. • Control of requested QoS. This function shall ensure that the QoS requested for the Radio Bearers can be met. This includes the allocation of a sufficient number of radio resources. • UE measurement reporting and control of the reporting. The measurements performed by the UE are controlled by the RRC layer, in terms of what to measure, when to measure and how to report, including UMTS air interface. The RRC layer may also perform the reporting of the measurements from the UE to the network (currently not planned in Moby Dick). • Initial cell selection and re-selection in idle mode. Selection of the most suitable cell based on idle mode measurements and cell selection criteria. D0103v1.doc 93 / 168
- Page 41 and 42: D0103v1.doc Version 1 6.7.2003 Ackn
- Page 43 and 44: D0103v1.doc Version 1 6.7.2003 inst
- Page 45 and 46: D0103v1.doc Version 1 6.7.2003 MT P
- Page 47 and 48: D0103v1.doc Version 1 6.7.2003 The
- Page 49 and 50: D0103v1.doc Version 1 6.7.2003 RtSo
- Page 51 and 52: D0103v1.doc Version 1 6.7.2003 auth
- Page 53 and 54: D0103v1.doc Version 1 6.7.2003 In a
- Page 55 and 56: D0103v1.doc Version 1 6.7.2003 AR s
- Page 57 and 58: D0103v1.doc Version 1 6.7.2003 4.2.
- Page 59 and 60: D0103v1.doc Version 1 6.7.2003 Even
- Page 61 and 62: D0103v1.doc Version 1 6.7.2003 4.2.
- Page 63 and 64: D0103v1.doc Version 1 6.7.2003 Filt
- Page 65 and 66: D0103v1.doc Version 1 6.7.2003 4.2.
- Page 67 and 68: D0103v1.doc Version 1 6.7.2003 •
- Page 69 and 70: D0103v1.doc Version 1 6.7.2003 The
- Page 71 and 72: D0103v1.doc Version 1 6.7.2003 is t
- Page 73 and 74: D0103v1.doc Version 1 6.7.2003 4.3
- Page 75 and 76: D0103v1.doc Version 1 6.7.2003 4.3.
- Page 77 and 78: D0103v1.doc Version 1 6.7.2003 This
- Page 79 and 80: D0103v1.doc Version 1 6.7.2003 This
- Page 81 and 82: D0103v1.doc Version 1 6.7.2003 4.3.
- Page 83 and 84: D0103v1.doc Version 1 6.7.2003 4.3.
- Page 85 and 86: D0103v1.doc Version 1 6.7.2003 The
- Page 87 and 88: D0103v1.doc Version 1 6.7.2003 4.3.
- Page 89 and 90: D0103v1.doc Version 1 6.7.2003 be u
- Page 91: D0103v1.doc Version 1 6.7.2003 o Ma
- Page 95 and 96: D0103v1.doc Version 1 6.7.2003 Upli
- Page 97 and 98: D0103v1.doc Version 1 6.7.2003 Now
- Page 99 and 100: D0103v1.doc Version 1 6.7.2003 3. D
- Page 101 and 102: D0103v1.doc Version 1 6.7.2003 User
- Page 103 and 104: D0103v1.doc Version 1 6.7.2003 Inte
- Page 105 and 106: D0103v1.doc Version 1 6.7.2003 User
- Page 107 and 108: D0103v1.doc Version 1 6.7.2003 Serv
- Page 109 and 110: D0103v1.doc Version 1 6.7.2003 S1 E
- Page 111 and 112: D0103v1.doc Version 1 6.7.2003 The
- Page 113 and 114: D0103v1.doc Version 1 6.7.2003 Old
- Page 115 and 116: D0103v1.doc Version 1 6.7.2003 This
- Page 117 and 118: D0103v1.doc Version 1 6.7.2003 Leng
- Page 119 and 120: D0103v1.doc Version 1 6.7.2003 4.5.
- Page 121 and 122: D0103v1.doc Version 1 6.7.2003 MN M
- Page 123 and 124: D0103v1.doc Version 1 6.7.2003 4.5.
- Page 125 and 126: D0103v1.doc Version 1 6.7.2003 Afte
- Page 127 and 128: D0103v1.doc Version 1 6.7.2003 Pack
- Page 129 and 130: D0103v1.doc Version 1 6.7.2003 4.5.
- Page 131 and 132: D0103v1.doc Version 1 6.7.2003 miss
- Page 133 and 134: D0103v1.doc Version 1 6.7.2003 Conn
- Page 135 and 136: D0103v1.doc Version 1 6.7.2003 4.5.
- Page 137 and 138: D0103v1.doc Version 1 6.7.2003 Acce
- Page 139 and 140: D0103v1.doc Version 1 6.7.2003 Logg
- Page 141 and 142: D0103v1.doc Version 1 6.7.2003 repr
D0103v1.doc Version 1 6.7.2003<br />
General Control SAP per Radio Gateway connection point. On the UE side, there is a single General<br />
Control SAP in an MS. This service broadcasts information to all UEs in the cell area.<br />
• Notification<br />
The Nt SAP provides paging and notification broadcast services. There is one Notification SAP per RG<br />
connection point. On the UE side, there is a single Notification SAP (a Paging SAP) in an MS. The<br />
paging service sends information to a specific UE(s). The information is broadcast in the cell area but<br />
addressed to a specific UE(s).<br />
• Dedicated Control<br />
The DC SAP provides services for establishment/release of a connection and transfer of messages using<br />
this connection. It should also be possible to transfer a message during the establishment phase. A<br />
connection is a relationship with a temporary context in the RG. The context in the RG is initiated at the<br />
establishment of the connection, and erased when the connection is released.<br />
There are typically a great number of Dedicated Control SAPs per RG connection point. SAPs are<br />
identified by a SAPI at the AS boundary. During the lifetime of a connection, the connection can be<br />
identified unambiguously by the SAPI of the associated SAP, and the SAPI is used as a reference in the<br />
exchanges at the AS boundary on the infrastructure side. On the UE side, there is a single dedicated<br />
control SAP.<br />
The information transfer service sends a signalling message using the earlier established connection.<br />
4.3.4.6.2 RRC functions<br />
The Radio Resource Control (RRC) layer handles the control plane signalling of Layer 3 between the<br />
UEs and the RG. The RRC performs the following functions:<br />
• Broadcast of information provided by the non-access stratum. The RRC layer performs system<br />
information broadcasting from the network to all UEs. The system information is normally repeated<br />
on a regular basis. How it is repeated is controlled by the non-access stratum. The RRC layer<br />
performs the scheduling, segmentation and repetition. This function supports broadcast of higher<br />
layer (above RRC) information. This information may be cell specific or not. As an example RRC<br />
may broadcast Router Advertisement IP packets and/or the list of suitable neighbouring cells.<br />
• Broadcast of information related to the access stratum. The RRC layer performs system<br />
information broadcasting from the network to all UEs. The system information is normally repeated<br />
on a regular basis. The RRC layer performs the scheduling, segmentation and repetition. This<br />
function supports broadcast of typically cell-specific information, such as common channels<br />
parameters.<br />
• Establishment, re-establishment, maintenance and release of an RRC connection between the<br />
UE and RG. The establishment of an RRC connection is initiated by a request from RCF at the UE<br />
side to establish the first Signalling Connection for the UE. The establishment of an RRC connection<br />
includes a layer 2 signalling link establishment. The release of an RRC connection can be initiated by<br />
a request from RCF to release the Connection for the UE or by the RRC layer itself in case of RRC<br />
connection failure. In case of connection loss, the UE requests re-establishment of the RRC<br />
connection. In case of RRC connection failure, RRC releases resources associated with the RRC<br />
connection.<br />
• Establishment and release of Radio Bearers. The RRC layer can, on request from RCF, perform<br />
the establishment and release of Radio Bearers in the user plane. A number of Radio Bearers can be<br />
established to an UE at the same time. At establishment, the RRC layer performs admission control<br />
and selects parameters describing the Radio Bearer processing in layer 2 and layer 1, based on<br />
information from RCF.<br />
This function includes coordination of the radio resource allocation between multiple radio bearers<br />
related to the same RRC connection. RRC controls the radio resources in the uplink and downlink<br />
such that UE and Network can communicate using unbalanced radio resources (asymmetric uplink<br />
and downlink).<br />
• Paging/notification. The RRC layer can broadcast paging information from the network to selected<br />
UEs. Higher layers on the network side can request paging and notification. The RRC layer can also<br />
propagate paging during an established RRC connection.<br />
• Control of requested QoS. This function shall ensure that the QoS requested for the Radio Bearers<br />
can be met. This includes the allocation of a sufficient number of radio resources.<br />
• UE measurement reporting and control of the reporting. The measurements performed by the UE<br />
are controlled by the RRC layer, in terms of what to measure, when to measure and how to report,<br />
including UMTS air interface. The RRC layer may also perform the reporting of the measurements<br />
from the UE to the network (currently not planned in <strong>Moby</strong> <strong>Dick</strong>).<br />
• Initial cell selection and re-selection in idle mode. Selection of the most suitable cell based on idle<br />
mode measurements and cell selection criteria.<br />
D0103v1.doc 93 / 168