KR20140068107A - Changing the machine-to-machine (m2m) group of an m2m device - Google Patents

Abstract

Briefly, in accordance with one or more embodiments, communication with a first base station is performed by a machine-to-machine (M2M) device using a first group identifier and handover is performed to a second base station. The M2M device listens to the message broadcast by the second base station to determine if the first group identifier should be changed. If it is determined that the first group identifier should be changed for the M2M device, the second group identifier is requested to communicate with the second base station. In some embodiments, the M2M device starts from the idle mode and listens for messages broadcast by the base station. If the message indicates that the group identifier should be changed, the M2M device requests allocation of the updated group identifier.

Description

{CHANGING THE MACHINE-TO-MACHINE (M2M) GROUP OF AN M2M DEVICE}

Cross-reference to related application

This application claims priority from U.S. Serial No. 61 / 533,689 filed on September 12, 2011. No. 61 / 533,689, which is incorporated herein by reference in its entirety.

A machine-to-machine (M2M) communication system may involve placement of devices in the network to periodically transmit and / or receive a relatively small amount of data to a remote application / server. The M2M system is often referred to as the "Internet of things" for exchanging information between a subscriber-station and a server within the core network, or alternatively between other subscriber-stations, via a wireless link with a base station or via a wired link, Can be carried out with or without the need for human interaction. For example, the field data may be collected by the M2M device and sent back to the monitoring station for collection and analysis. In this example, the M2M device may include a parking ticket vending machine. When the parking ticket vending machine is full of coins and it is time to leave, a given vending machine can communicate its status to a monitoring server coupled to the network, in which case the operator goes to the vending vending machine and stores the coins stored therein Can be removed. In another example, the M2M device may be arranged to monitor the presence of specified hazardous substances, such as chemical agents, biological agents, and / or radionuclides, and the M2M device includes suitable sensors.

M2M devices are typically grouped together and assigned a common identifier for the group. A common identifier allows data transfer to or from a group of M2M devices to be handled collectively, rather than being handled separately by a given device. However, one or more devices may often be relocated from one group to another, in which case the moved device (s) should be assigned a new group identifier.

The subject matter is particularly pointed out and particularly claimed in the concluding portion of the specification. However, such subject matter may be understood by reference to the following detailed description when read in conjunction with the accompanying drawings.
1 is a diagram illustrating an M2M system in which an M2M mobile station belongs to a first M2M group within a first M2M zone in accordance with one or more embodiments.
FIG. 2 is a diagram of the M2M system of FIG. 1, illustrating how an M2M mobile station performs handover to a target base station within a first M2M zone in accordance with one or more embodiments.
FIG. 3 is a diagram of the M2M system of FIG. 1, illustrating how an M2M mobile station performs handover to a target base station in an overlap region between a first M2M zone and a second M2M zone, in accordance with one or more embodiments.
FIG. 4 is a diagram of the M2M system of FIG. 1, showing that an M2M mobile station performs handover to a target base station located in a second M2M zone and not located in a first M2M zone, in accordance with one or more embodiments.
FIG. 5 is a diagram of the M2M system of FIG. 1, in which an M2M mobile station served by a base station in a first M2M zone according to one or more embodiments receives a hand toward a target base station in a second M2M zone, Over. ≪ / RTI >
FIG. 6 is a drawing of an exemplary architecture of an M2M system as illustrated in FIGS. 1-5, which illustrates a mobile network operator and a service consumer in accordance with one or more embodiments.
7 is a flow diagram of a method for an M2M mobile station to change an M2M group while in a connected mode according to one or more embodiments.
8 is a flow diagram of a method for an M2M mobile station for modifying an M2M group while in an idle mode in accordance with one or more embodiments.
9 is a block diagram of an information handling system capable of identifying and implementing changes to an M2M group of an M2M device in a broadband network in accordance with one or more embodiments.
10 is an isometric view of the information handling system of FIG. 10, which may optionally include a touch screen in accordance with one or more embodiments.
It will be appreciated that for simplicity and / or clarity, the elements shown in the figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. In addition, where appropriate, reference numerals may be repeated throughout the figures to denote corresponding and / or similar elements.

