2011年7月版A10A11协议规范：3GPP2 IOS

2星需积分: 9 167 浏览量更新于2024-07-31 收藏 1.32MB PDF 举报

"A10A11最新协议2011年7月，详细阐述了CDMA网络中的A10和A11接口的互操作性规范，是2011年7月更新的标准文档，版本为A.S0017-D v3.0。" 本文档是3GPP2（第三代合作伙伴计划2）及其组织伙伴的版权作品，旨在规定cdma2000接入网络接口的互操作性，特别是A10和A11接口。A10接口通常涉及移动台（MS）与基站子系统（BSS）之间的通信，而A11接口则连接BSS和核心网络（CN）。这些接口在CDMA网络中起着至关重要的作用，确保了不同设备和服务之间的兼容性和数据传输的顺畅。 A.S0017-D v3.0版本在2011年5月发布，包含了自2007年以来的多次更新，如2009年的v2.0版本，增加了对1x空中接口增强、EVRC-WB在A2p上的支持、EVRC-NW在A2和A2p上的支持以及错误修复。到2011年的v3.0版本，增加了紧急呼叫回呼功能、EVRC-NW容量运行点0的支持以及进一步的错误修复。此互操作性规范（IOS）详细定义了A10和A11接口的信令流程、消息格式、参数设置以及性能要求，以确保CDMA2000网络中的1x和EV-DO（Evolution-Data Optimized）服务能够正确无误地进行。这些接口不仅涵盖了语音服务，还包括数据服务，如互联网接入、多媒体消息服务（MMS）和增强型数据速率（HDR）等。文档的修订历史表明，随着技术的发展，3GPP2不断更新标准以适应新的需求和改进。例如，EVRC-WB（Enhanced Variable Rate Codec - Wideband）是一种宽带语音编码技术，可以提供更高质量的语音通话体验，而EVRC-NW（Enhanced Variable Rate Codec - Narrowband）则关注窄带环境下的效率和音质。此外，紧急呼叫回呼功能的加入是为了确保在紧急情况下，网络能够迅速响应并重新建立呼叫，这对于公共安全和应急服务至关重要。容量运营点0的引入可能涉及到优化网络资源分配，以在低负载条件下提高效率。整体来看，A.S0017-D v3.0互操作性规范是CDMA网络运营商、设备制造商和开发者的重要参考文档，它确保了网络组件之间的兼容性和高效运行，同时也反映了3GPP2对不断提升服务质量和技术演进的承诺。

3GPP2 A.S0017-D v3.0

Section 1 8

Note that this standard deviates from [20] in several respects. First, when registering, the 1

PCF uses a fictitious Home Address (= 0.0.0.0). The PDSN acting as an HA shall not 2

attempt to allocate a non-zero IP address, but instead return the Home IP address of 3

0.0.0.0 in its reply to the PCF. The PDSN uses information in the Session Specific 4

Extension (IMSI and SR_ID) as an identity of the “Mobile Node”. Second, this standard 5

specifies messages (Registration Update, Registration Acknowledge, Session Update, and 6

Session Update Acknowledge) not included in [20]. Third, the Registration Request and 7

Registration Reply messages are used not only for performing registrations, but also to 8

exchange other information (e.g., accounting) between the PCF and the PDSN. 9

1.9 PCF-PDSN Security Association 10

Security contexts are configurable between every PCF and PDSN pair on the packet data 11

network. Each security context indicates an authentication algorithm and mode, a secret 12

(a shared key, or appropriate public/private key pair), and a style of replay protection in 13

use. Refer to [20] for details. 14

An index identifying a security context between a pair of PCF and PDSN is called a 15

Security Parameter Index (SPI). SPI values „0‟ through „255‟ are reserved, hence not 16

used in any PCF-PDSN security association. 17

The “Mobile-Home Authentication Extension” and “Registration Update Authentication 18

Extension” provide a means for authenticating the registration messages on the A11 19

interface. The Authenticator value in the “Mobile-Home Authentication Extension” and 20

“Registration Update Authentication Extension” protects the following fields: 21

 the UDP payload of registration messages, 22

 all prior extensions in their entirety, and 23

 the Type, Length and SPI fields of the extension. 24

The authentication algorithm uses the default keyed-MD5 ([19]) in the “prefix-suffix” 25

mode to compute a 128-bit “message digest” of the registration message. The 26

Authenticator value is a 128-bit value computed as the MD5 checksum over the 27

following stream of bytes: 28

 the shared secret defined by the mobility security association between the PCF and 29

the PDSN and by the SPI value specified in the authentication extension, followed 30

by 31

 the protected fields from the registration message, in the order specified above, 32

followed by 33

 the shared secret again. 34

