• No results found

Packet Switched Voice (over IP) and Video Telephony Services End-to-end System Design Technical Report

N/A
N/A
Protected

Academic year: 2021

Share "Packet Switched Voice (over IP) and Video Telephony Services End-to-end System Design Technical Report"

Copied!
25
0
0

Loading.... (view fulltext now)

Full text

(1)

Date: November 2005 3

4

Packet Switched Voice (over IP) and Video Telephony

5

Services

6

End-to-end System Design

7

Technical Report

8

9

COPYRIGHT

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

(2)

FOREWORD

1

(This foreword is not part of this document) 2

This document was prepared by 3GPP2 TSG-X. 3

This document is a new specification. 4

(3)

Revision History

1

Revision

Date

2

Version 1.0 Initial Publication

November, 2005

(4)

1

CONTENTS

2

Foreword ii

3

Revision History iii

4

1 Scope 7

5

2 Introduction 7

6

3 Glossary and Definitions 8

7 3.1 Acronyms 8 8 3.2 Definitions 8 9 4 References 9 10

5 Protocol Reference Model 10

11

5.1 Network Reference Model 10

12

5.2 Protocol Stack 13

13

6 Session Control 17

14

6.1 Session Control Signaling 17

15

6.1.1 Over-the-air Link Establishment...17 16

6.1.2 A10 Connection Establishment ...17 17

6.1.3 IP Multimedia Session Registration...17 18

6.1.4 IP Multimedia Session Establishment ...17 19

6.2 Session Media Traffic 19

20

6.2.1 Over-the-air Link Establishment...19 21

6.2.2 A10 Connection Establishment ...19 22 6.2.2.1 Terminal Addressing ...19 23 6.2.2.2 PSVT Voice Retry...20 24 6.3 Session Release 20 25

6.3.1 IP Multimedia Session Release...20 26

6.4 In-Session Control 20

27

6.4.1 Media Stream Management ...20 28

6.4.2 Call Waiting Notification...20 29

7 Quality of Service 21

30

7.1 Flow Treatment 21

31

7.2 End-to-End QoS Transport 21

32

7.3 Establishing QoS 22

33

7.4 QoS Session Management 23

34

8 Compression 23

(5)

8.1 SIP Compression 23 1 8.2 Header Compression 23 2 9 Security 24 3

9.1 Authentication and Authorization 24

4

9.1.1 Over-the-Air Link ...24 5

9.1.2 Packet Data Service/ IP Bearer ...24 6

9.1.3 IP Multimedia Subsystem...24 7

9.2 Encryption and Integrity Protection 24

8

9.2.1 Over-the-Air Link Layer Encryption ...24 9

9.2.2 SIP Control Signaling Security...24 10

9.2.3 End-to-End Media Encryption...24 11

10 Accounting 24

12

10.1 Offline Charging 24

13

10.1.1 Packet Data Accounting...24 14

10.1.2 MMD Offline Charging ...24 15

10.1.3 Service Based Bearer Control Accounting ...25 16

10.2 Online Charging 25

17

10.2.1 PrePaid Packet Data Accounting ...25 18

10.2.2 MMD Online Charging...25 19

10.2.3 Service Based Bearer Control Accounting ...25 20

11 Mobility Management 25

21

11.1 Inter-BS and Inter-PDSN Handoffs 25

22

11.2 HRPD-1X Handoffs 25

(6)

LIST OF FIGURES

1

Figure 1 Network Reference Model for Non-roaming Mobile-to-Mobile PSVT or VoIP Call ...11 2

Figure 2 Network Reference Model for Non-roaming Mobile-to-Internet CN PSVT or VoIP Call ...13 3

Figure 3 PSVT and VoIP Protocol Stacks over IP ...14 4

Figure 4 Protocol Stack for the SIP Control Flow (when HDLC framing is applied)...15 5

Figure 5 Protocol Stack for the SIP Control Flow (when segment-based framing is applied) ...15 6

Figure 6 Protocol Stack for the Media Flows (when HDLC framing is applied) ...16 7

Figure 7 Protocol Stack for the Media Flows (when segment-based framing is applied) ...16 8

Figure 8 IP Multimedia Session Establishment - Roaming...18 9

Figure 9 Mobile Initiated IP Multimedia Session Release ...20 10

Figure 10 Access Network QoS Treatments for Different Data Flows ...21 11

Figure 11 QoS Mappings for End-to-End PSVT/VoIP Media Transport with PDSN Policing and 12

Remarking ...22 13

14

(7)

1

1 Scope

2

This document describes the end-to-end protocols and procedures for support of Packet Switched 3

Video Telephony (PSVT) and Voice-Over-IP (VoIP) Services over cdma2000®1 networks. The 4

document describes the end-to-end PSVT and VoIP services and architectures. 5

