| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi, Kaushik, Soojung, and all, Thanks for sharing these. I think it is not suitable to allocate a group ID in MAC with network unique feature. MAC layer is limited in cell level, and if a MS move to other cells there is handover procedure to re-allocate a new ID. In a cell level, there is broadcast and multicast process and group resource allocation already. So, I would prefer to discuss it more sufficient in the group before we put it to the AWD text. BR/Bin From: Kaushik Josiam [mailto:kjosiam@STA.SAMSUNG.COM] Thanks Soojung for sharing your opinion on the need for a group ID. I request other members to input their comments on this issue. Dear 16p members, Since we didn’t hear any objections from members for having a group ID in the conference call, would it be reasonable for us to add the following text to the addressing section 16.2.1.2.9 M2M device Group Identifier (MGID)A [TBD] bit value that is used to identify an M2M group which an M2M device belong to. It is unique in the domain of the entire network. A MGID is assigned by the network during initial network entry. What we are proposing to do is to create a new subsection for group identifier and add this description there. We welcome member’s comments on the text above. You can add your comments to the text as a reponse to this email. If you are opposed to creating a group ID, please don’t hesitate to state your objection. Regards Kaushik & Ming-Hung Dev RG Chairs From: 정수정 [mailto:sjjung@etri.re.kr] Dear 16p members, ETRI's opinion about group ID is as follows; M2M devices for the same service application (e.g. metering, tracking ) can share one or more features in common. In other words, due to the nature of M2M application, the M2M device within the same service application may have the same traffic pattern. In order to provide the same service application, the same control messages or the data traffic may be required for the M2M devices at the same time. In this case, individual transmission of the same data to mass M2M devices can cause huge overhead. By grouping the M2M devices that have same features, the 16p system can support efficient management. And the group control(e.g. group paging) and traffic (e.g. multicast transmission) may be needed to M2M devices in idle state as well as in connected state. therefore. We think that a group ID is necessary. And a group ID is network specific ID and is associated with subscriber. A network specific group ID which is associated with subscriber has benefits as following . Regards, Soojung jung --------------------------------------------------- Soojung Jung Senior Member Mobile Telecommunications Research Division Electronics and Telecommunications Research Institute(ETRI) Tel: +82-42-860-5928 Fax: +82-42-861-1966 ---------------------------------------------------
Dear 16p members, Two contributions C0006 and C0012 defined the concept of a group ID addressing different applications. Please respond to this email thread to voice your thoughts. In particular, we are looking for your inputs on the following: 1. Is a Group ID necessary to be defined for M2M devices? 2. What applications would use a group ID? 3. What are the characteristics of a group ID? (For ex: is it a network specific ID?) 4. What is the size of the proposed group ID? If you have any other thoughts, proposals or questions, please respond to this thread. Regards Kaushik & Ming-Hung DEV RG Chairs |