Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 24.501  Word version:  18.5.0

Top   Top   Up   Prev   None
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…   D.6.8   D.7… 
D.7 Timers of UE policy delivery service  D.8 Handling of unknown, unforeseen, and erroneous UPDS data  D.8.1 General  D.8.2 Message too short or too long  D.8.3 Unknown or unforeseen procedure transaction identity  D.8.4 Unknown or unforeseen message type  D.8.5 Non-semantical mandatory information element errors  D.8.6 Unknown and unforeseen IEs in the non-imperative message part  D.8.7 Non-imperative message part errors  D.8.8 Messages with semantically incorrect contents  $ Change history 

 

D.7  Timers of UE policy delivery service  p. 1109

Timers of UE policy delivery service are shown in Table D.7.1.
TIMER NUM. TIMER VALUE CAUSE OF START NORMAL STOP ON THE 1st, 2nd, 3rd, 4th EXPIRY (NOTE 1)
T3501NOTE 1Transmission of MANAGE UE POLICY COMMANDMANAGE UE POLICY COMMAND COMPLETE or MANAGE UE POLICY COMMAND REJECT message receivedRetransmission of MANAGE UE POLICY COMMAND message
NOTE 1:
The value of this timer is network dependent.
Up

D.8  Handling of unknown, unforeseen, and erroneous UPDS data |R16|  p. 1109

D.8.1  General  p. 1109

The procedures specified in the subclause apply to those messages which pass the checks described in this subclause.
This subclause also specifies procedures for the handling of unknown, unforeseen, and erroneous UPDS data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the UPDS.
Subclause D.8.1 to Subclause D.8.8 shall be applied in order of precedence.
Detailed error handling procedures in the network are implementation dependent and may vary from PLMN to PLMN. However, when extensions of UPDS are developed, networks are assumed to have the error handling which is indicated in this subclause as mandatory ("shall") and that is indicated as strongly recommended ("should").
Also, the error handling of the network is only considered as mandatory or strongly recommended when certain thresholds for errors are not reached during a dedicated connection.
For definition of semantical and syntactical errors see subclause 11.4.2 of TS 24.007.
Up

D.8.2  Message too short or too long  p. 1109

D.8.2.1  Message too short  p. 1109

When a message is received that is too short to contain a complete message type information element, that message shall be ignored, c.f. TS 24.007.

D.8.2.2  Message too long  p. 1109

The maximum size of a UE policy delivery service message is 65535 octets.

D.8.3  Unknown or unforeseen procedure transaction identity  p. 1110

D.8.3.1  Procedure transaction identity  p. 1110

The following network procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in a UPDS message:
  1. In case the network receives a MANAGE UE POLICY COMPLETE message or MANAGE UE POLICY COMMAND REJECT message in which the PTI value is an assigned or unassigned value that does not match any PTI in use, the network shall ignore the UPDS message.
  2. In case the network receives a UPDS message in which the PTI value is a reserved value, the network shall ignore the UPDS message.
The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in a UPDS message:
  1. In case the UE receives a UPDS message in which the PTI value is a reserved value, the UE shall ignore the UPDS message.
Up

D.8.4  Unknown or unforeseen message type  p. 1110

If the UE or the network receives a UPDS message with message type not defined for the UPDS or not implemented by the receiver, it shall ignore the UPDS message.
If the UE receives a message not compatible with the UPDS state, the UE shall ignore the UPDS message.
If the network receives a message not compatible with the UPDS state, the network actions are implementation dependent.
Up

D.8.5  Non-semantical mandatory information element errors  p. 1110

D.8.5.1  Common procedures  p. 1110

When on receipt of a message,
  1. an "imperative message part" error; or
  2. a "missing mandatory IE" error
is diagnosed or when a message containing:
  1. a syntactically incorrect mandatory IE;
  2. an IE with an IEI unknown in the message, but encoded as "comprehension required" (see TS 24.007); or
  3. an out of sequence IE encoded as "comprehension required" (see TS 24.007) is received,
the UE shall ignore the UPDS message;
the network shall proceed as follows:
the network shall:
  1. try to treat the message (the exact further actions are implementation dependent); or
  2. ignore the message.
Up

D.8.6  Unknown and unforeseen IEs in the non-imperative message part  p. 1111

D.8.6.1  IEIs unknown in the message  p. 1111

The UE shall ignore all IEs unknown in a message which are not encoded as "comprehension required" (see TS 24.007).
The network shall take the same approach.

D.8.6.2  Out of sequence IEs  p. 1111

The UE shall ignore all out of sequence IEs in a message which are not encoded as "comprehension required" (see TS 24.007).
The network should take the same approach.

D.8.6.3  Repeated IEs  p. 1111

If an information element with format T, TV, TLV, or TLV-E is repeated in a message in which repetition of the information element is not specified in subclause D.5, the UE shall handle only the contents of the information element appearing first and shall ignore all subsequent repetitions of the information element. When repetition of information elements is specified, the UE shall handle only the contents of specified repeated information elements. If the limit on repetition of information elements is exceeded, the UE shall handle the contents of information elements appearing first up to the limit of repetitions and shall ignore all subsequent repetitions of the information element.
The network should follow the same procedures.
Up

D.8.7  Non-imperative message part errors  p. 1111

This category includes:
  1. syntactically incorrect optional IEs; and
  2. conditional IE errors.

D.8.7.1  Syntactically incorrect optional IEs  p. 1111

The UE shall treat all optional IEs that are syntactically incorrect in a message as not present in the message.
The network shall take the same approach.

D.8.7.2  Conditional IE errors  p. 1111

When upon receipt of a UPDS message the UE diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error, or when it receives a UPDS message containing at least one syntactically incorrect conditional IE, the UE shall ignore the message.
When the network receives a message and diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives a message containing at least one syntactically incorrect conditional IE, the network shall either:
  1. try to treat the message (the exact further actions are implementation dependent); or
  2. ignore the message.
Up

D.8.8  Messages with semantically incorrect contents  p. 1112

When a message with semantically incorrect contents is received, the UE shall perform the foreseen reactions of the procedural part of subclause D.2. If, however no such reactions are specified, the UE shall ignore the message.
The network should follow the same procedure.

E  Void

$  Change history  p. 1114

Up   Top