tia/eiainterim standard

7/29/2019 TIA/EIAINTERIM STANDARD

1/132

TIA/EIA

INTERIM STANDARD

Medium Access Control (MAC)

Standard for cdma2000 Standardsfor Spread Spectrum Systems

TIA/EIA/IS-2000.3-A(Revision of TIA/EIA/IS-2000.3)

MARCH 2000

TELECOMMUNICATIONS INDUSTRY ASSOCIATION

Representing the telecommunications industry in

association with the Electronic Industries Alliance

TIA/EIA/IS-2000.3-A


2/132

NOTICE

TIA/EIA Engineering Standards and Publications are designed to serve the public interest through eliminating

misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of

products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his

particular need. Existence of such Standards and Publications shall not in any respect preclude any member or

nonmember of TIA/EIA from manufacturing or selling products not conforming to such Standards and Publications,

nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TIA/EIA

members, whether the standard is to be used either domestically or internationally.

Standards and Publications are adopted by TIA/EIA in accordance with the American National Standards Institute

(ANSI) patent policy. By such action, TIA/EIA does not assume any liability to any patent owner, nor does it

assume any obligation whatever to parties adopting the Standard or Publication.

Note: The users attention is called to the possibility that compliance with this standard may require use

of an invention covered by patent rights.

By publication of this standard, no position is taken with respect to the validity of this claim or of any

patent rights in connection therewith. The patent holder has, however, filed a statement of willingness to

grant a license under these rights on reasonable and nondiscriminatory terms and conditions to applicants

desiring to obtain such a license. Details may be obtained from the publisher.

TIA/EIA INTERIM STANDARDS

TIA/EIA Interim Standards contain information deemed to be of technical value to the industry, and are published at

the request of the originating Committee without necessarily following the rigorous public review and resolution of

comments which is a procedural part of the development of a TIA/EIA Standard.

TIA/EIA Interim Standards should be reviewed on an annual basis by the formulating Committee and a decision

made on whether to proceed to develop a TIA/EIA Standard on this subject. TIA/EIA Interim Standards must be

cancelled by the Committee and removed from the TIA/EIA Standards Catalog before the end of their third year of

existence.

Publication of this TIA/EIA Interim Standard for trial use and comment has been approved by the

Telecommunications Industry Association. Distribution of this TIA/EIA Interim Standard for comment shall not

continue beyond 36 months from the date of publication. It is expected that following this 36 month period, this

TIA/EIA Interim Standard, revised as necessary, will be submitted to the American National Standards Institute for

approval as an American National Standard. Suggestions for revision should be directed to: Standards &

Technology Department, Telecommunications Industry Association, 2500 Wilson Boulevard, Arlington, VA 22201.

(From Project No. 4695, formulated under the cognizance of the TIA TR-45.5 Subcommittee on Spread Spectrum

Digital Technology.)

Published by

TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2000

Standards & Technology Department

2500 Wilson Boulevard

Arlington, VA 22201

PRICE: Please refer to current Catalog of

EIA ELECTRONIC INDUSTRIES ALLIANCE STANDARDS and ENGINEERING PUBLICATIONS or

call Global Engineering Documents, USA and Canada

(1-800-854-7179) International (303-397-7956)

All rights reserved

Printed in U.S.A.


3/132

PLEASE!

DON'T VIOLATE

THE

LAW!

This document is copyrighted by the TIA and may not be reproduced without

permission.

Organizations may obtain permission to reproduce a limited number of copiesthrough entering into a license agreement. For information, contact:

Global Engineering Documents

15 Inverness Way East

Englewood, CO 80112-5704 or call

U.S.A. and Canada 1-800-854-7179, International (303) 397-7956


4/132


5/132

TIA/ EIA/ IS-200 0.3-A

i

CONTENTS1

1 INTRODUCTION......... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 1-12 1 .1 Scope ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 3 1 .2 Docum ent Releas e History........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 4 1 .3 Terms ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 1-2 5 1 .4 Nu mer ic In forma tion ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 6

1 .5 Norm ative References ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 7 1 .6 Overview ......... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 8 1.6.1 Layering Model....... . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . 1-10 9

1 .7 Convent ions Used in this Docu men t . . . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . . .. . . . .. . . 1-12 10 1.7.1 Service In terfaces ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 11

1.7.1.1 Service Primitives ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 12 1.7.2 Pseu do-code Rules ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 1-12 13

2 Definition of MAC Compon ent s ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 14 2 .1 Service Interfaces (Inf orm ativ e)....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 2-1 15

2.1.1 Service Interface Primitives Received by th e MAC Su blayer....... . . . . . . . . . . . . . . 2-2 16 2.1.2 Service In terface Primitives Sen t from th e MAC Sub layer ....... . . . . . . . . . . . . . . . . 2-4 17

2 .2 En tities of th e MAC Su blayer ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 18 2.2.1 MAC Su blayer Fu n ction al En tit ies ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . 2-5 19

2.2.1.1 Mu x an d QoS Su blayer . . . . . .. . . . . .. . . . .. . . . . .. . . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . .. . . . .. 2-620 2.2.1.1.1 The Multiplex Su blayer ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 2-6 21 2.2.1.1.1.1 Mobile Stat ion Su pport . . . . .. . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . . .. . . . .. . . . .. 2-10 22 2.2.1.1.1.2 Service Priority....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . 2-11 23 2.2.1.1.1.3 Mu lt iplex Su blayer Tran sm it t ing Fu nct ion .. . . . .. . . . . .. . . . . .. . . . . .. . 2-11 24

2.2.1.1.1.3.1 Ass emb lin g th e Physical Layer FCH SDU ......... . . . . . . . . . . . . . 2-11 25 2.2.1.1.1.3.2 Assem bling the Physical Layer DCCH SDU ... . .. . . . . .. . . . . .. . 2-12 26 2.2.1.1.1.3.3 Ass emb lin g th e Physical Layer SCCH SDU......... . . . . . . . . . . . 2-13 27 2.2.1.1.1.3.4 Ass emb lin g th e Physical Layer SCH SDU ......... . . . . . . . . . . . . . 2-15 28

2.2.1.1.1.4 Multiplex Su blayer Receivin g Fu n ction ........ . . . . . . . . . . . . . . . . . . . . . . . 2-19 29 2.2.1.1.1.4.1 Processing the Received Ph ysical Layer FCH SDU ......... 2-25 30 2.2.1.1.1.4.2 Processing th e Received Physical Layer DCCH SDU ... .. . 2-2731 2.2.1.1.1.4.3 Processing th e Received Ph ysical Layer SCCH SDU ....... 2-28 32

2.2.1.1.1.4.4 Processing the Received Physical Layer SCH SDU ......... 2-29 33

2.2.1.1.1.5 MuxPDU Types Processed by the Multiplex Su blayer....... . . . . 2-31 34 2.2.1.1.1.5.1 MuxPDU Type 1 ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 2-34 35 2.2.1.1.1.5.2 MuxPDU Type 2 ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 2-35 36 2.2.1.1.1.5.3 MuxPDU Type 3 ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 2-36 37 2.2.1.1.1.5.4 MuxPDU Type 4 ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 2-37 38 2.2.1.1.1.5.5 MuxPDU Type 5 ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 2-37 39 2.2.1.1.1.5.6 MuxPDU Type 6 ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 2-38 40

2.2.1.1.1.6 In terface to Sign aling ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . 2-38 41 2.2.1.1.1.6.1 Th e MAC-SDUReady.Request Primitive ........ . . . . . . . . . . . . . . . . . 2-39 42 2.2.1.1.1.6.2 Th e MAC-Availab ili ty.Indication Primitive ........ . . . . . . . . . . . . . 2-39 43 2.2.1.1.1.6.3 Th e MAC-Data .Reques t Primitive........ . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39 44 2.2.1.1.1.6.4 Th e MAC-Data .In dication Primitive........ . . . . . . . . . . . . . . . . . . . . . . . 2-40 45

2.2.1.1.1.7 In terface to the Physical Layer ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 2-40 46

2.2.1.1.1.7.1 Th e FCH Tra ns mit Request Service Int erface........ . . . . . . . . . 2-40 47 2.2.1.1.1.7.2 Th e DCCH Tran sm it Reques t Service In terface........ . . . . . . 2-41 48 2.2.1.1.1.7.3 The SCCH Tran sm it Request Service Interface . . . . .. . . . . .. . . 2-41 49 2.2.1.1.1.7.4 The S CH Tran sm it Request Service Interface . . . . .. . . . . .. . . . . 2-41 50 2.2.1.1.1.7.5 Th e FCH Receive In dication Service In terface ........ . . . . . . . . 2-42 51 2.2.1.1.1.7.6 Th e DCCH Receive In dication Service In terface ........ . . . . . 2-42 52 2.2.1.1.1.7.7 Th e SCCH Receive Ind ication Service In terface........ . . . . . . 2-42 53 2.2.1.1.1.7.8 Th e SCH Receive Indication Service In terface........ . . . . . . . . 2-43 54

2.2.1.1.2 SRBP and Common Chan nel Mult iplex Sub layer . . . . .. . . . .. . . . .. . . . . .. . 2-45 55


6/132


ii

2.2.1.1.2.1 Overview (Informa tive)....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . 2-45 1 2.2.1.1.2.1.1 Sync Chan nel . . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . .. . . 2-45 2 2.2.1.1.2.1.2 Forward Comm on Contr ol Chan n el . . . . . .. . . . . .. . . . .. . . . .. . . . . .. . 2-47 3 2.2.1.1.2.1.3 Broadcast Control Cha nn el . . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . .. . . . . 2-48 4 2.2.1.1.2.1.4 Pagin g Cha n nel ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . 2-49 5 2.2.1.1.2.1.5 Access Chan nel Procedu res . . . . .. . . . .. . . . .. . . . .. . . . .. . . . .. . . . .. . . . .. . 2-51 6