In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the claimed subject matter. However, it will be understood by those of ordinary skill in the art that the claimed subject matter can be practiced without these specific details. In other instances, well-known methods, procedures, components and / or circuits have not been described in detail.

In the following detailed description and / or claims, the terms "coupled" and / or "connected" may be used with their derivatives. In certain embodiments, "connected" can be used to indicate that two or more elements are in direct physical and / or electrical contact with each other. "coupled " may mean that two or more elements are in direct physical and / or electrical contact. However, "coupled" may also mean that two or more elements do not physically and / or electrically contact each other directly and instead cooperate and / or interact with each other. For example, "coupled " may mean that two or more elements are not in contact with one another, but instead are indirectly coupled together through another element or intermediate element. Finally, the terms "on", "overlying" and "over" may be used in the following detailed description and / or claims. "on "," overlying ", and "over" may be used to indicate that two or more elements are in direct physical contact with each other. However, "over" may mean that two or more elements are not in direct contact with each other. For example, "over" may have other elements or elements between two elements, with one element on another but not touching each other. Also, although the scope of the claimed subject matter is not limited in this respect, "and / or" can mean "and ", can mean" or, " quot; one ", which may mean "some, but not all ", and may mean " neither " and / or" both. In the following detailed description and / or claims, the terms "comprise" and "include" are used interchangeably and are intended to be synonymous with respect to each other.

Referring now to FIG. 1, an M2M system in which an M2M mobile station belongs to a first M2M group within a first M2M zone will be described in accordance with one or more embodiments. As shown in FIG. 1, the M2M system 100 may include a base station 110 serving one or more M2M devices or a mobile station (MS) belonging to a first M2M group in a first M2M zone 112. For example, an M2M mobile station 114, an M2M mobile station 116, and an M2M mobile station 118 may communicate with one or more M2M devices in a network entity group < RTI ID = 0.0 >Lt; RTI ID = 0.0 > MGID < / RTI > The domain of the network entity may be identified by an M2M zone identifier (M2M_ZONE_ID) that can be broadcast by an AAI_SCD message. The M2M group may be defined as a set of M2M devices having a common identifier such as a common MGID. An M2M zone may be defined as a geographic area served by one or more base stations whose M2M group and M2M zone identifiers are valid. Similarly, the base station 120 may serve one or more devices or mobile stations belonging to a second M2M group in the second M2M zone 122, and the M2M mobile station 124 may belong to a second M2M group assigned another MGID have. In one or more embodiments, the scope of the claimed subject matter is not limited in this respect, but the M2M system 100 may be an IEEE (Institute of Electrical and Electronics Engineers) 802.16p standard, or any future version, It can operate according to the standard.

In one or more embodiments, in the connected mode, an M2M device, such as M2M mobile station 114, may perform handover from one base station to another base station, referred to as the target base station. Depending on the M2M zone or zones being served by the target base station, the M2M mobile station 114 may or may not be required to update its M2M group and may need to update its MGID accordingly. It should be noted that the M2M group is only valid within a particular M2M zone. Thus, generally, when the M2M device is handed over from the base station to the target base station and both base stations serve the same M2M zone, there is no need to update the MGID. However, if the M2M device is handed over from the base station to the target base station and the target base station is serving a different M2M zone and not serving the original M2M zone, then the M2M device needs to update its M2M group and its MGID accordingly . An exemplary scenario for such a handover is shown and described below with respect to Figs. 2-5.

