hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
1549644dc078ef9fd6712bc573d8101d | 43.900 | 3.3 Abbreviations | SIP Session Initiation Protocol
DTM Dual Transfer Mode
CS Circuit Switched
GERAN GSM/EDGE Radio Access Network
FACCH Fast Associated Control Channel
RTP Real time Transport Protocol
UDP User Datagram Protocol
IP Internet Protocol
UL Uplink
DL Downlink
TS Time Slot
CN Core Network
SS Subsystem |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 4 Overall description of voice over IP in the IMS domain when connected to GERAN | GERAN is considering the solution to provide an optimized voice bearer as well as generic bearers to support speech originating from the Iu-ps. The optimization is achieved by reusing the channel coding of CS speech channels in GSM, and by employing header removal to increase the spectrum efficiency. The consideration ... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 6.1 Requirements | 1. It shall be possible to use a SIP based optimised voice service with a mobile terminal supporting multi slot class 1 (1 TS in DL, 1 TS in UL).
2. There shall be no performance degradation in coding and modulation compared to traditional circuit switched voice services.
3. GERAN shall not interpret SIP messages.
4. ... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 6.2 Working assumptions | 1. It is unclear when/whether mid path transcoders for the IMS will be available between two SIP end users.
2. TSG GERAN is responsible to develop the header removal solution for an Optimized Voice bearer.
3. GERAN informs the MS which codecs are currently supported and the MS is in charge of identifying a single code... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.0.1 Summary of GERAN/MS States for IMS Calls with Header Removal | A number of events have been identified. These are:
1. At some point, MS is made aware of current local Codec/Channel Coding Support
Note: This information may no longer be accurate by the time that the GERAN needs to allocate a bearer, due to changes in resource availability
2. MS has PDP Context for SIP traffic
3. ... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 10.1 PDCP Mode change from HR to HC is part of an Inter-RAT change from GERAN to UTRAN | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 10.2 PDCP HR to HC mode change occurs within GERAN | 11. Handover occurs, together with a PDCP mode change from Header Compression to Header Removal. This has two variants: |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 11.1 There is also an Inter-RAT change from UTRAN to GERAN | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 11.2 PDCP mode change without such an Inter-RAT change" | Note: Some of these events (notably those involving complex handover cases) are not covered within the Technical Report. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.0.2 PASNAS Information Structure | A group of data items can be used to assist the PDCP processor in selecting the appropriate scheme to be used when performing packet adaptation within the RAN. It can be viewed as a set of “suggestions” from the MS to the RAN. This information is doubly optional:
7 the MS need not send it (relying on default behaviour ... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.1 Optimized voice call set-up within the IMS | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.1.1 Description of | Call set-up in the CS domain is based on the following principle:
1. The terminal announces its capabilities
2. The network select speech codec to be used
Call set-up in the IMS domain is based on a fundamentally different principle:
1. The terminal endpoints negotiate speech codec (or more generally media codecs) to b... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.1.2.1 MS knowledge of GERAN channel coding capabilities at the start of or before SIP negotiation | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.1.2.1.1 Description of the solution | This solution is based on the principle of letting the peer involved in the SIP call set-up know about the capabilities of the GSM/EDGE Radio Access Network (e.g. supported channel codings in the cell). Such knowledge has to be provided prior to, or during, the SIP-based call set-up. Several solutions are possible:
◦ ... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.2 Handling of ACS for AMR | In case of optimized speech with AMR codec there are additional issues that are related to managing the ACS as listed
7.2.1 Max four AMR modes can be part of an ACS I GERAN, at a time
7.2.1.1 Description of problemIn case of a session between GERAN MS and some other IP terminal, the IP terminal (somewhere in the IP cl... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.2.4 How to force a change to an AMR rate able to be carried on a HR physical channel | 7.2.4.1 Description of problem
There may bea need to change from Full Rate to Half Rate channels. This may be the case in high traffic load situations. It may also be necessary if DTM is used for SIP signalling and only one TS in UL and DL can be used (also refer to chapter 7.9).
7.2.4.2 Description of solutions
,
7.... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.3.2.1.2 Pros and cons | + no impact to CN
+ if header removal is not to be applied to the media stream, the RB setup procedure remains unchanged (except for the transfer of the “Header Removal Supported” flag from the BSC to the MS and the “Header Removal Allowed” flag set to false from the MS back to the BSC).
• Two more messages will be re... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.3.2.2 SDU format information approach | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.3.2.2.1 Description of the solution | Detailed QoS information is provided in the ‘Activate PDP context request’ message by using the ‘SDU format information’ attribute. This information uniquely identifies the appropriate channel coding in the GERAN. However, ‘SDU format information’ would have to be introduced in R5.
For multi rate codecs such as AMR, it... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.3.2.2.2 Pros and cons | - The solution proposed does not specify how a potential future codec is uniquely identified if that codec has exactly the same bit mapping and protection for each class of bits in the payload format of an existing codec. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.3.2.3 Activate PDP context request message approach | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.3.2.3.1 Description of the solution | Following the SIP negotiation, which needs to result in one desired codec, the UE expresses this request explicitly by stating the desired codec in the subsequent resource request to the network. A field containing the specific speech codec desired is introduced in the ‘Activate PDP context request message’ to the SGSN... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.3.2.3.2 Pros and cons | + This solution is straightforward and imposes limited changes to existing standards. It is architecturally clean in that it uses existing messages for resource requests from the UE to GERAN. The codec information can potentially be used by other purposes as well, for example charging.
- Its potential drawback is that ... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.5.2.1 Activate PDP context request message approach | 7.5.2.1.1 Description of the solution
This solution is based on the principle of providing the information whether or not header removal is allowed in the Activate PDP context request message. Several solutions have been presented how to name these bits:
1. ‘Header removal allowed’ bit.
2. ‘This flow may be synchronize... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.5.2.1.2 Pros and cons | + This solution has the advantage that it implies very limited changes to existing specifications.
- A possible drawback is that that higher protocol messages such as the PDP context messages have to convey header adaptation information, which can be considered as being radio access related. Given the nature of optimi... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.5.2.2 Direct communication between the UE and the BSC | A different method is used to indicate that HR is possible when using the direct communications approach (see section 7.3.2.1.1). |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.5.3 Working assumption | No agreement reached so far.
7.6 IP and port number information transfer from MS to GERAN
7.6.1 Description of problem
In order to carry out header regeneration in the uplink the relevant information must be communicated with the PDCP entity in the GERAN. A number of possibilities have been identified, so far, in ord... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.6.2.1 RRC signalling approach | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.6.2.1.1 Description of the solution | The information is provided by RRC signalling at RB set-up. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.6.2.1.2 Pros and cons | Editors note: To be completed. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.6.2.2 TFT approach | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.6.2.2.1 Description of the solution | The information is sent in a TFT from the MS to SGSN, which in turn provides the information to the BSC. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.6.2.2.2 Pros and cons | Editors note: To be completed. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.6.2.3 Direct communication between the UE and the BSC | A slight variation on the RRC signalling method is used when using the direct communications approach (see section 7.3.2.1.1). The data is included within the message sent by the MS during the extended RB setup procedure.
7.6.3 Working assumption
Currently solution 7.6.2.1 seems to be the most promising solution. Howe... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.7.1 Description of problem | When inter BSS, inter RAN or BSS-RAN handover takes place, the header generation context may have to be relocated. A mechanism for this purpose is needed. In addition, it should be clarified how slips in RTP sequence numbers and timestamps can be minimized or completely eliminated.
7.7.2 Proposed solutions |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.7.2.1 Time stamp and sequence number handling during a handover | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.7.2.1.1 Description of the solution | This solution assumes that handover is carried out as specified in 44.018 and that relocation follows the procedures that have been specified in 25.413 and 23.060. As a part of the relocation of the RNS context the location of the header removal / generation function is moved from the source BSS to the target BSS.
In t... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.7.2.2 Pros and cons | - The proposed solution may lead to small drift in the transferred field values. It is the assumption that this does not cause large quality degradation. However, this needs to be verified from IETF AVT group. The size of the drift will be directly proportional to the number of muted or discarded frames as explained in... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.8 Mid call legacy codec support | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.8.1 Description of problem | The Radio Access Network infrastructure may not support all possible channel coding schemes in all areas, and, potentially, the set of channel coding schemes supported in one area may be completely different from the set supported elsewhere. If an IMS call is active and uses Header Removal (and so relies on an unequal ... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.8.2.1 PDCP Mode Change | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.8.2.1.1 Description of the solution | Editors note: To be completed |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.8.2.1.2 Pros and cons | Editors note: To be completed
7.8.2.2 Mid Call Codec Change
It is assumed that the call control entities must maintain a valid specification of the media transport in use.
If the codec used is to change in mid-call to one not specified in the existing session description, then the description agreed by the SIP end p... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.8.2.2.1 Description of the solutions | 1. SIP call re-negotiation
[Standard IMS procedure as will be described in TS24.228]
2. Non-SIP Codec change signalling
If a media description, at the end of call set up phase, includes a set of alternative CoDecs with more than one member, then a change in CoDec between these listed alternatives would not invalidate t... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.8.3 Working assumption | The current working assumption is based on SIP codec renegotiation 7.8.2.2.1-1. All other schemes as described in this chapter are FFS.
7.9 Bearer support for mid call SIP signalling |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.9.1 Description of problem | It is foreseen that there may be additional mid call IMS SIP communication using header removal. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.9.2 Solutions | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.9.2.1 Solution A | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 7.9.2.1.1 Description of the solution | The following means can be used for SIP signalling:
3. FACCH
4. Downgrade to HR channel. This requires further analysis of:
a. TBF allocations for signalling
b. The codec selected at the SIP negotiation must be able to be reconfigured to support a HR channel, without SIP level renegotiation.
5. Allocation of additional... |
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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.