最新GMSA GRX/IPX 骨干网互联标准IR.34

海浪

Table of Contents

1
Introduction.. 4

1.1
Overview.. 4

1.1.1
Purpose. 4

1.1.2
Background. 4

1.1.3
About this Document
4

1.2
Scope. 5

1.2.1
In scope. 5

1.2.2
Out of Scope. 5

1.3
Definition of Terms. 5

1.4
Document Cross-References. 7

2
The Need for IP Interconnect.. 8

2.1
General. 8

2.2
GRX.. 9

2.3
IPX.. 9

3
Inter-Service Provider IP Backbone Architecture.. 9

3.1
Service Provider to Inter-Service Provider IP Backbone connection. 9

3.2
GRX Architecture. 9

3.3
IPX Architecture. 10

3.4
IPX Connectivity Options. 11

3.4.1
IPX Transport
11

3.4.2
IPX Service Transit
11

3.4.3
IP Service Hub. 12

3.5
IPX Proxy Services. 12

3.6
Types of Service Provider and Interconnectivity Allowed. 12

3.7
Types of IP Backbone Provider. 13

3.7.1
GRX Provider
13

3.7.2
IPX Provider
13

4
Requirements of the Inter-Service Provider IP Backbone.. 13

4.1
GRX Provider Requirement. 13

4.1.1
General
13

4.1.2
Number of GRX Providers used to transit packets between Service Providers. 13

4.2
IPX Provider Requirements. 14

4.2.1
General
14

4.2.2
Number of IPX Providers used to transit packets between Service Providers. 14

4.3
Connections between IP Backbone Provider and Service Provider. 14

4.4
Peering Interface. 14

4.5
Technical Specification of the Inter-Service Provider IP Backbone. 15

4.5.1
IP Routing. 15

4.5.2
BGP-4 Advertisement Rules. 16

4.5.3
BGP Extended Community Attributes. 16

4.5.4
IP Addressing and Routing. 20

4.5.5
DNS.. 20

4.5.6
Security and Screening. 20

4.5.7
QoS.. 21

4.5.8
Generic IPX Proxy Requirements. 21

5
Technical Requirements for Service Providers.. 22

5.1
General Service Provider Requirements. 22

5.1.1
Service Provider IP Routing. 22

5.1.2
Service Provider IP Addressing. 22

5.1.3
Service Provider DNS.. 23

5.1.4
Service Provider Security and Screening. 23

5.2
BGP Advertisement Rules. 23

5.2.1
General Rules. 23

5.3
Service Provider and Inter-Service Provider IP Backbone Connectivity. 24

6
QoS.. 25

6.1
SLA for Inter-Service Provider IP Backbone. 25

6.1.1
Service Guarantees. 25

6.1.2
Responsibilities. 25

6.2
Traffic classification. 26

6.2.1
Traffic Handling Priority. 26

6.2.2
Diffserv Per Hop Behaviour
26

6.2.3
Differentiated Services Code Point
26

6.2.4
Traffic classes. 26

6.3
IP QoS Definitions for Inter-Service Provider IP Backbone. 27

6.3.1
Availability. 28

6.3.2
Delay. 28

6.3.3
Jitter
31

6.3.4
Packet Loss Rate. 32

7
Traffic Applications.. 32

7.1
GPRS/3G Data Roaming. 32

7.2
Service Provider Bilateral Services. 32

7.3
WLAN Roaming. 32

7.4
MMS Interworking. 33

7.5
IMS.. 34

Annex A: KNOWN Issues and Solutions.. 35

A.1 Double IP Backbone Provider problem.. 35

A.1.1 Short term solution: Network configuration. 35

A.1.2
Short-term solution disadvantages. 36

A.1.3
Long-term solution: Network design in Service Provider network. 36

Annex B: IPX Proxy Requirements.. 39

B1 Introduction.. 39

B2 Requirements for IPX Proxy.. 39

B2.1
General. 39

B.2.2.1
IPX Provider Requirements. 39

B.2.2.2
Operational Requirements. 41

Document Management.. 43

Document History. 43

1
Introduction1.1
Overview1.1.1
Purpose

The purpose of this document is to provide guidelines and technical information on how Inter-Service Provider IP Backbone networks are set-up and how Service Providers will connect to the Inter-Service Provider IP Backbone.

This document provides a clear distinction between GRX and IPX (evolved GRX) networks where applicable.

This document also defines high level security requirements for the Inter-Service Provider IP network.
Detailed complementary requirements can be found in the “Inter-Operator IP backbone Security Requirements for Service Providers and Inter-operator IP Backbone Providers” IR.77 [19].

1.1.2
Background

The Inter-Service Provider IP Backbone network was originally created to carry GTP-tunnels (GPRS Tunnelling Protocol) via the Gp interface between the GPRS Support Nodes (GSNs) in different GSM Operators i.e. data roaming. The Gp interface allowed mobile end-users to make use of the GPRS/3G services of their home network while roaming in a visited network. Later, MMS interworking and WLAN (authentication) data roaming has been added to the services supported in Inter-Service Provider IP Backbone. This Inter‑Service Provider IP Backbone is in fact an Inter-PLMN IP Backbone and is termed the GRX. The GRX model is used to interconnect in excess of 300 networks and has proven highly successful.

With the development of IP-based services, interworking of such services has become an industry wide challenge. The GRX model is applicable as an IP interworking solution; however the GRX specification does not meet all the requirements. It has been recognised that by adding interworking specific functionality to the GRX model and offering it to the industry, a common interconnect platform could be established for IP interworking. The enhanced GRX is called an IPX and is designed to support a variety of types of Service Providers in a secure and business sustainable way.

The core enhancements to the GRX are end-to-end Quality of Service and the introduction of the IPX Proxy which facilitates interconnect cascade billing and multi-lateral interconnect agreements.

1.1.3
About this Document

The document provides a brief introduction to the requirement for IP interworking and the IPX. It covers the background to the forerunner of the IPX, the GRX.

The technical architectures of both the GRX and IPX are described followed by the technical implementation guidelines for IPX and GRX Providers and connecting Service Providers. Technical guidelines for Security, Quality of Service and Traffic applications are also given.

Appendices provide details on known issues in the Inter-Service Provider IP Backbone and on the requirements for IPX proxies.

Note: In this document all references to the IP Inter-Service Provider IP Backbone Network (or abbreviated to IP Backbone Network) shall include both IPX and GRX where generic requirements exist. However specific requirements to IPX and GRX shall use each term independently. In addition, the term “evolution to an IPX network” shall not in any way suggest or mandate the GRX is either invalid or that it shall be replaced by an IPX.