2.2.1.1.2.1.6 En ha nced Access Chan nel Procedu res. . . . . . . . .. . . . . .. . . . .. . . . .. 2-58 7 2.2.1.1.2.2 Mobile Sta tion Procedu res ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 2-63 8 2.2.1.1.2.2.1 Sync Chan nel Procedures . . . . . .. . . . .. . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . 2-63 9 2.2.1.1.2.2.2 Paging Cha nn el Procedures . . . . .. . . . . .. . . . .. . . . .. . . . .. . . . . .. . . . .. . . . . 2-64 10 2.2.1.1.2.2.3 Access Chan nel Procedu res . . . . .. . . . .. . . . .. . . . .. . . . .. . . . .. . . . .. . . . .. . 2-64 11 2.2.1.1.2.2.4 En ha nced Access Chan nel Procedu res. . . . . . . . .. . . . . .. . . . .. . . . .. 2-67 12 2.2.1.1.2.2.5 Common Assignmen t Ch an nel Procedu res . . . . .. . . . . .. . . . .. . . . 2-79 13 2.2.1.1.2.2.6 Broadcast Control Chan nel Procedures . . . . .. . . . .. . . . .. . . . . .. . . . 2-81 14 2.2.1.1.2.2.7 Forward Comm on Contr ol Chan nel Procedur es. . . . . . . . . .. . . 2-82 15 2.2.1.1.2.2.8 Reverse Common Control Chan nel Procedures . . . . .. . . . .. . . . 2-82 16

2.2.1.1.2.3 Base Stat ion Procedur es. . . . . . . .. . . . .. . . . . .. . . . .. . . . . .. . . . . .. . . . .. . . . . .. . . . .. 2-8317 2.2.1.1.2.3.1 Sync Chan nel Procedures . . . . . .. . . . .. . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . 2-83 18 2.2.1.1.2.3.2 Paging Cha nn el Procedures . . . . .. . . . . .. . . . .. . . . .. . . . .. . . . . .. . . . .. . . . . 2-83 19

2.2.1.1.2.3.3 Access Chan nel Procedu res . . . . .. . . . .. . . . .. . . . .. . . . .. . . . .. . . . .. . . . .. . 2-83 20 2.2.1.1.2.3.4 En ha nced Access Chan nel Procedu res. . . . . . . . .. . . . . .. . . . .. . . . .. 2-84 21 2.2.1.1.2.3.5 Common Assignmen t Ch an nel Procedu res . . . . .. . . . . .. . . . .. . . . 2-84 22 2.2.1.1.2.3.6 Broadcast Control Chan nel Procedures . . . . .. . . . .. . . . .. . . . . .. . . . 2-87 23 2.2.1.1.2.3.7 Forward Comm on Contr ol Chan nel Procedur es. . . . . . . . . .. . . 2-87 24 2.2.1.1.2.3.8 Reverse Common Control Chan nel Procedures . . . . .. . . . .. . . . 2-88 25 2.2.1.1.2.3.9 Procedur es for Gen erat ing the Chan nel Ident i fier . . . . .. . . . . 2-88 26

2.2.2 Su pervisory Procedu res ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . 2-89 27 2.2.2.1 Mobile Stat ion Tran sm ission Stat is t ics . . . . .. . . . .. . . . .. . . . . .. . . . . .. . . . . .. . . . .. . . . 2-89 28

2.2.2.1.1 Mobile Sta tion Tran sm ission Statistics for th e FCH......... . . . . . . . . . . 2-89 29 2.2.2.1.2 Mobile Sta t ion Tran sm ission Stat is t ics for th e DCCH ... . .. . . . .. . . . .. 2-92 30 2.2.2.1.3 Mobile Stat ion Trans mission Sta t is t ics for th e SCCH ... . .. . . . .. . . . .. 2-94 31 2.2.2.1.4 Mobile Sta tion Tran sm ission Statistics for th e SCH......... . . . . . . . . . . 2-95 32

2.2.2.2 Mobile Sta tion Reception Sta tistics....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-98 33

2.2.2.2.1 Mobile Station Reception Stat istics for the FCH ......... . . . . . . . . . . . . . . . 2-99 34 2.2.2.2.2 Mobile Station Reception Stat istics for the DCCH......... . . . . . . . . . . . 2-101 35 2.2.2.2.3 Mobile Station Reception Stat istics for the SCCH ......... . . . . . . . . . . . 2-103 36 2.2.2.2.4 Mobile Sta t ion Recept ion Stat is t ics for th e SCH ... . .. . . . .. . . . .. . . . .. . 2-104 37

38


7/132


iii

FIGURES 1

Figure 1-1. cdma 2000 Layer Stru cture . . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . 1-92 Figu re 1-2. cdm a2 00 0 Entities an d Service In terfaces (Mobile Sta tion) ....... . . . . . . . . . . .. 1-11 3 Figure 2 -1. Mult iplex Su blayer Trans mit t ing Fu n ct ion E xample. . . . . . . . .. . . . .. . . . .. . . . . .. . . . . . 2-64 Figure 2-2. MuxPDU Types 1, 2, 3, and 4 Processed b y the Mult iplex Sublayer . . . . . . 2-33 5 Figu re 2-3. MuxPDU Type 5 Process ed by th e Multiplex Su blayer ....... . . . . . . . . . . . . . . . . . . . 2-34 6

Figu re 2-4. MuxPDU Type 6 Process ed by th e Multiplex Su blayer ....... . . . . . . . . . . . . . . . . . . . 2-34 7 Figure 2-5. Sync Cha nn el Stru cture Examp le. . . . . . . . . .. . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . . .. . . . .. . . . 2-46 8 Figure 2-6. Forward Comm on Control Chan nel Structu re Example. . . . . . . . . .. . . . . .. . . . .. . . . 2-48 9 Figure 2-7. Forward Broadcas t Contr ol Chan nel Structu re Example . . . . . .. . . . .. . . . .. . . . . .. 2-49 10 Figure 2-8. Paging Cha nn el Structu re E xample . . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . . .. . . . .. . . . .. . . . . . 2-50 11 Figu re 2-9. Access Attem pt (Part 1) ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . 2-52 12 Figu re 2-10. Access Attem pt (Part 2) ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . 2-53 13 Figu re 2-11 . Exam ple of R-ACH Slot Stru ctu re ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 2-55 14 Figu re 2-12 . R-ACH Stru ctu re Exam ple........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . 2-57 15 Figure 2-13. R-ACH Message Ca psu le Stru cture Examp le. . . . . . . .. . . . .. . . . . .. . . . .. . . . . .. . . . .. . . . 2-58 16 Figu re 2-14. Reservation Mode with out Soft Han doff (Exam ple) ....... . . . . . . . . . . . . . . . . . . . . . . . 2-62 17 Figu re 2-15 . Reservation Mode with S oft Han doff (Exam ple) ....... . . . . . . . . . . . . . . . . . . . . . . .. . . . . 2-63 18 Figure 2 -16. Exam ple of Ran dom Access Procedures at the Mobile Stat ion .. . . .. . . . .. . . . 2-67 19

Figu re 2-17 . Exam ple of En ha nced Access Procedu res a t th e Mobile Stat ion (Part 1 of 2)20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 2-72 21 Figu re 2-18 . Exam ple of En ha n ced Access Procedu res d ifferen t at t he Mobile Stat ion22

(Part 2 of 2)....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73 23 24


8/132


iv

TABLES1

Tab le 2-1. Service In terface Primitive Types ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . 2-1 2 Tab le 2-2. Abbr eviation s for Ent ity Names in Service Primitives ........ . . . . . . . . . . . . . . . . . . . . . . . 2-2 3 Tab le 2-3. Service Interface Primitives Received b y th e MAC Su blayer ....... . . . . . . . . . .. . . . . . 2-3 4 Tab le 2-4. Service interface Primitives Sen t from t h e MAC Su blayer ....... . . . . . . . . . . . . . . . . . . . 2-4 5 Tab le 2-5. Multiplex Options Applicable to a FCH or DCCH ......... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 6

Tab le 2-6. Multiplex Options Applicab le to SCCHs........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 7 Tab le 2-7. Multiplex Options Applicable to an SCH When Using MuxPDU Types 1, 2 , or8 3 ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 2-9 9

Table 2-8. Su pported MuxPDU Types for Each Physical Chan nel Type .. . . .. . . . .. . . . . .. . . . . 2-910 Table 2-9. Fields Used to Compu te Mu lt iplex Option Num bers Greater than 0x10 .. 2-10 11 Tab le 2-10 . Defau lt Num ber of LTUs in an SCH Physical Layer SDU ......... . . . . . . . . . . . . . 2-18 12 Tab le 2-11. Received Mu xPDU Type 1 Categories an d Form ats for th e FCH and DCCH13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 2-20 14 Tab le 2-12. Received Mu xPDU Type 2 Categories an d Form ats for th e FCH and DCCH15

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 2-21 16 Tab le 2-13. Received Mu xPDU Type 4 Categories an d Form ats for th e FCH and DCCH17

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 2-22 18 Tab le 2-14. Received Mu xPDU Type 6 Categories an d Form ats for th e FCH and DCCH.19

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 2-23 20 Tab le 2-15. Received MuxPDU Type 1 Categories an d Forma ts for th e SCCH and for the21 SCH ......... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24 22

Tab le 2-16. Received MuxPDU Type 2 Categories an d Forma ts for th e SCCH and for the23

SCH ......... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25 24 Tab le 2-17 . Received MuxPDU Type 3 Categories an d Forma ts for the SCH......... . . . 2-25 25 Tab le 2-18 . Received MuxPDU Type 5 Categories an d Forma ts for the SCH......... . . . 2-25 26 Tab le 2-19 . MuxPDU Type 1 Forma ts ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 2-35 27 Tab le 2-20 . MuxPDU Type 2 Forma ts ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 2-36 28 Tab le 2-21 . MuxPDU Type 3 Forma ts ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 2-37 29 Tab le 2-22 . MuxPDU Type 4 Forma ts ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 2-37 30 Tab le 2-23 . MuxPDU Type 5 Forma ts ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 2-38 31 Table 2-24. Calculated, Ran dom, a nd Hash ed Variables . . . . .. . . . .. . . . . .. . . . .. . . . .. . . . . .. . . . . .. . . 2-56 32

Tab le 2-25 . Has h Fu nct ion Modifier ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . 2-66 33

Table 2-26. R-EACH/ R-CCCH Data Rate an d Fram e Dura t ion a nd Bit Posit ion of 34

