hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
648692b32393c411cac073882fd20d74 | 103 275 | 6.3.3 Parameters | The service primitive calls the following parameters: • BSM_ID. It is the BSM Identity of the local SI-SAP interface. • Logoff Source. It identifies the source that initiated the logoff procedure. The source is part of the BSM system but may also be external to the BSM network. |
648692b32393c411cac073882fd20d74 | 103 275 | 6.3.4 Service primitive: SI-C-LOGOFF | |
648692b32393c411cac073882fd20d74 | 103 275 | 6.3.4.1 SI-C-LOGOFF primitive specification | Table 6.2: SI-C-LOGOFF primitive specification PRIMITIVE NAME SI-C-LOGOFF-*** FUNCTION Successful logon notification Primitive parameters: -ind Comments BSM_ID M Specific values of BSM_ID are used to distinguish between unicast, broadcast and multicast data transfers Logoff Source M To identify the source of the logoff... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.3.4.2 SI-C-LOGOFF-IND | The logoff message primitive is an unsolicited indication from the SD layer to the SI layer. Upon primitive receipt, the SDAF module shall reset all relevant traffic information related to address resolution, resource reservation, and multicast group membership, because the satellite air interface will be shut down. |
648692b32393c411cac073882fd20d74 | 103 275 | 6.4 SI layer configuration | |
648692b32393c411cac073882fd20d74 | 103 275 | 6.4.1 Service definition | The SI layer configuration service is provided by the SD layer of a ST to the SI layer in order to receive the necessary parameters from the gateway to perform the SI layer configuration in terms of addressing plan. Where applicable, the gateway may also provide additional parameters, related to the configuration of ot... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.4.2 Primitives involved in the service | The SI layer configuration service shall use the following primitives: • SI-C-CONF-REQ. • SI-C-CONF-CFM. • SI-C-CONF-IND. • SI-C-CONF-RES. |
648692b32393c411cac073882fd20d74 | 103 275 | 6.4.3 Parameters | The service primitives call the following parameters: • SICONF_BlockNumber. It defines the number of configuration blocks contained in the primitive. The first block is mandatory and contains information about address plans. Following blocks are optional. • Network_Address_Type. It defines the network protocol accordin... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.4.4 Service primitive: SI-C-SICONF | |
648692b32393c411cac073882fd20d74 | 103 275 | 6.4.4.1 SI-C-SICONF primitive specification | Table 6.3: SI-C-SICONF primitive specification PRIMITIVE NAME SI-C-SICONF-*** FUNCTION SI layer configuration for network addressing Primitive parameters: -req -cfm -ind -res Comments SICONF_BlockNumber O O O O The number of information block for the SI configuration Network_Address_Type M M M M Client_Network_Address ... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.4.4.2 SI-C-SICONF-REQ | The SI layer configuration primitive is a request from the SI layer to get the configuration parameters from the gateway. Upon primitive receipt, the SD layer shall forward the request to the gateway. |
648692b32393c411cac073882fd20d74 | 103 275 | 6.4.4.3 SI-C-SICONF-CFM | The SI layer configuration primitive is a confirmation issued by the SD layer to notify the SI layer about the set of parameters provided by the gateway necessary to perform the SI layer configuration. Upon primitive receipt, the SI layer shall implement the addressing plan and may implement the configuration of the ot... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.4.4.4 SI-C-SICONF-IND | The SI layer configuration primitive is an unsolicited indication from the SD layer of the gateway containing the list of parameters provided by the ST to carry out the SI layer configuration. Upon primitive receipt, the SI layer of the gateway processes the provided service parameters. |
648692b32393c411cac073882fd20d74 | 103 275 | 6.4.4.5 SI-C-SICONF-RES | The SI layer configuration primitive is a response from the SI layer of the gateway containing the list of parameters to be provided to the ST to carry out the SI layer configuration. Upon primitive receipt, the SD layer shall forward the response to the ST. ETSI ETSI TS 103 275 V1.1.1 (2015-05) 23 |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5 Group transmit | |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5.1 Service definition | The group transmit service is carried out by the SI layer of a gateway to enable the SD layer to transmit a new multicast group and to record the satellite terminals that subscribed to a given multicast group. The service may be triggered by multicast group membership (e.g. IGMP IETF RFC 3376 [11]) and routing protocol... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5.2 Primitives involved in the service | The group transmit service shall use the following primitives: • SI-C-MCGROUP_ADD-REQ. • SI-C-MCGROUP_ADD-CFM. • SI-C-MCGROUP_REMOVE-REQ. • SI-C-MCGROUP_REMOVE-CFM. |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5.3 Parameters | The service primitives call the following parameters: • BSM_ID. It defines the BSM Identity of the SI-SAP interface instance used by the ST during the multicast group transmit service. It is set to 0 by default during the activation of a new multicast group. • BSM_GID. It defines the BSM Group Identity of the SI-SAP in... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5.4 Service primitive: SI-C-MCGROUP_ADD | |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5.4.1 SI-C-MCGROUP_ADD primitive specification | Table 6.4: SI-C-MCGROUP_ADD primitive specification PRIMITIVE NAME SI-C-MCGROUP_ADD-*** FUNCTION To generate a new multicast group upon multicast SI signalling Primitive parameters: -req -cfm Comments BSM_ID M M BSM Identifier of the satellite terminal belonging to the multicast group being added BSM_GID M M Identifier... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5.4.2 SI-C-MCGROUP_ADD-REQ | The group transmit primitive is a request from the SI layer to enable the SD layer to transmit a new multicast group or subscribe new ST to the list of receivers for a given multicast group. Upon primitive receipt, the SD layer records the address of the new multicast group being activated and the addresses of the STs ... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5.4.3 SI-C-MCGROUP_ADD-CFM | The group transmit primitive is a confirmation from the SD layer about the completion of the multicast transmission configuration for the new group and the subscribers addresses. Upon primitive receipt, no action is performed by the SI layer. |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5.5 Service primitive: SI-C-MCGROUP_REMOVE | |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5.5.1 SI-C-MCGROUP_REMOVE primitive specification | Table 6.5: SI-C-MCGROUP_REMOVE primitive specification PRIMITIVE NAME SI-C-MCGROUP_REMOVE-*** FUNCTION To remove an existing multicast group upon multicast SI signalling Primitive parameters: -req -cfm Comments BSM_ID M M BSM Identifier of the satellite terminal belonging to the multicast group being removed BSM_GID M ... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5.5.2 SI-C-MCGROUP_REMOVE-REQ | The group transmit primitive is a request from the SI layer to remove the address of a given multicast group address or of satellite terminals that unsubscribe from the given multicast group. Upon primitive receipt, the SD layer removes the address of the multicast group and the STs unsubscribing from the multicast gro... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.5.5.3 SI-C-MCGROUP_REMOVE-CFM | The group transmit primitive is a confirmation from the SD layer about the completion of the multicast transmission removal for the new group and the subscribers addresses. Upon primitive receipt, no action is performed by the SI layer. |
648692b32393c411cac073882fd20d74 | 103 275 | 6.6 Data transfer | |
648692b32393c411cac073882fd20d74 | 103 275 | 6.6.1 Service definition | The data transfer service is carried out by the SI layer in conformance to the service definition given in ETSI TS 102 357 [7]. |
648692b32393c411cac073882fd20d74 | 103 275 | 6.6.2 Primitives involved in the service | The data transfer service shall use the following primitives, as stated in ETSI TS 102 357 [7]: • SI-U-UNITDATA-REQ. • SI-U-UNITDATA-CFM. ETSI ETSI TS 103 275 V1.1.1 (2015-05) 25 |
648692b32393c411cac073882fd20d74 | 103 275 | 6.6.3 Parameters | The service primitives call the following parameters: • Destination BSM_ID. It defines the BSM Identity of the SI-SAP interface instance used by the other peer to receive user data. • Source BSM_ID. It defines the BSM Identity of the SI-SAP interface instance used by the local peer to transmit user data. It shall be us... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.6.4 Service primitive: SI-U-UNITDATA | |
648692b32393c411cac073882fd20d74 | 103 275 | 6.6.4.1 SI-U-UNITDATA primitive specification | Table 6.6: SI-U-UNITDATA primitive specification PRIMITIVE NAME SI-C-UNITDATA -*** FUNCTION To transfer user data through the BSM network. Primitive parameters: -req -ind Comments Destination BSM_ID M M Specific values of BSM_ID are used to distinguish between unicast, broadcast and multicast data transfers Source BSM_... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.6.4.2 SI-U-UNITDATA-REQ | The data transfer primitive is a request from the SI layer to trigger the SD layer to transmit the transported SDU over the BSM subnetwork. Upon primitive receipt, the SD layer forwards the SDU to the SD queues according to the signalled QID and eventually encapsulates the SDU in an SD frame according to the destinatio... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.6.4.3 SI-U-UNITDATA-IND | The data transfer primitive is an unsolicited indication from the SD layer to deliver a SDU to the SI layer. Upon primitive receipt, the SI layer processes the SDU: the SI layer shall insert the SDU in the routing chain or forward it to the upper layer for further protocol processing operations depending on the destina... |
648692b32393c411cac073882fd20d74 | 103 275 | 6.7 Summary of SI-SAP interface service primitives | According to the specification of new and updated services given in the previous clauses, the summary of overall SI-SAP interface service primitives is as follows (Table 6.7, where the services already defined in the ETSI BSM relevant documentation are shaded in grey). Table 6.7: Summary of overall SI-SAP interface ser... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 1 Scope | The present document defines the methodology for discovering an Authoritative FQDN for a radio service, including discovery using DNS queries to radiodns.org, a root domain name server operated by RadioDNS. The present document also defines the construction of a unique ServiceIdentifier parameter and bearerURI for a ra... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 2 References | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 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. Referenced documents which a... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 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. NOTE: While any hyperlinks i... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 3 Definition of terms, symbols and abbreviations | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 3.1 Terms | For the purposes of the present document, the following terms apply: application: means of enhancing an associated radio service, using an IP connection, with additional content, functionality, or interactivity authoritative FQDN: internet domain for a service provider bearer: method of carriage of the service bearerUR... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 3.2 Symbols | Void. |
151aab35e130ed578d9b76b9059e128d | 103 270 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AM Amplitude Modulation AMSS Amplitude Modulation Signalling System ETSI ETSI TS 103 270 V1.4.1 (2022-05) 8 ASF Advanced Systems Format CNAME DNS Canonical NAME record DAB Digital Audio Broadcasting DNS Domain Name System DRM Digital Radio Mon... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 4 Introduction | It is possible to supplement uni-directional radio services with applications that can take advantage of bi-directional communication using the IP protocol. These applications may enhance the radio services with which they are associated with additional content or functionality, or enable interactivity. Radio devices s... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.1 FM with RDS/RBDS | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.1.1 RDS/RBDS parameters | The FM system supports identification of a radio service through transmission of meta-data by using RDS [8] or RBDS [9]. ETSI ETSI TS 103 270 V1.4.1 (2022-05) 10 The parameters are defined in table 1. Table 1: RDS/RBDS parameter description Parameter Description Value Status gcc The Global Country Code (GCC) of the cou... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.1.2 Construction of RadioDNS FQDN | The RadioDNS FQDN for a VHF/FM service is compiled as follows: <frequency>.<pi>.<gcc>.fm.radiodns.org Some examples of RadioDNS FQDNs constructed from broadcast parameters are shown in table 2. Table 2: Example of RadioDNS FQDN construction for RDS/RBDS GCC PI Frequency (MHz) RadioDNS FQDN ce1 c586 95,8 09580.c586.ce1.... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.1.3 Construction of ServiceIdentifier | The ServiceIdentifier for a VHF/FM service is compiled as follows: fm/<gcc>/<pi>/<frequency> Some examples of ServiceIdentifiers constructed from broadcast parameters are shown in table 3. Table 3: Example of RadioDNS ServiceIdentifier construction for RDS/RBDS GCC PI Frequency (MHz) RadioDNS ServiceIdentifier ce1 c586... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.1.4 Construction of bearerURI | The bearerURI for a VHF/FM service is compiled as follows: fm:<gcc>.<pi>.<frequency> The <frequency> element may be replaced by the asterisk ("*") character to signify any frequency. In this case the PI code alone shall be used by the device to locate the source. Some examples of FM bearerURIs constructed from broadcas... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.2 Digital Audio Broadcasting (DAB/DAB+) | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.2.1 DAB/DAB+ parameters | The parameters are defined in table 5. Table 5: DAB parameter description Parameters Description Value Status gcc The Global Country Code (GCC) of the country of origin of the service (see annex A) 3-char hexadecimal mandatory eid The Ensemble Identifier (EId) of the service 4-char hexadecimal mandatory sid The Service... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.2.2 Construction of RadioDNS FQDN | The RadioDNS FQDN for a DAB/DAB+ service is compiled as follows: [<uatype>.]<scids>.<sid>.<eid>.<gcc>.dab.radiodns.org Some examples of RadioDNS FQDNs constructed from broadcast parameters are shown in table 6. Table 6: Example of RadioDNS FQDN construction for DAB GCC EId SId SCIdS UAType RadioDNS FQDN de0 100c d220 0... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.2.3 Construction of ServiceIdentifier | The ServiceIdentifier for a DAB/DAB+ service is compiled as follows: dab/<gcc>/<eid>/<sid>/<scids>[/<uatype>] The <separator> element is application specific. The inclusion of <uatype> is mandatory for data services or data components of audio services. Some examples of ServiceIdentifiers constructed from broadcast par... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.2.4 Construction of bearerURI | The bearerURI for a DAB/DAB+ service is compiled as follows: dab:<gcc>.<eid>.<sid>.<scids>[.<uatype>] The inclusion of <uatype> is mandatory for data services or data components of audio services. Some examples of bearerURIs constructed from broadcast parameters are shown in table 8. Table 8: Example of RadioDNS bearer... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.3 Digital Radio Mondiale (DRM) | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.3.1 DRM parameters | The parameters are defined in table 9. Table 9: DRM parameter description Parameters Description Value Status sid The Service Identifier (SId) of the service 6-char hexadecimal mandatory appdomain The application domain of the data component 1-char hexadecimal mandatory for data components, otherwise omitted uatype The... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.3.2 Construction of RadioDNS FQDN | The RadioDNS FQDN for a Digital Radio Mondiale service is compiled as follows: [<uatype>.<appdomain>]<sid>.drm.radiodns.org Some examples of RadioDNS FQDNs constructed from broadcast parameters are shown in table 10. Table 10: Example of RadioDNS FQDN construction for DRM SId App Domain UAType RadioDNS FQDN e1c238 e1c2... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.3.3 Construction of ServiceIdentifier | The ServiceIdentifier for a Digital Radio Mondiale service compiled as follows: drm/<sid>[/<appdomain>/<uatype>] Some examples of ServiceIdentifiers constructed from broadcast parameters are shown in table 11. Table 11: Example of RadioDNS ServiceIdentifer construction for DRM SId App Domain UAType RadioDNS ServiceIden... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.3.4 Construction of bearerURI | The bearerURI for a Digital Radio Mondiale service is compiled as follows: drm:<sid>[.<appdomain>.<uatype>] Some examples of bearerURIs constructed from broadcast parameters are shown in table 12. Table 12: Example of RadioDNS bearerURI construction for DRM SId App Domain UAType RadioDNS bearerURI e1c238 drm:e1c238 f07... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.4 AM Signalling System (AMSS) | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.4.1 AMSS parameters | The parameters are defined in table 13. Table 13: AMSS parameter description Parameters Description Value Status sid The Service Identifier (SId) of the service 6-char hexadecimal mandatory The SId value for AMSS is intended to be suitably unique internationally so as to not require region identification. |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.4.2 Construction of RadioDNS FQDN | The RadioDNS FQDN for an AM service with AMSS is compiled as follows: <sid>.amss.radiodns.org |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.4.3 Construction of ServiceIdentifier | The ServiceIdentifier for an AM service with AMSS is compiled as follows: amss/<sid> ETSI ETSI TS 103 270 V1.4.1 (2022-05) 14 |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.4.4 Construction of bearerURI | The bearerURI for an AM service with AMSS is compiled as follows: amss:<sid> |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.5 IBOC | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.5.1 IBOC parameters | The parameters are defined in table 14. Table 14: IBOC parameter description Parameters Description Value Status tx Transmitter Identifier Service broadcast identifier 5-char hexadecimal mandatory cc Country Code Service broadcast country code 3-char hexadecimal mandatory mId The identifier for a multicast Supplemental... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.5.2 Construction of RadioDNS FQDN | The RadioDNS FQDN for an IBOC service is compiled as follows: [<mId>.]<tx>.<cc>.hd.radiodns.org Table 15: Example of RadioDNS FQDN construction for IBOC tx cc mId RadioDNS FQDN 07A26 292 07a26.292.hd.radiodns.org 07A26 292 2 2.07a26.292.hd.radiodns.org |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.5.3 Construction of ServiceIdentifier | The ServiceIdentifier for an IBOC service is compiled as follows: hd/<cc>/<tx>[/<mId>] Table 16: Example of RadioDNS ServiceIdentifier construction for IBOC tx cc mId RadioDNS ServiceIdentifier 07A26 292 hd/292/07a26 07A26 292 2 hd/292/07a26/2 ETSI ETSI TS 103 270 V1.4.1 (2022-05) 15 |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.1.5.4 Construction of bearerURI | The bearerURI for an IBOC service is compiled as follows: hd:<cc>.<tx>[.<mId>] Table 17: Example of RadioDNS bearerURI construction for IBOC tx cc mId RadioDNS bearerURI 07A26 292 hd:292.07a26 07A26 292 2 hd:292.07a26.2 |
151aab35e130ed578d9b76b9059e128d | 103 270 | 5.2 Resolution of Authoritative FQDN | The RadioDNS FQDN, constructed from the broadcast parameters, is used to acquire the Authoritative FQDN. Making a DNS query with a RadioDNS FQDN will return a single CNAME record containing the Authoritative FQDN of the service provider. If no CNAME is returned, then the service has not been registered. EXAMPLE: Consid... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 6.1 General | An Authoritative FQDN may also be provided for IP-streamed services, by sending the value as part of the in-stream metadata of the IP stream. This is defined as the parameter fqdn. Since no broadcast parameters exist for such services, an additional parameter is required to provide disambiguation so that the particular... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 6.2 Inclusion of parameters into stream metadata | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 6.2.1 Streaming transports | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 6.2.1.1 SHOUTcast | SHOUTcast uses a client-server model, with each component communicating via a network protocol that intermingles audio or video data with metadata such as song titles and the station name. It uses HTTP as a transport protocol. NOTE: Additional information is available from https://forums.radiotoolbox.com/viewtopic.php?... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 6.2.1.2 ASF | Advanced Systems Format (ASF) is a container format that is part of the Windows Media framework. It typically defines a payload containing multiple streams of data, e.g. audio and a metadata stream. An additional stream shall be created, solely containing the fqdn and sid, declared as Custom Metadata using key/value pa... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 6.2.1.3 Flash Audio | Flash Audio is a container format for audio and video streams. The parameters shall be implemented as a non-persistent Remote Shared Object available on the URI of the Flash Audio stream itself. The object shall be read-only for clients. NOTE: Guidance is available from http://help.adobe.com/en_US/FlashPlatform/referen... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 6.2.2 Metadata intervals | It is desirable that the client receives initial or updated parameters with as short a delay as possible. The cycle time of the metadata parameters will directly affect the speed at which connecting clients can access applications. It is recommended that service providers ensure that connecting clients receive the para... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 6.3 Construction of bearerURI | The bearerURI for an IP-based service is constructed from the URL for the stream source. EXAMPLE: http://media-ice.musicradio.com/Capital |
151aab35e130ed578d9b76b9059e128d | 103 270 | 6.4 Construction of ServiceIdentifier | The ServiceIdentifier for an IP-based service is constructed as follows: id/<fqdn>/<sid> 7 Authoritative FQDN and ServiceIdentifier resolution from SPI SI An Authoritative FQDN may also be provided in an SPI SI document [5]. In this case, the fqdn and sid parameters (see clause 6) are provided as attributes of the radi... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 8 Implementation requirements | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 8.1 Service provider implementation | For broadcast services, a service provider shall support clause 5, Authoritative FQDN resolution for broadcast services. In addition, for services transmitted via FM with RDS/RBDS or DAB, the service provider shall transmit the ECC via RDS Group 1A or DAB FIG 0/9 respectively. For DAB or DRM services, the service provi... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 8.2 Device Implementation | For broadcast services, a device shall support clause 5, Authoritative FQDN resolution for broadcast services. For DAB or DRM services, the device may also support clause 7, Authoritative FQDN resolution from SPI SI. For IP-streamed services, a device shall support the acquisition of values for the fqdn and ServiceIden... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 9 Client identification | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 9.1 Introduction | A service provider's application may wish to identify connecting clients by using a client identifier. This enables it to provide a varying response to the client; for example, to provide more detailed or personalized responses to clients that present a client identifier, and less detailed or more generic responses to ... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 9.2 Client identifier format | A client identifier is a string of between 16 and 128 characters, drawn from the allowed characters: [a-zA-Z0-9] It is strongly recommended that a client stores an acquired client identifier against the Authoritative FQDN(s) it has determined it applies to. |
151aab35e130ed578d9b76b9059e128d | 103 270 | 9.3 Client Identifier Presentation | |
151aab35e130ed578d9b76b9059e128d | 103 270 | 9.3.1 Introduction | The common behaviour is defined as: • A client shall determine whether the service provider's application supports the use of a client identifier, using the defined SRV records. • A client may present a client identifier when supported by the service provider's application. • A client shall only present the client iden... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 9.3.2 Use of TLS | Implementation of the use of a client identifier shall require the use of Transport Layer Security (TLS) [13] encryption for any requests or connections that present the client identifier to an application and for any resulting responses or connections from the application to the client. The appropriate version (or ver... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 9.3.3 Protocol guidance | This clause contains specific guidance for a client to present the relevant client identifier over common protocols. In the present document, only a single protocol is defined: HTTPS. Guidance for additional protocols specific to an application, or additional and more specific guidance may be given in the application s... |
151aab35e130ed578d9b76b9059e128d | 103 270 | 9.4 Service provider reception | The common behaviour is defined as: • a service provider's application shall ignore a presented client identifier if it does not intend to make use of it; • a service provider's application shall return a valid response if the client identifier is not presented; • a service provider shall signal that its application su... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 1 Scope | The present document defines the minimum set of 3GPP GPRS features to support ETCS application and to guarantee QoS required. Two operational cases are applicable in GSM-R networks: • GSM-R GPRS packet switched bearer service is only utilized by ETCS PS-mode operation - ETCS only operation. • GSM-R GPRS packet switched... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 2 References | |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 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. Referenced documents which a... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 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. NOTE: While any hyperlinks i... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 3 Definition of terms, symbols and abbreviations | |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 3.1 Terms | For the purposes of the present document, the following terms apply: ETCS application: application comprising the EuroRadio protocol suite non-ETCS application(s): application comprising any other protocol suites than EuroRadio |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 3.2 Symbols | Void. |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ARP Allocation Retention Priority BSS Base Station Subsystem CS Coding Schemes EGPRS Evolved GPRS ETCS European Train Control System ETSI European Telecommunication Standards Institute GERAN GSM/EDGE Radio Access Network GGSN Gateway GPRS Supp... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 4 General requirements | |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 4.1 ETCS application characteristics | GPRS and EGPRS are the available packet switched bearer services based on GSM, and are applicable for GSM-R too. These bearer services are to be considered for the transport of the ETCS application and in addition, certain features are required to adapt to the ETCS characteristics and to prioritize the ETCS application... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.