hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.2 Relocation involving 2 SGSNs | |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.2.1 Preparation | In this phase the UTRAN reserves resources for the relocation. Then the source SGSN and source RNC are informed when the target RNC is ready. The GGSN is also instructed to start bi-casting downlink N-PDUs as part of the Relocation preparation process. As an implementation choice in the SGSN, this can happen in paralle... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.2.2 Bi-casting of DL flow and switching of UL flow | In this phase, DL traffic is bi-casted from the GGSN to the target RNC (as well as to the source RNC). Also at this point in both the hard handover and SRNS relocation cases, the UE sends UL traffic to the target RNC and UL traffic needs to be switched to the target SGSN and GGSN, using the new route.
Figure 14: Contro... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.2.3 Completion | This is the completion of the signalling. Also, the GGSN is instructed to stop bi-casting downlink N-PDUs. At this stage, the relocation has effectively already been completed. Note that SGSN2 informs SGSN1 that the relocation is complete once all of the GGSNs involved have stopped the bi-casting. Then it informs SGSN1... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.3 Relocation involving only one SGSN | In the case that the relocation involves only one SGSN, the flow of N-PDUs across the Gn interface does not need to be changed. Indeed, the tunnel switching point in the SGSN can serve as the anchor for the tunnel instead of the GGSN as proposed above.
Figure 19: Packet flows during relocation with only one SGSN invol... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.3.1 Preparation | In this phase the UTRAN reserves resources for the relocation. Then the source SGSN and source RNC are informed when the target RNC is ready. The SGSN starts bi-casting downlink N-PDUs as part of the Relocation preparation process.
Figure 20: Control Plane – Preparation phase with only one SGSN
Handling of abnormal con... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.3.2 Bi-casting of DL flow and switching of UL flow | In this phase, DL traffic is bi-casted from the SGSN to the target RNC (as well as to the source RNC). Also at this point in both the hard handover and SRNS relocation cases, the UE sends UL traffic to the target RNC and UL traffic needs to be switched to the SGSN and using the new route.
Figure 23: Control Plane - Bi-... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.3.3 Completion | This is the completion of the signalling. Also, the SGSN is instructed to stop bi-casting downlink N-PDUs. At this stage, the relocation has effectively already been completed.
Figure 26: Control Plane – Completion phase with only one SGSN
Handling of abnormal conditions in the Completion phase:
If the RELOCATION DETEC... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.4 Specifications Impact | |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.4.1 Impacts on RAN3 specifications | Solution 2 does not require any new procedures or messages to be introduced to any RAN 3 specification.
In R99, there is a clear indication in the RAB parameters used at RAB assignment that a RAB is to be treated in a “lossless” or “other” way. Therefore a new value for that Information Element is needed to indicate “s... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.4.2 Impacts on other groups’ specifications | The impacts to other groups' specifications relate to inclusion of bi-casting from GGSN to the Gn interface specification and corresponding stage 2 specifications.
Procedures to initialise and terminate the GGSN bicasting from SGSN including error cases needs to be defined by TSG CN WG4.
29.060 example changes:
The Bi-... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.5 Interaction with other systems | The Core Network bi-casting solution will work with a GERAN connected via the Iu-PS in exactly the same way as with a UTRAN connected via the Iu-PS. Therefore all the description above is applicable to GERAN, with the RNC being replaced by a BSS (can contain BSCs or not). There is no other functionality required at the... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.6 Summary: solution 2 | In the Core Network bi-casting solution, handling of the real time data is done at the GGSN. Real time support requires that the GGSN is able to bi-cast the DL traffic to the target RNC. In the case of relocation involving only one SGSN, the SGSN may perform the bi-casting without involving the GGSN.
In any relocation ... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.7 Open issues | |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 7 Open items for all solutions | Real time PDCP numbers are a RAN2 issue that has not been resolved yet. The questions to be solved with R2 include whether the RAB contexts (i.e. the sequence numbers) need to be between RNCs or not, and whether the header compression/stripping solution to be selected allows that transmission to UE continues via the Iu... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 8 Comparison of the solutions | Both solutions meet the requirements defined in this TR. In addition, the following differences are pointed out:
Solution 1 (SRNC duplication)
Solution 2 (Core Network Bi-casting)
For a rel4 UTRAN, user data path between RNCs is same as in lossless relocation for R99
User data path for real-time is different from user ... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 9 Agreements | Solution 1 has been agreed for handling relocation for real time services from PS domain Rel 4.
Annex A (informative):
Change History
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
03/2001
11
RP-010132
-
-
Approved at TSG RAN #11 and placed under Change Control
2.0.0
4.0.0
12/2001
14
-
-
-
Formatting... |
dc7f93eeb005e644aa8f154545a30461 | 29.198-04 | 1 Scope | The present document is Part 4 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The ... |
dc7f93eeb005e644aa8f154545a30461 | 29.198-04 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
dc7f93eeb005e644aa8f154545a30461 | 29.198-04 | 3 Definitions and abbreviations | |
dc7f93eeb005e644aa8f154545a30461 | 29.198-04 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 29.198-1 [1] apply. |
dc7f93eeb005e644aa8f154545a30461 | 29.198-04 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 29.198-1 [1] apply.
4 Call Control SCF
Two flavours of Call Control (CC) APIs have been included in 3GPP Release 4. These are the Generic Call Control (GCC) and the Multi-Party Call Control (MPCC). The GCC is the same API as was already present in ... |
dc7f93eeb005e644aa8f154545a30461 | 29.198-04 | 4.1 Call Model Description | The adopted call model has the following objects.
• a call object. A call is a relation between a number of parties. The call object relates to the entire call view from the application. E.g., the entire call will be released when a release is called on the call. Note that different applications can have different view... |
dc7f93eeb005e644aa8f154545a30461 | 29.198-04 | 4.2 General requirements on support of methods | An implementation of this API which supports or implements a method described in the present document, shall support or implement the functionality described for that method, for at least one valid set of values for the parameters of that method.
Where a method is not supported by an implementation of a Service interfa... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 1 Scope | The present document deals with the procedures allowing the technical realization of the real time end‑to‑end facsimile group 3 service within the GSM PLMN using non‑transparent network support according to the definition of the Teleservices 61 and 62 specified in GSM 02.03. Within the present document particular atten... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 2.1 Abbreviations | In addition to those below abbreviations used in the present document are listed in GSM 01.04.
BCS Binary coded signalling
CCT Circuit(s)
I/F Interface
RA1,RA1',RA2 Rate adaptation functions
SREJ Selective reject
The abbreviations for the facsimile specific protocol elements and signals are listed in appendix I. |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 3 Service definition | The fixed network facsimile group 3 service, as basically defined in CCITT Recommendation F.160, is an international telematic service for document transmission between two facsimile group 3 terminals.
The service specifications are comprised of two parts:
‑ the control procedures described in CCITT Recommendation T.30... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 4 Network architecture | The network architecture applicable to this Teleservice is shown in figure 1/03.46 below.
: ╔════════╗ :
: ║ ║ :
:─╢ PLMN ╟─:
: ║ ║ :
: ╚════════╝ :
v v : ╔════════╗ :
╔═════╗ ┌──────┐ │ │ ┌───────┐ ┌───────┐ : ║ ║ : ╔═════╗
║ FAX ╟─┤ MT ├─┘ └─┤ BSS ├─┤MSC/IWF├─:─╢ PSTN ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 5 Reference configuration at the mobile station | The mobile station reference configurations described in this clause are defined as per GSM 04.02.
<----------------- Mobile station ----------------->
╔═══════╗ 2-w ┌───────────┐ R ┌─────┐ :
a) ║ FAX ╟──┼──┤FAX Adaptor├──╫───────────────┤ MT2 ├─╫
╚═══════╝ └───────────┘ : └───... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 5.1 Fax adaptor functionality | The fax adaptor block, figure 3/03.46, is intended to specifically complement the facsimile group 3 terminal in order to be able to communicate over a GSM PLMN.
╔═══════════════════╤═══════════════════╗
║ │ ║
║ Composite │ ║
║ Modem │ Contro... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 5.2 GSM facsimile machine functionality | The special GSM facsimile machine shown in the MS configuration of figure 2d/03.46 is similar to the digital part of the fax adaptor, but without any of the analogue portions.
It appears at the CCITT Recommendation V.24 interface as identical as the fax adaptor, i.e. the MT2 needs to have no knowledge of the particular... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6 Connection types | Table 1/03.46 shows the connection elements attributes applicable to these Teleservices, extracted from GSM 03.10.
Table 1/03.46: Connection elements
Protocol type
Access to TAF
Radio interface
Intermediate
BS‑MSC/IWF
of fig. 6
of the Mobile
connection element
rate
connection
GSM 03.10
Station
RA1 to RA2
element
Model ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.1 Protocol model | Figure 5/03.46 depicts the protocol model for this Teleservice, deduced from model 7 of figure 6/GSM 03.10.
It should be noted that depending on the particular implementation the R reference point may not explicitly exist. In this case the LAPB protocol and consequently the LAPB entities operating across this interface... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.2 Principles of the Facsimile Protocol Adaptation | The basic approach of the present document for facsimile group 3 is:
‑ to use the standard non‑transparent network support (including e.g. standard MT) as basically defined in technical specifications GSM 07.01, GSM 07.03, and GSM 09.07;
‑ to use the CCITT Recommendation T.30 procedure at both ends of the connection be... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.2.1 Fax Adaptor Protocol | To cater for the appropriate facsimile transmission some protocol elements and their use (procedure) are defined. These protocol elements are exchanged between both fax adaptors. They are defined as follows and are structured as outlined in annex A:
‑ BCS element:
The BCS element is used to relay CCITT Recommendation T... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.2.2 Interactions and interventions within the fax adaptors | Interactions and interventions within the fax adaptors are necessary:
‑ where protocol elements cannot be passed due to the differences between the PSTN and the GSM system;
‑ where the content of protocol elements has to be aligned with the capabilities of the supporting GSM PLMN;
‑ where BCS commands are repeated by t... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.2.3 Training Check | The training check sequence (TCF) as per CCITT Recommendation T.30 is exchanged only locally between the fax adaptor and the associated facsimile terminal. However, the subsequent exchange of CFR or FTT is, in principle, end‑to‑end. The training check sequence sent by the fax adaptor must have the minimum duration perm... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.2.4 Mobile to mobile calls | In this section, an interim solution is described. The final solution depends on the progress in the ITU‑T and is expected by the end of 1995.
To get the information about the nature of the call, a GSM specific country code inside the NSF frame is used to identify an inter MSC call.
The GSM country code (refer to CCITT... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.2.5 Facsimile Message Transfer | |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.2.5.1 Message Transcoding | To save transmission capacity at the radio interface the content of the document shall be transcoded. This applies only, when using the normal facsimile data transfer, i.e. not with the error correction mode.
The facsimile coded data received by the fax adaptor from the facsimile terminal is transcoded and transmitted ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.2.5.2 Generation of the normal data element | The normal facsimile coded data which have been transcoded and buffered as described in the present document is segmented for transmission across the radio interface into blocks of max. 936 bits (afterwards constituting a sequence of max. 5 L2RBOP PDUs). Each such block is contained in the information field of a normal... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.2.5.3 Generation of the error correction data element | The content of a FCD frame, if received correctly, is stored by the fax adaptor. Each such block is contained in the information field of a error correction data element of the FA protocol (see annex A).
The facsimile message transfer is finalized by a trailing end of data element which allows the transmitting fax adap... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.3 Procedure interrupts | Procedure interrupts are only supported in Teleservices 61; in case of Teleservice 62 any attempt to invoke procedure interrupts by MMI on the MT (see subclause 6.4 below) will have no effect. |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.4 Radio channel modification | This applies to Teleservice 61 only, if a change of the radio channel during the call swapping from speech to facsimile or vice versa is required. For this purpose the in‑call modification procedure (ICM) as detailed in GSM 04.08 is carried out.
The change from speech to facsimile is initiated by MMI at the MS as in o... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 6.5 Performance constraints | In order to perform the procedures described in the present document the MS and the IWF environment should be designed to be able to transmit and receive facsimile data continuously without any need to flow control the procedure by themselves. This applies specifically for the RLP, L2R, and the LAPB entities within the... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7 Use of terminal adaptation functions | According to the protocol model of the connection types (figure 5/03.46) there are two classes of TAFs to be considered. |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.1 Standard TAFs for synchronous services | The TAFs are those described in GSM 07.03 for synchronous bearer capabilities in the non‑transparent mode, i.e. presently for LAPB only. The rate adaptation functions shall comply with GSM 04.21. The interchange signalling mapping is in accordance with GSM 07.03. |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2 Specific TAFs for facsimile service | Integral part of an end‑to‑end connection for this Teleservice is the fax adaptor function, located at both the PLMN ends and in charge of:
‑ establishment and maintenance of a LAPB link between the fax adaptation function and the standard synchronous terminal adaptation function according to GSM 07.03, where applicabl... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.1 BCS phase | |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.1.1 BCS command/response procedures | The CCITT Recommendation T.30 procedure is segmented in sections of associated BCS commands and responses. Any command sent by a facsimile terminal must be answered by an appropriate BCS response (refer to Appendix III, CCITT Recommendation T.30). To guarantee that transmission and reception of responses take place rig... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.1.2 Compatibility checking | Some features cannot be supported in the GSM PLMN environment. The fax adaptor function is in charge of dealing with such compatibility checking which is carried out by monitoring certain BCS frames (DIS/DTC).
‑ Group 1 and group 2 equipments are not supported by the Teleservice as described in the present document.
‑ ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.1.3 Message speed checking | Although it is strongly recommended to use the maximum user rate of the MT2 (9 600 bit/s), a particular user may signal a lower user rate. In this case the fax adaptors have to carry out the following additional procedures:
‑ max speed indicated in the call set‑up message is 4 800 bit/s:
‑ if the fax adaptor receives a... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.1.4 Control of transmission rate | The controlling entity of the fax adaptor recognizes when a change of the transmission rate ‑ and in conjunction with this a change of the modem function ‑ has to commence. The transmission rate is then changed only locally, i.e. between the facsimile terminal and the fax adaptor at both the MSC/IWF and the MS ends.
Th... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.1.5 Clocking | The fax adaptor or the GSM facsimile machine will acquire received data bit timing on circuit 115 (according to CCITT Recommendation V.24). The transmitter element timing circuit 114 shall be synchronized to circuit 115.
The clock rate at the CCITT Recommendation V.24 interface will reflect the user rate of the MT2 as ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.2 Message phase | During the message phase (phase C of CCITT Recommendation T.30) a single bit pattern has to be detected, the EOL character (see subclause 4.1.2/CCITT Recommendation T.4), a unique code word that can never be found within a valid line of facsimile coded data, and is used, as per CCITT Recommendation T.4:
‑ to identify t... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.2.1 Normal facsimile data | The message phase (see figure II.6/GSM 03.46 and II.7/GSM 03.46, respectively) at both the PLMN ends is triggered by the transit of a frame (either the CFR or the MCF) sent by the receiving terminal to confirm a previous frame from the transmitting terminal, and marking the end of a BCS phase.
The terminal adaptation f... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.2.2 Error correction facsimile data | As these facsimile coded data between the fax adaptor and the facsimile terminal are structured in HDLC frames, the handling of this procedure segment will exploit such formatting. The content of such an HDLC frame is further on called a block.
Each such block is included in the information field of a error correction ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.2.3 Buffering of facsimile coded data | The following subclauses only apply, when using the normal facsimile data transfer, i.e. not with the error correction mode. |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.2.3.1 Transmitter adaptation function | In the transmitter adaptation function the facsimile coded data being received from the facsimile terminal are transcoded stripping of FILL information and written into the buffer.
If there is enough information available, this data is read out from the buffer, and a FA protocol element is generated which is processed ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.2.3.2 Receiver adaptation function | In the receiver adaptation function FILL information is transmitted to the facsimile terminal at the beginning of each page, if necessary, to bridge the gap between the training sequence and the real facsimile coded data. In case of normal fax data the FILL 0's can be expanded up to 5s only and therefore after these up... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.3 Disconnect procedure | The transmitter adaptation function, upon detection of the DCN frame (see CCITT Recommendation T.30) sent by the local terminal to indicate the end of the facsimile transmission, initiates the disconnect procedure. |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 7.2.4 Timeouts | The overall fax adaptation function is in principle bound to the timing constraints associated with the end‑to‑end CCITT Recommendation T.30 procedure. This means that, no matter of the reference configuration used at the mobile station, either the "standard" one (figure 2a/GSM 03.46) or the "GSM facsimile machine" (fi... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 8 Signalling aspects | GSM 07.03 identifies the bearer capability requirements to be supported by the terminal adaptation function in the MT (see GSM 07.01 for BC and HLC coding). The specific signalling requirements are those for "speech" and "facsimile group 3" or "facsimile group 3" only, respectively. The MT indicates in the call set up ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 8.1 Handling of tonal signals | Because the CCITT defined service uses modems, there are some signals received from the analogue link at the MSC/IWF and (where used) the fax adaptor which do not have a direct binary representation. These signals cannot therefore be passed across the radio interface in the same way as the CCITT Recommendation T.30 and... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 8.2 Call establishment | |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 8.2.1 Mobile terminated call | The PSTN facsimile group 3 terminal may be manually or automatically calling. |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 8.2.1.1 Speech then facsimile | Refer to the diagram in figure II.1a/03.46 and II.1b/03.46. In both of the figures the initial call setup is mobile terminated. In figure I.1a/03.46 the DCD is also mobile terminated (MT), while the DCD in figure I.1b/03.46 is mobile originated (MO).
In order to make the transition from the speech phase to the facsimil... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 8.2.1.2 Auto answer | Refer to diagram in figure II.2/GSM 03.46. A call received from the PSTN will cause the MT to turn on circuit 125 (according to CCITT Recommendation V.24) at the R interface.
In the case where a GSM facsimile machine is used, CCITT Recommendation V.25bis auto answering process is handled directly by turning on circuit ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 8.2.2 Mobile originated calls | The PSTN facsimile group 3 terminal may be manually or automatically answered. |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 8.2.2.1 Speech then facsimile | Refer to the diagram in figure II.3a/03.46 and figure II.3b/03.46. In both of the figures the initial call setup is mobile terminated. In figure II.3a/03.46 the DCD is also MO, while in figure II.3b/03.46 the DCD is MT.
In order to make the transition from the speech phase to the facsimile phase, the MODIFY command mus... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 8.2.2.2 Auto calling | Refer to diagram in figure II.4/GSM 03.46. The auto calling procedure of CCITT Recommendation V.25bis is initiated at the CCITT Recommendation V.24 interface. This is done either directly from the GSM facsimile machine or, in the case where a fax adaptor is used, by loop disconnect or DTMF dialling information between ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 8.2.2.3 Manual calling | Refer to diagram in figure II.5/GSM 03.46. When the call is answered, the RLP will be established across the radio interface providing circuit 108/2 in ON condition.
In the case where a fax adaptor is used, the mobile facsimile terminal must be connected to line by manual intervention at this stage, and will cause the ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 9 Interworking to fixed networks | PSTN and ISDN only are considered, both used as transit networks to complement the PLMN in the end‑to‑end connection between facsimile group 3 terminal, figure 7/GSM 03.46.
I W F
┌ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┐
:┌────────┐┌─────────┐ :
:│Protocol││ V.21 │ :
┌─────┐ :│Control ││... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 9.1 Interworking to PSTN | As the standard access of facsimile group 3 terminals for this Teleservice is a 2‑wire analogue interface, all the technical requirements for network interworking to PSTN are identical in principle to those encountered for the terminal connection to the MT. The key functional block is the fax adaptor described in claus... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 9.2 Interworking to ISDN | The use of 3.1 kHz audio bearer capability of ISDN allows for an interworking of PLMN very similar in practice to the scheme for PSTN, figure 7/GSM 03.46. The fax adaptor function is in conformance with the description given in clause 4 and subclause 7.1 of the present document.
Annex A (normative):
Structure and conte... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 1 Principle structure of an element | Each FA protocol element consists of the element discriminator (one single octet) and the optional information field (arbitrary length).
The elements are transmitted with octet 0, bit 1 first. Received information is forwarded with the same bit sequence as received.
octet: 0 1 ..... ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 2 Element discriminator coding | |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 2.1 BCS element | bit 8 7 6 5 4 3 2 1
┌───┬───┬───┬───┬───┬───┬───┬───┐
│ X │ 0 │ y │ y │ 0 │ 0 │ 0 │ 0 │
└───┴───┴───┴───┴───┴───┴───┴───┘
│ └──┬──┘
│ 0 1 = begin of a BCS frame
│ 1 0 = end of a BCS frame
│ 0 0 = middle of a BCS frame
│ 1 1 = entire BCS frame
0 = non-final frame
1 ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 2.2 BCS abort element | bit 8 7 6 5 4 3 2 1
┌───┬───┬───┬───┬───┬───┬───┬───┐
│ 1 │ 0 │ 1 │ 0 │ 0 │ 0 │ 0 │ 1 │
└───┴───┴───┴───┴───┴───┴───┴───┘
Figure A.3/03.46: Element discriminator of a BCS abort element |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 2.3 BCS transmit request element | bit 8 7 6 5 4 3 2 1
┌───┬───┬───┬───┬───┬───┬───┬───┐
│ 0 │ 1 │ 0 │ 0 │ 0 │ 0 │ 0 │ 1 │
└───┴───┴───┴───┴───┴───┴───┴───┘
Figure A.4/03.46: Element discriminator of a BCS transmit request element |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 2.4 Preamble element | bit 8 7 6 5 4 3 2 1
┌───┬───┬───┬───┬───┬───┬───┬───┐
│ 0 │ 1 │ 0 │ 0 │ 0 │ 0 │ 0 │ 0 │
└───┴───┴───┴───┴───┴───┴───┴───┘
Figure A.5/03.46: Element discriminator of a preamble element |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 2.5 Normal fax data element | bit 8 7 6 5 4 3 2 1
┌───┬───┬───┬───┬───┬───┬───┬───┐
│ 0 │ 1 │ 0 │ 0 │ 1 │ 0 │ 0 │ 0 │
└───┴───┴───┴───┴───┴───┴───┴───┘
Figure A.6/03.46: Element discriminator of a normal fax data element |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 2.6 Error correction fax data element | bit 8 7 6 5 4 3 2 1
┌───┬───┬───┬───┬───┬───┬───┬───┐
│ 0 │ 1 │ 0 │ 0 │ 1 │ 0 │ 0 │ 1 │
└───┴───┴───┴───┴───┴───┴───┴───┘
Figure A.7/03.46: Element discriminator of an error correction fax data element |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 2.7 End of data element | bit 8 7 6 5 4 3 2 1
┌───┬───┬───┬───┬───┬───┬───┬───┐
│ 0 │ 1 │ 0 │ 0 │ 1 │ 0 │ 1 │ 0 │
└───┴───┴───┴───┴───┴───┴───┴───┘
Figure A.8/03.46: Element discriminator of an end of data element |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 2.8 TCF element | bit 8 7 6 5 4 3 2 1
┌───┬───┬───┬───┬───┬───┬───┬───┐
│ 1 │ 0 │ 0 │ 1 │ 0 │ 0 │ 0 │ 1 │
└───┴───┴───┴───┴───┴───┴───┴───┘
Figure A.9/03.46: Element discriminator of a TCF element |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 3 Information field content | |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 3.1 BCS element | CCITT Recommendation ╔════════════════════════╗
T.30 frame ║ FCF + [FIF] ║
╚════════════════════════╝
| |
FA protocol ╔═══╤════╤════════════════════════╗
element ║ D │ SN │ ║
╚═══╧════╧════════════════════════╝
D = discriminator ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 3.2 BCS abort element | no information field available |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 3.3 BCS transmit request element | FA protocol ╔═══╤════╗
element ║ D │ SN ║
╚═══╧════╝
D = discriminator octet
SN = sequence number (0 .. 255),
bit 1 = LSB = Least significant bit |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 3.4 Preamble element | no information field available |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 3.5 Normal fax data element | transcoded ═╤═══════════════════════════════════════╤═
facsimile │ max. 936 bits of facsimile coded data │
data ═╧═══════════════════════════════════════╧═
│ │
FA protocol ╔═══╤═══════════════════════════════════════╗
element ║ D │ ... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 3.6 Error correction fax data element | CCITT Recommendation
T.4 frame ╔════════════════════════╗
(FCD or RCP) ║ FCF + [FIF] ║
╚════════════════════════╝
| |
FA protocol ╔═══╤════════════════════════╗
element ║ D │ ║
╚═══╧════════════════════════╝
D = discriminator octe... |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 3.7 End of data element | no information field available |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 3.8 TCF element | bit 8 7 6 5 4 3 2 1
┌───┬───┬───┬───┬───┬───┬───┬───┐
│ 0 │ 0 │ 0 │ 0 │ 0 │ 0 │ 0 │ X │
└───┴───┴───┴───┴───┴───┴───┴───┘
X = 0 : TCF_OK
X = 1 : TCF_NOK
Figure A.13/03.46: Information field content of a TCF element |
1b3a41393e6b9c2d9c5a8ec454e96ca8 | 03.46 | 4 Relationship of FA protocol elements with LAPB, L2RBOP and RLP | Refer also to GSM 07.03
FA protocol ╔═╤════════════════════════╗
element ║D│ optional information ║
╚═╧════════════════════════╝
| |
LAPB I-frame ╔═╤═╤══════════════════════════╤═══╗
information ║A│C│ │FCS║
field ╚═╧═╧═════════════... |
8b410df87e6e8f32e6bbafe6636ff843 | 06.07 | 1 Scope | The present document specifies the digital test sequences for the GSM half rate speech codec. These sequences test for a bit exact implementation of the half rate speech transcoder (GSM 06.20 [2]), Voice Activity Detector (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]) and the discontinuous transmission (GSM 06.41 [5]). |
8b410df87e6e8f32e6bbafe6636ff843 | 06.07 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
8b410df87e6e8f32e6bbafe6636ff843 | 06.07 | 3 Definitions and abbreviations | |
8b410df87e6e8f32e6bbafe6636ff843 | 06.07 | 3.1 Definitions | Definition of terms used in the present document can be found in GSM 06.20 [2], GSM 06.21 [3], GSM 06.22 [4], GSM 06.41 [5] and GSM 06.42 [6]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.