PSVT provides support of one-to-one conversational video services between a mobile station and 6

another mobile station or a video terminal on the Internet. VoIP provides support of one-to-one 7

conversational speech services between a mobile station and another mobile station or a voice 8

terminal on the Internet. The designs are compliant with the procedures specified in the 3GPP2 9

standards [6][7][8][9][10][11][12][13][16][17][19]. 10

2 Introduction

11

This technical report is an informative document that identifies and summarizes the relevant 12

procedures in other 3GPP2 specifications that are used to provide 3GPP2 PSVT and VoIP 13

services. The language used in this document is informative and is not meant to add or modify 14

procedures already specified in other 3GPP2 standards. 15

1

“cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the 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.”

(8)

8

3 Glossary

and

Definitions

1

3.1 Acronyms

2

1X cdma2000 1X Air Interface 3

AAA Authentication, Authorization, and Accounting 4

AIR Accounting Information Record 5

AES Advanced Encryption Standard 6

BSC Base Station Controller 7

DSCP Diff-serve Code Point 8

H-AAA Home AAA

9

HRPD High Rate Packet Data 10

HTTP Hyperlink Text Transfer Protocol 11

IMS IP Multimedia Subsystem 12

IP Internet Protocol

13

MS Mobile Station

14

NAI Network Address Identifier

15

NID Network Identifier

16

OTA Over The Air

17

PCF Packet Control Function 18

PDSN Packet Data Serving Node 19

PSVT Packet Switched Video Telephony 20

PZID Packet Zone Identifier 21

RADIUS Remote Authentication Dial In User Service 22

RAN Radio Access Network

23

ROHC Robust Header Compression

24

RTCP Real-time Transport Control Protocol 25

RTP Real-time Transport Protocol 26

SBBC Service Based Bearer Control 27

SDP Session Description Protocol

28

SIP Session Initiation Protocol 29

SRTP Secure Real-time Transport Protocol 30

UDP User Datagram Protocol 31

UIM User Identity Module 32

UTC Universal Coordinated Time 33

VOIP Voice over IP

34

VSA Vendor Specific Attribute 35

3.2 Definitions

36

1X Air interface specification as defined in [6][7][8][9][10].

37

HRPD Air interface specification as defined in [13]. 38

Media Traffic The RTP/UDP/IP packets transporting the encoded audio, video, or VoIP traffic.

(9)

4 References

1

The following documents contain provisions, which, through reference in this text, constitute 2

provisions of this document. 3

ƒ References are either specific (identified by date of publication, edition number, version 4

number, etc.) or non-specific. 5

ƒ For a specific reference, subsequent revisions do not apply. 6

ƒ For a non-specific reference, the latest version applies. In the case of a reference to a 7

3GPP2 document, a non-specific reference implicitly refers to the latest version of that 8

document in the same Release as the present document. 9

10

[1] 3GPP2: A.S0008-A, Interoperability Specification (IOS) for High Rate Packet Data

11

(HRPD) Access Network Interfaces - Rev A, March 2006. 12

[2] 3GPP2: A.S0009-A, Interoperability Specification (IOS) for High Rate Packet Data

13

(HRPD) Access Network Interfaces - Rev A, March 2006. 14

[3] 3GPP2: A.S0013-C, Interoperability Specification (IOS) for cdma2000 Access Network

15

Interfaces – Part 3 Features, February 2005. 16

[4] 3GPP2: A.S0014-C, Interoperability Specification (IOS) for cdma2000 Access Network

17

Interfaces – Part 4 (A1, A1p, A2, and A5 Interfaces), February 2005. 18

[5] 3GPP2: C.R1001-E v1.0, Administration of Parameter Value Assignments for cdma2000

19

Standards for Spread Spectrum Systems, October 2005. 20

[6] 3GPP2: C.S0001-A v5.0, Introduction for cdma2000 Standards for Spread Spectrum

21

Systems, July 2001. 22

[7] 3GPP2: C.S0002-A v6.0, Physical Layer Standard for cdma2000 Standards for Spread

23

Spectrum Systems, February 2002. 24

[8] 3GPP2: C.S0003-A v6.0, Medium Access Control (MAC) Standard for cdma2000

25

Standards for Spread Spectrum Systems, February 2002. 26

[9] 3GPP2: C.S0004-A v6.0, Signalling Link Access Control (LAC) Standard for cdma2000

27

Standards for Spread Spectrum Systems, February 2002. 28

[10] 3GPP2: C.S0005-A v6.0, Upper Layer (Layer 3) Signalling Standard for cdma2000 29

Standards for Spread Spectrum Systems, February 2002. 30

[11] 3GPP2: C.S0017-010-A v1.0, Data Service Options for Spread Spectrum Systems: Radio 31

Link Protocol Type 3, July 2004. 32

