hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.2.2 Bearer handover/replacement information | The provisions of EN 300 444 (GAP) [9], clause 10.3.4 shall apply. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.2.3 Other bearer position | The RFP is recommended to broadcast the "other bearer" information indicating the position of a 2nd dummy bearer or traffic bearer, if such bearer exists. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.2.4 Recommended other bearer position | The RFP is recommended to broadcast the "recommended other bearer" information indicating the position of another bearer. This message shall not be sent unless the bearer that it is sent on will be released in less than or equal to 4 multiframes. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.2.5 Dummy or C/L bearer position | The RFP shall announce the dummy bearer position, if a dummy bearer exists. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.2.6 C/L bearer position | The RFP shall announce the connectionless downlink bearer position, if such a bearer exists. The bearer position shall be announced 1 Multi-Frame (4 MF in case of low duty cycle) in advance of transmission of C/L data via this bearer. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.2.7 RFP-status and Modulation Types | The RFP should send the RFP-status information "RFP busy-for-data/not-busy-for-data" as soon as possible after a detection of a change in RFP-status, i.e. in the first allowed frame after the change. It is recommended that the RFP periodically sends the RFP-status information. It is not recommended to send this message... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.2.8 Blind slot information for packet mode service | The RFP shall announce the slots which are blocked for packet mode service. The coding of the message is identical to clause 10.4.2.1 Blind slot information for circuit mode service, except that the MAC layer information type bits are coded as '1111'B ('0F'H). ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 65 ULE PPs shall us... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.3 Paging Procedures | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.3.1 LCE Paging | The procedure shall be performed as defined by EN 300 175-3 [3], clauses 9.1.3.1 and 9.1.3.2.2. This procedure includes transmission and reception of Zero length, short and full page messages. In the LCE procedure, the BS channel SDU is provided by the DLC layer. The procedure is compatible with normal, high and low du... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.4 Paging detection | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.4.1 Normal duty cycle | The procedure shall be performed as defined by EN 300 175-3 [3], clause 9.1.3.2.1. The PT shall be in the state "Normal Idle Locked mode" as defined in EN 300 175-3 [3], clause 11.3.3.1. In this mode, the PT shall receive any BS channel transmitted in frame 0 and additional frames that are commanded by the extend flag.... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.5 ULE Dummy Bearer Procedures | The following procedures shall be performed as defined in EN 300 175-3 [3], clause 9.5. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.5.1 NS channel | The FT shall send the NS message in all frames where a ULE Dummy Bearer is active and the PT shall be capable of receiving and processing the NS split identities message as defined in EN 300 175-3 [3], clause 7.3.5. This message contains the RFPI of the RFP constructed in an identical manner to the information sent in ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.5.2 QC channel | The FT shall send the QC message in all frames where a ULE Dummy Bearer is active and the PT shall be capable of receiving and processing the QC compound system information message as defined in EN 300 175-3 [3], clause 7.3.5. This message contains information constructed in an identical manner to the information sent ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.5.3 MU channel | The FT shall send one MU message in every frame where a ULE Dummy Bearer is active and the PT shall be capable of receiving and processing the MU ULE MAC control channel message as defined in EN 300 175-3 [3], clause 7.3.5. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 66 The message contains MAC layer information specific t... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.5.4 Reception of Messages | DECT ULE PTs are not required to listen for NS, QC or MU messages at any mandated rate, the PTs will listen when there is a requirement for the PT to gain lock to a specific FT at which point the NS, QC and MU messages shall be collected and the information understood to enable the PT to lock to the desired FT. All the... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.5.5 Operation in unlocked mode | Operation in unlocked mode refers to the operation mode when the PP losses the locked state to the RFP during idle time. The PP shall be capable to get synchronization again to the RFP, when required, by using the information provided in the channels NS and QC. The PP shall be capable to react properly to a possible ch... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.6 ULE Paging Procedures | This clause refers to ULE specific paging capability using B-Field channels over the ULE dummy bearer. Refer to clause 10.4 for LCE paging using A-field tail. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.6.1 PU Paging Message Formats | The FT and PT shall support the ULE Dummy Bearer paging format as defined in EN 300 175-3 [3], clause 7.3.5. The FT shall send a PU message in all frames where a ULE Dummy Bearer is active and the PT shall be capable of receiving and processing the PU ULE Paging channel message. The message contains information specifi... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.6.1.1 PU Message General format | The PU Message is spread across two fields of the ULE Dummy Bearer, one field of 44 bits and one field of 56 bits as shown below, the 44 bit field is subdivided into a control field (comprised of the SFa, SFb and CA mask fields) and a data field, the 56 bit field is solely a data field. 44 bit field 56 bit field Contro... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.6.2 Paging Descriptors for ULE Paging | The ULE Dummy Bearer paging channels (BU channel and PU channel) are used to pass transient information from the FT to the PT. As described in the present document, clause 10.6.1.1 the meaning of the information passed is given to the PTs by the FT using the << ULE-MAC-CONFIGURATION-INFO >> information element in highe... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7 Connection Management | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.1 Logical Connection Setup | Logical Connection Setup is the procedure of creation of MBC. Depending on the procedure, it may be immediately followed by a Physical connection setup or not. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.1.1 ULE logical connection setup - explicit procedure | The creation of an MBC shall be performed as described in EN 300 175-3 [3], clause 10.2.4.1, with the following specific provisions: • Connection shall be advanced, full slot; • ECN number shall be set to "7". The connections created with this ECN shall be "Expedited" as defined in EN 300 175-3 [3], clause 10.2.5. Init... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.1.2 ULE logical connection setup - procedure for ancillary connections | The creation of an MBC for an ancillary connection, such as the required by the feature [ULE1-N.2] (Service Call) is done as described in EN 300 175-3 [3], clause 10.2.4, with the following specific provisions: • Connection shall be basic, full slot. Therefore the procedure is identical to the one used in GAP (EN 300 4... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.1.3 ULE logical connection setup - implicit procedure | It is possible to create a pair of MBCs for the ULE connection without any exchange of air interface messages by means of the mechanism described in clause 12.1.3.1.2.2, case b). In order to do that, another MBC, generally associated to a circuit mode service, should exist in order to transport the NWK layer messages. ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.2 Logical Connection Release | Logical Connection Release is the procedure of removal of an MBC. This procedure is preceded by either a NWK layer release procedure, by a NWK layer suspend procedure or by a handshake failure. The NWK layer release procedure and the NWK layer suspend procedure will cause DLC layer to send a MAC_DIS- req primitive to M... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.2.1 ULE logical connection release - explicit procedure | The following procedure shall be performed: • If the connection was active, the procedure A-field connection/bearer release as defined in clause 10.9.3 shall be executed. NOTE: It is assumed that a NWK layer RELEASE procedure has been previously executed between both peers in order to release the logical connection. • ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.2.2 ULE logical connection release - procedure for ancillary connections | This procedure shall be used to release the MBC for an ancillary basic connection, such as the required by the feature [ULE1-N.2] (Service Call). The same procedure described in EN 300 444 (GAP) [9], clause 10.5 shall be performed. The procedure releases at the same time the bearer and the connection. NOTE: An ancillar... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.2.3 ULE logical connection release - implicit procedure | The execution of the NWK layer procedure "NWK suspend" as described in clause 12.1.3.2, when the NWK messages are carried by a different MBC to the one associated to the CC entity, and when the associated MBC is in "MAC suspend" state, causes the release of the MBC at both peers without any further signalling operation... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.2.4 ULE logical connection release - abnormal procedure | Abnormal release of the connection at all levels may also be done by the Management Entity as result of failure of stay- alive procedures. In such a case, the procedure is implicit and there is no exchange of air i/f messages. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.3 Connection Suspend and Resume | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.3.1 General | The suspend/resume process used in ULE in entirely handled at MAC layer and under control by the Management Entity in response to instantaneous traffic need. The suspend/resume process is the DECT packet handling mechanism over the MAC C/O service. The suspend/resume process happens at an imaginary in between the MAC T... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.3.2 Suspend | Suspend is defined as the process of releasing the physical connection without releasing the logical connection. Therefore in suspend state: • There are not physical bearers active at the physical layer • There is not active TBC entity • There is a MBC associated to the connection • All higher layer entities (DLC and a... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.3.2.1 Entering in suspended state | A connection enters in suspend state by releasing its bearer at MAC layer without an explicit process of connection release. The previous principle applies independently of the process for the bearer release, that may be normal (as described in clause 10.9), expedited (as describe in clause 10.10) or even due to errors... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.3.3 Resume | Resume is the process of activating the physical layer for an existing connection in suspended state. A connection is resumed state behaves as a normal DECT connection and includes at least a TBC entity. However the connection is still identified as packet-mode at MBC level, which would trigger the proper action at MBC... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.3.3.1 Resuming a suspended connection | For devices compliant with the present document the resume process is performed by executing a bearer setup process with any of the following two options: • Any Advanced connection setup (as described in clause 10.9) with the ECN number belonging to an existing suspended connection between the PT - FT pair. NOTE 1: The... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.4 Other Connection Modification | The following additional connection modification procedures (other than suspend and resume) may be supported by ULE devices. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.4.1 Void | 10.7.4.2 Connection modification to change service type, slot type, modulation type or adaptive code rate |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.4.2.1 Connection modification to change MAC service type | The MAC connection modification procedure to change the service type is needed to change the actual service type of a logical connection to a new one due to the result of the NWK service negotiation defined by clause 12.5 or service changes defined in clauses 12.6 and 12.7. The connection modification procedure to chan... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.4.2.2 Connection modification to change slot type | The MAC connection modification procedure to change the slot type is needed to change the slot type of a logical connection to a new one due to the result of the NWK service negotiation defined by clause 12.5 or service changes defined in clauses 12.6 and 12.7. The connection modification procedure is in charge to chan... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.4.2.3 Connection modification to change maximum MAC packet lifetime | The MAC connection modification procedure to change the maximum MAC packet lifetime is needed to change this parameter which influences the IP_error_correct operation. The following provisions shall apply: The connection modification procedure to change the maximum MAC packet lifetime shall be performed as defined by E... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.7.4.2.5 Use of ATTRIBUTES_T.req/cfm in connection modification | This clause applies to all connection modification cases covered by clause 10.8.2. The ATTRIBUTES_T.req/cfm message as defined by EN 300 175-3 [3], clause 7.2.5.3.8 shall be used for connection modification to change service type and/or modulation scheme. The message shall be supported if any connection modification ca... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8 Other MAC control procedures | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.1 Quality control | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.1.1 RFPI handshake | RFPI handshake procedure shall be performed as defined in EN 300 175-3 [3], clause 11.5.1. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.1.2 PT frequency correction | PT frequency correction procedure shall be performed as defined in EN 300 175-3 [3], clause 11.5.2.2. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.1.3 Bearer quality report | Receiver side will send bits Q1 (or BCK) and Q2 reporting quality of received bearers. Report shall be done in bits a3 and a7 of a field in the reverse bearer of the duplex pair. The bit Q1 shall be set as defined in EN 300 175-3 [3], clause 10.8.1.3.4. The bit Q2 shall be set as described in EN 300 175-3 [3], clause 1... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.1.4 A-CRC handshake | When a TBC is in active connected state, if no correct A-CRC is received (in regard to the active FT identity) for a time equal to maximum MAC packet lifetime, the bearer shall be released. The abnormal expedited release procedure (clause 10.10.3.6) shall be used in this case. NOTE: The normal reaction on the release o... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.2 Physical channel selection | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.2.1 Channel selection for the ULE packet data connection | The ULE specific channel selection mechanisms, as described in clause 9.2, shall be used for the channel selection of the ULE packet data connection (MBC resume procedure), except in the exceptional cases listed in clause 10.8.2.2. Such channel selection procedures, combined with expedited setup procedures (clause 10.1... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.2.2 Exceptional cases | Regular DECT channel selection procedures (as described in EN 300 175-5 [5], clause 11.4) may only be used for channel selection for the ULE packet data connection, on an exceptional basis, in the following cases: • In the initial setup of the connection, when explicit procedures are used (see clause 10.7.7.1.1). • Whe... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.2.3 Channel selection for the Service Call and other circuit mode connections | The setup of the Service Call (feature [ULE1-N.2]), or other circuit-mode connections that may exist in the system, shall be done using regular DECT channel selection procedures as described in EN 300 175-5 [5], clause 11.4. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.3 A-field MAC Bearer replacement procedure (MT) | The PT shall be able to perform bearer replacement, by setting up new TBCs within the same logical connection. The following rules shall apply: • The bearer replacement shall be always implemented by dropping the existing bearer before establishing the new one. • There should not be more than one bearer over the air at... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.4 Dummy bearer replacement procedure | The FT shall be able to control the quality and to move the position of the dummy bearer as response to quality issues. The following rules shall be followed. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.4.1 Quality control | The FT shall be able to periodically measure the background RSSI level on the dummy bearer channel. To do that, it is allowed to interrupt the transmission of the dummy bearer from time to time. This interruption of transmission has some implications on system operation: • A ULE PP device might try to lock to the FP on... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.8.4.2 Requirements | • The bearer replacement shall consist of raising a new dummy bearer on a new channel, before releasing the old one. • The old dummy bearer shall be released latest four multiframes after raising the new replacement dummy bearer. • The number of physical channel changes for the dummy bearer shall not exceed 5 changes p... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.9 A-field (MT) Advanced Connection control procedures | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.9.1 General | A-field MAC advanced control procedures are used for the setup, release and handover of ULE connections. They may be used in any case (including initial setup, resume, suspend and complete release), however expedited operations (clause 10.10) are assumed to be normally used in suspend and resume by efficiency reasons. ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.9.2 PT initiated A-field advanced bearer setup | The connection setup procedure shall be performed as defined in EN 300 175-3 [3], clauses 10.2.4.1 and 10.2.4.2 or 10.2.4.3. The connection setup procedure described in EN 300 175-3 [3], clause 10.2.4.2 shall be used in the following cases: • PT initiated setup (all cases). • FT initiated indirect setup (via paging). T... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.9.2.1 MT access request message | The following fields as defined in EN 300 175-3 [3], clause 7.2.5.3 of in the MAC control (MT) message shall be supported by the PT and the FT. Table 34: Values used within MT message MAC message Field within the message Standard values within the MAC message Normative action/comment <<MT message>> <MT header> 1 "Advan... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.9.2.2 MT Attributes_T.req/cfm message | The following fields as defined in EN 300 175-3 [3], clause 7.2.5.3.8 of the ATTRIBUTES_T.req/cfm messages shall be supported by the PT and the FT. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 77 Table 35: Values used within ATTRIBUTES_T.req/cfm messages MAC message Field within the message Standard values within the MAC me... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.9.3 A-field connection/bearer release | The procedure shall be performed as defined in EN 300 175-3 [3], clauses 10.4 and 10.7.2.1. The procedure may be used if the connection is either, basic or advanced. The proper value shall be inserted in the MT header. PT FT MAC-DIS.Ind MAC-DIS.Req RELEASE RELEASE Figure 7: Bearer release ETSI ETSI TS 102 939-1 V1.1.1 ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.9.3.1 MT message | The following fields as defined in EN 300 175-3 [3], clause 7.2.5.2 in the MAC control (MT) message shall be supported by the PT and the FT. Table 36: Values used within MT message MAC message Field within the message Standard values within the MAC message Normative action/comment <<MT message>> <MT header> 0 Basic con... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.9.4 A-field bearer handover request | The procedure shall be performed as defined in EN 300 175-3 [3], clauses 10.6.2 and 10.5.1.1. The procedure is equivalent for intra- and inter-cell handover. The procedure may be used if the connection is either, basic or advanced. The proper value for the MT header shall be used. The FT should not release the old bear... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.9.4.1 MT message | The following fields as defined in EN 300 175-3 [3], clause 7.2.5.2 in the MAC control (MT) message shall be supported by the PT and the FT. Table 37: Values used within MT message MAC message Field within the message Standard values within the MAC message Normative action/comment <<MT message>> <MT header> 1 "Advanced... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.9.5 A-field connection handover request | The procedure shall be performed as defined in EN 300 175-3 [3], clauses 10.2.4.2 and 10.5.1.1. The procedure may be used if the connection is either, basic or advanced. The proper value for the MT header shall be used. The procedure is equivalent for intra- and inter-cell handover. ETSI ETSI TS 102 939-1 V1.1.1 (2013-... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.9.5.1 MT message | The following fields as defined in EN 300 175-3 [3], clause 7.2.5.2 in the MAC control (MT) message shall be supported by the PT and the FT. Table 38: Values used within MT message MAC message Field within the message Standard values within the MAC message Normative action/comment <<MT message>> <MT header> 1 "Advanced... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.2.1 Supported MT messages | The PT and FT shall support the following MT advanced control messages from the Advanced connection control part 2 set (see EN 300 175-3 [3], clauses 7.2.5.12.1 and 7.2.5.12.2): • "Expedited Access Request" (command "0000"B) • "Expedited Access Request ready for release" (command "0001"B) • "Null or GFA channel transmi... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.2.2 GFA transmission | The PT and FT shall include a GFA message indicating last valid DLC RN (positive ACK) in all transmissions of "expedited release" and "ready for release" messages. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.2.3 Reason codes in "expedited release" and "ready for release" messages | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.2.3.1 Reason codes in "expedited release" message | The following reason codes shall be supported by both peers in the "expedited release" message Table 39: Supported "reason codes" in "expedited release" message Reason code Meaning Info field a22 a23 a24 a25 a26 a27 0 0 0 0 0 1 Normal bearer release (see note 1) Not used, note 9 0 0 1 0 1 0 base station busy (see note ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.2.3.2 Reason codes in "ready for release" message | The following reason codes shall be supported by both peers in the "ready for release" message. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 81 Table 40: Supported "reason codes" in "ready for release" message Reason code Meaning Info field a22 a23 a24 a25 a26 a27 0 0 0 0 0 1 Normal bearer release (see note 1) Not used, not... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.2.4 Operation codes in "Null or GFAchannel transmission" message | The following operation code shall be supported by both peers in the "Null or GFAchannel transmission" message • "01"B: GFAchannel NOTE: See EN 300 175-3 [3], clause 7.2.5.12.5. 10.10.3 Expedited procedures The following expedited procedures shall be supported. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.3.1 Procedure for Single-burst setup and release | The PT and FT shall support the Procedure for Single-burst setup and release as defined by EN 300 175-3 [3], clause 10.5.1.8.2. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.3.2 Procedure for Multi-burst setup | The PT and FT shall support the Procedure for Multi-burst setup as defined by EN 300 175-3 [3], clause 10.5.1.8.3, including the modification single-burst setup > Multi burst setup and the FT response table defined by EN 300 175-3 [3], clauses 10.5.1.8.3.2 and 10.5.1.8.3.3. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 82 |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.3.3 Announcement "Ready for Release" | The PT and FT shall support the Procedure for announcement "Ready for Release" as defined by EN 300 175-3 [3], clause 10.5.1.8.4, including the protection as defined by EN 300 175-3 [3], clause 10.5.1.8.4.1. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.3.4 General Expedited Release procedure | The PT and FT shall support the General Expedited Release procedure as defined by EN 300 175-3 [3], clause 10.7.3.2. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.3.5 Single-message expedited release procedure | The PT and FT shall support the Single-message expedited release procedure as defined by EN 300 175-3 [3], clause 10.7.3.3.1. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.3.6 Abnormal expedited release procedure | The PT and FT shall support the Abnormal expedited release procedure as defined by EN 300 175-3 [3], clause 10.7.3.3.2. 10.10.4 Expedited procedures use cases |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.1 General use cases | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.1.1 Single Packet Data Transfer - Success | Description: • Single-packet Data Transfer is designed to be as fast and simple as possible. It can even contain no data at all, and serve as a data pull request (PP->FP) only. • Single-packet Data Transfer will normally be preceded by a regular advanced connection which has negotiated service and slot type, and which ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.1.2 Single Packet Data Transfer: error/abnormal cases | 10.10.4.1.2.1 Error in B-field CRC Description: • MAC signalling procedure is OK (A-field received and message decoded),), but due to a corrupted B-field the IP packet has not been received. • In this case, the PP should understood that the packet has not been accepted and should try to retransmit it. • The bearer is r... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.1.3 Multi Packet Data Transfer | Description: • Multi-packet Data Transfer will normally be preceded by a regular advanced connection which has negotiated service and slot type, and which has been suspended before. By default the multi-packet data transfer uses IP error correct MAC service, single subfield protection, and full slot. The first messages... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.2 C-plane related use cases | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.2.1 Multi Packet Data Transfer: FP requested C-plane traffic only - Success | Description: • FP requested setup to execute a C-plane procedure. • In the example, there is C-plane traffic only. - For practical purposes, it may be assumed that the C-plane operation requested by the FP is an MM authentication. RFP PP access_request release (no B-field) Bearer_confirm (Q2=1, Q1 = 0, BA=IP1) ready_fo... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.3 Stay alive related use cases | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.3.1 PT initiated stay alive with transmission of GFA from FT | Description: • Stay alive handshake designed as a short single-burst transfer process, but without U-plane. Successfully handshake requires correct reception of release with Q2=1 and any of the following reason codes in the release message: • Normal bearer release. • Stay in higher paging detection mode (paging mode an... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.3.3 PT initiated stay alive - the FT changes the procedure to send U-plane data | Description: • It starts as a stay alive. The FP decides to keep the bearer changing the procedure to multi-burst. This is done by replying "bearer confirm" to the setup. The procedure continues as a multi-burst transfer. • It also qualifies as a handshake. The reception of the "bearer confirm" makes the handshake succ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.4 Failure and Retransmission Use cases | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.4.1 Setup Failure and Retransmission Examples | This clause shows some scenarios where the packet mode connection setup fails, and where re-transmission is applied. The BA header codes and Q bit settings are omitted mostly for clarity reasons. In the examples below the red lightning indicates that the message was not received error free. 10.10.4.4.1.1 Error in acces... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.4.2 Release Failure and Retransmission Examples | 10.10.4.4.2.1 Error in the "release" message Description: • This flowchart shows a single two-way packet transfer, were the first release message is not received. As this is a 'multi packet data transfer', and this release message is the 3rd message, the packet mode connection is considered to be failed. The FP starts ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.4.3 Errors when in TBC "connected" state | 10.10.4.4.3.1 Retransmission abandoned and abnormal release of the TBC due to multiple errors Description • This flowchart shows how data retransmission is abandoned when the data is not going for 3 re-transmissions. RFP PP access_request (BA=IP1) confirm (Q2=1, BA=IP1) ready_for_release (Q2=1, BA=IP0) ready_for_releas... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.4.4.5 Errors in release procedures | 10.10.4.4.5.1 Multiple errors in release: abandoned release retransmission General remark: • In any case one should bear in mind that these are all exceptional error cases only. Figure 38 shows release retransmission: Figure 38: Multi Packet Data Transfer - Abandoned release retransmission (option 1) The above mechanis... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.5.1 Use of reason code "normal bearer release" | This is the normal situation at the end of a ULE packet transaction, the release reason is "normal bearer release" which instructs the PT to return to Idle. This reason code shall be used by both, the FT and the PT, unless there is a reason for using any other code. RFP PP access_request (Q2=0, BA=IP1) bearer_confirm (... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.5.2 Use of reason code "base station busy" | The release reason "base station busy" indicates that the RFP is too busy to continue handling the connection with PT. Oppositely to the reason code "Setup again after n frames", no explicit action is mandated. It is expected that the PT will retry the access (including new channel selection process) after a timer. The... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.5.3 Use of reason code "unacceptable PMID / Unregistered PMID" | The release reason "unacceptable PMID / Unregistered PMID" is used to indicate to the PT that the PT is not registered in the RFP. This can be the result of an abnormal situation, such as reset of the RFP. The expected response shall be the PT to execute Mobility Management procedures in order to register again the PT ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.5.4 Use of reason code "switch to circuit mode" | The release reason "switch to circuit mode" is used to request to the PT that a circuit mode connection should be started. The requested circuit mode service is indicated by the info field as shown in table 41. In figure 48, the PT behaviour at the end of the ULE service call is shown as returning to idle but the actua... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.5.5 Use of reason code "Stay in LCE paging detection mode" | The release reason "stay in LCE paging detection mode" is used to instruct the PT to enter a mode where it can listen for LCE paging. Being able to respond to LCE paging lets the FT initiate circuit mode transactions, the example given here is of deregistration of a ULE node. Both, normal and fast LCE paging may be sup... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.10.5.6 Use of reason code "Stay in higher paging detection mode" | The release reason "stay on higher paging detection mode" is used to cause the PT to stay listening for a ULE page message with a different paging cycle from the standard one. This feature is used in slow paging cycle devices, such as PP type 1 (sensors), when the FT may have the need to send data to such PP sooner tha... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.