CID structure for 802.16m
IEEE 802.16 Presentation Submission Template (Rev. 9)
Document Number:
IEEE S802.16m-08/787
Date Submitted:
2008-07-07
Source:
Kiseon Ryu, GeneBeck Hahn,
Youngsoo Yuk and Ronny Yongho Kim
Voice:+82-31-450-7903
LG Electronic Inc.
E-mail: {ksryu,gbhahn,sixs,ronnykim}@lge.com
LG R&D Complex, 533 Hogye-1dong,
Dongan-gu, Anyang, 431-749, Korea
*<http://standards.ieee.org/faqs/affiliationFAQ.html>
Venue:
IEEE 802.16m-08/024 - Call for Contributions on Project 802.16m System Description, specific topic "Upper MAC Addressing"
Base Contribution:
IEEE C802.16m-08/787, IEEE C802.16m-08/789
Purpose:
To be discussed and adopted by TGm for the 802.16m SDD.
Notice:
This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It represents only the views of the participants listed in
the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who 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 material contained in this contribution, and any modifications thereof, in the creation of an
IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s
sole discretion to permit others to reproduce 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.16.
Patent Policy:
The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
<http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and <http://standards.ieee.org/guides/opman/sect6.html#6.3>.
Further information is located at <http://standards.ieee.org/board/pat/pat-material.html> and <http://standards.ieee.org/board/pat >.
Contents
• CID Re-organization (C802.16m-08/787)
• ID Management for Location Privacy (C802.16m-08/789)
CID Re-organization
Background
•
Function of 16 bits CID
– In MAP
• Identification of an MS when DL/UL resource allocation by a BS
– In MAC Header
• Classification of the service flow within an MS
•
For DL allocation
– Non-HARQ case
• Primary and Transport CID can be used
– HARQ case
• Only Basic CID is used
•
For UL allocation
– Non-HARQ & HARQ case
• Only Basic CID is used
•
•
•
If HARQ is enabled, only Basic CID is used to allocate DL/UL resource with
unicast manner
Once BS allocates DL/UL resources to an MS, 4 to 6 bits are enough to
differentiate the certain MS’s service flow
Current CID should be re-organized in order to reduce the MAC overhead
Proposed scheme
•
Separation of the CID function into Resource Assignment and Service Flow
classification
– For Resource Assignment
• SCID (Scheduling CID) which is unique within a BS
• 16 bits can be used
• Basic CID can be re-used
– For Service Flow classification
• FCID (Flow CID) which is unique within an MS
• 4 – 6 bits can be used
•
Example
– A BS allocates SCID during the MS’ initial network entry procedure
– Management FCIDs are allocated during RNG-REQ/RSP message transaction
• Basic FCID and Primary FCID can be fixed
– An MS and a BS negotiate FCIDs during service flow creation
– A BS and an MS generate a MAC PDU including FCID in a MAC Header
– A BS allocates DL/UL resources with the SCID
•
Expectation
– CID overhead reduction compared to the legacy CID structure
Example of the proposed CID structure
MAC PDU
concatenation
MAC Header
(FCID)
DL-MAP
(SCID)
Payload
MAC Header
(FCID)
DL burst
DL-MAP
(SCID)
DL subframe
DL burst
DL-MAP
(SCID)
DL burst
DL-MAP
(SCID)
DL burst
Payload
MAC Header
(FCID)
Payload
Example of SCID & FCID mapping
Classification
The legacy CID
SCID (16bits)
FCID (4bits)
Random
Access ID
Ranging CID
Ranging SCID (0x00)
Fixed value (e.g. 0b0000)
Unicast ID
Basic CID
MSID
Fixed value
Primary CID
MSID
Fixed value
Or may not be defined
Transport CID
MSID
Dynamic allocation
Multicast ID
(For MBS)
Multicast CID
Multicast SCID
Dynamic allocation
Broadcast ID
Broadcast CID
Broadcast SCID (0xff)
Fixed value (e.g. 0b1111)
ID Management for Location Privacy
Problem Definition
•
The threat to location privacy is made to compromise MS
– Few ongoing works to offer strong level of user identity and location confidentiality
• Few safeguards on the location privacy although location-based services are
emerging as the future killer applications
– Attackers can find where a user is and can further use this information to track the user
• User’s communications can be easily correlated in case all communications came
from the same address and the address can be used to trace user’s movements
•
The wireless privacy protection act of 2003, currently under consideration by the
US congress proposes to amend the communications act of 1934
– “To require customer consent to the provision of wireless call location information”
•
In legacy IEEE 802.16m systems, MAC address is a globally unique value
– MAC address is treated as a means for authentication or as an identifier to grant a
varying level of network privilege to user
• Location of a user can be easily inferred from fixed MAC address
Proposed Scheme
•
IEEE 802.16m SRD
– Security function which provides the necessary means to achieve the protection and
confidentiality of user-generated and user-related data
• MS MAC address is sent from MS to BS in an unprotected way (during initial
ranging, location update and network reentry)
•
Use of temporary identifier during initial ranging
– BS allocates a new temporary identifier that can be used instead of MS MAC address
– Avoid the compromise of MS MAC address while minimizing the network overhead
incurred from the use of it
– BS shall keep the mapping of temporary identifier, MS MAC address and CID prior to the
initiation of authorization phase
•
Use of paging identifier during location update and network reentry
– Paging identifier is allocated from paging controller while MS enters into idle mode
– Avoid the compromise of MS MAC address while minimizing the network overhead
incurred from the use of it
– Paging controller keeps the mapping of paging identifier and MS MAC address
Use of Temporary Identifier during Initial Ranging
•
Lightweight procedure of temporary identifier allocation meets the requirements of
IEEE 802.16m SRD with regard to security
BS
DCD/UCD/
DL-MAP
BS
BS
SS
Binary
Exponential
Random
Backoff
SS
BS
BS
RNG-RSP
(Continue)
UL-MAP
RNG-REQ
(Code)
SS
BS
RNG-REQ
(Code)
SS
BS
RNG-RSP
(Success,
TID)
UL-MAP
RNG-REQ
(Code)
SS
SS
BS
BS
RNG-RSP
(Management
CIDs)
RNG-REQ
(TID)
SS
SS
SS
Use of Paging Identifier during Location Update
•
•
Lightweight procedure of paging identifier allocation meets the requirements of
IEEE 802.16m SRD with regard to security
If MS awakes from idle mode and performs location update, Paging ID is sent
from MS to paging controller via target BS
– Paging controller is notified of the new location of MS
– In case paging controller is changed, new paging controller tries to retrieve the location
information for MS from old paging controller (New paging ID is allocated to
corresponding MS via target BS)
– In case paging group is changed, new paging group ID is sent to MS via target BS
MS
MS
BS
DREG-REQ (code : 0x01)
Paging
Controlle
r
RNG-REQ
(Paging ID)
(IDLE mode retain IE)
Idle Mode timer
DREG-CMD (code : 0x05)
(Paging ID, IDLE mode retain IE)
Idle system timer
Paging
Controller
Target
BS
RNG-RSP
(Location Update
Response, HMAC Tuple,
New Paging ID or New
Paging Group ID)
New Location Info of
MS
Use of Paging Identifier during Network Reentry
•
If MS tries to perform network reentry, it also uses paging ID as in the case of
ranging procedure during location update
– Target BS shall retrieve MS information from paging controller when it receives a RNGREQ containing the paging ID from MS
– Target BS will know of MS MAC address corresponding to the received paging ID
Paging
Controller
Target BS
MS
RNG-REQ
(Paging ID)
MS Info Request
MS Info Response
RNG-RSP
(HO Optimization Info.for Network
Entry)
(MS MAC Address,
Paging ID Mapping Info)
Proposed SDD text
• Adopt the proposed text in the contribution C80216m-08_xxx ID
management for location privacy
• Adopt the proposed text in the contribution C80216m-08_xxx CID
re-organization