EACH_BA_RATES_SUPPORTEDs/ RC CC H_RATE S_SUPPO RTE Ds . . .. . .. . 2 -7735 Tab le 2-27 . Form at of th e R-EACH Header ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . 2-77 36 Tab le 2-28. RATE_WORD En coding........ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 2-78 37 Table 2-29. Forma t of Early Acknowledgemen t Ch an nel Assignmen t Message .. . . .. . . . 2-85 38 Tab le 2-30 . Forma t of Power Contr ol Cha nn el Ass ign men t Mess age (PCCAM)........ . . 2-86 39 Table 2-31. FCH Tran sm ission Coun ters for Mult iplex Option 0x1 .. . . . .. . . . .. . . . . .. . . . .. . . 2-90 40 Table 2-32. FCH Tran sm ission Coun ters for Mult iplex Option 0x2 .. . . . .. . . . .. . . . . .. . . . .. . . 2-91 41 Table 2-33. DCCH Tran sm ission Coun ters for Mu lt iplex Option 0x1 .. . . . .. . . . . .. . . . .. . . . . 2-92 42 Table 2-34. DCCH Tran sm ission Coun ters for Mu lt iplex Option 0x2 .. . . . .. . . . . .. . . . .. . . . . 2-93 43 Tab le 2-35 . SCCH Tran sm ission Coun ters ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 2-95 44 Table 2-36. SCH Trans mission Coun ters . . . . .. . . . . .. . . . .. . . . . .. . . . .. . . . . .. . . . . .. . . . .. . . . . .. . . . .. . . . . .. . 2-9645

Tab le 2-37. Tran sm ission Coun ters for R-SCH0 (Mux Opt ion 0xf20, for Non-flexible46 Data Rates) ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97 47

Tab le 2-38. Tran sm ission Coun ters for R-SCH2 (Mux Opt ion 0xf20, for Non-flexible48

Data Rates) ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97 49 Tab le 2-39. Tran sm ission Coun ters for R-SCH0 (Mux Option 0 xf20, for Flexible Data50

Rates)....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 2-98 51 Tab le 2-40. Tran sm ission Coun ters for R-SCH2 (Mux Option 0 xf20, for Flexible Data52

Rates)....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 2-98 53 Tab le 2-41 . FCH Reception Coun ters for Multiplex Option 0x1........ . . . . . . . . . . . . . . . . . . . . . . . 2-99 54 Tab le 2-42 . FCH Reception Coun ters for Multiplex Option 0x2........ . . . . . . . . . . . . . . . . . . . . . 2-100 55


9/132


v

Tab le 2-43 . DCCH Reception Coun ters for Multiplex Option 0x1 ........ . . . . . . . . . . . . . . . . . . 2-101 1 Tab le 2-44 . DCCH Reception Coun ters for Multiplex Option 0x2 ........ . . . . . . . . . . . . . . . . . . 2-102 2 Table 2-45 . SCCH Recept ion Coun ters . . . . .. . . . . .. . . . .. . . . . .. . . . .. . . . . .. . . . .. . . . . .. . . . . .. . . . .. . . . . .. . . 2-104 3 Tab le 2-46 . SCH Reception Coun ters....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-105 4 Table 2-47. Reception Counters for F-SCH0 (Mux Option 0xf20, for Non-flexible Data5

Rates)....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 2-106 6

Table 2-48. Reception Counters for F-SCH2 (Mux Option 0xf20, for Non-flexible Data7 Rates)....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 2-107 8 Tab le 2-49. Reception Coun ters for F-SCH0 (Mux Option 0xf20, for Flexible Data Rates)9

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 2-108 10 Tab le 2-50. Reception Coun ters for F-SCH2 (Mux Option 0xf20, for Flexible Data Rates)11

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . 2-108 12 13


10/132


No text.1


11/132


1-1

1 INTRODUCTION1

This s tan dard s s pecificat ion documen t defines the cdma 2000 Medium Access Contr ol2

(MAC) su bla yer.3

1 .1 Scope4

Th is stan da rd p rovides th e detailed defin itions of all compon ent entit ies with in th e MAC5 Sublayer, the service interfaces and primitives exchanged between entit ies within the6

MAC Su blayer, an d th e service in terfaces an d pr imitives excha n ged between th e MAC7

Su blayer and other layers in th e cdma 2000 fam ily of s tan dard s. This s tan dard a lso8

prescribes the normative procedures for the behavior of the MAC Sublayer entit ies.9

1 .2 Docum en t Re l ea s e His t o r y10

Th is docum ent is Revision A of TIA/ EIA/ IS-200 0.3.11


12/132


1-2

1 . 3 T e r m s1

ACH Access Chan nel .

Bas e s t a t i on A fixed st ation u sed for commu nicating with m obile

stat ions. Depending upon th e context , the term bas e

sta tion ma y refer to a cell , a sector within a cell , an MSC,

or other part of the wireless system.

Blank da t a b lock A data block that contains no service information bits.

BS Base s tat ion.

CCCH Common Control Chan nel .

Conf igure d Mult ip lex

Opt ion

The multiplex option number stored in the Service

Configuration Record for a physical channel (see [5]).

cs ch Common Signa ling Cha nn el.

A point to multipoint logical channel that carries Upper

Layer Signaling traffic over a comm on p hysical cha nn el.

Data Block The unit of information exchanged between the multiplex

su blayer an d a service or Upper Layer Signalin g.

DCCH Dedicated Control Cha nn el.

Dedi ca t ed An att ribu te of the forward or reverse ph ysical or logical

cha nn el, implying tha t the ch an nel can only be us ed by a

single u ser .

ds ch Dedicated Signaling Channel.

A point-to-point logical cha nn el that carr ies Upp er Layer

Signa lin g traffic over a dedicated ph ysical cha n n el.

d t c h Dedicated Traffic Cha n n el.

A point-to-point logical cha nn el tha t car ries da ta or voice

tra ffic over a d edicated ph ysical cha n nel.

DT X Discont inuous Transmission.

EACAM Early Acknowledgement Channel Assignment Message.

EACH Enhanced Access Channel .

Even t A st imu lus genera ted outs ide of an ent i ty that t r iggers

some pr ocedu re within the ent i ty.

F-BCCH Forward Broadcas t Control Chan nel .

F-CACH Forward Common Assignm ent Cha nn el.

F-CCCH Forward Comm on Control Cha nn el.

FCH Fundamenta l Channel .

F-CPCCH Forward Common Power Control Chan nel .

The ph ysical cha nn el tha t carr ies Common Cha nn el power

control in forma tion on th e forward link.

F-CPCSCH Forward Common Power Control Sub-cha nn el.

The physical sub-channel that carr ies Common Channel

power control in forma tion on th e forward link.


13/132


1-3

f-csch Forward Comm on Signa l ing Cha nn el.

A csch th at car r ies information from th e base s tat ion to the

mobile station.

f -dsch Forward Dedicated Signaling Channel.

A dsch tha t carr ies informa tion from th e base s tat ion to th e

mobile station.

f -dtch Forward Dedicated Traffic Ch an nel.

A dtch tha t carr ies informa tion from the b ase s tat ion to the

mobile station.

Fill MuxPDU A MuxPDU Type 3 th at is n ot ass ociated with an y service,

u sed a s fil ler when as sem blin g a Physical Layer SCH SDU.

F-PCH Forward Paging Ch an nel .

The physical channel that carr ies Common Channel

informa tion on th e forward link an d th at is backward

compa tible with th e TIA/ EIA-95-B Paging Ch an nel.

F r a m e d u r a t i on The du rat ion of a p hysical chan nel t ran sm ission interval ;ma y be 5, 10, or 20 ms .

IMSI Intern ationa l Mobile Su bscr iber Iden tity.

See [5].

LAC Link Access Control.

Ent i ty tha t provides assu red mode or u nas su red mode

delivery of in forma tion across th e air interface between t h e

mobile s tat ion a nd the ba se s tat ion. See [4].

Logica l Chan ne l Logical conn ection between peer en tit ies.

LPM Logical-to-Ph ysical Mapp ing.

Information that is used by the Multiplex Sublayer for

perform ing th e logical-to-ph ysical cha nn el ma pping. See

[5].

LTU Logical Tran sm ission Un it.

One or m ore Type 3 or Type 5 Mu xPDUs with a 16-bit CRC.

MAC Mediu m Access Contr ol.

Ent ity that controls th e access to an d from Upper Layer

Signa ling, Da ta Services, a n d Voice Services to Physical

Layer resources.

Mobi le s t a t ion A stat ion tha t commu nicates with th e base s tat ion.

Mode A Multiplex Sublayer operational mode in which the Radio

Configuration is less than or equal to 2.

Mode B Multiplex Sublayer operational mode in which the Radio

Configurat ion is greater th an 2.

MS Mobile station.


14/132


1-4

Mult ip lex Opt ion Used to s pecify the m u ltiplex sub layer opera tion for a

physical channel. Each Multiplex Option specifies the

available data rates for the physical channel (FCH, DCCH

or ma x SCH rate).

MuxPDU Multiplex Su blayer Protocol Data Unit.

One or more data blocks combined according to multiplexoption rules.

Null MuxPDU A MuxPDU that contains no bi ts .

Null Traffic MuxPDU A MuxPDU conta ining only th e lowest n egotiated tra ns mit

ra te pr ima ry tra ffic data block with all bits s et to 1.

PCCAM Power Control Channel Assignment Message.

PDU Protocol Data Unit.

An atomic set of data , h eader information, an d control

informa tion t ha t is provided b y a service u ser to a s ervice

provider.

Phys i ca l Chann e l Radio t rans mission link.Phys ica l Layer SDU An S DU that is generated by the Mux an d QoS Ent i ty that

is accepted by the Physical Layer for transmission.

Pr ima ry Traf fi c Data bi ts from a service that ha s th e t raffic type in the

Service Configura tion Record s et to Prima ry.

Pr i m i t i ve An abs tract , a t omic, implementa t ion-independen trepresenta t ion of an intera ct ion between a service us er an d

its s ervice provider. See [7].

QO F Qua si-Orthogona l Fun ct ion.

Set of nu merical sequences t ha t are u sed in place of Walsh

codes, and which have pair-wise low cross correlations, but

which are less than perfectly orthogonal.

Qo S Qu ality of Ser vice.

Metrics th at a ffect th e qua lity of a d ata service th at is

delivered to an end u ser (e .g. , throu ghpu t , guara nteed bi t

rat e, delay, etc.).

R a t e S e t 1 The se t of da ta ra tes 9 .6 , 4 .8 , 2 .7 / 2 .4 , 1 .5 / 1 .2 kbps , and

all integral mu ltiples of 9.6 kbp s. Data ra tes of 2.7 an d 1.5

