3GPP2 C.S0085-A

 Version 1.0

 Date: April, 2009




                          VoIP Codecs and Protocols




© 3GPP2 2009...
C.S0085-A v1.0         VoIP Codecs and Protocols


 1
 2   No Tex t
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
...
C.S0085-A v1.0                                                            VoIP Codecs and Protocols


 1
 2   Foreword
 3
...
C.S0085-A v1.0                                                           VoIP Codecs and Protocols


 1
 2
 3
 4   Scope
 ...
C.S0085-A v1.0                                                                                                            ...
C.S0085-A v1.0                                                                       VoIP Codecs and Protocols


 1
 2
 3 ...
C.S0085-A v1.0                                                                           VoIP Codecs and Protocols


 1
 2...
C.S0085-A v1.0                                                                 VoIP Codecs and Protocols


 1             ...
C.S0085-A v1.0                                                                        VoIP Codecs and Protocols


 1
 2
 3...
C.S0085-A v1.0                                                                        VoIP Codecs and Protocols


 1
 2
 3...
C.S0085-A v1.0                                                                          VoIP Codecs and Protocols


 1
 2
...
C.S0085-A v1.0                                                                          VoIP Codecs and Protocols


 1    ...
C.S0085-A v1.0                                                                          VoIP Codecs and Protocols


 1
 2
...
C.S0085-A v1.0                                                 VoIP Codecs and Protocols


 1                    o    TxT2...
C.S0085-A v1.0                                                 VoIP Codecs and Protocols


 1
 2
 3               • PowerP...
