hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.2 TCH/F14.4, TCH/F28.8, and TCH/F32.0 channel codings | |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.2.1 User rate adaptation on the A interface, AIUR less than or equal to 56 kbit/s | The A-TRAU frame shall be used for transparent user data rates other than 32 kbit/s on the A interface. The A-TRAU frames are transmitted on up to four substreams multiplexed into one stream sent over the A interface. The split/combine function is applied on the substreams as specified in clause 7 of this TS. The relat... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.2.2 User Rate Adaptation on the A-interface, AIUR greater than 56 kbit/s | For AIUR of 64 kbit/s one stream consisting of ITU-T V.110 32 bit frames or 64 bit frames, as specified in 3GPP TS 04.21 shall be transmitted over the A-interface. Splitting/Combining which occurs in the BSS, shall be as specified in 3GPP TS 04.21.
Table 12 gives the relation between the User Rate, Substream Rate Chann... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.2.3 Relation between AIUR and the number of channels | Table 12: Relationship between the AIUR, AIUR per substream, channel coding, intermediate rate and number of substreams
AIUR
Number of substreams x
AIUR per substream
Channel Coding
Multislot intermediate Rate (note 1)
14,4 kbit/s
14,4 kbit/s
TCH/F14.4
16 kbit/s
28,8 kbit/s
2X14,4 kbit/s
TCH/F14.4
TCH/F28.8
16 kbit/s
3... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.2.4 Handling of status bits X and SB | The X and SB bits shall be carried over the A interface in a multiframe structure as described in subclause 8.1.1.1 of 3GPP TS 04.21. SA bit is not carried over the A interface.
The handling of the status bits shall comply with the synchronisation procedures for transparent services which are as described in 3GPP TS 29... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 17 Frame Formats | Octet
Bit number
No.
0
1
2
3
4
5
6
7
0
0
0
0
0
0
0
0
0
1
1
D1
D2
D3
D4
D5
D6
S1
2
1
D7
D8
D9
D10
D11
D12
X
3
1
D13
D14
D15
D16
D17
D18
S3
4
1
D19
D20
D21
D22
D23
D24
S4
5
1
E1
E2
E3
E4
E5
E6
E7
6
1
D25
D26
D27
D28
D29
D30
S6
7
1
D31
D32
D33
D34
D35
D36
X
8
1
D37
D38
D39
D40
D41
D42
S8
9
1
D43
D44
D45
D46
D47
D48
S9
Fig... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1 Bearer capabilities | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1.1 Bearer capabilities | The EDGE radio interface shall be designed to work in all typical GSM radio environments like rural area (RA), typical urban (TU) and an indoor environment. EDGE shall also work in a Hilly Terrain (HT) environment however the main focus is on channels with lower delay spread than HT, as specified in GSM05.05.
The peak ... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1.1.1 Enhanced GPRS | EGPRS shall provide a range of bearer capabilities that depend upon the environment and user’s speed. The peak rate shall at least be:
EGPRS
Indoor/Low range outdoor
Urban/Suburban outdoor
Rural outdoor
EGPRS
384 kbps (48 kbps/timeslot)
384 kbps (48 kbps/timeslot)
144 kbps (18kbps/timeslot)
Speed
up to 10 km/h
up to 10... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1.1.2 Enhanced CSD | ECSD shall provide a range of bearer capabilities (per time slot) that depend upon the environment and user’s speed. The peak rates should at least be:
ECSD/T
Indoor/Low range outdoor
Urban/Suburban outdoor
Rural outdoor
ECSD/T
32 kbps/timeslot *)
32 kbps/timeslot *)
-
Speed
up to 10 km/h
up to 100 km/h
-
Propagation c... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1.2 Bearer service attributes | The same bearer service attributes used for GPRS and CSD should be used for EGPRS and ECSD. Some new bearer service parameters relevant to the radio interface may be needed. For EGPRS the same QoS classes should apply. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1.3 Hand over/cell re-selection | The same hand over/cell re-selection mechanisms as for CSD/GPRS apply. Re-selection methods should allow the operator to optimise the service availability for EDGE users.
Seamless transition ECSD-> CSD -> ECSD and EGPRS classic->GPRS -> EGPRS classic.
Seamless transition from EGPRS Classic->EGPRS Compact->EGPRS Classic... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.2 Operational requirements | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.2.1 Compatibility with services provided by present core networks | EDGE will enhance the GPRS and CSD service by providing higher data rates. That means, that EDGE will rely on underlying GSM functionality. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.2.2 Operating environments | The operational scenario for EDGE includes international operation across various EDGE radio operating environments (850/900/1800/1900 MHz bands). Further, EDGE will support a variety of services with a range of bit rates. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.2.3 Radio Access network planning | EDGE should not require a modification of actual frequency/coverage planning defined for GSM air interface when introduced. Frequency/coverage re-planning may be used to maximise the throughput in the system.
An EDGE network shall support at least 4/12, 3/9 and 1/3 frequency reuse patterns. EGPRS Compact shall support ... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.2.4 Operators | All GSM900/1800/1900 operators should be able to deploy EDGE without licensing problems. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3 Efficient spectrum usage | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.1 Spectral Efficiency | The spectral efficiency of EDGE should be significantly higher than in GSM.
The radio interface should be designed to maximise spectral efficiency.
EGPRS Compact shall be possible to implement in less than 1 MHz initial spectrum. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.2 Spectrum utilisation | It should be possible to use EDGE in all GSM bands.
It should be possible to mix EDGE and non EDGE timeslots on the same carrier.
If simultaneous EDGE and non EDGE operation in the same time slot is required or not is for further investigation.
If EDGE is used on the BCCH carrier, it should not have any impact on BCCH ... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.3 Coverage/capacity | The peak service rates may be provided only in a limited coverage area. Link adaptation shall provide a mechanism to have a smooth degradation of the service rates for the outer cell areas.
EDGE should be designed to maximise the area where high data rates can be achieved.
SMG2 should define appropriate evaluation crit... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.4 Evolution requirements | With EDGE several 3rd generation services can be provided in GSM. The technical parameters for EDGE should allow an evolution for coverage and capacity, as well as provisioning of future 3rd generation services. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.4.1 Coverage evolution | The radio coverage for the EDGE may be:
- contiguous coverage;
- island coverage;
- spot coverage.
EDGE should be sufficiently flexible to support a variety of initial coverage configurations and facilitate coverage evolution. Coverage can be increased by deploying cell planning parameters optimised for EDGE usage and/... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.4.2 Capacity evolution | EDGE should facilitate the implementation and use of appropriate capacity improvement techniques, if applicable, in the various radio operating environments.
EDGE should not prevent capacity improvements, e.g. adaptive antennas, advanced power control, efficient resource allocation etc. It is desirable that the EDGE do... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.4 Complexity / Cost | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.4.1 Mobile complexity and cost | Hand portable and PCMCIA card sized EDGE terminals should be optimised in terms of size, weight, operating time, range, effective radiated power and cost/performance ratio. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.4.2 Network complexity and cost | The cost/performance ratio of development and equipment should be kept at a reasonable level. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.4.3 Mobile Station / Base Station types | The EDGE standard should support multislot operation for ECSD and EGPRS. It should be possible to provide a variety of Mobile Station as well as Base Station types of varying complexity, cost and capabilities in order to satisfy the needs of different types of users. The number of mobile classes should though be minimi... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.5 Requirements from bodies outside SMG | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.5.1 Electromagnetic compatibility | The modulation characteristics have to be such that the degree of interference caused to other equipment is not higher than in today's systems. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.5.2 RF Radiation effects | EDGE shall be operative at RF emission power levels which are in line with the recommendations related to electromagnetic radiation. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.5.3 Security | The EDGE radio interface should be able to accommodate at least the same level of security as the GSM radio interface does. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.6 Co-existence with other systems | A GSM system with EDGE should be capable to co-exist with a GSM system without EDGE deployment within the same or neighbouring band as well on neighbouring time slots. Furthermore should the performance of GSM channels without EDGE not be worsened by the fact that the neighbouring channel is a GSM channel with EDGE and... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.7 Further Work Areas | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.7.1 Services coordination | Possibility to have same or similar services in EDGE as in UMTS needs to be investigated. Investigation of hand-over between GSM and UMTS is necessary. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.7.3 Measurements in existing GSM | It should be studied if there is a need to modify existing measurements for EDGE or other work items.
History
Document history
16th February 1998
First draft
20th February 1998
Update after Joint SMG1,2,3 & 4 EDGE workshop in Helsinki
27th April 1998
Update after SMG1 and SMG2 WPB#4
25th May 1998
Update after SMG4 and ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 1 Scope | The purpose of this Technical Report is to study the feasibility of a core network CAMEL server controlling voice services carried by VoIP within a GPRS PDP Context using:
1) An architecture based on ITU-T, H.323 family of recommendations.
2) An architecture based on IETF SIP specifications. |
14ce710049a3c611ebb26f3972649957 | 21.978 | 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... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 3 Introduction | The GSM CAMEL feature for control of operator specific services when roaming has evolved over a number of years and work on the latest Phase (Phase 3) is planned for completion as part of Release '99. Work in other 3GPP groups, particularly S2, is focused on developing a reference architecture for an all IP PLMN. One ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 4 Definitions and Abbreviations | BCSM Basic Call State Model
CAMEL Customised Application for Mobile networks Enhanced Logic
CAP CAMEL Application Protocol
CSI CAMEL Subscriber Information
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
HLR Home Location Register
IPSSF Internet Protocol Service Switching Function
MAP Mobile Applicatio... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 5 Proposition | An overall objective for this feasibility study is to demonstrate that CAMEL control of VoIP services in 3G networks can be readily specified and implemented by adapting standards and software used in 2G networks. This approach leads to services that function the same when a user roams between 2G and 3G networks, simpl... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 5.1 Relationship with Architecture work in S2 | Ongoing architecture work in S2 for 3G is documented in TS 23.121 and in the Technical Report on 'Architecture for an all IP network' (TR 23.922 V1.0.0). The work in this CAMEL control of VoIP services FTR is intended to aid/complement S2 work by analysing feasibility at a somewhat lower level of abstraction, focusing ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 6 Service Requirements | In 3GPP, SA1 has responsibility for the definition of service requirements. Requirements for Release '00 are at a very early stage of development. When considering feasibility it is very useful to have in mind the services that a 3G network may be required to support. This section lists many example 2G network voice se... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 6.1 Basic Services | Example basic services that may require CAMEL control in a 3G network:
- Speech
- Emergency calls
- Low bit rate data
- Medium bit rate data
- High bit rate data
- High quality audio
- Low bandwidth video
- High bandwidth video |
14ce710049a3c611ebb26f3972649957 | 21.978 | 6.2 Supplementary Services | Example 2G supplementary services that may require CAMEL control in a 3G network:
- Operator determined barring
- User defined barring
- Call screening
- Call deflection
- Call forwarding unconditional
- Call forwarding on busy, no reply and not reachable
- Call waiting
- Call hold
- Call transfer
- Calling number iden... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 6.3 Operator Specific Services | Example 2G operator specific services that may require CAMEL control in a 3G network:
- Short number dialling
- Prepay
- VPN |
14ce710049a3c611ebb26f3972649957 | 21.978 | 6.4 Other Services | Example services not listed in the ‘Basic Services’, ‘Supplementary Services’ or ‘Operator Specific Services categories that may require CAMEL control in a 3G network:
- Lawful interception
- Voice group-call service
- Voice broadcast service
- SMS
- Fax
- ASCI
- MExE
- Location Services
- SoLSA |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7 H.323 Solution | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.1 Description | ITU-T defines a family of recommendations known as H.323 for multimedia communications over packet based networks. The majority of VoIP products available today support H.323.
Figure 2: H.323 Environment
The H.323 environment is illustrated in Figure 2. A 'terminal' is a network endpoint that provides real-time, voice... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.2 Architecture | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.2.1 Introduction | This section of the report provides information flows that illustrate simple MO and MT calls with CAMEL interactions. It is based upon an architecture that proposed in references [6] and [7]. The objective is to provide further understanding of the proposed architecture and to further progress the work in the feasibili... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.2.2 Assumptions | a. The call flows presented are based on using the ITU-T H.323 protocol between the Mobile Station (MS) and the Gatekeeper.
b. The gatekeeper and the IPSSF have been co-located in order to avoid any showing information flows between the two entities. Standardisation of the information flows between these entities is fo... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.2.3 Functional Architecture | The proposed functional architecture is discussed in [6] and is shown in Figure 6. The main idea behind this functional architecture is to be able to reuse existing (circuit switched) CAMEL services for VoIP.
Figure 6: Proposed functional architecture |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.3 Message Flows | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.3.1 Registration | It is not within the scope of this feasibility study to investigate or select the registration and location update process that must exist within a multimedia service network. However this section outlines a possible registration process that allows CAMEL Subscriber Information (CSI) to be stored in the Gatekeeper/IPSS... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.3.2 MO call requiring CAMEL interaction | The call flows for a mobile originated (MO) calls are shown in Figure 8 and are further explained below:
{1} The MS wishes to place a VoIP call. A PDP context must be established to allow an IP session to be set up.
{2} The MS checks that it is allowed to place a call via RAS Admission Request message.
{3} If the MS is... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.3.3 MT call requiring CAMEL interaction | The call flows for mobile terminated (MT) calls are shown in Figure 9 and are further explained below:
{1} An incoming H225 Setup message is received by the mediation gatekeeper in the home network of the called subscriber. (The incoming call could be from an other H.323 gatekeeper or H.323 signalling gateway represent... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.4 State Models | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.4.1 H.323 and CAMEL O-BCSM | Figures 10, 11 and 12 show the relationship between the H.323 protocol state model and the points in call (PICs) defined in the CAMEL phase 3 Originating Basic Call State Model (O-BCSM) for successful and unsuccessful call attempts. The O-BCSM represented is based on CAMEL phase 3 state models as described in reference... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.4.2 Successful call establishment | Figure 10 shows the PICs and relationship to H.323 messages for a successful call establishment of MO call with CAMEL interaction.
{1} The H.225 Setup message indicates that a dialled number is received from the MS and detects that an O-CSI exists for this subscriber.
{2} Analysis of the O-CSI takes place and gsmSCF is... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.4.3 Unsuccessful call establishment due to gatekeeper admission reject | Figure 11 shows the PICs and relationship to H.323 messages for the situation where the destination is refused permission to accept the incoming call by the gatekeeper. An AdmissionReject message may be sent by the gatekeeper to the destination is registered with for reasons specified in RAS procedures. In order to kee... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.4.4 Unsuccessful call establishment due to refusal by destination party | Figure 12 shows the PICs and relationship to H.323 messages for the situation where the destination does not accept the incoming call request. Once again, in order to keep the Figures relatively simple, the PICs O_Null&Authorise.. and Analyse_Info and corresponding message flows are not shown.
{1} Instructions received... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.4.5 H.323 and CAMEL T-BCSM | Figures 13 and 14 show the relationship between the H.323 protocol state model and the points in call (PICs) defined in the CAMEL phase 3 Terminating Basic Call State Model (T-BCSM) for successful and unsuccessful MT call attempts. The T-BCSM represented is based on CAMEL phase 3 state models as described in reference ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.4.6 Successful MT call delivery | Figure 13 shows the PICS and relationship to the H.323 protocol state model for a successfully established MT call requiring CAMEL interaction.
{1} The H.225 Setup message arrives at the gatekeeper the destination MS is register with. If a T-CSI exists for the subscriber, a T-BCSM instance is created.
{2} Analysis of t... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.4.7 Unsuccessful MT call delivery | Figure 14 shows the PICs and relationship to H.323 message for the situation where the terminating MS does not accept the incoming call.
{1} The H.225 Setup message arrives at the gatekeeper the destination MS is register with. If a T-CSI exists for the subscriber, a T-BCSM instance is created.
{2} Analysis of the T-CS... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.5 CAMEL Integration | Integration of CAMEL functions with H.323 Gatekeeper functions may require enhancements to H.323 standards or CAMEL standards. Some initial work has been done to identify the standards that may need to be enhanced and to assess the extent of the changes required. |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.5.1 Impact on H.323 Standards | Section 7.4 describes and illustrates how H.225 messages may be mapped to O_BCSM and T_BCSM Detection Points (DPs) at the Gatekeeper/SSF. When studying the Figures it can be seen that some CAMEL Phase 3 DPs (such as O_Active) have good correspondence with H.225 messages at the Gatekeeper, while other DPs require more d... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.5.2 Impact on CAMEL and other UMTS Standards | It is likely the some functional modelling additions and some CAP message information element additions will be needed. It is also likely that some HLR/VLR data and MAP protocol additions may be needed. It is of course very difficult to assess and describe exactly how much effort and meeting time is required to effect ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.6 Service Impacts | The combination of CAMEL and H.323 (as described in this report) may support some GSM supplementary services, such as unconditional call forwarding (subject to some re-engineering) and perhaps most operator specific services (depends on the extent of any reduced functionality necessary for integration). Every service n... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.7 Multimedia Evolution | The proposal in this report is focused on voice not multimedia. Control of multimedia services requires further study. However, the proposal does not in any way preclude CAMEL evolution to control multimedia services supported by the H.323 family of recommendations. It is likely that further enhancements to the protoco... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.8 Advantages | The following advantages have been identified:
Maximises the re-use of existing functional entities, protocols and services. Such reuse decreases the development and ownership costs allowing existing familiar 2G services to be provided to 3G subscribers at an early stage.
Minimum changes to the CSE for the support ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.9 Disadvantages | The following disadvantages have been identified:
Introduces new functional entity ‘IPSSF’, which provides the necessary mapping between the Gatekeeper and the CSE. However, this functional entity is based on the functions already provided by a VMSC/GMSC, where already standardised process such as the gsmSSF can be ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8 SIP Solution | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.1 Description | The IETF Multiparty Multimedia Session Control (MMUSIC) working group specifies an IP telephony architecture (Figure 15). The architecture is seen as an alternative to ITU-T H.323 family of recommendations that is simpler to implement. It allows for the possibility of interworking with H.323 terminals. However, H.323... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.2 Architecture | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.2.1 Introduction | This section of the report provides information flows that illustrate the possible interaction of CAMEL and SIP. In particular it provides a proposal for the triggering of CAMEL services as well as a mapping between the CAMEL call states and the call states of the Session Initiation Protocol (SIP).
An overall objective... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.2.2 Functional Architecture | The proposed functional architecture is derived from various companion contributions relating to the technical report. It is provided here for completeness. The concept of the ‘IPSSF’ is introduced which acts as an overlay between the IP telephony call control and the Intelligent Network layer provided by the CAMEL Ser... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.2.3 Basic concept of the proposal | Subscribers may register in the visited SIP network allowing the subscriber to receive incoming calls. A subscriber may use the MSISDN as an additional identifier in the registration process. Upon registration with the server, the CAMEL subscription information for the subscriber is sent to the IPSSF by the HLR in the ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.2.4 Assumptions | a. All the call flows show that the SIP Proxy Server and the IPSSF have been co-located in order to avoid showing an information flows between the two entities. Standardisation of the messages for this interface is for further study.
b. The attach/detach and establishment of the Packet Data Protocol (PDP) session are b... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.3 Message Flows | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.3.1 Proposed Registration process | This section outlines a possible registration process based on the SIP REGISTER method, which allows CAMEL subscription information to be stored in the SIP Proxy Server/IPSSF. IETF RFC 2543 [4] defines the term Registrar for registration purposes and it is the SIP registrar that accepts the REGISTER method. In this sec... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.3.2 Mobile Originating Call with CAMEL interaction | This section deals with the mobile originating calls that require interaction with CAMEL.
The call flows are shown in Figure 22 and are further explained below:
{1} The MS wishes to place a VoIP call. A PDP context is established to allow an IP session to be established over the GPRS network.
{2} The User Agent Server ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.3.3 Mobile Terminating Call with CAMEL interaction | This section deals with the CAMEL interaction for mobile terminated calls. A CAMEL service is triggered if the triggering criteria held in the called subscriber’s T-CSI matches the characteristics of the incoming call. The information flows are shown in Figure 23 and further explained below:
{1} The terminating SIP Pro... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.4 State Models | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.4.1 Mapping SIP message to CAMEL Basic Call State Models | This section deals with how the Originating Basic Call State Model (O-BCSM) Points in Call (PICs) and Detection Points (DPs) or ‘triggers’ are mapped to the appropriate SIP messages. Although a mapping is possible, there is not always the same analogy between the circuit switched environment that the CAMEL BCSM were de... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.4.2 Mapping to Originating BCSM for MO calls | The mapping between the SIP methods and responses for O-BCSM relating to Mobile Originating Calls are shown in Figure 24. Only the successful case is described. Further work is necessary to describe all other scenarios. The information flows are further described below :
{1} INVITE method arrives at the proxy server, i... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.4.3 Terminating BCSM for MT Calls | The mapping between the SIP methods and responses for T-BCSM and Mobile Terminating Call is shown in Figure 25. The information flows further described below :
{1} INVITE method arrives at the destination SIP Proxy server. Server/IPSSF determines if a T-CSI exists for the called user
{2} T-CSI is analysed and if necess... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.4.4 Unsuccessful MT Call Delivery | This subsection explores the mapping and the reporting of the DPs that may be encountered when the call is not successfully established. The information flows are shown in Figure 26 and further explained below:
{1} INVITE method arrives at the destination SIP proxy server. Server/IPSSF determines is a T-CSI exists for ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.5 CAMEL Integration | Integration of CAMEL functions with SIP Proxy Server functions may require enhancements to SIP standards or CAMEL standards. Some initial work has been done to identify the standards that may need to be enhanced and to assess the extent of the changes required. |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.5.1 Impact on SIP Standards | Section 8.4 describes and illustrates how SIP messages may be mapped to O_BCSM and T_BCSM Detection Points (DPs) at the SIP Proxy Server/SSF. When studying the Figures it can be seen that some CAMEL Phase 3 DPs (such as O_Active) have good correspondence with SIP messages at the SIP Proxy Server, while other DPs requir... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.5.2 Impact on CAMEL and other UMTS Standards | It is likely that some functional modelling additions and some CAP message information element additions will be needed. It is also likely that some HLR/VLR data and MAP protocol additions may be needed. It is of course very difficult to assess and describe exactly how much effort and meeting time is required to effect... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.6 Service Impacts | The combination of CAMEL and SIP (as described in this report) may support some GSM supplementary services, such as unconditional call forwarding (subject to some re-engineering) and perhaps most operator specific services (depends on the extent of any reduced functionality necessary for integration). Every service nee... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.7 Multimedia Evolution | The proposal in this report is focused on voice not multimedia. Control of multimedia services requires further study. However, the proposal does not in any way preclude CAMEL evolution to control multimedia services supported by SIP. It is likely that further enhancements to the protocols and functions listed in secti... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.8 Advantages | The following advantages have been identified:
Maximises the re-use of existing functional entities, protocols and services. Such reuse decreases the development and ownership costs allowing existing familiar 2G services to be provided to 3G subscribers at an early stage.
Minimum changes to the CSE for the support of... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 8.9 Disadvantages | The following disadvantages have been identified:
This approach is not in line with the work currently underway in ETSI SPAN 3 (Services and Protocols), in particular a work item addressing IN support for voice over IP on the H.323 architecture and associated protocols in association with the TIPHON project.
Introd... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 9 Work in other Standards Groups | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 9.1 3GPP | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 9.1.1 System Architecture Working Group 2 (S2) | The 3GPP S2 group has overall system architecture responsibility for the GSM/GPRS evolved system within the 3GPP organisation and also has close linkage with the ETSI SMG12 (GSM/GPRS) system architecture group.
The S2 group is investigating the architectural impacts and linkages involved with providing IN (CAMEL) based... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 9.2 ETSI | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 9.2.1 TIPHON | TIPHON Working Group 7 is studying the implementation of TIPHON networks in a mobile environment, and has been in existence since the beginning of 1999. TIPHON mobility is user and service mobility in the context of the VoIP application. The group has an understanding with 3GPP S2 to liase over IP activities. It is cur... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.