The Authenticator field itself and the UDP header are NOT included in the computation 35

of the Authenticator value. The receiver uses the SPI value within an authentication 36

extension to determine the security context, and to compute the Authenticator value. A 37

mismatch in the Authenticator values results in rejection of the registration message with 38

error code „131‟ (sending node failed authentication). Refer to [20] for implementation 39

details. 40

3GPP2 A.S0017-D v3.0

9 Section 2

2.0 Message Procedures 1

This section describes message procedures for the A10/A11 interface. In the following 2

sections, the term “valid” is used for messages that pass authentication and whose 3

Identification information element is valid (refer to section 4.2.7). 4

2.1 A10 Connection Establishment, Refresh and Release 5

Procedures 6

This section describes message procedures to establish, refresh or release an A10 7

connection. The release of an A10 connection is controlled by the PCF. For PDSN 8

initiated A10 connection release, the PDSN requests that the PCF release the connection. 9

2.1.1 A11-Registration Request 10

This message is sent from the PCF to the PDSN to initiate establishment, refresh or 11

release of an A10 connection. In addition, accounting information pertaining to an A10 12

connection may be included in any A11-Registration Request message for that 13

connection. Refer to section 2.3 for further details. 14

2.1.1.1 Successful Establishment Operation 15

When the PCF receives an A9-Setup-A8 message from a BS, the PCF shall initiate setup 16

of an A10 connection as indicated below unless it has an existing A10 connection for the 17

identified user and SR_ID. 18

 If the A9-Setup-A8 message does not contain a handoff indication, then the PCF 19

shall initiate setup of the A10 connection upon receiving the A9-Setup-A8 message. 20

 In a fast handoff situation, the (target) PCF shall initiate setup of the A10 connection 21

upon receiving the A9-Setup-A8 message. 22

 In all other handoff situations, the (target) PCF shall initiate setup of the A10 23

connection when the (target) BS captures the MS (i.e., upon receiving an A9-AL 24

Connected message from the BS). 25

The PCF initiates setup of an A10 connection by sending an A11-Registration Request 26

message to the selected PDSN (refer to “PDSN Selection Algorithm” in [13]) with a non-27

zero Lifetime value. After sending this message, the PCF shall start timer T

regreq

. The 28

A11-Registration Request message is structured as specified in section 3.1. 29

If the connection setup request is accepted, the PDSN creates a binding record for the 30

A10 connection by creating an association between the PDSN Session Identifier (PDSN 31

SID) and the IMSI, the MN Session Reference ID and PCF Addresses. If both the PCF 32

and the PDSN support a Session Identifier Version higher than „0‟, the PDSN may 33

choose any PDSN SID, otherwise the PDSN SID shall be identical to the PCF Session 34

Identifier (PCF SID). In the case of multiple A10 connections for an MS, each A10 35

connection has its own binding record and Lifetime timer. 36

The PCF and the PDSN shall use the PCF IP Address (sent in the A11-Registration 37

Request message) and the PDSN IP Address (returned in the A11-Registration Reply 38

message) as the A10 connection endpoints for the transport of user traffic. The PCF IP 39

Address and the PDSN IP Address form the unique link layer ID for each A10 40

3GPP2 A.S0017-D v3.0

Section 2 10

connection. The PCF and the PDSN maintain an association of the MS‟s IMSI address 1

and MN Session Reference ID with the A10 connection. 2

When establishing a new A10 connection, the PCF shall include the ANID NVSE with 3

the Current Access Network Identifiers (CANID) as specified in [13]. If the PCF received 4

the ANID from the BS, it shall populate it in the PANID field of the ANID NVSE sent in 5

the A11-Registration Request message. 6

If the PCF is able to determine that the setup of the A10 connection is due to a dormant 7

handoff or an inter-PCF hard handoff (e.g., the A9-Setup-A8 message included the 8

Access Network Identifiers (ANID) IE or the Data Ready Indicator field in the A9 9

Indicators IE was set to „0‟), the PCF shall include the Mobility Event Indicator (MEI) 10

CVSE in the A11-Registration Request message. The PCF may provide the PDSN with 11

an indication of PCF enabled features for the A10 connection (e.g. short data indication). 12

In a fast handoff, the (target) PCF shall set the flag bit S to „1‟, include the Anchor P-P 13

Address and set the Lifetime value to T

presetup

in the A11-Registration Request message. 14

In other cases the PCF shall set the Lifetime to T

rp.

2.1.1.2 Successful Refresh Operation 16

All A11-Registration Request messages with a non-zero Lifetime value sent for an 17

existing A10 connection have the effect of requesting a refresh of that A10 connection. 18

When sending an A11-Registration Request message for an already existing A10 19