Referring now to FIG. 2, an M2M system in which an M2M mobile station performs handover to a target base station in a first M2M zone will be described in accordance with one or more embodiments as a drawing of the M2M system of FIG. Sometimes an M2M mobile station may perform handover from one base station to another, and the target base station is still located within the same zone as the first base station. As shown in FIG. 2, the M2M mobile station 114 performs handover from the base station 110 to the target base station 128. The base station 128 transmits its M2M zone identifier as the M2M_ZONE_ID in the message received by the M2M mobile station 114. [ The M2M mobile station 114 compares the M2M zone information broadcast by the target base station 128 with the previous M2M zone information. The M2M zone information transmitted by the target base station 128 is the same as the M2M zone information of the original base station 110 since the target base station 128 is located in the M2M zone 112 which is the same M2M zone. Therefore, the M2M_ZONE_ID is the same because the zone is unchanged, and the M2M mobile station 114 does not need to update its MGID since the M2M group is unchanged.

Referring now to FIG. 3, an M2M system in which an M2M mobile station performs handover to a target base station in an overlap region between a first M2M zone and a second M2M zone, according to one or more embodiments, Will be. One or more devices of the first group may move / relocate from one M2M zone to another M2M zone, for example, the M2M mobile station 114 of the first M2M group may move from the M2M zone 112 to the M2M zone 122, . ≪ / RTI > 3, when the M2M mobile station 114 is handed over from its serving base station 110 to the target base station 130 and the target base station 130 is handed over to the first M2M zone 112 and the second M2M zone 122, such an event occurs. Thus, the target base station 130 is located in the overlapping region of the first M2M zone 112 and the second M2M zone 122. When the M2M mobile station 114 performs such a handover from its serving base station 110 to the target base station 130, the M2M mobile station 114 determines whether the target base station 130 is in coverage of the first M2M zone 112 The mobile station may listen to the M2M zone information broadcast from the target base station 130 to recognize whether it resides in the zone. In one or more embodiments, the first M2M zone 112 and the second M2M zone 122 may at least partially overlap in the overlap region 126 and the target base station 130 may overlap in the overlap region 126 do. In this case, the target base station 130 may broadcast the M2M_ZONE_ID of the first M2M zone and the M2M_ZONE_ID of the second M2M zone. Thus, when the M2M mobile station 114 moves to the coverage area of the target base station 130 and receives this broadcasted message, the target base station 130 will determine that it belongs to its current first M2M zone. Thus, in this situation, when the M2M mobile station 114 performs handover from one base station 110 to another base station 130 but the base station 130 is still in the first M2M zone 112, For example, when the M2M mobile station 114 moves to the overlap area 126, there is no need to change its MGID. It should be noted that the base station 130 in the overlap area 126 may actually serve a number of M2M zones, such as the first M2M zone 112 and the second M2M zone 122. In this situation, the base station 130 serving a plurality of M2M zones will broadcast M2M zone information for every serving M2M zone. Accordingly, when performing handover to the target base station 130 in the overlapping region, the base station 130 may determine that the first M2M zone 112 received by the M2M mobile station 114 and the M2M_ZONE_ID 102 for the second M2M zone 122 ≪ / RTI > Since the M2M mobile station 114 is still in the same M2M zone as it receives the M2M zone information for the first M2M zone 112 that is its original M2M zone, There is no need to update the MGID accordingly. The M2M mobile station 114 needs to update its MGID only when the M2M mobile station 114 is completely out of its original zone and performs handover to the new base station.

Referring now to FIG. 4, an M2M system in accordance with one or more embodiments of the M2M system of FIG. ≪ RTI ID = 0.0 > 1 < / RTI > for performing a handover to a target base station located in a second M2M zone and not located in a first M2M zone, Will be. 4, the M2M mobile station 114 receives a new target base station 132 in the second M2M zone 122 from being served by the base station 110 of the first M2M group in the first M2M zone 112 ). ≪ / RTI > The M2M mobile station 114 listens for M2M zone information broadcast by the target base station 132, e.g., a message carrying M2M_ZONE_ID. The M2M mobile station 114 determines that the M2M zone information broadcast by the target base station 132 is in the second M2M zone 122 where the M2M mobile station 114 is currently a new M2M zone, Which indicates that the M2M zone 112 has completely gone off. Thus, since the M2M zone is changed, the M2M mobile station 114 requests the target base station 132 to update or change its M2M group in the M2M system and update its MGID to a valid MGID in the second M2M zone 122 Lt; / RTI > To reduce or reduce overhead, in one or more embodiments, M2M system 100 periodically broadcasts a sufficient amount of information, such as M2M zone ID (M2M_ZONE_ID), to specify a geographic boundary between multiple M2M zones You can cast. The M2M mobile station 114 receives such handover information from the serving base station 110 and / or the target base station 120 to determine whether it needs to update its MGID and / or update its M2M zone. Once the M2M mobile station 114 updates its MGID, the M2M mobile station 114 may operate within the second M2M zone 122 using its MGID, which is valid within the second M2M zone 122.