[12] 3GPP2: C.S0017-012-A v1.0, Data Service Options for Spread Spectrum Systems: Service 33

Options 33 and 66, July 2004. 34

[13] 3GPP2: C.S0024-A v1.0, cdma2000 High Rate Packet Data Air Interface Specification, 35

April 2004. 36

[14] 3GPP2: C.S0039-0 v1.0, Enhanced Subscriber Privacy for cdma2000 High Rate Packet 37

Data, September 2002. 38

[15] 3GPP2: C.S0047-0 v1.0, Link-Layer Assisted Service Options for Voice-Over-IP: Header 39

Removal (SO 60) and Robust Header Compression (SO 61), April 2003. 40

[16] 3GPP2: S.R0086-A, IMS Security Framework, June 2004. 41

[17] 3GPP2: X.S0011, cdma2000 Wireless IP Network Standard. 42

(10)

10

[18] 3GPP2: X.S0013-000-0 v2.0, All-IP Core Network Multimedia Domain: Overview, August 1

2005. 2

[19] 3GPP2: X.S0013-002-0 v1.0, All-IP Core Network Multimedia Domain: IP Multimedia 3

Subsystem – Stage 2, February 2004. 4

[20] 3GPP2: X.S0013-003-0 v2.0, All-IP Core Network Multimedia Domain: IP Multimedia 5

Session Handling; IP Multimedia Call Model – Stage 2, August 2005. 6

[21] 3GPP2: X.S0013-007-0 v1.0, All-IP Core Network Multimedia Domain: IP Multimedia 7

Subsystem – Charging Architecture, February 2004. 8

[22] 3GPP2: X.S0013-008-0 v2.0, All-IP Core Network Multimedia Domain: IP Multimedia 9

Subsystem – Accounting Information Flows and Protocol, August 2005. 10

[23] IETF: RFC 3095, Borman, et al, ‘RObust Header Compression (ROHC): Framework and 11

four profiles: RTP, UDP, ESP, and uncompressed’, July 2001. 12

[24] IETF: RFC 3261, J. Rosenberg et al, ‘SIP: Session Initiation Protocol’, June 2002. 13

[25] IETF: RFC 3545, T. Koren, et al. ‘Enhanced Compressed RTP (CRTP) for Links with High 14

Delay, Packet Loss and Reordering’, July 2003. 15

16 17

5

Protocol Reference Model

18 19

5.1

Network Reference Model

20

The network reference model for a mobile-to-mobile PSVT or VoIP call is illustrated in Figure 1. 21

(11)

IP Networks PDSN RAN Network A PDSN RAN Network B I/S-CSCF I/S-CSCF MS MS MRFP (optional) MRFC (optional) AAA HSS P-CSCF AAA HSS P-CSCF AS (optional) SIP Signaling

Air Interface/IOS Signaling Media Control for Audio/Video PSVT /VoIP Audio Bearer Path PSVT Video Bearer Path AAA/HSS Interfaces MP Interfaces [19]

AS

(optional)

1

Figure 1 Network Reference Model for Non-roaming Mobile-to-Mobile PSVT or VoIP Call

2

The function of each entity is listed below: 3

AAA

4

The AAA authenticates the subscriber to the access network and sends the list of the subscriber’s 5

authorized Flow Profile IDs to the RAN via the PDSN, including the Flow Profile IDs for PSVT 6

or VoIP. The AAA also performs the accounting for the access network. 7

AS

8

The Application Server can be a SIP application server (e.g., video mail or voice mail server, 9

etc…) or an OSA gateway as specified in [19]. 10

HSS

11

The HSS provides the authentication vector to the S-CSCF for IMS authentication. The HSS 12

also performs authorization and accounting for the IMS. 13

I-CSCF

14

Interrogating-CSCF (I-CSCF) is the entry point within an operator’s network for all session setup 15

attempts destined to a user of that network operator, or a roaming user currently located within 16

that network operator’s service area. 17

(12)

12

P-CSCF

1

The Proxy-CSCF is the first entry point within the IP Multimedia Subsystem [19]. The P-CSCF 2

behaves like a Proxy, i.e. it accepts requests and services them internally or forwards them on to 3

the MS, an I-CSCF, or the S-CSCF. 4

PDSN

5

The PDSN communicates with the MS using service connections for packet data session 6

establishment, to add and remove IP flows, etc. as described in [17]. The PDSN function acts as 7

the first-hop router for IP traffic to and from the MS. 8

MRFC

9

The Media Resource Function Controller, in conjunction with the MRFP, provides a set of 10

resources with the MMD core network that are useful in supporting services to subscribers. In 11

the network reference model the MRFC interfaces to the S-CSCF to determine media conversion 12

requirements and instructs the MRFP to perform any necessary conversion of the media stream. 13

MRFP

14

The Media Resource Function Processor converts the media formats sent between the mobile 15

