hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.1.2 Header Compression Sub-layer | The Header Compression sub-layer provides four access services (also called header compression channels) to the higher layer: • Non-Compressed Channel (nCC): IP packets accessing through this service will be transmitted with uncompressed header. This header compression channel can be accessed by all applications and se... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.1.3 Encapsulation and Addressing sub-layers | Encapsulation and addressing is split in two sub-layers, one at MPE level and another one at MPEG-TS level. This splitting serves the possibility to insert MAC layer encryption in the Forward Link. These sub-layers shall provide the following encapsulation services in the FWD link: • MPE Encapsulation: - MPE Encapsulat... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.2 Return Link | The SSA and QS-CDMA options are described separately below. |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.2.1 Asynchronous Access | This refers to the SSA option. The detailed protocol stack for the S-MIM link any physical layers for access to SS1, SS2 in the Asynchronous Return Link is depicted in Figure 4.2. USER PLANE MANAGEMENT PLANE CONTROL PLANE Modulation & Transmission Header Compression Encryption (LL) Encapsulation & Addressing Transmissi... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.2.1.1 Header Compression Sub-layer | The Header Compression sub-layer provides two access services to the IP layer: • Non-Compressed Channel (nCC). • Unidirectional stateless Compressed Channel (UsCC). These are as defined in clause 4.1.2. |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.2.1.2 Transmission Mode sub-layer | The Transmission Mode sub-layer, managed by the ARQ Management and Load control function, offers three access services to the Header Compression sub-layer: • Transparent Mode (Tr Mode): PDUs mapped into this transmission mode will be transmitted without expecting any link layer acknowledgements in the forward link. • A... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.2.1.3 Encapsulation and Addressing sub-layer | The Encapsulation sub-layer offers one access service to the Transmission Mode sub-layer: • RLE: Return Link Encapsulation. Hence, RLE is used to encapsulate higher layer packets and to insert the system specific MAC layer addressing. The MAC layer addresses applied are specified in clause 7. |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.2.1.4 Encryption sub-layer | The encryption sub-layer, only in the link layer in the case of the return link, managed by the link layer authentication control, provide two access services to the Encapsulation and Addressing sub-layer: • Encrypted Channel (EC): upper layer packets mapped into this access service will be transmitted encrypted, as sp... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.2.2 Synchronous Access | This refers to the QS-CDMA option. The detailed protocol stack for the S-MIM link any physical layers for access to SS3, in the Synchronous Return Link is depicted in Figure 4.3. USER PLANE MANAGEMENT PLANE CONTROL PLANE Modulation & Transmission Header Compression Encryption (LL) Encapsulation & Addressing PHY Link La... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.2.2.1 Header Compression sub-layer | The Header Compression sub-layer provides two access services (also called header compression channel) to the IP layer: • Non-Compressed Channel (nCC): IP packets accessing through this service will be transmitted with uncompressed header. This header compression channel can be accessed by all applications and services... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.2.2.2 Encapsulation and Addressing sub-layer | The Encapsulation sub-layer offers one access service to the Transmission Mode sub-layer: • RLE: Return Link Encapsulation. Hence, RLE is used to encapsulate higher layer packets and to insert the system specific MAC layer addressing. The MAC layer addresses applied are specified in clause 7. |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 4.2.2.3 Encryption sub-layer | The encryption sub-layer, only in the link layer in the case of the return link, managed by the link layer authentication control, provide two access services to the Encapsulation and Addressing sub-layer: • Encrypted Channel (EC): upper layer packets mapped into this access service will be transmitted encrypted, as sp... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5 Header Compression | The Header Compression sub-layer provides four access services (also called header compression channels in the present document) to the IP layer, as can be observed in Figure 5.1 and Figure 5.2: • Non-Compressed Channel (nCC): IP packets accessing through this service will be transmitted with uncompressed header. This ... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5.1 Header Compression for Broadcast/Multicast Services | The use of header compression on broadcast/Multicast service is optional. If header compression is used, these services shall use a modified version of ROHC [11] as specified in this clause. ROHC shall be used in the following configuration: • Unidirectional mode. • Multicast IP should not be discarded at the compresso... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5.2 Header Compression for Short Messages | These services are connectionless and will use UDP/IP. These services are static in the sense that the parameters used for the communication (IP addresses and port numbers) do not vary in a long period of time. Header compression is optional for these services. Header compression can be applied separately in the FWD an... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5.2.1 Context Identifier extension | Instead of defining 16 different contexts (4 bits) for source and destination addresses, the size of the context identifier extension has been increased so that now there are 256 contexts for source and destination (8 bits each). This allows the compression scheme to support up to 256 different service centres in the s... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5.3 Header Compression for Bidirectional Services | The ROHC standard [11] provides a good framework for header compression for large delay and error prone links and is proposed as the header compression schema for bidirectional services. Besides the unidirectional mode proposed for broadcast and multicast services in clause 5.3, the ROHC standard [11] defines two addit... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5.3.1 Feedback Messages | For both O-mode and R-mode a feedback logical channel is required for the decompressor instance to send messages towards the associated compressor instance, this scenario is depicted by Figure 5.10. ETSI ETSI TS 102 721-5 V1.2.1 (2013-08) 22 Figure 5.10: ROHC logical channels Feedback messages consist of small ROHC pac... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5.3.1.1 Piggybacked or interspersed mode | The piggybacked mode method is preferable as it saves the large overhead introduced by the link layer encapsulation due to the very small size of the ROHC feedback packets. The format of the feedback packet is shown in Figure 5.11. Figure 5.11: Piggybacked and interspersed ROHC feedback message format The semantics of ... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5.3.1.2 Dedicated channel mode | In case that the feedback message is sent through a dedicated feedback channel, its format shall be modified to that shown in Figure 5.12. Figure 5.12: Dedicated channel ROHC feedback message format The semantics of the feedback message are: • comp channel: This field helps to identify to which compressor instance the ... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5.3.2 Encapsulation | Network datagrams, IPv4 and IPv6, are compressed with the ROHC technology and then passed through the layer 2 encapsulation which shall provide the functionalities below, from [9] and [11]: • Error detection: Lower layers shall detect errors in the reconstructed compressed datagram. It is recommended, though, that such... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5.3.2.1 Encapsulation with MPE | The services provided through the forward link are based in MPE over MPEG2-TS. That is, all network datagrams shall be encapsulated with an MPE datagram_section as specified in [1]. • LLC_SNAP_flag shall be set to "1" and the payload type (IPv4/IPv6 ROHC Compressed) shall be signalled through the LLC_SNAP structure. In... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5.3.2.2 Encapsulation with RLE | In the return link, the compressed network datagrams are encapsulated through the RLE protocol and identified with dedicated logical channels, as it is defined in clause 6.2.1, therefore the RLE protocol_type field can be omitted to reduce the overhead introduced by the encapsulator. In case feedback messages are not p... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 5.3.3 ROHC parameters | The ROHC protocol is based on a number of parameters that form part of the negotiated channel state and per-context state. • rohc_large_cid: This flag indicates whether short (0 or 1 byte) or large (1 or 2 bytes) CID identifiers are used. • rohc_max_cid: This parameter constraints the maximum number of context identifi... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 6 Encapsulation (Fragmentation & Reassembly) | The Encapsulation sub-layer provides two access services (also called encapsulation options) to the encryption sub-layer in the FWD link, see Figure 6.1: • MPE/MPEG Encapsulation; • MPE-iFEC/MPEG Encapsulation; where the MPE/MPEG service is taken as baseline. All planes (user, control and management) shall have access ... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 6.1 Forward Link Encapsulation | In the S-MIM system MPE will be used in similar way to DVB-H [i.3]: • To encode an IP flow into a Transport Stream, Multiprotocol Encapsulation (MPE) shall be used. LLC_SNAP_flag = 0 shall be used when the MPE section encapsulates an (uncompressed) IPv6 packet. Stuffing bytes shall not be used. LLC_SNAP flag = 1 shall ... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 6.2 Return Link Encapsulation | The encapsulation protocol return link will be Return-link Encapsulation (RLE) as defined in [i.15]. The RLE protocol provides mechanisms to encapsulate and fragment generic PDU, whether IP based or not, into physical frames. In addition the standard provides a native capability to create new facilities and to customiz... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 6.2.1 Encapsulation for SSA Radio Interface | Four different protocols shall be encapsulated in RLE to access SSA: • IPv6; • IPv4; • RFC 6282 [i.14] (header-compressed IP) with adaptations described in clause 5.2; • LLC-SNAP (for authentication signalling). Additionally, SSA requires the reservation of 1 byte for ARQ management, the reservation of 6B to carry the ... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 6.2.2 Encapsulation for QS-CDMA radio interface | Four different protocols shall be encapsulated in RLE to access QS-CDMA: • IPv6; • IPv4; • ROHC - bidirectional mode (header-compressed IP); • Internal MAC signalling. QS-CDMA has two types of transport channels, namely DCH and RACH. Different RLE configurations will be applied to access each transport channel. ETSI ET... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 6.2.2.1 DCH transport channel | • alpdu_label_type = 2 (1 byte long ALPDU label); • protocol_type_suppressed flag = 1 if the PDU to be encapsulated is IPv6; • protocol_type_suppressed flag = 0 if the PDU to be encapsulated is other than IPv6. In this case, the compressed_protocol_type field is present and shall be set according to Table 6.1, depend... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 6.2.2.2 RACH transport channel | • alpdu_label_type = 1 (8 bytes long ALPDU label); • protocol_type_suppressed flag = 0, since the RACH channel is used only for signalling; • compressed_protocol_type = 0x31. Additionally, the following shall be fulfilled at the FPDU: • it shall set the use_explicit_payload_header_map to 0 (since the physical layer h... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 7 MAC Layer Addressing | Completing the encapsulation protocol, the definition of the system specific MAC layer addressing is provided in this clause. In particular, the authentication process will provide the necessary information to addressing terminals in the system. ETSI ETSI TS 102 721-5 V1.2.1 (2013-08) 30 |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 7.1 Forward Link | The Addressing for the different services shall be performed based on IP/MAC notification tables as specified in [1]. Note that descriptors based on IP addresses or IP address ranges can only be used when the services are transported using uncompressed IP. If the services are carried using compressed IP or other protoc... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 7.2 MPE MAC Address format | When the MAC address field of MPE is used the format specified in [12] shall be used. According to the specification of MPE in [1], the MAC address field in MPE is 48 bit long. The MAC address is fragmented in 6 fields of 8-bits, labelled MAC_address_1 to MAC_address_6. The order of the bits in the bytes is not reverse... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 7.3 Return Link | |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 7.3.1 QS-CDMA return link | For the SS3 return link subsystem the format of the MAC address will be the same as the one specified for the forward link in clause 7.2. |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 7.3.1.1 MAC Layer addressing for RACH | For this carrier the MAC address of the source is required for the Hub to identify the originator terminal. This information cannot be derived from other means as all terminals share the same random access resource. It is not required to use the MAC address of the destination, namely the Hub, because the each Hub shoul... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 7.3.1.2 MAC Layer addressing for QS-CDMA | Neither source nor destination MAC address is required as the dedicated resources are enough to identify both the terminal and the Hub. |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 7.3.2 SSA return link | In the SSA return link, no MAC destination addresses shall be used, since all the packets target the hub which controls the return link over which the packet was sent. The MAC layer source address shall be used in the SSA return link. The format of the address will be the same as in the forward link, see Table 7.1. NOT... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 8 Link Layer ARQ | The Link Layer provides three Transmission Modes for services being mapped into the SSA air interface: • ACK Mode: acknowledged mode. Upper sub-layer packets mapped into this transmission mode will require link layer acknowledgements in the form of a CRC in the forward link and a re-transmission buffer. All transmitted... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 9 Load control (LC) | The LC for the RTN link only is specified (the FWD link is internal to the hub and is not specified). LC is implemented by (i) monitoring the load in the RTN link and (ii) signalling to the terminals the parameters to be used by the ARQ mechanism to limit the overall load. This signalling is implemented in the SAT and ... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 9.1 Internal Interfaces | Both subfunctions of the RTN Load Control Manager are interconnected, as the RTN load monitoring function will trigger the load control resolution function whenever it detects congestion. Additionally, the RTN load monitoring function will interface the NCC policies related to SS1/SS2, as among these policies the conge... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 9.2 External Interfaces | The RTN link resources are shared between the SSA and QS-CDMA interfaces. Therefore, an interface between the CAC/DAMA functions (corresponding to the QS-CDMA interface) and the RTN load control manager is necessary to better balance the resource share. Through this interface both functions can exchange channel load es... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 10 Call Admission Control/DAMA | In the next clauses some flow charts depicts the protocols involved in the CAC/DAMA for the SS3 which involves both the FWD and RTN links. A more detailed description of the contents of the messages interchanged can be found in TS 102 721-6 [4]. |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 10.1 Capacity Allocation Initiated by the Terminal | The procedure shown in Figure 10.1 is used by SS3 terminals to request dedicated resources. It is assumed that the terminal is in LOGGED_ON state as defined in [6]. ETSI ETSI TS 102 721-5 V1.2.1 (2013-08) 38 Figure 10.1: Capacity Allocation initiated by the Terminal |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 10.2 Capacity Allocation Initiated by the Hub | The procedure shown in Figure 10.2 is used by the Hub to announce a SS3 terminal to request dedicated resources. It is assumed that the terminal is in LOGGED_ON state as defined in [6]. ETSI ETSI TS 102 721-5 V1.2.1 (2013-08) 39 Figure 10.2: Capacity Allocation initiated by the Hub |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 10.3 Capacity Release Initiated by the Terminal | The procedure shown in Figure 10.3 is used by SS3 terminals to request the release of previously allocated resources. It is assumed that the terminal is in TX_ON_DATA_ON state as defined in [6]. Term inal Hub CAC/DAM A TX_ON_DATA_ON LOGGED_ON Figure 10.3: Capacity Release initiated by the Terminal ETSI ETSI TS 102 721-... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 10.4 Capacity Release Initiated by the Hub | The procedure shown in Figure 10.4 is used by the Hub to indicate to a SS3 terminal to release its allocated resources. Term inal Hub CAC/DAM A TX_ON_DATA_ON LOGGED_ON Figure 10.4: Capacity Release initiated by the Hub |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11 Security Mechanisms | Security mechanisms refer to mutual authentication and encryption. Mutual authentication is carried out at link layer, while encryption may be applied either at the link or at the network layer. Encryption at the link layer is preferred, but it is in general not compatible with existing broadcast standards. Therefore, ... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1 Security procedures | |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1.1 Mutual authentication procedure | This procedure is used to authenticate the terminal in the network. Furthermore it allows terminals to authenticate the network. This procedure is identical to the UMTS mutual authentication procedure and shall be performed as specified in [5]. After this procedure the terminal and the hub have a valid encryption key (... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1.1.1 Mutual Authentication procedure using IMSI over Satellite | This procedure is used for the first entry into the S-MIM network, or when the hub identifier of the LAI received over the air interface is different from the previously received LAI stored in the terminal (while the operator identifier remains the same). This procedure is used when terminal does not have valid TMSI an... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1.1.2 Mutual Authentication procedure using IMSI over CGC | This procedure is essentially the same as the equivalent procedure over satellite. The only difference is that the CGC is used to relay packets, however the functionality regarding security resides in the terminal and the hub, being the CGC transparent to security. Figure 11.3: UMTS authentication procedure over CGC us... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1.1.3 Mutual Authentication procedure using TMSI over Satellite | This procedure is used by the terminals to renew the authentication in the network provided that they have been authenticated in the network before. This implies the terminal has already a valid CK and IK and TMSI. In contrast to the authentication procedure using IMSI, in this case all messages are sent encrypted. Mor... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1.1.4 Mutual Authentication procedure using TMSI over CGC | This procedure is essentially the same as the equivalent for satellite. The only difference is that the CGC is acting as a relay forwarding the messages from the terminal to the hub and vice versa. ETSI ETSI TS 102 721-5 V1.2.1 (2013-08) 45 Figure 11.5: UMTS authentication using TMSI over CGC |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1.2 TMSI renewal procedure | The procedure to renew the TMSI over satellite shall be performed as specified in [5]. This procedure assigns a new temporary MAC address to a terminal. The use of temporary MAC addresses increases the security of the system. The validity of a TMSI is monitored by the hub. When a TMSI has been used to secure a certain ... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1.2.1 TMSI renewal procedure over Sat | TMSI_new LAI UT Hub/VLR AuC TMSI_new ok Figure 11.6: TMSI renewal over sat |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1.2.2 TMSI renewal procedure over CGC | The TMSI renewal procedure over is the same as the equivalent over satellite, with the only difference that the CGC acts as a relay between the terminal and the hub. Figure 11.7: TMSI renewal over CGC |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1.3 Forward link security negotiation procedure | After the mutual authentication procedure and the TMSI renewal procedure, terminals shall perform the forward link security negotiation procedure. The purpose of this procedure is to establish a secure connection over the forward link. This procedure is initiated by the user terminal with a Security_Capabilities notifi... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1.3.1 Forward link security negotiation procedure over Sat | The forward link security negotiation procedure over satellite is shown in Figure 11.8 for the case in which link layer security is used over the forward link. In case IP layer security is used the procedure is shown in clause 11.2. Figure 11.8: Forward link security negotiation procedure over Satellite. Link layer sec... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.1.3.2 Forward link security negotiation procedure over CGC | The forward link security negotiation procedure over CGC is shown in Figure 11.8 for the case in which link layer security is used over the forward link. In case IP layer security is used the procedure is shown in clause 11.2. ETSI ETSI TS 102 721-5 V1.2.1 (2013-08) 48 UT Hub/VLR AuC CGC Security_capabilites_message Li... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 11.2 IP Layer Security | Security at IP Layer will be provided by using the IPsec protocol suite. IP layer security will only be used in the forward link. The IPsec negotiation shall be performed using IKEv2 as specified in [7]. In order provide privacy and integrity ESP shall be used in transport mode [9]. This protocol is based on the Diffie... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12 Mobility Management | |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12.1 Location Management Protocol | In mobile networks, location management refers to the network identifying the location area of a terminal to locate it whenever the terminal receives a call, message, etc. With this definition, it is not the terminal the one "understanding" its location, but the network. In the S-MIM system, the satellite shall reach t... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12.1.1 Terminal Location in the FWD Link | The terminal shall be capable of identifying its operator, managing hub, satellite beam and (if applicable) terrestrial cell through the forward link signalling and store this information. The set of identifier(s) enabling such identification is hereafter referred to as Local Area Identifier (LAI). NOTE: In case of DVB... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12.1.2 Terminal Location in the RTN Link: Cell Selection Procedure | The S-MIM system allows asymmetrical coverage in FWD and RTN links. The following configurations are possible: • Symmetric coverage: same satellite antenna beam pattern coverage between FWD and RTN links • Asymmetric coverage: different satellite antenna beam pattern coverage between FWD and RTN links with return link ... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12.1.2.1 Positioning Device-Disabled Terminals | The procedure described below shall be applied to terminals without positioning device and/or terminals with positioning device with outdated coverage maps. Terminals not equipped with a "positioning" device (this is applicable to low cost terminals for SS1/S2) cannot solve the uncertainty about the suitable return lin... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12.2 Handover Protocols for SS1/SS2 | |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12.2.1 FWD link handover | The management of mobility for DVB-H and DVB-SH systems is defined in ETSI specifications [i.1] and [i.2]. These documents identify a set of use cases for a FWD link handover. If DVB-SH is applied as forward link radio interface in the S-MIM system, forward link mobility shall be compliant to the ETSI specifications [i... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12.2.2 RTN Link Handover | The Cell Selection procedure defined in clause 12.1.2 applies. |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12.3 Handover Protocols for SS3 | This clause remains for further study. |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12.4 Roaming | |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12.4.1 Scope of roaming in the S-MIM system | The architecture of the S-MIM system allows that a satellite hub manages one or more forward link beams, and the corresponding return links (spotbeams). Each hub could be managed by a different service operator, and different services shall be provided in different forward link beams (and their corresponding return lin... |
3d14b790ab1d8cfcab6b3435fd02e146 | 102 721-5 | 12.4.2 The roaming procedure | When a terminal enters in the coverage area of a forward link beam managed by a different hub than its home hub (home network), it will start receiving also the broadcast signalling of the visited network, which indicates the identity of the managing hub (through the LAI). The terminal will compare the hub identity wit... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 1 Scope | The present document describes the UICC Application Programming Interface for Java Card™ for contactless Applications. Its purpose is to provide access for a contactless Applet to the services provided by the HCI protocol defined in ETSI TS 102 622 [4] for the communication via the CLF. In the scope of the present docu... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 2 References | |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 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 referenced document (including any amendments) applies. • In the case of a reference... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 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 referenced document (including any amendments) applies. • In the case of a reference... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 3 Definition of terms, symbols and abbreviations | |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 3.1 Terms | For the purposes of the present document, the following terms apply: contactless mode: used as a generic term for "Card Emulation Mode" and "Reader Mode" contactless state: corresponds to the logical state of the contactless framework HCP message: Message as specified in ETSI TS 102 622 [4]. NOTE: An HCP message can be... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 3.2 Symbols | Void. ETSI ETSI TS 102 705 V18.0.0 (2023-02) 8 Release 18 |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AID Application IDentifier APDU Application Protocol Data Unit NOTE: According to ISO/IEC 7816-3 [i.1]. API Application Programming Interface CAT Card Application Toolkit CLF ContactLess Front-end NOTE: According to ETSI TS 102 622 [4]. CLT Co... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 4 Description | |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 4.1 Architecture | The present document describes an API and a Contactless Framework that enables Java Card™ Platform based Applets, defined in [9], [10] and [11], to send and receive messages using the HCI protocol as specified in ETSI TS 102 622 [4] and to act as contactless Applets. The Contactless Framework shall support card emulati... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 4.2 Card Emulation Mode | In card emulation mode there exist two exclusive ways to exchange messages over the HCP [4]. The first is based on APDUs provided to the Applet through its process() method as specified in "Application Programming Interface, Java Card™ Platform, 3.0.1 Classic Edition" [9]. The second is made available by the package ui... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 4.3 Reader Mode | |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 4.3.0 Reader Mode service description | The functionality to support the reader mode is provided in the package uicc.hci.services.reader. In reader mode the communication technologies defined by the contactless platform for reader mode [4] are supported. The Contactless Framework shall bind the services defined in uicc.hci.services.reader to the correspondin... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 4.3.1 Receiving and sending messages over the contactless interface | To be able to receive and send messages over the contactless interface in reader mode the Applet shall activate the ReaderListener.EVENT_TARGET_DISCOVERED. An Applet shall only be able to activate this event or to use the restartReadermodeProcedure method if it is in lifecycle state ACTIVATED. To release the CLF contro... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 4.3.2 Receiving notifications about reader status | To be able to receive CLF reader status notifications the Applet shall activate the event ReaderListener.EVENT_READER_STATUS. An Applet shall only be able to activate this event if it is in lifecycle state ACTIVATED. To release the CLF reader status notifications an Applet shall deactivate the event ReaderListener.EVEN... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 4.4 Connectivity Service | The functionality to support the connectivity mechanisms specified in the HCI specification [4] is provided in the package uicc.hci.services.connectivity. The Contactless Framework shall bind the services defined in uicc.hci.services.connectivity to the corresponding resources (e.g. gates and pipes) specified in the HC... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 4.5 CLT specific extension to Card Emulation Mode | The Contactless Framework shall observe the communication in CLT mode as specified in the SWP specification [14] between the CLF and arbitrary entities on the UICC. It shall notify every Applet which registered a CLTObserverListener object and activated the event EVENT_CLT_TRANSACTION_A_DONE about the end of a CLT sess... |
727d36e9aec13edd26afb056e6a4495e | 102 705 | 5 Interaction with Proactive Functionality | The ProactiveHandler defined in ETSI TS 102 241 [5] shall not be available when the contactless Applet is invoked with the callback methods defined in the present document, or when the Applet is invoked with the process() method of the Applet class defined in Application Programming Interface, "Java Card™ Platform, App... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 1 Scope | The present document specifies the S-MIM (S-band Mobile Interactive Multimedia) system in which a standardized S-band satellite mobile broadcast system is complemented by the addition of a return channel The present document is part 3 of the multi-part deliverable and concerns aspects of the air interface for the S-ban... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 2 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 referenced document (including any amendments) applies. Referenced documents which a... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 721-6: "Satellite Earth Stations and Systems (SES); Air interface for S-band Mobile Interactive Multimedia (S-MIM); Part 6: Protocol Specifications, System Signalling". |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] IEEE Journal on Selected Areas in Communications: "Bandlimited Quasi-Synchronous CDMA: A Novel Satellite Access Technique for Mobile and Personal Comm... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 3 Definitions, symbols and abbreviations | |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: 2 GHz MSS band: 1 980 MHz to 2 010 MHz (earth-to-space) and 2 170 MHz to 2 200 MHz (space-to-earth) frequency bands NOTE: These paired bands are assigned to MSS. architecture: abstract representation of a communications system NOTE: Th... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: N0 Single-sided noise power spectral density I0 Single-sided interference power spectral density ETSI ETSI TS 102 721-3 V1.2.1 (2013-08) 8 |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK Acknowledgement signalling ACLR Adjacent Channel Leakage power Ratio C number of Columns C Received signal (carrier) power CDMA Code Division Multiple Access CGC Complementary Ground Component CRC Cyclic Redundancy Check DL Down-Link DVB-S... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.