Ranging

6.3.10.3 OFDMA-based ranging [Change subclause 6.3.10.3.2 as indicated:]

6.3.10.3.2 Periodic ranging and automatic adjustments

An SS that wishes to perform periodic ranging shall take the following steps:

The SS, shall choose randomly a Ranging Slot (with the use of a binary truncated exponent algorithm to avoid possible re-collisions) at the time to perform the ranging, then it chooses randomly a Periodic Ranging Code (from the Periodic Ranging domain) and sends it to the BS (as a CDMA code).

If the MS does not receive a response, the MS may send a new CDMA code at the next appropriate peri-odic Ranging transmission opportunity and adjust its power level up to PTX_IR_MAX (6.3.9.5.1).

The BS cannot tell which SS sent the CDMA ranging request; therefore, upon successfully receiving a CDMA Periodic Ranging Code, the BS broadcasts a Ranging Response message that advertises the received Periodic Ranging Code as well as the ranging slot (OFDMA symbol number, subchannel, etc.) where the CDMA Periodic Ranging code has been identified. This information is used by the SS that sent the CDMA Periodic ranging code to identify the Ranging Response message that corresponds to its ranging request. The Ranging Response message contains all the needed adjustment (e.g., time, power, and possibly frequency corrections) and a status notification.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65

[Insert new subclause 6.3.10.3.3:]

6.3.10.3.3 CDMA handover ranging and automatic adjustment

An MS that wishes to perform handover ranging shall take a process similar to that defined in the initial ranging section with the following modifications.

In CDMA handover ranging process, the CDMA handover ranging code is used instead of the initial ranging code. The code is selected from the handover-ranging domain as defined in 8.4.7.3.

Alternatively, if the BS is pre-notified for the upcoming handover MS, it may provide BW allocation infor-mation to the MS using Fast_Ranging_IE to send an RNG-REQ message.

6.3.14 QoS

6.3.14.4 Service classes [Insert new subclause 6.3.14.4.1:]

6.3.14.4.1 Global service flows

Mobile networks require common definitions of service class names and associated AuthorizedQoSParam-Sets in order to facilitate operation across a distributed topology. Global service class names shall be sup-ported to enable operation in this context.

In operation, global service class names are employed as a baseline convention for communicating Autho-rizedQoSParamSet or AdmittedQoSParamSet. Global service class name is similar in function to service class name except that 1) Global service class name use may not be modified by a BS, 2) Global service class names remain consistent among all BS, and 3) Global service class names are a rules-based naming system whereby the global service class name itself contains referential QoS Parameter codes. In practice, global service class names are intended to be accompanied by extending or modifying QoS Param Set defin-ing parameters, as needed, to provide a complete and expedited method for transferrdefin-ing Authorized- or AdmittedQoSParamSet information.

Global service class name A rules-based, composite name parsed in eight information fields of format ISBRLSPTR, elements reference extensible look-up tables. Each information field placeholders must be an expressed value obtained from Table 122a, as part of the name, and may not be omitted.

Table 124a Global service flow class name information field parameters

Position Name Size

(bits) Value

I Uplink/Downlink indicator 1 0 or 1:

0=uplink;

1=downlink S Maximum sustained traffic

rate

6 Extensible look-up Table 122b (value 0b111111 indicates TLV to follow)

T Traffic indication preference 1 0 or 1:

0=No traffic indication;

1=Traffic indication

B Maximum traffic burst 6 Extensible look-up Table 122b (value 0b111111 indicates TLV to follow)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64

Global service flow class name parameters Uplink/Downlink indicator

The Uplink/Downlink indicator parameter identifies the defined service flow direction from the originating entity

Maximum sustained traffic rate

