hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.6 Bearer-number-present | The BOOLEAN variable bearer-number-present is used in the return (from-UE) direction only and specifies whether the sequence timing (containing the information fields timing-required, fwd-bearer and slot-num) is present. If this flag is set to '1', then this sequence is present. The information is used by the RNC to de... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.7 Timing-required (T) | The BOOLEAN variable timing-required indicates whether the UE requires timing correction information. This flag is set to '1' whenever the UE transmits an initial or un-timed random access burst in a contention slot. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.8 FwdBearer | The variable fwd-bearer field is a three-bit field which contains the f-bearer value transmitted by the RNC in the bulletin board (see clause 5.4.4) identifying the forward bearer to which the UE is currently tuned. FwdBearer ::= INTEGER (0..7) |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.9 SlotNumber | The variable slot-num field is a four-bit field which indicates in which slot position within the return frame the UE considers that it is currently transmitting. Return slot timing is synchronized, but offset from, forward frames. Slot-num indicates the slot position within the return frame, with the return frame havi... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.10 TranslatedBearerConnectionID | The variable tbcn-id is a 12-bit address field used to identify a specific connection within the scope of the Bearer Control object managing this bearer. It is mapped to a Bearer Connection ID during the Establishment, Modify or Handover processes. TranslatedBearerConnectionID ::= INTEGER (0..4095) |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.11 ComSigAddress | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.11.0 General | The parameter comsig-addr carries the Non Access Stratum (NAS) UE Identity which is used to address common signalling messages, and the data type ComSigAddress is defined as follows: ComSigAddress ::= SEQUENCE { ue-id-type UEIdType, intial-ue-identity CHOICE { p-tmsi-seq SEQUENCE { reserved1 BIT STRING (SIZE (4)), plmn... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.11.1 Ue-id-type | The data type UEIdType is defined as follows: UEIdType ::= INTEGER { p-tmsi (0), tmsi (1), imsi (2), imei (3), imsi-DS-41 (4) } (0..15) The data types used in the initial-ue-identity field are as specified in ETSI TS 125 331 [1], clause 10.3.3.15. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.11.2 P-tmsi-seq | The p-tmsi-seq is used if the registration signalling uses a P-TMSI in the ComSigAddress. Since P-TMSI is only unique within one routing area, the plmn-id and lac (location area code) to which the P-TMSI relates are included. NOTE: Normally the Routing Area Identification (RAI) would also need to be included to uniquel... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.11.3 Tmsi-seq | The tmsi-seq is used if the registration signalling uses a Temporary Mobile Subscriber Identity (TMSI) in the ComSigAddress. Since TMSI is only unique within one location area, the plmn-id and lac (location area code) to which the TMSI relates are included. In this case ue-id-type and initial-ue-identity are encoded in... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.11.4 Imsi | In the case that neither TMSI nor P-TMSI are available then the International Mobile Subscriber Identity (IMSI) shall be used as the initial-ue-identity (ue-id-type = 2). The IMSI is defined in ETSI TS 125 331 [1], clauses 10.3.1.5 and 11.3 as follows: IMSI-GSM-MAP ::= SEQUENCE (SIZE (6..15)) OF Digit with Digit ::= IN... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.11.5 Imei | In the case that no SIM card is inserted in the UE and that registration without SIM card is permitted (see clause 5.7.19) then the International Mobile Equipment Identity (IMEI) shall be used as the initial-ue-identity (ue-id-type = 3). The IMEI is defined in ETSI TS 125 331 [1], clauses 10.3.1.4 and 11.3 as follows: ... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.11.6 Imsi-DS-41 | The imsi-DS-41 parameter is used if a SIM card issued by a network to ANSI-41 standard is inserted into the UE. In this case, ue-id-type = 4 and the data type IMSI-DS-41 is defined in ETSI TS 125 331 [1], clause 11.3 as follows: IMSI-DS-41 ::= OCTET STRING (SIZE (5..7)) The variable length of the imsi-DS-41 parameter i... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.12 Common Signalling (ComSig) Types | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.12.1 ToMobileComSigType | The variable com-sig-type is defined in the to-UE direction as follows: ToMobileComSigType ::= INTEGER { information (1), paging-type-1 (2), register-ack (3), register-rej (4), deregister-common (5) } (0..7) |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.12.2 FromMobileComSigType | The variable com-sig-type is defined in the from-UE direction as follows: FromMobileComSigType ::= INTEGER { register (2) } (0..7) |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.12.3 Comsig-or-ext-addr | The boolean variable comsig-or-ext-addr is used to specify whether Common Signalling or extended addressing is used in the BCtPDU Header. If comsig-or-ext-addr is set to '1' then Common Signalling is used in the BCtPDU Header (see clause 5.1.5.11). If comsig-or-ext-addr is set to '0', then extended addressing is used i... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.12.4 Ext-addr-type-and-address | The sequence ext-addr-type-and-address consists of the variable ext-addr-type and the variable extended-address. At present, extended-address is always of type BCnID that allows a connection to be addressed by its Bearer Connection ID (BCnID). The variable ext-addr-type allows adding further addressing mechanisms in bo... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.13 Continuation-burst | The Boolean variable continuation-burst (con) is set to TRUE when a burst will be transmitted in the next slot only if the burst or continuous sequence of bursts is being preceded with a Preamble Acquisition sequence. This information is used to signal to the RAN demodulator and decoder that a subsequent transmission w... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.14 Backoff-and-bcnid | The sequence backoff-and-bcnid is used in the LdrBCtPDUHeader for two purposes: 1) to provide for the UE to use addressing on the basis of Bearer Connection IDs (see clause 5.1.3.2); and 2) to allow the UE to inform the RNC of the maximum level of backoff (in the variable backoff in units of one dB) from the maximum po... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.6 BCtPayload | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.6.0 General | The bct-payload field contains either a Bearer Connection PDU (BCnPDU) or an Adaptation Layer Common Signalling PDU (ALComPDU) as determined by the header parameters. BCtPayload ::= CHOICE { common-pdu ALComPDU, bcn-pdu BCnPDU } |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.6.1 BCnPDU | The bcn-pdu contains a Bearer Connection Layer Protocol Data Unit, the contents of which are transparent to the Bearer Control Layer. For a definition of Bearer Connection Protocol Data Unit, refer to ETSI TS 102 744-3-3 [11]. BCnPDU ::= OCTET STRING (SIZE (0..255)) |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.6.2 ALComPDU | The common-pdu contains an Adaptation Layer Common Signalling Protocol Data Unit (ALComPDU), the contents of which are transparent to the Bearer Control Layer. For a definition of Adaptation Layer Common Signalling Protocol Data Unit, refer to ETSI TS 102 744-3-5 [13]. ALComPDU ::= OCTET STRING (SIZE (0..255)) |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.7 CRC | The crc field is used to identify erroneous Bearer Control PDUs. Bearer Control PDUs which do not have a valid CRC shall be discarded by the receiving Bearer Control process unless the Bearer Connection supports the delivery of erroneous PDUs (see ETSI TS 102 744-3-2 [10]). The Generator Polynomial x16 + x12 + x5 + 1 a... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.2 Bearer Control Embedded Protocol Data Unit ( BCtEPDU) | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.2.1 Bearer Control Embedded PDU Structure | The Bearer Control Embedded PDU (BCtEPDU) is contained within an Establish, Modify or Handover Adaptation Layer Signalling PDU (ALSigPDU) as well as the RegisterAck Common Signalling PDU (ALComPDU) and is used to carry Bearer Control specific information associated with the connection synchronously with the AL-SigPDU. ... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.2.2 BCtESDU Lists | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.2.2.1 AttachBCtESDUList | The AttachBCtESDUList is used to carry Bearer Control parameters required to attach a connection to the Bearer Control (as occurs during the Establishment of new connections, including the RegisterAck process) and is structured as follows: AttachBCtESDUList ::= SEQUENCE { attached-conn-info AttachedConnInfo, hardware-i... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.2.2.2 ReattachBCtESDUList | The ReattachBCtESDUList is used to carry Bearer Control parameters required to reattach a connection to the Bearer Control (as occurs during the Handover of connections) and is structured as follows: ReattachBCtESDUlist ::= SEQUENCE { reattached-conn-info-list SEQUENCE OF ReattachedConnInfo, hardware-info-list SEQUENCE... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.2.2.3 SystemInformationBCtESDUList | The ESDU-List is sent in the SystemInformation AL-Sig-PDU to transfer system information to a UE in connected mode. The ESDU-List has the following structure: SystemInformationBCtESDUList ::= SEQUENCE { spot-beam-maps SEQUENCE OF BCtESDU OPTIONAL, -- of type SpotBeamMap bearer-table-update SEQUENCE OF BCtESDU OPTIONAL,... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.2.3 BCtESDU Sequences | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.2.3.1 AttachedConnInfo | This sequence of SDUs is used to provide the parameters associated with the connection which is being established at the bearer connection level. AttachedConnInfo ::= SEQUENCE { conn-association BCtESDU OPTIONAL -- of type ConnectionAssociation, conn-avp-list BCtESDU OPTIONAL -- of type AVPList } Conn-association (see ... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.2.3.2 ReattachedConnInfo | This sequence of SDUs is used to provide the parameters associated with the bearer connections which are being handed over to this bearer control during a Handover operation. ReattachedConnInfo ::= SEQUENCE { conn-reassociation BCtESDU -- of type ConnectionReassociation, conn-avp-list ETSI ETSI TS 102 744-3-1 V1.1.1 (2... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.2.3.3 ModifiedConnInfo | This sequence of SDUs is used to provide bearer control layer parameters associated with the bearer connection which is being modified. ModifiedConnInfo ::= SEQUENCE { conn-avp-list BCtESDU -- of type AVPList } NOTE: Although the data type contains one element only, it has been defined as SEQUENCE in order to comply wi... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.3 Bearer Control SDUs (BCtSDU) | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.3.0 General | Bearer Control SDUs (BCtSDUs) are used for the peer-to-peer communication between Bearer Control Processes at the UE and the RNC. Tables 5.2 and 5.3 define the different BCtSDU Types which can be sent either by the UE or the RNC. Table 5.2: From-UE Bearer Control SDU Types SDUType Interpretation Contained In 0x00 ConnP... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.3.1 Bearer Control SDU Structure (BCtSDU) | The Bearer Control SDU (BCtSDU) Structure is as follows and the format is shown in Figures 5.38 and 5.39: BCtSDU ::= SEQUENCE { bct-sdu-follows BOOLEAN, type-and-length CHOICE { short SEQUENCE { extended-length BOOLEAN, -- FALSE s-type ShortBCtSigType, s-length INTEGER (1..8) }, long SEQUENCE { extended-length BOOLEAN,... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.3.2 BCtSDU Parameters | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.3.2.1 Bct-sdu-follows | This is a single-bit flag which, when set to '1' indicates that another BCtSDU follows this BCtSDU, else either the CRC, ALComPDU or a BCnPDU follows this BCtSDU. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.3.2.2 Extended-length | This is a single-bit flag which, when set to '1' indicates that an extended type and length field are utilized within the BCtSDU header. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.3.2.3 S-length / length | The s-length and length fields are a 3-bit and 8-bit value respectively, both of which are used to indicate the length of the SDU. The value of s-length / length represents the number of octets in the sdu-payload. The encoding of these parameters, which are defined as INTEGER(1..8) and INTEGER (1..256) respectively, fo... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.3.2.4 BCtSigType and ShortBCtSigType | The s-type / sdu-type parameter defines the Bearer Control Signalling Data Unit type. Values in the range 0x00..0x07 shall be encoded as a ShortBCtSigType, in a 3-bit field (i.e. the BCtSDU type-and-length field is of CHOICE short), unless the length of the SDU exceeds 8 bytes, in which case they shall be encoded as a ... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.3.2.5 SDUPayload | This field contains the body of the bearer control signalling PDU and is type dependent. SDUPayload ::= CHOICE { conn-pdu BCnPDU, status Status, q-rate QRate, q-len QLen, bulletin-board BulletinBoard, return-schedule ReturnSchedule, status-ack-list StatusAckList, specific-avp-list SpecificAVPList, avp-list AVPList, spo... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4 Bearer Control SDU Payloads | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.0 General | NOTE: Throughout clauses 5.4.1 to 5.4.15, the ASN.1 defines components of SDUPayload, while the figures illustrate the entire BCtSDU structure (i.e. including the fields bct-sdu-follows and type-and-length). |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.1 ConnPDU | The ConnPDU SDU is transferred in a connection specific BCtPDU and is only used when multiple Bearer Connection PDUs are to be transferred within a single Bearer Control PDU. The SDU Payload contains a BCnPDU and the format is shown in Figures 5.40 and 5.41. ETSI ETSI TS 102 744-3-1 V1.1.1 (2015-10) 40 (MSB) Bit No (LS... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.2 Status | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.2.0 General | The Status SDU is transmitted in a BCtPDU to transfer information about the queue status for a specific connection at a UE to the RNC and is used for the purpose of requesting resources. A detailed description on the use of this SDU is provided in ETSI TS 102 744-3-2 [10]. The SDU-Payload has the following structure: S... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.2.1 SequenceNumber | This field contains a sequence-number which is incremented for each Status Message sent. SequenceNumber ::= INTEGER (0..15) ETSI ETSI TS 102 744-3-1 V1.1.1 (2015-10) 42 |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.2.2 Queue-length | This parameter provides the queue-length in units of bytes. It is divided into two parts, a four bit exponent and a ten bit mantissa. The queue length can then be calculated as follows: queue-length = mantissa × 2exponent When sending the parameter, queue-length shall be expressed with the maximum possible precision. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.2.3 Time-head | Time-head refers to the delivery time of the first PDU in the calling process queue. The units of time-head are in 80 ms units, offset by the time the Status SDU was created minus 8 s. The expected delivery times of the head of the queue is therefore calculated from the value time-head according to the following formul... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.2.4 Delivery-rate | The delivery-rate parameter gives the required delivery rate as calculated by the UE such that the entire queue at the UE can be delivered meeting the specified QoS. The parameter is defined in units of 128 bytes/s. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.2.5 Status-avp-list | The status-avp-list may carry information from the UE to the RNC, such as Received Signal Quality. This parameter is of type AVPList which is defined as follows: AVPList ::= SEQUENCE OF BCtAVP The data type BCtAVP is defined in clause 5.7. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.3 BulletinBoard | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.3.0 General | The BulletinBoard SDU is transferred in a Broadcast BCtPDU used to transfer information to all UEs about the current bearer. The BulletinBoard SDU is transmitted at regular intervals, but not necessarily in every frame. If a BulletinBoard SDU is scheduled for transmission in a particular frame, then: • the BulletinBoar... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.3.1 Rnc-id | This 8-bit field is used to identify a RNC within a region. The purpose of the field is to assist with the process of recovery in the event that a channel is allocated to another RNC. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.3.2 Net-ver | This 4-bit field is incremented whenever the RNC performs a software reset, or whenever the information held about UEs by the particular bearer may be obsolete. The purpose of the field is to assist with the process of recovery in the event of a problem within the RNC. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.3.3 FrameNumber | This field is a 12-bit field of type INTEGER (0x000 .. 0xFFF). The value is used to identify the Frame Number of the Bearer Control at the RNC. The purpose of the field is to synchronize sleep mode and ciphering operation between the RNC and the UE. FrameNumber ::= INTEGER (0..4095) |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.3.4 Spot-beam-present | This BOOLEAN field indicates whether the optional spot-beam-id field is present. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.3.5 FwdBearer | This field is a 3-bit field which is used to identify this Forward Bearer Number within the Bearer Control. The purpose of the field is to assist with the process of locating the UE within the Bearer Control. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.3.6 BCtID | This field is a 4-bit field which is used to identify this Bearer Control within the Spot Beam (identified by spot-beam-id, if present) at a particular RNC (identified by the rnc-id). The purpose of the field is to identify error conditions within the UE. BCtID ::= INTEGER (0..15) |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.3.7 SpotBeamID | The spot-beam-id field specifies the spot-beam in which the bearer is being transmitted. SpotBeamID ::= INTEGER (0..255) ETSI ETSI TS 102 744-3-1 V1.1.1 (2015-10) 45 |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.3.8 BB-avp-list | The bb-avp-list field is used to carry various configuration parameters which are intended for all UEs on the forward bearer. The field is of data type AVPList which is defined as follows: AVPList ::= SEQUENCE OF BCtAVP The data type BCtAVP is defined in clause 5.7. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4 ReturnSchedule | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.0 General | The ReturnSchedule SDU is sent in a Broadcast BCtPDU to transfer information to UEs about the availability of slots in the return direction, and may also be transmitted to a specific UE to allocate dedicated return channel resources. The SDU Payload has the following structure: ReturnSchedule::= SEQUENCE { return-chann... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.1 RetChannelNumber | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.1.0 General | This field is used to specify the Channel Number to which the Return Schedule applies. RetChannelNumber ::= SEQUENCE { offset Offset, channel-index ChannelIndex } If RetChannelNumber is 0 or 0xFFFF, this indicates that the channel is unavailable. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.1.1 Offset | The offset field is a one bit field defined as follows: Offset ::= INTEGER (0..1) ETSI ETSI TS 102 744-3-1 V1.1.1 (2015-10) 46 It is interpreted as shown in Table 5.4. Table 5.4: Offset Field Values Offset Value: Interpretation 0: 0 Hz offset 1: +1,25 kHz offset |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.1.2 ChannelIndex | The remaining 15 bits represent the channel-index field, which is expressed as a hexadecimal number, such that the L-Band transmit frequency can be calculated as described in ETSI TS 102 744-2-1 [8]. The return channel centre frequency is calculated from channel-index and offset as follows: return frequency [MHz] = cha... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.2 Bearer-type-and-spotid-included | The bearer-type-and-spot-id-included field is of type BOOLEAN, and if set to '1' indicates that the bearer-type-and-spot-id sequence is included. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.3 Res-plan-included | The res-plan-included field is of type BOOLEAN, and if set to '1' indicates that the res-plan field is present. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.4 Number-of-slot-plans | This field is used to specify the number of slot-plans included in the ReturnSchedule SDU. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.5 ReturnBearerTypeShort | The value in r-bearer-type field specifies the type of return bearer that shall be used by the UE in conjunction with the particular Return Schedule and the data type ReturnBearerTypeShort is defined as follows: ReturnBearerTypeShort::= INTEGER { r20t05q-or-r80t05q (0), r20t1q (1), r5t2q-or-r20t2q (2), r5t45q-or-r20t45... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.6 SpotBeamID | The spot-beam-id field is used if the bearer control at the RNC supports return channels associated with multiple spot beams; e.g. when the forward bearer (on which this schedule is sent) is transmitted in the regional beam but narrow beams are available to receive return channel transmissions. In this case, the spot-b... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.7 SlotPlan | Values of slot-plans are defined as shown in Figure 5.47. Figure 5.47: SlotPlan Structure The values of slot-plan are defined in relation to a slot number, where four (short) slots may be combined to provide a long (reserved) slot, as is the case in slot structures 1 to 6. The actual slot duration (in ms) depends on th... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.8 ResourcePlan | The res-plan field, if present, indicates whether or not reserved slots for the slot plan(s) have Translated Bearer Connection IDs listed below. The mapping of Translated Bearer Connection IDs to reserved slots is explained in ETSI TS 102 744-3-2 [10]. If res-plan is not present, then Translated Bearer Connection IDs a... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.4.9 Return Schedule Examples | This clause provides examples of different Return Schedules and shall not be considered as exhaustive. The example shown in Figure 5.48 illustrates the case where only contention slots are available on this channel for mobiles tuned to this bearer. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 x 0 0 1 0 0 1 0 Octet 1 return- Octe... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.5 StatusAckList | The StatusAckList SDU is transferred in a Broadcast BCtPDU and is used to acknowledge the receipt of status messages from UEs. The SDU Payload has the following structure: StatusAckList::= SEQUENCE (1..64) OF StatusAck ETSI ETSI TS 102 744-3-1 V1.1.1 (2015-10) 52 with StatusAck defined as follows: StatusAck ::= SEQUENC... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.6 QRate | The QRate SDU is transmitted in a BCtPDU to transfer information about the characteristics of the traffic being presented at the input to a specific connection to the RNC. The SDU-Payload currently only carries a QueueRate parameter and is formatted as below with structure as shown in Figure 5.57. QRate ::= SEQUENCE { ... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.7 QLen | The QLen SDU is transmitted in a BCtPDU to transfer information about the state of the queue for a specific connection to the RNC and is used for the purpose of requesting resources for Background class connections and Interactive class connections with low information rate. A detailed description on the use of this SD... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.8 SpecificAVPList | The SpecificAVPList SDU may be used within a Broadcast BCtPDU to direct information at a specific UE, a connection within a UE, or hardware within a UE (depending upon the AVP context), for instance when a timing, frequency or power correction is required. The SDU Payload has the following structure, with format as sho... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.9 AVPList | The AVPList SDU may be used in any of the following ways: • in a Broadcast BCtPDU to change global parameters within all UEs tuned to the forward bearer; • in a Common Signalling BCtPDU (RegisterAck) to carry timing and return link reference level information to a UE; and • in a Connection Specific BCtPDU (i.e. which i... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10 SpotBeamMap | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.0 General | This SDU is used to describe spot beam contour information to the UEs and has the following structure, with format as shown in Figure 5.63: SpotBeamMap::= SEQUENCE { spotbeam-map-version INTEGER (0..255), total-number-of-spots INTEGER (0..255), spotbeam-map-number INTEGER (0..255), spotbeam-info-list SEQUENCE OF SpotBe... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.1 Spotbeam-map-version | The spotbeam-map-version field is used to indicate to the UEs that the spotbeam information has been updated and that it should obtain a complete list of spotbeam map information prior to taking any further action. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.2 Total-number-of-spots and spotbeam-map-number | The parameters total-number-of-spots and spotbeam-map-number are provided in order for the UE to track the reception of spotbeam maps if a complete set of spotbeam maps is transmitted in a number of SpotBeamMap SDUs. This would be the case if the capacity of the physical layer is insufficient to transmit all SpotBeamIn... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.3 SpotBeamInfo | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.3.0 General | The spot-beam-info structure is defined as follows, with format as shown in Figures 5.64 and 5.65: SpotBeamInfo::= SEQUENCE { spotbeam-id SpotBeamID, reserved BIT STRING (SIZE (4)), sb-prf INTEGER (0..3), sb-data CHOICE { sb-vertices SEQUENCE { sb-type SpotBeamMapType, -- sb-type = 0 number-of-vertices INTEGER (0..63),... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.3.1 Sb-prf | The value in the sb-prf field indicates to the UE the spot beam preference level, i.e. which spot-beam the UE should move into (or the spot beam to which the mobile should make a request to move into). If there is more than one suitable spot beam to chose from then the UE shall choose the one with the highest sb-prf va... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.3.2 SpotBeamMapType | The value in the two-bit field sb-type specifies the format of the remaining octets in the spotbeam-info structure: SpotBeamMapType ::= INTEGER { spotbeam-vertex-list (0), regular-spotbeam (1) } (0..3) Current implementations shall ignore the spot-beam information if sb-type is set to a reserved value. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.3.3 Number-of-vertices | The number-of-vertices field specifies the length of the spot-beam-vertex-list expressed as the number of vertices (each vertex occupies two octets) as defined in clause 5.4.11.3.4. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.3.4 SpotbeamVertex | The data type SpotbeamVertex is defined as: SpotbeamVertex ::= INTEGER (0..65535) and the value of a SpotbeamVertex is calculated as follows: SpotBeamVertexValue = [360(φ+90)]+θ+180 where: φ := Latitude in degrees, rounded to the nearest integer with (90°S ≡ -90) ≤ φ ≤ (90 ≡ 90°N) and: θ := Longitude in degrees, rounde... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.3.5 SpotBeamAzimuth | The data type SpotbeamAzimuth is defined as: SpotbeamAzimuth ::= INTEGER (0..255) This element specifies the centre of a spot beam in terms of the azimuth angle from the satellite to the spot beam centre. The azimuth angle, Azc, is expressed in degrees and encoded as follows: Az = (SpotBeamAzimuth-128)/10 |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.3.6 SpotBeamElevation | The data type SpotbeamElevation is defined as: SpotbeamElevation ::= INTEGER (0..255) This element specifies the centre of a spot beam in terms of the elevation angle from the satellite to the spot beam centre. The elevation angle, Elc, is expressed in degrees and encoded as follows: El = (SpotbeamElevation -128)/10 |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.10.3.7 SpotBeamRadius | The data type SpotbeamRadius is defined as: SpotbeamRadius ::= INTEGER (0..255) This field describes the boundary of a spot beam as a constant "distance" in terms of satellite-centred azimuth and elevation angles from the satellite, i.e. the radius: where Azc and Elc are the azimuth and elevation angles which point to ... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.11 BearerTables | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.11.0 General | The BearerTable SDU may be used by the RNC to signal any changes in the properties of the physical layer return bearer types and subtypes in a connection specific BCtPDU. The implementation of this SDU is mandatory only for UE Classes 1 to 3 of RI-Versions below 0x83 (see ETSI TS 102 744-3-5 [13], clause 6.1.2.2). For ... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.11.1 Bearer-table-follows | This BOOLEAN flag indicates that the current Bearer Table will be continued in another Bearer Tables SDU. Bearer Tables may need to be split over several SDUs if the number of octets available in a forward bearer FEC block is insufficient to accommodate a full Bearer Table. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.4.11.2 Lowest-coding-rate-index-included | This BOOLEAN flag indicates that the field lowest-coding-rate-index is included in the structure. ETSI ETSI TS 102 744-3-1 V1.1.1 (2015-10) 62 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.