hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.1.4.1 Scenario Number 1 | The prepaid subscriber wishes to recharge their account with a voucher and query their account balance. The subscriber uses their mobile phone or other wireline phone to interact with an IVR system. In order to recharge their account, the subscriber must enter the voucher number, the MSISDN to be recharged , and PIN(... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.1.4.2 Scenario Number 2 | Directly recharging (i.e. without a voucher) works much along the same way. In this case, we assume the prepaid subscriber interacts with a web page. After providing the MSISDN, along with the PIN, the user can query the account balance (getBalance). For recharging, the subscriber must enter payment details, for exa... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.1.4.3 Scenario Number 3 | Every time a subscriber makes a telephone call the balance of their prepaid account is decremented with the cost of the call. When a recharge is done, the balance is increased either directly (balanceUpdate) or with an amount represented by a voucher (voucherUpdate). When a subscriber has doubts about the correctness... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2 Account Management API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• getBalance
• getCreditExpiryDate
• balanceUpdate
• voucherUpdate
• getHistory
Note that certain parameters are negotiated off line. For example the reseller identifi... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2.1 Account Balance Query | getBalance(EndUserIdentifier endUserIdentifier, String endUserPin, out Decimal amount)
b) Behaviour:
This message results in getting account balance indicated by the end user identifier and associated end user PIN. The returned amount is specified as a currency amount.
c) Parameters:
NAME
TYPE
DESCRIPTION
endUserIdent... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2.2 Account Credit Expiration Date Query | a) getCreditExpiryDate(EndUserIdentifier endUserIdentifier, String endUserPin, out DateTime date)
b) Behaviour:
This message results in getting the expiration date of the credit indicated by the end user identifier and associated end user PIN. The returned date is the date the current balance will expire. Nil is retu... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2.3 Account Balance Recharging | a) balanceUpdate(EndUserIdentifier endUserIdentifier, String endUserPin, String referenceCode, Decimal amount, Integer period)
b) Behaviour:
This message results in directly recharging the account indicated by the end user identifier and optional associated end user PIN. The reference code is used to uniquely identify ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2.4 Account Balance Voucher Recharging | a) voucherUpdate(EndUserIdentifier endUserIdentifier, String endUserPin, String referenceCode, String voucherIdentifier, String voucherPin)
b) Behaviour:
This message results in directly recharging the account indicated by the end user identifier and optional associated end user PIN. The reference code is used to uniqu... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.2.5 Account Transaction History Query | a) getHistory(EndUserIdentifier endUserIdentifier, String endUserPin, DateTime date, Integer maxEntries, out DatedTransaction[] history)
b) Behaviour:
This message results in returning the transaction history of the account indicated by the end user identifier and associated optional end user PIN. The maximum number o... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.3 Web Service Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.3.1 Data Types | In addition to the Common Data Types defined in clause 5.1, the following Data Types are specific to this Web Service. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.3.1.1 DatedTransaction | The DatedTransaction data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
transactionDate
DateTime
The date the transaction occurred.
transactionDetails
String
The transaction details. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.3.2 Exceptions | In addition to the Common Exceptions defined in clause 5.2, there are exceptions specific to this Web Service. Similar to the Common Exceptions, each Web Service-specific exception is assigned an eight-character identifier. This identifier is interpreted as described in clause 5.2, except that the first 3 characters u... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 11.4 Web Service Syntax – WSDL | The W3C WSDL representation of this API is contained in a set of files which accompany the present document (see Annex A).
The rpc/literal files are
• parlayx_account_management_types.xsd
• parlayx_account_management_service_port.wsdl
• parlayx_account_management_service.wsdl
The rpc/encoded file is
• parlayx_account_m... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12 User status | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1 Overview | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.1 Description | The Parlay X User Status Web Service will be used for getting user status information. The use of the Web Service will not require any specific telecommunication skills. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.2 Commercial & Technical Rationale | The use of a Parlay X User Status Web Service will enable fast and easy development of user status aware applications. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.3 Relationship to Similar or Supplanted Specifications | The Parlay/OSA Mobility (User Status) Service API can also provide user status information, but the Parlay X API for this Web Service is easier to use.
The Parlay/OSA Presence and Availability Management Service specifies a set of interfaces for applications that provide broader presence and availability capabilities t... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.4 Scenarios | In the following, two sample Scenarios are described. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.4.1 Buddy-list | This application is a mobile version of services like ICQ, MSN Messenger Service and Yahoo! Messenger, which offer text and voice chat and text conferencing. With a mobile terminal the user can be always on.
The user of the service can define one or more buddy-lists containing their friends (alternatively their family,... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.1.4.2 Manual call routing | When a switchboard receives a call, the switchboard operator may obtain the status of a mobile terminal before trying to route the call to it. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.2 User Status API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• getUserStatus |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.2.1 Get User Status | a) getUserStatus(EndUserIdentifier endUser, EndUserIdentifier requester, out UserStatusData userStatus)
b) Behaviour:
Requests the user status information of a user. Before returning the user status indicator, end-user and operator policies must be satisfied.
c) Parameters:
NAME
TYPE
DESCRIPTION
endUser
EndUserIdentif... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.3 Web Service Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.3.1 Data Types | In addition to the Common Data Types defined in clause 5.1, the following Data Types are specific to this Web Service. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.3.1.1 UserStatusData | The UserStatusData data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
userStatusIndicator
UserStatusIndicator
It indicates the status of the end user.
additionalUserStatus
Information
String
A string to hold additional information if the userStatusIndicator is 'Other'. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.3.1.2 UserStatusIndicator | The UserStatusIndicator data type is an enumeration with the following values:
VALUE
DESCRIPTION
Online
User is online.
Offline
User is offline (mobile terminal switched off/other terminal not connected to the service), or wants to appear to be offline.
Busy
User is busy.
Other
Custom user status information can be ret... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.3.2 Exceptions | All exceptions thrown by this Web Service are Common Exceptions, as defined in clause 5.2. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 12.4 Web Service Syntax – WSDL | The W3C WSDL representation of this API is contained in a set of files which accompany the present document (see Annex A).
The rpc/literal files are
• parlayx_user_status_types.xsd
• parlayx_user_status_service_port.wsdl
• parlayx_user_status_service.wsdl
The rpc/encoded file is
parlayx_user_status_service.wsdl |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13 Terminal Location | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1 Overview | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1.1 Description | The Parlay X Terminal Location Web Service will be used for getting location information. The use of the Web Service will not require any specific telecommunication skills, but knowledge of location co-ordinates will be required. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1.2 Commercial & Technical Rationale | The use of a Parlay X Terminal Location Web Service will enable fast and easy development of location aware Applications. The use of the Web Service will only require knowledge of longitude and latitude from the World Geodetic System 1984 (WGS 84), which is the reference system chosen for the coding of locations.
The m... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1.3 Relationship to Similar or Supplanted Specifications | The Mobile Positioning System (MPS) offers much of the same functionality that the Parlay X Terminal Location Web Service will offer. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1.4 Scenarios | In the following, a sample Scenario is described. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.1.4.1 Location enabled Buddy-list: | This application is a mobile version of services like ICQ, MSN Messenger Service and Yahoo! Messenger, which offer text and voice chat and text conferencing. With a mobile terminal the user can be always on, and the service can also show where buddies are located.
The user of the service can define one or more buddy-li... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.2 Terminal Location API | This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:
• getLocation |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.2.1 Get Location of Terminal | a) getLocation(EndUserIdentifier endUser, EndUserIdentifier requester, LocationAccuracy accuracy, out LocationInfo location)
b) Behaviour:
Requests the location of one terminal. The location is returned if the terminal is available. Before returning the location, end-user and operator policies must be satisfied.
c) Par... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.3 Web Service Data Definitions | |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.3.1 Data Types | In addition to the Common Data Types defined in clause 5.1, the following Data Types are specific to this Web Service. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.3.1.1 LocationInfo | The LocationInfo data type is a structure containing the following parameters:
NAME
TYPE
DESCRIPTION
longitude
Float
Longitude
latitude
Float
Latitude
accuracy
LocationAccuracy
How accurate the Location information is. If the degree of accuracy wanted is available this should be given, if not the best possible accuracy... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.3.1.2 LocationAccuracy | The LocationAccuracy data type is an enumeration with the following values: (Each Parlay X Gateway operator must specify the uncertainty radiuses for Low, Medium and High)
VALUE
DESCRIPTION
Low
Low accuracy i.e. < 3 km radius of uncertainty.
Medium
Medium accuracy i.e. < 1 km radius of uncertainty.
High
High accuracy ... |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.3.2 Exceptions | All exceptions thrown by this Web Service are Common Exceptions, as defined in clause 5.2. |
e3edf551830c62df14a4eaeee607bff5 | 29.199 | 13.4 Web Service Syntax – WSDL | The W3C WSDL representation of this API is contained in a set of files which accompany the present document (see Annex A).
The rpc/literal files are
• parlayx_terminal_location_types.xsd
• parlayx_terminal_location_service_port.wsdl
• parlayx_terminal_location_service.wsdl
The rpc/encoded file is
parlayx_terminal_locat... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 1 Scope | The present document provides an overview of the architecture and issues related to the provision of voice optimisation within the GERAN. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
[1] 3G TS 26.090, "Adaptive Multi-Rate (AMR) speech transcoding".
[2] 3G TS 26.190, "AMR Wideband speech codec, Transcoding functions".
[3] IETF AVT internet-draft "RTP, A Transport P... |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 3 Definitions, symbols and abbreviations | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 3.1 Definitions | |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 3.1.1 Terminal integrated application | In this document the term “Terminal integrated application” is used. An application is considered to be “integrated in the terminal” when the application is co-located with the PDCP and RRC protocol entities. |
1549644dc078ef9fd6712bc573d8101d | 43.900 | 3.2 Symbols | Editors note: to be completed |
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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.