stations when the mobile stations use incompatible codecs. 16

MS

17

The mobile station contains the video and audio codecs that provide the multimedia interface to 18

the user. The mobile station also contains the SIP user agent that communicates with the other 19

terminal (MS or general IP video or voice telephony device) through the core network CSCFs. 20

RAN

21

The Radio Access Network communicates with the MS using the service option [12][15] or link 22

flow [13] to transport packet data over the radio link. 23

S-CSCF

24

The Serving-CSCF (S-CSCF) performs the session control services for the MS. It maintains a 25

session state as needed by the network operator for support of the services. 26

(13)

IP Networks (Internet) CN SIP Proxy SIP Signaling

Air interface/IOS Signaling Media Control for Audio/Video PSVT /VoIP Audio Bearer Path PSVT Video Bearer Path AAA/HSS Interfaces MP Interfaces [19] PDSN RAN Network A I/S-CSCF MS MRFP (optional) MRFC (optional) AAA HSS P-CSCF AS (optional) 1 2

Figure 2 Network Reference Model for Non-roaming Mobile-to-Internet CN PSVT or VoIP Call

3

CN

4

The Correspondent Node is a packet switched video and/or voice terminal on the Internet. This 5

terminal complies with the protocols and procedures above the IP level that are specified in this 6

document. 7

5.2 Protocol

Stack

8

Control and media traffic flows are carried over the IP protocol. Control traffic flow includes session/call control 9

traffic (SIP/UDP or SIP/TCP) and media control (RTCP/UDP). Media traffic flow refers to RTP/UDP traffic. 10

They have different protocol stacks and may travel through different paths, as illustrated in Figure 3. 11

(14)

14 IP Networks Application SIP Processing Media Processing Application SIP Processing Media Processing SIP Servers SIP Session Control IP IP SIP TCP SIP Session Control IP Session Control Protocol Stacks Network Connection Model Media Application and RTCP Protocol Stacks PSVT or VoIP Terminal PSVT or VoIP Terminal UDP IP RTP/RTCP UDP IP RTP/RTCP Media Processing Media Processing TCP UDP Media Processing Media Resource Function Processor RTP/RTCP UDP IP Session Control TCP UDP SIP UDP TCP UDP IP RTP/RTCP UDP IP SIP Server 1 2

Figure 3 PSVT and VoIP Protocol Stacks over IP

3

Figure 4 illustrates the protocol reference model for the PSVT and VoIP Services SIP control flow between two 4

PSVT or two VoIP mobiles when HDLC framing is used between the PDSN and MS to frame IP packets. For 1X 5

this illustrates service option 33 or 66 over the air interface. For HRPD this illustrates service option 59 or 64. 6

(15)

R-P MS-1 RAN-1 PDSN-1 Router(s) Physical Layer R-P IP TCP IP PDSN-2 RAN-2 SIP Physical Layer Mux HDLC Framing PPP Encapsulation IP IP IP HDLC L1 PPP L1 L2 L1 L2 L1 Mux R-P IP IP IP HDLC L1 PPP L1 L2 R-P Physical Layer L1 Mux UDP RLP RLP MS-2 Physical Layer Mux HDLC Framing PPP Encapsulation IP RLP RLP TCP SIP UDP IP L1 L2 CSCF-1 IP L1 L2 CSCF-2 Compression Compression TCP SIP UDP Compression TCP SIP UDP TCP SIP UDP Compression TCP SIP UDP IP L1 L2 IP L1 L2 1 2

Figure 4 Protocol Stack for the SIP Control Flow (when HDLC framing is applied)

3

Figure 5 illustrates the protocol reference model for the PSVT or VoIP Services SIP control flow between two 4

PSVT or two VoIP mobiles when segment-based framing (service option 67 for HRPD) is used between the RAN 5

and MS to frame IP packets. 6 R-P R-P IP IP L1 L1 L2 L1 L2 L1 Mux R-P IP L1 L1 L2 R-P Physical Layer L1 Mux Physical Layer Mux RLP RLP

Physical Layer Physical Layer Mux IP TCP SIP UDP Compression TCP SIP UDP Compression MS-1 RAN-1 PDSN-1 CSCF-1 Router(s) CSCF-2 PDSN-2 RAN-2 MS-2

TCP SIP UDP IP L1 L2 Compression TCP SIP UDP IP L1 L2 TCP SIP UDP IP L1 L2 Compression TCP SIP UDP IP L1 L2 RLP RLP Segment Framing IP Segment

Framing Segment Framing Segment

Framing

7 8

Figure 5 Protocol Stack for the SIP Control Flow (when segment-based framing is applied)

9

Figure 6 illustrates the protocol reference model for PSVT or VoIP Services media flows between two PSVT or two 10

VoIP mobiles when HDLC framing is used between the PDSN and MS to frame IP packets. The protocol stack 11

