User's Manual

AVIATOR 200S/700S
User Manual
COBHAM PRIVATE
Document:
98-158752
Page:
56 of 105
Revision:
B
Level:
COM
CC:
1
(T: 99-161853-F)
9.2.4.5 Binding to an active Primary PDP context
Before being able to modify, control or add a secondary PDP to a primary PDP context, the TELNET session
needs to be linked to a primary PDP through the use of the AT_IPDS AT-command. This indicates that all
subsequent AT commands are related to the chosen PPPoE session and related PDP contexts.
A connection to the out-of-band control interface must be established as described in section 9.2.4.3.
Refer to Appendix D.3.11 for further guidance regarding the AT_IPDPS AT-command.
9.2.4.6 Adding a Secondary PDP Context
As described in section 9.2.1, a secondary PDP context and Traffic Flow Template (TFT) may be used to isolate
specific traffic types or data that require a different QoS.
Example: A 16 kbps streaming class PDP context for UDP type traffic in the port range 50000 to 50005.
Method 1
The AT-commands may be sent separately:
• AT+CGDSCONT=2,1 Attached a secondary CID to the primary CID number 1.
• AT+CGEQREQ=2,1,16,16,16,16 Defines the PDP context type and the requested maximum
and guaranteed QoS.
• AT+CGEQMIN=2,1,16,16,16,16 Defines the requested minimum QoS.
• AT+CGTFT=2,1,0,,17,50000.50005 Defines the downlink TFT (UDP port range 50000 to 50005).
• AT+CGACT=1,2 Activates the secondary PDP context.
Method 2
The AT commands may be sent together, separated by a “;”:
• AT+CGDSCONT=2,1;+CGEQREQ=2,1,16,16,16,16;+CGEQMIN=2,1,16,16,16,16;+CGTFT=2
,1,0,,17,50000.50005;+CGACT=1,2
9.2.4.7 Traffic Flow Templates
A Traffic Flow Template (TFT) is used in conjunction with a secondary PDP context. Multiple TFT’s may be
linked to the same secondary PDP context, however each must be uniquely identified by:
<packet_filter_identifier>
 TFT identifier between 1 & 8.
 Multiple (max 8) TFTs may be applied to a single secondary.
 Starts with ‘1’.
 Does not indicate TFT precedence, only identifier.
 Multiple TFTs may be added to a single secondary context by incrementing the
<packet_filter_identifier> allowing multiple ‘groups’ of traffic to be routed to the secondary context.
<evaluation_precedence_index>
 The index must be a unique number within all TFTs associated with the same primary PDP.
 The evaluation precedence index defines the precedence given to a filter when routing traffic.
 The filter with the precedence index of 0 is the first to be applied; the filter with the precedence index
of 1 is next and so on. The lowest possible evaluation precedence index is 255. Traffic that may be
applicable to more than one TFT will be routed over the TFT with the highest precedence i.e. whichever
TFT is evaluated first.
Refer to Appendix D.3.9 for further guidance reading the +CGTFT AT-command.