A parameter that defines the peak information rate of the service. The rate is expressed in bits per second and pertains to the service data units (SDUs) at the input to the system. Explicitly, this parameter does not include transport, protocol, or network overhead such as MAC headers or CRCs, or non-payload session maintenance overhead like SIP, MGCP, H.323 administration, etc. This parameter does not limit the instantaneous rate of the service since this is governed by the physical attributes of the ingress port. However, at the destination network interface in the uplink direction, the service shall be policed to conform to this parameter, on the average, over time. On the network in the downlink direction, it may be assumed that the service was already policed at the ingress to the network. If this parameter is set to zero, then there is no explicitly mandated maximum rate. The Maximum sustained traffic rate field specifies only a bound, not a guarantee that the rate is available. The algorithm for policing this parameter is left to vendor differentiation and is outside the scope of the standard.

Table 124b Traffic rate and burst values R Minimum reserved traffic

rate

6 Extensible look-up Table 122b (value 0b111111 indicates TLV to follow)

L Maximum latency 6 Extensible look-up Table 122c (value 0b111111 indicates TLV to follow)

S Fixed-length versus variable-length SDU indicator

1 0 or 1:

0=variable length;

1=fixed length

P Paging preference 1 0 or 1:

0 = No paging generation 1 = Paging generation

R Reserved 4 Shall be set to 0b0000

6-bit Code (binary)

Traffic rate (bits/s)

Burst values (bits)

6-bit Code (binary)

Traffic rate (bits/s)

Burst values (bits)

000000 No

requirement

No requirement

010000 192000 192000

000001 1200 1200 010001 256000 256000

000010 2400 2400 010010 384000 384000

000011 4800 4800 010011 512000 512000

000100 9600 9600 010100 768000 768000

000101 14400 14400 010101 1024000 1024000

000110 19200 19200 010110 1536000 1536000

(bits)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65

Traffic Indication Preference

This parameter is a single bit indicator of an MS s preference for the reception of Traffic cation messages during sleep mode. When set it indicates that the BS may present Traffic Indi-cation messages to the MS when data SDUs bound for the MS are present while the MS is in Sleep Mode.

Maximum traffic burst

The maximum traffic burst parameter defines the maximum burst size that must be accommo-dated for the service. Since the physical speed of ingress/egress ports, any air interface, and the backhaul will in general be greater than the maximum sustained traffic rate parameter for a ser-vice, this parameter describes the maximum continuous burst the system should accommodate for the service assuming the service is not currently using any of its available resources. Maxi-mum traffic burst set to zero shall mean no MaxiMaxi-mum traffic burst reservation requirement.

Minimum reserved traffic rate

The minimum reserved traffic rate parameter specifies the minimum rate, in bits per second, reserved for this service flow. The BS shall be able to satisfy bandwidth requests for a connec-tion up to its Minimum Reserved Traffic Rate. If less bandwidth than its Minimum Reserved Traffic Rate is requested for a connection, the BS may reallocate the excess reserved bandwidth for other purposes. The value of this parameter is calculated excluding MAC overhead. Mini-mum reserved traffic set to zero shall mean no MiniMini-mum reserved traffic rate requirement.

Maximum latency

The value of this parameter specifies the maximum interval between the reception of a packet at CS of BS or SS and the arrival of the packet to the peer device. If defined, this parameter rep-resents a service commitment and shall be guaranteed. A value of zero for Maximum latency shall be interpreted as no commitment.

000111 24000 24000 010111 1921000 1921000

001000 26400 26400

011000-111110

Reserved Reserved

001001 28000 28000

001010 36000 36000 111111 TLV follows TLV follows

001011 44000 44000

001100 48000 48000

001101 56000 56000

001110 64000 64000

001111 128000 128000

6-bit Code (binary)

Traffic rate (bits/s)

Burst values (bits)

6-bit Code (binary)

Traffic rate (bits/s)

Burst values (bits)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64

SDU indicator

The value of this parameter specifies whether the SDUs on the service flow are fixed-length or variable-length.

Paging Preference

This parameter is a single bit indicator of an MS s preference for the reception of paging advi-sory messages during idle mode. When set, it indicates that the BS may present Paging Advi-sory messages or other indicative messages to the MS when data SDUs bound for the MS are present while the MS is in Idle Mode.

[Change 6.3.17 as indicated:]