Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-16] regarding service flow in 802.16



Title:
Hi,
 
It depends on the implementation of MAC_packet_CS.
 
For example, the stream is: IPv4->UDP->RTP
 
1. Classifier:
Source Address + Destination Address +   Protocol + Type of Service
If any packet matches the classifier,  the packet can be classified to the
SF and CID. But if Source  Port  or Destination Port is different, the MAC_packet_CS
can apply a DSC_REQ to request a Qos change.
 
 
2. Classifier:
Source Address + Destination Address +   Protocol + Type of Service
Source  Port   + Destination Port 

3. Classifier:
Source Address + Destination Address +   Protocol + Type of Service +
Source  Port   + Destination Port +
synchronization source (SSRC) identifier + contributing source (CSRC) identifiers
In the case, each session can apply a SFID and CID. It is rather tricky.
 
----- Original Message -----
Sent: Tuesday, August 29, 2006 10:25 PM
Subject: [STDS-802-16] regarding service flow in 802.16

hi all,

I had read in some doc as stating below

"An 802.16 system should not be forced to open a different CID for each upper layer protocol if packets for upper layer protocols have the same QoS requirements (802.16 scheduling service types)"

So it means if a SS has multiple RTPS connection with same Qos parameters then is it all RTPS connections have same transport CID and SFID??



Plz clear my doubt???

Thanks in advance
subodh kumar