hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.9.2.1.2 Pros and cons | Editors note: To be completed |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.9.3 Working assumption | Solution 7.9.2.1 has been accepted as working assumption.
8 Header compression in GERAN
Editors note: To be completed
9 Recommended work for GERAN voice optimization schemes
Editors note: To be completed.
9.1 Recommended work for particular groups
Editors note: To be completed. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 10 Open issues | This section lists identified open issues related to support of voice optimisation for the IMS in the GERAN.
Ref
Description of problem
Status
1
Is it necessary to define one channel coding scheme as mandatory in the standard, required to be supported in all GERAN based IMS SIP based calls?
2
Is there a requirement for... |
8a9283a656db20cd080be5c53231664c | 23.922 | 1 Scope | This technical report will propose an architecture that provisions an all-IP architecture option for release 00. The purpose of the technical report is to
• identify key issues and affected ongoing 3GPP work that need to be resolved and
• propose a high level work plan for completion of an all IP release 00 UMTS stand... |
8a9283a656db20cd080be5c53231664c | 23.922 | 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... |
8a9283a656db20cd080be5c53231664c | 23.922 | 3 Definitions and abbreviations | |
8a9283a656db20cd080be5c53231664c | 23.922 | 3.1 Definitions | For the purposes of the present document, the [following] terms and definitions [given in ... and the following] apply.
existing service: services supported in Release 99 and earlier releases for both GSM and UMTS.
All IP core network: core network of release 2000 that uses IP for transport of all user data and signall... |
8a9283a656db20cd080be5c53231664c | 23.922 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
<ACRONYM> <Explanation>
2G second generation
3G third generation
AMR Adaptive Multi Rate
AS Application Server
BSC Base Station Controller
BTS Base Station
CAMEL Customised Applications for Mobile Network Enhanced Logic
CAP CAMEL Application P... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4 Requirements | In order for TSG-SA2 to conduct a study of the architecture issues relating to the introduction of an All IP architecture within UMTS, assumptions were made as to the requirements for this architecture. TSG-SA1 are invited to validate and to extend these requirements as part of the work package on requirements for Re... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.1 General | The aim of the all IP architecture is to allow operators to deploy IP technology to deliver 3rd Generation services, that is an architecture based on packet technologies and IP telephony for simultaneous real time and non real time services. This architecture should be based on an evolution from Release 99 specificati... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.1.1 General Requirements | 1. The overall aim of the all IP network is to support similar services to GSM release ’99 and new innovative services. Where appropriate these services should inter-work with exisiting GSM services.
2. In addition it should also possible to support existing (R99 and before) services/capabilities (speech, data, multi... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.2 Service Capabilities | |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.2.1 General | The following general service capabilities are identified:
1. Legal interception has to be possible in the R00 All-IP network.
2. Emergency calls shall be supported in the R00 All-IP network. |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.2.2 Basic requirements for the Service and Application Platforms | List of requirements on the “Application and Service” block:
1. Service capabilities are to be made available to the Applications through Service capability features;
2. Service capability features are provided by one or more service capabilities (possibly directly provided by network functions, e.g. HSS, CSCF etc.), a... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.3 Numbering Schemes | The standards shall allow mobile terminated communications to be routed to the user’s terminal on the basis of a single identifier e.g. MSISDN. This does not preclude multiple addresses being used for different services and capabilities (e.g. data, Fax, SMS). The network will route the call to the terminal over the a... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.4 R99 Terminals | See section 4.1.1 above: The following requirements for the support of R99 terminals is an operator specific option.
1. The standards shall enable the All-IP core network to support UMTS R99 terminals.
2. Speech services including emergency calls shall be provided in All-IP networks to any UMTS R99 terminal support... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.5 Radio aspects | 1. The radio resource usage should be optimised within the architecture for both service and signalling support.
2. Separation of the radio related and radio un-related functionalties between the core network and the radio access network
3. Separation of the user plane and control plane protocol stacks in the radio acc... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.6 Interworking | 1. The All-IP core network shall support interworking to external IP and non-IP networks (e.g. circuit-switched networks (PSTN, ISDN, GSM PLMN, UMTS PLMN,...). |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.7 Mobility management | 1. The All-IP core network shall provide streamlining and CN operated hand-over procedures for UMTS. |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.8 Roaming | 1. The standard shall enable the All-IP core network to support roaming with 2G GSM/GPRS networks and R99 UMTS networks. |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.9 Handover | The support of handover between release 98, release 99 and release 2000 network technologies is essential in maintaining adequate network coverage. Table 4-1 illustrates the necessary handover scenarios and the status of development of mechanisms.
Table 4-1: Handover requirements for UMTS All IP network
Between
2G-GSM ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.9.1 Handover Categories | 1 Intra network handover
Handover inside one all IP network
1a Intra RAN handover
1b Inter RAN handover
2 Inter network handover
Handover between two all IP networks
3 Inter-system handover
Handover between an all IP network and other systems |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.9.2 General Definition | Reselection and handover are two methods of supporting mobility during an active session. Reselection is the process whereby the mobile station autonomously determines which cell the mobile will receive services on. Handover is the process whereby the network determines which cell the mobile will receive services on. |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.9.3 General Requirements | For real-time services handover procedure shall be used. The network shall control the handover procedure.
Handover shall be the selected method of mobility if one or more active sessions have requested handover in a multi session call with different QoS requirements
Performance requirement on speech interruption (i.e.... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.9.4 MS Requirements | The mobile station shall be capable of supporting both reselection and handover.
The mobile station shall aid the RAN in the handover decision by supplying RF environmental information (e.g. received signal strength from serving cell and neighbour cells). |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.9.5 RAN Requirements | Handover decisions shall be based in the RAN.
Maintain the RAN QoS parameters, associated with the mobile station, across a handover boundary. Note, RAN QoS parameters for a mobile station are based upon the negotiated set of QoS parameters.
Facilitate admission control to optimize radio resources.
Select a handover ta... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.10 Call Control and Roaming | The following requirements need consideration for call control and roaming support in an all IP based network.
1 Routing of signalling and transport needs to be optimised, for the purposes of call control and roaming between networks.
2 Whenever possible, tromboning of the user's voice or data communication session ba... |
8a9283a656db20cd080be5c53231664c | 23.922 | 4.11 Security | The general principle for security for the all IP network implementation is to reuse the same mechanisms developed for 3GPP Release 99 wherever possible. |
8a9283a656db20cd080be5c53231664c | 23.922 | 5 Architecture for an all IP PLMN | |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.1 Reference Architecture | The reference architecture provides two options:
Option 1: has been developed with the goal of allowing operators to deploy an all IP based architecture to deliver 3rd Generation wireless/mobile services. This architecture is based on packet technologies and IP telephony for simultaneous real time and non real time s... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.1.1 Reference Architecture – Option 1 | As described earlier in the Requirements section 4.1, the architecture shown in Figure 5-1 has been developed with the goal of allowing operators to deploy an all IP based architecture to deliver 3rd Generation wireless/mobile services. This architecture is based on packet technologies and IP telephony for simultaneou... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.1.2 Reference Architecture – Option 2 | As described earlier in the Requirements section 4.1.1 item 3 and 6, the architecture shown in Figure 5-2 allows operators to migrate from a R’99 UMTS network into a R’00 All IP network. One purpose of option 2 is to allow support of release 99 CS terminals. Option 2 allows the two domains of R’99 to evolve independent... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.2 New Functional Elements | 5.2.1 Call State Control Function (CSCF)
In the following section, CSCF has been divided into several logical components.
Currently, these logical components are internal to the CSCF. The need for external components to be able to address directly one of the logical components of the CSCF is for FFS.
Every CSCF actin... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.2.3 Transport Signalling Gateway Function (T-SWG) | This is component in the R00 all-IP network is PSTN/PLMN termination point for a defined network. The functionality defined within T-SGW should be consistent with existing/ongoing industry protocols/interfaces that will satisfy the requirements.
• Maps call related signalling from/to PSTN/PLMN on an IP bearer and sen... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.2.4 Roaming Signalling Gateway Function (R-SGW) | The role of the R-SGW described in the following bullets is related only to roaming to/from 2G/R99 CS and GPRS domain to/from R00 CS and GPRS domain and is not involving the multimedia/VoIP domain.
• In order to ensure proper roaming, the R-SGW performs the signaling conversion at transport level (conversion: Sigtran S... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.2.5 Composite Gateway | Composite gateway: A logical entity composed of a single MGC and one or more MGs that may be reside on different machines. Together, they preserve the behaviour of a gateway as defined in H.323 and H.246 (this may include SIP servers and MSC servers in release 2000). |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.2.6 Media Gateway Control Function (MGCF) | This component in the R00 all-IP network is PSTN/PLMN termination point for a defined network. The functionality defined within MGCF should be consistent with existing/ongoing industry protocols/interfaces that will satisfy the requirements.
• Controls the parts of the call state that pertain to connection control fo... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.2.7 Media Gateway Function (MGW) | This component in the R00 all-IP network is PSTN/PLMN transport termination point for a defined network. For the architecture option 2, the component is also used for interfacing UTRAN with the All IP core network over Iu.
The functionality defined within MGW should be consistent with existing/ongoing industry protoco... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.3 Description of Reference Points | |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.3.1 Cx Reference Point (HSS – CSCF) | This reference point supports the transfer of data between the HSS and the CSCF.
When a UE has registered with a CSCF, the CSCF can update its location towards HSS. This will allow the HSS to determine which CSCF to direct incoming calls to. On this update towards the HSS, the HSS sends the subscriber data (applicatio... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.3.2 Gm Reference Point (CSCF – UE) | This interface is to allow UE to communicate with the CSCF e.g.
• register with a CSCF,
• Call origination and termination
• Supplementary services control. |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.3.43 Mc reference point (MGCF – MGW) | The Mc reference point describes the interfaces between the MGCF and MGW, between the MSC Server and MGW, and between the GMSC Server and MGW. It has the following properties:
• full compliance with the H.248 standard, baseline work of which is currently carried out in ITU-T Study Group 16, in conjunction with IETF ME... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.3.4 Mh Reference Point (HSS – R-SGW) | This interface supports the exchange of mobility management and subscription data information between HSS and R99/legacy mobile networks. This is required to support All IP users who are roaming in a 2G network. |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.3.5 Mm reference Point (CSCF – Multimedia IP networks) | This is an IP interface between CSCF and IP networks. This interface is used, for example, to receive a call request from another VoIP call control server or terminal. |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.3.6 Mr Reference Point (CSCF - MRF) | Allows the CSCF to control the resources within the MRF
5.3.7 Ms reference Point (CSCF – R-SGW)
This interface allows CSCF to contact legacy network elements, e.g. 2G HLR, for location management (location update and subscriber data download), and call control (eg 2G HLR enquires for routing number (RN) for a roaming ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.3.8 Mw Reference Point (CSCF – CSCF) | The interface allows one CSCF (e.g. home CSCF) to relay the call request to another CSCF (eg serving CSCF).
5.3.9 Nc Reference Points (MSC Server – GMSC Server)
Over the Nc reference point the Network-Network based call control is performed. Examples of this are ISUP or an evolvement of ISUP for bearer independent ca... |
8a9283a656db20cd080be5c53231664c | 23.922 | 5.3.10 Nb Reference points (MGW-MGW) | Over the Nb reference point the bearer control and transport are performed. The transport may be RTP/UDP/IP or AAL2 for transport of user data. The bearer control over Nb is FFS, it may be based on RTP, H.245 or corresponding. [Note: in the general R’00 architecture different options for user data transport and bea... |
8a9283a656db20cd080be5c53231664c | 23.922 | 6 QoS | The work currently being done within the S2 QoS Ad Hoc is reflected within TR 23.907 and the QoS section of TR 22.105. The R99 version of these specifications will support real time applications on a packet switched network which includes the ability of UMTS to transparently support multi‑media applications that utili... |
8a9283a656db20cd080be5c53231664c | 23.922 | 7 Handover | Within this section, the topics to be studied and standardised to support handover for real time services in the PS domain have been identified. This section has investigated various handover scenarios, however the fact that the scenario has been studied here does NOT imply a requirement for the support of that scenari... |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.1 SRNC Relocation within a UMTS R00 IP network | Within UMTS, work has already been undertaken to provide handover for real time PS domain services. The UTRAN does not distinguish between circuit and packet services, it simply provides for real and non-real time services, hence Intra RAN handover for real time services is available. |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.1.1 Support Required within ERAN | The goal of the All IP architecture is to provide a common core network for both UTRAN and ERAN. The specification of this work is outside the scope of this study, however, it is worth noting that the ERAN will need to support the following procedures:
• SRNC Relocation
• Mobile Assisted Network Controlled handover for... |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.1.2 All IP UTRAN to All IP ERAN Handover | The need to support this handover scenario is for FFS.
In this scenario, a CSCF will support terminals in both the ERAN and the UTRAN. The terminal will have access to the same Media Gateway from both RANs, hence the same media codec will be used in the network. |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2 SRNC Relocation/Handover Between All IP and CS Domain/GSM | |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2.1 Requirement | The need to support these handover scenarios is for FFS.
The expected scenarios:
• Inter system handover, where target system does not support the necessary RT requirements for its packet domain (e.g. Inter system hand-over towards R97)
To fulfill this potential requirement, 2 solutions have been currently proposed (ot... |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2.2 Solution with CSCF supporting MAP E | The following text considers the scenario when a UE has at least one session active which involves the CSCF.
On receipt of an SRNC relocation required message, the SGSN determines that the SRNC relocation results in a change of SGSN to one, which does not support the All IP services. One option is to force the serving... |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2.3 Inter-System handover using the ISHF | The mechanism described in this section, identifies a new functional element, the ISHF. This isolates MAP/E from the CSCF. Further work is required to identify if this approach, or the approach of supporting MAP/E on the CSCF (see section 7.2.2) should be adopted. |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2.3.1 General | Based on the handover requirements given in Table 4-1, the following intersystem handover scenarios should be accommodated by the All IP architecture.
• UMTS R 00 IP network to/from 2G GSM network handover
These procedures listed shall not require change to the terminal.
Figure 7-1: Support of InterSystem Handover
To s... |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2.3.2 UMTS R 00 IP network to/from 2G network handover | This example shows how handover (Hard Handover) is performed from UMTS R 00 IP network to a legacy GSM network. This demonstrates the signaling required between the networks and assumes a trunk circuit bearer between the networks. Other bearer connection schemes are possible, but not addressed in this example. (Note ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.3 Areas for Further Study | The following areas may require further study.
• Bearer set-up/control between networks during handover
• Anchoring bearer in the UMTS R 00 IP network
• MAHO support
• Inter-RNC Soft handover
• Inter RAN to RAN of same type streamlining
• Inter RAN to RAN of different type streamlining |
8a9283a656db20cd080be5c53231664c | 23.922 | 8 Radio Aspects | Note: This section requires support from the RAN group. |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.1 General | 1) CN – RAN interface definition
(a) Functional split between CN and RAN- new radio access network called EGPRS Radio Access Network (ERAN) is considered. The interface between the radio access network such as ERAN or UTRAN and the CN needs to be defined/extended and should allow different air interface technologies t... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2 Airlink Optimisation for Real-Time IP | |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.1 Introduction | In the all-IP architecture, a fundamental objective is to support IP-based real-time and non real-time traffic for a mobile terminal while achieving spectral efficiency and error robustness. In the case of real-time voice, spectral efficiency and error robustness have a performance baseline coming from the current cell... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.2.1 Full opacity (no adaptation) | The UPA has no knowledge of the internal structure of the headers or payload, and no transformation is done on the IP/UDP/RTP headers which are sent in full over the air interface. Error protection is applied evenly to all the bits in the header, and evenly to all the bits in the payload. The header part will likely re... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.2.2 Payload opacity (header adaptation only) | In this case, the UPA only needs to know the internal structure of the IP/UDP/RTP header but not of the payload. Only the headers are adapted, either by header compression or header stripping. |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.2.2.1 Header compression/decompression | IP/UDP/RTP headers are compressed before transmission over air interface and decompressed at the receiving end. Like before, headers require stronger error protection than payload. The most wellknown header compression algorithm is the Van Jacobson algorithm (RFC 1144, Compressing TCP/IP Headers for low speed serial li... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.2.2.2 Header stripping/regeneration | IP/UDP/RTP headers are stripped before transmission over air interface and regenerated at the receiving end. Essentially only the payload is transmitted, but some additional header-related information needs to be transmitted to enable the header regeneration. The degree of header transparency achieved is variable, depe... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.2.3 No opacity (full adaptation) | The UPA knows the structure of the headers and the payload. Headers can be compressed or stripped. In addition, payload transmission is optimised by techniques such as unequal bit protection, channel and error coding optimised for the payload structure, etc. |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.3 Application to all-IP network | The all-IP network is expected to provide real-time bearer services intended to carry
• Basic conversational voice (service equivalent to voice in current cellular)
• Real-time Multimedia (includes voice which is seen as a component of multimedia) |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.3.1 Basic voice | For basic voice, the emphasis is on meeting and if possible exceeding the baseline of traditional cellular in terms of spectrum efficiency, error robustness and voice quality. Traditional cellular systems achieve that baseline by using well known techniques such as unequal bit protection, channel and error coding optim... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.3.2 Real-Time multimedia | Real-time multimedia is a new service that does not exist in traditional 2G cellular systems. A new bearer is proposed. For that bearer, transparency for all the IP/UDP/RTP fields is crucial. Under the transparency constraint, we want to optimise spectrum efficiency and error robustness, but unlike voice, there is no b... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.3.3 Pure IP | The Pure IP service can be provided to accommodate end-to-end protocols such as IPSEC. In order to achieve this accomodation, the bearer does not do any adaptation and corresponds to the "No adaptation" case above. Header adaptation may also apply for Pure IP. Specific algorithms for header adaptation shall be evalua... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.4 Conclusions | IP/UDP/RTP packets require adaptation to the radio link to meet the spectrum efficiency and error robustness requirements of cellular systems. It shall be investigated if a single scheme can simultaneously and fully meet the above requirements and IP transparency. An alternative to a single scheme is a gradation of sc... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9 Call Control | 9.1 Terminology for Call Control
The terminology in this section is that terminology used that is new or has been changed from that defined for R99. The terminology defined in this section has not been the object of a real debate and hence cannot be considered as agreed. This section needs to be aligned with the term... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.2 Assumptions | The following assumptions have been considered in the development of the roaming models described in the present version of the document.
1 The addressing requirements and mechanisms will be based on the requirements and mechanisms identified by 3GPP in 3G TR 22.975 and 3G TS 33.003.
2 Call admission/denying and call r... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3 Roaming Within All IP networks | In the follow, a set of roaming scenarios is described.
Editor's Note: please note that the network interfaces and the names shown in the diagrams from 6.4 to 6.7 may not always be correct. |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.1 Call Model | The call model described by the following statements has been adopted in the present document:
• Calls from/through PSTN are routed to an MGCF with connectivity to the Home Network corresponding to the dialled DN.
• Calls from a Release 2000 all IP network to a different Release 2000 all IP networks originated with a D... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.2 Scenario 1, Traditional Model | The following pictures show respectively the roaming scenario 1 applied to roaming inside a single network and applied to roaming between networks.
Figure 9-2: Scenario 1 applied to roaming inside a single network
Figure 9-3: Scenario 1 applied to roaming between networks
The following points characterise scenario 1:
•... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.3 Scenario 2 | The following pictures show respectively the roaming scenario 2 applied to roaming inside a single network and applied to roaming between networks.
Figure 9-4: Scenario 2 applied to roaming inside a single network
Figure 9-5: Scenario 2 applied to roaming between networks
The following points characterise scenario 2:
•... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.4 Scenario 1: Information Flows for Validation | In order to validate scenario 1 proposed above, information flows for registration, location management and call delivery/origination are provided in this section.
The information flows presented in the Call Control and Roaming proposal do not provide many details. Generic names have been chosen for signalling messages... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.4.1 Registration and Location Management | • In this version of the Technical Report, only a basic registration procedure is considered.
• The basic registration procedure is composed of three steps:
• GPRS attach: is a plain GPRS attach procedure;
• PDP context activation: a PDP context is set up to support application level signalling;
• application level reg... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.4.2 MT/MO Calls | Two call information flows are presented in this version of the Technical Report. The call flows are based on the following call delivery model:
• a call from PSTN towards a DN corresponding to the user is received by one of the MGCF of the Home Network, ISP or corporate LAN domain in the IP multimedia network;
• MGCF ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.4.2.1 Incoming call from PSTN to a Release 2000 all IP network | The following flow describes the call delivery for a MT call from PSTN to a Release 2000 all IP network user addressed through a DN.
Figure 9-7: Incoming call from PSTN to a Release 2000 all IP network
Issues such as QoS negotiation, policy management, etc. are FFS. |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.4.2.2 Call from an 3GPP IP based network/Multimedia IP Network to 3GPP IP network | The following flow assumes that a Release 2000 all IP network user has roamed into a visited network. The flow describes a call from a different Release 2000 all IP network terminated into the home domain of the called user. It is assumed that the Release 2000 all IP network where the call is coming from, is aware of ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.5 Scenario 2: Information Flows for Validation | No flow will be shown for this version of the document. |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.4 Roaming to Other Networks | In order to ensure compatibility and easy roaming between 2G GSM/GPRS, UMTS R99 and UMTS R00 CS and GPRS domain (excluding the VoIP/multimedia domain), the same mobility procedures are used within and between the 3 kind of networks (storage of the current location in the HSS, use of MAP to update the HSS with the curre... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.4.1 Roaming Procedures for R00 networks | One possible solution for the support of roaming in R00 networks is described in Tdoc S2k99117. The contribution covers both roaming between R00 networks and roaming to mobile legacy networks. The contribution only covers the PS-only architecture in UMTS R00. Roaming from UMTS R99 considered in this document is in term... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.4.2 Overlaid solution to roaming | One roaming solution is to introduce an overlaid personal number service, which keeps track of users registrations (attached to 2G/3G CS and/or PS MultiMedia) and call reception preferences. This enables inter-service as well as inter network roaming for Telephony as classical TeleService Speech in 2G/3G networks and T... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.5 Open Issues | The following issues need to be discussed and solved through interaction with the other working groups in Release 2000 all IP network and might require discussion in the plenary.
• Support of multiparty voice and data communications sessions (including the capability for the user or service logic to dynamically add or ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 10 Service Platform Impacts | |
8a9283a656db20cd080be5c53231664c | 23.922 | 10.1 3GPP Release 2000 Service Architecture | This section describes how the 3GPP release 99 service architecture [3] can be applied to the 3GPP release 2000 network by extending the VHE/OSA concept to the Multi-Media core network. This can be done by providing an application interface (as described in VHE specification [3]) from the CSCF, see Figure 10-1.. As VH... |
8a9283a656db20cd080be5c53231664c | 23.922 | 10.2 IN based Services | The IN based service is one example of legacy services and the IN based service logic is one example of how legacy services may be introduced to the 3GPP Release 2000 networks. This IN based service logic may need to be enhanced in 3GPP Release 2000 networks, based on the proposed architecture, when full support for ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 10.3 Issues requiring further contributions | The following issues require further contributions:
• Applications may reside not only in Application Servers (AS) but also in terminals.
• Options for sharing applications or parts of them between AS and terminals
• Which elements, beside the CSCF, will provide API for application design (aligned with VHE/OSA)
• Termi... |
8a9283a656db20cd080be5c53231664c | 23.922 | 11 Security | There will be a common authentication scheme for the terminals operating in the all-IP mode, which will be SIM/USIM based. It is required that all-IP terminals will be able to register and provide basic service when used with a 3GPP SIM/USIM.
12 Work Plan |
8a9283a656db20cd080be5c53231664c | 23.922 | 12.1 Milestones for Release 00 | 3GPP has the objective of producing the second release of specification for UMTS by the end of 2000. The project management for this work will need to include the elements of work package definition, the interdependency of these work packages and their scheduling. As the work is undertaken in the various TSGs and WGs i... |
8a9283a656db20cd080be5c53231664c | 23.922 | 12.1.1 Release 00 milestones | 3GPP has not yet agreed overall milestones for release 00. For the purposes development of a high-level work plan the following key milestones are proposed.
July 99 3GPP All-IP network feasibility study started
Sept 99 TSG-S2 R00 Ad Hoc will submit the results of the TSG-S2 for approval
Oct 99 After TSG-S2 approval,... |
8a9283a656db20cd080be5c53231664c | 23.922 | 12.1.2 Detailed activity plan | Date
Meeting group
Proposed activity
August 23 – 27
S2
Progress architectural study
September 13 - 17
S2
Joint S1 – S2 activity on R00 - Finalize the requirements for the architectural study and identify the key issues. Finalize the proposed R00 architecture at the TSG-S2 R00 ad hoc group.
Late September/early October... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 1 Scope | The present document specifies the overall requirements for 3G Fault Management as it applies to the NE, EM and NM.
Clauses 4 and 5 define the fault management concept and functional requirements for the detection of faults and the generation, collection and presentation of alarms, operational state data and test resul... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 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... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 3 Definitions and abbreviations |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.