connection, the PCF shall use the same Key value (refer to the Session Specific 20

Extension in section 4.2.12). 21

 If the A9-Setup-A8 message does not contain a handoff indication, then the PCF 22

shall send an A11-Registration Request message to the PDSN upon receiving the 23

A9-Setup-A8 message. 24

 In a fast handoff, the (target) PCF shall send an A11-Registration Request message 25

to the PDSN upon receiving the A9-Setup-A8 message. 26

 In all other handoff situations, the (target) PCF shall send an A11-Registration 27

Request message to the PDSN to initiate setup of the A10 connection when the 28

(target) BS captures the MS (i.e., upon receiving an A9-AL Connected message from 29

the BS). 30

If the PCF is able to determine that an inter-PCF hard handoff has occurred (e.g., the A9-31

Setup-A8 message included the Access Network Identifiers (ANID) IE or the Data Ready 32

Indicator field in the A9 Indicators IE is set to „0‟), the PCF shall include the MEI CVSE 33

and the ANID NVSE in the A11-Registration Request message. 34

In a fast handoff case the Lifetime value shall be set to T

presetup

; in all other cases the 35

Lifetime value shall be set to T

. 36

If the PCF set the Lifetime value to T

presetup

in the A11-Registration Request message 37

(i.e., in the case of a fast handoff), then the PCF shall not refresh the A10 connection 38

unless it is notified that the MS has successfully accessed the target BS. At that time, the 39

PCF refreshes the A10 connection with the PDSN by sending an A11-Registration 40

Request message with Lifetime value set to T

. 41

If the PCF set the Lifetime value to T

, then the PCF periodically refreshes the A10 42

connection with the PDSN by sending an A11-Registration Request message with a non-43

3GPP2 A.S0017-D v3.0

11 Section 2

zero Lifetime value before the A10 connection registration Lifetime timer expires. After 1

sending this message, the PCF shall start timer T

regreq

. 2

2.1.1.3 Successful Release Operation 3

The PCF may initiate release of the A10 connection by sending an A11-Registration 4

Request message to the PDSN with Lifetime field set to zero. The PCF shall include 5

accounting related and other information in the A11-Registration Request message. After 6

receiving this message, the PDSN shall remove the binding record for the A10 7

connection and save the accounting related and other information for further processing. 8

The PDSN shall send an A11-Registration Reply message to the PCF with the Lifetime 9

parameter set to „0‟; refer to section 2.1.2.3. 10

2.1.1.4 Failure Operation 11

Failure detection at the PDSN: If the A11-Registration Request message is invalid, the 12

PDSN shall send an A11-Registration Reply message indicating authentication failure 13

(Code value 83H) or identification mismatch (Code value 85H) and shall then discard the 14

A11-Registration Request message; refer to section 2.1.2. If the PDSN indicates 15

identification mismatch (Code value 85H) in the A11-Registration Reply message, the 16

PDSN shall also include its own time in the 32 high-order bits of the Identification 17

information element of this message to allow the PCF to avoid identification mismatch 18

for subsequent A11-Registration Request messages. 19

If the Lifetime timer for an A10 connection expires before the PDSN has received a valid 20

A11-Registration Request message from the PCF, then the PDSN shall delete the binding 21

record for the A10 connection. 22

Failure detection at the PCF: If the PCF does not receive a valid A11-Registration Reply 23

message from the PDSN before timer T

regreq

expires, the PCF may retransmit the A11-24

Registration Request message with a new timestamp in the Identification information 25

element and restart timer T

regreq

. A connection establishment or refresh is considered to 26

have failed if no valid A11-Registration Reply message is received after a configurable 27

number of A11-Registration Request message retransmissions. For a connection refresh 28

or release, on failure to receive a valid A11-Registration Reply message in response to a 29

configurable number of A11-Registration Request message retransmissions, the PCF 30

removes the binding record for the A10 connection. 31

2.1.2 A11-Registration Reply 32

The PDSN sends this message to the PCF to acknowledge receipt of an A11-Registration 33

Request message. 34

2.1.2.1 Successful Establishment Operation 35

Upon receipt of an A11-Registration Request message with a nonzero Lifetime value, the 36

PDSN shall respond with an A11-Registration Reply message containing the appropriate 37

value in the Code IE. For a valid A11-Registration Request message, if the PDSN accepts 38

establishment of the A10 connection, it shall send a Registration Accepted indication 39

(Code value 00H) and a non-zero Lifetime parameter value in the message. The value of 40

the Lifetime parameter in the A11-Registration Reply message shall be less or equal to 41

the value of the Lifetime parameter received in the A11-Registration Request message. 42

Upon receiving the A11-Registration Reply message, the PCF shall perform 43