Thus, in one or more embodiments, when the M2M mobile station 114 performs a handover from its serving base station to the target base station, the M2M mobile station 114 may notify the M2M mobile station 114 of a new serving And hears M2M_ZONE_ID information from the target base station serving as the base station. When the M2M_ZONE_ID information from the target base station indicates that the M2M mobile station 114 is currently in a new M2M zone, for example, the second M2M zone 122, the M2M mobile station 114 transmits a new MGID corresponding to the new M2M group May be requested from the M2M system 100.

In a situation where M2M mobile station 114 is in an idle mode, M2M mobile station 114 carries information about the M2M zone to determine whether M2M mobile station 114 needs to update its M2M group and / or its MGID And may periodically wake up during a paging listening interval to receive a broadcasting message. In idle mode, the M2M mobile station 114 monitors the M2M_ZONE_ID broadcast from the serving base station and / or informs the base station about the M2M group boundary for that particular base station based at least in part on the base station identifier (BSID) Such as the M2M group 112, by contacting the network to the M2M group. The MGID of the M2M mobile station 114 during an idle state may be changed or updated, for example, via a location update procedure, such as an M2M device initialized location update or a base station initialized location update, or by network re-entry. The location update may be based on a paging message from the base station or based on a timer based update. For example, the M2M device may be activated during the paging listening interval to determine whether its current base station is the original or previous M2M zone or a portion thereof. Otherwise, the M2M device will update its MGID and also update its M2M_ZONE_ID. A description of how the M2M mobile station 114 can determine when it needs to change the M2M group and / or the MGID is described below with respect to FIGS. 7 and 8. FIG. An example of an M2M system 100 in which no overlapping regions exist between M2M regions is shown and described with respect to FIG. 5 below.

Referring now to FIG. 5, an M2M system in which an M2M mobile station served by a base station in a first M2M zone according to one or more embodiments performs a handover to a target base station in a second M2M zone, where the M2M zone does not overlap, . The M2M system 100 of Figure 5 is similar to the M2M system 100 of Figure 1 except that there is no overlap area 126 between the zones of the M2M groups 112 and 122 in the embodiment shown in Figures 3 and 4. [ 0.0 > 100 < / RTI > In this embodiment, when the M2M mobile station 114 performs handover from the serving base station 128 to the target base station 132, there is no overlap between the M2M zones served by each base station, There is a clear boundary between the M2M zones so that the first M2M group 114 and / or the MGID need to switch to the M2M group and / or MGID of the second M2M group 122 served by the target base station 132 do. In any case, the M2M mobile station 114 may be configured to determine whether the M2M mobile station 114 needs to update its M2M group and / or its MGID as determined by the M2M system 100, ) Listens for messages broadcast by the base station. An exemplary architecture of the M2M system is shown and described below with respect to FIG.

Referring now to FIG. 6, an architecture illustrating a mobile network operator and service consumer according to one or more embodiments will be described, as a drawing of an exemplary architecture of an M2M system as shown in FIGS. 1-5. As shown in FIG. 6, the architecture 600 shown in FIG. 6 is for the M2M system 100 as shown in FIGS. 1-5, and the architecture 600 is for the M2M device 614 and / One or more M2M devices such as M2M device 616 and / or one or more non-M2M devices such as a non-M2M device 612 and / or a non-M2M device 618, : MNO) 610. In any case, the scope of the claimed subject matter is not limited in this respect, but the architecture 600 may be based on the Institute of Electrical and Electronics Engineers (IEEE) 802.16e network-based IEEE 802.16 p network, or an IEEE 802.16 network such as an IEEE 802.16p network based on an IEEE 802.16m network to implement a WiMAX-II system. In such an embodiment, the scope of the claimed subject matter is not limited in this respect, but a non-M2M device may operate in accordance with the IEEE 802.16 standard and the M2M device may operate in accordance with the IEEE 802.16 standard, in particular the IEEE 802.16p standard . Alternatively, the scope of the claimed subject matter is not limited in this respect, but the architecture 600 may be compatible with Third Generation Partnership Project (3GPP) standards such as 3G systems, or may be a Long Term Evolution (LTE) Compatible with LTE-Advanced systems.