kbp s a re only applicable to reverse Rad io Configura tion s 3

an d 5 a nd forward Radio Configurat ions 3, 4, 6 , an d 7.

R a t e S e t 2 The set of data rates 14 .4, 7.2, 3.6, 1.8 kbps, a nd al l

integral multiples of 14.4 kbps.

R-CCCH Reverse Comm on Control Chan nel .

R-CCCH slot Reverse Common Control Channel Slot

The reverse Common Control Channel Slot with length

RCCCH_SLOTs .


15/132


1-5

r -csch Reverse Comm on Signa ling Ch an nel .

A csch that carries information from the mobile station to

the ba se s ta t ion .

r -dsch Reverse Dedicated Signaling Channel.

A dsch that carries information from the mobile station to


r -d tch Reverse Dedicated Traffic Cha n nel.

A dtch that carries information from the mobile station to


RLP Rad io Link Protocol.

Connection-oriented, negative-acknowledgment-based data

delivery prot ocol.

SCCH Supplemental Code Channel .

The Physical Layer Supplemental Code Channel.

SCH Supplementa l Chan nel.The Physical Layer Su pplemental Ch an nel .

SDU Service Data Unit.

A set of data, header information, and control information

th at is a ccepted by a s ervice provider from a s ervice us er.

Secon dary Traf f ic Data bi ts from a service that ha s th e t raffic type in the

Service Configura tion Record set to Secon da ry.

Signa l ing da t a b lock The u ni t of data excha nged between th e mu lt iplex su blayer

an d s ignal ing.

Signal in g Traff ic Another name for the signaling information bits.

sr_id Service Referen ce iden tifier.

A u nique nu mber a ssigned to each connected service

opt ion insta nce.

SRBP Signa ling Ra dio Burs t Protocol.

An ent ity that provides conn ectionless p rotocol for

Signa ling mess ages.

1


16/132


1-6

1 .4 Num er i c I n fo r m a t i on1

Num eric informa tion is d efined in [5]. Th e following a re ad ditiona l int ern al values th at2

are defined in th is s ta nda rd. The valu es are s tored by the mobile s tat ion in temp orary3

mem ory an d are n ot sent over th e air. The scope of th ese int ern al values is limited to4

th i s s t andard .5

ACC_FRAME_DURATIONs Frame durat ion that corresponds to ACC_RATEs , in u ni ts6

of 5 m s.7

ACH_FRAME_SIZE Size, in bits , of th e R-ACH ph ysical layer fram e. The value of8

ACH_FRAME_SIZE is 88 .9

ACC_MAX_DURATIONs Maximu m du rat ion th at th e mobile s tat ion can t ra ns mit10

continuously on the R-EACH or R-CCCH, in units of 5 ms.11

ACC_MIN_RATE s Minimu m tr an sm ission rate , in bps , tha t th e mobile s tat ion12

su pports for t ran sm ission of a Layer 2 encap su lated PDU in less th an13

ACC_MAX_DURATIONs .14

ACC_MODE s Access Mode.15

ACC_MSG_SIZEs Size of th e Layer 2 en caps u lated PDU in bits.16

ACC_NUM_BITSs Num ber of informa tion bits in a Ph ysical Layer fram e correspon ding17

to ACC_RATEs .18

ACC_PREAMBLE_TX_SLOT s Th e R-EACH slot in dex at which th e prea mb le is to b e19

t r ansmi t t ed .20

ACC_RATEs Tran sm ission rat e of th e R-EACH or R-CCCH, in bps .21

BCCH_FRAME_SIZE Size, in bits, of th e F-BCCH ph ysical layer fra m e. The value of22

BCCH_FRAME_SIZE is 744.23

EACH_SLOT s Enh an ced Access Ch an nel s lot s ize in u ni ts of 1.25 m s.24

FCCCH_FRAME_SIZE Size, in bits, of the F-CCCH physical layer frame.25

PCH_FRAME_SIZE Size, in bits, of the F-PCH physical layer frame.26

SYNC_FRAME_SIZE Size, in bits, of th e F-SYNC ph ysical layer fram e. The value of27

SYNC_FRAME_SIZE is 32 . 28

1 .5 Nor m a t i ve Re fe r ence s29

The following standards contain provisions that, through reference in this text,30

cons titute provisions of th is Stan da rd. At the time of pu blication, th e editions in dicated31

were val id. All s tanda rds a re su bject to revis ion, a nd par t ies to agreements based on32

this Standard are encouraged to investigate the possibili ty of applying the most recent33

editions of th e stan da rds ind icated b elow. ANSI an d TIA ma intain registers of cu rren tly34

valid nat iona l s tan dards pu bl ish ed by them .35

Standards:36

1. Reserved.

2. TIA/ EIA/ IS-2000.2-A, Physical Layer Stan dard for cdma 2000 Spread Spectru m

Systems, March, 2000.

3. Reserved.

4. TIA/ EIA/ IS-200 0.4-A, Link Access Control (LAC) Sta n dar d for cdm a20 00

Spread Spec t rum Sys tems , March , 2000.

5. TIA/ EIA/ IS-200 0.5-A, Upper Layer (Layer 3) Sign alin g Sta nd ard for cdma 200 0

Spread Spec t rum Sys tems , March , 2000.

6. Reserved.


17/132


1-7

7. ITU-T Recomm end ation X.210 (11/ 93) Informa tion techn ology Open System s

Interconn ection Basic reference m odel: Conventions for th e definition of OSI

services, International Telecommunication Union.

1

Other Documents:2

9. ISO/ IEC 14882 :1998 Program ming lan guages - C++.

3


18/132


1-8

1.6 Overview1

Section 1 conta ins an overview of th is sta nd ard . Section 2 defines the n orma tive2

beh avior of th e MAC su blayer by describing the p recise pr ocessing ru les for each of th e3

MAC su blayer entit ies. Section 2 a lso describes the overall str u ctu re of th e MAC4

su blayer , defines t he ent ity and service model tha t is us ed within th is s ta nd ard, a nd5

specifies th e entit ies tha t comp rise the MAC su blayer.6

As sh own in Figu re 1-1, IS-951 ha s a layered s t ru cture providing voice, packet da ta (up7

to 64 kbps), simple circuit data (e.g., async Fax), and simultaneous voice and packet8

da ta services. At the m ost bas ic level, cdma 200 0 provides protocols an d services tha t9

correspon d to th e bottom two layers of the ISO/ OSI Reference Model (i .e., Layer 1 - th e10

Physical Layer, an d Layer 2 - the Link Layer) according to th e general str u ctu re11

specified by th e ITU for IMT-2000 system s. Layer 2 is fu rth er su bdivided int o the Lin k12

Access Control (LAC) sublayer and the Medium Access Control (MAC) sublayer.13

Applications and upper layer protocols, corresponding to OSI Layers 3 through 7, util ize14

th e services provided by the cdma 200 0 LAC services. Exam ples in clu de Sign alin g15

Services, Voice Services, Pa cket Da ta Applications , a nd Circu it Data Applications.16

Motivated by higher bandwidths and the need to handle a wider variety of services,17

several enh an cements ha ve been incorporated into cdma200 0. In cdma 2000, a18 genera lized mu lti-media s ervice model is s u pported. Th is allows a comb ination of voice,19

packet d ata , an d ci rcui t data services to be operat ing concurren t ly (within t he20

l imitat ion s of th e air interface system ca pa city). cdm a2 000 a lso includes a Qu ality of21

Service (QoS) control mech an ism to ba lance th e varyin g QoS requ irement s of mu ltiple22

concurren t s ervices .23

1 In t his sect ion, th e term IS-95 denotes an y of the s tan dards tha t are predecessors to

cdm a2 000 , i .e., IS-95, IS-95-A, an d TIA/ EIA-95-B.


19/132


1-9

MACSublayer

Upper LayerSignaling

Physical Layer

LACSublayer

DataServices

VoiceServices

Multiplexing andQoS Delivery

SignalingtoPhysicalLayerInterface

RLP RLP RLP

OSILayers

3-7

OSILayer

2

OSILayer

1

SRBP

1

Fi gu r e 1 - 1 . cdm a200 0 Laye r S t r uc t u r e2

The cdma2000 MAC sublayer provides two important functions:3

Best E ffort Delivery - reason ab ly reliable tra ns miss ion over th e ra dio link with a4 Radio Link Protocol (RLP) that provides a best effort level of reliability; and5

Multiplexing an d QoS Con trol - enforcemen t of negotiated QoS levels b y mediating6 conflicting reques ts from compet ing services an d by th e app ropriate pr iorit ization of7

access requests .8


20/132


1-10

1.6 .1 Layer ing Model1

Figure 1-2 depicts the cdma2000 entit ies and services interfaces from the mobile2

station perspective.3


21/132


1-11

1

2

RLP

Data Service(s)

Voice Service(s)

Signaling LAC

SRBP

Data Burst

L3 PDU

LAC PDU

Data

Mux and QoS Sublayer

Voice

RLP

RLP SDU

f/r-dtchf/r-csch f/r-dsch

Signaling to Physical Layer Interface

UpperLayers

Physical Layer (Coding and Modulation)

LACSublayer

MAC

Sublayer

PhysicalLayer

Multiplex SublayerCommon Channel Multiplex Sublayer

F-SYNCF-

BCCHF-CACH R-EACH

F-CPCCH

R-ACH F-PCHF/R-

CCCHF/R-

DCCHF/R-FCH

F/R-SCHi

f/r-dtch

f-csch

Upper LayerSignaling

3 4

Fi gu r e 1 - 2 . cdm a200 0 En t i t i e s and Se r v ice I n t e r f ace s (Mob il e S t a t i on )5


22/132


1-12

1 .7 Conven t i ons Us ed i n t h i s Docum en t1

1 .7 .1 Se r v ice I n t e r f ace s2

1 .7 .1 .1 Se r v ice P r i m i t i ve s3

Service pr imit ives are abs tract , a tomic, implementa t ion-independen t representa t ions of 4

intera ctions b etween a service user a nd its service provider. No requ irem ent is placed5

on th e mobile stat ion or th e bas e stat ion to implement s pecific service primitives. See6

[7].7

1 .7 .2 Ps eudo-code Ru l e s8

Pseu do-code to describe procedur es in th is sta nd ard will follow the flow cont rol and9

syn tax of th e C++ program min g lan gua ge [9].10


23/132


