The set command is used to request the MT to return all the route selection descriptors for the URSP rules with different precedence values matching the traffic descriptor indicated by the input parameters in
<APPID>,
<OSID&APPID>,
<DNNs>,
<FQDN>,
<Connection_capabilities>,
<remote_ipv4_address_and_mask>,
<remote_ipv6_address_and_prefix_length>,
<protocol number (ipv4)/next header (ipv6)>,
<single_remote_port>,
<remote port range>,
<security para index>,
<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>,
<flow label>,
<ether_type>,
<destination_mac_address>,
<cTagVid>,
<sTagVid>,
<cTagPcpDei>,
<sTagPcpDei>,
<Regular_expression>,
<PIN ID>,
<Connectivity group ID>.
A special form of the set command can be given as +C5GURSPQRY=. This form can be used as Match-all type to request the MT to return the default URSP rule.
The read command is used to return all of the URSP rules stored at MT.
Test command returns values supported as compound values.
<APPID>
string type. Indicates an application.
<OSID&APPID>
string type. Indicates an operating system and an associated application.
<DNNs>
string type. The string can be separated by semicolon(s), indicates the list of
<DNN> referred in
clause 10.1.57.
<FQDN>
string type. Indicates a fully qualified Domain Name.
<Connection_capabilities>
integer type. A decimal value indicates the connection's supported services according to Table 5.2.1 of
TS 24.526.
<remote_ipv4_address_and_mask>
string type. The string is given as dot-separated numeric (0-255) parameters which indicates a remote IPv4 address and the associated mask, on the form of
"a1.a2.a3.a4.m1.m2.m3.m4".
<remote_ipv6_address_and_prefix_length>
string type. The string is given as dot-separated numeric (0-255) parameters which indicates a remote IPv6 address and the associated length of the prefix, on the form of
"a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16. m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16".
When +CGPIAF is supported, its settings can influence the format of this parameter returned with the read form of +C5GURSPQRY.
<protocol number (ipv4) / next header (ipv6)>
integer type. Value range is from 0 to 255.
<single_remote_port>
integer type. Value range is from 0 to 65535.
<remote port range>
string type. The string is given as dot-separated numeric (0-65535) parameters on the form
"f.t".
<security para index>
numeric value in hexadecimal format. Value range is from 00000000 to FFFFFFFF.
<type of service (tos) (ipv4) and mask/traffic class (ipv6) and mask>
string type. The string is given as dot-separated numeric (0-255) parameters on the form
"t.m".
<flow label>
numeric value in hexadecimal format. The value range is from 00000 to FFFFF. Valid for IPv6 only.
<ether_type>
integer type. Value range is from 0 to 65535
<destination_mac_address>
string type, on the form of
"a1.a2.a3.a4.a5.a6".
<cTagVid>
integer type. See IEEE 802.1Q [181].
<sTagVid>
integer type. See IEEE 802.1Q [181].
<cTagPcpDei>
integer type. See IEEE 802.1Q [181].
<sTagPcpDei>
integer type. See IEEE 802.1Q [181].
<PIN ID>
string type. Indicates a PIN.
<Connectivity group ID>
string type. Indicates a connectivity group configured in the 5G-RG.
<Regular_expression>
string type. The regular expression value field shall take the form of Extended Regular xpressions (ERE) as defined in chapter 9 in IEEE 1003.1-2004 Part 1 [182].
<ursp_rule_type>
integer type. Indicates if the type of the URSP rule.
0
non-default URSP rule
1
default URSP rule
<ursp_rule_precedence>
integer type. Indicates the precedence of the URSP rule.
<route_selection_descriptor_precedence>
Indicates the precedence of the route selection descriptor.
<SSC_mode>
integer type. Indicates the session and service continuity (SSC) mode for the PDU session in 5GS, see
TS 23.501.
0
indicates that the PDU session is associated with SSC mode 1
1
indicates that the PDU session is associated with SSC mode 2
2
indicates that the PDU session is associated with SSC mode 3
<NSSAI>
string type in hexadecimal character format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). The
<NSSAI> is coded as a list of
<S-NSSAI>s separated by colons. This parameter shall not be subject to conventional character conversion as per +CSCS. The
<S-NSSAI> has one of the forms:
sst
only slice/service type (SST) is present
sst;mapped_sst
SST and mapped configured SST are present
sst.sd
SST and slice differentiator (SD) are present
sst.sd;mapped_sst
SST, SD and mapped configured SST are present
sst.sd;mapped_sst.mapped_sd
SST, SD, mapped configured SST and mapped configured SD are present
<pdp_type>
string type. Indicates the type of the PDU session. Specifies the type of packet data protocol.
IP
Internet Protocol (IETF STD 5 [103]). Indicates that the PDU session type is IPv4 only
IPv6
Internet Protocol, version 6 (see
RFC 2460). Indicates that the PDU session type is IPv6 only
IPv4v6
Virtual
<PDP_type> introduced to handle dual IP stack UE capability. (See
TS 24.301). Indicates that the PDU session type is IPv4v6
Unstructured
Transfer of Unstructured data to the Data Network via N6 (see
TS 23.501). Indicatesthat the PDU session type is Unstructured only
Ethernet
Ethernet protocol (IEEE 802.3). Indicates that the PDU session type is Ethernet only
<preferred_access_type>
integer type. Indicates the preferred access type for the PDU session in 5GS, see
TS 24.526.
0
indicates that the preferred access type is 3GPP access
1
indicates that the preferred access type is non-3GPP access
<Non-seamless_non-3GPP_offload_indication>
integer type.
0
indicates that the non-seamless non-3GPP offload is invalid
1
indicates that the non-seamless non-3GPP offload is valid
<Location_criteria_type>
string type. The route selection descriptor component value field may contain one or more types of location area and is encoded as shown in Figure 5.2.5 and Table 5.2.2 of
TS 24.526.
<Time_window_type>
string type. The Time window type value field shall be encoded as a sequence of a Starttime field followed by a Stoptime field. The Starttime field is represented by the number of seconds since 00:00:00 on 1 January 1970 and is encoded as the 64-bit NTP timestamp format defined in
RFC 5905, where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The encoding of the Stoptime field is the same as the Starttime field. The Starttime field and the Stoptime field are separated by a dot.