hash
stringlengths
32
32
doc_id
stringlengths
5
12
section
stringlengths
4
1.47k
content
stringlengths
0
6.67M
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6 Asynchronous Transparent Bearer Capabilities
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.1 Data Rate Adaptation
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.1.1 Definition
-29.2.6.1.2 Conformance requirement An MS supporting asynchronous transparent bearer capabilities shall perform data rate adaptation and support the frames at the Um-interface according to the following specifications: 1. 3GPP TS 04.21, subclauses 4.1 and 4.4, clauses 5 and 7.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.1.3 Test purpose
The purpose of these tests is to verify the conversion between an asynchronous data stream at the R-interface and the 3GPP TS 04.21 frames at the Um-interface.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.1.4 Method of test
The Test shall be carried out for all possible user data rates which are supported by the MS in asynchronous mode (see below). Procedure: a) A data call shall be set up between the SS and the MS with a BCIE (see below) supported by the MS. The next step shall be entered immediately after TCH synchronization has been completed at the SS side. b) The interface circuit bit(s) in the 3GPP TS 04.21 frame shall be set to ON and the SS shall start to transmit pseudo random characters as described below to the MS. c) MT2 configuration: The SS shall input pseudo random characters as described below over the R-interface to the MS. MT0 configuration: the transmission of data from the MS over the Um-interface shall be stimulated (if it does not start automatically). d) Approximately 5 s after the data have been received by the SS over the Um-interface the test shall be stopped.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.1.5 Test requirements
1) During the test no 3GPP TS 04.21 frame with incorrect format (i.e. format not compliant to 3GPP TS 04.21 (see conformance requirement) or not corresponding to the user data rate currently under test) shall have been received by the SS. 2) MT2 configuration only: the user data stream input to the R-interface shall match character by character the user data stream sent to the SS over the Um-interface and the user data streams output from the R-interface shall match character by character the user data stream sent by the SS over the Um-interface.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.1.6 Generation of the asynchronous pseudo random characters
Downlink direction: The 3GPP TS 04.21 frames shall contain a bit stream which consists of repeating: - a character which is generated pseudo randomly every time; - n stop bits, where n is drawn pseudo randomly from the interval 1..15 every time. Uplink direction: The data stream at the R-interface consists of repeating: - a character which is generated pseudo randomly every time; - 1 stop bit; - 1,13 ± 1 % bit frames (i.e. 1/nominal data rate) of stop polarity.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.1.7 BCIE
Same as subclause 29.2.3. The Number of Data Bits per character (excl. parity) shall be 8. No parity bit shall be used. The Number of Stop Bits shall be 1. If the MS does not support these values different ones shall be chosen. The remaining parameters of the BCIE shall and the channel type (FR/HR) be set to a value supported by the MS.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.2 Passage of the Break Signal
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.2.1 Definition
-29.2.6.2.2 Conformance requirement An MS supporting asynchronous transparent bearer capabilities shall perform passage of the break signal in uplink and downlink direction according to: 1. 3GPP TS 04.21, subclauses 4.1, 4.2 and 4.4, clauses 5 and 7.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.2.3 Test purpose
The purpose of these tests is to verify the ability of the MS to transfer a Break Signal to the R-interface and vice versa.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.2.4 Method of test
The Test shall be carried out for all possible user data rates which are supported by the MS in asynchronous mode (see below). Procedure: a) A data call shall be set up between the SS and the MS with a BCIE (see below) supported by the MS. The next step shall be entered immediately after TCH synchronization has been completed at the SS side. b) The interface circuit bit(s) in the 3GPP TS 04.21 frame shall be set to ON. c) The SS shall send pseudo random characters with start and stop bit(s) (as selected by the BCIE) in the 3GPP TS 04.21 frames to the MS for approximately 5 s. Then it shall send the following bit sequence in the 3GPP TS 04.21 frames: - 2M+3 bits of start polarity; - 2M bits of stop polarity. d) The SS shall send pseudo random characters with start and stop bit(s) (as selected by the BCIE) in the 3GPP TS 04.21 frames to the MS for approximately 2 s. Then it shall send the following bit sequence in the 3GPP TS 04.21 frames: - for 1 s bits of start polarity; - 2M bits of stop polarity, where M is as defined in 3GPP TS 04.21, subclause 4.2, and then again pseudo random characters as above. e) The SS shall input pseudo random characters with start and stop bit(s) (as selected by the BCIE) over the R‑interface to the MS for approximately 2 s. Then it shall input the following bit sequence to the R-interface: - M bits of start polarity; - 2M bits of stop polarity. f) The SS shall input pseudo random characters with start and stop bit(s) (as selected by the BCIE) over the R-interface to the MS for approximately 2 s. Then it shall input the following bit sequence to the R-interface: - for 1 s bits of start polarity; - 2M bits of stop polarity, where M is as defined in 3GPP TS 04.21, subclause 4.2, and then again pseudo random characters as above. g) the test shall be stopped 2 s later.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.2.5 Test requirements
1) During the test no 3GPP TS 04.21 frame with incorrect format (i.e. format not compliant to 3GPP TS 04.21 (see conformance requirement) or not corresponding to the user data rate currently under test) shall have been received by the SS. 2) The user data stream sent over the Um-interface by the SS shall match character by character the user data stream output at the R-interface. 3) The two Break Signals shall be detectable at the R-interface between the same characters as having been sent. 4) The user data stream received over the Um-interface by the SS shall match character by character the user data stream input at the R-interface. 5) The two Break Signals shall be detectable at the Um-interface between the same characters as having been input.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.2.6 BCIE
Same as subclause 29.2.2.6.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.3 Overspeed/Underspeed Handling (Local Terminal)
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.3.1 Definition
-29.2.6.3.2 Conformance requirement An MS supporting asynchronous transparent bearer capabilities shall handle overspeed and underspeed of the local terminal according to: 1. 3GPP TS 04.21, subclauses 4.1, 4.3 and 4.4, clauses 5 and 7.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.3.3 Test purpose
The purpose of these tests is to verify the ability of the MS to deal with plesiosynchronous bit clocks in the MS and the TE in case of asynchronous Bearer Capabilities.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.3.4 Method of test
The Test shall be carried out for all possible user data rates supported by the MS in asynchronous mode (see below). Procedure: a) A data call shall be set up between the SS and the MS with a BCIE (see below) supported by the MS. The next step shall be entered immediately after CT107 has been set to on by the MS. b) The interface circuit bit(s) in the 3GPP TS 04.21 frame shall be set to ON. c) The SS shall input continuously pseudo random characters with a bit clock of: - nominal user data rate +2,5 % bit/s in case of less than 600 bit/s user data rate; - nominal user data rate +1 % in the other cases. (ref. 3GPP TS 04.21, subclause 4.3) to the R-interface of the MS for approximately 5 s. d) The SS shall input continuously pseudo random characters with a bit clock of nominal user rate -2,5 % (ref. ITU‑T Recommendation V.14, clause 3) to the R-interface of the MS for approximately 5 s. e) The test shall be stopped.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.3.5 Test requirements
1) During the test no 3GPP TS 04.21 frame with incorrect format (i.e. format not compliant to 3GPP TS 04.21 (see conformance requirement) or not corresponding to the user data rate currently under test) shall have been received by the SS. 2) The user data stream input to the R-interface shall match character by character the user data stream sent to the SS over the Um-interface.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.3.6 BCIE
Same as subclause 29.2.2.6. The Number of Data Bits per character (excl. parity) shall be 8. No parity bit shall be used. The Number of Stop Bits shall be 1. If the MS does not support these values different ones shall be chosen. The remaining parameters of the BCIE and the channel type (FR/HR) shall be set to a value supported by the MS.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.4 Overspeed/Underspeed Handling (Remote Terminal)
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.4.1 Definition
-29.2.6.4.2 Conformance requirement An MS supporting asynchronous transparent bearer capabilities shall handle overspeed and underspeed of the remote terminal (which shows in the structure of the 3GPP TS 04.21 frames received over the Um-interface) according to: 1. 3GPP TS 04.21, subclauses 4.1, 4.3 and 4.4, clauses 5 and 7.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.4.3 Test purpose
The purpose of these tests is to verify the ability of the MS to deal with plesiosynchronous bit clocks in the MS and the remote Terminal in case of asynchronous Bearer Capabilities. The case of underspeed is covered by subclause 29.6.1. The case of overspeed shall be tested as follows.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.4.4 Method of test
The Test shall be carried out for all possible user data rates supported by the MS in asynchronous mode (see below). Procedure: a) A data call shall be set up between the SS and the MS with a BCIE (see below) supported by the MS. The next step shall be entered immediately after CT107 has been set to on by the MS. b) The interface circuit bit(s) in the 3GPP TS 04.21 frame shall be set to ON. c) The SS shall start sending pseudo random characters in the 3GPP TS 04.21 frames over the Um-interface with minimal number of stop bits between the characters and where one stop bit is omitted every 8th character. e) The test shall be stopped 5 s later.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.4.5 Test requirements
1) During the test no 3GPP TS 04.21 frame with incorrect format (i.e. format not compliant to 3GPP TS 04.21 (see conformance requirement) or not corresponding to the user data rate currently under test) shall have been received by the SS. 2) The user data stream sent by the SS over the Um-interface shall match character by character the user data stream sent by the MS over the R-interface.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.6.4.6 BCIE
Same as subclause 29.2.6.3.6.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.7 Interchange circuit mapping for transparent bearer capabilities
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.7.1 Definition
This test cannot be applied fully to MSs which support e.g.: - CT108/2 for releasing the call (e.g. support of ITU-T Recommendation V.25bis) and/or - similar use of the circuit C for ITU-T Recommendation X.21. Therefore the test shall be applied only for those interchange circuits which do not influence Layer 3 signalling. In case of circuit C the X.21-byte timing circuit B shall not be used.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.7.2 Conformance requirement
1) An MS supporting transparent bearer capabilities with a V-series R-interface shall map the interchange circuits CT105 and CT108/2 to the 3GPP TS 04.21 frames sent over the Um-interface according to: 1.1 3GPP TS 04.21, subclauses 4.1 and 4.4, clauses 5 and 7. 1.2 3GPP TS 07.02, subclause 3.2.1. 2) An MS supporting transparent bearer capabilities with an X-series R-interface shall map the interchange circuit C to the 3GPP TS 04.21 frames sent over the Um-interface according to: 2.1 3GPP TS 04.21, subclauses 4.1 and 4.4, clauses 5 and 7. 2.2 3GPP TS 07.03, subclauses 4.2.1 and 4.2.2.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.7.3 Test purpose
The purpose of these tests is to verify the ability of the MS to correctly convey changes of the interface circuits at the R‑interface to the 3GPP TS 04.21 frame sent over the Um-interface in case of Transparent Bearer Capabilities.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.7.4 Method of test
Specific PICS statements: - PIXIT statements: - Interchange Circuits which influence Layer 3 signalling The Test shall be carried out for all user data rates supported by the MS (see below) and the circuits CT105 and CT108/2 (ITU-T Recommendation V.24) and C (ITU-T Recommendation X.21). The test shall be carried out only for those frame formats and circuits which are supported by the MS (exceptions see above). Procedure: a) A data call shall be set up between the SS and the MS with a BCIE (see below) supported by the MS. The next step shall be entered immediately after CT107 has been set to ON by the MS. b) The interface circuit bit(s) in the 3GPP TS 04.21 frame shall be set to ON and the SS shall input continuously pseudo random data to the R-interface during the following steps. The SS shall wait for approximately 1 s before entering the next step. c) The SS shall set the interchange circuit at the R-interface to OFF and wait for 2 s. d) The SS shall again set the interchange circuit at the R-interface to ON. e) After further 2 s the test shall be stopped.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.7.5 Test requirements
1) During the test no 3GPP TS 04.21 frame with incorrect format (i.e. format not compliant to 3GPP TS 04.21 (see conformance requirement) or not corresponding to the user data rate currently under test) shall have been received by the SS. 2) The change of the interchange circuit signal level shall be indicated in the 3GPP TS 04.21 frames as required by 3GPP TS 04.21 and ITU-T Recommendation V.110 (i.e. OFF state shall start and end in the correct 3GPP TS 04.21 frame).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.2.7.6 BCIE
Same as subclause 29.2.2.5.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3 Testing of non transparent data services (RLP tests)
SS sends NULL (C/R=0, P/F=0) frames when it has nothing else to send in ADM mode. SS does not use DTX if not explicitly indicated in the test and sends supervisory RR (C/R=0, P/F=0) frames when it has nothing else to send in ABM mode. N(R) is equal to N(R) of the previous frame. For the first frame N(R)=0. The information field of the Supervisory frames sent by the SS is fully coded with "1". The tolerance on timers or delays is ±10%. The SS will check FSI (Frame Start Identifier) alignment in all received RLP frames. The information field of the Supervisory frames sent by the MS is never verified. The SABM-UA exchange for RLP link establishment is initiated by the MS. Immediately upon RLP link connection, the MS may send an I+S frame containing updated status bits SA, SB and X and the SS must send it.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1 Initialization
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.1 Normal initialization done by the MS
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.1.1 Test purpose
To test the normal establishment of multiple frame operation between the SS and the MS. This test is performed twice for testing MO and MT data calls:
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.1.2 Method of test
Initial Conditions System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use default RLP parameters. MO data call: The MS is made to establish a MO non transparent data call, so that the initial conditions are that the MS is in call state U10 ("Call Active") after having sent a CONNECT ACKNOWLEDGE message. MT data call: The SS establishes a MT non transparent data call, so that the initial conditions are that the MS is in call state U10 ("Call Active") after having received a CONNECT ACKNOWLEDGE message from the SS. Case a: No negotiation will be initiated by the MS. Case b: The MS initiates negotiation of RLP default parameters. NOTE: The MS is allowed to initiate the negotiation of the RLP default parameters, within allowed ranges, defined in 3GPP TS 04.22. The MS shall do this in the ADM, after having sent a CONNECT ACKNOWLEDGE message (MO-case) or after having received a CONNECT ACKNOWLEDGE message from the SS (MT-case). The SS shall accept and use the new RLP parameters till the end of the test. Procedure The MS shall send a SABM frame. The SS responds with a correct UA frame (within T1). The SS waits for 2*T1 after the UA to ensure the SABM frame is not repeated. This confirms that the UA has been received. The MS shall be in ABM mode. After optional status bits exchange between the MS and the SS, this is verified by sending an I + S frame and waiting for the acknowledgement from the MS. The MS is returned to the idle state by clearing the call. Expected sequence MS SS 1 SABM > Within T1 < UA 2 Waits for 2*T1 ( I+S >) Optional (< I+S ) < I+S 3 4 S or I+S > The frames from the SS will be: 2: One UA frame containing: R=0, F=1. 3: One correct I+S frame in a RR frame with N(S)=0.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.1.3 Test requirements
The frames from the MS shall be: 1: One SABM frame containing: C=1, P=1. The SABM shall not be repeated. 4: One S or I+S frame with N(R)=1 acknowledging the I+S frame.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.2 Initialization failure
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.2.1 Loss of UA frame
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.2.1.1 Test purpose
To test the MS response to the loss of an UA frame during initialization.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.2.1.2 Method of test
Initial Conditions System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use default RLP parameters. The MS is made to establish a MO non transparent data call so that the initial conditions are that the MS is in call state U10 ("Call Active") after having sent a CONNECT ACKNOWLEDGE message. Case a: No negotiation will be initiated by the MS. Case b: The MS initiates negotiation of RLP default parameters. NOTE: The MS is allowed to initiate the negotiation of the RLP default parameters, within allowed ranges, defined in 3GPP TS 04.22. The MS shall do this in the ADM, after having sent a CONNECT ACKNOWLEDGE message (MO-case) or after having received a CONNECT ACKNOWLEDGE message from the SS (MT-case). The SS shall accept and use the new RLP parameters till the end of the test. Procedure The MS shall send an SABM frame. The SS ignores the first SABM frame from the MS. The MS shall wait for time-out of timer T1 and then send a second SABM frame. The SS responds to the second SABM frame with an UA frame (within T1). The MS enters in ABM mode. After optional status bits exchange between the MS and the SS, this is verified by sending an I+S frame and waiting for the acknowledgement from the MS. The MS is returned to the idle state by clearing the call. Expected sequence MS SS 1 SABM > T1 time-out 2 SABM > < UA 3 ( I+S >) Optional (< I+S ) < I+S 4 5 S or I+S > The frames from the SS will be: 3: One UA frame containing: R=0, F=1. within T1 after the second SABM. 4: One correct I+S frame in a RR frame with N(S)=0.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.2.1.3 Test requirements
The frames from the MS shall be: 1, 2: One SABM frame containing: C=1, P=1. The second SABM frame shall follow the first SABM frame after time-out of timer T1. 5: One S or I+S frame with N(R)=1 acknowledging the I+S frame.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.2.2 Total loss of UA frame
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.2.2.1 Test purpose
To test the MS response to a total loss of UA frame during initialization.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.2.2.2 Method of test
Initial Conditions System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use default RLP parameters. The MS is made to establish a MO non transparent data call so that the initial conditions are that the MS is in call state U10 ("Call Active") after having sent a CONNECT ACKNOWLEDGE message. Case a: No negotiation will be initiated by the MS. Case b: The MS initiates negotiation of RLP default parameters. NOTE: The MS is allowed to initiate the negotiation of the RLP default parameters, within allowed ranges, defined in 3GPP TS 04.22. The MS shall do this in the ADM, after having sent a CONNECT ACKNOWLEDGE message (MO-case) or after having received a CONNECT ACKNOWLEDGE message from the SS (MT-case). The SS shall accept and use the new RLP parameters till the end of the test. Procedure The MS shall send an SABM frame. The SS ignores the SABM frame from the MS. The MS shall wait for time-out of timer T1 and then send a new SABM frame. The SS ignores the SABM frame sent by the MS. These 2 last steps are repeated N2 times. The SS waits for 2 * T1 to ensure the SABM frame is not repeated. The MS shall not enter in ABM mode. This is verified by sending an I+S frame. The MS shall ignore this frame. The MS is returned to the idle state by clearing the call. Expected sequence: MS SS 1 SABM > T1 time-out SABM N2 times ............................................................................................................................... SABM > Wait 2*T1 < I+S 8 The frames from the SS will be: 8: One correct I+S frame in a RR frame containing with N(S)=0.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.1.2.2.3 Test requirements:
The frames from the MS shall be: 1, .... N2: One SABM frame containing: C=1, P=1. An SABM frame follows the previous one after time-out of timer T1.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2 Data transfer
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.1 Default conditions
The initial conditions are that the MS is in call state U10 ("Call Active") and in RLP ABM mode. During the synchronization of the traffic channel, the MS and the SS have transmitted I+S frames. Unless, other indication in the test, each test of this subclause will begin in the following conditions: - the MS has previously sent I+S frames numbered N(S)=0,...,Nms‑1 mod(62) and has previously sent a frame containing N(R) = Nss mod (62); - the SS has previously sent I+S frames numbered N(S)=0,...,Nss‑1 mod(62) and has previously sent a frame containing N(R) = Nms mod (62). The first I+S frame that an MS will send in a test will be numbered N(S)= Nms and the first I+S frame that the SS will send will be numbered Nss.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2 MS sends I+S frames
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.1 N(S) sequence number
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.1.1 Test purpose
To test the correct handling of the N(S) sequence number.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.1.2 Method of test
Initial Conditions System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use RLP default parameters except the window size from MS to IWF (SS), called Kmi. A non transparent data call will be established, so that the MS is in call state U10 ("Call Active"). Since some RLP parameters are different from the default parameters, a negotiation procedure will be initiated by the MS after the CONNECKT ACKNOWLEDGE message. The MS may negotiate the RLP default parameters within allowed ranges, defined in 3GPP TS 04.22, except the window size from MS to IWF (SS), called Kmi, which has to be a non default value. The SS shall accept and use the new RLP parameters till the end of the test. After the negotiation procedure the ABM will be entered. This test is performed twice with 2 different values of Kmi, randomly chosen. Procedure After optional status bits exchange between the MS and the SS, the MS is made to send continuously I+S frames (more than 2*64 frames). The MS shall send I+S frames with N(S) incremented by 1 mod(62) in each frame. The SS acknowledges the I+S frames in RR frame in sequence. The MS is returned to the idle state by clearing the call. Expected sequence MS SS 0 I+S > < RR 0' ... etc... ... i I+S > < RR i' The frames from the SS will be: 0',...,i': One supervisory RR frame containing: N(R) = Nms+1, ... , Nms+i+1 mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.1.3 Test requirements
The frames from the MS shall be: 0,...,i: One I+S frame containing: N(S) = Nms, ... , Nms+i mod(62)
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.2 Transmission window
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.2.1 Test purpose
To test the correct handling of the transmission window.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.2.2 Method of test
Initial Conditions System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use RLP default parameters except the window size from MS to IWF (SS), called Kmi. A non transparent data call will be established, so that the MS is in call state U10 ("Call Active"). Since some RLP parameters are different from the default parameters, a negotiation procedure will be initiated by the MS after the CONNECKT ACKNOWLEDGE message. The MS may negotiate the RLP default parameters within allowed ranges, defined in 3GPP TS 04.22, except the window size from MS to IWF (SS), called Kmi, which has to be a non default value. The SS shall accept and use the new RLP parameters till the end of the test. After the negotiation procedure the ABM will be entered. This test is performed twice with 2 different values of Kmi, randomly chosen. Procedure The MS is made to send continuously I+S frames with a delay inferior to T1 between each frame. The SS does not acknowledge the first Kmi frames. The MS stops sending I+S frames after having sent Kmi frames, due to the window size. The SS waits for 0,5*T1 after the last frame of the sequence (N(S)=Nms+Kmi‑1) to acknowledge the first j frames, with j<Kmi. The MS shall transmit j new I+S frames and stop sending I+S frames after having sent them, due to the window size. The SS waits for 0,5*T1 after the last frame of the sequence (N(S)=Nms+Kmi‑1+j mod (62)) to acknowledge all frames transmitted by the MS. The MS shall transmit all the following I+S frames. The SS acknowledges the I+S frames sequentially (i.e. 1 after 1). The MS is returned to the idle state by clearing the call. Expected sequence MS SS 0 I+S > < RR 0' ... etc... ... Kmi‑1 I+S > < RR Kmi‑1' Stops sending I+S frames Kmi S > < RR Kmi' ... etc... ... i‑1 S > < RR i‑1' i S > After 0,5*T1 < RR i' i+1 I+S > < RR i+1' ... etc... ... i+j I+S > < RR i+j' Stops sending I+S frames i+j+1 S > < RR i+j+1' ... etc... ... n‑1 S > < RR n‑1' n S > After 0,5*T1 < RR n' n+1 I+S > < RR n+1' ... etc... ... The frames from the SS will be: 0',...,i‑1': One RR frame containing: N(R)=Nms mod(62). i': One RR frame containing: N(R)=Nms+j mod(62) with j <Kmi, after a delay of 0,5*T1 after the last received I+S frame. i+1',...,n‑1': One RR frame containing: N(R)=Nms+j mod(62). n': One RR frame containing: N(R)=Nms+Kmi+j mod(62), after a delay of 0,5*T1 after the last received I+S frame. n+1', n+2',...: One RR frame containing: N(R) = Nms + Kmi + j + 1 , Nms + Kmi + j + 2 ,... mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.2.3 Test requirements
The frames from the MS shall be: 0,...,Kmi‑1: One I+S frame containing: N(S) = Nms, ..., Nms + Kmi - 1 mod(62). MS stops sending I+S frames until reception of an acknowledgement of at least one I+S frame. Kmi,...,i: One S frame. i+1,...,i+j: One I+S frame containing: N(S)=Nms+Kmi,...,Nms+Kmi+j‑1 mod(62). MS stops sending I+S frames until reception of an acknowledgement of at least one I+S frame. i+j+1,...,n: One S frame. n+1,n+2...: One I+S frame containing: N(S)=Nms+Kmi+j,Nms+Kmi+j+1,... mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.3 Busy condition
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.3.1 Test purpose
To test the correct handling of a RNR frame received.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.3.2 Method of test
Initial Conditions System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use default RLP parameters. A non transparent data call will be established, so that the MS is in call state U10 ("Call Active"). Case a: No negotiation will be initiated by the MS. Case b: The MS initiates negotiation of RLP default parameters. NOTE: The MS is allowed to initiate the negotiation of the RLP default parameters, within allowed ranges, defined in 3GPP TS 04.22. The MS shall do this in the ADM, after having sent a CONNECT ACKNOWLEDGE message (MO-case) or after having received a CONNECT ACKNOWLEDGE message from the SS (MT-case). The SS shall accept and use the new RLP parameters till the end of the test. The ABM will be entered. Procedure The MS is made to send continuously I+S frames. The SS acknowledges the received I+S frames in supervisory RR frames. After 1 second it acknowledged the received I+S frames in supervisory RNR frames. After the first RNR frame, the MS shall stop sending I+S frames and shall start sending supervisory frames within T2. After 1 second receiving supervisory frames, the SS sends RR frames instead of RNR. After the first RR frame, the MS will restart the transmission of I+S frames within T2. The MS is returned to the idle state by clearing the call. Expected sequence MS SS 0 I+S > < RR 0' ... etc... ... i‑1 I+S > < RR i‑1' i I+S > < RNR i' stops sending I+S frames within T2 i+1 S > < RNR i+1' ... etc... ... n+i‑1 S > < RNR n+i‑1' n+i S > < RR n+i' restarts sending I+S frames within T2 n+i+1 I+S > < RR n+i+1' ... etc... ... The frames from the SS will be: 0',...,i‑1': One RR frame containing: N(R)=Nms+1,...,Nms+i mod(62). i',...,n+i‑1': One RNR frame containing: N(R)=Nms+i+1 mod(62). n+i': One RR frame containing: N(R)=Nms+i+1 mod(62). n+i+1',n+i+2',...: One RR frame containing: N(R)=Nms+i+2,Nms+i+3,... mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.2.3.3 Test requirements
The frames from the MS shall be: 0,...,i: One I+S frame containing: N(S)=Nms,...,Nms+i mod(62). MS stops sending I+S frames within T2 after the reception of the first RNR frame from the SS. i+1,...,n+i: One S frame. MS restarts sending I+S frames within T2 after the reception of the first RR frame from the SS. n+i+1,n+i+2,...: One I+S frame containing: N(S)=Nms+i+1,Nms+i+2,... mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.3 SS sends I+S frames
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.3.1 N(R) sequence number
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.3.1.1 Test purpose
To test the correct handling of the N(R) sequence number.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.3.1.2 Method of test
Initial Conditions System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use RLP default parameters except the window size from IWF (SS) to MS, called KIM. A non transparent data call will be established, so that the MS is in call state U10 ("Call Active"). Since some RLP parameters are different from the default parameters, a negotiation procedure will be initiated by the MS after the CONNECKT ACKNOWLEDGE message. The MS may negotiate the RLP default parameters within allowed ranges, defined in 3GPP TS 04.22, except the window size from IWF (SS) to MS, called KIM, which has to be a non default value. The SS shall accept and use the new RLP parameters till the end of the test. After the negotiation procedure the ABM will be entered. This test is performed twice with 2 different values of KIM, randomly chosen. Procedure The SS is made to send continuously I+S frames (more than 2*64 frames). The delay between two I+S frames shall be superior to T2 and inferior to T1. The MS is made to send no data i.e. no I+S frame. NOTE: The MS may have previously sent I+S frames. The SS sends I+S frames in I+S RR frames. The MS shall acknowledge the I+S frames in RR frame sequentially within T2. The MS is returned to the idle state by clearing the call. Expected sequence MS SS < I+S 0' Within T2 0 S > ... etc... ... < I+S i' Within T2 i S > The frames from the SS will be: 0,...,i': One I+S frame containing N(S)=Nss,...,Nss+i mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.3.1.3 Test requirements
The frames from the MS shall be: 0,...,i: One S frame containing: N(R)=Nss+1,...,Nss+i+1 mod (62). The MS shall acknowledge the I+S frames sent by the SS within T2. NOTE: If T2 parameter is equal to default T2 (<80 ms), the SS has to checked that the MS acknowledges an I+S frame within 80 ms.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.3.2 Busy condition
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.3.2.1 Test purpose
To test the correct handling of a RNR frame with information received.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.3.2.2 Method of test
Initial Conditions System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use default RLP parameters. A non transparent data call will be established, so that the MS is in call state U10 ("Call Active"). Case a: No negotiation will be initiated by the MS. Case b: The MS initiates negotiation of RLP default parameters. NOTE: The MS is allowed to initiate the negotiation of the RLP default parameters, within allowed ranges, defined in 3GPP TS 04.22. The MS shall do this in the ADM, after having sent a CONNECT ACKNOWLEDGE message (MO-case) or after having received a CONNECT ACKNOWLEDGE message from the SS (MT-case). The SS shall accept and use the new RLP parameters till the end of the test. The ABM will be entered. Procedure The SS is made to send continuously I+S frames. The delay between two consecutive I+S frames shall be inferior to T1. The MS is made to send continuously I+S frames with a delay inferior to T1 between each frame. The SS acknowledges the received I+S frames in I+S RR frames. After 1 second, it acknowledged the received I+S frames in supervisory RNR frames. The MS shall acknowledge the I+S frames in I+S RR frame sequentially. After the first RNR frame, the MS shall stop sending I+S frames and shall acknowledge the I+S received frame in supervisory frames within T2. After 1 second receiving supervisory frames, the SS sends I+S RR frames instead of RNR. After the first RR frame, the MS will restart the transmission of I+S frames, it shall acknowledge the I+S received frame in I+S frame within T2. The MS is returned to the idle state by clearing the call. Expected sequence MS SS 0 I+S > < RR(I+S) 0' ... etc... ... i‑1 I+S > < RR(I+S) i‑1' i I+S > < RNR(I+S) i' stops sending I+S frames within T2 i+1 S > < RNR(I+S) i+1' ... etc... ... n+i‑1 S > < RNR(I+S) n+i‑1' n+i S > < RR(I+S) n+i' restarts sending I+S frames within T2 n+i+1 I+S > < RR(I+S) n+i+1' ... etc... ... The frames from the SS will be: 0',...,i‑1': One I+S RR frame containing: N(S)=Nss,...,Nss+i‑1 mod(62), N(R)=Nms+1,...,Nms+i mod(62). i',...,n+i‑1': One I+S RNR frame containing: N(S)=Nss+i,...,Nss+n+i‑1 mod(62), N(R)=Nms+i+1 mod(62). n+i',n+i+1',...: One I+S RR frame containing: N(S)=Nss+n+i,Nss+n+i+1,... mod(62), N(R)=Nms+i+1,Nms+i+2,... mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.3.2.3 Test requirements
The frames from the MS shall be: 0,...,i: One I+S frame containing: N(S)=Nms,...,Nms+i mod(62), N(R)=Nss,...,Nss+i mod(62). MS stops sending I+S frames within T2 after the reception of the first RNR frame from the SS. i+1,...,n+i: One S frame containing: N(R)=Nss+i+1,...,Nss+n+i mod(62). MS restarts sending I+S frames within T2 after the reception of the first RR frame from the SS. n+i+1,n+i+2,...: One I+S frame containing: N(S)=Nms+i+1,Nms+i+2,... mod(62), N(R)=Nss+n+i+1,Nss+n+i+1... mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4 SS rejects I+S frames
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.1 REJ frame
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.1.1 Test purpose
To test the correct handling of a REJ frame received.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.1.2 Method of test
Initial Conditions The window size from MS to IWF (SS) is called Kmi. System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use default RLP parameters. A non transparent data call will be established, so that the MS is in call state U10 ("Call Active"). Case a: No negotiation will be initiated by the MS. Case b: The MS initiates negotiation of RLP default parameters. NOTE: The MS is allowed to initiate the negotiation of the RLP default parameters, within allowed ranges, defined in 3GPP TS 04.22. The MS shall do this in the ADM, after having sent a CONNECT ACKNOWLEDGE message (MO-case) or after having received a CONNECT ACKNOWLEDGE message from the SS (MT-case). The SS shall accept and use the new RLP parameters till the end of the test. The ABM will be entered. Procedure The MS is made to send continuously I+S frames with a delay inferior to T1 between each frame. The SS acknowledges the i first I+S frames in supervisory RR frames. The SS does not acknowledge the following I+S frames. The SS rejects the 2 last I+S frames with a REJ and then send UI frames. The MS shall retransmit the rejected I+S frames and the continue to send I+S frames. The MS shall stop sending I+S frame when the transmission window is full. The SS acknowledges all the received I+S frames with a RR frame after a delay of 0,5*T1 after the last received I+S frame. The MS restarts sending I+S frame. The SS acknowledges the received I+S frames. The MS is returned to the idle state by clearing of the call. Expected sequence MS SS 0 I+S > < RR 0' ... etc... ... i‑1 I+S > < RR i‑1' i I+S > < RR i' i+1 I+S > < RR i+1' i+2 I+S > < RR i+2' i+3 I+S > < REJ i+3' i+4 I+S > < UI i+4' i+5 I+S > < UI i+5' i+6 I+S > < UI i+6' ... etc... ... i+3+Kmi I+S > < UI i+3+Kmi' Stops sending I+S frames i+4+Kmi S > < UI i+4+Kmi' ... etc... ... n‑1 S > < UI n‑1' n S > After 0,5*T1 < RR n' n+1 I+S > < RR n+1' ... etc... ... The frames from the SS will be: 0',...,i‑1': One RR frame containing: N(R)=Nms+1,...,Nms+i mod(62). i',...,i+2': One RR frame containing: N(R)=Nms+i mod(62). i+3': One REJ frame containing: N(R)=Nms+i+2 mod(62). i+4',...,n‑1': One UI frame. n': One RR frame containing: N(R)=Nms+i+2+Kmi mod(62), after a delay of 0,5*T1 after the last received I+S frame. n+1',...: One RR frame containing N(R)=Nms+i+3+Kmi,... mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.1.3 Test requirements
The frames from the MS shall be: 0,...,i+3: One I+S frame containing N(S)=Nms,...,Nms+i+3 mod(62). i+4,i+5: One I+S frame containing N(S)=Nms+i+2,Nms+i+3 mod(62). i+6,...,i+3+Kmi: One I+S frame containing: N(S)=Nms+i+4...,Nms+i+Kmi+1 mod(62). i+4+Kmi,...,n: One S frame. MS stops sending I+S frames until reception of an acknowledging of at least 1 I+S frame of the window (received N(R) from Nms+i+3 to Nms+i+2+Kmi mod(62)). n+1,...: One I+S frame containing: N(S)=Nms+i+Kmi,... mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.2 SREJ frame
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.2.1 Test purpose
To test the correct handling of a SREJ frame received.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.2.2 Method of test
Initial Conditions The window size from MS to IWF (SS) is called Kmi. System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use default RLP parameters. A non transparent data call will be established, so that the MS is in call state U10 ("Call Active"). Case a: No negotiation will be initiated by the MS. Case b: The MS initiates negotiation of RLP default parameters. NOTE: The MS is allowed to initiate the negotiation of the RLP default parameters, within allowed ranges, defined in 3GPP TS 04.22. The MS shall do this in the ADM, after having sent a CONNECT ACKNOWLEDGE message (MO-case) or after having received a CONNECT ACKNOWLEDGE message from the SS (MT-case). The SS shall accept and use the new RLP parameters till the end of the test. The ABM will be entered. Procedure The MS is made to send continuously I+S frames with a delay inferior to T1 between each frame. The SS acknowledges the i first I+S frames in supervisory RR frames. The SS does not acknowledge the following I+S frames. The SS rejects one I+S frame with a SREJ and then send UI frames. The MS shall retransmit the rejected I+S frame and the continue to send I+S frames. The MS shall stop sending I+S frame when the transmission window is full. The SS acknowledges all the received I+S frames with a RR frame after a delay of 0,5*T1 after the last received I+S frame. The MS restarts sending I+S frame. The SS acknowledges the received I+S frames. The MS is returned to the idle state by clearing of the call. Expected sequence MS SS 0 I+S > < RR 0' ... etc... ... i‑1 I+S > < RR i‑1' i I+S > < RR i' i+1 I+S > < RR i+1' i+2 I+S > < RR i+2' i+3 I+S > < SREJ i+3' i+4 I+S > < UI i+4' i+5 I+S > < UI i+5' ... etc... ... i+Kmi I+S > < UI i+Kmi' Stops sending I+S frames i+1+Kmi S > < UI i+1+Kmi' ... etc... ... n‑1 S > < UI n‑1' n S > After 0,5*T1 < RR n' n+1 I+S > < RR n+1' ... etc... ... The frames from the SS will be: 0',...,i‑1': One RR frame containing: N(R)=Nms+1,...,Nms+i mod(62). i',...,i+2': One RR frame containing: N(R)=Nms+i mod(62). i+3': One SREJ frame containing: N(R)=Nms+i+2 mod(62). i+4',...,n‑1': One UI frame. n': One RR frame containing: N(R)=Nms+i+Kmi mod(62), after a delay of 0,5*T1 after the last received I+S frame. n+1',...: One RR frame containing: N(R)=Nms+i+1+Kmi mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.2.3 Test requirements
The frames from the MS shall be: 0,...,i+3: One I+S frame containing: N(S)=Nms,...,Nms+i+3 mod(62). i+4: One I+S frame containing: N(S)=Nms+i+2 mod(62). i+5,...,i+Kmi: One I+S frame containing: N(S)=Nms+i+4...,Nms+i+Kmi‑1 mod(62). i+1+Kmi,...,n: One S frame. MS stops sending I+S frames until reception of an acknowledging of at least 1 I+S frame of the window (received N(R) from Nms+i+1 to Nms+i+Kmi mod(62)). n+1,...: One I+S frame containing: N(S)=Nms+i+Kmi,... mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.3 I+S reject frame
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.3.1 Test purpose
To test the correct handling of a I+S reject frame received.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.3.2 Method of test
Initial Conditions The window size from MS to IWF (SS) is called Kmi. System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use default RLP parameters. A non transparent data call will be established, so that the MS is in call state U10 ("Call Active"). Case a: No negotiation will be initiated by the MS. Case b: The MS initiates negotiation of RLP default parameters. NOTE: The MS is allowed to initiate the negotiation of the RLP default parameters, within allowed ranges, defined in 3GPP TS 04.22. The MS shall do this in the ADM, after having sent a CONNECT ACKNOWLEDGE message (MO-case) or after having received a CONNECT ACKNOWLEDGE message from the SS (MT-case). The SS shall accept and use the new RLP parameters till the end of the test. The ABM will be entered. Procedure The MS is made to send continuously I+S frames with a delay inferior to T1 between each frame. The SS acknowledges the i first I+S frames in supervisory RR frames. The SS does not acknowledge the following I+S frames. The SS rejects the 2 last I+S frames with a REJ. The MS shall retransmit the 2 rejected I+S frames. The SS acknowledges these 2 frames. The MS shall continue sending I+S frames. The SS does not acknowledge these frames. The SS rejects one I+S frame with a SREJ. The MS shall retransmit the rejected I+S frame and continue sending I+S frames. The SS acknowledges the received I+S frames. The MS is returned to the idle state by clearing of the call. Expected sequence MS SS 0 I+S > < RR 0' ... etc... ... i‑1 I+S > < RR i‑1' i I+S > < RR i' i+1 I+S > < RR i+1' i+2 I+S > < REJ(I+S) i+2' i+3 I+S > < RR i+3' i+4 I+S > < RR i+4' i+5 I+S > < RR i+5' i+6 I+S > < SREJ(I+S) i+6' i+7 I+S > < RR i+7' i+8 I+S > < RR i+8' ... etc... ... The frames from the SS will be: 0',...,i‑1': One RR frame containing: N(R)=Nms+1,...,Nms+i mod(62). i',i+1': One RR frame containing: N(R)=Nms+i mod(62). i+2': One I+S REJ frame containing: N(R)=Nms+i+1 mod(62), N(S)=Nss mod (62). i+3',i+4': One RR frame containing: N(R)=Nms+i+2,Nms+i+3 mod(62). i+5': One RR frame containing: N(R)=Nms+i+3 mod(62). i+6': One I+S REJ frame containing: N(R)=Nms+i+3 mod(62), N(S)=Nss+1 mod (62). i+7': One RR frame containing: N(R)=Nms+i+3 mod(62). i+8': One RR frame containing: N(R)=Nms+i+6,... mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.4.3.3 Test requirements
The frames from the MS shall be: 0,...,i+2: One I+S frame containing: N(S)=Nms,...,Nms+i+2 mod(62). i+3,i+4: One I+S frame containing: N(S)=Nms+i+1,Nms+i+2 mod(62). i+5,i+6: One I+S frame containing: N(S)=Nms+i+3,Nms+i+4 mod(62). i+7: One I+S frame containing: N(S)=Nms+i+3 mod(62). i+8,...: One I+S frame containing: N(S)=Nms+i+5,... mod(62). The MS shall acknowledge the I+S frames sent by the SS within T2.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5 MS rejects I+S frames
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.1 Rejection with REJ or SREJ supervisory frames
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.1.1 Conformance requirements
The MS shall be able to detect that an I+S frame is out of sequence, and to indicate to the network that some information needs to be retransmitted. This shall be done by using either a REJ or a SREJ RLP frame. The MS has the freedom to choose either one of these frames, but it shall correctly indicate which frames need to be retransmitted. References 3GPP TS 04.22 subclauses 5.2.3.4, 5.2.3.6 and 5.3.2.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.1.2 Test purpose
To test that the MS is able to send correct REJ or SREJ supervisory frames to ask for the transmission of a sequence when an out of sequence information frame has been received.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.1.3 Test method
Initial Conditions The window size from IWF (SS) to MS is called KIM. System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use default RLP parameters. A non transparent data call will be established, so that the MS is in call state U10 ("Call Active"). Case a: No negotiation will be initiated by the MS. Case b: The MS initiates negotiation of RLP default parameters. NOTE: The MS is allowed to initiate the negotiation of the RLP default parameters, within allowed ranges, defined in 3GPP TS 04.22. The MS shall do this in the ADM, after having sent a CONNECT ACKNOWLEDGE message (MO-case) or after having received a CONNECT ACKNOWLEDGE message from the SS (MT-case). The SS shall accept and use the new RLP parameters till the end of the test. The ABM will be entered. Specific PICS statements: - PIXIT statements: • Bearer services supported • Characteristics of non-transparent services. Foreseen final state of the MS Idle. Test procedure The SS is made to send continuously I+S frames. The delay between two consecutive I+S frames shall be inferior to T1. The MS is made to send no user data. It sends only supervisory frames. The SS sends a I+S frame numbered NSS. The MS shall acknowledge this frame. Then the SS sends a I+S frame numbered NSS+2. The MS shall ask for the retransmission of the missing frame numbered NSS+1. The MS may send a SREJ frame (see case a). If it cannot send SREJ, it shall send a REJ frame (see case b). Case a: If the MS chooses to send a SREJ, it shall send a SREJ frame containing N(R)=NSS+1. The SS sends a I+S frame numbered NSS+4. The MS shall ask for the retransmission of the missing frame numbered NSS+3 The MS may send a SREJ frame (see case a/a If it cannot send SREJ, it shall send a REJ frame (see case a/b). Case a/a: If the MS chooses to send a SREJ, it shall send a SREJ frame containing N(R)=NSS+3. The SS sends a I+S frame numbered NSS+1 and the MS shall acknowledge this frame (N(R)=NSS+3). The SS sends a I+S frame numbered NSS+3 and the MS shall acknowledge this frame (N(R)=NSS+5). Case a/b: If the MS chooses to send a REJ, it shall send a REJ frame containing N(R)=NSS+1. The SS sends I+S frames numbered NSS+1, ..., NSS+4 and the MS shall acknowledge these frames (N(R)=NSS+2, ... , NSS+5). Case b: If the MS chooses to send a REJ, it shall send a REJ frame containing N(R)=NSS+1. The SS sends I+S frames numbered NSS+1, NSS+2 and the MS shall acknowledge this frame (N(R)=NSS+2, NSS+3). The SS sends a I+S frame numbered NSS+4. The MS shall ask for the retransmission of the missing frame numbered NSS+3 The MS may send a SREJ frame (see case b/a If it cannot send SREJ, it shall send a REJ frame (see case b/b). Case b/a: If the MS chooses to send a SREJ, it shall send a SREJ frame containing N(R)=NSS+3. The SS sends a I+S frame numbered NSS+3 and the MS shall acknowledge this frame (N(R)=NSS+5). Case b/b: If the MS chooses to send a REJ, it shall send a REJ frame containing N(R)=NSS+3. The SS sends I+S frames numbered NSS+3, NSS+4 and the MS shall acknowledge these frames (N(R)=NSS+4, NSS+5). The SS sends a I+S frame numbered NSS+5. The MS shall acknowledge this frame. Then the SS sends a I+S frame numbered NSS+5+KIM. The MS shall ask for the retransmission of the missing frame numbered NSS+6 to NSS+4+KIM. The MS may send a SREJ frame (see sequence c with k=1). If it cannot send SREJ, it shall send a REJ frame (see sequence d with k=1). Sequence c: If the MS chooses to send a SREJ, it shall send a SREJ frame containing N(R)=NSS+5+k. The SS sends a I+S frame numbered NSS+5+k. When using SREJ frames, the MS shall send RR frames to acknowledge the received I+S frames. The time when these RR frames are sent is not tested. If k<KIM‑1, the MS shall ask for the retransmission of the missing frames numbered NSS+5+k+1 to NSS+4+KIM. The MS may send a SREJ frame (see sequence c with k=k+1). If it cannot send SREJ, it shall send a REJ frame (see sequence d with k=k+1). If k=KIM‑1, the MS has no more frame to reject. It shall acknowledge the frame numbered NSS+5+KIM. with a frame containing N(R)=NSS+6+KIM.,. The SS sends I+S frames numbered NSS+6+KIM, etc... and the MS shall acknowledge these frames (N(R)=NSS+7+KIM, etc. Sequence d: If the MS chooses to send a REJ, it shall send a REJ frame containing N(R)=NSS+5+k. The SS sends a I+S frame numbered NSS+5+k and the MS shall acknowledge this frame (N(R)=NSS+5+k+1). The SS sends a I+S frame numbered NSS+5+KIM. If k<KIM‑1, the MS shall ask for the retransmission of the missing frames numbered NSS+5+k+1 to NSS+4+KIM. The MS may send a SREJ frame (see sequence c with k=k+1). If it cannot send SREJ, it shall send a REJ frame (see sequence d with k=k+1). If k=KIM‑1, the MS has no more frame to reject. It shall acknowledge the frame numbered NSS+5+KIM. with a frame containing N(R)=NSS+6+KIM.,. The SS sends I+S frames numbered NSS+6+KIM, etc... and the MS shall acknowledge these frames (N(R)=NSS+7+KIM, etc. The MS is returned to the idle state by clearing of the call. Maximum duration of test 1 minute. Expected sequence MS SS <------ I+S ------- 0' 0 ------- RR ------> <------ I+S ------- 1' 1 SREJ(a) or REJ(b) ? Case a a - 1 ------- SREJ ------> <------ I+S ------- a - 2' a - 2 SREJ(a/a) or REJ(a/b) ? Case a/a a/a - 1 ------- SREJ ------> <------ I+S ------- a/a - 2' a/a - 2 ------- RR ------> <------ I+S ------- a/a - 3' a/a - 3 ------- RR ------> Case a/b a/b - 1 ------- REJ ------> <------ I+S ------- a/b - 2' a/b - 2 ------- RR ------> <------ I+S ------- a/b - 3' a/b - 3 ------- RR ------> <------ I+S ------- a/b - 4' a/b - 4 ------- RR ------> <------ I+S ------- a/b - 5' a/b - 5 ------- RR ------> Case b b - 1 ------- REJ ------> <------ I+S ------- b - 2' b - 2 ------- RR ------> <------ I+S ------- b - 3' b - 3 ------- RR ------> <------ I+S ------- b - 4' b - 4 SREJ(b/a) or REJ(b/b) ? Case b/a b/a - 1 ------- SREJ ------> <------ I+S ------- b/a - 2' b/a - 2 ------- RR ------> Case b/b b/b - 1 ------- REJ ------> <------ I+S ------- b/b - 2' b/b - 2 ------- RR ------> <------ I+S ------- b/b - 3' b/b - 3 ------- RR ------> <------ I+S ------- i' i ------- RR ------> <------ I+S ------- i+1' i+1 SREJ(c) or REJ(d) ? Sequence c (SREJ used) c/k - 0 ------- SREJ ------> <------ I+S ------- c/k - 0' c/k - 1 SREJ(c) or REJ(d) ? Sequence d (REJ used) d/k - 0 ------- REJ ------> <------ I+S ------- d/k - 0' d/k - 1 ------- RR ------> <------ I+S ------- d/k - 1' d/k - 2 SREJ(c) or REJ(d) ? j ------- RR ------> <------ I+S ------- j' ... etc... ... The frames from the SS will be: 0': One I+S frame containing N(S)=NSS mod(62), N(R)=NMS+1 mod(62). 1': One I+S frame containing N(S)=NSS+2 mod(62), N(R)=NMS+1 mod(62). Case a: a - 2': One I+S frame containing N(S)=NSS+4 mod(62), N(R)=NMS+1 mod(62). Case a/a: a/a - 2': One I+S frame containing N(S)=NSS+1 mod(62), N(R)=NMS+1 mod(62). a/a - 3': One I+S frame containing N(S)=NSS+3 mod(62), N(R)=NMS+1 mod(62). Case a/b: a/b - 2': One I+S frame containing N(S)=NSS+1 mod(62), N(R)=NMS+1 mod(62). a/b - 3': One I+S frame containing N(S)=NSS+2 mod(62), N(R)=NMS+1 mod(62). a/b - 4': One I+S frame containing N(S)=NSS+3 mod(62), N(R)=NMS+1 mod(62). a/b - 5': One I+S frame containing N(S)=NSS+4 mod(62), N(R)=NMS+1 mod(62). Case b: b - 2': One I+S frame containing N(S)=NSS+1 mod(62), N(R)=NMS+1 mod(62). b - 3': One I+S frame containing N(S)=NSS+2 mod(62), N(R)=NMS+1 mod(62). b - 4': One I+S frame containing N(S)=NSS+4 mod(62), N(R)=NMS+1 mod(62). Case b/a: b/a - 2': One I+S frame containing N(S)=NSS+3 mod(62), N(R)=NMS+1 mod(62). Case b/b: b/b - 2': One I+S frame containing N(S)=NSS+3 mod(62), N(R)=NMS+1 mod(62). b/b - 3': One I+S frame containing N(S)=NSS+4 mod(62), N(R)=NMS+1 mod(62). i': One I+S frame containing N(S)=NSS+5 mod(62), N(R)=NMS+1 mod(62). i+1': One I+S frame containing N(S)=NSS+5+KIM mod(62), N(R)=NMS+1 mod(62). Sequence c (with k=1 to KIM‑1): c/k - 0': One I+S frame containing N(S)=NSS+5+k mod(62), N(R)=NMS+1 mod(62). Sequence d (with k=1 to KIM‑1): d/k - 0': One I+S frame containing N(S)=NSS+5+k mod(62), N(R)=NMS+1 mod(62). d/k - 1': One I+S frame containing N(S)=NSS+5+KIM mod(62), N(R)=NMS+1 mod(62). j',...: One I+S frame containing N(S)=NSS+KIM+6,... mod(62), N(R)=NMS+1 mod(62). Specific message content The frames from the MS shall be: 0: One RR frame containing N(R)=NSS+1 mod(62). 1: The MS shall reject the missing I+S frame numbered NSS+1. It may send a SREJ frame (see case a). If it cannot send SREJ, it shall send a REJ frame (see case b). Case a a - 1: One supervisory SREJ frame containing N(R)=NSS+1 mod(62). a - 2: The MS shall reject the missing I+S frame numbered NSS+3. It may send a SREJ frame (see case a). If it cannot send SREJ, it shall send a REJ frame (see case b). Case a/a a/a - 1: One supervisory SREJ frame containing N(R)=NSS+3 mod(62). a/a - 2: One RR frame containing N(R)=NSS+3 mod(62). a/a - 3: One RR frame containing N(R)=NSS+5 mod(62). Case a/b a/b - 1: One supervisory REJ frame containing N(R)=NSS+1 mod(62). a/b - 2: One RR frame containing N(R)=NSS+2 mod(62). a/b - 3: One RR frame containing N(R)=NSS+3 mod(62). a/b - 4: One RR frame containing N(R)=NSS+4 mod(62). a/b - 5: One RR frame containing N(R)=NSS+5 mod(62). Case b b - 1: One supervisory REJ frame containing N(R)=NSS+1 mod(62). b - 2: One RR frame containing N(R)=NSS+2 mod(62). b - 3: One RR frame containing N(R)=NSS+3 mod(62). b - 4: The MS shall reject the missing I+S frame numbered NSS+2. It may send a SREJ frame (see case a). If it cannot send SREJ, it shall send a REJ frame (see case b). Case b/a b/a - 1: One supervisory SREJ frame containing N(R)=NSS+2 mod(62). b/a - 2: One RR frame containing N(R)=NSS+5 mod(62). Case b/b b/b - 1: One supervisory REJ frame containing N(R)=NSS+2 mod(62). b/b - 2: One RR frame containing N(R)=NSS+4 mod(62). b/b - 3: One RR frame containing N(R)=NSS+5 mod(62). i: One RR frame containing N(R)=NSS+6 mod(62). i+1: The MS shall reject all missing I+S frames (i.e. KIM‑1 frames). It may send a SREJ frame (see sequence c with k=1). If it cannot send SREJ, it shall send a REJ frame (see sequence d with k=1). Sequence c (with k=1 to KIM‑1): c/k - 0: One SREJ frame containing N(R)=NSS+5+k mod(62). c/k - 1: If k<KIM‑1, the MS shall reject all missing I+S frames (i.e. KIM‑1 frames). It may send a SREJ frame (see sequence c with k=k+1). If it cannot send SREJ, it shall send a REJ frame (see sequence d with k=k+1). If k=KIM‑1, the MS has no more frame to reject (see frame numbered j). Sequence d (with k=1 to KIM‑1): d/k - 0: One REJ frame containing N(R)=NSS+5+k mod(62). d/k - 1: One RR frame containing N(R)=NSS+5+k+1 mod(62). d/k - 2: If k<KIM‑1, the MS shall reject all missing I+S frames (i.e. KIM‑1 frames). It may send a SREJ frame (see sequence c with k=k+1). If it cannot send SREJ, it shall send a REJ frame (see sequence d with k=k+1). If k=KIM‑1, the MS has no more frame to reject (see frame numbered j). j,...: One RR frame containing N(R)=NSS+KIM+6,... mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.2 Retransmission of REJ or SREJ frames
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.2.1 Conformance requirements
The MS shall not retransmit a REJ frame upon time-out. It may repeat SREJ frames. References 3GPP TS 04.22 subclauses 5.2.3.4 and 5.2.3.6.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.2.2 Test purpose
To test that the MS is able to retransmit a SREJ supervisory frames, and does not retransmit a REJ frame.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.2.3 Test method
Initial Conditions The window size from IWF (SS) to MS is called KIM. System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use default RLP parameters. A non transparent data call will be established, so that the MS is in call state U10 ("Call Active"). Case a: No negotiation will be initiated by the MS. Case b: The MS initiates negotiation of RLP default parameters. NOTE: The MS is allowed to initiate the negotiation of the RLP default parameters, within allowed ranges, defined in 3GPP TS 04.22. The MS shall do this in the ADM, after having sent a CONNECT ACKNOWLEDGE message (MO-case) or after having received a CONNECT ACKNOWLEDGE message from the SS (MT-case). The SS shall accept and use the new RLP parameters till the end of the test. The ABM will be entered. Specific PICS statements: - PIXIT statements: • Bearer services supported • Characteristics of non-transparent services. Foreseen final state of the MS Idle. Test procedure After optional status bits exchange between the MS and the SS, the SS is made to send continuously I+S frames. The delay between two consecutive I+S frames shall be inferior to T1. The MS is made to send no user data. It sends only supervisory frames. The SS sends a I+S frame numbered NSS. The MS shall acknowledge this frame. Then the SS sends a I+S frame numbered NSS+2. The MS shall ask for the retransmission of the missing frame numbered NSS+1. The MS may send a SREJ frame (see case a). If it cannot send SREJ, it shall send a REJ frame (see case b). Case a: If the MS chooses to send a SREJ, it shall send a SREJ frame containing N(R)=NSS+1. The SS does not retransmit the rejected frame. The MS may repeat (see case a1) or not (see case a2) the reject SREJ frame. Case a1: If the MS chooses to retransmit the SREJ, it shall send a SREJ frame containing N(R)=NSS+1, at the expiry of T1. The SS sends a I+S frame numbered NSS+1 and the MS shall acknowledge this frame (N(R)=NSS+3). The SS sends a I+S frame numbered NSS+4. The MS shall ask for the retransmission of the missing frame numbered NSS+3. The MS shall send a SREJ frame containing N(R)=NSS+3. At expiry of T1, the MS shall send a new SREJ frame containing N(R)=NSS+3. This step is repeated N2 times. The SS checks for 2*T1 that the SREJ frame is not repeated by the MS. Case a2: If the MS chooses not to repeat the SREJ frame, The SS checks for 2*T1 that the SREJ frame is not repeated by the MS. Case b: If the MS chooses to send a REJ, it shall send a REJ frame containing N(R)=NSS+1. The SS does not retransmit the rejected frame. The MS shall not repeat the reject REJ frame. The SS checks for 2*T1 that the SREJ frame is not repeated by the MS. The MS is returned to the idle state by clearing of the call. Maximum duration of test 1 minute. Expected sequence MS SS <------ I+S ------- 0' 0 ------- RR ------> <------ I+S ------- 1' 1 SREJ(a) or REJ(b) ? Case a a - 1 ------- SREJ ------> a - 2 SREJ repeated (a1) or not (a2) ? Case a1 T1 Time-out a1 - 1 ------- SREJ ------> <------ I+S ------- a1 - 1' a1 - 2 ------- RR ------> <------ I+S ------- a1 - 2' a1 - 3 ------- SREJ ------> T1 Time-out a1 - 4 ------- SREJ ------> ... etc... ... T1 Time-out a1 - 3+N2 ------- SREJ ------> T1 Time-out SREJ not repeated Case a2 T1 Time-out SREJ not repeated Case b b - 1 ------- REJ ------> T1 Time-out SREJ not repeated The frames from the SS will be: 0': One I+S frame containing N(S)=NSS mod(62), N(R)=NMS+1 mod(62). 1': One I+S frame containing N(S)=NSS+2 mod(62), N(R)=NMS+1 mod(62). Case a: Case a1: a1 - 1': One I+S frame containing N(S)=NSS+1 mod(62), N(R)=NMS+1 mod(62). a1 - 2': One I+S frame containing N(S)=NSS+4 mod(62), N(R)=NMS+1 mod(62). Specific message content The frames from the MS shall be: 0: One RR frame containing N(R)=NSS+1 mod(62). 1: The MS shall reject the missing I+S frame numbered NSS+1. It may send a SREJ frame (see case a). If it cannot send SREJ, it shall send a REJ frame (see case b). Case a a - 1: One supervisory SREJ frame containing N(R)=NSS+1 mod(62). a - 2: SREJ frame may be repeated, (see case a1) or not (see case a2). Case a1 a1 - 1: On T1 Time-out, one supervisory SREJ frame containing N(R)=NSS+1 mod(62). a1 - 2: One RR frame containing N(R)=NSS+3 mod(62). a1 - 3,...,b2 - 3+N2: On T1 Time-out, one supervisory SREJ frame containing N(R)=NSS+3 mod(62). Case b b - 1: One supervisory REJ frame containing N(R)=NSS+1 mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.3 I+S reject frame
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.3.1 Conformance requirements
The MS shall be able to use I+S frames to carry a REJ or SREJ frame when it detects that one or more numbered information frame is received out of sequence. References 3GPP TS 04.22 subclauses 5.2.3.4 and 5.2.3.6.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.3.2 Test purpose
To test the MS is able to send SREJ or REJ frames in I+S frames when an out of sequence information frame has been received.
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.5.3.3 Test method
Initial Conditions The window size from IWF (SS) to MS is called KIM. System Simulator: The SS is configured to use default RLP parameters. Mobile Station: The MS is configured to use default RLP parameters. A non transparent data call will be established, so that the MS is in call state U10 ("Call Active"). Case a: No negotiation will be initiated by the MS. Case b: The MS initiates negotiation of RLP default parameters. NOTE: The MS is allowed to initiate the negotiation of the RLP default parameters, within allowed ranges, defined in 3GPP TS 04.22. The MS shall do this in the ADM, after having sent a CONNECT ACKNOWLEDGE message (MO-case) or after having received a CONNECT ACKNOWLEDGE message from the SS (MT-case). The SS shall accept and use the new RLP parameters till the end of the test. The ABM will be entered. Specific PICS statements: - PIXIT statements: • Bearer services supported • Characteristics of non-transparent services. Foreseen final state of the MS Idle. Test procedure The SS is made to send continuously I+S frames. The delay between two consecutive I+S frames shall be inferior to T1. The SS acknowledges all the received I+S frames. The MS is made to send continuously I+S frames. The SS sends a I+S frame numbered NSS. The MS shall acknowledge this frame. Then the SS sends a I+S frame numbered NSS+2. The MS shall ask for the retransmission of the missing frame numbered NSS+1. The MS may send a SREJ frame (see case a). If it cannot send SREJ, it shall send a REJ frame (see case b). The MS has user data to transmit, it shall use an I+S frame (instead of supervisory frame) to reject the missing frame. Case a: If the MS chooses to send a SREJ, it shall send a I+S SREJ frame containing N(R)=NSS+1. The SS sends a I+S frame numbered NSS+1 and the MS acknowledges this frame (N(R)=NSS+3). The SS sends a I+S frame numbered NSS+3, etc... and the MS acknowledges these frames (N(R)=NSS+4, etc...). Case b: If the MS chooses to send a REJ, it shall send a I+S REJ frame containing N(R)=NSS+1. The SS sends I+S frames numbered NSS+1, NSS+2, etc... and the MS shall acknowledge this frame (N(R)=NSS+2, NSS+3, etc...). The MS is returned to the idle state by clearing of the call. Maximum duration of test 1 minute. Expected sequence MS SS <------ I+S ------- 0' 0 ------- I+S ------> <------ I+S ------- 1' 1 SREJ(a) or REJ(b) ? Case a a - 1 ------- SREJ(I+S) ------> <------ I+S ------- a - 2' a - 2 ------- I+S ------> <------ I+S ------- a - 3' a - 3 ------- I+S ------> Case b b - 1 ------- REJ (I+S) ------> <------ I+S ------- b - 2' b - 2 ------- I+S ------> <------ I+S ------- b - 3' b - 3 ------- I+S ------> ... etc... ... The frames from the SS will be: 0': One I+S frame containing N(S)=NSS mod(62), N(R)=NMS+1 mod(62). 1': One I+S frame containing N(S)=NSS+2 mod(62), N(R)=NMS+2 mod(62). Case a: a - 2': One I+S frame containing N(S)=NSS+1 mod(62), N(R)=NMS+3 mod(62). a - 3': One I+S frame containing N(S)=NSS+3 mod(62), N(R)=NMS+4 mod(62). Case b: b - 2': One I+S frame containing N(S)=NSS+1 mod(62), N(R)=NMS+3 mod(62). b - 3': One I+S frame containing N(S)=NSS+2 mod(62), N(R)=NMS+4 mod(62). Specific message content The frames from the MS shall be: 0: One I+S RR frame containing N(S)=NMS+1, N(R)=NSS+1 mod(62). 1: The MS shall reject the missing I+S frame numbered NSS+1. It may send a I+S SREJ frame (see case a). If it cannot send SREJ, it shall send a I+S REJ frame (see case b). Case a a - 1: One I+S SREJ frame containing N(S)=NMS+2, N(R)=NSS+1 mod(62). a - 2: One I+S RR frame containing N(S)=NMS+3, N(R)=NSS+3 mod(62). a - 3: One I+S RR frame containing N(S)=NMS+4, N(R)=NSS+4 mod(62). Case b b - 1: One I+S REJ frame containing N(S)=NMS+2, N(R)=NSS+1 mod(62). b - 2: One I+S RR frame containing N(S)=NMS+3, N(R)=NSS+2 mod(62). b - 3: One I+S RR frame containing N(S)=NMS+4, N(R)=NSS+3 mod(62).
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.6 Checkpoint recovery
683b5b8a98f7b1390ddd5516ea9247a2
51.010-1
29.3.2.6.1 SS in checkpoint recovery mode