hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.2.1 Recording Session | The primary function to be delivered by the present interface is the means to initiate and tear down a simplex audio (voice) connection between the SRS and SRC with a single, logical, SIP Endpoint involved per connection on each side of the present interface that controls the connection as well as its respective Media ... |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.3 Signalling Interface | |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.3.0 General Description | The SRC initiates a recording session by sending a SIP INVITE request to the SRS. The SRC and the SRS are identified in the From and To header fields, respectively. |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.3.1 SIP Request Methods | Table 8.1 specifies the requests that shall be, may be, or shall not be supported by the SIP on the SRS/SRC interface in order to provide the required interface functionality. The terms and abbreviations used in table 8.1 have the following meaning: • "Sending" means "initiating the method" • "Replying" means "answerin... |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.3.2 SIP Responses | Upon receiving a SIP request SIP entities reply to it with an appropriate SIP response, which depends on the type of request, the type of the receiving SIP entity and the request computing logic. All SIP entities implementing the present interface shall support sending, receiving and processing of all applicable respon... |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.3.3 SIP Header Fields | IETF RFC 3261 [3], IETF RFC 3326 [8], IETF RFC 4412 [12], IETF RFC 3325 [13], IETF RFC 5876 [14], IETF RFC 3323 [15], IETF RFC 4028 [16], IETF RFC 3311 [17] and IETF RFC 4244 [36] - all of them are applicable to the present interface - specify in detail the SIP header fields used at the present interface and explain th... |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.3.4 SIP Bodies | SIP messages may, depending on the application and message type, contain one or more bodies to include information that is not encoded into SIP header fields. This clause specifies the relevant body or content types to be supported at SRS/SRC interface. Table 8.3 shows the SDP types, parameters and values that shall be... |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.3.5 SIP URI Convention | At the SRS/SRC interface the same SIP URI conventions as defined in clause 6.3.6 of the present document apply. |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.3.6 Option Tags | Option tags are used to identify to SIP Endpoints the required, supported or unsupported SIP options/extensions. Table 8.4 lists the option tags which shall be used accordingly at the SRS/SRC interface by all SIP entities. Table 8.4: Option Tags Option Tag List in header field Reference siprec Require, Supported IETF R... |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.3.7 Feature Parameter | A feature parameter describes a feature of a SIP Endpoint associated with the URI in the Contact header field. Table 8.5 lists feature parameters which shall be used accordingly at the SRS/SRC interface by all SIP entities. Table 8.5: Feature Parameter Feature Parameter List in header field Reference +sip.src Contact I... |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.3.8 Handling of Recording Session | The SRC shall include a Resource-Priority header as specified in clause 6.4.5.1 and as shown in table 8.1 in each INIVITE request sent to the SRS containing the resource priority of the CS. This is to inform the SRS about the resource priority of the CS and requires no specific action related to the header field at the... |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.4 Media interface | |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.4.0 General | This clause specifies media interface capabilities at the SRC/SRS interface. Clauses 7.1, 7.2 and 7.4. of the present document are completely supported at the SRC/SRS media interface. Functionality Media inactivity detection as specified in clause 7.3 of the present document is an option at the SRC/SRS media interface. |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.4.1 Media mixing | When using mixing, the SRC combines RTP streams from different participants and sends them towards the SRS using its own SSRC. The SSRCs from the contributing participants shall be conveyed as CSRCs identifiers. The SRC includes one m-line and a unique label for each RTP session in an SDP offer to the SRS. Having recei... |
f3c9c9f0a5d00e88420ea6902915e91c | 103 389 | 8.4.2 Multiple streams | When using multiple streams (m-lines), an SRC includes each m-line (unique label per m-line) in an SDP offer to the SRS. 1. INVITE 5. ACK (200 OK on INVITE) 2. 180 Ringing 7. BYE Bi-directional RTP 4. 200 OK (INVITE) 8. 200 OK 3. PRACK 6. 200 OK (PRACK) Privacy: none Resource-Priority: q735.3 Require: resource-priority... |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 1 Scope | The present document specifies European requirements for ADSL2. The present document endorses ITU-T Recommendation G.992.3 [1] and amendments 1 [2], 2 [3] and 3 [4], the contents of which apply together with the addition of the modifications being covered herein, to the exclusion of annex C in ITU-T Recommendation G.99... |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ITU-T Recommendation G.992.3 (01/05): "Asymmetric dig... |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: DSL Digital Subscriber Line INP Impulse Noise Protection REIN Repetitive Electrical Impulse Noise |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 4 Test methods | All test methods shall be as defined in TS 101 388 [6] , and DSL Forum Technical report TR-100 [5], as required by test definitions in clause 5. |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 5 Other specific requirements | |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 5.1 European specific tests | This clause contains European specific tests. Other performance requirements are for further study. |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 5.1.1 Repetitive Electrical Impulse Noise (REIN) test | The test method shall be identical to the section 7.2.2 of DSL Forum TR-100 [5]. |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 5.2 Framing related requirements | This clause contains European specific requirements related to framing parameter and framing parameter control. |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 5.2.1 Requirements for INP | The mandatory values for Impulse Noise Protection (INP) for upstream and downstream transmission in European ADSL2 transmission systems are 0, ½, 1, 2, 4, 8 and 16. The choice of values for INP_min and Delay_max can dramatically affect the resulting net data rate of the transmission system. This is illustrated in table... |
929e765c73599f395b4ae6393a7f4f63 | 103 388 | 5.2.2 Requirements for S&D framing parameters | The mandatory downstream framing control parameter support for the mandatory latency path 0 is extended as follows (extension of table 7-9/G.992.3 of ITU-T Recommendation G.992.3 amendment 1 [2]). The values in the table shall be supported in the transmitter and receiver. Table 1: Mandatory downstream control parameter... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 1 Scope | The present document defines the application protocol on the LSA1 interface, between LSA Controller (LC) and LSA Repository (LR) [i.2] (LSA1 protocol), and the content of the LSA Spectrum Resource Availability Information (LSRAI) conveyed by this protocol. It is based on the System Requirements defined in ETSI TS 103 1... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 2 References | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 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... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 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... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 3 Definitions and abbreviations | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: idle zone: zone which has been defined but which is not currently operational LSA Licensee: entity operating a MFCN, which holds individual rights of use to an LSA spectrum resource LSA spectrum resource: spectrum resource which is to ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACLR Adjacent Channel Leakage power Ratio ACS Adjacent Channel Selectivity ECC Electronic Communications Committee of the CEPT EIRP Equivalent Isotopic Radiated Power IE Information Element LC LSA Controller LR LSA Repository LSA Licensed Shar... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 4.1 Introduction | Clause 4 contains a high level description of the LSA Spectrum Resource Availability Information (LSRAI), and LSRAI-related functionality supported by the nodes (LC and LR), and the interface (LSA1). This clause expands the related material in the stage 2 specification of ETSI TS 103 235 [i.2], and describes detailed r... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 4.2 LSRAI Scope | LSA Spectrum Resource Availability Information (LSRAI) is information provided to a LSA Licensee, which conveys information on the LSA spectrum resource that may be used by the LSA Licensee. As described in ETSI TS 103 235 [i.2], LSRAI is generated in the LR, and sent to the LC over the LSA1 interface, using LSA1 proto... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 4.3 LSRAI Definition | LSRAI has the following characteristics: • It contains one or more Zones. A Zone is an information object which describes a set of operational conditions or restrictions to be applied by the LSA Licensee. • A Zone has a Zone Type associated to it (e.g. restriction, protection, exclusion). • A Zone contains space, frequ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 4.4 LSRAI Handling Functionality | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 4.4.1 Introduction | As described in ETSI TS 103 235 [i.2], the LSA Information Exchange Function supports communication mechanisms to exchange LSRAI and related acknowledgement information between LR and LC. Clauses 4.4.2 and 4.4.3 further specify the related functional split between LR and LC in support of this high level function. |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 4.4.2 LR Support | The LR supports the LSA Information Exchange Function by: • Constructing zone information including type and parameters for each Zone. • Assigning a Zone ID, which uniquely identifies a Zone over all instances of the LSA1 interface for a given LR. • Assigning a Zone Configuration Index, which uniquely identifies the pa... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 4.5 LSRAI Context | The LSRAI Context is the complete set of zones and their parameters that are to be maintained by the nodes (LC and LR) in an instance of the LSA1 interface. The LR determines the LSRAI Context and informs the LC of any changes in the Context due to creation, modification or deletion of zones. When receiving zone inform... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 4.6 LSRAI Synchronization | As described in ETSI TS 103 235 [i.2], see e.g. clause 5.6.4, the LSA Information Exchange Function supports means for maintaining and restoring LSRAI Synchronization between LR and LC. In the present document, LSRAI Synchronization is the process by which it is ensured that the LR provides the LSRAI context to the LC.... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 4.7 LSRAI Confirmation | As described in ETSI TS 103 235 [i.2], the LSA Information Exchange Function supports means for the LC to notify the LR once the necessary configuration changes in the MFCN have been applied according to the received LSRAI. This process is known as LSRAI Confirmation. The LC shall explicitly provide confirmation for ea... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 4.8 LC Handling of non-impacting Zones | The LC may receive a zone configuration such that the LC has identified that no MFCN resource is impacted by the zone. The LC shall however consider that the zone (and its information) forms part of the LSRAI Context. The LC shall also act as if the necessary configuration changes have been applied, by sending an assoc... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 5 LSA1 Protocol Principles | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 5.1 Specification Notation | For the purposes of the present document, the following notations apply: Procedure When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. LSRAI Notification procedure. Message When r... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 5.2 LSA1 Protocol Procedures | The LSA1 protocol procedures are classified in the following categories: 1) LSRAI handling Procedures 2) Interface management procedures The LSRAI handling procedures are those procedures whose primary function is to convey LSRAI, or to exchange information directly related to the provision of LSRAI (e.g. confirmations... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 5.3 Identification of procedures and messages | Each message defined in the LSA1 protocol (as listed in the tables of clause 5.2) includes a specific Message Type IE, allowing the receiver to identify the general procedure and message. Each procedure instance is identified by a Transaction ID IE, which is mandatory in all messages of the LSA1 protocol. The value of ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 5.4 Procedure Outcome | The node that receives the initiating message shall process the message and its IEs according to the requirements in clauses 6 and 7, and shall include in the response message an indication of whether it considers the procedure to be successful or unsuccessful. The node that initiates the procedure shall also consider ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 5.6 Message Encoding and IE attributes | The message encoding is not specified in the present document. Definitions of the messages and respective information elements are provided including presence, type and range for each IE, in order to enable translation into any particular encoding format. For example: 1) The presence of the IE in a message is defined a... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 5.7 Overview of the protocol specification | Clauses 6 and 7 provide the detailed specification of the LSA1 protocol, as follows. Clause 6 documents for each procedure: 1) The format of each message in the procedure, including: a) List of IEs in each message. b) Presence of the IE in the message. c) Type of the IE and range (if applicable). d) Description of the ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6 LSA1 Protocol: Procedures and Messages | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.1 Registration procedure | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.1.1 General | The purpose of the Registration procedure is to register an LC with an LR. This is the first procedure executed on the LSA1 interface. After successful completion of this procedure, the LC is able to initiate requests or receive notifications concerning LSRAI. ETSI ETSI TS 103 379 V1.1.1 (2017-01) 14 Figure 6.1-1: Regi... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.1.2 REGISTRATION REQUEST | This message is sent by the LC in order to request registration from the LR. The parameter list contained in the message is as follows. Table 6.1-1 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, initiating message). Transaction ID M 7.31 Uniquely identifies ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.1.3 REGISTRATION RESPONSE | This message is sent by the LR in order to respond to a REGISTRATION REQUEST message from the LC. The parameter list contained in the message is as follows. ETSI ETSI TS 103 379 V1.1.1 (2017-01) 15 Table 6.1-2 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, r... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.2 Deregistration procedure | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.2.1 General | The purpose of the Deregistration procedure is to allow the LC to deregister with the LR. After successful completion of this procedure, the LC and LR shall consider that connectivity is no longer available and no new procedures shall be initiated by either node (except for a new Registration procedure). Figure 6.2-1: ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.2.2 DEREGISTRATION REQUEST | This message is sent by the LC in order to request deregistration from the LR. The parameter list contained in the message is as follows. Table 6.2-1 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, initiating message). Transaction ID M 7.31 Uniquely identifie... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.2.3 DEREGISTRATION RESPONSE | This message is sent by the LR in order to respond to a DEREGISTRATION REQUEST message from the LC. The parameter list contained in the message is as follows. Table 6.2-2 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, response message). Transaction ID M 7.31... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.3 Connectivity Check Notification procedure | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.3.1 General | The purpose of the Connectivity Check Notification procedure is to enable the LR to test the connectivity with a registered LC. Figure 6.3-1: Connectivity Check Notification Procedure The LR initiates the procedure by sending a CONNECTIVITY CHECK NOTIFICATION message to the LC. ETSI ETSI TS 103 379 V1.1.1 (2017-01) 17 ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.3.2 CONNECTIVITY CHECK NOTIFICATION | This message is sent by the LR in order to initiate a connectivity check with the LC. The parameter list contained in the message is as follows. Table 6.3-1 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, initiating message). Transaction ID M 7.31 Uniquely id... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.3.3 CONNECTIVITY CHECK NOTIFICATION ACK | This message is sent by the LC in order to respond to a CONNECTIVITY CHECK NOTIFICATION message from the LR. The parameter list contained in the message is as follows. Table 6.3-2 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, response message). Transaction ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.4 Connectivity Check Request procedure | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.4.1 General | The purpose of the Connectivity Check Request procedure is to enable the LC to test the connectivity with the LR with which it is registered. ETSI ETSI TS 103 379 V1.1.1 (2017-01) 18 Figure 6.4-1: Connectivity Check Request Procedure The LC initiates the procedure by sending a CONNECTIVITY CHECK REQUEST message to the ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.4.2 CONNECTIVITY CHECK REQUEST | This message is sent by the LC in order to initiate a connectivity check with the LR. The parameter list contained in the message is as follows. Table 6.4-1 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, initiating message). Transaction ID M 7.31 Uniquely id... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.4.3 CONNECTIVITY CHECK RESPONSE | This message is sent by the LR in order to respond to a CONNECTIVITY CHECK REQUEST message from the LC. The parameter list contained in the message is as follows. ETSI ETSI TS 103 379 V1.1.1 (2017-01) 19 Table 6.4-2 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure c... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.5 LSRAI Notification procedure | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.5.1 General | The purpose of the LSRAI Notification procedure is to enable the LR to convey LSRAI to the LC. Figure 6.5-1: LSRAI Notification Procedure The LR initiates the procedure by sending a LSRAI NOTIFICATION message to the LC. Upon receiving the LSRAI NOTIFICATION message, the LC shall check the contents of the message, store... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.5.2 LSRAI NOTIFICATION | This message is sent by the LR in order to convey LSRAI to the LC. The parameter list contained in the message is as follows. Table 6.5-1 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, initiating message). Transaction ID M 7.31 Uniquely identifies the transa... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.5.3 LSRAI NOTIFICATION ACK | This message is sent by the LC in order to respond to a LSRAI NOTIFICATION message from the LR. The parameter list contained in the message is as follows. Table 6.5-2 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, response message). Transaction ID M 7.31 Uni... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.6 LSRAI Request procedure | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.6.1 General | The purpose of the LSRAI Request procedure is to enable the LC to request the LR to convey LSRAI. ETSI ETSI TS 103 379 V1.1.1 (2017-01) 21 Figure 6.6-1: LSRAI Request procedure The LC initiates the procedure by sending a LSRAI REQUEST message to the LR. Upon receiving the LSRAI REQUEST message, the LR shall check the c... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.6.2 LSRAI REQUEST | This message is sent by the LC in order to request LSRAI from the LR. The parameter list contained in the message is as follows. Table 6.6-1 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, initiating message). Transaction ID M 7.31 Uniquely identifies the tra... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.6.3 LSRAI RESPONSE | This message is sent by the LR in order to respond to a LSRAI REQUEST message from the LC. The parameter list contained in the message is as follows. Table 6.6-2 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, response message). Transaction ID M 7.31 Uniquely... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.7 LSRAI Confirmation procedure | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.7.1 General | The purpose of the LSRAI Confirmation procedure is to enable the LC to notify the LR that configuration changes in the MFCN (if needed) have been applied according to previously received LSRAI. Figure 6.7-1: LSRAI Confirmation Procedure The LC initiates the procedure by sending a LSRAI CONFIRMATION REQUEST message to t... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.7.2 LSRAI CONFIRMATION REQUEST | This message is sent by the LC in order to notify the LR about processed configuration changes for a zone or zones. The parameter list contained in the message is as follows. Table 6.7-1 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, initiating message). Tra... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 6.7.3 LSRAI CONFIRMATION RESPONSE | This message is sent by the LR in order to respond to a LSRAI CONFIRMATION REQUEST message from the LC. The parameter list contained in the message is as follows. Table 6.7-2 Name Presence Type or reference Description Message Type M 7.30 Identifies the message type (procedure code, response message). Transaction ID M ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7 LSA1 Protocol: Information Elements | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.1 LSRAI | The LSRAI IE is used to convey zone descriptions (i.e. exclusion zones, restriction zones, protection zones). ETSI ETSI TS 103 379 V1.1.1 (2017-01) 24 Table 7.1-1 Name Presence Type or reference Description Number of zones M INTEGER (0.. 1 023) Identifies the number of zones N included in the LSRAI IE. If set to "0", i... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.2 Zone Description | The Zone Description IE contains information about the parameters of a zone. If the Zone Action IE is set to "Create", the Frequency, Radio Constraints, Space and Time IEs shall be included in the Zone Description IE, except in the case of exclusion zones (Zone Type IE set to "0"), for which the Radio Constraints IE sh... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.3 Zone Type | The Zone Type IE contains information about the zone type. Table 7.3-1 Name Presence Type or reference Description Zone Type M INTEGER (0..255) The following values shall be used: "0" - Exclusion Zone. "1" - Restriction Zone. "2" - Protection Zone. Other values are reserved for future use. ETSI ETSI TS 103 379 V1.1.1 (... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.4 Zone Action | The Zone Action IE contains information about the action to be performed on the zone. Table 7.4-1 Name Presence Type or reference Description Zone Action M INTEGER (0..7) The following values shall be used: "0" - Create (zone does not exist and is to be created). "1" - Modify (zone exists and some of its parameters are... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.5 Frequency | The Frequency IE contains information about the frequency span within which the zone constraints should be applied. Table 7.5-1 Name Presence Type or reference Description Lower frequency M 7.15 Zone applies to frequencies above the signalled value. Upper frequency M 7.15 Zone applies to frequencies below the signalled... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.6 Radio Constraints | |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.6.1 Introduction | The Radio Constraints IE contains information on the radio constraints that need be satisfied by the MFCN, for a given zone. |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.6.2 Radio Constraints parameters | This clause describes the parameters that can be used to define radio constraints of a zone. Table 7.6-1 Name Presence Type or reference Description Radio Constraints Profile identifier M INTEGER (0..1 023) Uniquely identifies a Radio Constraints Profile. For each Radio Constraints Profile, a set of mandatory and optio... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.6.3 Radio Constraints profiles | This clause describes, for each Radio Constraints Profile, the set of parameters that are allowed. For a particular Zone, the Radio Constraints Profile identifier shall be consistent with the Zone Type IE, as specified for each identifier below. NOTE 1: The precise usage of a radio constraints parameter, for a given Ra... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.7 Space | The Space IE contains information about the space parameters of a zone. Only one of the options in table 7.7-1 may be present in a particular instance of this IE. ETSI ETSI TS 103 379 V1.1.1 (2017-01) 27 Table 7.7-1 Name Presence Type or reference Description Circle O 7.11 Zone is to become operational within the defin... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.8 Time | The Time IE contains information about the time parameters of a zone. Only one of the options in table 7.8-1may be present in a particular instance of this IE. The Aperiodic IE shall be used for all cases of non-periodic operation, including simple start, stop or schedules (see details in clause 7.17). Table 7.8-1 Name... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.9 Synchronization Information | The Synchronization Information IE contains information about an ongoing synchronization process. Table 7.9-1 Name Presence Type or reference Description Sync ID M 7.36 Identifies the synchronization process. Sync Status M ENUMERATED (ongoing, last message) Indicates whether further procedures will be initiated for thi... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.10 Synchronization Ack Information | The Synchronization Ack Information IE contains acknowledgement information about an ongoing synchronization process. Table 7.10-1 Name Presence Type or reference Description Sync ID M 7.36 Identifies the synchronization process. Sync Zone List O 7.37 For each zone received as part of the synchronization process, inclu... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.11 Circle | The Circle IE contains the parameters defining a circle. NOTE: A Radius parameter set to 0 indicates that the zone consists of a single point whose location is specified by the Centre coordinates IE. ETSI ETSI TS 103 379 V1.1.1 (2017-01) 28 Table 7.11-1 Name Presence Type or reference Description Centre coordinates M |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.14 Geographical coordinates | . Radius M INTEGER (0..223-1) The relation between the value (N) and the radius (r) in meters it describes is 5N ≤ r < 5(N+1), except for N=223-1 for which the range is extended to include all greater values of (r). |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.12 Polygon | The Polygon IE contains the parameters defining a polygon. Table 7.12-1 Name Presence Type or reference Description Number of points M INTEGER (3..15) Identifies the number N of points in the polygon Point 1 M 7.14 Geographical coordinates Point 2 M 7.14 Geographical coordinates Point 3 M 7.14 Geographical coordinates ... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.13 Area Descriptor | The Area Descriptor IE contains text strings that may be interpreted as identifying an area (e.g. postcodes). Table 7.13-1 Name Presence Type or reference Description Number of strings M INTEGER (1..1 000) Identifies the number N of text strings in the Area Descriptor String 1 M PrintableString(SIZE(1..150)) Text strin... |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.15 Frequency value | The Frequency Value IE contains a frequency value. Table 7.15-1 Name Presence Type or reference Description Frequency value M INTEGER (0..100 000) The IE value (N) is derived from the following formula: F = (N/10) Where F is the frequency in MHz |
215933479751513f1e1cea9999cc3ad9 | 103 379 | 7.16 Periodic | The Periodic IE contains the times when a zone is to be operational within a period (day/week/month/year). Table 7.16-1 Name Presence Type or reference Description CHOICE Period Length M >Day >>Day schedule M 7.19 One day schedule to be repeated every 24 hours >Week >>Week schedule M 7.20 One week schedule to be repeat... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.