2-1

2 DEF INITION OF MAC COMPONENTS1

2 .1 Se r v ice I n t e r f ace s (In f o r m a t i v e )2

Th is section describes t he fun ction al service int erfaces t o an d from en tit ies of th e MAC3

su blayer . To sup port the m u lt i-media capa bi lit ies required by cdm a200 0, i t is4

necessar y tha t th e ab stract fun ct ional descr ipt ion of the ai r interface (pr imari ly the5 precise defin ition of the mobile st ations operat ion) be d ecomposed into n arr owly defined6

functional e n titie s . Fu rth erm ore, each of th ese fu nct iona l ent it ies is described by:7

a set of service interface primitives for every event tha t acts as a s t imu lu s for a8 functional entity (informative);9

a set of proce d ures th at th e fu n ction al ent ity is t o follow when a valid primitive is10 encou nt ered in ea ch sta te (e.g., set a t imer, m odify a variable, etc.) (n orma tive).11

The conventions that are used for service interface primitives are shown in Table 2-1,12

an d con form to [7].13

Table 2-1 . Serv ice In te r face Pr imi t ive Types14

Pr i m i t i ve Type Sour ce Des t i na t i on Pu r pos e

Requ es t service u ser service provider Request a service,

resource, e tc .

Confirm ser vice pr ovider ser vice u ser Resp ons e (pos itive or

n egative) to a Request

primitive.

Ind ica tion service provider service u ser Ind icates tha t data ha s

arr ived or a n even t for

the service user h as

occurred.

Res pon s e service u ser service provider Ackn owledgmen t of an

Indication.

15


24/132


2-2

The invocation of service primitives is notated as follows:1

RX-Primitive .Primitive_Type (parameters)2

where:3

RX - An ab br eviat ion for th e s ervice provider en tity (e.g., MAC for MAC

su blayer); see Tab le 2-2

Prim itive - The name of the specific primitive to or from the service provider

(e.g., Data)

Primitive_Type - The specific Primitive Type as defined in Table 2-1 (e.g., Request)

param ete rs - A list of parameters for the primitive (e.g., channel_type, d ata, an d

size ); some pr imit ives m ay h ave no pa ram eters .

4

For example, a request to the MAC sublayer to transmit data specified by the variable5

data , of type channel_type, and of size size , is n otated as follows:6

MAC-Data.Requ est (channel_type, d ata, size)7

Table 2-2 su mm arizes th e abbr eviat ions (RX) that are used in Service Primitive names8

for variou s en tit ies th at a re providers of services.9

Table 2-2 . Abbrevia t ions for Ent i ty Nam es in Serv ice Pr imi t ives10

Ent i ty (Serv ice Provider ) Abbrevia t ion

(R X)

P r i m i t i ve s

Defined In

Mediu m Access Con trol Sub layer MAC th i s s t andard

Physical Layer PHY [2]

11

Th e following su bs ections conta in a s u mm ary of th e service in terface defin itions .12

2.1 .1 Serv ice In te r face Pr imi t ives Rece ived by th e MAC Sublayer13

Th e primitives s ent from th e Sign aling LAC to th e MAC ar e su mm arized in Tab le 2-3.14


25/132


2-3

Table 2-3 . Serv ice In t e r face Pr im i t ives Rece ived by th e MAC Sublayer1

Pr i m i t i ve

Type

Pr im i t i ve Pa r am e t e r s No t e s

Requ es t MAC-SDUReady channel_type,

size, P, seqno,

scheduling_hint

Initiates sending of a MAC SDU.

channel_type is s et to 5ms FCH/ DCCH

fram e, 20ms FCH/ DCCH frame, F-CCCH

frame, F-BCCH frame, R-CCCH frame,

F-PCH frame, F-SYNC frame, R-ACH

frame or ENHANCED ACCESS frame;

size is th e size of th e SDU in bits;

P is th e value u sed in th e persis tence test ;2

seqno is th e access pr obe coun t within th e

cur rent access sub-a t t empt ;3 a n d

scheduling_hintis a n indicator to the

mu ltiplex sub layer on h ow to priorit ize

fragments of the Layer 2 en capsu lated PDU

relative to other types of multiplexed traffic

(e .g. , to determine whether to u se blank -and-

burs t or d im-and-burs t )4.

Requ es t MAC-Data channel_type,

data, size

In resp ons e to the MAC-

Availab ility.In dicat ion pr imitive, th is

pr imit ive carr ies the da ta to be t ra ns mit ted.


fram e, 20ms FCH/ DCCH frame, F-CCCH




data is a n S DU or a f ragment of an SDU; an d

s ize is th e size ofdata in bits.

2

2 Only u sed for th e r -csch.

3 Only u sed for th e r -csch.

4 Only u sed for the ds ch.


26/132


2-4

2 .1 .2 Se r v ice In t e r f ace P r im i t i ve s Sen t f r om t h e MAC Sub laye r1

Th e primitives s ent from th e MAC en tity to the LAC en tity are sh own in Tab le 2-4.2

Table 2-4 . Serv ice in te r face Pr imi t ives Sent f rom the MAC Sublayer3

Pr i m i t i ve

Type

Pr im i t i ve Pa r am e t e r s No t e s

Ind ica tion MAC-Data channel_id, channel_type,

data, size,

system_time

The MAC Su blayer d elivers data .

channel_id is a ch an nel iden tifier for th e

ph ysical chan nel on which th e data was

received (see 2.2 .1.1.2 .3.9);


fram e, 20m s FCH/ DCCH fram e, F-CCCH




data is a n SDU or a fragmen t of an SDU;

size is th e size ofdata in bi ts ; an d

system_time i s the t ime at wh ich th e

Physical Layer received the first bit of the

Physical Layer fram e conta ining data .

Ind ica tion MAC-Availability type, max_size,

system_time

Indicat ion of the m aximu m nu mber of bits

tha t can be t ransm it t ed by the next frame.

type is th e type of data to be t ran sm it ted

(e.g., 5 ms, 2 0 m s, or either);

max_size is th e maximum nu mber of bi ts

tha t can be placed in th e Physical Layer

SDU; an d

system_time i s the t ime at wh ich th ePhysical Layer will tran sm it the first bit of

th e Physical Layer fram e conta ining all th e

information bits supplied.

Ind ica tion MAC-

AccessFailure

reason,

acceptable_rate

reason is the reason for the access failure.

reason ma y ha ve one of the followin g valu es:

Timer Expired or Insufficient

Tran sm ission Rate, an d

acceptable_rate is set to the m aximu m

ins tan taneous t ran smiss ion ra te tha t can be

u sed for th e t ran sfer , whenever reason is set

to Ins u fficient Trans miss ion Rate.

Res pon s e MAC-SDUReady access_mode access_mode is th e access m ode selected by

the SRBP entity for the transmission of the

MAC S DU (i.e., Bas ic or Res erva tion ).

4 4


27/132


2-5

2.2 Ent i t i es of th e MAC Sublayer1

Th is section d efines each of th e entit ies in t he MAC Su blayer an d defines th e2

procedures that these entit ies follow when processing events and service primitives from3

other ent i t ies . The s ub sect ions in th is sect ion ma y conta in informa tive text that is4

designated Inf orm ative in th e sect ion head ing. Otherwise, the su bsect ions contain5

normative text.6

2 .2 .1 MAC Sub laye r Fun c t i ona l En t i t i e s7

This section describes the functional entit ies that are contained within the MAC8

Sublayer .9


28/132


2-6

2 .2 .1 .1 Mux and QoS Sub laye r1

2 .2 .1 .1 .1 The Mul t i p lex Sub laye r2

The m ult iplex su blayer ha s both a t ra ns mit t ing an d a r eceiving fun ct ion. The m u lt iplex3

sublayer transmitting function combines information from various sources (e.g., Upper4

Layer Signaling, Data Service insta nces , an d Voice Service) an d forms Physical Layer5 SDUs for tran sm ission (see Figur e 2-1). The mu ltiplex su blayer receiving fu nct ion6

separa tes th e informa tion conta ined in Physical Layer SDUs, an d directs th e7

informa tion to th e correct ent ity (e.g., Upper Layer Signaling, Da ta S ervice insta nces , or8

Voice Service).9

Multiplex

Sublayer

Data Service (sr_id = 1)Signaling

dsch dtch, sr_id = 1

dtch, sr_id = 1

data

block

data

block

data

block

data

block

Header

(format bits)

MuxPDU

Header

data block CRC data block

MuxPDU Type 3 or 5

LTU

CRC

SCH SDU

FCH or DCCH SDU

MuxPDU Type 1, 2, or 6

MuxPDU

HeaderLPM Table

data block

data block

LTU

MuxPDU Type 3 or 5

10 11

Fi gu r e 2 - 1 . Mul t i p lex Sub laye r T r ans m i t t i ng Func t i on Exam pl e .12

Th e mu ltiplex su blayer operat es in one of the following two m odes:13

Mode A is u sed when operatin g with a TIA/ EIA-95-B Ph ysical Layer.14

Mode B is u sed wh en operat ing with a cdma2 000 Physical Layer .15


29/132


2-7

The t r an sm it t ing fu nct ion, u nd er QoS control ,5 solicits inform ation bits from s ign aling1

an d conn ected s ervices . Informa tion b its are exchan ged b etween s igna ling an d th e2

multiplex sublayer using the primitives described in 2.2.1.1.1.6; the multiplex sublayer3

converts th e in forma tion bits received from s igna lin g in to a da ta b lock. Informa tion bits4

are exchan ged b etween a connected service or a logical chan nel an d th e mu lt iplex5

sublayer in a unit called a data block. The multiplex sublayer multiplexes one or more6

data blocks into a MuxPDU and combines one or more MuxPDUs into a Physical Layer7 SDU for tra n sm ission b y the Ph ysical Layer. Physical layer SDUs a re excha nged8

between the multiplex sublayer and the Physical Layer using the service interface9

operat ions in 2.2.1.1.1.7.10

Th ere is a s ingle MuxPDU in each Physical Layer FCH or DCCH SDU. Tab le 2-19 an d11

Table 2-20 detail the data block combinations allowed in the MuxPDU that forms a 2012

ms Physical Layer FCH or DCCH SDU. As s hown in Table 2-22, only a sin gle dat a b lock13

is in t h e Mu xPDU th at is u sed to form a 5 ms Physical Layer FCH or DCCH SDU. Table14