In some embodiments, the M2M device and the non-M2M device may communicate directly with the mobile network operator 610, and in some embodiments, the non-M2M device 618 may communicate with the non-M2M device 618, And may indirectly communicate with the mobile network operator 610 via the M2M device 616. A device may communicate over an air interface by a base station 624 compliant with IEEE 802.16 as part of an IEEE 802.16 access service network (ASN) The access service network 620 may be coupled to a Connectivity Service Network (CSN) 622, which may include one or more M2M servers 626. The M2M server 626 may communicate with the mobile network operator 610 over a network such as the Internet to receive M2M services from the M2M device and / or from the non-M2M device via the mobile network operator 610 Can be combined with an M2M service consumer 628 that can be combined. As shown in FIG. 5, the architecture 600 of the M2M network is only one exemplary network architecture, and other types of network architectures may be provided to implement the M2M system 100, It should be noted that the present invention is not limited in view of the above. An exemplary flow diagram of how an M2M mobile station operating in M2M system 100 while in connected mode changes its M2M group is shown and described below with respect to FIG.

Referring now to FIG. 7, a flow diagram of how an M2M mobile station changes M2M groups while in connected mode according to one or more embodiments will be described. Method 700 illustrates one specific embodiment of a method by which an M2M mobile station changes an M2M group in an M2M system. However, in one or more other embodiments, blocks of various other orders of method 700 may be implemented and may have more or fewer blocks, and the scope of the claimed subject matter is not limited in this respect . At block 710, the base station identifies one or more M2M users or M2M devices located in one or more of its M2M zones that the base station is serving. Next, in block 712, the base station assigns the M2M group identifier (MGID) to the user or device in each M2M zone. At block 714, the base station periodically broadcasts a M2M_ZONE_ID for a given M2M zone, and at block 716, a user or device in a given M2M group receives a predetermined M2M Multicasting traffic sent to all users in the group and the M2M user or device can send the traffic to the base station according to the resources allocated to that M2M group. Next, at block 718, a mobile station, such as M2M mobile station 114, may perform a handover from the current serving base station to the target base station, as shown and described above with respect to FIGS. 1-5. At block 720, the M2M mobile station 114 hears the M2M_ZONE_ID broadcast by the target base station and at block 722 determines if the M2M mobile station 114 is in the new M2M zone and needs a new MGID. If the M2M mobile station 114 is not in the new M2M zone and therefore does not require a new MGID, then at block 726 the M2M mobile station 114 will not change the MGID of the M2M mobile station 114, And can communicate with the target base station. On the other hand, if the M2M mobile station 114 is in the new M2M zone and thus requires a new MGID, then at block 724 the M2M mobile station 114 requests a new MGID from the target base station and at block 726, It may proceed to communicate with the target base station as its new serving base station using the MGID. An exemplary flow diagram of how an M2M mobile station operating in the M2M system 100 while in idle mode changes its M2M group is shown and described below with respect to FIG.

Referring now to FIG. 8, a flow diagram of how an M2M mobile station changes an M2M group while in idle mode according to one or more embodiments will be described. Method 800 illustrates one particular embodiment of how an M2M mobile station changes an M2M group while in an idle mode in an M2M system. However, in one or more other embodiments, blocks of various other orders of method 800 may be implemented and may have more or fewer blocks, and the scope of the claimed subject matter is not limited in this respect . At block 810, the base station identifies one or more M2M users or M2M devices located in one or more of its M2M zones that the base station is serving. Next, at block 812, the base station assigns the M2M group identifier (MGID) to the user or device in each M2M zone. At block 814, the base station periodically broadcasts M2M_ZONE_ID and its base station identifier (BSID) for a given M2M zone, so that at block 816, the user or device within a given M2M zone is subscribed to the MGID of those users or devices Multicasting traffic sent to all users in a given M2M group by the base station and the M2M user or device can send that traffic to the base station according to the resources allocated to that M2M group. Next, at block 818, a mobile station, such as M2M mobile station 114, may enter an idle mode, as shown and described above with respect to Figs. 1-5. At block 820, the M2M mobile station 114 periodically activates during its paging listening interval to listen to the M2M_ZONE_ID and BSID broadcast by its serving base station, and when the BSID and M2M_ZONE_ID change in block 822, the M2M mobile station 114 Can determine whether it is necessary to update the MGID. Paging may be initiated by the base station to broadcast a paging message (AAI_PAG_ADV) to the M2M mobile station 114, or the M2M mobile station 114 may periodically wake up during the paging listening interval. If the M2M mobile station 114 does not need to update its MGID, the M2M mobile station may connect to that base station and transmit to or receive from the base station using its current MGID. On the other hand, if the M2M mobile station 114 determines in block 822 that it needs to update its MGID, then in block 824 the M2M mobile station 114 requests the updated MGID for that serving base station. A determination may be made based at least in part on the current geographic location based at least in part on the identity of the current base station, the base station identifier (BSID), and / or the current M2M_ZONE_ID. At block 826, the M2M mobile station 114 may transmit data to or receive data from the base station using the updated MGID. An exemplary block diagram of an information handling system that can identify and implement changes to that MGID is shown and described with respect to FIG. 9 below.

