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 .
it doesn't require an additional update procedure because it is unique identifier within the network.
In regard to multicast transmission, it can be used to send DL multicast data to a group of M2M devices in a specific BS without ID change when the service BS is changed.
Also, even though the same group ID is given to mass M2M devices, it is possible to page some M2M devices within a specific paging group by using the network specific group ID and a specific paging group ID.
---------------------------------------------------
Soojung Jung
Senior Member
Mobile Telecommunications Research Division
Electronics and Telecommunications Research Institute(ETRI)
Tel: +82-42-860-5928 Fax: +82-42-861-1966
---------------------------------------------------
-----원본 메시지-----
From: "Kaushik Josiam" <kjosiam@STA.SAMSUNG.COM>
From Date: 2011-02-10 오전 5:29:23
To: "STDS-802-16@LISTSERV.IEEE.ORG" <STDS-802-16@LISTSERV.IEEE.ORG>
Cc:
Subject: [STDS-802-16] [802.16p][DEV RG] Group ID to support different applications
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