hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.1.2.3 Additional uplink parameters | Table 9.13
Parameter
Value
Channel Estimation
Ideal multipath delay estimation and joint channel estimator according to article from Steiner and Baier in Freq., vol. 47, 1993, pp.292-298, based on correlation to obtain the complex amplitudes for the path.
Receiver antenna diversity
ON (2 antennas)
Îor/Ioc [dB]
Paramete... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2 Simulation results | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.1 12.2kps service | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.1.1 Graphical Presentation of 12.2kbps service UL Simulation Results | Figure 9.6
Figure 9.7
Figure 9.8
Figure 9.9 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.1.2 Graphical Presentation of 12.2kbps service DL Simulation Results | Figure 9.10
Figure 9.11
Figure 9.12
Figure 9.13 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.2 64kps Service | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.2.1 Graphical Presentation of 64kbps service UL Simulation Results | Figure 9.14
Figure 9.15
Figure 9.16
Figure 9.17 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.2.2 Graphical Presentation of 64kbps service DL Simulation Results | Figure 9.18
Figure 9.19
Figure 9.20
Figure 9.21 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.3 144kps Service | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.3.1 Graphical Presentation of 144kbps service UL Simulation Results | Figure 9.22
Figure 9.23
Figure 9.24
Figure 9.25 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.3.2 Graphical Presentation of 144kbps service DL Simulation Results | Figure 9.26
Figure 9.27
Figure 9.28
Figure 9.29 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.4 384kps Service | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.4.1 Graphical Presentation of 384kbps service UL Simulation Results | Figure 9.30
Figure 9.31
Figure 9.32
Figure 9.33 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.1.2.4.2 Graphical Presentation of 384kbps service DL Simulation Results | Figure 9.34
Figure 9.35
Figure 9.36
Figure 9.37 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 9.7.2 1.28 Mcps TDD and FDD link level simulation | (void)
Annex A (informative):
The key physical layer parameters for low chip rate TDD option
Table A.1
Support of :
Difference to high chiprate TDD option
Further details
Support of different radio frame structure
1.Different frame structure to high chiprate TDD option
2.Different basic midamble sequences, maximum chan... |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 8.3.8.2 Peak Code Domain Error | H.4 Notes
NOTE: Symbol length
Description is common with 3.84 Mcps TDD option
NOTE: Deviation
Description is common with 3.84 Mcps TDD option.
NOTE: Residual
Description is common with 3.84 Mcps TDD option.
NOTE: Scrambling code
Description is common with 3.84Mpcs TDD option.
NOTE: TDD
Description is common with 3.84 M... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 1 Scope | The purpose of the present document is to help the relevant 3GPP groups to specify the changes to existing specifications, needed for the introduction of the “Handover for real-time services from PS domain” Building Block for Release 2000.
The purpose of this R00 work task is to define the relocation procedure to be us... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 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... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 3 Definitions, symbols and abbreviations | |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply.
SRNS relocation: The definition of [5] applies.
Handover: The definition of [5] applies.
Hard handover: The definition of [5] applies.
Relocation, or Relocation of SRNS: The definition of [4] applies.
Bi-casting: The capability of a no... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 3.2 Symbols | None. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
DL Downlink
GGSN Gateway GPRS Support Node
GTP GPRS Tunnelling Protocol
N-PDU Network PDU
PDCP Packet Data Convergence Protocol
PDU Protocol Data Unit
RLC Radio Link Protocol
RNC Radio Network Controller
RRC Radio Resource Control
SGSN Serving... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 4 GSM and UMTS R99 status | None. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 4.1 GSM solution | Inter-BSC handovers in GSM are described in ref. [1].
The 2G systems have been optimised to minimize the interruption of speech during handovers. In DL the standards allow bi-casting from the MSC. In UL this is achieved by fast radio resynchronisation by the UE. Typical values are in the range of 60 to 120 ms in UL. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 4.2 UMTS R99 status | Relocation in UMTS R99 for the CS domain is described in ref. [1].
Similarly to the GSM solution, the interruption of speech during relocation has been minimised. In DL the standards allow bi-casting from the MSC. In UL this is achieved by fast radio resynchronisation by the UE.
In UMTS R99, relocation for the PS domai... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5 Requirements | None. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5.1 General | General requirement is to minimise disruption to the user. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5.2 Packet loss | Frame loss can already occur over the radio. Therefore when relocation occurs, any frame loss happens in addition to the frames lost over the radio. Therefore frame loss should be minimised. As a reference, in CS wireless speech, the FER must not be greater than 1%.
The packet loss should be similar to what is achieved... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5.3 Round-trip delay | - The round-trip delay should be minimised in real-time conversational services.
- The round-trip delay should be similar to what is achieved currently in 2G systems for CS wireless speech, or smaller.
- The global delay variation should be minimised. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5.4 Speech interruption | The speech interruption should be similar to what is achieved currently in 2G systems for CS wireless speech, or smaller. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5.5 Frequency of interruption | The number and frequency of interruption perceived by the user should be minimised. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5.6 Security | Editor’s Note: This section is intended to list any security requirements for the real-time handover solution. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5.7 Inter-system operation | It is required that the real-time relocation solution for PS domain works with a rel4 Core Network and a GERAN. The assumption is that the GERAN will be connected to the rel4 Core Network via the Iu-PS. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5.8 Backwards compatibility | The real-time relocation solution shall be backwards compatible with UMTS R99 UEs. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5.9 General applicability of the selected solution | It is required, that a unique solution will be finally selected supporting
- hard handover (“UE involved”)
- SRNS Relocation (“UE not involved”)
- inter-system operation (GERAN<->UTRAN) and
- intra-system operation (GERAN, UTRAN).
The solution shall, additionally, take care of an optimum support for intra-SGSN relocati... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5.10 Alignment of selected solution with transport mechanisms within Rel4 CN | It is required that the selected solution takes into consideration transport mechanisms selected for the Rel4 PS CN.
If the Rel4 transport protocols for the PS domain utilises/requires resource reservation or initialisation of transport characteristics (like is done in CS domain), it shall be ensured that these mechani... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 5.11 Support for multiple simultaneous RABs with different QoS | It shall be capable to relocate/handover multiple RABs belonging to the same UE with the same signalling transaction on the Iu interface. These RABs, including the RAB for call control signalling, may belong to different QoS classes, and some of them may require lossless relocation/handover. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6 Study areas | |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.1 Solution 1: Reuse of release 99 Packet Duplication mechanism | |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.1.1 General | The idea of Solution 1 is to reuse the release 99 Data forwarding mechanism also for real time services requiring seamless Relocation of SRNS. Seamless Relocation of SRNS means that the interruptions to the data stream flow are minimised and are basically unnoticeable by the users.
The basic principle of SRNC duplicati... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.1.2 The main steps of Relocation for data forwarding | [Note: Since for the solution 1 the procedures and mechanisms of performing Relocation of SRNS for all RABs from PS domain are the same, both the handling of lossless and Seamless RABs during Relocation of SRNS are described in this chapter.] |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.1.2.1 Preparation of Relocation of SRNS and Resource allocation | In this phase the UTRAN reserves resources for the relocation.
Specifically for Solution 1, it is assumed that lossless and seamless existing RABs are set to be "subject to data forwarding" in Relocation Command.
At the end of the preparation phase source RNC should:
- for lossless RABs; stop processing DL GTP-PDUs dat... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.1.2.3 Switching of DL flow in CN and Completion | In this phase, the DL GTP tunnel is updated between the SGSN and the GGSN so that the DL flow can use the new route.
The mechanism shown assumes that the DL GTP port used for a given RAB in target RNC is the same for all arriving GTP-PDUs regardless of their arrival route.
Only effect to the UTRAN may be the slightly e... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.1.3 Specifications Impact | |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.1.3.1 Impacts on RAN3 specifications | The Solution 1 reuses the Release 99 data forwarding mechanisms also for the seamless RABs from PS domain. Solution 1 does not require any new procedures, messages nor information elements to be introduced to any RAN 3 specification.
In R99, there is a clear indication in the RAB parameters used at RAB assignment that ... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.1.3.2 Impacts on other groups’ specifications | Depending on RAN 2 opinion, maybe addition of one parameter to RRC container could ensure the unambiguous operation of the solution 1. (See the chapter describing the Open Issues).
Stage 2 specification TS 23.060 has to be aligned with the selected solution for RT PS domain Relocation of SRNS. The consistent handling o... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.1.4 Interaction with other systems | This section is intended to explain how this solution will work with other systems such as GERAN, UTRAN R99, GSM and GPRS. This is subject to information availability for these other systems. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.1.5 Summary: solution 1 | This solution is based on making some procedure enhancements to the R99 mechanisms. During an interim state, the processing of the real time data is done at the source RNC so that the source RNC both sends the traffic to the UE, and forwards it to the target RNC.
This solution also assumes that considering the nature o... |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.1.6 Open issues | None. |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2 Solution 2: Core Network bi-casting | |
7d3783c93dcb97023753560f1c6e0f1f | 25.936 | 6.2.1 General | The Core Network bi-casting mechanism handles real-time data from the GGSN/SGSN based on the model from GSM and the CS domain in UMTS R99.
The principle is that the packet anchor is at the GGSN/SGSN which acts as the equivalent of the three-party bridge in the CS domain MSC.
During the relocation, real-time downlink N-... |
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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.