3GPP2 A.S0017-D v3.0

Section 2 12

authentication and identification checks. After the message passes the checks, the PCF 1

shall stop timer T

regreq

and start the Lifetime timer initialized to the value of the returned 2

Lifetime parameter. 3

If the PDSN has data to send to the PCF when it receives an A11-Registration Request 4

message, the PDSN shall include a Data Available Indication as a CVSE in the A11-5

Registration Reply message. 6

If the PDSN accepts a fast handoff request, the A11-Registration Reply message shall 7

include an NVSE containing the Anchor P-P Address value copied from the 8

corresponding A11-Registration Request message. If the PDSN supports fast handoff and 9

becomes the anchor PDSN, the PDSN shall include its Anchor P-P Address in an NVSE 10

in the A11-Registration Reply message. 11

If the selected PDSN does not accept establishment of the A10 connection, it shall return 12

an A11-Registration Reply message with a reject result code in the Code IE. Upon receipt 13

of this message, the PCF shall stop timer T

regreq

. 14

The PDSN may return an A11-Registration Reply message with result code „88H‟ 15

(Registration Denied – unknown PDSN address). When code „88H‟ is used, an alternate 16

PDSN address is included in the A11-Registration Reply message. The address of the 17

alternate proposed PDSN shall be returned in the Home Agent field of the A11-18

Registration Reply message. Upon receipt of this message, the PCF shall stop timer 19

regreq

. 20

On receipt of an A11-Registration Reply message with code „88H‟, the PCF shall either 21

initiate establishment of the A10 connection with the proposed PDSN by sending a new 22

A11-Registration Request message as indicated in this section, or it shall use internal 23

algorithms to select a new PDSN. 24

If the PCF receives a valid A11-Registration Reply message before timer T

regreq

expires 25

that indicates identification mismatch (Code value 85H), the PCF may adjust the clock 26

that it uses for communication with the PDSN, retransmit the A11-Registration Request 27

message with a newly generated Identification IE, and restart timer T

regreq

. 28

On receipt of a valid A11-Registration Reply message with another result code, 29

depending on the result code, the PCF may attempt to re-try setting up the A10 30

connection with the same or another PDSN; refer to “PDSN Selection Algorithm” in 31

[13]. 32

The PDSN may provide the PCF with an indication of PDSN enabled features for the 33

A10 connection (e.g. flow control). 34

2.1.2.2 Successful Refresh Operation 35

Upon receipt of a valid A11-Registration Request message with a nonzero Lifetime 36

value, the PDSN shall respond with an A11-Registration Reply message with an accept 37

indication (Code value 00H), including a Lifetime parameter value less or equal to the 38

value of the received Lifetime parameter and restart the Lifetime timer initialized to the 39

value of the returned Lifetime parameter. Upon receipt of this message, the PCF shall 40

stop timer T

regreq

and start the Lifetime timer initialized to the value of the returned 41

Lifetime parameter. 42

剩余85页未读，继续阅读

Brandy16

粉丝: 0
资源: 3

2011年7月版A10A11协议规范：3GPP2 IOS

全志a10刷机工具

全志A10固件编辑工具

全志A10 MAC OSX 固件更新工具

函数或变量 'a11' 无法识别。 出错 untitled (第 3 行) a10,a11,a12,a13,a20,a21,a22,a23,a30,a31,a32,a33,tc1,tc2,tcf,theta1,theta2,theta3,theta4;

函数或变量 'a11' 无法识别。 出错 untitled (第 2 行) syms a10,a11,a12,a13,a20,a21,a22,a23,a30,a31,a32,a33,tc1,tc2,tcf,theta1,theta2,theta3,theta4;

使用LabelEncoder 和 OneHotEncoder将csv文件列标签为A1,A4,A5,A6,A7,A9,A10,A11,A12,A13,A16的英文标签自动替换成不同数字

Matrix4f(//接受16个浮点参数保存为中介4x4矩阵 float a00, float a01, float a02, float a03, float a10, float a11, float a12, float a13, float a20, float a21, float a22, float a23, float a30, float a31, float a32, float a33 );转QMatrix4x4类型

csr8510 a10驱动

英伟达a10 gpu是那一年的，与a40 gpu比，性能差别如何

最新资源

函数或变量 'a11' 无法识别。出错 untitled (第 3 行) a10,a11,a12,a13,a20,a21,a22,a23,a30,a31,a32,a33,tc1,tc2,tcf,theta1,theta2,theta3,theta4;

函数或变量 'a11' 无法识别。出错 untitled (第 2 行) syms a10,a11,a12,a13,a20,a21,a22,a23,a30,a31,a32,a33,tc1,tc2,tcf,theta1,theta2,theta3,theta4;