1、Ranga Reddy, US Army,June 2009,Ranga Reddy, US Army,Slide 1,New Connection Identifier Approach,IEEE P802.22 Wireless RANs Date: 2009-06-xx,Authors:,Notice: This document has been prepared to assist IEEE 802.22. It is offered as a basis for discussion and is not binding on the contributing individual
2、(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.Release: The contributor grants a free, irrevocable license to the IEEE to incorporate mater
3、ial contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs sole discretion to permit others to reproduce
4、in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.22.Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures http:/standards.ieee.org/guide
5、s/bylaws/sb-bylaws.pdf including the statement IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of
6、the standard. Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Cha
7、ir Carl R. Stevenson as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.22 Working Group. If you have questions, contact the IEEE Patent Committee Adminis
8、trator at patcomiee.org.,Ranga Reddy, US Army,June 2009,Ranga Reddy, US Army,Slide 2,Abstract,This contribution proposes a new way to treat connection identifier (CIDs) in the 802.22 MAC. The purpose of this method is to reduce overhead, optimize processing, and reduce storage requirements for maint
9、aining CPE context at both the BS and CPE.,Ranga Reddy, US Army,June 2009,Ranga Reddy, US Army,Slide 3,Current (in v2.0) CID Description(where m = max # of supported CPEs),Ranga Reddy, US Army,June 2009,Ranga Reddy, US Army,Slide 4,New Method for Treating CID,Proposal is to break up the CID into 2 e
10、ntities:Station ID (9 MSB): ID that is unique to CPE or multicast groupFlow ID (3 LSB): ID that identifies a traffic flow that is mapped to a particular Station IDThe figure below depicts this breakdown,Ranga Reddy, US Army,Station ID,Station ID is broken down as follows.Station ID space split up be
11、tween CPEs and Multicast Groups, using m, the maximum # of CPEs supported in a cell. With a 9-bit Station ID, 512 stations are possible.CPE Station ID: 0x001 mMulticast Group ID:m+1 0x200 Station ID = 0x000 (see Slide 8), well call this the Cell Station ID,June 2009,Ranga Reddy, US Army,Slide 5,Rang
12、a Reddy, US Army,Flow ID,Flow ID is 3 bits long. Its treated differently, based on whether or not the Station ID is a CPE (Unicast) Station ID or a Multicast Station ID.When Station ID is Unicast:000 = Basic Flow001 = Primary Management Flow010-110 = Unicast Transport Flows111 = Secondary Management
13、 Flow if Secondary Management connection is enable, or reserved for vendor/operator specific useWhen Station ID is Multicast:000 = Multicast Polling Flow001 = Multicast Management Flow010-110 = Multicast Transport Flow111 = Padding Flow ID, when Station ID = 0x000, otherwise reserved,June 2009,Ranga
14、 Reddy, US Army,Slide 6,Ranga Reddy, US Army,What happened to “Well Known” CIDs in Table 299?,CIDs are constructed from the Station ID + Flow IDCPE Basic CIDUnicast Station ID | Basic Flow ID (000)CPE Primary Management CIDUnicast Station ID | Primary Management Flow ID (001)CPE Transport CIDUnicast
15、 Station ID | Unicast Transport Flow ID (010-110)Multicast Polling CIDMulticast Station ID | Multicast Polling Flow ID (000)Multicast Management CIDMulticast Station ID | Multicast Management Flow ID (001)Multicast Transport CIDMulticast Station ID | Multicast Transport Flow ID (010-110),June 2009,R
16、anga Reddy, US Army,Slide 7,Ranga Reddy, US Army,What happened to “Well Known” CIDs in Table 299?(continued),Broadcast, Initial Ranging, and Padding CID are based off the “Cell Station ID” alluded to on slide 5Broadcast CID= Cell Station ID | Multicast Management Flow ID (001) = 0x001Initial Ranging
17、 CID= Cell Station ID | Multicast Polling Flow ID (000) = 0x000Padding CID= Cell Station ID | Padding Flow ID (111) = 0x007,June 2009,Ranga Reddy, US Army,Slide 8,Ranga Reddy, US Army,Why use this new approach?,The new approach is an attempt to reduce overhead and optimize use of system resources:Re
18、duce size of GMH (by 9 bits). This may not seem like much, but over many PDUs it could add up.Bursts are then identified by signaling the Station ID in the DS/US-MAP IEWere suggesting using only maximum of 5 Transport CIDs per CPE, one per service class. All SFs pertaining to (unicast/multicast) tra
19、ffic can be mapped onto one of these Flow IDs. If there is prioritization differentiation within a service class, this requires the CPE, when transmitting data to take into account is current bandwidth allocation and QoS context when deciding how to pack/fragment MAC SDUs into PDUs for transmissionT
20、he new behavior is optimized, so BSs and CPEs only have to maintain as much information about the connections. This may be useful when handling certain operations such as Timeout or performing HO (a potential future capability), as well as reducing the memory/storage/processing requirements for a CP
21、Es connections at both the CPE & BS.,June 2009,Ranga Reddy, US Army,Slide 9,Ranga Reddy, US Army,Text Proposal,If the WG decides to adopt this approach then text modification in many areas throughout the draft are required. A contribution or set of contributions with the actual text modifications wi
22、ll be brought in at a later date.:Introduce Station ID and Flow ID terms into Clause 3GMH in Table 3, Section 6.8.1.1; CID field changed to Flow ID and size reduced to 3 bitsDS-MAP IE in Table 37, Section 6.10.2.1; Remove brackets around “IF (INCLUDE_CID)” block, change CID to Station ID and change
23、size to 9 bitsRemove CID Switch Extended IE, section 6.10.2.1.2.2US-MAP IE in Table 48; change CID to Station ID and change size to 9 bitsRNG-RSP IEs in Table 59, Section 6.10.6; remove Basic CID and Primary Management CID & replace with Station IDReview MAC management messages and adjust references
24、 to CID to match Station ID or Flow ID accordinglyReview references to CID in draft and make sure they align with the new usage as defined by this contribution,June 2009,Ranga Reddy, US Army,Slide 10,Ranga Reddy, US Army,June 2009,Ranga Reddy, US Army,Slide 11,References,Hamiti, Shkumbin, “IEEE 802.16m System Description Document Draft”, IEEE 802.16m-08/003r9a, May 2009.,