reference model for VoIP services does not include the video application component in the mobiles or MRFP. For 12

1X this illustrates service option 66 over the air interface. For HRPD this illustrates service option 64. 13

(16)

16 1 R-P Physical Layer R-P IP IP HDLC L1 L1 L2 L1 L2 L1 Mux IP L1 L2 Video/ Audio Video/ Audio RTP RTP UDP Physical Layer Mux HDLC Framing IP Video/Audio RTP UDP Physical Layer Mux HDLC Framing IP Video/Audio RTP UDP R-P Physical Layer L1 Mux R-P HDLC L1 L1 L2 IP RLP RLP RLP RLP PPP Encapsulation PPP PPP PPP Encapsulation MS-1 RAN-1 PDSN-1 MRFP Router(s) PDSN-2 RAN-2 MS-2

IP

L1 L2

2 3

Figure 6 Protocol Stack for the Media Flows (when HDLC framing is applied)

4

Figure 7 illustrates the protocol reference model for the PSVT or VoIP Services media flows between two PSVT or 5

two VoIP mobiles when segment-based framing (service option 67 for HRPD) is used between the RAN and MS to 6

frame IP packets. The protocol stack reference model for VoIP services does not include the video application 7

component in the mobiles or MRFP. 8 R-P R-P Physical Layer Mux IP IP IP L1 L1 L2 L1 L2 L1 Mux Video/Audio RTP UDP IP L1 L2 Video/ Audio Video/ Audio RTP RTP UDP L2 IP IP IP L1 L1 R-P R-P Physical Layer L1 Mux Physical Layer Mux IP Video/Audio RTP UDP Physical Layer

MS-1 RAN-1 PDSN-1 MRFP Router(s) PDSN-2 RAN-2 MS-2

IP L1 L2 RLP RLP Segment Framing RLP RLP Segment

Framing Segment Framing Segment

Framing

9 10

Figure 7 Protocol Stack for the Media Flows (when segment-based framing is applied)

11

For PSVT services, RTCP may be used by the MS to provide information needed for the synchronization of the 12

audio and video media streams. Such synchronization is not needed for VoIP services. 13

(17)

6 Session

Control

1

6.1 Session

Control

Signaling

2

6.1.1

Over-the-air Link Establishment

3

The MS requests establishment of an over-the-air link with the RAN to transport the SIP signalling and RTCP over 4

the radio interface. 5

6

In 1X, the MS first requests the main packet data service option (33) which is connected to the PDSN. The MS is 7

then assigned a Simple or Mobile IP address. Once this is granted by the RAN, SIP signaling and RTCP can be 8

transported over this main service option. Alternatively, the MS can request auxiliary service options (66) with 9

different QoS attributes to transport the SIP signalling and RTCP together or separately. 10

11

In HRPD, the MS first requests main link flows in the forward and reverse direction which are connected as service 12

option 59 to the PDSN. The mobile is then assigned a Simple or Mobile IP address. SIP signalling and RTCP can 13

be transported over these main link flows. Alternatively, the MS can request different QoS attributes for auxiliary 14

link flows in each direction (connected as service options 64 or 67 to the PDSN) to transport the SIP signalling and 15

RTCP together or separately. 16

6.1.2

A10 Connection Establishment

17

As the over-the-air links are connected the RAN and PDSN establish corresponding A10 connections between them. 18

Traffic flow filters for these A10 connections are also set by the MS. If Service Based Bearer Control of MMD is 19

not required by the network for these bearers then these connections and filters may be established prior to call setup 20

to reduce setup delay. Otherwise, the procedures for SBBC are followed (SIP signalling bearers may be 21

established prior to call setup even when SBBC is required by the network.) 22

6.1.3

IP Multimedia Session Registration

23

The SIP level registration can be initiated after access network registration has been completed, and the IP bearer for 24

the signaling has been connected to the access network. The MS registers with the S-CSCF. 25

6.1.4

IP Multimedia Session Establishment

26

The PSVT and VoIP services use the IP Multimedia Subsystem [19] to establish the IP multimedia session. Figure 27

8 illustrates an example call flow for establishing a mobile-to-mobile IP multimedia session. The different steps in 28

the call flow identify the main functions that need to be performed. 29

(18)

18

1 2

Figure 8 IP Multimedia Session Establishment - Roaming

3

1. When MS-1 originates a call to MS-2, MS-1 and MS-2 exchange their media capabilities through a series of 4

SIP messages. The SDP, present in the SIP messages, contains one or more media descriptions for the 5

multimedia session. The SIP messages traverse through the visited and the home networks of both the mobile 6

stations. 7

2. Based on the session parameters agreed in the previous step, MS-1 completes establishment of bearer 8

resources in its serving network. 9

10