2-5 lists the various multiplex options used with the FCH or DCCH.15

Table 2-5 . Mul t ip lex Opt ion s Appl icable t o a FCH or DCCH16

Multiplex Option

Rate Set 1 Rate Set 2FCH 0x1, 0x704 0x2, 0x704

DCCH 0x1, 0x704 0x2, 0x704

17

18

5 When operat ing in Mode A, th e mu ltiplex su blayer as signs relative service priority (see

2.2.1.1.1.2)


30/132


2-8

When operatin g in Mode A, one Mu xPDU is u sed to form ea ch Physical Layer SCCH1

SDU. Each MuxPDU used contains a single data block. Table 2-6 lists the various2

multiplex options used with SCCHs.3

Table 2-6 . Mult ip lex Opt ion s Appl icable to SCCHs4

Multiplex Opt ionMaximum

Num ber of SCCHs

Maximum

Nu mber of MuxPDUs

Rate Set 1 Rate Set 2

1 1 0x3 0x4

2 2 0x5 0x6

3 3 0x7 0x8

4 4 0x9 0xa

5 5 0xb 0xc

6 6 0xd 0xe

7 7 0xf 0x10

5

When oper ating in Mode B, one or m ore Mu xPDUs a re u sed to form a Ph ysical Layer6

SCH SDU. Each MuxPDU used contains a single data block. The multiplex option7

ass ociated with th e SCH defines both th e nu mb er of Mu xPDUs in the SDU an d defines8 th e size of th e dat a b lock in each MuxPDU. Tab le 2-7 lists th e variou s m u ltiplex options9

used with the SCH at various frame lengths when using MuxPDU Type 1, Type 2, or10

Type 3 .11


31/132


2-9

Table 2-7 . Mult ip lex Opt ion s Appl icable to an SCH Whe n Using MuxPDU Types 1 ,1

2 , o r 32

Multiplex OptionMaximu m Num ber of

MuxPDUs in the Physical

Layer SDURate Set 1 Rate Set 2

MuxPDU Type3

MuxPDU Type 3 MuxPDU Type 3

Bits p er

SCHPhysical

Layer SDU

MuxPDUType

1 or 2 single double

MuxPDUType 1

single double

MuxPDUType 2

single double

172 / 267 1 0x3 0x4

360/ 552 2 1 0x809 0x905 0x80a 0x906

7 4 4 / 1 1 28 4 2 0x811 0x909 0x812 0x90a

1512/ 2280 8 4 0x821 0x911 0x822 0x912

3048/ 4584 8 0x921 0x922

3

When u sing MuxPDU Type 1, 2, or 3, for th e SCH, the m u ltiplex su blayer derives th e4

mu lt iplex opt ion in us e for the SCH bas ed u pon th e configured m u lt iplex opt ion a nd the5

size (in bits) of th e Physical Layer SDU for the cu rren t SCH as sign men t. For Mu xPDU6

Type 1 an d a Ph ysical Layer SDU size of 172 bits, th e mu ltiplex option in u se is 0x3.7

For MuxPDU Type 2 a nd a Physical Layer SDU s ize of 267 bits, th e mu ltiplex option in8

u se is 0x4. For all other com bina tion s of Physical Layer SDU size an d MuxPDU Type in9

Tab le 2-7, th e mu ltiplex option in u se is specified by th e colu mn in Tab le 2-7 cont aining10

th e configu red m u ltiplex option an d th e row in Tab le 2-7 corresp ond ing to the size (in11

bits) of th e Physical Layer SDU for th e cu rren t SCH ra te.12

Table 2-8 descr ibes the Mu xPDU Types tha t a re su pported for each Physical Chan nel .13

Table 2-8 . Supp or t ed MuxPDU Types for Each Phys ica l Chan ne l Type14

Phys ica l Chan ne l Supp or t ed MuxPDU Types

FCH 1, 2, 4, an d 6

DCCH 1, 2, 4, an d 6SCCH 1 and 2

SCH 1, 2, 3, an d 5

15

For multiplex options greater than 0x10, Table 2-9 describes the fields used to compute16

the m u lt iplex opt ion n um ber .17


32/132


2-10

Tab le 2 -9 . F i e ld s Us ed t o Com pu t e Mul t i p lex Op t i on Num ber s Gr ea t e r t han 0x101

Fie ld Nam e Num ber of Bi ts Value

Rate_Set 200 Not Applicable

01 Rat e S et 1

10 Rat e S et 2

Least

Significant

Bit

Max_Data_Blocks 6 600 00 00 No rest riction00 00 01 00 10 00

Data_Block_Size 2

00 Sin gle s ize

01 Dou b le size

11 Variable size

MuxPDU_Type 2

00 Mu xPDU Types 1, 2, or 4

10 MuxPDU Typ e 3

01 MuxPDU Typ e 6

11 MuxPDU Typ e 5

Forma t_Descriptor 4 000 0 Forma t 1

Most

Significant

Bit

2

Th e receiving fu nct ion accepts a Physical Layer SDU, d ivides it in to one or more3

MuxPDUs, demultiplexes the data blocks in each MuxPDU and delivers the information4

bits to the appropriate service.5

Th e informa tion bits in a signalin g data block a re a lso called signa ling tra ffic.6

2 .2 .1 .1 .1 .1 Mob il e S t a t i on Suppor t7

If the mobile s ta t ion s u pports Rad io Configurat ion 1, it s ha ll sup port th e FCH, and the8

mobile station shall support Mode A on the FCH.9

If the m obile s tat ion su pports a Radio Configurat ion with a n u mber greater th an 2, an d10

if the mobile station supports a voice service option, the mobile station shall support11

the FCH, an d th e mobile s tat ion s ha ll support Mode B on th e FCH.12

Th e mobile sta tion ma y su pport Mode B on th e FCH, DCCH, or SCH. If th e mobile13

stat ion su pports a Radio Configurat ion with a n u mber greater th an 2, an d i f the m obile14

stat ion su pports th e FCH, the m obile s tat ion sh al l su pport Mode B on th e FCH.15

The mobile s ta t ion s ha ll sup port mu lt iplex opt ion 0x1 an d Rate S et 1.16

Th e mobile sta tion s h all su pport s igna lin g traffic an d s ha ll sup port Prima ry Traffic.17

The m obile s tat ion sh al l su pport th ose Mu xPDU Type 1 s t ru ctures tha t contain18

signaling tra ffic only, pr imary t raffic on ly, or b oth signalin g an d p rimar y tra ffic.19

The mobile station may support multiplex option 0x2 and Rate Set 2. If the mobile20

stat ion su pports m u lt iplex opt ion 0 x2 an d Rate Set 2, i t sha ll support th ose Mu xPDU21

Type 2 str u ctu res t ha t conta in signalin g traffic only, primary tra ffic only, or both22

signaling an d pr imar y traffic.23

Th e mobile sta tion ma y su pport second ary tra ffic. If i t su pport s s econda ry traffic, i t24

sh al l su pport th ose Mu xPDU Type 1 s t ru ctures tha t contain secondary t raffic . If the25

mobile s tat ion s up ports s econda ry t raffic , mu lt iplex opt ion 0 x2, an d Rate Set 2, th e26

mobile s tat ion sh al l a lso sup port th ose MuxPDU Type 2 s t ru ctures tha t contain27

second ary tra ffic.28

6 Specifies th e ma ximu m n u mb er of MuxPDUs to be inclu ded in a single Physical Layer

SDU.


33/132


2-11

The mobile station may support one or more of multiplex options 0x3, 0x5, 0x7, 0x9,1

0xb, 0xd, a n d 0xf, in t he forward direction, or in t he r everse direction, or in b oth2

directions.3

The mobile station may support one or more of multiplex options 0x4, 0x6, 0x8, 0xa,4

0xc, 0xe, and 0x10, in the forward direction, or in the reverse direction, or in both5

directions.6

The mobile s tat ion m ay su pport one or m ore of mu lt iplex opt ions 0x704, 0x809, 0x811,7

0x821, 0x905, 0x909 , 0x911, 0x921, a nd 0xf20 in th e forward direct ion, or in th e8

reverse direction, or in both directions. If the mobile station supports any of these9

mu ltiplex options , it sh all also su pport Mode B.10

The mobile s tat ion m ay su pport one or m ore of mu lt iplex opt ions 0x704, 0x80a, 0x812,11

0x822, 0x906, 0x90a , 0x912, 0x922, a nd 0xf20 in th e forward direct ion, or in th e12

reverse direction, or in both directions. If the mobile station supports any of these13

mu ltiplex options , it sh all also su pport Mode B.14

The mobile station may support MuxPDU Type 4.15

2 .2 .1 .1 .1 .2 Se r v ice P r i or i t y16

Th e mu ltiplex su blayer ma y determine t he r elative priority between tr affic su pplied by17

Signal ing an d other services u sing the information provided by th e para meters in th e18

MAC-SDUReady.Reques t () primitive. The exact m an ner for u sing th is informa tion to19

deliver over-the-a ir Qua lity of Service is not sp ecified b y th is sta nd ard .20

2 .2 .1 .1 .1 .3 Mul t i p lex Sub laye r T r ans m i t t i ng Fun c t i on21

2.2 .1 .1 .1 .3 .1 Assem bl ing th e Phys ica l Layer FCH SDU22

2 .2 .1 .1 .1 .3 .1 .1 Mode A23

If an FCH physical chan nel has been a ssigned, th e mu lt iplex sub layer sha ll assemb le a24

Physical Layer FCH SDU every 20 ms . The mu ltiplex sub layer s ha ll combine a vailable25 da ta b locks from signaling and all conn ected services, a ccording to the relative priority26

of each , to form a MuxPDU.27

If the FCH ph ysical chan nel is u sed with Rate Set 1, th e mu lt iplex su blayer sh al l u se28

the supplied data blocks to form a MuxPDU Type 1, as specified in 2.2.1.1.1.5.29


the supplied data blocks to form a MuxPDU Type 2, as specified in 2.2.1.1.1.5.31

If signaling and all services supply Blank data blocks, the multiplex sublayer shall32

create a nu ll tra ffic Mu xPDU. A nu ll tra ffic Mu xPDU con tains only the lowest n egotiated33

tra n sm it rate p rimar y traffic data block with a ll bits set to 1.34

Th e mu ltiplex su blayer sh all deliver the a ss emb led Ph ysical Layer SDU to the Ph ysical35