Referring now to FIG. 9, a block diagram of an information handling system capable of identifying and implementing changes to an M2M group of an M2M device in a broadband network, in accordance with one or more embodiments, will be described. The information handling system 900 of FIG. 9 may implement any one or more of the network elements or devices of the M2M system 100 as shown and described with respect to FIGS. 1-5. For example, the information handling system 900 may include a basic M2M mobile station 114, a serving base station 110, a target base station 120, and more or fewer components depending on the hardware specifications of a particular device or network element. , And / or hardware of any device and / or other base station in the M2M group. Although the information handling system 900 represents one example of some types of computing platforms, the information handling system 900 may include more or fewer elements and / or configurations of various elements than those shown in FIG. 9, The scope of the object is not limited in this respect.

In one or more embodiments, the information handling system 900 may include an application processor 910 and a baseband processor 912. The application processor 910 may be used as a general purpose processor including an application for the information handling system 900 and various subsystems. The application processor 910 may comprise a single core, or alternatively may include multiple processing cores, and one or more cores may include a digital signal processor or a digital signal processing core. In addition, application processor 910 may include a graphics processor or coprocessor located on the same chip, or, alternatively, a graphics processor coupled to application processor 910 may include separate and distinct graphics chips. The application processor 910 may include an onboard memory such as a cache memory and may also include a synchronous dynamic random access memory (SDRAM) 914 for storing and / or executing an application during operation, Or may be coupled to an external memory device, such as a NAND flash 916, which stores applications and / or data. The baseband processor 912 may control the broadband wireless capability for the information handling system 900. The baseband processor 912 may store code that controls such broadband wireless capability in the NOR flash 918. Baseband processor 912 may include a wireless wide area network (WWAN) transceiver 920 used to modulate and / or demodulate broadband network signals to communicate via, for example, a WiMAX network or 3GPP LTE network based on IEEE 802.16p, . The WWAN transceiver 920 couples to one or more power amplifiers 922 each coupled to one or more antennas 924 that transmit and receive radio frequency signals via a WWAN broadband network. Baseband processor 912 may also control a wireless local area network (WLAN) transceiver 926 coupled to one or more suitable antennas 928 and may be a Wi-Fi, Bluetooth, and / or IEEE 802.11 a / b / (AM) or Frequency Modulation (FM) radio standards, including the g / n standard. It should be noted that these are merely exemplary implementations for the application processor 910 and the baseband processor 912, and the scope of the claimed subject matter is not limited in this respect. For example, one or more of SDRAM 914, NAND flash 916, and / or NOR flash 918 may be implemented as a memory, such as a magnetic memory, a chalcogenide memory, a phase change memory, or an ovonic memory Other types of memory technology, and the scope of the claimed subject matter is not limited in this respect.