To minimize call setup time this step can be performed in advance of step 1 when Service Based Bearer 11

Control is not required by the network. In this scenario the bearer resource reservation is not based on the 12

agreed session parameters. Resource reservation may be based on the maximum resources that MS-1 13

expects to use for the IMS session. 14

3. After the bearer resources are set up in its serving network, MS-1 indicates to MS-2 that the reservation has 15

been completed. 16

4. After MS-2 completes resource reservation in its serving network, MS-2 alerts the user. 17

5. MS-2 indicates to MS-1 that it is alerting the user. 18

6. The called party answers the phone. 19

7. MS-2 indicates to MS-1 that the called-party has answered and completes the call setup. 20

8. The PSVT or VoIP session is established and MS-1 & MS-2 now exchange media traffic. To reduce call 21

setup time media traffic exchange can also start at step 6. 22

(19)

6.2 Session

Media

Traffic

1

6.2.1

Over-the-air Link Establishment

2

The MS requests establishment of over-the-air links with the RAN to transport media traffic over the radio interface. 3

4

In 1X, all media traffic is transported over auxiliary service options (60, 61, or 66). The MS and RAN establish the 5

necessary service options according to one of the following procedures: 6

• For VoIP services the MS requests an auxiliary service option (60, 61, or 66) with the appropriate QoS for 7

transport of the speech stream with the flow profiles described in section 7.3 8

• For PSVT services one of the following procedures is used: 9

o The MS requests an auxiliary service option (66) with the appropriate QoS for the combined 10

transport of both the video and audio streams with the flow profiles described in section 7.3. The 11

RAN grants this QoS request on an existing service option or the RAN establishes a new service 12

option instance to provide the requested QoS. Having the audio stream share a service 13

connection with video stream is acceptable if the audio stream does not require a QoS treatment 14

distinct from the video stream. 15

o The MS establishes two auxiliary service options (66) for the separate transport of the audio and 16

video streams with the flow profiles described in section 7.3. The RAN grants these QoS 17

requests on existing service options or the RAN establishes new service option instances to 18

provide the requested QoS. 19

Separate transport of the media streams allows the RAN to provide different QoS treatments for 20

the streams. Other options for the separate transport of the audio stream are service option 60 or 21

61. Service option 60 can be used but does not provide audio-video synchronization information 22

(audio media RTP timestamps) to the MS. Service option 61 can be used but imposes significant 23

implementation complexity which is not warranted by the savings of zero-byte audio packet 24

overhead when in a PSVT call. 25

26

In HRPD, all the media traffic is transported over auxiliary link flows that are connected to the PDSN as service 27

option 64 or 67. The MS and RAN establish the necessary auxiliary link flows according to one of the following 28

procedures: 29

• For VoIP services the MS request two auxiliary link flows (one in each direction) for the transport of the 30

speech stream with the flow profiles described in section 7.3. 31

• For PSVT services one of the following procedures is used: 32

o The MS requests two auxiliary link flows (one in each direction) for the combined transport of 33

both the video and audio streams with the flow profiles described in section 7.3. The RAN 34

grants this QoS request on existing link flows or the RAN establishes new link flows to provide 35

the requested QoS. 36

o The MS establishes two pairs of auxiliary link flows for the separate transport of the audio and 37

video streams with the flow profiles described in section 7.3. The RAN grants these QoS 38

requests on existing link flows or the RAN establishes new link flows to provide the requested 39

QoS. Separate transport of the media streams allows the RAN to provide different QoS 40

treatments for the streams. 41

6.2.2

A10 Connection Establishment

42

As the over-the-air links are connected the RAN and PDSN establish corresponding A10 connections between them. 43

Traffic flow filters for these A10 connections are also set by the MS. If Service Based Bearer Control is not 44

required by the network then these connections and filters may be established prior to call setup to reduce setup 45

delay. Otherwise, the Service Based Bearer Control procedures will be followed. 46

6.2.2.1 Terminal Addressing

47

The MS and network support SIP URIs and tel URLs (MDNs) as specified in [19]. 48

(20)

20

6.2.2.2 PSVT Voice Retry

1

Due to lack of resources in the calling or called terminal’s network, a MS may be unable to initiate a PSVT session. 2

When this happens the MS attempts to connect a voice-over-IP or circuit-switched voice call to the called party if 3

the user has selected such fall back operation. 4

6.3 Session

Release

5

6.3.1

IP Multimedia Session Release

6 7

Figure 9 illustrates the call flow for a mobile initiated IP multimedia session release when one of the mobiles is 8

roaming. 9

10 11

Figure 9 Mobile Initiated IP Multimedia Session Release

12 13

1. If the MS-1 wants to terminate the session, it sends a SIP BYE messages towards MS-2. The SIP messages 14

traverse through all the proxies that are a part of the session. 15

