U.S. patent application number 13/994109 was filed with the patent office on 2015-09-10 for technology for triggering groups of wireless devices.
The applicant listed for this patent is Kamran Etemad, Mo-Han Fong, Puneet K. Jain. Invention is credited to Kamran Etemad, Mo-Han Fong, Puneet K. Jain.
Application Number | 20150256959 13/994109 |
Document ID | / |
Family ID | 47668759 |
Filed Date | 2015-09-10 |
United States Patent
Application |
20150256959 |
Kind Code |
A1 |
Jain; Puneet K. ; et
al. |
September 10, 2015 |
TECHNOLOGY FOR TRIGGERING GROUPS OF WIRELESS DEVICES
Abstract
Technology for triggering machine type communication (MTC)
devices is disclosed. One method comprises sending a triggering
indication from an MTC server to a plurality of MTC devices using a
cell broadcasting service. Another method comprises sending a
triggering indication from an MTC server to a plurality of MTC
devices using Paging. The triggering indication is configured to
initiate a communication between the MTC server and selected MTC
devices in the plurality of MTC devices that receive the triggering
indication. The triggering indication includes an MTC group
identification (ID) value. Only those MTC devices that belong to
the MTC group ID value in the triggering indication act on the
triggering indication.
Inventors: |
Jain; Puneet K.; (Hillsboro,
OR) ; Etemad; Kamran; (Potomac, MD) ; Fong;
Mo-Han; (Sunnyvale, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Jain; Puneet K.
Etemad; Kamran
Fong; Mo-Han |
Hillsboro
Potomac
Sunnyvale |
OR
MD
CA |
US
US
US |
|
|
Family ID: |
47668759 |
Appl. No.: |
13/994109 |
Filed: |
December 19, 2011 |
PCT Filed: |
December 19, 2011 |
PCT NO: |
PCT/US2011/065838 |
371 Date: |
April 10, 2014 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61522623 |
Aug 11, 2011 |
|
|
|
Current U.S.
Class: |
370/312 |
Current CPC
Class: |
H04W 4/06 20130101; H04N
21/64707 20130101; Y02D 30/70 20200801; H04N 21/8456 20130101; H04L
65/80 20130101; H04L 12/18 20130101; H04W 76/40 20180201; H04L
5/0037 20130101; H04W 72/005 20130101; H04W 56/00 20130101; H04L
67/02 20130101; H04W 84/042 20130101; H04L 65/1069 20130101; H04L
12/1863 20130101; H04L 65/1006 20130101; H04L 65/1016 20130101;
H04L 12/189 20130101; H04W 4/70 20180201; H04N 21/23439 20130101;
H04N 21/6131 20130101; H04L 65/105 20130101; H04W 4/08
20130101 |
International
Class: |
H04W 4/00 20060101
H04W004/00; H04W 4/08 20060101 H04W004/08; H04W 76/00 20060101
H04W076/00; H04W 72/00 20060101 H04W072/00 |
Claims
1. A method for triggering machine type communication (MTC)
devices, comprising: sending a triggering indication from an MTC
server to a plurality of MTC devices using a cell broadcasting
service (CBS), wherein the triggering indication is configured to
initiate a communication between the MTC server and selected MTC
devices in the plurality of MTC devices that receive the triggering
indication, wherein the triggering indication includes an MTC group
identification (ID) value and only MTC devices belonging to the MTC
group ID value in the triggering indication are configured to act
on the triggering indication.
2. The method of claim 1, further comprising sending the triggering
indication with the MTC group ID value carried as a transparent
data container.
3. The method of claim 1, further comprising sending the triggering
indication with a transparent data container containing application
specific data.
4. The method of claim 1, wherein the triggering indication with
the MTC group ID value is communicated to a cell broadcasting
center that communicates with a radio network controller (RNC)
configured to interpret the triggering indication.
5. The method of claim 1, further comprising sending the triggering
indication with the MTC group ID value in a short message service
(SMS) broadcast command message.
6. The method of claim 5, further comprising sending the SMS
broadcast message using a base transceiver station that is
configured to segment the SMS broadcast message into a sequence of
4 blocks that are each 22 octets long for transmission to the MTC
device.
7. The method of claim 1, further comprising sending the triggering
indication with the MTC group ID value using a cell broadcasting
service having a cell broadcasting center in communication with the
MTC server and a radio access network (RAN).
8. The method of claim 7, further comprising sending an
acknowledgement of the trigger indication from a cell broadcast
center to the MTC server.
9. The method of claim 1, further comprising sending the trigger
indication with the MTC group ID value in a short message service
(SMS) broadcast request message.
10. The method of claim 1, further comprising sending the
triggering indication with the MTC group ID value as a paging
message sent by a Node B to notify the selected MTC devices that an
MTC system information block (SIB) is being broadcast by the Node
B.
11. The method of claim 10, further comprising receiving the MTC
SIB only at the selected MTC devices having the MTC group ID
value.
12. The method of claim 10, further comprising receiving the MTC
SIB at all MTC devices that receive the triggering indication when
a null MTC group ID value is used.
13. The method of claim 1, further comprising sending the
triggering indication from the MTC server to the plurality of MTC
devices, wherein the MTC devices are selected from the group
consisting of a sensor coupled to a transceiver, a user equipment,
a mobile station, a mobile computing device, a smart phone, a
tablet computer, and a laptop computer.
14. A Cell Broadcast Service operable to trigger a plurality of
machine type communication (MTC) devices, comprising: a cell
broadcast center configured to communicate with a radio access
network RAN and an MTC server through an MTC Inter Working Function
(IWF) gateway; and a group broadcast reference point defined
between the cell broadcast center and the MTC IWF gateway, wherein
the group broadcast reference point is configured to send a
triggering indication from the MTC server to the plurality of MTC
devices using the RAN, wherein the triggering indication is
configured to initiate a communication between the MTC server and
selected MTC devices in the plurality of MTC devices that receive
the triggering indication, wherein the triggering indication
includes an MTC group identification (ID) value and only those
selected MTC devices having the MTC group ID of the triggering
indication are configured to act on the trigger indication to
communicate with the MTC server.
15. The Cell Broadcast Service of claim 14, wherein the RAN is
configured to operate as one of a Global System for Mobile
Communications (GSM) having Enhanced Data rates for GSM Evolution
(EDGE) Radio Access Network (GERAN) and a Universal Terrestrial
Radio Access Network (UTRAN).
16. The Cell Broadcast Service of claim 14, wherein the RAN
comprises a CBC 108 is configured to send messages to a base
station controller (BSC) configured to receive a message from the
cell broadcast center, interpret the message and send the message
to a base transceiver station (BTS) for broadcast to the plurality
of MTC devices.
17. The Cell Broadcast Service of claim 14, wherein the triggering
indication and the MTC group ID are communicated via one of a short
message service (SMS) command and an SMS request.
18. The Cell Broadcast Service of claim 17, wherein the SMS
broadcast command is communicated using a base transceiver station
that is configured to segment the SMS broadcast message into a
sequence of 4 blocks that are each 22 octets long for transmission
to the MTC device.
19. The Cell Broadcast Service of claim 14, wherein the triggering
indication and the MTC group ID are carried by a transparent data
container.
20. The Cell Broadcast Service of claim 14, wherein the CBC is
configured to communicate an acknowledgement of the trigger
indication to the MTC server.
21. A Node B operable to trigger a plurality of machine type
communication (MTC) devices to communicate with an MTC server,
comprising: a paging module configured to communicate a first
system information block (SIB1) to the plurality of MTC devices via
a radio access network (RAN) to provide scheduling information for
the reception of an MTC SIB broadcast by the Node B, wherein the
MTC SIB includes a triggering indication that includes an MTC group
identification (ID) value and only those selected MTC devices
having the MTC group ID of the MTC SIB act on the triggering
indication to communicate with the MTC server.
22. The Node B of claim 21, wherein the Node B is an enhanced Node
B as defined by at least one of the third generation partnership
project long term evolution (3GPP LTE) Release 8, 9 or 10.
23. The Node B of claim 21, wherein the MTC SIB is configured to
include a plurality of MTC group ID values.
24. The Node B of claim, wherein the RAN is one of a Global System
for Mobile Communications (GSM) having Enhanced Data rates for GSM
Evolution (EDGE) Radio Access Network (GERAN), a Universal
Terrestrial Radio Access Network (UTRAN), and an Enhanced UTRAN
(E-UTRAN).
Description
CLAIM OF PRIORITY
[0001] This application claims priority to U.S. provisional patent
application Ser. No. 61/522,623, Attorney Docket No. P39106Z, filed
Aug. 11, 2011, which is incorporated by reference herein in its
entirety.
BACKGROUND
[0002] The increasing use of wireless communications has
revolutionized the way societies function. A large segment of
society in the developed world now has nearly constant and
ubiquitous access to the internet along with the ability to
communicate. Wireless personal area networks (WPAN), wireless local
area networks (WLAN), and wireless wide area networks (WWAN) have
been set up to provide the nearly omnipresent wireless access.
[0003] The WPAN, WLAN, and WWAN networks have been designed and set
up mainly for human interaction, such as person to person voice
calls and person to machine connections to specific servers and/or
general connections to the internet.
[0004] As the ability to perform wireless communications grows in
ability and complexity, there is an increased use of sensors and
other hardware devices that are configured to communicate data
wirelessly to other devices. This so called machine to machine
(M2M) communication often entails different characteristics of
wireless communication relative to those employed by people. For
instance, machines may communicate relatively small amounts of data
at infrequent intervals, such as once a day or once per week. In
addition, the machines don't sleep, enabling them to communicate at
any time of day. In some situations, a large number of machines may
communicate simultaneously, which can cause network connection
problems.
[0005] Accordingly, different design characteristics are needed to
allow a large numbers of machines to autonomously or
semi-autonomously wirelessly communicate with other machines, while
minimizing the impact of the machine communication on wireless
networks designed for people to communicate.
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] Features and advantages of the disclosure will be apparent
from the detailed description which follows, taken in conjunction
with the accompanying drawings, which together illustrate, by way
of example, features of the disclosure; and, wherein:
[0007] FIG. 1 illustrates a block diagram of a cell broadcast
service configured to communicate a trigger that includes a group
ID value to a plurality of MTC devices in accordance with an
example;
[0008] FIG. 2 depicts a flow chart of a method for triggering
machine type communication (MTC) devices, in accordance with an
example; and
[0009] FIG. 3 illustrates a block diagram of a Node B operable to
trigger a plurality of machine type communication (MTC) devices to
communicate with an MTC server in accordance with an example.
[0010] Reference will now be made to the exemplary embodiments
illustrated, and specific language will be used herein to describe
the same. It will nevertheless be understood that no limitation of
the scope of the invention is thereby intended.
DETAILED DESCRIPTION
[0011] Before the present invention is disclosed and described, it
is to be understood that this invention is not limited to the
particular structures, process steps, or materials disclosed
herein, but is extended to equivalents thereof as would be
recognized by those ordinarily skilled in the relevant arts. It
should also be understood that terminology employed herein is used
for the purpose of describing particular examples only and is not
intended to be limiting. The same reference numerals in different
drawings represent the same element.
Example Embodiments
[0012] An initial overview of technology embodiments is provided
below and then specific technology embodiments are described in
further detail later. This initial summary is intended to aid
readers in understanding the technology more quickly but is not
intended to identify key features or essential features of the
technology nor is it intended to limit the scope of the claimed
subject matter. The following definitions are provided for clarity
of the overview and embodiments described below.
[0013] In a third generation partnership project (3GPP) radio
access network (RAN) system, the transmission station can be a
combination of a Universal Terrestrial Radio Access Network (UTRAN)
(or Evolved UTRAN for 3GPP long term evolution (LTE)), Node Bs
(also commonly denoted as evolved Node Bs, enhanced Node Bs, eNode
Bs, or eNBs in 3GPP LTE) and Radio Network Controllers (RNCs),
which communicates with the wireless mobile device commonly
referred to as user equipment (UE). In a Global System for Mobile
Communications (GSM) having Enhanced Data rates for GSM Evolution
(EDGE) Radio Access Network (GERAN), communication is sent from a
base station controller (BSC) to a base transmission station (BTS)
to a wireless mobile device referred to as a mobile station
(MS).
[0014] A wireless mobile device that is configured to communicate
with another machine can be referred to as a machine type
communication (MTC) device. The term MTC device refers to a device
that is configured to communicate with another machine without the
need for human interaction. An MTC device may be as simple as a
sensor that is electrically coupled to a wireless transceiver. The
wireless transceiver may be configured to communicate with at least
one of a WPAN, WLAN, and WWAN. The MTC device can vary from the
simple device to a complex device such as a smart phone, a tablet
computing device, or a wireless laptop which may be employed for
machine to machine communication. The MTC device can include a
mobile station, as defined by IEEE 802.16e (2005 or 802.16m (2009)
or user equipment, as defined by 3GPP LTE Release 8 (2008), Release
9 (2009), or Release 10 (2011), commonly referred to as Rel.
8/9/10. The MTC device can also include a transceiver configured to
communicate using GERAN or other GSM networks. The term MTC, as
used herein, is also considered to be inclusive of the term
"machine to machine" (M2M), which is considered to be synonymous
with the term MTC.
[0015] A downlink (DL) transmission can be a communication from the
transmission station to the wireless mobile device (i.e. MTC
device), and an uplink (UL) transmission can be a communication
from the wireless mobile device to the transmission station (i.e.
MTC device).
[0016] MTC devices can be used in nearly any instance when
information needs to be collected and or communicated to another
source. A few examples include the use of MTC devices in the so
called "smart grid" in which additional information can
revolutionize the electrical distribution system through the use of
collecting and reporting meter information, power delivery and
distribution data, and power usage and billing information.
Millions of wireless sensors may be deployed that can be configured
to report desired data via a WPAN, a WLAN, or a WWAN, depending on
the location of the wireless sensor.
[0017] Another example includes the use of wireless sensors in an
intelligent transport system, in which wireless sensors can be used
to monitor traffic on roads and freeways, to provide logistics data
and toll data, and to synchronize traffic signals based on
information that is gathered and reported by the wireless sensors
in near real time.
[0018] Wireless sensors can also be used in healthcare systems such
as hospitals to report critical patient data, weather monitoring
systems to obtain a broader, more accurate view of climate
conditions, and so forth. The use of wireless sensors is only
limited by people's imaginations.
[0019] As the number of MTC devices increase, one challenge is
dealing with a large number of MTC devices that all attempt to
communicate at approximately the same time. For instance, a large
utility company may use MTC devices to wirelessly report a utility
usage value for each customer via a WWAN. If a transmission station
sends a request for data over a large area, tens of thousands of
MTC devices may simultaneously attempt to connect to an RAN and
communicate the designated data. Obviously, this can inundate the
RAN and potentially keep the MTC devices from reporting.
[0020] One way of dealing with a potential inundation of
communication at a RAN from a large number of MTC devices is to
divide MTC devices into groups. Each MTC device can be assigned a
group identification (ID) value. The group ID values may be
assigned by a user or a manufacturer. Alternatively, the group ID
value may be based on another value, such as an internet address or
media access control (MAC) address. The group ID value may be
static. Alternatively, the group ID value may be dynamic, thereby
the value can be assigned or changed remotely when it is needed or
desired. For example, if a group becomes too large, some members of
the group can be assigned to another group to average out the load
on the RAN when MTC devices in the groups communicate.
[0021] When each MTC device is assigned a group ID value, a
selected number of MTC devices can be designated to communicate at
a given time. The communication can involve establishing a
connection between the MTC device and a RAN. The communication may
also involve receiving data from a RAN at the MTC device or sending
data from an MTC device to the RAN.
[0022] For many MTC applications, a poll type model may be used to
enable communication between MTC devices and a machine, such as a
server designated to communicate with the MTC devices. Such a
server is referred to herein as an MTC server. An example of an MTC
server may be a server employed by a state transportation system
that collects data from and sends signals to wireless devices used
to monitor and control a state's transportation infrastructure. In
a poll type model, the MTC server can poll the MTC devices to
communicate. When a poll type model is used, the MTC devices are
typically configured so that they will not communicate without
being triggered by the MTC server.
[0023] There are many advantages to the use of a poll type model
for communicating with MTC devices. For instance, an MTC user (i.e.
a transportation management company) can be in control of
communication from the MTC devices. The MTC devices will not
randomly access the MTC server. This allows a communication
timeline to be designed to reduce the chances of the RAN being
inundated with MTC device traffic. Also, for applications where MTC
devices typically initiate communications, there may still be an
occasional need for an MTC server to poll data from the MTC
devices. Accordingly, in one embodiment, a group ID value can be
used to trigger selected MTC devices to communicate with an MTC
server.
[0024] In one embodiment, a trigger can be communicated from an MTC
server to selected MTC devices via a RAN using a cell broadcast
service. Particularly, in systems configured to operate based on a
GERAN or UTRAN specification, hereby referred to as a GERAN or
UTRAN system, a cell broadcast service (CBS) can be used. A cell
broadcast service can be configured to communicate a trigger
indication to a plurality of MTC devices that includes a group ID
value via a RAN.
[0025] FIG. 1 provides one example configuration of a cell
broadcast service configured to communicate a trigger indication
that includes a group ID value to a plurality of MTC devices 104
via a RAN 102. Each MTC device can include an MTC application that
recognizes one or more MTC group ID values. As previously
discussed, the MTC group ID value of each MTC device may be static
or dynamic. In this example, a communication from an MTC server can
be sent on the control plane to a cell broadcast center (CBC) 108
via an MTC Inter Working Function (IWF) 106.
[0026] Reference points in the example MTC broadcast architecture
of FIG. 1 include a Tunnel setup protocol (Tsp) reference point and
the SGi/Gi reference point. The Tsp reference point can be used to
connect the MTC-IWF to one or more MTC servers 104. The Tsp
reference point can support the reception of a device trigger
request from the MTC server; report to the MTC server the
acceptance or non-acceptance of the device trigger request; report
to the MTC server the success or failure of a device trigger
delivery; and provide congestion/load control information to the
MTC server as part of the response to trigger requests. The Tsp
reference point can also provide optional security and privacy
protection for communication between the MTC-IWF and the MTC
server. The Tsp reference point is the reference point an entity
outside the 3GPP network uses to communicate with the MTC-IWF
related control plane signaling to connect the MTC server with a
WWAN network, such as a 3GPP network, including a UTRAN based
network and a GERAN based network.
[0027] In this example, an additional reference point is
illustrated. The MTCc 110 reference point is defined as being
located between the MTC-IWF 106 and the CBC 108. The MTCc reference
point is used to send a trigger indication to a large number of MTC
devices. The trigger indication can be sent inside a CBS message or
a paging message. The trigger indication can include a group ID
value to indicate a group of MTC devices that will respond to the
trigger indication. This will be discussed more fully below. The
trigger indication can also include application specific data.
[0028] In the example embodiment of FIG. 1, the MTC-IWF 106 can
perform the functionality of a cell broadcast entity. The MTC-IWF
can be configured to format information sent between the MTC server
104 and the CBC 108, including the splitting of a CBS message into
a number of pages.
[0029] In one embodiment, the RAN 102 can be configured as a GERAN,
wherein the CBC 108 is configured to send messages to a base
station controller (BSC) portion of the RAN, which can interpret
the messages and send them to a base transceiver station (BTS) of
the RAN, as can be appreciated. Commands interpreted by the BSC
will result in a sequence of 4 SMS broadcast request messages or 1
SMS broadcast command message being sent to a BTS.
[0030] An SMS broadcast request message is sent from the BSC to the
BTS to request the sending of an SMS cell broadcast message. An SMS
cell broadcast (SMSCB) information element can be used. The SMSCB
information element contains the complete information to be
broadcast on the cell broadcast channel (CBCH), including the Layer
2 header that can be used on the radio path. The SMSCB channel
indicator information element indicates the CBCH which can be used
for broadcasting the data. If this information element is not
present then the basic CBCH can be used.
[0031] An SMS broadcast command message is sent from the BSC to the
BTS to command an SMS cell broadcast (CB) to be sent. The CB
command type of information element contains the command to be
performed, allowing the BSC to: request immediate broadcast (i.e.
transmit in the next CBCH opportunity); and set the BTS broadcast
default mode. The SMSCB message information element contains the
actual message to be broadcast on the CBCH. In this embodiment, a
maximum of 88 octets of data can be communicated. The BTS is
responsible for performing the segmentation, building the block
types and padding if necessary. The SMSCB channel indicator
information element indicates the CBCH that is used for
broadcasting the data. If this information element is not present
then the basic CBCH can be used. The SMS broadcast command message
can be sent to the BTS, which can segment the message into a
sequence of 4 blocks that are each 22 octets long. These segments
can be transferred via a base transmission station-mobile station
(BTS-MS) interface. In this example, the mobile station can be an
MTC device.
[0032] In one embodiment, a trigger message defined over the
BSC-BTS interface and the BTS-MS interface can be extended further
to carry additional information in a transparent data container.
For instance, an MTC group ID value can be included in the
transparent data container. The information in the transparent data
container, such as the MTC group ID value, can be directly
interpreted by the MS (i.e. the MTC device). The MTC device can use
this information to determine if it belongs to the MTC group
identified by the MTC group ID value. Based on the information in
the transparent data container, the MTC device can determine
whether or not to respond back to the trigger. Alternatively, the
trigger message itself can be enhanced to carry the MTC group ID
value that can be used to enable an MTC device to respond to
trigger messages containing a selected group ID value. Typically,
the MTC device will respond to trigger messages that contain the
same group ID value as the MTC device.
[0033] In another embodiment, the transparent data container and/or
the trigger message can include a plurality of different MTC group
ID values. This allows the MTC server to request communication with
devices in more than one group. In addition, one or more MTC group
ID values can be attached to another type of message. The MTC
device can be configured to read each MTC group ID value in the
message and/or transparent data container. If one of the MTC group
ID values is the same as the MTC device then the MTC device can
respond to the trigger message.
[0034] In another embodiment, the RAN can be configured as a UTRAN.
In this embodiment, CBS messages can be sent to the radio network
controller (RNC), where the messages can be interpreted. The
message can be formatted and sent as a single SMS broadcast command
to a UE. The UE can be configured to operate as an MTC device. In a
UTRAN system, the CBS messages can be completely transparent to the
Node B. No manipulation of data such as a fragmentation of data is
performed at the Node B.
[0035] In one embodiment, messages defined over an RNC-UE interface
can be extended further to be carried as a transparent data
container. As previously discussed, one or more group ID values can
be placed in the transparent data container. The information
carried in the transparent data container can be directly
interpreted by the UE (i.e. MTC device) to determine if the UE
belongs to a particular MTC group. Based on that information, the
UE can communicate a response to the trigger back to the RNC at the
RAN. Alternatively, the trigger message can be enhanced to carry an
MTC group ID that can be used to identify a UE belonging to the
same group identified by the MTC group ID. Another alternative is
to define a new message for group triggering of MTC devices with a
new set of action codes in the RAN.
[0036] In both the GERAN and UTRAN, a new control message can be
introduced to provide an acknowledgement of the trigger from the
CBC back to the MTC server. The acknowledgement can be communicated
through the MTC-IWF to allow for formatting of the acknowledgement
to a desired format that is usable by the MTC server.
[0037] In another embodiment, the RAN can be configured as a UTRAN
or an Enhanced-UTRAN (E-UTRAN) based on the 3GPP LTE Rel. 8/9/10. A
new MTC trigger indication can be communicated in a paging message
sent by the Node B or the enhanced Node B, herein referred to
together as the (e)Node B. A system information block (SIB) can
carry an MTC trigger indication and an MTC group ID. The SIB can be
referred to as an MTC SIB. If an MTC group ID is included, only MTC
devices belonging to the corresponding MTC group may be configured
to acquire the SIB. If an MTC group ID is not included, all MTC
devices can acquire the MTC SIB.
[0038] In a RAN configured as an E-UTRAN based on the 3GPP LTE Rel.
8/9/10 specifications, the scheduling information of the MTC SIB
can be provided in the SIB1. An MTC device can first acquire SIB1
information and subsequently acquire the MTC SIB based on the
scheduling information of the MTC SIB that is included in the
SIB1.
[0039] In one embodiment, a method 200 for triggering machine type
communication (MTC) devices is disclosed, as depicted in FIG. 2.
The method comprises the operation of sending a triggering
indication from an MTC server to a plurality of MTC devices using a
cell broadcast service (CBS), as shown in block 210. The triggering
indication is configured to initiate a communication between the
MTC server and selected MTC devices in the plurality of MTC devices
that receive the triggering indication, as shown in block 220. The
triggering indication can include an MTC group identification (ID)
value. Only those selected MTC devices belonging to the MTC group
(based on the group ID value in the triggering indication) are
configured to act on the trigger indication, as shown in block
230.
[0040] The triggering indication can be sent with the MTC group ID
value in a transparent data container. The transparent data
container can also contain application specific data such as an
application ID, application related counters/timer, and so forth
etc. The triggering indication with the MTC group ID value can be
sent in a short message service (SMS) broadcast command.
[0041] In another embodiment, a cell broadcast service (CBS) is
disclosed that is operable to trigger a plurality of machine type
communication (MTC) devices. The CBS comprises a cell broadcast
center that is configured to communicate with a radio access
network and an MTC server through an MTC Inter Working Function
(MTC-IWF) gateway. As previously discussed, the RAN can be
configured based on a GERAN specification, a UMTS specification, an
E-UMTS specification, or another wide area wireless network
specification.
[0042] The CBS further comprises a group broadcast reference point
that is located between the cell broadcast center and the MTC IWF
gateway. The group broadcast reference point is configured to send
a trigger indication from the MTC server to the plurality of MTC
devices using the RAN. The trigger indication can be communicated
using a broadcast communication technique based on the type of
specification for which the CBS is configured. The triggering
indication is configured to initiate a communication between the
MTC server and selected MTC devices in the plurality of MTC devices
that receive the triggering indication. The triggering indication
can include an MTC group identification (ID) value. Only those
selected MTC devices having the MTC group ID value of the
triggering indication may act on the triggering indication to
communicate with the MTC server.
[0043] In another embodiment, illustrated in an example block
diagram in FIG. 3, a Node B 304 is disclosed that is operable to
trigger a plurality of machine type communication (MTC) devices
318, 320, 322 to communicate with an MTC server 330 via a core
network 325. The Node B can be part of a RAN 302 that comprises a
paging module 306 configured to communicate a first system
information block (SIB1) to the plurality of MTC devices 318, 320,
322 to provide scheduling information for the reception of an MTC
SIB that is broadcast from the Node B 302. The MTC SIB includes a
triggering indication that can include an MTC group identification
(ID) value. Only those selected MTC devices having the MTC group ID
of the MTC SIB act on the triggering indication to communicate with
the MTC server. The Node B can be an enhanced Node B as defined by
the 3GPP LTE Release 8, 9 or 10. The MTC devices may be relatively
simple detectors, depicted in 318, or more complex wireless
devices, illustrated as a smart phone UE 320 and a laptop 322. The
RAN 302 can be a UTRAN, an E-UTRAN, or a GERAN, as previously
discussed.
[0044] It should be understood that many of the functional units
described in this specification have been labeled as modules, in
order to more particularly emphasize their implementation
independence. For example, a module may be implemented as a
hardware circuit comprising custom VLSI circuits or gate arrays,
off-the-shelf semiconductors such as logic chips, transistors, or
other discrete components. A module may also be implemented in
programmable hardware devices such as field programmable gate
arrays, programmable array logic, programmable logic devices or the
like.
[0045] Modules may also be implemented in software for execution by
various types of processors. An identified module of executable
code may, for instance, comprise one or more physical or logical
blocks of computer instructions, which may, for instance, be
organized as an object, procedure, or function. Nevertheless, the
executables of an identified module need not be physically located
together, but may comprise disparate instructions stored in
different locations which, when joined logically together, comprise
the module and achieve the stated purpose for the module.
[0046] Indeed, a module of executable code may be a single
instruction, or many instructions, and may even be distributed over
several different code segments, among different programs, and
across several memory devices. Similarly, operational data may be
identified and illustrated herein within modules, and may be
embodied in any suitable form and organized within any suitable
type of data structure. The operational data may be collected as a
single data set, or may be distributed over different locations
including over different storage devices, and may exist, at least
partially, merely as electronic signals on a system or network. The
modules may be passive or active, including agents operable to
perform desired functions.
[0047] Reference throughout this specification to "an example"
means that a particular feature, structure, or characteristic
described in connection with the example is included in at least
one embodiment of the present invention. Thus, appearances of the
phrases "in an example" in various places throughout this
specification are not necessarily all referring to the same
embodiment.
[0048] As used herein, a plurality of items, structural elements,
compositional elements, and/or materials may be presented in a
common list for convenience. However, these lists should be
construed as though each member of the list is individually
identified as a separate and unique member. Thus, no individual
member of such list should be construed as a de facto equivalent of
any other member of the same list solely based on their
presentation in a common group without indications to the contrary.
In addition, various embodiments and example of the present
invention may be referred to herein along with alternatives for the
various components thereof. It is understood that such embodiments,
examples, and alternatives are not to be construed as defacto
equivalents of one another, but are to be considered as separate
and autonomous representations of the present invention.
[0049] Furthermore, the described features, structures, or
characteristics may be combined in any suitable manner in one or
more embodiments. In the following description, numerous specific
details are provided, such as examples of search spaces, to provide
a thorough understanding of embodiments of the invention. One
skilled in the relevant art will recognize, however, that the
invention can be practiced without one or more of the specific
details, or with other methods, components, materials, etc. In
other instances, well-known structures, materials, or operations
are not shown or described in detail to avoid obscuring aspects of
the invention.
[0050] While the forgoing examples are illustrative of the
principles of the present invention in one or more particular
applications, it will be apparent to those of ordinary skill in the
art that numerous modifications in form, usage and details of
implementation can be made without the exercise of inventive
faculty, and without departing from the principles and concepts of
the invention. Accordingly, it is not intended that the invention
be limited, except as by the claims set forth below.
* * * * *