In one or more embodiments, the application processor 910 may drive a display 930 that displays various information or data, and may also be coupled to the display 930 via a touch screen 932, e.g., via a finger or a stylus The touch input can be received from the user. The ambient light sensor 934 is operable to sense the ambient or ambient brightness of the display 930 such that the information handling system 900 is operable to control the brightness or contrast value for the display 930 according to the intensity of the ambient light detected by the ambient light sensor 934, And can be used to detect the amount of light. One or more cameras 936 can be used to capture images that are processed by the application processor 910 and / or are at least temporarily stored in the NAND flash 916. [ The application processor may also include a gyroscope 938, an accelerometer 940 coupled to a suitable GPS antenna 948 for detection of various environmental characteristics including location, movement, and / or orientation of the information handling system 900. [ (CODEC) 944, and / or a global positioning system (GPS) controller 946, as will be appreciated by those skilled in the art. Alternatively, the controller 946 may include a Global Navigation Satellite System (GNSS) controller. The audio CODEC 944 may be coupled to the information handling system via an audio port 950, for example, via one or more audio (s) to provide microphone input and speaker output via an internal device and / Port 950. In this embodiment, Also, the application processor 910 may include one or more input / output (I / O) ports to couple one or more I / O ports 954, such as a universal serial bus (USB) port, a high- May be coupled to the transceiver 952. Also, although the scope of the claimed subject matter is not limited in this respect, the one or more I / O transceivers 952 may include one or more memory for selectively removable memory, such as a secure digital (SD) card or a subscriber identity module Slot 956. In this embodiment,

Referring now to FIG. 10, an information handling system that may optionally include a touch screen in accordance with one or more embodiments will be described as an isometric view of the information handling system of FIG. FIG. 10 illustrates an exemplary implementation of the information handling system 900 of FIG. 9 implemented as a cellular telephone, smartphone, or tablet type device or the like. In one or more embodiments, the scope of the claimed subject matter is not limited in this regard, but the information handling system 900 may include any one of the internal structure nodes and / or mobile stations of Figs. 1-5. The information handling system 900 includes a touch screen 912 that receives tactile input control and commands through the user's finger 1016 and / or stylus 1018 to control one or more application processors 910 And a housing 1010 having a display 930, The housing 1010 may include one or more components of the information handling system 900, such as one or more processors 910, an SDRAM 914, a NAND flash 916 and a NOR flash 918, a baseband processor 912 ) And / or a WWAN transceiver 920. < / RTI > The information handling system 900 may also optionally include a physical actuator region 1020 that may include a keyboard or button that controls the information handling system via one or more buttons or switches. The information handling system 900 may also include a memory port or slot 956 that receives non-volatile memory, such as, for example, flash memory in the form of a secure digital (SD) card or a subscriber identity module have. Optionally, the information handling system 900 may include one or more speakers and / or microphones 1024 and a connection port 924 that connects the information handling system 900 to other electronic devices, docks, displays, battery chargers, ). In addition, the information handling system 900 may include a headphone or speaker jack 1028, and one or more cameras 936 on one or more sides of the housing 1010. It should be noted that the information handling system 900 of FIG. 10 may include more or fewer elements than are shown in various arrangements, and the scope of the claimed subject matter is not limited in this respect.

Although the claimed subject matter has been described in specific detail, it will be appreciated by those of ordinary skill in the art that the elements may be altered without departing from the spirit and / or scope of the claimed subject matter. It will be understood by those of ordinary skill in the art that changes in the M2M group and / or its many related uses of M2M devices will be understood by the foregoing detailed description and do not depart from the scope and / or spirit of the claimed subject matter, Without departing from the spirit and scope of the invention, various changes may be made in form, arrangement and / or arrangement of elements thereof without departing from the spirit and / or the practical aspects of the present invention, . The claims are intended to encompass and / or include such changes.

Claims (24)

15. An article of manufacture comprising a storage medium in which instructions are stored,
The instructions, when executed,
Communicating with a first base station using a first group identifier;
Performing a handover to a second base station,
Listening to a message broadcast by the second base station to determine if the first group identifier should be changed;
If the first group identifier is to be changed, requesting assignment of a second group identifier to communicate with the second base station
Products.
The method according to claim 1,
The first group identifier, or the second group identifier, or a combination thereof includes a machine-to-machine group identifier (MGID)
Products.
The method according to claim 1,
The first group identifier is assigned to an M2M device in a first M2M zone and the second group identifier is assigned to an M2M device in a second M2M zone
Products.
The method according to claim 1,
Wherein the first group identifier is assigned to an M2M device in a first M2M zone and the second group identifier is assigned to an M2M device in a second M2M zone and wherein the first M2M zone is at least partially overlapped with the second M2M zone doing
Products.
The method according to claim 1,
Wherein the first group identifier is assigned to an M2M device in a first M2M zone and the second group identifier is assigned to an M2M device in a second M2M zone and wherein the first M2M zone does not overlap the second M2M zone
Products.
The method according to claim 1,
Wherein the message broadcast by the second base station indicates a geographic boundary between a first zone to which the first group identifier is assigned and a second zone to which the second group identifier is assigned, , Further requesting allocation of a second group identifier in response to a change from the first zone to the second zone
Products.
The method according to claim 1,
Wherein the message broadcast by the second base station comprises an M2M zone identifier (M2M_ZONE_ID), the instruction, when executed, requesting allocation of a second group identifier in response to a change in the M2M zone identifier More to run
Products.
15. An article of manufacture comprising a storage medium in which instructions are stored,
The instructions, when executed,
Waking from the idle mode to listen to a message broadcast by the base station,
If the message indicates that the group identifier should be changed, requesting assignment of the updated group identifier from the base station
Products.
9. The method of claim 8,
The group identifier includes an MGID
Products.
9. The method of claim 8,
Wherein the message broadcasted by the base station includes information about an M2M zone identifier (M2M_ZONE_ID), wherein the instructions, when executed, further comprise requesting allocation of the updated group identifier if the M2M zone identifier has changed Running
Products.
9. The method of claim 8,
Wherein the message broadcast by the base station comprises a base station identifier (BSID), and when executed, requests the allocation of the updated group identifier in response to the change of the BSID if the M2M zone identifier has changed Run the step further
Products.
And a baseband processor coupled to the one or more wireless transceivers,
The baseband processor includes:
Communicate with a first base station using a first group identifier,
Performs handover to the second base station,
Listening to a message broadcast by the second base station to determine whether the first group identifier should be changed,
And to request allocation of a second group identifier to communicate with the second base station if the first group identifier is to be changed
Information handling system.
13. The method of claim 12,
The first group identifier, or the second group identifier, or a combination thereof,
Information handling system.
13. The method of claim 12,
The first group identifier is assigned to an M2M device in a first M2M zone and the second group identifier is assigned to an M2M device in a second M2M zone
Information handling system.
13. The method of claim 12,
Wherein the first group identifier is assigned to an M2M device in a first M2M zone and the second group identifier is assigned to an M2M device in a second M2M zone and wherein the first M2M zone is at least partially overlapped with the second M2M zone doing
Information handling system.
13. The method of claim 12,
Wherein the first group identifier is assigned to an M2M device in a first M2M zone and the second group identifier is assigned to an M2M device in a second M2M zone and wherein the first M2M zone does not overlap the second M2M zone
Information handling system.
13. The method of claim 12,
Wherein the message broadcast by the second base station indicates a geographic boundary between a first zone to which the first group identifier is assigned and a second zone to which the second group identifier is assigned, And to execute an allocation request of the second group identifier in response to a change from the first zone to the second zone
Information handling system.
13. The method of claim 12,
Wherein the message broadcast by the second base station comprises an M2M zone identifier (M2M_ZONE_ID) and the baseband processor is further configured to execute an allocation request of a second group identifier in response to a change in the M2M zone identifier
Information handling system.
13. The method of claim 12,
An application processor coupled to the baseband processor, and a touch screen for receiving input to control the application processor
Information handling system.
And a baseband processor coupled to the one or more wireless transceivers,
The baseband processor includes:
Starting from the idle mode, listening to a message broadcast by the base station,
If the message indicates that the group identifier should be changed, requesting assignment of the updated group identifier from the base station
Information handling system.
9. The method of claim 8,
The group identifier includes an MGID
Information handling system.
21. The method of claim 20,
Wherein the message broadcast by the base station includes information about an M2M zone identifier (M2M_ZONE_ID), wherein the baseband processor is further configured to execute an allocation request of the updated group identifier if the M2M zone identifier is changed
Information handling system.
21. The method of claim 20,
Wherein the message broadcast by the base station comprises a base station identifier (BSID), the baseband processor further configured to execute an assignment request of the updated group identifier in response to the change of the BSID if the M2M zone identifier has changed felled
Information handling system.
21. The method of claim 20,
An application processor coupled to the baseband processor, and a touch screen for receiving input to control the application processor
Information handling system.

Images