hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.10.1 StartValue | This parameter returns the start-value for the ciphering and integrity protection algorithms from the UE to the RNC and follows the definition of the same IE in [3], clauses 10.3.3.38 and 11.3: StartValue ::= BIT STRING (SIZE(20)) |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.10.2 UERadioAccessCapability | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.10.2.0 General | The parameter ue-radio-access-capability carries information about the UE's Packet Data Convergence Protocol (PDCP), security and other optional capabilities. The type UERadioAccessCapability is defined as follows: UERadioAccessCapability ::= CHOICE { capability-extension-not-present SEQUENCE { pdcp-capability ETSI ETS... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.10.2.1 PDCPCapability and LongPDCPCapability | The parameter pdcp-capability carries information about the PDCP algorithms which are implemented in the UE. The parameter is of type PDCPCapability and is defined as follows, with structure as shown in Figures 6.17 and 6.18. PDCPCapability ::= -- with Release 4 Extension SEQUENCE { lossless-SRNS-relocation-support BOO... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.10.2.2 SecurityCapability | The parameter security-capability carries information about the integrity protection and ciphering algorithms which are implemented in the UE. The parameter is of type SecurityCapability and is defined as follows, with structure as shown in Figure 6.19. SecurityCapability ::= SEQUENCE { ciphering-algorithm-cap BIT STRI... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.10.2.3 Capability Extension | 6.2.10.2.3.0 General The parameter capability-extension carries information about optional UE capabilities and shall be included in the RegisterComplete message as specified in each of the following clauses. The parameter is of typeCapabilityExtensionAVPList. CapabilityExtension ::= CapabilityExtensionAVPList 6.2.10.2.... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.11 EstablishReject | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.11.0 General | This message is used by the UE to indicate a failure in the Establishment of a Bearer Connection. The PDU is defined as below, with structure as shown in Figure 6.26. EstablishReject ::= SEQUENCE { bearer-conn-id BcnID, ctrl-flags CtrlFlags, trans-id TransactionID, cause CHOICE { failure-cause FailureCause, prot-err-ca... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.11.1 FailureCause and ProtocolErrorCause | The cause parameter may either contain a failure cause or a protocol error cause value. The failure-cause parameter in the EstablishReject message is of type FailureCause and defined as follows: FailureCause ::= INTEGER { configuration-not-supported(0), configuration-incomplete(1), invalid-configuration(2), physical-ch... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.12 ReleaseReject | This message is used by the UE to indicate a failure to release of a Bearer Connection. The PDU is defined as below, with structure as shown in Figure 6.27. Release Reject ::= SEQUENCE { bearer-conn-id BcnID, ctrl-flags CtrlFlags, trans-id TransactionID, cause CHOICE { failure-cause FailureCause, prot-err-cause Protoco... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.13 ModifyReject | This message is used by the UE to indicate a failure to modify a Bearer Connection. The PDU is defined as below, with structure as shown in Figure 6.28. ModifyReject ::= SEQUENCE { bearer-conn-id BcnID, ctrl-flags CtrlFlags, trans-id TransactionID, cause CHOICE { failure-cause FailureCause, prot-err-cause ProtocolError... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.14 PagingType2 | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.14.0 General | The PagingType2 Signalling PDU is used by the RNC when a UE-Specific Signalling Connection exists between the UE and the RNC. The PDU is defined as below, with structure as shown in Figure 6.29. ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10) 39 PagingType2 ::= SEQUENCE { cn-domain-identity CNDomainIdentity, paging-cause Pag... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.14.1 PagingRecordTypeID | This IE is defined in [3], clauses 10.3.1.10 and 11.3 as follows: PagingRecordTypeID ::= INTEGER { imsi (0), tmsi-or-p-tmsi (1) } (0..255) |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.15 InitialDirectTransfer | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.15.0 General | This Signalling PDU is used by the UE to transfer the initial NAS message from the UE via the RNC to the Core Network prior to the establishment of an Iu signalling connection. The NAS message is passed transparently through the RNC. The PDU is defined as below, with structure as shown in Figure 6.30. InitialDirectTran... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.15.1 NASMessage | This parameter carries the message between Non-Access-Stratum peers (e.g. Mobility Management messages) is not interpreted by the Adaptation Layer. Its definition in [3], clauses 10.3.3.14 and 11.3 is modified for the satellite network as follows: NASMessage ::= OCTET STRING (SIZE (1..2040)) -- Satellite network RI can... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.16 UplinkDirectTransfer | This Signalling PDU is used by the UE to transfer NAS messages via the RNC to the Core Network if an Iu signalling connection already exists. The NAS message is passed transparently through the RNC. The PDU is defined as below, with structure as shown in Figure 6.31. UplinkDirectTransfer::= SEQUENCE { reserved BIT STRI... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.17 DownlinkDirectTransfer | This Signalling PDU is used by the RNC to transfer NAS messages from the Core Network to the UE if an Iu signalling connection already exists. The NAS message is passed transparently through the RNC. The PDU is defined as below, with structure as shown in Figure 6.32. DownlinkDirectTransfer ::= SEQUENCE { reserved BIT ... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.18 SecurityModeCommand | This Signalling PDU is used by the RNC to start or reconfigure integrity protection and/or ciphering in the UE. The PDU is defined as below, with structure as shown in Figure 6.33. ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10) 42 SecurityModeCommand ::= SEQUENCE { reserved BIT STRING (SIZE (6)), cn-domain-identity CNDomain... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.19 SecurityModeComplete | This message is sent from the UE to the RNC to confirm the start or reconfiguration of integrity protection and/or ciphering in the UE. The PDU is defined as below, with structure as shown in Figure 6.34. SecurityModeComplete::= SEQUENCE { ul-integrity-protection-activation-info-avp ULIntegrityProtectionActivationInfoA... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.20 SecurityModeFailure | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.20.0 General | This message is sent from the UE to the RNC to indicate a failure to act on a received SecurityModeControl message. The PDU is defined as below, with structure as shown in Figure 6.35. SecurityModeFailure::= SEQUENCE { cause CHOICE { security-failure-cause SecurityFailureCause, prot-err-cause ProtocolErrorCause }, ul-i... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.20.1 SecurityFailureCause | The parameter security-failure-cause is of type SecurityFailureCause and is defined as follows: SecurityFailureCause ::= INTEGER { unsupported-or-mismatched-security-configuration (0), integrity-protection-algorithm-failure (1), ciphering-algorithm-failure (2) } (0..255) -- valid range 0-127 -- 128-255 reserved for Pro... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.21 SignallingConnectionReleaseReq | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.21.0 General | This message is sent from the UE to the RNC to request the release of an existing Iu signalling connection from the RNC towards the specified CN domain. The PDU is defined as below, with structure as shown in Figure 6.36. SignallingConnectionReleaseReq ::= SEQUENCE { reserved BIT STRING (SIZE (6)), cn-domain-identity C... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.21.1 ConnectionReleaseCause | The parameter conn-rel-cause is of type ConnectionReleaseCause and is defined as follows: ConnectionReleaseCause ::= INTEGER { mm-sublayer-initiated (0) } (0..255) -- valid range 0-127 -- 128-255 reserved for ProtocolErrorCause |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.22 SignallingConnectionRelease | This message is sent by the RNC to inform the UE that the ongoing Iu signalling connection from the RNC to the specified CN domain has been released. The PDU is defined as below, with structure as shown in Figure 6.37. SignallingConnectionRelease::= SEQUENCE { reserved BIT STRING (SIZE (6)), cn-domain-identity CNDomain... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.23 UEPositionRequest | This message is used by the RNC during the registration procedure (only) to command the UE to provide its GPS position. To maintain user confidentiality, the RNC may either provide a public key to be used by the UE to encrypt its response, or an index to a pre-defined public key which is stored in the UE. The PDU is de... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.24 UEPositionResponse | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.24.0 General | This message is used by the UE to provide the GPS position to the RNC, either in response to the UEPositionRequest message or unsolicited (see clause 6.2.25). The GPS position may be encrypted using the method described in ETSI TS 102 744-3-6 [8]. The PDU is defined as below, with structure as shown in Figure 6.40. UEP... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.24.1 Ue-position | The format of the ue-position string (prior to encryption) is derived from the National Marine Electronics Association (NMEA-0183) sentence type GGA [i.1]. It is either 35 or 38 characters long with each character encoded as 8-bit ASCII. All position reporting in terms of latitude and longitude and as well as any conve... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.25 RegModeUpdate | This message is used by the RNC to change the registration mode and to control the GPS position display capabilities (if implemented) of a UE at any time after the registration process has been completed. The PDU is defined as below, with structure as shown in Figure 6.41. RegModeUpdate ::= SEQUENCE { reg-ref Registrat... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.26 SystemInformation | This message is used by the RNC to transfer System Information to the UE while in the connected state. The PDU is defined as below, with structure as shown in Figure 6.42. SystemInformation ::= bct-epdu BCtEPDU (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 Octet 1 bct-epdu Octet n Figure 6.42: SystemInformation Signalling PDU The... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.27 Deregister | The Deregister message is used by the RNC to deregister an individual Ues. The Deregister Common Signalling PDU is defined as below, with structure as shown in Figure 6.43. ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10) 49 Deregister ::= SEQUENCE { reg-ref RegistrationReference, cause CHOICE { deregistration-cause Deregistr... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.28 DeregisterAck | The DeregisterAck message is used by the UE to complete the deregistration process. The DeregisterAck Signalling PDU is defined as below, with structure as shown in Figure 6.44. DeregisterAck ::= SEQUENCE { reg-ref RegistrationReference } (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 reg-ref Octet 1 Figure 6.44: DeregisterAck Sig... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.2.29 HandoverRequest | The HandoverRequest message is used by a moving UE to signal to the RNC that it has changed position and that a Handover into another spot beam may be required. The HandoverRequest Signalling PDU is defined as below, with structure as shown in Figure 6.45. HandoverRequest ::= SEQUENCE { handover-info SEQUENCE { reserve... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3 Adaptation Layer AVPs | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.0 General | Adaptation Layer AVPs (AL-AVPs) are used to carry Information Elements (Ies) which are required to provide additional signalling for UMTS specific features (e.g. ciphering, PDCP parameters etc.) in messages related to the establishment, modification and release of user plane connections. In this case, AL-AVPs are conta... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.1 AdaptationLayerAVP Structure | The structure of the data type AdaptationLayerAVP is as follows: AdaptationLayerAVP ::= CHOICE { al-short-avp ALShortAVP, al-standard-avp ALStandardAVP } The ALShortAVP structure is used for a value size of up to eight octets, while the ALStandardAVP structure can be used for a value size of up to 256 octets. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.2 ALShortAVP | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.2.0 General | The ALShortAVP is defined as below, with structure as shown in Figure 6.46. ALShortAVP ::= SEQUENCE { length-control BOOLEAN, --{encode as FALSE} al-short-avp-type ALShortAVPType, al-short-avp-length INTEGER(1..8), -- encode as minimum bits from lowest bound param-value CHOICE { -- as appropriate to value of al-short-a... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.2.1 ALShortAVPType | This INTEGER parameter specifies the parameter value of the short AVP: ALShortAVPType ::= INTEGER { count-c-activation-time(1), pdcp-sn-info(2), rab-info(3), uplink-ciphering-activation-time-info(4), cs-call-type(5), uplink-integrity-protection-activation-info(7), ciphering-mode-info(8), reserved (9), -- placeholder fo... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.3 ALStandardAVP | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.3.0 General | The ALStandardAVP is defined as below, with structure as shown in Figure 6.47. ALStandardAVP ::= SEQUENCE { length-control BOOLEAN, --{encode as TRUE} al-standard-avp-type ALStandardAVPType, al-standard-avp-length INTEGER(1..256), -- encode as minimum bits from lowest bound param-value CHOICE { -- al-standard-avp-type ... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.3.1 ALStandardAVPType | This INTEGER parameter specifies the parameter value of the standard AVP: ALStandardAVPType ::= INTEGER { ciphering-mode-info(8), pdcp-info(12) group-cipher-info(13) } (0..127) The Standard AVP Types are defined in Table 6.7. Table 6.7: Standard AVP Types StandardAVPType Parameter-Value StandardAVPLen 0x08 CipheringMod... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.4 CountCActivationTimeParam (ShortAVPType 0x01) | This AVP parameter specifies the COUNT-C activation time for a transparent mode (TM) connection. The parameter is defined as below, with structure as shown in Figure 6.48. CountCActivationTimeParam ::= SEQUENCE { reserved BIT STRING (SIZE (4)), frame-number FrameNumber } The data type FrameNumber is defined as follows:... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.5 PDCPSNInfoParam (ShortAVPType 0x02) | This AVP parameter encapsulates the PDCP Sequence Number (PDCP SN) Info IE specified in [3], clause 10.3.4.3. The parameter is defined as below, with structure as shown in Figure 6.49. PDCPSNInfoParam ::= INTEGER (0..65535) (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 PDCPSNInfo Octet 1 Param Octet 2 Figure 6.49: PDCPInfo Parame... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.6 RABInfoParam (ShortAVPType 0x03) | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.6.0 General | This AVP parameter encapsulates a number of Ies required to signal Radio Access Bearer (RAB) related parameters to the UE. The parameter is defined as below, with structure as shown in Figures 6.50 and 6.51. RABInfoParam ::= SEQUENCE { rab-Identity RABIdentity, nas-sync-ind-included BOOLEAN, ext-rab-info-present BOOLEA... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.6.1 TrafficHandlingPriority | The parameter thp is of type TrafficHandlingPriority which is defined as follows: TrafficHandlingPriority ::= INTEGER { traffic-handling-priority-15-or-background (0), traffic-handling-priority-1 (1), ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10) 56 traffic-handling-priority-2 (2), traffic-handling-priority-3 (3) } (0..3) ... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.6.2 RabAccessPriority | The parameter rab-access-priority is of type RabAccessPriority which is defined as follows: RabAccessPriority ::= INTEGER (0..15) The parameter is specified by the RNC for this RAB and is used by the UE to determine the radio resources that are available for use and for assembly of transmit bursts. The value of 0 repre... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.7 ULCipheringActivationTimeInfoParam (ShortAVPType 0x04) | The Activation Time Info value in this AVP is expressed as the BCn Send Sequence Number and specifies when the change in the uplink ciphering occurs. The parameter is defined as below, with structure as shown in Figure 6.53. ULCipheringActivationTimeInfoParam ::= SEQUENCE { reserved BIT STRING (SIZE(6)), bcn-send-seq-n... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.8 ULIntegrityProtectionActivationInfoParam (ShortAVPType 0x07) | This parameter is expressed as the current Adaptation Layer (AL) message sequence number when a new integrity protection configuration is activated for the signalling connection. The parameter is defined as below, with structure as shown in Figure 6.54. ULIntegrityProtectionActivationInfoParam ::= SEQUENCE { reserved B... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.9 CipheringModeInfoParam (Short/StandardAVPType 0x08) | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.9.0 General | This parameter encapsulates the Ciphering Mode Info IE specified in [3], clause 10.3.3.5. The parameter is defined as below, with structure as shown in Figures 6.55 and 6.56. CipheringModeInfoParam ::= SEQUENCE { activation-time-for-tm-included BOOLEAN, reserved BIT STRING (SIZE (3)), ciphering-mode-command CipheringMo... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.9.1 CipheringModeCommand | The parameter ciphering-mode-command specifies the ciphering algorithm to be used and its data type is defined as follows: CipheringModeCommand ::= SEQUENCE { start-restart CipheringAlgorithm } with CipheringAlgorithm ::= INTEGER { uea0(0), uea1(1) } (0..15) The parameter dl-ciph-activation-time-info-list is of type RB... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.9.2 RBActivationTimeInfoList | The data type RBActivationTimeInfoList contains a list of Translated Bearer Connection IDs and Bearer Connection Sequence Numbers, specifying for each Acknowledged Mode (AM) or Unacknowledged Mode (UM) connection the sequence number from when the specified ciphering shall be applied to the connection. RBActivationTimeI... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.10 IntegrityProtectionModeInfoParam (ShortAVPType 0x0A) | This parameter encapsulates the Integrity Protection Mode Info IE specified in [3], clause 10.3.3.19. IntegrityProtectionModeInfoParam ::= SEQUENCE { integrity-protection-mode-command IntegrityProtectionModeCommand, optional-algorithm SEQUENCE { reserved BIT STRING (SIZE (4)), integrity-protection-algorithm IntegrityPr... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.11 PDCPInfoParam (Short/StandardAVPType0x0C) | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.11.0 General | This parameter encapsulates the PDCP Info IE specified in [3], clause 10.3.4.2. The parameter is defined as follows, with structure as shown in Figure 6.61. PDCPInfoParam ::= SEQUENCE { lossless-srns-reloc-supported BOOLEAN, max-pdcp-sn-window-size MaxPDCPSNWindowSize, pdcp-pdu-header PDCPPDUHeader, header-compression-... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.11.1 RFC2507Info | The parameter rfc2507-info carries the header compression info for the RFC 2507 [i.2] compression algorithm. The data type RFC2507Info is defined as follows: RFC2507Info ::= SEQUENCE { algorith-type AlgorithmType, -- encode as 0: rfc-2507 expect-reordering ExpectReordering, f-max-period-included ETSI ETSI TS 102 744-3-... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.11.2 RFC3095Info | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.11.2.0 General | The parameter rfc3095-info carries the header compression info for the RFC 3095 [i.3] compression algorithm. The data type RFC3095Info is defined as follows, with structure as shown in Figure 6.63. RFC3095Info ::= SEQUENCE { algorithm-type AlgorithmType, -- encode as 1: rfc-3095 uplink-data-present BOOLEAN, downlink-da... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.11.2.1 UplinkROHCData | The parameter uplink-rohc-data carries the necessary information elements for configuring the RFC 3095 Robust Header Compression (ROHC) algorithm [i.3] for compression of uplink traffic at the UE. The data type UplinkROHCData is defined as follows, with structure as shown in Figure 6.64. UplinkROHCData ::= SEQUENCE { u... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.11.2.2 DownlinkROHCData | The parameter downlink-rohc-data carries the necessary information elements for configuring the RFC 3095 ROHC algorithm [i.3] for decompression of downlink traffic at the UE. The data type DownlinkROHCData is defined as follows, with structure as shown in Figure 6.65. DownlinkROHCData ::= SEQUENCE { downlink-cid-inclus... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.12 CSCallTypeParam (ParamType 0x05) | This parameter has a length of one octet and is used to signal the Circuit Switched Call Type for the Circuit Switched User Plane Handler (CSH) from the UE to the RNC. The parameter is defined as follows, with structure as shown in Figure 6.66. CSCallTypeParam ::= SEQUENCE reserved BIT STRING (SIZE (4)), cs-call-type I... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.3.13 GroupCipherInfoParam (StandardAVPType 0x0D) | This parameter encapsulates the Group Ciphering Key and Count-C value for generation of the group bearer connection specific decipher keystream block information in the UE. GroupCipherInfoParam ::= BIT STRING (SIZE (128)) The parameter value is structured as shown in Figure 6.67. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 Octe... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4 Connection Layer AVP | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.0 General | Connection Sub-Layer AVPs are used to transfer parameters relating to the configuration of the Connection Sub-Layer peers. ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10) 67 |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.1 BCn-AVP Structure | |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.1.0 General | The structure of a Connection Sub-Layer AVP is as follows: BCnAVP ::= SEQUENCE { bcn-avp-type BCnAVPType, param-value CHOICE { -- as appropriate to value of -- bcn-avp-type response-time-param ResponseTimeParam, max-idle-time-param MaxIdleTimeParam, max-connection-time-param MaxConnectionTimeParam, tx-window-size-param... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.1.1 PrmLen | This three bit field specifies the length of the parameter value in the AVP. This field forms the least significant three bits of the param-type field, and contains the one less than the length of the param-value field. Note that this implies that a zero-length parameter length is not supported. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.1.2 PrmLenType | This five bit field indicates the type of the parameter within the context of the prm-len field value. This field forms the most significant five bits of the param-type field. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.2 ResponseTimeParam (ParamType 0x08) | This parameter has a length of one octet and is used to define the response timer value for the connection which is being established or modified. This time is used by the ARQ timer to generate a retransmission of a Receive Ready message in the event that no response was received from the peer. ResponseTimeParam ::= IN... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.3 MaxIdleTimeParam (ParamType 0x09) | This parameter has a length of two octets (prm-len = 1) and is used to define the period of inactivity for the connection which is being established or modified, before the connection shall be automatically released. A period of inactivity is defined as the period over which no data is successfully transferred (and ack... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.4 MaxConnectionTimeParam (ParamType 0x11) | This parameter has a length of two octets (prm-len = 1) and is used to define the maximum period that the connection which is being established or modified, shall be allowed to operate before the connection is automatically released. MaxConnectionTimeParam ::= INTEGER (0..65535) The unit of max-connection-time is 10 se... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.5 TxWindowSizeParam (ParamType 0x21) | This parameter has a length of two octets (prm-len = 1) and is used define the transmit window size to utilize at the UE for the connection that is being established. TxWindowSizeParam ::= INTEGER (0..511); -- encoded within a 16 bit field The units are segments. The default value for tx-window-size is the maximum valu... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.6 TxBufferSizeParam (ParamType 0x29) | This parameter has a length of two octets and is used to define the transmit buffer size to utilize at the UE for the connection that is being established, before flow control is asserted on external interfaces. TxBufferSize ::= INTEGER (0..65535); The value is specified in a unit size of 256 bytes. The default value f... |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.7 AdaptationLayerAVPListLengthParam (ParamType 0xF8) | This parameter has a length of one octet and is used to signal the number of Adaptation Layer AVPs which follow this AVP. AdaptationLayerAVPListLengthParam ::= INTEGER (0..255); The contents of the Adaptation Layer AVP List are specified in clause 6.3. |
27d1e647d88050d00e1f2ff68afb59e5 | 102 744-3-5 | 6.4.8 CSHConfigurationParam (ParamType 0x30) | This parameter has a length of one octet and is used to signal the configuration parameters for the Circuit Switched User Plane Handler (CSH). The parameter is defined as follows, with structure as shown in Figure 6.69. ETSI ETSI TS 102 744-3-5 V1.1.1 (2015-10) 70 CSHConfigurationParam ::= SEQUENCE { fwd-dtx BOOLEAN, f... |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 1 Scope | The present document defines the Bearer Connection Layer operation of the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network. The Bearer Connection Layer (BCn) peer-to-peer interface is described in ETSI TS 102 744-3-3 [9]. |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 2 References | |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 3 Symbols and abbreviations | |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 3.1 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 744-1-4 [6], clause 3 apply. |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 744-1-4 [6], clause 3 apply. |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4 General Architecture | |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4.0 Overview | The function of the satellite radio interface Bearer Connection Layer (BCn) is to provide a number of different data transport services to upper layers. Figure 4.1 illustrates the position of the Bearer Connection Layer within the Family SL air interface protocol stack. An overview of the radio interface layering and r... |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4.1 Bearer Connection Layer Entities | |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4.1.0 General | The Bearer Connection Layer consists of a Bearer Connection Manager and instances of one of four possible data handlers (COM_DH, AM_DH, NUM_DH and TM_DH) with their associated Service Access Points (SAPs). The Control Plane of each UE consists of an AM_DH for the UE Specific Signalling connection, a COM_DH for managing... |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4.1.1 Bearer Connection Manager (BCnM) | The Bearer Connection Manager (BCnM) provides bearer connection management services to the Adaptation Layer via the CBCn-SAP. This includes the creation and removal of a particular connection, and the setting of its QoS parameters. Bearer Connection Manager STATUS-SAP BCt-DATA- SAP AM-SAP CBCn- SAP Adaptation Layer - C... |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4.1.2 Acknowledged Mode Data Handler (AM_DH) | The Acknowledged Mode Data Handler shall be created when a reliable delivery message transport is required e.g. for packet data and signalling connections. In the control plane, it is used to transport UE Specific Signalling (UESS) messages from the Adaptation Layer (AL). Note that the SIG-SAP as defined in the Adaptat... |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4.1.3 Transparent Mode Data Handler (TM_DH) | The transparent mode data handler (TM_DH) is created when a transparent data link is requested. This is primarily used to support circuit switched (CS) traffic. In transparent mode, no connection layer overhead is added to the data arriving from the layer above. Data coming from the higher layer via the TM-SAP is buffe... |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4.1.4 Numbered Frame Data Handler (NUM_DH) | For Un-Acknowledged Mode data coming from the layer above via the UM-SAP, a Numbered Frame Data Handler (NUM_DH) shall be used. The NUM_DH provides in-sequence delivery, segmentation and re-assembly, and ciphering of data. However, packet delivery is not guaranteed. The ciphered data PDUs are sent to the Bearer Control... |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4.1.5 Common Signalling Data Handler (COM_DH) | The Common Signalling Data Handler exists only in the control plane of the Bearer Connection Layer. This handler provides buffering for Common Signalling messages from the Adaptation Layer. It also supports the reporting of STATUS information via the STATUS-SAP to the control layer. No Ciphering is required for Common ... |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4.2 Interfaces to Upper Layers | |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4.2.1 User Plane Interfaces | |
699dc8d2d5b7aed14bd4330dab22869d | 102 744-3-4 | 4.2.1.0 General | Three SAPs (AM-SAP, UM-SAP and TM-SAP) are defined between the Bearer Connection Layer and the upper layers in the user plane. Their definitions are based on [1]. The primitives and parameters used are summarized below. ETSI ETSI TS 102 744-3-4 V1.1.1 (2015-10) 11 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.