Content for  TS 27.007  Word version:  18.5.0

This command allows the TE to specify a Packet Filter - PF for a Traffic Flow Template - TFT that is used in the GGSN and in the Packet GW for routing of packets onto different QoS flows towards the TE. The concept is further described in the TS 23.060, TS 23.501 and TS 24.501. A TFT consists of from one and up to 16 Packet Filters, each identified by a unique <packet filter identifier>. A Packet Filter also has an <evaluation precedence index> that is unique within all TFTs associated with all PDP contexts that are associated with the same PDP address. The set command specifies a Packet Filter that is to be added to the TFT stored in the MT and used for the context identified by the (local) context identification parameter, <cid>. The specified TFT will be stored in the GGSN, the Packet GW and UPF only at activation or MS-initiated modification of the related context. Since this is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, the +CGTFT command is effectively an extension to these commands. The Packet Filters consist of a number of parameters, each of which may be set to a separate value. A special form of the set command, +CGTFT=<cid> causes all of the Packet Filters in the TFT for context number <cid> to become undefined. At any time there may exist only one PDP context with no associated TFT amongst all PDP contexts associated to one PDP address. At an attempt to delete a TFT, which would violate this rule, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. Refer to clause 9.2 for possible <err> values. The read command returns the current settings for all Packet Filters for each defined context. The test command returns values supported as compound values. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line. TFTs shall be used for PDP-type IP and PPP only. For PDP-type PPP a TFT is applicable only when IP traffic is carried over PPP. If PPP carries header-compressed IP packets, then a TFT cannot be used.

<cid> <PDP_type> For the following parameters, see also TS 23.060, TS 23.501 and TS 24.501: <packet filter identifier> <evaluation precedence index> <remote address and subnet mask> <protocol number (ipv4) / next header (ipv6)> <local port range> <remote port range> <ipsec security parameter index (spi)> <type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask> <flow label (ipv6)> <direction> <local address and subnet mask> When +CGPIAF is supported, its settings can influence the format of this parameter returned with the read form of +CGTFT. <QRI> <traffic_segregation> <destination MAC address> <source MAC address> <802.1Q C-TAG VID> <802.1Q S-TAG VID> <802.1Q C-TAG PCP/DEI> <802.1Q S-TAG PCP/DEI> <ethertype> Some of the above listed attributes may coexist in a Packet Filter while others mutually exclude each other, the possible combinations are shown in TS 23.060, TS 23.501 and TS 24.501.

Optional.

This command allows the TE to specify a Quality of Service Profile that is used when the MT activates a PDP context. The set command specifies a profile for the context identified by the (local) context identification parameter, <cid>. Since this is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, the +CGQREQ command is effectively an extension to these commands. The QoS profile consists of a number of parameters, each of which may be set to a separate value. A special form of the set command, +CGQREQ=<cid> causes the requested profile for context number <cid> to become undefined. The read command returns the current settings for each defined context. The test command returns values supported as compound values. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line.

<cid> <PDP_type> The following parameters are defined in TS 23.107: <precedence> <delay> <reliability> <peak> <mean> If a value is omitted for a particular class then the value is considered to be unspecified.

Optional. If the command is not implemented then all the values are considered to be unspecified.

This command allows the TE to specify a minimum acceptable profile which is checked by the MT against the negotiated profile when the PDP context is activated. The set command specifies a profile for the context identified by the (local) context identification parameter, <cid>. Since this is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, the +CGQMIN command is effectively an extension to these commands. The QoS profile consists of a number of parameters, each of which may be set to a separate value. A special form of the set command, +CGQMIN=<cid> causes the minimum acceptable profile for context number <cid> to become undefined. In this case no check is made against the negotiated profile. The read command returns the current settings for each defined context. The test command returns values supported as compound values. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line.

<cid> <PDP_type> The following parameters are defined in TS 23.107: <precedence> <delay> <reliability> <peak> <mean> If a value is omitted for a particular class then this class is not checked.