Layer u sing th e PHY-FCH.Requ est service interface pr imitive in accorda nce with36 2.2.1.1.1.7.1.37

2 .2 .1 .1 .1 .3 .1 .2 Mode B38

If an FCH physical chan nel has been a ssigned, th e mu lt iplex sub layer sha ll assemb le a39

Physical Layer FCH SDU at th e begin nin g of every 20 m s interval. The m u ltiplex40

su blayer sha ll not as semble a 20 m s FCH SDU at an y t ime other th an the beginn ing of 41

a 20 ms interval. The m u ltiplex su blayer ma y form a MuxPDU Type 4 every 5 ms .42


34/132


2-12

To ass emb le a Ph ysical Layer FCH SDU, the m u ltiplex su blayer sh all combine a vailable1

data blocks from signaling and all FCH-mapped logical channels 7, according to th e2

relative priority of each, to form a MuxPDU.3

If s igna ling su ppl ies a 5 m s da ta b lock a t th e beginn ing of a 2 0 m s interval, th e4

mu ltiplex su blayer sh all perform th e followin g:5

If the m u lt iplex sublayer does not a ssem ble a 20 ms FCH SDU in th e sam e 20 m s6

interval, the multiplex sublayer shall require all other FCH-mapped logical channels7

to su pply a Blank data block. The m u lt iplex su blayer sh al l us e the s u ppl ied 5 m s8

dat a block to form a MuxPDU Type 4, as specified in 2.2.1 .1.1.5 . Th e mu ltiplex9

su blayer sh all form a MuxPDU Type 4 or Null MuxPDU every 5 ms th ereafter un til10

the beginning of the next 20 ms interval .11

If the m u lt iplex sublayer assemb les a 20 ms FCH SDU in t he sa me 20 ms interval,12 the m u lt iplex su blayer sh al l u se th e su ppl ied 5 m s da ta b lock to form a Mu xPDU13

Type 4, as s pecified in 2.2.1.1.1.5, a nd also assemb le a 20 ms FCH SDU in the14

sam e 20 ms interval.15

If s igna ling su ppl ies a 5 ms data block at a ny t ime other tha n th e beginn ing of a 20 ms16

interval, th e mu lt iplex su blayer sh al l us e the s u ppl ied 5 m s da ta b lock to form a17

MuxPDU Type 4, as specified in 2 .2.1.1 .1.5.18

After an y FCH-mapp ed logical cha nn el su ppl ies a non -Blan k 20 ms data block, the19

mu lt iplex sub layer sha ll not accept a 5 m s d ata block for the Mu xPDU being as sembled.20


th e su pplied da ta blocks to form a MuxPDU Type 1 or Type 6, a s s pecified in22

2.2.1.1.1.5.23


th e su pplied da ta blocks to form a MuxPDU Type 2 or Type 6, a s s pecified in25

2.2.1.1.1.5.26

If, at th e begin nin g of a 2 0 m s interval, signalin g and all FCH-ma pped logical cha n nels27

su pply Blan k dat a blocks , the mu ltiplex su blayer sha ll create a n u ll tra ffic MuxPDU. A28

nu ll tra ffic MuxPDU cont ains only the lowest n egotiated tra ns mit ra te prima ry traffic29 da ta block with all bits s et to 1.30

Th e mu ltiplex su blayer sh all deliver the a ss emb led Ph ysical Layer FCH SDU or SDUs to31

th e Physical Layer u sing th e PHY-FCH.Requ est s ervice interface primitive in accorda nce32

with 2.2.1.1.1.7.1.33

2.2 .1 .1 .1 .3 .2 Assem bl ing th e Phys ica l Layer DCCH SDU34

2 .2 .1 .1 .1 .3 .2 .1 Mode B35

If a DCCH ph ysical cha nn el ha s b een as signed, th e mu lt iplex sub layer sha ll assemble a36

Physical Layer DCCH SDU at th e beginn ing of every 20 m s interval. Th e mu ltiplex37

su blayer sha ll not as semble a 20 m s DCCH SDU at an y t ime other th an the beginn ing38 of a 20 ms interval. Th e mu ltiplex su blayer ma y form a MuxPDU Type 4 every 5 ms .39

7 The Logical-to-Physical Mapping Table specifies the mapping of logical channels to

physical channels .


35/132


2-13

To assemble a physical layer DCCH SDU, the multiplex sublayer shall perform the1

followin g:2

If PILOT_GATING_USE_RATE is equ al t o 0, t h en th e m u ltiplex s u blayer sh all3 combine a vailable da ta blocks from s igna lin g an d a ll DCCH-mapp ed logical4

cha n nels, a ccording to the r elative priority of each , to form a MuxPDU.5

Oth erwise, if PILOT_GATING_USE_RATE is n ot equ al t o 0, t h en th e m u ltiplex6

su blayer sh all form a MuxPDU from th e available dat a block from s ign alin g.7

If s igna ling su ppl ies a 5 m s da ta b lock a t th e beginn ing of a 2 0 m s interval, th e8

mu ltiplex su blayer sh all perform th e followin g:9

If the m u lt iplex sublayer does not a ssem ble a 20 ms DCCH SDU in th e sam e 20 m s10 interval, the m u ltiplex su blayer sh all requ ire all oth er DCCH-map ped logical11

chan nels to sup ply a Blank da ta block. The m u lt iplex sub layer sha ll use th e12

su pplied 5 ms dat a block to form a Mu xPDU Type 4, as specified in 2.2.1.1 .1.5. The13

mu ltiplex sub layer sh all form a MuxPDU Type 4 or Nu ll MuxPDU every 5 m s14

thereaf ter u nt i l the beginn ing of the next 20 ms interval .15

If the m u lt iplex sub layer assem bles a 20 m s DCCH SDU in the s am e 20 m s interval,16

the m u lt iplex su blayer sh al l u se th e su ppl ied 5 m s da ta b lock to form a Mu xPDU17 Type 4, as s pecified in 2.2.1.1.1.5, a nd also assemb le a 2 0 m s DCCH SDU in the18

sam e 20 ms interval.19

If s igna ling su ppl ies a 5 ms data block at a ny t ime other tha n th e beginn ing of a 20 ms20

interval, th e mu lt iplex su blayer sh al l us e the s u ppl ied 5 m s da ta b lock to form a21

MuxPDU Type 4, a ccordin g to Table 2-22.22

After an y DCCH-mapped logical chan nel su ppl ies a non -Blan k 20 ms data block, th e23

mu lt iplex sub layer sha ll not accept a 5 m s d ata block for the Mu xPDU being as sembled.24

If the DCCH ph ysical cha nn el is u sed with Rate Set 1, th e mu lt iplex su blayer sh al l u se25

th e su pplied da ta b locks to form a MuxPDU Type 1 or Type 6 as specified in 2.2 .1.1.1 .5.26

If the DCCH ph ysical cha nn el is u sed with Rate Set 2, th e mu lt iplex su blayer sh al l u se27

th e su pplied da ta b locks to form a MuxPDU Type 2 or Type 6 as specified in 2.2 .1.1.1 .5.28

If, at the beginning of a 20 ms interval, signaling supplies a Blank data block, and all29

other DCCH-ma pped logical chan nels su pply either a Blan k da ta block or an idle30

category data block,8 th e mu ltiplex su blayer sh all create a Null MuxPDU.31

Th e mu ltiplex su blayer sh all deliver the a ss emb led Ph ysical Layer DCCH SDU or SDUs32

to th e Ph ysical Layer u sing th e PHY-DCCH.Requ est service interface pr imitive in33

accordance with 2.2.1.1.1.7.2.34

2.2 .1 .1 .1 .3 .3 Assem bl ing th e Phys ica l Layer SCCH SDU35

2 .2 .1 .1 .1 .3 .3 .1 Mode A36

For each SCCH physical cha nn el tha t ha s been a ssigned, th e mu lt iplex sub layer shal l37 as sem ble a Physical Layer SCCH SDU every 20 m s. The m u ltiplex su blayer sh all form a38

MuxPDU using a single data block from a connected service, requesting the data block39

from each conn ected s ervice in order of the r elative priority of each conn ected ser vice.40

If all connected services supply Blank data blocks, the multiplex sublayer shall create a41

Null MuxPDU.42

8 A da ta s ervice option m ay ind icate a d ata blocks category when it su pplies th e data

block to the multiplex sublayer.


36/132


2-14

If a connected service supplies a non-Blank data block and if the SCCH is used with1

Rate Set 1, th e mu lt iplex su blayer sh al l us e the s u ppl ied data block to form a MuxPDU2

Type 1, as specified in 2.2 .1.1.1 .5.3

If a connected service supplies a non-Blank data block and if the SCCH is used with4

Rate Set 2, th e mu lt iplex su blayer sh al l us e the s u ppl ied data block to form a MuxPDU5

Type 2, as specified in 2.2 .1.1.1 .5.6

Th e mu ltiplex su blayer sh all deliver the a ss emb led Ph ysical Layer SCCH SDU to the7

Physical Layer u sing th e PHY-SCCH.Requ est s ervice interface primitive in accorda n ce8

with 2.2.1.1.1.7.3.9

2.2 .1 .1 .1 .3 .3 .2 Procedu res for Addin g an d Dropping R-SCCHs10

Whenever the Multiplex Sublayer is delivering MuxPDUs of Type 1 or 2 for i R-SCCHs,11

the Multiplex Sublayer shall deliver a MuxPDU of Type 1 or 2 for each R-SCCH with12

code chan nel ind ices 1 to i. If th e Mu ltiplex Su blayer reduces th e nu mb er of R-SCCHs13

on wh ich it is delivering Mu xPDUs of Type 1 or 2 (e.g., du e to tra n sm itter power14

l im itation s, lack of da ta t o tran sm it, or when fewer R-SCCHs a re allocated), th e15

Multiplex Sub layer sh all discon tinu e deliverin g Mu xPDUs of Type 1 or 2 to th e Physical16

Layer for R-SCCHs with th e highest code ch an nel ind ices first .17

If REV_DTX_DURATIONs is not equ al to 111 1 an d th e Multiplex Sublayer st ops18

delivering MuxPDUs of Type 1 or 2 to the Physical Layer for an R-SCCH for a period of19

time longer than REV_DTX_DURATIONs 20 m s, th en th e Mu lt iplex Sublayer sha l l not20

