3gpp2 tsg-p title: bcmcs adhoc Meeting Summary

Jun Wang

Qualcomm Inc

858-658-4884

1. 
   Some discussions on the terms of references of the Adhoc. Should the Adhoc focus on the technical discussions and try to reach a consensus on the common approach for BCMCS architectures, stage 2 and stage 3 or should the Adhoc only focus on the TSG-P BCMCS requirements? No consensus is made.
   
2. 
   Several members expressed that the Adhoc group should work on the Broadcast/Multicast service requirements relevant to TSG-P before further looking into architecture framework.
   
3. 
   Samsung presented their contribution (P00-BCMCS-20020522-001) to suggest that Broadcast/Multicast should be moved from D3 work items to post Release D work items because TSG-C will work on the 1XEV-DV addendum with Release D and it may slow down the new business such as BCMCS. SAMSUNG also proposed in this contribution that Adhoc group should work on BCMCS technical requirement on TSG-P perspective, and make recommendation to TSG-A/C. The suggestion is supported by Nokia and Cisco. Some companies felt that the BCMCS schedule needs to be addressed by TSG-P because of lack of service providers’ input in this Adhoc and the recommendation to TSG-A/C on BCMCS requirements may be beyond of the scope of TGS-P. The issues are left open.
   
4. 
   Qualcomm proposed the phased approach for BCMCS service. The issue is left open.
   
5. 
   The group agreed the following process rule so that progress can be made smoothly: if only one company has objection, the issue will be move forward regardless the objection. If two or more companies have objections, the issue will remain open for further study.
   
6. 
   Nokia presented their contribution on BCMCS design goals and system requirements (see P00-BCMCS-20020522-002):
   
   • 
     Section 2: Regarding on the requirements for support of receiver heterogeneity, spectrum efficiency radio transmissions, and the rate control by the base station, some companies felt that the requirements are not feasible to implement and should be debated in TSG-C or TSG-A. There is no consensus.
     
   • 
     Section3: The group has reviewed system requirements up to number 6 under section 3.1. Numbers 1 and 4 are agreed by the group. Numbers 2 and 5 are agreed with modifications. Numbers 3 and 6 remain open. Please see following for more detail.
     
   • 
     The following System Requirements are agreed by the group:
     

1. 
   For IPv4, the end-to-end solution is using Class-D IP Multicast addresses. IP broadcast addresses should not be used for the multicast/broadcast services.
   
2. 
   A mapping between radio connections and IP Multi­cast­ing flows identifier shall be defined.
   
3. 
   A standard multicast routing protocol shall be used for the IP related part of the architecture.
   
4. 
   Header Compression may be support in the MS and the system.
   

• 
  Open issues:
  

1. 
   Should BCMCS design also apply for IPv6?
   
2. 
   The following System Requirements remain open:
   

• 
  Depending on the number of content subscribers, it should be possible for the system to transmit between broadcast and non-broadcast radio channel.
  
• 
  There shall be a way to configure an “always present” kind of service, i.e. a service similar to the TV broadcast service.
  

The group agreed that another BCMCS Adhoc will be held at June 5, 2002, 5:30PM to 7:30PM (CT). The meeting bridge will be provided by the chair before the conference call.

7. 
   The group agreed to only include TSG-P requirements/working assumptions in BCMCS Adhoc Agenda.
   
8. 
   The group agreed to meet face in face in Shenzhen to finish the work regarding on TSG-P BCMCS requirements and design goals if TSG-P allocates the time to the Adhoc. After that, the Adhoc will seek the guideline from TSG-P on how to proceed in the next step (whether to continuously work on stage 2 and stage 3).
   
9. 
   Some discussions on how mapping between the different standards over the different interfaces. The following table gives the mapping.
   

10. 
    The group will decide whether to send a liaison to TSG-S and other TSGs after the work on TSG-P requirements is finished.
    
11. 
    Nokia continuously presented their contribution on BCMCS design goals and system requirements (see P00-BCMCS-20020522-002):
    
    • 
      Section 2: Regarding on the requirements for support of receiver heterogeneity, spectrum-effeiciency readio transmission, and the rate control by the base station, some companies felt that the requirements are not feasible to implement and should be debated in TSG-C or TSG-A. There is no concensus.
      
    • 
      Section 3.1: The group has finished to review system requirements on this section. Number 7 is agreed with the modifications. Numbers 8, 9, 10, and 12 are not needed (Number 8 is already included in BCMCS stage 1 requirements; Number 9 is common sense; Number 10 is not correct requirement; Number 12 will be included in Number 11 with the modifications). Number 11 (with the modifications) remains open and waits to see whether it will be added in the TSG-S stage 1 requirement. Please see following for more detail.
      
    • 
      The following System Requirement is agreed by the group:
      

• 
  The different multicast IP flows shall be supported and identified by the different multicast IP addresses and port numbers.
  

• 
  The following System Requirement remains open:
  

• 
  The subscriber shall be able to discover what broadcast and multicast services are available at the subscriber’s current location.
  

The group agreed that BCMCS Adhoc should meet face in face in Shenzhen if TSG-P schedule is permitted.