C.S0085-A v1.0                                          VoIP Codecs and Protocols


 1               • T2PInflowRangeNN (N...
C.S0085-A v1.0                                                                       VoIP Codecs and Protocols


 1
 2
 3 ...
C.S0085-A v1.0                                                                  VoIP Codecs and Protocols


 1            ...
C.S0085-A v1.0                                                                       VoIP Codecs and Protocols


 1
 2
 3 ...
C.S0085-A v1.0                                                                          VoIP Codecs and Protocols


 1
 2
...
C.S0085-A v1.0                                                                       VoIP Codecs and Protocols


 1
 2
 3 ...
C.S0085-A v1.0                                                                         VoIP Codecs and Protocols


 1
 2
 ...
C.S0085-A v1.0                                                                           VoIP Codecs and Protocols


 1   ...
C.S0085-A v1.0                                                                          VoIP Codecs and Protocols


 1    ...
C.S0085-A v1.0                                                                        VoIP Codecs and Protocols


 1      ...
C.S0085-A v1.0                                                                               VoIP Codecs and Protocols


 ...
C.S0085-A v1.0                                                                                  VoIP Codecs and Protocols
...
C.S0085-A v1.0                                                                          VoIP Codecs and Protocols


 1   9...
C.S0085-A v1.0                                                                              VoIP Codecs and Protocols


 1...
C.S0085-A v1.0                                                                                 VoIP Codecs and Protocols

...
C.S0085-A v1.0                                                                               VoIP Codecs and Protocols


 ...
C.S0085-A v1.0                                                                             VoIP Codecs and Protocols


 1
...
Upcoming SlideShare
Loading in...5
×

VoIP Codecs and Protocols

794

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
794
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
22
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

VoIP Codecs and Protocols

  1. 1. 3GPP2 C.S0085-A Version 1.0 Date: April, 2009 VoIP Codecs and Protocols © 3GPP2 2009 COPYRIGHT NOTICE 3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information
  2. 2. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 No Tex t 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 © 3 GPP2 2 0 0 9 58 i 3GPP2
  3. 3. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 Foreword 3 4 This technical specification recommends codecs as well as protocol configuration for efficient 5 6 support of VoIP over HRPD 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 ii 3GPP2
  4. 4. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 4 Scope 5 6 This technical specification recommends codecs as well as protocol configuration for efficient 7 support of VoIP over HRPD. Recommendations are provided for parameter values for transport 8 9 protocols, RoHC, RLP and RLMAC. Also a pre-configured provisioned session is also defined 10 for use in supporting non-authorized access for VoIP emergency services 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 i 3GPP2
  5. 5. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 4 Contents 5 6 Foreword....................................................................................................................................................................... ii 7 Scope ..............................................................................................................................................................................i 8 Contents .........................................................................................................................................................................1 9 1 Introduction ..........................................................................................................................................................2 10 2 References ............................................................................................................................................................3 11 3 Definitions, Symbols and Abbreviations .............................................................................................................5 12 3.1 Symbols and Abbreviations.............................................................................................................................5 13 4 SDP Offer/Answer ...............................................................................................................................................6 14 5 Media ...................................................................................................................................................................7 15 5.1 Voice ...............................................................................................................................................................7 16 5.1.1 Narrowband .........................................................................................................................................7 17 5.1.2 Wideband ............................................................................................................................................7 18 5.2 VoIP Transport ................................................................................................................................................7 19 5.2.1 RTP Header and Packetization ............................................................................................................7 20 21 5.2.2 Header Compression ...........................................................................................................................7 22 6 HRPD System Configuration for VoIP Flow .......................................................................................................9 23 6.1 RLP (Radio Link Protocol) Configuration ......................................................................................................9 24 6.2 RLMAC (Reverse Link Medium Access Control) Configuration ...................................................................9 25 7 HRPD System Configuration for SIP Flow ....................................................................................................... 13 26 7.1 RLP (Radio Link Protocol) Configuration .................................................................................................... 13 27 7.2 RLMAC (Reverse Link Medium Access Control) Configuration ................................................................. 13 28 8 QoS Configuration/Activation ........................................................................................................................... 15 29 9 Emergency Services ........................................................................................................................................... 16 30 9.1 Authorized Terminals .................................................................................................................................... 17 31 9.1.1 Establishing an HRPD Session with the Access Network ................................................................. 17 32 9.1.2 Configuring QoS for VoIP and SIP Flows ........................................................................................ 17 33 9.1.3 Accessing the HRPD Access Network to Establish Air Link Resources .......................................... 17 34 9.1.4 Activating QoS for VoIP and SIP Flows ........................................................................................... 18 35 9.2 Non-Authorized Terminals............................................................................................................................ 18 36 9.2.1 Pre-configured HRPD Session .......................................................................................................... 18 37 38 9.2.1.1 PriorSessionGAUP Not Supported.................................................................. 18 39 9.2.1.2 PriorSessionGAUP Supported......................................................................... 20 40 9.2.2 HRPD Protocol and Application Configuration for Emergency Services VoIP and SIP Flows ....... 21 41 9.2.2.1 Session Configuration Protocol ....................................................................... 22 42 9.2.2.2 Stream Protocol ............................................................................................... 23 43 44 9.2.2.3 Enhanced Multi-Flow Packet Application ...................................................... 24 45 9.2.3 HRPD system Configuration for SIP Flow ....................................................................................... 25 46 9.2.3.1 Enhanced Multi-Flow Packet Application ...................................................... 25 47 9.2.3.2 Subtype 3 RTCMAC Protocol ......................................................................... 25 48 9.2.4 HRPD System Configuration for VoIP Flow .................................................................................... 26 49 9.2.4.1 Enhanced Multi-Flow Packet Application ...................................................... 26 50 51 9.2.4.2 RTCMAC Subtype 3 ....................................................................................... 28 52 9.3 PDSN QoS Filter for VoIP and SIP Flows .................................................................................................... 28 53 54 55 56 57 58 1 3GPP2
  6. 6. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 1 Introduction 4 5 This specification includes recommendations for VoIP codecs as well as protocol configuration to 6 enable efficient support of VoIP over HRPD Rev A and HRPD Rev B. VoIP codecs are chosen from 7 existing 3GPP2 technologies keeping in mind system efficiency as well as quality considerations. 8 9 Recommendations are provided for transport protocols as well as for 3GPP2-specific system 10 parameter settings for RoHC, RLP and RLMAC. 11 12 A pre-configured provisioned session is also defined for use in supporting non-authorized access for 13 VoIP emergency services. 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 2 3GPP2
  7. 7. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 2 References 4 5 The following standards are referenced in this text. At the time of publication, the editions indicated 6 were valid. All standards are subject to revision, and parties to agreements based upon this document 7 are encouraged to investigate the possibility of applying the most recent editions of the standards 8 indicated below. ANSI and TIA maintain registers of currently valid national standards published by 9 them. 10 11 12 [1] 3GPP2 C.S0014-B v1.0, “Enhanced Variable Rate Codec, Speech Service Options 3 and 68 for 13 14 Wideband Spread Spectrum Digital Systems”, May 2006. 15 16 [2] 3GPP2 C.S0014-A v1.0, “Enhanced Variable Rate Codec, Speech Service Option 3 for 17 Wideband Spread Spectrum Digital Systems”, May 2004. 18 19 20 [3] 3GPP2 C.S0014-C v1.0, “Enhanced Variable Rate Codec, Speech Service Options 3, 68 and 21 70 for Wideband Spread Spectrum Digital Systems”, February 2007. 22 23 [4] IETF RFC 3095, Borman, et al, “RObust Header Compression (ROHC): Framework and four 24 profiles: RTP, UDP, ESP, and uncompressed”, July 2001. 25 26 27 [5] 3GPP2 C.S0055-A v1.0, “Packet Switched Video Telephony Services (PSVT/MCS)”, June 28 2008. 29 30 [6] 3GPP2 C.S0024-A v3.0, “cdma2000® High Rate Packet Data Air Interface Specification”, 31 September 2006. 32 33 34 [7] IETF RFC 3264, Rosenberg and Schulzrinne, “An Offer/Answer Model with the Session 35 Description Protocol (SDP)”, June 2002. 36 37 [8] 3GPP2 X.S0013-004-A v1.0, “All-IP Core Network Multimedia Domain: IP Multimedia Call 38 Control Protocol Based on SIP and SDP – Stage 3”, November 2005. 39 40 41 [9] 3GPP2 C.S0076-0 v1.0, “Discontinuous Transmission (DTX) of Speech in cdma2000 42 Systems”, December 2005. 43 44 45 [10] 3GPP2 C.S0024-B v2.0, “cdma2000 High Rate Packet Data Air Interface Specification”, 46 March 2007 47 48 [11] 3GPP2 X.S0049-0 v1.0, “All-IP Network Emergency Call Support”, February 2008 49 50 51 [12] 3GPP2 C.R1001-F “Administration of Parameter Value Assignments for cdma2000 Spread 52 Spectrum Standards”, January 2007 53 54 [13] 3GPP2 C.S0063-A v2.0, “cdma2000 Packet Data Supplemental Services”, March 2007 55 56 57 cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the 58 Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. 3 3GPP2
  8. 8. C.S0085-A v1.0 VoIP Codecs and Protocols 1 [14] 3GPP2 X.S0011-D v2.0 “cdma2000 Wireless IP Network Standards: Books 1-6, November 2 2008 3 4 5 [15] 3GPP2 X.S0060-0 v1.0 “HRPD Support for Emergency Services”, July 2008 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 4 3GPP2
  9. 9. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 3 Definitions, Symbols and Abbreviations 4 5 This section contains definitions, symbols and abbreviations that are used throughout the document. 6 7 8 9 3.1 Symbols and Abbreviations 10 3GPP2 3rd Generation Partnership Project 2 11 12 EMFPA Enhanced Multi Flow Packet Application 13 EVRC Enhanced Variable Rate Codec 14 15 EVRC-B Enhanced Variable Rate Codec-B 16 EVRC-WB Enhanced Variable Rate Codec- Wideband 17 HRPD High Rate Packet Data 18 19 IP Internet Protocol 20 IP-ID Internet Protocol Identifier 21 MAC Medium Access Control 22 23 QoS Quality of Service 24 RFC Request for Comments 25 RLMAC Reverse Link Medium Access Control 26 27 RLP Radio Link Protocol 28 RoHC Robust Header Compression 29 30 RS-1 Rate Set-1 31 RTP Real Time Protocol 32 SIP Session Initiation Protocol 33 34 UDP User Datagram Protocol 35 VoIP Voice over Internet Protocol 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 5 3GPP2
  10. 10. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 4 SDP Offer/Answer 4 5 The SDP offer typically contains at least one audio media line (m=) offering one or more RTP 6 payload formats. For each media line, the codecs are listed in order of decreasing preference with the 7 most preferred codec listed first. 8 9 The SDP answer for each audio media line (m=) typically contains only one codec format, i.e., the 10 first codec format in the offer that can be used by the answering VoIP Terminal for the VoIP session. 11 12 The selection of the voice codec and any parameters (for example [9]) associated with the codec used 13 in a VoIP call shall follow [7] for non-IMS call control scenarios and [8] for IMS call control 14 scenarios. 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 6 3GPP2
  11. 11. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 5 Media 4 5 6 7 5.1 Voice 8 9 10 11 5.1.1 Narrowband 12 13 Narrowband-only VoIP terminals shall support EVRC-B [1] and EVRC [2] codecs. EVRC-B is the 14 default and most preferred voice codec for these VoIP terminals. The audio m-lines of the SDP offer 15 shall contain EVRC-B as one of the offered codecs. 16 17 5.1.2 Wideband 18 19 Wideband-capable VoIP terminals shall support EVRC-WB [3] in addition to EVRC-B and EVRC 20 codecs. EVRC-WB is the default and most preferred codec for wideband-capable VoIP terminals. 21 The audio m-lines of the SDP offer shall contain EVRC-WB as one of the offered codecs. 22 23 24 5.2 VoIP Transport 25 26 27 28 5.2.1 RTP Header and Packetization 29 30 Maintaining low end-to-end delays is important for VoIP. Thus, a VoIP terminal shall send VoIP 31 frames without any bundling, i.e., each speech frame in a separate RTP packet. 32 33 5.2.2 Header Compression 34 35 To reduce RTP/UDP/IP overhead, a VoIP terminal shall use Robust Header Compression (RoHC) [4] 36 to compress IP/UDP/RTP headers for VoIP flows. The recommended configuration for RoHC is 37 described below: 38 39 • The recommended profile to use is the RTP profile. 40 41 • The recommended mode of operation is the Optimistic ‘O’ mode (Even this in case, RoHC starts 42 in the Unidirectional ‘U’ mode, as defined in [4], and then transitions to the ‘O’ mode). 43 44 • Timer-based compression is recommended to compress the RTP timestamp. 45 46 • To ensure robust operation, it is recommended to set the window size (as used in Window-Based 47 LSB encoding) to 6. 48 49 • To ensure robust operation, it is recommended to set the number of updates sent by the RoHC 50 compressor as per the Optimistic Approach principle to 6. 51 52 • To ensure that RoHC can tolerate jitter on the air link when doing timer-based compression, it is 53 recommended to set the value of Max_Jitter_CD (Max_Jitter_CD is the upper bound of jitter 54 expected on the communication channel between compressor and decompressor) to 150 msec. 55 56 • To handle out-of-order packets, it is recommended to set the ‘p’ value for RTP SN (Sequence 57 Number) to 6. Note that [4] recommends setting this parameter to 1, but it assumes a reordering- 58 free channel. Since reordering is likely to happen over an HRPD channel, it is recommended to set this parameter to a value that is large enough to handle this reordering. 7 3GPP2
  12. 12. C.S0085-A v1.0 VoIP Codecs and Protocols 1 • In order to enable timer-based compression, the VoIP Terminal should set the parameter 2 TimerBasedCompressionSupported in the ATSupportedFlowProtocolParameters04 or 3 ATSupportedRouteProtocolParameters04 attribute to 1 when the Flow Protocol or Route Protocol 4 5 is RoHC. Also, when the Flow Protocol or Route Protocol is RoHC, the parameter 6 TimerBasedCompression in the FlowNNFlowProtocolParametersRev or 7 FlowNNRouteProtocolParametersRev attribute should be set to 1. 8 9 • To handle the IP-ID (IP Identification) efficiently for IPv4, it is recommended to set the IP-ID to 10 the same value as the RTP SN. This ensures that the IP-ID is completely compressed away by the 11 RoHC compressor. 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 8 3GPP2
  13. 13. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 6 HRPD System Configuration for VoIP Flow 4 5 6 7 6.1 RLP (Radio Link Protocol) Configuration 8 9 The recommended Enhanced Multi-Flow Packet Application [13] RLP configuration for a VoIP flow 10 is as follows (note that not all the RLP parameters are shown here; only those that are critical for 11 efficient support of VoIP are shown): 12 13 • FlowRRNakEnableFwd: 0x00 (Nak-based retransmission disallowed) 14 • FlowRRNakEnableRev: 0x00 (Nak-based retransmission disallowed) 15 16 • FlowRRPhysicalLayerNakEnableRev: 0x00 (RLP is to ignore physical layer Reverse Traffic 17 Packets missed indication) 18 19 • ReservationMMIdleStateFwd: 0x01 (Closes when connection is closed) 20 21 • ReservationMMIdleStateRev: 0x01 (Closes when connection is closed) 22 23 • FlowRRSequenceLengthFwd: 0x00 (6-bit sequence number) 24 25 • FlowRRSequenceLengthRev: 0x00 (6-bit sequence number) 26 • FlowRRFlowProtocolPDUFwd: 0x01 (Packet stream) 27 28 • FlowRRFlowProtocolPDURev: 0x01 (Packet stream) 29 30 • FlowRRDataUnitFwd: 0x01 (Segment sequencing) 31 32 • FlowRRDataUnitRev: 0x01 (Segment sequencing) 33 34 • FlowRRRouteProtocolPDUFwd: 0x01 (Packet stream) 35 36 • FlowRRRouteProtocolPDURev: 0x01 (Packet stream) 37 38 • FlowRROutOfOrderDeliveryToRouteProtocolFwd: 0x01 (Out-of-order delivery allowed) 39 • FlowRRTimersFwd: 40 41 o AbortTimer: 0x00c8 (200 msec). This assumes that RoHC supports out-of-order delivery. 42 43 • FlowRRTimersRev: 44 45 o AbortTimer: 0x00c8 (200 msec). This assumes that RoHC supports out-of-order delivery. 46 47 • FlowRRTransmitAbortTimerRev: 0x0028 (200 msec). 48 49 50 6.2 RLMAC (Reverse Link Medium Access Control) Configuration 51 52 The recommended RLMAC configuration for a VoIP flow is shown below. Note that not all RLMAC 53 parameters are mentioned here; all other RLMAC parameters should be set as per the default values 54 in [6][10]. Also, it is recommended to use direct Rise over Thermal based measurement control on the 55 Reverse Link. 56 57 • CommonPowerParameters 58 o AllocationStagger: 0000 9 3GPP2
  14. 14. C.S0085-A v1.0 VoIP Codecs and Protocols 1 o TxT2Pmin: 0x1A 2 3 o RPCStep: 01 4 5 6 7 • PowerParameters128 8 9 o LoLatT2PTransition128: 0x2 10 o LoLatTerminationTarget128: 0x2 11 12 o HiCapT2PTransition128: 0x3 13 14 o HiCapTerminationTarget128: 0x3 15 16 o T2PLoLatPreTransition128: 0x0D 17 18 o T2PLoLatPostTransition128: 0x03 19 o T2PHiCapPreTransition128: 0x03 20 21 o T2PHiCapPostTransition128: 0x03 22 23 24 25 • PowerParameters256 26 27 o LoLatT2PTransition256: 0x2 28 29 o LoLatTerminationTarget256: 0x2 30 o HiCapT2PTransition256: 0x3 31 32 o HiCapTerminationTarget256: 0x3 33 34 o T2PLoLatPreTransition256: 0x1A 35 36 o T2PLoLatPostTransition256: 0x0F 37 38 o T2PHiCapPreTransition256: 0x0F 39 o T2PHiCapPostTransition256: 0x0F 40 41 42 43 • PowerParameters512 44 45 o LoLatT2PTransition512: 0x2 46 47 o LoLatTerminationTarget512: 0x2 48 49 o HiCapT2PTransition512: 0x3 50 o HiCapTerminationTarget512: 0x3 51 52 o T2PLoLatPreTransition512: 0x26 53 54 o T2PLoLatPostTransition512: 0x1C 55 56 o T2PHiCapPreTransition512: 0x1C 57 58 o T2PHiCapPostTransition512: 0x1C 10 3GPP2
  15. 15. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 • PowerParameters768 4 5 o LoLatT2PTransition768: 0x2 6 7 o LoLatTerminationTarget768: 0x2 8 9 o HiCapT2PTransition768: 0x3 10 o HiCapTerminationTarget768: 0x3 11 12 o T2PLoLatPreTransition768: 0x2E 13 14 o T2PLoLatPostTransition768: 0x23 15 16 o T2PHiCapPreTransition768: 0x23 17 18 o T2PHiCapPostTransition768: 0x23 19 20 21 • PowerParameters1024 22 23 o LoLatT2PTransition1024: 0x2 24 25 o LoLatTerminationTarget1024: 0x2 26 27 o HiCapT2PTransition1024: 0x3 28 29 o HiCapTerminationTarget1024: 0x3 30 o T2PLoLatPreTransition1024: 0x32 31 32 o T2PLoLatPostTransition1024: 0x28 33 34 o T2PHiCapPreTransition1024: 0x28 35 36 o T2PHiCapPostTransition1024: 0x28 37 38 39 40 • BucketLevelMaxNN: 0x66 41 42 43 • TransmissionModeNN: 0x01 44 45 46 47 • BucketFactorNN 48 49 o NumT2PAxisValues: 0x0 50 o NumFRABAxisValues: 0x0 51 52 o T2PAxis00: 0x00 53 54 o FRABAxis0: 0x8 55 56 o BucketFactorT2PAxis00FRABAxis0: 0x08 57 58 11 3GPP2
  16. 16. C.S0085-A v1.0 VoIP Codecs and Protocols 1 • T2PInflowRangeNN (NN > 0) 2 3 o T2PInflowmin: 0x0F 4 5 o T2PInflowmax: 0x78 6 7 8 9 • T2PTransitionFunctionNN (NN > 0) 10 o NumT2PAxisValues: 0x2 11 12 o NumFRABAxisValues: 0x0 13 14 o T2PAxis00: 0x00 15 16 o T2PAxis01: 0x34 17 18 o T2PAxis02: 0x35 19 o FRABAxis0: 0x8 20 21 o T2PUpT2PAxis00FRABAxis0: 0x1C 22 23 o T2PUpT2PAxis01FRABAxis0: 0x1C 24 25 o T2PUpT2PAxis02FRABAxis0: 0x88 26 27 o T2PDnT2PAxis00FRABAxis0: 0xB0 28 29 o T2PDnT2PAxis01FRABAxis0: 0xB0 30 o T2PDnT2PAxis02FRABAxis0: 0xB0 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 12 3GPP2
  17. 17. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 7 HRPD System Configuration for SIP Flow 4 5 6 7 7.1 RLP (Radio Link Protocol) Configuration 8 9 The recommended Enhanced Multi-Flow Packet Application [13] RLP configuration for a SIP flow is 10 as follows (note that not all the RLP parameters are shown here; only those that are critical for 11 efficient support of SIP are shown): 12 13 • FlowSSNakEnableFwd: 0x01 (Nak-based retransmission enabled) 14 • FlowSSNakEnableRev: 0x01 (Nak-based retransmission enabled) 15 16 • ReservationMMIdleStateFwd: 0x00 (Reservation does not change states when a connection is 17 closed) 18 19 • ReservationMMIdleStateRev: 0x00 (Reservation does not change states when a connection is 20 closed) 21 22 • FlowSSSequenceLengthFwd: 0x02 (22-bit sequence number) 23 24 • FlowSSSequenceLengthRev: 0x02 (22-bit sequence number) 25 26 • FlowSSFlowProtocolPDUFwd: 0x01 (Packet stream) 27 28 • FlowSSFlowProtocolPDURev: 0x01 (Packet stream) 29 • FlowSSDataUnitFwd: 0x00 (Octet sequencing) 30 31 • FlowSSDataUnitRev: 0x00 (Octet sequencing) 32 33 • FlowSSRouteProtocolPDUFwd: 0x01 (Packet stream) 34 35 • FlowSSRouteProtocolPDURev: 0x01 (Packet stream) 36 37 • FlowSSOutOfOrderDeliveryToRouteProtocolFwd: 0x01 (Out-of-order delivery allowed) 38 39 • FlowSSTimersFwd: 40 o AbortTimer: 0x01f4 (500 msec). 41 42 o FlushTimer: 0x0064 (100 msec) 43 44 • FlowSSTimersRev: 45 46 o AbortTimer: 0x01f4 (500 msec). 47 48 o FlushTimer: 0x0064 (100 msec) 49 50 • FlowSSTransmitAbortTimerRev: 0x00c8 (1000 msec). 51 52 53 7.2 RLMAC (Reverse Link Medium Access Control) Configuration 54 55 The recommended RLMAC configuration for a SIP flow is shown below. Note that not all RLMAC 56 parameters are mentioned here; all other RLMAC parameters should be set as per the default values 57 in [6][10]. 58 13 3GPP2
  18. 18. C.S0085-A v1.0 VoIP Codecs and Protocols 1 All the recommended RLMAC parameter values mentioned in Section 6.2 for a VoIP flow also apply 2 to a SIP flow, except for the parameters mentioned below: 3 4 • T2PTransitionFunctionNN (NN > 0) 5 6 o T2PUpT2PAxis00FRABAxis0: 0x1B 7 8 o T2PUpT2PAxis01FRABAxis0: 0x1B 9 10 o T2PUpT2PAxis02FRABAxis0: 0xB0 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 14 3GPP2
  19. 19. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 8 QoS Configuration/Activation 4 5 [5] defines procedures for pre-configuring QoS reservations and Activating QoS at call origination. A 6 VoIP terminal shall follow the QoS procedures defined in [5] to configure and activate QoS for 7 VoIP. 8 9 [5] defines procedures for negotiating end-to-end QoS between VoIP terminals. A VoIP terminal 10 should follow the end-to-end QoS negotiation procedures defined in [5]. 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 15 3GPP2
  20. 20. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 9 Emergency Services 4 5 This section defines how an authorized or a non-authorized access terminal can originate an HRPD 6 Emergency Services VoIP call. 7 8 Prior to making an HRPD Emergency Services call at the IMS layer the authorized or non-authorized 9 access terminal first: 10 11 • Establishes an HRPD session with the access network 12 13 • Configures air link QoS for the VoIP flow and SIP flow 14 15 • Configures QoS filters for the VoIP flow and SIP flow with the PDSN 16 17 • Accesses the HRPD access network to establish air link resources 18 • Activates the QoS for the VoIP flow and SIP flow 19 20 Upon finding HRPD service the authorized terminal should establish an HRPD session according to 21 the Default Session Configuration Protocol as defined in [10] and should configure QoS according to 22 Section 8 of this document. Upon making an Emergency Services call the non-authorized terminal 23 24 may also establish an HRPD session according to the Default Session Configuration Protocol as 25 defined in [10] or may use an alternative approach defined in this document. 26 Authorized and non-authorized terminals should follow the same steps for accessing the HRPD 27 28 access network to establish air link resources, configuring QoS filters at the PDSN, and activating 29 access network QoS for the VoIP flow and SIP flow. 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 16 3GPP2
  21. 21. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 3 9.1 Authorized Terminals 4 5 9.1.1 Establishing an HRPD Session with the Access Network 6 7 The access terminal and the access network perform session negotiation according to the Default 8 Session Configuration Protocol in [6] or [10]. As a result of the Session Negotiation, the access 9 terminal and the access network should agree to use the following group of application and protocol 10 subtypes in one of the negotiated Personalities: 11 12 • Enhanced Multi-Flow Packet Application according to [13] 13 14 • Enhanced Idle State Protocol according to [10] 15 • Enhanced Access Channel MAC Protocol according to [10] 16 17 • Enhanced Control Channel MAC Protocol according to [6] 18 19 • Subtype 3 Reverse Traffic Channel MAC Protocol according to [6] 20 21 • Enhanced Forward Traffic Channel MAC Protocol according to [6] 22 23 • Subtype 2 Physical Layer Protocol according to [6] 24 25 26 27 9.1.2 Configuring QoS for VoIP and SIP Flows 28 29 The access terminal sends AttributeUpdateRequest messages using the ReservationKKQoSRequest 30 Attribute according to [13], using an appropriate Profile ID as defined in [12] for the VoIP flow and 31 the SIP flow. 32 33 The access network creates, configures and activates Link Flows at the access terminal according to 34 [13]. 35 36 The access network creates, configures, and activates RTCMAC Instances according to [6]. 37 The access network Associates Link Flows in with RTCMAC flows according to [6]. 38 39 Refer to Section 8 in this document for more information on Configuring QoS at the access network. 40 41 42 43 9.1.3 Accessing the HRPD Access Network to Establish Air Link Resources 44 45 Through the SectorParameters message defined in the Overhead Messages Protocol in [10] the access 46 terminal may find a CDMA channel at the access network that supports Emergency Services. This 47 support is indicated through the AccessHashingChannel mask described in the Overhead Message 48 Protocol in [10]. 49 50 The access terminal uses the information transmitted in the Access Parameters message to determine 51 if the access network supports the Emergency APersist mechanism as defined in the Enhanced Access 52 Channel MAC Protocol in [10]. The access terminal may use this information to generate and send 53 an Access Capsule accordingly. 54 55 The access terminal sends an emergency ConnectionRequest message with Emergency Indicator bit 56 set to 1 as defined in the Enhanced Idle State Protocol according to [10]. 57 58 17 3GPP2
  22. 22. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 9.1.4 Activating QoS for VoIP and SIP Flows 3 The access terminal sends an emergency ReservationOnRequest message with the Emergency 4 Indication bit set to 1 according to [13]. 5 6 7 8 9.2 Non-Authorized Terminals 9 10 9.2.1 Pre-configured HRPD Session 11 12 13 14 Authorized access terminals should already have an established session and can originate a VoIP call 15 immediately or can negotiate a session and then originate a connection (e.g., just powering up). See 16 previous section. 17 18 For non-authorized access terminals a pre-configured provisioned session should be used to support 19 an HRPD Emergency Services VoIP call. The use of a pre-configured provisioned session is 20 desirable as it allows the bypass of session configuration and key generation and allows the access 21 terminal to access the system, for emergency services purposes only, quickly and without the need to 22 pass authentication. 23 24 A non-authorized access terminal in this context is not authorized to use Profile IDs 0x0500 or 25 0x0100. If an access terminal is authorized for other services (i.e. Best Effort), but not for SIP/VoIP 26 as described by this document, the access terminal should purge its existing HRPD Session and use 27 the pre-configured session and PriorSession call flows described in this chapter. 28 29 If PriorSessionGAUP is not supported by the access network, then the access terminal may use 30 Generic Configuration Protocol through the ConfigurationRequest message with the PriorSession 31 attribute to instantiate the pre-configured provisioned session. If the access network supports the 32 PriorSessionGAUP the preconfigured provisioned session can be instantiated using the Generic 33 Attribute Update Protocol through the AttributeUpdateRequest message with the PriorSession 34 attribute 35 36 37 38 9.2.1.1 PriorSessionGAUP Not Supported 39 40 Figure 9-1 shows the details on how the pre-configured provisioned session is instantiated when 41 PriorSessionGAUP is not supported by the access network. The access network retrieves the pre- 42 configured provisioned session, through A13 signaling, without performing session configuration 43 exchanges over the air-interface. The visited access network may have an internal SessionStorage 44 entity as an implementation option, in which case there would be no A13 signaling. 45 46 47 48 49 50 51 52 53 54 55 56 57 58 18 3GPP2
  23. 23. C.S0085-A v1.0 VoIP Codecs and Protocols 1 Visiting 2 AT SessionStorage AN 3 4 Radio session is Radio session is provisioned at the AT provisioned at the a 5 SessionStorage 6 ~ ~ ~ 7 8 ~ UATIRequest w/ RATI ~ ~ 9 b 10 UATIAssignment(newUATI) c 11 UATIComplete,ConnectionRequest 12 d 13 TCA e 14 TCC, f 15 ConfigurationRequest( PriorSession(ProvisionedUATI) ) 16 17 A13-SessionInformationRequest g 18 A13-SessionInformationResponse h 19 A13-SessionInformationConfirm i 20 ConfigurationResponse( PriorSession) 21 j 22 ConfigurationComplete k 23 24 SoftConfigurationComplete l 25 ConnectionClose m 26 ConnectionClose n 27 28 ConnectionRequest o 29 30 TCA p 31 TCC,ReservationOnRequest 32 q 33 34 35 36 37 38 39 40 41 Fi gu r e 9 -1 Pr i or Sessi on r et r i ev al wh en Pr i or Sessi on GAUP n ot su ppor t ed 42 a) The pre-configured session is stored on the access terminal and the access network 43 44 b) The access terminal requests a new UATI with the UATIRequest message. The Access Channel 45 MAC Header is populated with a RATI. 46 47 c) The access network assigns the access terminal a new UATI with the UATIAssignment message 48 49 d) The access terminal sends a UATIComplete message, and a ConnectionRequest message. 50 51 e) The access network assigns air link resources using the TrafficChannelAssignment message 52 53 f) The access terminal completes the assignment of air link resources using the 54 TrafficChannelComplete message, and sends a ConfigurationRequest message with the PriorSession 55 attribute that includes the Pre-provisioned PriorSession information. 56 57 g) h) i) The access network retrieves the PriorSession information from the Session Storage entity. If 58 the SessionStorage entity is internal to the access network, then A-13 signaling is not necessary. 19 3GPP2
  24. 24. C.S0085-A v1.0 VoIP Codecs and Protocols 1 j) The access network sends a ConfigurationResponse message to the access terminal indicating that 2 the PriorSession was retrieved. 3 4 k) The access terminal sends a ConfigurationComplete message to end the Session Configuration 5 6 l) The access network sends a SoftConfigurationComplete message with Continue=0, Commit = 1 7 and sets the SessionConfigurationToken to indicate the Personality Index the access terminal is to use. 8 9 m) n)The access terminal sends a ConnectionClose message and the access network responds with 10 ConnectionClose message 11 12 o) The access terminal opens a new Connection 13 14 p) The access network assigns air-link resources using the TrafficChannelAssignment message 15 q) The access terminal completes the assignment of air link resources using the 16 17 TrafficChannelComplete message and sends the ReservationOnRequest message to turn on the 18 Reservations for the VoIP flow and the SIP flow. 19 20 21 9.2.1.2 PriorSessionGAUP Supported 22 23 Figure9-2 shows how the pre-configured provisioned session is instantiated when PriorSessionGAUP 24 is supported by the access network. The access network retrieves the pre-configured provisioned 25 session, through A13 signaling, without performing session configuration exchanges over the air- 26 interface. The visited access network may have an internal SessionStorage entity as an 27 implementation option, in which case there would be no A13 signaling. 28 29 Visiting 30 AT SessionStorage AN 31 32 Radio session is Radio session is 33 provisioned at the AT provisioned at the a SessionStorage 34 35 ~ ~ ~ 36 ~ UATIRequest w/ RATI ~ ~ 37 38 b 39 UATIAssignment(newUATI) 40 c 41 UATIComplete, 42 AttributeUpdateRequest( PrirorSession(ProvisionedUATI) ), d 43 ConnectionRequest, ReservationOnRequest 44 45 A13-SessionInformationRequest e 46 A13-SessionInformationResponse f 47 A13-SessionInformationConfirm g 48 49 AttributeUpdateAccept, TCA h 50 i 51 TCC 52 53 54 55 56 Fi gu r e9 -2 Pr i or Sessi on r et r i ev al wh en Pr i or Sessi on GAUP su ppor t ed 57 58 a) The pre-configured session is stored on the access terminal and the access network 20 3GPP2
  25. 25. C.S0085-A v1.0 VoIP Codecs and Protocols 1 b) The access terminal requests a new UATI with the UATIRequest message. The Access Channel 2 MAC Header is populated with a RATI. 3 4 c) The access network assigns the access terminal a new UATI with the UATIAssignment message 5 6 d) The access terminal sends a UATIComplete message, an AttributeUpdateRequest message for the 7 PriorSession Attribute that includes the pre-provisioned PriorSession information, a 8 ConnectionRequest message and a ReservationOnRequest message to turn on the reservations for the 9 VoIP media and SIP flows. 10 11 e) f) g) The access network retrieves the PriorSession information from the Session Storage entity. If 12 the SessionStorage entity is internal to the access network, then A-13 signaling is not necessary. 13 14 h) The access network sends the AttributeUpdateAccept message in response to the 15 AttributeUpdateRequest(PriorSession) from the access terminal, and assigns air-link resources to the 16 access terminal using the TrafficChannelAssignment message. 17 18 i) The access terminal completes the assignment of air-link resources with the 19 TrafficChannelComplete message. 20 21 9.2.2 HRPD Protocol and Application Configuration for Emergency Services 22 VoIP and SIP Flows 23 24 The pre-configured provisioned HRPD session defines the non-default HRPD protocol subtypes and 25 application subtypes as defined in [12] to be used for Emergency Services, and the non-default 26 27 attribute values used within the protocol subtypes and application subtypes. Figure 9-3 depicts the 28 Emergency Services VoIP flow and SIP flow configuration. This configuration depicts the mappings 29 necessary between the Enhanced Multi-Flow Packet Application at the HRPD Application Layer, 30 HRPD Stream Layer, and the HRPD RTCMAC 3 at the MAC Layer to allow for the necessary QoS 31 desired for the Emergency Services VoIP flow and the SIP flow. 32 33 The non-authorized access terminal should configure QoS according to Section 9.1.2 of this 34 document, access the HRPD access netwok according to Section 9.1.3 of this document, and activate 35 QoS for the VoIP flow and SIP flow as stated in Section 9.1.4 of this document 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 21 3GPP2
  26. 26. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 SIP Signaling Audio Traffic OSI 3 IP Flows Reservation Reservation Application 4 Label KK = 03 Label KK = 04 Layer 5 6 Enhanced Multi-Flow - 7 Packet Application 8 9 LinkFlow NN LinkFlow NN 1xEV DO - 10 NN= 3 NN=4 Application 11 Layer 12 13 14 15 16 17 Enhanced Multi-Flow Packet Application bound to Stream = 2 18 Stream 19 - Stream n = 2 Layer 20 21 22 23 24 RTCMAC RTCMAC 25 FlowNN = 2 FlowNN = 3 RTCMAC 26 SIP Flow Audio Flow Layer 27 28 29 Fi gu r e 9 -3 Em er gen cy Ser v i ces VoI P an d SI P Fl ow Pr ot ocol an d 30 31 Appl i cat i on M appi n gs 32 33 9.2.2.1 Session Configuration Protocol 34 This section of the document describes non-default Simple Attribute and Complex Attribute values to 35 36 be used in the pre-configured session for attributes that are defined in the Session Configuration 37 Protocol. All other Simple and Complex Attributes shall use the default values as per [6][10]. 38 The definition of the HRPD Protocol Subtypes to be used in the pre-configured session for 39 40 Emergency VoIP Services is defined in the following table. Note that the Enhanced Access Channel 41 MAC and Enhanced Idle State Protocol are as specified in [10] 42 43 Tabl e 9 -1 Em er gen cy Sessi on Pr ot ocol Su bt y pes 44 45 Attribute ID (Protocol Value) Attribute Value (Sub Protocol Type) Meaning 46 0x0000 0x02 Subtype 2 Physical Layer Protocol 47 0x0002 0x01 Enhanced Access Channel MAC 48 Enhanced Forward Traffic Channel 49 0x0003 0x01 MAC 50 Subtype 3 Reverse Traffic Channel 51 0x0004 0x03 MAC 52 53 0x000c 0x01 Enhanced Idle State Protocol 54 55 56 The definition of the Attribute Values of the Simple Attributes SessionConfigurationToken and 57 PersonalityCount for the pre-configured session shall be as per the table below. 58 22 3GPP2
  27. 27. C.S0085-A v1.0 VoIP Codecs and Protocols 1 Tabl e 9 -2 Sessi on Con f i gu r at i on Pr ot ocol Si m pl e At t r i bu t e Set t i n gs 2 3 Attribute ID Attribute Value Meaning 4 The SessionConfigurationToken shall be 5 6 set to the value 0xE911 1 0x0100 0xE911 7 The access terminal supports a 8 0x0110 0x04 PersonalityCount of 4 9 10 11 12 The definition of the PriorSessionAttribute for the pre-configured session shall be as per the table 13 below. The access network should skip the authentication function of the Security Packet included in 14 the PriorSession attribute. This is PriorSession attribute that will be encapsulated in the 15 AttributeUpdateRequest Message depicted in Figure9-2 if the access network supports 16 PriorSessionGAUP, or in the ConfigurationRequest depicted in Figure 9-1 when the access network 17 does not support PriorSessionGAUP. 18 19 20 21 Tabl e 9 -3 Em er gen cy Sessi on Pr i or Sessi on At t r i bu t e Set t i n gs 22 Length Value Meaning 23 Field (bits) 24 16 Length of this attribute in octets; excluding the length field 25 Length 26 16 0x0100 PriorSession attribute Attribute ID 27 8 0 Identifier assigned to this complex value 28 ValueID 29 1 0x1 Request the PriorSession to be restored Restore 30 7 0x0 Reserved 31 128 0xffffffffffffffff The provisioned UATI contains all 1’s. 32 UATI 33 8 Variable Length of Security Packet Field in octets SecurityPacketLength 34 64 SecurityPacketLengthx8 Created according to section 6.4.6.1.6.1in [10] 35 SecurityPacket 36 37 9.2.2.2 Stream Protocol 38 The definition of the Stream Protocol bindings to be used in the pre-configured session for 39 40 Emergency Services is defined in the following table. 41 42 43 Tabl e 9 -4 Em er gen cy VoI P Sessi on St r eam Pr ot ocol def i n i t i on 44 45 Attribute Attribute iD Value Meaning 46 47 Stream0 0x14 0x0000 Default Signaling Application 48 Stream1 0x15 0xffff No Application 49 50 Stream2 0x16 0x0009 Enhanced Multi-Flow Packet Application bound to Service Network 51 Stream3 0x17 0xffff No Application 52 53 54 55 56 57 58 1 Note that 4 MSBs represent the personality index, and value 0xE is used to ensure it is outside the typical range of personality index values used. 23 3GPP2
  28. 28. C.S0085-A v1.0 VoIP Codecs and Protocols 1 9.2.2.3 Enhanced Multi-Flow Packet Application 2 3 Tabl e 9 -5 Em er gen cy VoI P Ser v i ces ATSu ppor t edFl owPr ot ocol Par am et er s Def i n i t i on 4 5 Length 6 Field (bits) Value Meaning 7 Length 8 Length of the packet 8 We are defining support 9 AttributeID 0xf004 associated with RoHC 10 Number used to keep track of 11 ValueID 8 1 this record 12 ProtocolSupported 1 1 RoHC is supported 13 14 SupportedProtocolParametersValueLength 8 See 9-6 15 SupportedProtocolParametersValue See Table 9-6 16 17 18 19 20 21 9 -6 Su ppor t ed Pr ot ocol s Par am et er Val u es f or ATSu ppor t edFl owPr ot ocol Par am et er s0 4 22 Length Value Meaning 23 Field (bits) 24 16 0 25 MaxSupportedMaxCID 26 LargeCIDSupported 1 0 Large CID is not supported 27 16 0 No segmentation 28 MaxSupportedMRRU 29 1 1 Timer based compression is 30 TimerBasedCompressionSupported supported 31 8 3 There are three profiles 32 SupportedProfileCount supported 33 34 16 0 Uncompressed SupportedProfile 35 16 1 RTP 36 SupportedProfile 37 16 2 UDP SupportedProfile 38 0-7 Padding as necessary 39 Reserved 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 24 3GPP2
  29. 29. C.S0085-A v1.0 VoIP Codecs and Protocols 1 2 9.2.3 HRPD system Configuration for SIP Flow 3 4 This section of the document defines the non-default attributes to be used in the pre configured HRPD 5 Session for the SIP flow. Non-default attribute values are defined for the Enhanced Multi-Flow Packet 6 Application and the Subtype 3 RTCMAC Protocol. 7 8 9 9.2.3.1 Enhanced Multi-Flow Packet Application 10 11 The recommended RLP configuration in EMFPA for an Emergency Services SIP flow is as specified in 12 Section 7.1 with the follow additions. All other RLP parameters shall be set as per the default values in [6]. 13 14 The EMFPA Simple Attribute values ReservationKKQOSRequestFwd/Rev in the table below defines the 15 ProfileID relationships to the Forward and Reverse ReservationLabels. 16 17 18 Tabl e 9 -7 Em er gen cy Ser v i ces I P Fl ow t o Reser v at i on Label M appi n gs f or SI P Si gn al i n g 19 20 Attribute Name Attribute Value ProfileID Meaning 21 22 ReservationKKQOSRequestFwd ProfileID 1280 for Forward SIP Flow with 23 KK=3 0x0703 0x0500 Reservation Label=3 24 ReservationKKQOSRequestRev ProfileID 1280 for Reverse SIP Flow with 25 KK=3 0x0803 0x0500 Reservation Label=3 26 27 28 29 The EMFPA Simple Attribute Values in the table below defines the Forward and Reverse 30 ReservationLabels relationships to the Forward and Reverse Flows created to carry the SIP signaling 31 information. 32 Tabl e 9 -8 Em er gen cy Ser v i ces Reser v at i on Label t o Li n k Fl ow M appi n gs f or SI P Si gn al i n g 33 34 Attribute Name Attribute Value Reservation Label Meaning 35 36 Map SIP Flow Forward Reservation = 3 37 FlowNNReservationFwd NN=3 0x0503 0x03 to Forward Link Flow =3 (SIP Signaling) 38 Map SIP Flow Reverse Reservation = 3 39 FlowNNReservationRev NN=3 0x0603 0x03 to Reverse Link Flow=3 (SIP Signaling) 40 41 42 The EMFPA Simple Attribute values in the table below activate the Forward and Reverse Link Flows 43 created to carry the SIP signaling information. 44 Tabl e 9 -9 Em er gen cy Ser v i ces Li n k Fl ow Act i v at i on f or SI P Si gn al i n g 45 46 Attribute Name Attribute Value Activated Meaning 47 48 The Forward Link Flow for the SIP 49 FlowNNActivatedFwd nn=3 0xf303 0x01 Signaling is Activated 50 The Reverse Link Flow for the SIP Signaling 51 FlowNNActivatedRev nn = 3 0xf203 0x01 is Activated 52 53 54 9.2.3.2 Subtype 3 RTCMAC Protocol 55 56 The recommended RTCMAC Subtype 3 parameters in the RL MAC for an Emergency Services SIP flow is 57 as specified in Section 7.2 with the follow additions. All other RTCMAC Subtype 3 parameters shall be set 58 as per the default values in [6]. 25 3GPP2
  30. 30. C.S0085-A v1.0 VoIP Codecs and Protocols 1 The Simple Attribute value defined in the table below defines the associated EMFPA Link Flow instance 2 created to carry SIP signaling information to an RTCMAC instance. 3 4 Tabl e 9 -1 0 Em er gen cy Ser v i ces RT CM AC Fl ow t o EM FPA Li n k Fl ow M appi n g f or SI P 5 Si gn al i n g 6 7 Attribute Name Attribute ID Stream Substream Meaning 8 9 Bind RTCMAC Flow 2 to ReverseLinkFlow 3 10 AssociatedFlowsNN NN=2 0x0102 0x02 0x03 running in EMFPA (SIP Signaling) 11 12 13 The Simple Attribute value BucketLevelMaxNN is set to a non-zero number to turn on the instance of 14 Subtype 3 RTCMAC that is created to carry SIP signaling information. This non-zero number activates the 15 RTCMAC flow NN. 16 17 Tabl e 9 -1 1 Em er gen cy Ser v i ces RT CM AC Bu ck et Lev el M ax NN Set t i n g f or SI P Si gn al i n g 18 19 Attribute Name AttributeID Attribute Value Meaning 20 21 BucketLevelMaxNN Bucket Level Max for RTCMAC Flow 2 (SIP 22 NN=2 0xfe02 0x66 Signaling) 23 24 25 9.2.4 HRPD System Configuration for VoIP Flow 26 27 This section of the document defines the non-default attributes to be used in the pre-configured HRPD 28 Session for the VoIP flow. Non-default attribute values are defined for the Enhanced Multi-Flow Packet 29 Application, and the Subtype 3 RTCMAC protocol. 30 31 32 9.2.4.1 Enhanced Multi-Flow Packet Application 33 34 The recommendation RLP configuration for an Emergency Services VoIP flow is as specified in Section 35 6.1 with the follow additions. All other RLP parameters should be set as per the default values in [6]. 36 37 The EMFPA Simple Attribute values ReservationKKQoSRequestFwd/Rev in the table below defines the 38 ProfileID relationships to the Forward and Reverse ReservationLabels. 39 40 Tabl e 9 -1 2 Em er gen cy Ser v i ces I P Fl ow t o Reser v at i on Label M appi n gs f or VoI P 41 42 Attribute Name Attribute Value ProfileID Meaning 43 44 ReservationKKQoSRequestFwd ProfileID 256 for Forward VoIP Flow with 45 KK=4 0x0704 0x0100 Reservation Label=4 46 ReservationKKQoSRequestRev ProfileID 256 for Reverse VoIP Flow with 47 KK=4 0x0804 0x0100 Reservation Label=4 48 49 The EMFPA Simple Attribute Values in the table below defines the Forward and Reverse 50 51 ReservationLabels relationships to the Forward and Reverse Flows created to carry the VoIP information. 52 53 54 55 56 57 58 26 3GPP2
  31. 31. C.S0085-A v1.0 VoIP Codecs and Protocols 1 Tabl e 9 -1 3 Em er gen cy Ser v i ces Li n k Fl ow t o Reser v at i on Label M appi n g f or VoI P 2 3 Reservation 4 Attribute Name Attribute Value Label Meaning 5 6 Map VoIP Flow Forward Reservation = 4 7 FlowNNReservationFwd NN=4 0x0504 0x04 to Forward Link Flow =4 (VoIP) 8 Map VoIP Flow Reverse Reservation = 4 9 FlowNNReservationRev NN=4 0x0604 0x04 to Reverse Link Flow=4 (VoIP) 10 11 12 The EMFPA Simple Attribute values in the table below activate the Forward and Reverse Link Flows 13 created to carry the SIP signaling information. 14 15 Tabl e 9 -1 4 Em er gen cy Ser v i ces Li n k Fl ow Act i v at i on f or VoI P 16 17 Attribute Name Attribute Value Activated Meaning 18 19 20 FlowNNActivatedFwd NN=4 0xf304 0x01 The Forward Link Flow for VoIP is Activated 21 22 FlowNNActivatedRev NN = 4 0xf204 0x01 The Reverse Link Flow for VoIP is Activated 23 24 25 26 9 -1 5 Fl ow NNFl owPr ot ocol Fwd At t r i bu t e Set t i n gs 27 28 Field Length (bits) Value Meaning 29 Length 8 Length of the packet 30 31 AttributeID 0x0b03 FlowNNFlowProtocolFwd AttributeID 32 ValueID 8 1 Number used to keep track of this record 33 ProtocolSupported 8 0x4 RoHC is supported 34 35 ProtocolParametersLength 8 See 9-17 36 ProtocolParametersValue See 9-17 37 38 39 9 -1 6 Fl ow NNFl owPr ot ocol Rev At t r i bu t e Set t i n gs 40 41 Length 42 Field (bits) Value Meaning 43 Length 8 Length of the packet 44 45 AttributeID 0x0c03 FlowNNFlowProtocolRev AttributeID 46 ValueID 8 1 Number used to keep track of this record 47 48 ProtocolSupported 8 0x4 RoHC is used 49 ProtocolParametersLength 8 See 9-17 50 ProtocolParametersValue See 9-17 51 52 53 54 55 56 57 58 27 3GPP2
  32. 32. C.S0085-A v1.0 VoIP Codecs and Protocols 1 9 -1 7 Pr ot ocol Par am et er s Recor d f or Fl owNNFl owPr ot ocol s At t r i bu t e 2 3 Length Value Meaning 4 Field (bits) 5 16 0 MaxCID 6 1 0 7 LargeCIDs 8 FeedbackForIncluded 1 0 Feedback is for this LinkFlow only 9 5 0 Ommitted since FeedbackFor = 0 10 FeedbackFor 11 MRRU 8 0 No segmentation 12 13 14 ProfileCount 8 3 There are three profiles supported 15 16 16 0 Uncompressed 17 Profile 18 Profile 16 1 RTP 19 16 2 UDP 20 Profile 21 22 23 9.2.4.2 RTCMAC Subtype 3 24 25 The recommended RTCMAC Subtype 3 parameters in the RL MAC for an Emergency Services VoIP flow 26 is as specified in Section 6.2 with the follow additions. All other RTCMAC Subtype 3 parameters should 27 be set as per the default values in [6] 28 29 The Simple Attribute value defined in the table below defines the associated EMFPA Link Flow instance 30 created to carry VoIP frames to an RTCMAC instance. 31 32 Tabl e 9 -1 8 Em er gen cy Ser v i ces RT CM AC Fl ow t o EM FPA Li n k Fl ow M appi n g f or VoI P 33 34 Attribute Name Attribute ID Stream Substream Meaning 35 36 AssociatedFlowsNN Bind RTCMAC Flow 3 to ReverseLinkFlow 4 running in 37 NN=3 0x0103 0x02 0x03 EMFPA 38 39 40 The Simple Attribute value BucketLevelMaxNN is set to a non-zero number to turn on the instance of 41 Subtype 3 RTCMAC that is created to carry VoIP frames. This non-zero number activates the RTCMAC 42 flow NN. 43 44 Tabl e 9 -1 9 Em er gen cy Ser v i ces Bu ck et Lev el M ax NN f or VoI P 45 46 Attribute Name AttributeID Attribute Value Meaning 47 BucketLevelMaxNN 48 NN=3 0xfe03 0x66 Bucket Level Max for RTCMAC Flow 3 (VoIP) 49 50 51 52 53 9.3 PDSN QoS Filter for VoIP and SIP Flows 54 55 The access terminal uses RSVP signaling as defined in [14] to install Traffic Flow Templates at the PDSN. 56 Refer to Section 8 in this document for more information on Configuring QoS at the PDSN. 57 58 28 3GPP2

×