2. MS-1 releases all bearer resources which were allocated to the session. This may also be performed in 16

parallel with step 1 as long as the service connection transporting SIP control traffic is maintained. 17

3. MS-2 releases all bearer resources which were allocated to the session. This may also be performed in 18

parallel with step 1 as long as the service connection transporting SIP control traffic is maintained. 19

6.4 In-Session

Control

20

6.4.1

Media Stream Management

21

The MS supports the ability for the user to add, remove, or modify different media streams as follows: 22

• A new SDP offer will be used to modify the existing session attributes as described in [24]. 23

• An MS that receives a new SDP offer notifies the user of the request to modify the session. The MS 24

renegotiates QoS reservations as needed to support the new session attributes. 25

• If a media stream is on hold, the MS does not release the QoS reservation for that stream. 26

6.4.2

Call Waiting Notification

27

While the MS is in an active PSVT or VoIP session it alerts the user of other incoming calls using the following 28

procedures: 29

(21)

1. If the incoming call is over IMS, the MS receives a SIP INVITE message over a 1X packet data instance or 1

a HRPD link flow. 2

2. If the incoming call is from the legacy network (via the MSC or MSCe), the MS can be either 3

a. A 1X-only MS which receives an alert over the 1X signaling channel, or 4

b. A hybrid HRPD-1X MS which receives a page 5

i. Over HRPD signaling (via cross-paging) [1] and [2], or 6

ii. Over the 1X paging channel. 7 8

7

Quality of Service

9

7.1 Flow

Treatment

10 11

The PSVT and VoIP services support the QoS requirements for each flow as specified in section 7.3. Figure 10 12

illustrates example QoS treatments applied by the RAN to the different data flows. For VoIP services, transport of 13

the video RTP and video RTCP as shown in Figure 10 are not applicable. 14

15

16 17

Figure 10 Access Network QoS Treatments for Different Data Flows

18

7.2

End-to-End QoS Transport

19

Figure 11 illustrates an example of how IP packets are provided QoS treatments as they are transported between the 20

terminal, RAN, PDSN, and core network, for a mobile-to-mobile PSVT or VoIP call. The transport of traffic in the 21

opposite direction is not shown in the figure but is the mirror image of the call flow shown. 22

23

RLP links are used to manage different QoS treatments over the air interface between the terminal and the RAN. 24

QoS is managed between the RAN and the PDSN using A10 connections. Diffserv is an example of how to 25

manage QoS between the PDSNs. 26

(22)

22

1 2 3

Figure 11 QoS Mappings for End-to-End PSVT/VoIP Media Transport with PDSN Policing and Remarking

4

For the reverse link, the MS sends session control, RTCP, and media packets on the over-the-air links with the 5

appropriate QoS treatments. Based on the Flow Profile ID(s) and its local policy the PDSN polices and may 6

remark the DSCP values of the reverse link packets before forwarding them to the Diffserv Network. 7

8

For the forward link, the MS sets the TFT filters at the PDSN to direct forward link traffic across the A10 flows with 9

the appropriate QoS treatments as previously defined by the RAN. Each of the A10 flows is mapped into a 10

corresponding over-the-air link at the RAN. 11

7.3 Establishing

QoS

12

When the MS establishes the main HRPD link flow or 1X service option the PDSN obtains the Flow Profile ID(s) 13

authorized for the user from the H-AAA and passes these to the RAN for RAN QoS authorization purposes [17]. 14

15

The MS reserves a QoS treatment for each media and control flow by requesting an appropriate Flow Profile ID [5] 16

for each flow using the procedures specified in [10] or [13]. The SIP signaling flow uses a Flow Profile ID that 17

supports SIP signaling traffic or best effort QoS. The audio/speech flow uses a Flow Profile ID that supports 18

audio/speech traffic. The video flow of a PSVT session uses a Flow Profile ID that supports video traffic. RTCP 19

(23)

traffic uses a Flow Profile ID that supports RTCP traffic or best effort QoS. 1

Alternatively, instead of using Flow Profile IDs, the terminal can use detailed QoS parameters to request the 2

necessary QoS treatment for each type of stream from the RAN. 3

4

If a QoS reservation is to be used for transporting SIP signaling then the MS reserves this QoS treatment with the 5

RAN and establish the corresponding TFT filter(s) at the PDSN before a SIP session is initiated. Before the called 6

party is alerted of the PSVT or VoIP session the QoS reservation(s) for media flows and the setting of their 7

corresponding TFT filters are completed by both the calling and called mobile stations with their respective RAN’s 8

and PDSNs. 9

7.4

QoS Session Management

10

The network notifies the MS of changes in the QoS reservations. The MS notifies the user of this change and 11

provides the following options to the user 12

1. If the change is a reduction in QoS 13

• Continue the session unmodified 14

• Modify the session to adapt to the new QoS 15