resu me d elivering Mu xPDUs of Type 1 or 2 to th e Physical Layer for th at R-SCCH u nt il21

th at R-SCCH is re-allocated. Similarly, if th e Mu ltiplex Su blayer incr eas es th e nu mb er22

of MuxPDUs of Type 1 or 2 tha t are s ent t o the Physical Layer for R-SCCHs th at a re in23

use from j to j + 1 (e .g. , du e to resum ption of t ran sm ission when discont inu ous24

transmission is permitted, or when additional R-SCCHs are allocated), the Multiplex25

Su blayer sh all begin to d eliver MuxPDUs of Type 1 or 2 for a n R-SCCH with code26

channel index j + 1 before delivering MuxPDUs of Type 1 or 2 for code channels with27

any larger index.28

2 .2 .1 .1 .1 .3 .3 .3 P r ocedur e s fo r t h e R-SCCH Tr ans m i s s ion P r eam ble29

Whenever th e Multiplex Sub layer b egins to deliver Mu xPDUs of Type 1 or 2 to th e30

Physical Layer for an R-SCCH following one or more Null MuxPDUs for the first time31

after th e allocation of th e R-SCCH, the Multiplex Su blayer sh all sen d a PHY-32

SCCHPreamble.Request (num_preamble_frames ) to th e Ph ysical Layer with33

num_preamble_frames set to BEGIN_PREAMBLEs .34

2 .2 .1 .1 .1 .3 .3 .4 P r ocedur e s fo r t h e R-SCCH Dis con t i nuous Tr ans m i s s ion35

Pr eam bl e36

If the cu rrent ly conn ected service opt ion p ermits discont inu ous R-SCCH tran sm ission,37

th en th e Mu ltiplex Su blayer ma y resu me d elivering Mu xPDUs of Type 1 or 2 to th e38

Physical Layer for an R-SCCH following one or more Null MuxPDUs for that R-SCCH.39 When th e Multiplex Sub layer res u mes delivering Mu xPDUs of Type 1 or 2 for an40

R-SCCH, the Multiplex Sublayer shall indicate to the Physical Layer that the41

Discont inuou s Trans mission p reamb le is to be t ran sm it ted on th e R-SCCH by send ing a42

PHY- SCCHPream ble.Reques t (num_preamble_frames )to th e Ph ysical Layer with43

num_preamble_frames set to RESUME_PREAMBLEs . The Multiplex Su blayer sh all n ot44

ind icate tha t the Su pplemental Code Chan nel Discont inu ous Tran smission p reamb le is45

to be tra n sm itted by the Ph ysical Layer when th e Mu ltiplex Su blayer begins to deliver46

MuxPDUs of Type 1 or 2 for an R-SCCH, following the allocation of that R-SCCH.47


37/132


2-15

2.2 .1 .1 .1 .3 .4 Assem bl ing th e Phys ica l Layer SCH SDU1

2 .2 .1 .1 .1 .3 .4 .1 Mode B2

For each SCH tha t ha s been ass igned, the m u lt iplex su blayer sh al l ass emble a Physical3

Layer SCH SDU every 20 m s, every 40 ms , or every 80 m s a ccording to the SCH fram e4

length configured . The mu ltiplex su blayer sha ll form each Mu xPDU u sing a single data5

block from an SCH-mapped logical channel. The multiplex sublayer shall request data6 blocks from th e SCH-ma pped logical cha nn els, a ccordin g to the relative priority of each7

logical chan nel , un t il enou gh da ta b locks ha ve been s up pl ied to form th e nu mb er of 8

MuxPDUs need ed to fill the SCH SDU, or a ll SCH-ma pped logical cha nn els h ave9

su pplied all availab le da ta blocks. The m u ltiplex su blayer sha ll indicate the m u ltiplex10

opt ion in us e and the SCH rate when i t requests d ata b locks from th e SCH-ma pped11

logical cha nn els.12

If all SCH-mapped logical channels supply a Blank data block, the multiplex sublayer13

sh all create a single Null MuxPDU an d s h all consider a ss emb ly of th is Ph ysical Layer14

SCH SDU completed.15

If the SCH multiplex option in use is 0x3, the multiplex sublayer shall use the supplied16

non-Blank data block to form a MuxPDU Type 1, as specified in 2.2.1.1.1.5.17

If the SCH multiplex option in use is 0x4, the multiplex sublayer shall use the supplied18

non-Blank data block to form a MuxPDU Type 2, as specified in 2.2.1.1.1.5.19

If the SCH mu lt iplex opt ion in us e is 0x809, 0x80a, 0x811, 0x812, 0x821, 0x822,20

0x905, 0x906, 0x909, 0x90a, 0x911, 0 x912, 0x921, or 0x922, th e mu lt iplex su blayer21

sh all u se each su pplied non -Blan k dat a block to form a MuxPDU Type 3. If th e SCH22

mu lt iplex opt ion in u se is 0xf20, th e mu lt iplex su blayer sh al l us e each su ppl ied n on-23

Blan k da ta block to form a MuxPDU Type 5. Th e mu ltiplex su blayer sha ll form th ese24

MuxPDUs as specified in 2.2.1.1.1.5.25

If th e Physical Layer u ses con volutional coding for th e SCH du ring tran sm ission of the26

Physical Layer frame conta ining th e SDU, an d if an y of th e followin g conditions is tru e,27

the multiplex sublayer shall assemble the Physical Layer SCH SDU using LTUs,28

according to 2.2.1.1.1.3.4.1.1:29

the SCH m u lt iplex opt ion in u se is 0x809, 0x80a, 0x811, 0x812, 0x821, 0x822,30 0x905, 0x906, 0x909, 0x90a, 0 x911, 0x912, 0x921, or 0x922 an d Table 2-1031

indicates a non -zero nu mber of LTUs in th e SDU correspond ing to the n u mber of 32

bits per SDU for the multiplex option in use;33

th e SCH mu ltiplex option in u se is 0xf20, a nd th ere is no ent ry in th e LTU Tab le34 correspond ing to th e nu mber of bi ts in the Ph ysical Layer SDU for the curren t35

su pplemental chan nel assignm ent , an d th e nu mber of bi ts in th e Physical Layer36

SDU for the curren t su pplemental chan nel assignm ent h as a correspond ing entry in37

Table 2-10 with a non -zero nu mb er of LTUs in th e SDU; or38

the SCH multiplex option in use is 0xf20 and there is an entry in the LTU Table39 entry corresponding to the n u mber of bi ts in the Physical Layer SDU for th e curr ent40 su pplemental chan nel ass ignmen t a nd the LTU size in th e corresponding LTU Table41

entry is non-zero.42

Otherwise, the multiplex sublayer shall insert the MuxPDUs serially into the Physical43

Layer SCH SDU. If the n u mber of ins er ted MuxPDUs is less th an the n u mber of 44

MuxPDUs required by the multiplex option for the SCH then the multiplex sublayer45

sh all insert on e Fill Mu xPDU conta ining a da ta b lock of th e size in dicated by th e46

mu ltiplex option as sociated with th e SCH, fil led with 0 bits. The mu ltiplex su blayer47

sh all fi ll an y rema ining spa ce in th e SCH SDU with 0 bits.48


38/132


2-16

Th e mu ltiplex su blayer sh all deliver the a ss emb led Ph ysical Layer SCH SDU to th e1

Physical Layer u sing th e PHY-SCH.Request service interface primitive in a ccordan ce2

with 2.2.1.1.1.7.4.3


39/132


2-17

2.2 .1 .1 .1 .3 .4 .1 .1 LTU Assem bly1

Th e mu ltiplex su blayer sh all comb ine Type 3 MuxPDUs into LTUs a ccording to Tab le2

2-10. Each LTU sha ll contain a 16-bi t CRC an d either 2 Mu xPDUs tha t contain a s ingle3

size non -Blan k da ta b lock or 1 MuxPDU that contains a double s ize non -Blan k da ta4

block. Th e size of each LTU tha t conta ins Type 3 MuxPDUs is 36 8 bits.5

Th e mu ltiplex su blayer sh all comb ine Type 5 MuxPDUs into LTUs of a size tha t is6

determ ined a s follows:7

If there is no entry in the LTU Table corresponding to the number of bits in the8 Physical Layer SDU for the curr ent su pplemental chan nel assignm ent , th e nu mber9

of bits in each LTU is determ ined a s follows:10

LTU Size = ((SDU length in bits ) / 8) / l 8 bits11

where l is the number of LTUs in the SDU in the entry in Table 2-1012

corresponding to the number of bits in the Physical Layer SDU for the13

cur rent s upplementa l chan nel ass ignm ent .14

Oth erwise, th e LTU size in bits is deter mined by th e LTU Tab le ent ry correspon ding15 to the cur rent s upp lementa l chan nel ass ignm ent .16

Each LTU sha ll contain a 16-bi t CRC and at least 1 MuxPDU that contains a n on-Blan k17

data block.18

If th ere a re n ot enou gh s u pplied Mu xPDUs t o fill every LTU in th e Physical Layer SCH19

SDU, the m u ltiplex su blayer sh all insert enou gh Fill Mu xPDUs into ea ch LTU tha t is20

not fu ll, in order to fi ll the LTU. If th e SCH m u ltiplex option in u se is 0 x809, 0x80a ,21

0x811, 0x812, 0x821, 0x822, 0x905, 0x906, 0 x909, 0x90a, 0x911, 0x912, 0x921, or22

0x9 22 , each Fill Mu xPDU sh all con ta in a d at a b lock filled with 0 bits , of th e size23

indicated by th e mu ltiplex option as sociated with th e SCH. If th e SCH mu ltiplex option24

in u se is 0 xf20 , each Fill Mu xPDU sh all conta in a d at a b lock filled with 0 bits, of the25

size needed t o fill the LTU. Th e m u ltiplex su blayer sh all calcu late a 16-bit CRC on a ll26

bits in th e LTU, except th e CRC, and sh all insert th e CRC following th e MuxPDUs in th e27

LTU. The CRC shall be calculated using the procedure used to calculate the 16-bit SCH28

fram e qua lity in dicator. Th e mu ltiplex su blayer sh all insert t h e LTUs ser ially into th e29

Physical Layer SCH SDU a n d s h all fi ll any rem aining s pace in th e Physical Layer SCH30

SDU with 0 bits.31

7/29/2019 TIA/EIAINT