Optional. If the command is not implemented then no check is made against the negotiated profile.

This command allows the TE to specify a UMTS Quality of Service Profile that is used when the MT activates a PDP context. The set command specifies a profile for the context identified by the (local) context identification parameter, <cid>. The specified profile will be stored in the MT and sent to the network only at activation or MS-initiated modification of the related context. Since this is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, the +CGEQREQ command is effectively an extension to these commands. The QoS profile consists of a number of parameters, each of which may be set to a separate value. A special form of the set command, +CGEQREQ=<cid> causes the requested profile for context number <cid> to become undefined. The read command returns the current settings for each defined context. The test command returns values supported as compound values. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line.

<cid> <PDP_type> For the following parameters, see also TS 23.107. <Traffic class> <Maximum bitrate UL> <Maximum bitrate DL> <Guaranteed bitrate UL> <Guaranteed bitrate DL> <Delivery order> <Maximum SDU size> <SDU error ratio> <Residual bit error ratio> <Delivery of erroneous SDUs> <Transfer delay> <Traffic handling priority> <Source Statistics Descriptor> <Signalling Indication> If a value is omitted for a particular class then the value is considered to be unspecified.

Optional. If the command is not implemented then all the values are considered to be unspecified.

This command allows the TE to specify a minimum acceptable profile, which is checked by the MT against the negotiated profile returned in the PDP context establishment and PDP contect modification procedures. The set command specifies a profile for the context identified by the (local) context identification parameter, <cid>. The specified profile will be stored in the MT and checked against the negotiated profile only at activation or MS-initiated modification of the related context. Since this is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, the +CGEQMIN command is effectively an extension to these commands. The QoS profile consists of a number of parameters, each of which may be set to a separate value. A special form of the set command, +CGEQMIN=<cid> causes the minimum acceptable profile for context number <cid> to become undefined. In this case no check is made against the negotiated profile. The read command returns the current settings for each defined context. The test command returns values supported as compound values. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line.

<cid> <PDP_type> For the following parameters, see also TS 23.107. <Traffic class> <Maximum bitrate UL> <Maximum bitrate DL> <Guaranteed bitrate UL> <Guaranteed bitrate DL> <Delivery order> <Maximum SDU size> <SDU error ratio> <Residual bit error ratio> <Delivery of erroneous SDUs> <Transfer delay> <Traffic handling priority> <Source Statistics Descriptor> <Signalling Indication> If a value is omitted for a particular class then the value is considered to be unspecified.

Optional. If the command is not implemented then no check is made against the negotiated profile.

This command allows the TE to retrieve the negotiated QoS profiles returned in the PDP context establishment procedure. The execution command returns the negotiated QoS profile for the specified context identifiers, <cid>s. The QoS profile consists of a number of parameters, each of which may have a separate value. If the parameter <cid> is omitted, the relevant information for all established PDP contexts are returned. The test command returns a list of <cid>s associated with active contexts.

<cid> For the following parameters, see also TS 23.107. <Traffic class> <Maximum bitrate UL> <Maximum bitrate DL> <Guaranteed bitrate UL> <Guaranteed bitrate DL> <Delivery order> <Maximum SDU size> <SDU error ratio> <Residual bit error ratio> <Delivery of erroneous SDUs> <Transfer delay> <Traffic handling priority> If a value is omitted for a particular class then the value is considered to be unspecified.

Optional.

The execution command is used to attach the MT to, or detach the MT from, the Packet Domain service. After the command has completed, the MT remains in V.250 command state. If the MT is already in the requested state, the command is ignored and the OK response is returned. If the requested state cannot be achieved, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. Refer to clause 9.2 for possible <err> values. Any active PDP contexts will be automatically deactivated when the attachment state changes to detached. The read command returns the current Packet Domain service state. The test command is used for requesting information on the supported Packet Domain service states.

<state>

Optional.