• Terminate the session 16

2. If the change is an improvement in QoS 17

• Continue the session unmodified 18

• Modify the session to adapt to the new QoS level 19

The choice of these options can be selected before the user starts a PSVT or VoIP session. 20

8 Compression

21

8.1 SIP

Compression

22

Support for SIP compression uses the procedures specified in [20]. 23

8.2 Header

Compression

24

To reduce the overhead of the audio and video streams ROHC [23] can be used to compress the headers of these 25

streams. Other compression protocols such as ECRTP [25] may also be used for service options that support the 26

compression protocol. These compression protocols can be used in either HRPD or 1X air interfaces. 27

28

In 1X, LLA-ROHC (Service Option 61 [15]) may also be used to compress the audio stream headers over 1X 29

channels when a native cdma2000 codec is used. Service Option 60 [15] may be used to compress the audio 30

stream headers but will require additional procedures to provide audio-video media synchronization. These 31

synchronization procedures are beyond the scope of this document. 32

33

The amount of overhead per audio payload frame can also be reduced by bundling multiple audio frames in a single 34

audio RTP packet. 35

(24)

24

9 Security

1

9.1 Authentication

and

Authorization

2

9.1.1 Over-the-Air

Link

3

The HLR and AN-AAA provide the authentication and authorization information for the 1X and HRPD radio links, 4

respectively. Over-the-air access authentication and authorization of the MS is performed by the RAN as described 5

in [10] or [13]. 6

9.1.2

Packet Data Service/ IP Bearer

7

The H-AAA provides the authentication and authorization information for the packet data service/IP bearer, 8

including authorization of Flow Profile IDs and treatments. The H-AAA performs the authentication and 9

authorization of the MS as described in [17]. 10

9.1.3

IP Multimedia Subsystem

11

The HSS provides the authentication and authorization information for the IMS. The S-CSCF performs the 12

authentication and authorization of the MS as described in [16]. 13

9.2

Encryption and Integrity Protection

14

9.2.1 Over-the-Air

Link Layer Encryption

15

Link layer encryption over the 1X and HRPD RAN’s can be provided using the procedures in [11] and [14]. 16

9.2.2

SIP Control Signaling Security

17

Security of all SIP control signaling between various IMS entities uses the procedures specified in [16]. 18

9.2.3

End-to-End Media Encryption

19

For further study. 20 21

10 Accounting

22

10.1 Offline

Charging

23

10.1.1

Packet Data Accounting

24

Offline packet data accounting for PSVT or VoIP sessions is performed using the accounting procedures specified in 25

[17]. 26

10.1.2

MMD Offline Charging

27

MMD offline charging is performed using the procedures specified in [21] and [22]. 28

(25)

10.1.3

Service Based Bearer Control Accounting

1

For further study. 2

10.2 Online

Charging

3

10.2.1 PrePaid

Packet Data Accounting

4

PrePaid packet data accounting for PSVT or VoIP sessions is performed using the accounting procedures for PrePaid 5

packet data services specified in [17]. 6

10.2.2

MMD Online Charging

7

For further study. 8

10.2.3

Service Based Bearer Control Accounting

9

For further study. 10

11

11 Mobility

Management

12

11.1

Inter-BS and Inter-PDSN Handoffs

13

The inter-BS and inter-PDSN handoff procedures specified in [1][2][3][4][17] are used by the network to provide 14

handoffs of the PSVT or VoIP session. 15

11.2 HRPD-1X

Handoffs

16

For further study. 17

12 Regulatory

Requirements

18

Support for regulatory requirements for Packet Switched Video Telephony (PSVT) and Voice-Over-IP (VoIP) 19

services over cdma2000 are outside the scope of this technical report. 20

References

Related documents

Considering that the phosphorylation/dephosphorylation of FMRP is tightly connected with its translation regulator function and that the minor splice isoforms ISO2 and ISO3

Voice over IP (VoIP) – It is an IP based voice communication system using the internet protocol (IP) to transfer voice communications between two parties.. The voice

DESCRIPTORS *Chinese; Cultural Context; Language Proficiency; Language Role; *Language Tests; Listening Skills; Reading Skills; *Second Languages; *Standardized Tests;

Voice over Internet Protocol (VoIP) is an evolving telephony solution that brings voice and data traffic together on the same IP-based network.. As a result, VoIP is becoming

The picture of a solid as a system of atoms which are free to vibrate about a periodic array of equilibrium positions, which has been developed in the preceding sections to

Given a statistical model consisting of a set of observed data, a set of unobserved latent data or missing values , and a vector of unknown parameters , along with a

•  Mandatory supply chain risk assessment reports for each Rx drug product to be made available to FDA.. Supply Chain - Country

615.49(018) О-64 Організація та регулювання діяльності підприємств фармації : Навчально-методичний посібник для практичних