TW201731269A - Aggregated signaling for machine type communication (MTC) devices - Google Patents

Abstract

Technology for an eNodeB operable to facilitate aggregated signaling from a plurality of devices is disclosed. The eNodeB can receive a connection request message from each of the plurality of devices. The eNodeB can select a device from the plurality of devices using a set of selection criteria. The eNodeB can send a connection reject message that includes a configuration that causes the selected device to form a cell comprising a selected subset of devices of the plurality of devices. The eNodeB can send a connection reject message that includes a redirection to the cell formed by the selected device, wherein each of the devices in the selected subset are configured to transmit a connection request message to the selected device based on the redirection to the cell.

Description

Aggregate signaling for machine type communication (MTC) devices

The present invention relates to aggregate signaling for a machine type communication (MTC) device.

Wireless mobile communication technologies use various standards and protocols to transfer data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device). Some wireless devices use Orthogonal Frequency-Division Multiple Access (OFDMA) communication in Downlink (DL) transmission and uplink (UpLink; UL) transmission. A single carrier frequency division multiple access (SC-FDMA) communication is used. Standards and protocols for Orthogonal Frequency-Division Multiplexing (OFDM) for signal transmission include the Third Generation Partnership Project (3GPP) Long-Range Evolution Project (Long Term Evolution) (referred to as LTE), commonly referred to as global interoperability microwave access in industrial groups (Worldwide Interoperability for Microwave Access; WiMAX), Institute of Electrical and Electronics Engineers (IEEE) 1102.16 standard (for example, 1102.16e, 1102.16m), and commonly referred to as WiFi in industrial groups. IEEE 1102.11 standard.

In a 3GPP Radio Access Network (RAN) LTE system, the node may be an evolved global terrestrial radio access network that communicates with a wireless device called User Equipment (UE). (Evolved Universal Terrestrial Radio Access Network; E-UTRAN for short) Node B (also commonly referred to as evolved Node B, Enhanced Node B, eNodeB, or eNB) and Radio Network Controller (Radio Network) One combination of Controller; RNC for short. The downlink (DL) transmission may be from one of the nodes (eg, eNodeBs) to the wireless device (eg, UE), and the uplink (UL) transmission may be from one of the wireless devices to the node. .

110, 210, 310, 410, 510, 610, 710‧‧‧Evolved Node B

112, 212, 312, 412, 512, 612, 712‧‧‧ device A

114, 214, 314, 414, 514, 614, 714‧‧‧ device B

116, 216, 316, 416, 516, 616, 716‧‧‧ device C

118, 218, 318, 418, 518, 618, 718 ‧ ‧ device D

1100‧‧‧User equipment installation

1102‧‧‧Application Circuit

1104‧‧‧Base frequency circuit

1106‧‧‧RF circuit

1108‧‧‧ front-end module circuit

1110‧‧‧Antenna

1112‧‧‧ Storage media

1104a‧‧‧second generation baseband processor

1104b‧‧‧ third generation baseband processor

1104c‧‧‧ fourth generation baseband processor

1104d‧‧‧Other baseband processors

1104e‧‧‧Central Processing Unit

1104f‧‧‧Audio digital signal processor

1106a‧‧‧Mixer circuit

1106b‧‧‧Amplifier Circuit

1106c‧‧‧Filter circuit

1106d‧‧‧Synthesizer circuit

The features and advantages of the present invention will be readily apparent from the description of the appended claims. An example of a plurality of machine type communication (MTC) devices that transmit radio resource control (RRC) connection request information to an eNodeB; 2 shows, according to an example, a plurality of Machine Type Communication (MTC) devices that receive Radio Resource Control (RRC) Connection Rejection information from an eNodeB; FIG. 3 shows transmission of signaling information to a selected one according to an example. One or more machine type communication (MTC) devices of the MTC device; FIG. 4 illustrates a selected machine type communication (MTC) device for transmitting an acknowledgment to one or more MTC devices, according to an example; 5 shows, according to an example, a selected machine type communication (MTC) device that transmits a radio resource control (RRC) connection request message to an eNodeB; FIG. 6 shows one or more according to an example. The aggregated signaling information of the MTC device is transmitted to a selected machine type communication (MTC) device of an eNodeB; FIG. 7 illustrates an example of transmitting an accept or reject message to one or more MTC devices according to an example. Selected Machine Type Communication (MTC) device; Figure 8 illustrates the functionality of an eNodeB operable to facilitate aggregated signaling from a plurality of devices, according to an example; Figure 9 is illustrated as operable to aggregate according to an example Letter of multiple MTC devices A function of an aggregate machine type communication (MTC) device; FIG. 10 shows, according to an example, a machine readable file having contained instructions for transferring a small amount of data from a user equipment (UE) to an eNodeB A flow chart of one of the storage media taken; FIG. 11 shows a wireless device (eg, UE) according to an example One of the drawings; and FIG. 12 shows a diagram of a wireless device (e.g., UE) according to an example.

The embodiments have been described above with reference to the illustrated embodiments, and such embodiments have been described in the specific language. However, it should be understood that the scope of the present technology is not intended to be limited thereby.

SUMMARY OF THE INVENTION AND EMBODIMENT

Before the technology of the present invention is disclosed and illustrated, it is to be understood that the present invention is not limited to the specific structures, procedures, or materials disclosed in the present disclosure, but rather extended to those skilled in the art. The equivalent of a particular structure, procedure, or material. It should also be understood that the terms used in this specification are used for the purpose of illustrating particular examples, and such terms are not intended to be limiting. The same reference numbers in different drawings represent the same elements. Flowcharts and numbers provided in the program are provided for clarity of action and operation, and such numbers do not necessarily indicate a particular order or order.

Illustrative embodiment

A preliminary overview of one of the various technical embodiments will be provided below, and then some specific technical embodiments are described in further detail. This preliminary summary is intended to assist the reader in understanding the technology more quickly, and is not intended to identify important features or essential features of the technology, or to limit the scope of the claimed scope.

Equipment suppliers and mobile network operators have a great interest in Machine Type Communication (MTC) for a wide range of potential applications. MTC is a form of small amount of data communication between one or more entities that does not necessarily need to interact with people. An MTC device can communicate with each MTC server and/or other MTC device via a network. As a non-limiting example, the MTC device can include a health monitoring device, a smart meter, a sensor, and the like.

In one example, the MTC device can communicate (ie, transmit or receive) a small amount of data via the network. Such small amounts of data typically range from a few bits to thousands of bits of data. In a particular example, the length of the payload of a small amount of data can range from 1 to 128 bytes, but it should be understood that in some instances, the payload of a small amount of data may be larger. In general, a small amount of data is transmitted in the form of a short packet in a single packet or burst. The network may be a Wireless Wide Area Network (WWAN) or a Wireless Local Area Network (WLAN) according to a selected Radio Access Network (RAN) technology. The WWAN can be configured to operate in accordance with cellular network connectivity standards such as the 3rd Generation Partnership Project (3GPP). The illustrated versions of the 3GPP standard include 3GPP LTE, Release 8 (8th Edition) in the fourth quarter of 2008, 3GPP LTE Advanced Release 10 (10th Edition) in the first quarter of 2011, and 3GPP LTE in the third quarter of 2012. Release 11 (11th edition).

In an example, an MTC application executing on an MTC device can be associated with, for example, security (eg, surveillance system, driver safety), tracking and tracing (eg, asset tracking, navigation, traffic information) , road tolls), payments (eg, vending machines, game consoles), health (eg, monitoring vital signs, supporting elderly or disabled people), remote maintenance/control (eg, sensors) Related to lighting, vehicle diagnostics, metering (eg, electricity, gas, water, heating), and/or consumer devices (eg, digital cameras).

In a conventional LTE cellular system, a User Equipment (UE), which may include an MTC device, transmits Radio Resource Control (RRC) connection request information to an eNodeB for cellular communication from the eNodeB. Resources. However, when the network is blocked, the eNodeB can receive the RRC connection request information from the UEs, and the eNodeB can transmit the RRC connection reject information to the UEs when responding. The RRC Connection Reject message may include a backoff timer (or a wait timer) and a non-priority of the UE. The eNodeB can use different values for the backoff timer depending on the user, so the eNodeB can distribute the access load for a period of time. In addition, the backoff timer can be randomly distributed to distribute the initiation of access by these UEs to that period of time. By using the backoff timer, the eNodeB can prevent the UEs from further smashing the network. After the fallback timer expires, the UEs can initiate a connection to the network again. For example, the UEs can Another RRC Connection Request message is transmitted to the eNodeB in an attempt to establish a connection with the network.

However, one problem with this conventional LTE cellular system associated with MTC devices is signaling congestion control. Since the number of MTC devices in the network is expected to be large, the number of MTC devices that are connected to the network even after being woken up after the expiration of the backoff timer may still cause further congestion of the network. In the existing solution, the number of UEs connected to the network is relatively small, so the backoff timer mechanism is an effective solution, but the backoff timer is expected for a large number of MTCs in the next few years. The device will not be an effective solution.

In the technique of the present invention, in order to alleviate the above problems, a selected MTC device (also referred to as a phantom device) can aggregate signaling information from a plurality of MTC devices, and the selected MTC device Aggregate signaling information can be transmitted to the eNodeB. In other words, instead of individually providing signaling information to the eNodeB by each MTC device, each MTC device can transmit signaling information to the selected MTC device. The selected MTC device can aggregate the signaling information and then transmit the aggregate signaling information to the eNodeB. Thus, individual signaling from each MTC device to the eNodeB is prevented, thereby reducing congestion in the network.

More specifically, in the technique of the present invention, when a plurality of MTC devices transmit RRC connection request information to the eNodeB, the eNodeB may transmit RRC connection reject information to the plurality of MTC devices. Of course Instead, the eNodeB can select one of the plurality of MTC devices as the phantom device. For example, when the eNodeB transmits the RRC Connection Reject message to the selected MTC device (or phantom device), the eNodeB provides a configuration (eg, resource) that enables the selected MTC device to form a new cell. . The new cell formed by the selected MTC device may also be referred to as a shadow cell. The new cell (or shadow cell) formed by the selected MTC device may have a more limited ability than the cells formed by the eNodeB. In the RRC connection reject information transmitted from the eNodeB to other MTC devices (ie, other MTC devices that are not selected as the phantom device), the eNodeB may redirect the other MTC devices to the selected one. MTC device. In other words, the eNodeB can redirect the other MTC devices to camp on the new cells formed by the selected MTC device.

In an example, in the technique of the present invention, after the other MTC devices are connected to the new cell formed by the selected MTC device, each of the other MTC devices may have an RRC. The connection request information is transmitted to the selected MTC device (or phantom device). The communication between the other MTC devices and the selected MTC device (or phantom device) may be in the form of a Device To Device (D2D) communication. The selected MTC device (or phantom device) may aggregate the RRC connection request information from the other MTC devices to form aggregate signaling information, and the selected MTC device may transmit the aggregate signaling information to The eNodeB. In one case In the sub-device, the selected MTC device may concatenate or piggyback the aggregate signaling information with its own signaling information and/or a small amount of uplink data to be transmitted to the eNodeB.

In an example, in the technique of the present invention, the eNodeB can receive the aggregated signaling information from the selected MTC device, and the eNodeB can decide to accept or reject the RRC connection request from each of the other MTC devices. . The eNodeB may transmit accept or reject information to the selected MTC device, and the selected MTC device may forward the accept or reject information to the other MTC devices.

The increasing number of MTC devices in the next few years is likely to overload the network, and the current signaling congestion mechanism is not sufficient to deal with this problem. When using the techniques of the present invention, the LTE cellular system can support an increasing number of MTC devices without significantly delaying UL signaling and small amounts of UL data. When the technique of the present invention is used, the number of RRC connection requirements and the number of RRC connection replies per MTC device can be reduced. Furthermore, cellular information on the eNodeB can be saved by aggregating signaling information for a plurality of MTC devices on the selected MTC device (or phantom device).

Figure 1 shows an example of a plurality of User Equipments (UEs) such as Machine Type Communication (MTC) devices in a network. For example, the network can include an eNodeB 110 and some MTC devices. In a configuration, the user equipment (UE) may be substituted for the MTC devices. The MTC devices can form a cluster of devices that surround the eNodeB 110. These MTC devices may have low mobility delay tolerant uplink (UL) data and signals Order. In an example, each MTC device may transmit a Radio Resource Control (RRC) connection request message to the eNodeB 110.

In the example shown in FIG. 1, device A 112, device B 114, device C 116, and device D 118 may form an MTC device that surrounds the cluster of eNodeBs 110. Further, the device A 112, the device B 114, the device C 116, and the device D 118 can respectively transmit an RRC connection request information to the eNodeB 110 to connect to the network.

In a specific example, the RRC connection request information transmitted from each MTC device to the eNodeB 110 may be a Tracking Area Update (TAU) information. However, the MTC device can transmit other control signal information or data to the eNodeB 110. For example, the MTC device may transmit Non Access Stratum (NAS) information or upper layer application signaling information.

In an example, the MTC device may transmit RRC connection request information to the eNodeB 110 when the network is blocked. For example, when the amount of traffic on the eNodeB 110 exceeds a defined threshold, the network may be blocked.

Figure 2 shows an example of a plurality of Machine Type Communication (MTC) devices that receive Radio Resource Control (RRC) Connection Rejection information from an eNodeB 210. The eNodeB 210 may transmit an RRC connection reject message to the plurality of MTC devices in response to receiving an RRC connection request message from each MTC device as shown in FIG. 1. In an example, when the network is blocked, the eNodeB 210 can transmit the RRC connection reject information to the plurality of MTC devices.

In an example, it is not a retreat like the previous solution. The timer is included in the RRC connection reject information, but the eNodeB 210 can select one of the MTC devices as a phantom device. More specifically, the eNodeB 210 may transmit an RRC Connection Reject message to the selected MTC device (or phantom device), and the RRC Connection Reject message may include enabling the selected MTC device to form a new cell (also A configuration called a shadow cell). The configuration in the RRC Connection Rejection information transmitted to the selected MTC device may include a selected Elevated Universal Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency. Channel Number (EARFCN for short) and a selected Physical Cell Identifier (PCI). In other words, the selected EARFCN and the selected PCI enable the selected MTC device to form the new cell (or shadow cell). In addition, the eNodeB 210 can select the EARFCN and PCI for the selected MTC device (or phantom device) such that the EARFCN and PCI cause minimal interference with the cell operating frequency.

In one example, the new cells (or shadow cells) formed by the selected MTC device have a more limited ability than the cells formed by the eNodeB 210. The selected MTC device (or phantom device) that forms the new cell can broadcast a minimal set of information to allow other MTC devices to connect to the selected MTC device. For example, the selected MTC device may broadcast a primary information block (Master Information Block; short for allowing other MTC devices to connect to the selected MTC device. MIB), System Information Block 1 (SIB1), and System Information Block 2 (SIB2). Furthermore, the selected MTC device (or phantom device) forming the new cell may only be allowed to be connected by the other MTC devices and to transmit/receive data to the other MTC devices. The selected MTC device may not be able to perform the reselection, handover, and other cellular eNodeB capabilities. Therefore, a smaller and less capable device can also form the new cell. The new cell (or shadow cell) may be a less capable cell, but has sufficient capacity to perform data transfer. In some instances, the new cell can have enhanced/reduced ability depending on the selected MTC device that is hosting the new cell.

In an example, the eNodeB 210 can use various selection criteria when deciding which of the plurality of MTC devices is best suited to function as the phantom device. For example, the eNodeB 210 can select an MTC device based on the type of power source associated with the MTC device. If the MTC device is connected to a dedicated power source, the MTC device is more likely to be selected as the phantom device. In one configuration, each of the plurality of MTC devices can transmit capability information including one of various capabilities or characteristics (eg, type of power source) associated with the MTC device to the eNodeB 210, and the eNodeB 210 A particular MTC device can be selected to act as the phantom device and form the new cell (or shadow cell) based on the capability information received from the plurality of MTC devices. The capability information can be transmitted from the MTC devices to the eNodeB 210 during a connection procedure.

In an example, the capability information transmitted to the eNodeB 210 can indicate whether a particular MTC device is capable of forming a new cell (or hosting a new cell). The MTC device can use its own algorithm to determine if the MTC device is capable of forming the new cell. For example, the MTC device may set a flag to "true" or "false" in the capability information depending on whether the MTC device is capable of forming the new cell. In an example, the MTC device can set the flag to "true" based on the current battery status of the MTC device and/or can be based on a profit factor (eg, when a network operator provides compensation to the escrow) When the MTC device of the new cell is used, the MTC device can set the flag to "true".

In an example, other MTC devices (i.e., MTC devices that are not selected as the phantom device) may also receive an RRC Connection Reject message from the eNodeB 210. However, each RRC Connection Reject message may include a redirect to the new cell formed by the selected MTC device (or phantom device). The redirection in each RRC Connection Reject message may include an EARFCN and a PCI associated with the selected MTC device (or phantom device). In other words, including the EARFCN and the PCI, the other MTC devices can be enabled to redirect signaling to the selected MTC device instead of to the eNodeB 210. Additionally, each RRC Connection Reject message may include additional information that enables the selected MTC device to form the new cell.

As will be explained in more detail below, when redirected to the new cell, signaling from the other MTC devices will be redirected to or offloaded to the selected MTC device (or phantom device) instead of Being redirected Go to or offload to eNodeB 210. The selected MTC device can handle a number of signaling from such other MTC devices instead of being processed by the eNodeB 210. Thus, the amount of signaling to the eNodeB 210 is reduced, thereby reducing or mitigating congestion at the network.

In the example shown in FIG. 2, the plurality of MTC devices that receive an RRC connection reject message from the eNodeB 210, respectively, may include device A 212, device B 214, device C 216, and device D 218. The eNodeB 210 can select the device B 214 as the phantom device based on the capability information received from each of the device A 212, the device B 214, the device C 216, and the device D 218. Thus, the RRC Connection Reject message transmitted from eNodeB 210 to Device B 214 (phantom device) may include a new EARFCN and one of the values set to 500, PCI. Moreover, the RRC connection reject information transmitted from eNodeB 210 to each of device A 212, device C 216, and device D 218 can include a redirect to device B 214 (phantom device), wherein the redirect includes The new EARFCN and the PCI are set to a value of 500. Device A 212, device C 216, and device D 218 may be coupled to (or connected to) device B 214 (phantom device) in accordance with the redirection included in the RRC connection rejection information.

Figure 3 shows an example of one or more machine type communication (MTC) devices transmitting signaling to a selected MTC device. As described above, an eNodeB 310 can select an MTC device from a plurality of MTC devices to act as a phantom device, and the selected MTC device can form a new cell (or shadow cell) with limited capabilities. Other MTC devices (also That is, other MTC devices that are not selected as the phantom device can be connected to the selected MTC device. In other words, signaling from the other MTC devices can be redirected to the selected MTC device instead of being transmitted to the eNodeB 310. From the standpoint of such other MTC devices, signaling is communicated to the selected MTC device (or phantom device) in a manner similar to transmitting signaling to the eNodeB 310. Thus, in an example, the other MTC devices can each transmit an RRC connection request message to the selected MTC device (or phantom device). In a particular example, the other MTC devices can each transmit a Tracking Area Update (TAU) message to the selected MTC device (or phantom device). Instead of transmitting the TAU information to the eNodeB 310, the other MTC devices may transmit the TAU information directly to the selected MTC device, thereby reducing the amount of signaling on the eNodeB 310. In another example, the other MTC devices can transmit non-access stratum (NAS) information or upper layer application signaling information to the selected MTC device.

In the example shown in FIG. 3, device B 314 can be selected as the phantom device, and device B 314 can form the new cell with limited capabilities. Device A 312, device C 316, and device D 318 may be redirected by eNodeB 310 to communicate directly with device B 314 instead of communicating with eNodeB 310. Device A 312, device C 316, and device D 318 may each transmit a Tracking Area Update (TAU) message to Device B 314 (or a phantom device).

Figure 4 shows a selected machine type communication (MTC) device will An example of an acknowledgement being transmitted to one or more MTC devices. As described above, the selected MTC device (or phantom device) can receive signaling directly from the one or more MTC devices. The one or more MTC devices may transmit signaling to the selected MTC device instead of signaling to an eNodeB 410. For example, the selected MTC device (or phantom device) can receive a Tracking Area Update (TAU) message from each of the one or more MTC devices. In response, the selected MTC device (or phantom device) may transmit an acknowledgment (ACK) to each of the one or more MTC devices. In other words, the ACK is not an acknowledgment of the TAU, but an acknowledgement that the transmission of the TAU information is successful.

In the example shown in Figure 4, device B 414 can be selected as the phantom device, and device B 414 can form the new cell with limited capabilities. Device A 412, device C 416, and device D 418 can each transmit a Tracking Area Update (TAU) message to Device B 414 (or phantom device). In response, device B 414 (or phantom device) may transmit an acknowledgment (ACK) to each of device A 412, device C 416, and device D 418.

In a configuration, after the selected MTC device (phantom device) receives the signaling from the other MTC devices, the selected MTC device can signal together the one or more MTC devices. The signaling of the selected MTC device itself is aggregated or concatenated or piggybacked. For example, the selected MTC device may receive periodic TAU information received from the one or more MTC devices along with the periodicity of the selected MTC device itself. TAU information is aggregated or concatenated or piggybacked.

Figure 5 shows an example of a selected machine type communication (MTC) device transmitting a Radio Resource Control (RRC) connection request message to an eNodeB 510. The selected MTC device (or phantom device) may indicate a defined number of MTC devices in the RRC connection request information, wherein the defined number indicates that the selected MTC device is transmitting aggregated or concatenated or piggybacked signaling The number of MTC devices targeted by the information. In other words, one or more MTC devices may transmit signaling to the selected MTC device, and the selected MTC device may aggregate or concatenate or piggyback signaling from the one or more MTC devices, and the The selected MTC device can then indicate the number of MTC devices for which the selected MTC device is transmitting aggregated or concatenated or piggybacked signaling information.

In an example, the eNodeB 510 can receive the RRC connection request information from the selected MTC device (or phantom device) indicating the number of MTC devices for which the selected MTC device is transmitting aggregated signaling information. In response, the eNodeB 510 can perform an RRC connection setup with the selected MTC device, wherein the eNodeB 510 assigns an increased priority level to the signaling requirements received from the selected MTC device. In addition, the eNodeB 510 can allocate resources to receive the aggregated signaling information from the selected MTC device.

In the example shown in Figure 5, device B 514 can be selected as the phantom device, and device B 514 can form the new cell with limited capabilities. Device A 512, device C 516, and device D 518 may respectively A Tracking Area Update (TAU) message is transmitted to Device B 514 (or phantom device). Device B 514 (or phantom device) may transmit an RRC Connection Request message to eNodeB 510, where the RRC Connection Requirement information may indicate the number of MTC devices that will update the TAU. In other words, the RRC connection request information may indicate the number of MTC devices to which the device B 514 (phantom device) is transmitting the piggybacked TAU information. In this example, the RRC connection request information may indicate three MTC devices corresponding to device A 512, device C 516, and device D 518. The eNodeB 510 can initiate an RRC connection setup procedure in response to receiving the RRC connection request information with the device B 514 (or phantom device) to perform the TAU. In addition, eNodeB 510 can assign an increased priority level to the TAU information received from device B 514, and eNodeB 510 can allocate resources to receive the periodic TAU information.

Figure 6 shows an example of a selected machine type communication (MTC) device transmitting aggregated signaling information for one or more MTC devices to an eNodeB 610. As described above, the selected MTC device (or phantom device) can receive signaling information from one or more MTC devices, and the selected MTC device can be aggregated along with signaling of the selected MTC device itself. The signaling information. The eNodeB 610 can allocate resources to the selected MTC device, and the selected MTC device can use the resources to transmit aggregated signaling information to the eNodeB 610.

In an example, the aggregated signaling information can include periodic tracking area update (TAU) information for the one or more MTC devices, and periodic TAU information for the selected MTC device itself.

The eNodeB 610 can receive the aggregated signaling information from the selected MTC device. The eNodeB 610 may decide that it is receiving aggregate signaling information because the signaling information is from the selected MTC device (or phantom device). Since the eNodeB 610 knows that it is receiving aggregate signaling information and that the signaling received from the selected MTC device (or phantom device) is assigned the higher priority level, the eNodeB 610 is less likely to reject the aggregate signaling information. . The eNodeB 610 may receive the aggregated signaling information from the selected MTC device, and transmit an accept message or a reject message to each of the one or more MTC devices to the selected MTC. Device (or phantom device). In other words, for each MTC device, the eNodeB 610 can transmit an accept message indicating that the MTC device is allowed to connect to the eNodeB 610, or the eNodeB 610 can transmit a reject to indicate that the MTC device is not allowed to connect to the eNodeB 610 information. In an example, eNodeB 610 can transmit an acceptance message for all of the MTC devices that are requesting to connect to eNodeB 610. In another example, the eNodeB 610 can transmit an acceptance message for certain MTC devices while transmitting a rejection message for other MTC devices.

In the example shown in Figure 6, device B 614 can be selected as the phantom device, and device B 614 can form the new cell with limited capabilities. Device A 612, device C 616, and device D 618 can each transmit a Tracking Area Update (TAU) message to Device B 614 (or a phantom device). Device B 614 can aggregate the TAU information received from device A 612, device C 616, and device D 618, respectively, and aggregate the same The combined TAU information is transmitted to the eNodeB 610. In other words, device B 614 can piggyback the TAU information received from device A 612, device C 616, and device D 618 to the periodic TAU information of device B itself. After the device B 614 receives the aggregated TAU information, the eNodeB 610 can transmit an acceptance message or a rejection message to each of the device A 612, the device C 616, and the device D 618 to the device B 614, respectively. As a non-limiting example, eNodeB 610 can transmit an acceptance information for device A 612 and rejection information for device C 616 and device D 618 to device B 614.

Figure 7 shows an example of a selected machine type communication (MTC) device transmitting an accept or reject message to one or more MTC devices. As described above, the selected MTC device (or phantom device) may receive an accept or reject message from an eNodeB 710 for each of the one or more MTC devices. Thus, the selected MTC device can forward an acceptance or rejection message to each of the one or more MTC devices. Additionally, the selected MTC device can instruct each of the one or more MTC devices to detach from the selected MTC device (or phantom device). In other words, the one or more MTC devices can now be connected to the eNodeB 710 and there is no need to maintain a connection with the selected MTC device (or phantom device).

In the example shown in Figure 7, device B 714 can be selected as the phantom device, and device B 714 can form the new cell with limited capabilities. Device A 712, device C 716, and device D 718 may respectively A Tracking Area Update (TAU) message is transmitted to Device B 714 (or phantom device). Device B 714 can transmit aggregated TAU information to eNodeB 710, and eNodeB 710 can respond to an accept or reject message for each of device A 712, device C 716, and device D 718, respectively. Device B 714 (or phantom device) may forward the acceptance or rejection information to each of device A 712, device C 716, and device D 718, respectively. After receiving the acceptance or rejection information from device B 714, each of device A 712, device C 716, and device D 718 may be separated from device B 714 (or phantom device).

In one configuration, the one or more MTC devices may automatically attempt to perform a TAU with the selected MTC device (or phantom device) during a next cycle of performing periodic TAU signaling. In other words, the one or more MTC devices can automatically transmit the periodic TAU information to the selected MTC device (or phantom device), and the selected MTC device can aggregate the TAU information and aggregate The TAU information is passed to the eNodeB (as described above). If the one or more MTC devices are unsuccessful in transmitting the periodic TAU information to the selected MTC device (or phantom device), or if the selected MTC device is no longer configured as the phantom And the one or more MTC devices can directly transmit the periodic TAU information to the eNodeB.

In an example, the time period during which the selected MTC device continues to act as the phantom device is configured by the network. For example, the network can configure the selected MTC device to act as the phantom device for several hours. As another example, the network can configure the selected MTC device to be in daily Acting as a phantom device during a certain period of time.

In one configuration, the eNodeB can select a particular MTC device to act as a phantom device and form a new cell (or shadow cell). Other MTC devices can be redirected to the selected MTC device. For example, when the other MTC devices want to transmit uplink data (eg, sensor data, temperature data) to the eNodeB 710, the other MTC devices can transmit the data to the selected MTC device. . The selected MTC device can aggregate the data and then transmit the aggregated data to the eNodeB 710. Thus, the selected MTC device can aggregate uplink data from the other MTC devices in addition to aggregating signaling information (as described above). In other words, the selected MTC device can act as a relay between the other MTC devices and the eNodeB 710. By aggregating the data on the selected MTC device, the signaling overhead on the eNodeB 710 can be reduced, and/or the signaling burden can be more efficiently managed on the eNodeB 710.

As a non-limiting example, a group of MTC devices may transmit a Short Messaging Service (SMS) to the selected MTC device (or phantom device). The selected MTC device may aggregate the SMS messages received from the group of MTC devices and then transmit an aggregated SMS message to the eNodeB.

As another non-limiting example, a group of MTC devices can be configured to transmit a burst of data (eg, 100 packets) every 24 hours. Rather than transmitting the data directly to the eNodeB, the MTC devices can transmit the data to the selected MTC device (or phantom) Apparatus), and the selected MTC device can aggregate the data and transmit the aggregated data to the eNodeB.

In one configuration, the formation of the cells and the redirection to the cells can be accomplished via Radio Resource Control (RRC) reconfiguration messages. The RRC reconfiguration information can be used when the cell is formed in an ongoing call. For example, an eNodeB can communicate an RRC reconfiguration message to a selected MTC device, wherein the RRC reconfiguration information includes a configuration that causes the selected MTC device to form the cell. The cells formed by the selected MTC device may comprise a selected subset of MTC devices. In an example, the selected MTC device can form a lower capacity cell, wherein the selected MTC device is only configured to transmit a primary information block (MIB), a system information block 1 (SIB1) And one SIB2. Additionally, the eNodeB can transmit an RRC reconfiguration information to the selected subset of devices, wherein the RRC reconfiguration information includes redirection to one of the cells formed by the selected MTC device. In this configuration, instead of forming the cell using the RRC connection request/deny information and redirecting the selected subset of MTC devices to the selected MTC device, the eNodeB can utilize the RRC reconfiguration information. .

In one configuration, a series of actions can be performed on an eNodeB and one or more MTC devices to reduce signaling congestion on the eNodeB. In action 1, when the network is blocked, a plurality of co-located MTC devices may simultaneously initiate periodic TAU control signaling to the eNodeB. In action 2, the eNodeB can select this One of the MTC devices in the MTC device acts as a phantom device, and other MTC devices are redirected to the phantom device. In act 3, the other MTC devices can be coupled to the phantom device and transmit their periodic TAU information to the phantom device. In act 4, the phantom device may transmit an acknowledgment (ACK) for the periodic TAU information that has been received. In act 5, the phantom device may concatenate or piggyback the periodic TAU information of the other MTC devices along with the periodic TAU information of the phantom device itself. In act 6, the phantom device may transmit an RRC connection request for indicating the number of MTC devices for which the phantom device is transmitting the piggybacked TAU information to the eNodeB, and the eNodeB will be used to transmit the cycles Resources for sexual TAU information are provided to the phantom device. In act 7, the phantom device may transmit the piggybacked TAU information to the eNodeB, and the eNodeB may transmit a TAU accept message or a TAU reject message for each of the MTC devices. In act 8, the phantom device can transmit the received TAU accept/reject information and an instruction to separate the MTC devices from the phantom device to the MTC devices. In act 9, in a next cycle of performing periodic TAU control signaling, the MTC devices may first attempt to perform TAU using the phantom device.

As shown in the flow diagram of Figure 8, another example provides a function 800 of an eNodeB that is operable to facilitate aggregate signaling from a plurality of devices. The function can be implemented as a method, or the function can be executed as an instruction on a machine, wherein the instructions are included on at least one computer readable medium or a non-transitory machine readable storage medium . Such as a square 810, the eNodeB can include one or more processors and memory configured to: receive a connection request message from each of the plurality of devices on the eNodeB. As represented by block 820, the eNodeB can include one or more processors and memory configured to perform a process of selecting a device from the plurality of devices using a set of selection criteria on the eNodeB. As represented by block 830, the eNodeB can include one or more processors and memory configured to: transmit a connection rejection message to the selected device, the connection rejection information including the selected The device configures one of a cell of a device comprising a selected subset of the plurality of devices. As represented by block 840, the eNodeB can include one or more processors and memory configured to: communicate a connection rejection message to the selected subset, the connection rejection information being included One of the cells formed by the selected device is redirected, wherein each device in the selected subset is configured to transmit a connection request message to the selected device based on the redirection to the cell.

As shown in the flow chart of Figure 9, another example provides a function 900 of a Converged Machine Type Communication (MTC) device operable to aggregate signaling for a plurality of MTC devices. The function can be implemented as a method, or the function can be executed as an instruction on a machine, wherein the instructions are included in at least one computer readable medium or a non-transitory machine readable storage medium. As represented by block 910, the aggregated MTC device can include one or more processors and memory configured to perform the following operations: transmitting a connection request message to an eNodeB. As shown in block 920, the aggregation The MTC device can include one or more processors and memory configured to: receive a connection reject message from the eNodeB, the connection reject message including a configuration indicating that the aggregated MTC device forms a cell, wherein The eNodeB is configured to select the polymeric MTC device for forming the cell based on a set of selection criteria. As represented by block 930, the aggregated MTC device can include one or more processors and memory configured to: receive a connection from one or more MTC devices in the cell on the aggregated MTC device Information is requested wherein the eNodeB is configured to redirect control signaling from the one or more MTC devices in the cell to the aggregated MTC device. As represented by block 940, the aggregated MTC device can include one or more processors and memory configured to: transmit an aggregate connection request message from the aggregated MTC device, the aggregate connection request information being included from the cell The connection request information received by the one or more MTC devices.

As shown in the flowchart of FIG. 10, another example provides at least one machine readable storage medium having included instructions 1000 for transferring a small amount of data from a user equipment (UE) to an eNodeB. . The instructions can be executed on a machine, wherein the instructions are included in at least one computer readable medium or a non-transitory machine readable storage medium. As shown in block 1010, when the instructions are executed, the following operations are performed: receiving one Radio Resource Control (RRC) reconfiguration information from the eNodeB using one or more processors of the UE, wherein the RRC reconfiguration The information is redirected to one of the selected aggregated UEs that are hosting a cell, wherein the eNodeB is selected according to the capabilities of the selected aggregated UE The selected aggregated UE that hosts the cell. As indicated by block 1020, when the instructions are executed, the following operations are performed: transmitting data using one or more processors of the UE based on the redirection included in the RRC reconfiguration information received from the eNodeB To the selected aggregated UE, wherein the selected aggregated UE is configured to forward the data to the eNodeB.

Figure 11 provides such a wireless device, a mobile station (MS), a machine type communication (MTC) device, a mobile wireless device, a mobile communication device, a tablet computer, a mobile phone, or other type. One of the user equipment (UE) devices 1100 of the wireless device or the like is illustrated. The UE device 1100 may include one or more antennas, and the one or more antennas are configured to be associated with, for example, a base station (BS), an evolved Node B (eNB), and a baseband unit (Baseband Unit; Abbreviated as BBU), a wireless radio head device (RRH), a remote radio device (RRE), a relay station (RS), and a radio device (Radio Equipment). (referred to as RE), a remote radio unit (RRU), a central processing module (CPM), or other types of wireless wide area network (WWAN) access points, etc. Transport station communication. The UE device 1100 can be configured to communicate using at least one wireless communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and Wi-Fi. UE device 1100 can be used for each A separate antenna of a wireless communication standard or a shared antenna for a plurality of wireless communication standards. The UE device 1100 can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN.

In some embodiments, the UE device 1100 can include an application circuit 1102, a baseband circuit 1104, a radio frequency (RF) circuit 1106, and a front-end module (Front-End Module) that are coupled together at least as shown. FEM) circuit 1108, and one or more antennas 1110.

Application circuit 1102 can include one or more application processors. For example, application circuit 1102 can include circuitry such as, but not limited to, one or more single core or multi-core processors. The one or more processors can include any combination of general purpose processors and special purpose processors (eg, dedicated processors of graphics processors, application processors, etc.). The processors can be coupled to and/or can include a storage medium 1112 and can be configured to execute instructions stored in the storage medium 1112 to enable various applications and/or operating systems to operate on the system.

The baseband circuit 1104 can include circuitry such as, but not limited to, one or more single core or multi-core processors. The baseband circuit 1104 can include one or more baseband processors and/or control logic for processing the baseband signals received from a receive signal path of the RF circuitry 1106 and for generating a transmit signal path for the RF circuitry 1106. The fundamental frequency signal. The baseband circuit 1104 can interface with the application circuit 1102 to generate and process the baseband signals and control the operation of the RF circuitry 1106. For example, in some embodiments, the baseband power The path 1104 can include a second generation (2G) baseband processor 1104a, a third generation (3G) baseband processor 1104b, a fourth generation (4G) baseband processor 1104c, and/or for other existing generations, Other baseband processors 1104d of generations in development, or generations to be developed in the future (eg, generations of fifth generation (5G), 6G, etc.). The baseband circuitry 1104 (e.g., one or more baseband processors 1104a-d) can process various radio control functions capable of communicating with one or more radio networks via the RF circuitry 1106. The radio control functions may include, but are not limited to, functions of signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some embodiments, the modulation/demodulation circuit of the baseband circuit 1104 can include Fast Fourier Transform (FFT), precoding, and/or constellation mapping. /demapping) function. In some embodiments, the encoding/decoding circuitry of the baseband circuit 1104 can include convolution, tail-biting convolution, turbo, Viterbi, and/or low. Density Parity Check (LDPC) encoder/decoder function. Embodiments of the modulation/demodulation and encoder/decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

In some embodiments, the baseband circuit 1104 can include components of a protocol stack, such as elements of an Evolved Global Terrestrial Radio Access Network (EUTRAN) protocol, including, for example, physical layer (PHY), media access control. (Media Access Control; MAC for short), radio chain Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and/or Radio Resource Control (RRC) components. A Central Processing Unit (CPU) 1104e, one of the baseband circuits 1104, can be configured to operate elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP, and/or RRC layers. In some embodiments, the baseband circuit can include one or more Digital Signal Processors (DSPs) 1104f. The one or more audio DSPs 1104f may include elements for compression/decompression and echo cancellation, and may include other suitable processing elements in other embodiments. The components of the baseband circuit can be suitably combined in a single wafer or a single wafer set, or can be configured on the same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuit 1104 and the application circuit 1102 can be implemented together in, for example, a System on a Chip (SoC).

In some embodiments, the baseband circuit 1104 can provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 1104 can support an evolved Global Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Network (WMAN), a wireless area network. Communication between the road (WLAN) and the wireless personal area network (WPAN). Embodiments in which the baseband circuit 1104 is configured to support more than one wireless protocol for radio communication may be referred to as a multi-mode baseband circuit.

The RF circuit 1106 is capable of using modulated electromagnetic waves through a non-solid medium Radiation and communication with the wireless network. In various embodiments, RF circuitry 1106 can include components for facilitating communication, communication, and the like, switches, filters, amplifiers, and the like. The RF circuit 1106 can include a receive signal path that can include circuitry for down-converting the RF signal received from the FEM circuit 1108 and providing the baseband signal to the baseband circuit 1104. The RF circuit 1106 can also include a transmit signal path that can include up-converting the baseband signal provided by the baseband circuit 1104 and providing the RF output signal to the FEM circuit 1108 for transmission. Circuit.

In some embodiments, RF circuit 1106 can include a receive signal path and a transmit signal path. The receive signal path of RF circuit 1106 can include mixer circuit 1106a, amplifier circuit 1106b, and filter circuit 1106c. The transmit signal path of RF circuit 1106 can include filter circuit 1106c and mixer circuit 1106a. The RF circuit 1106 can also include a synthesizer circuit 1106d for synthesizing the received signal path and the frequency used by the mixer circuit 1106a of the transmitted signal path. In some embodiments, the mixer circuit 1106a of the receive signal path can be configured to downconvert the radio frequency signal received from the FEM circuit 1108 based on the synthesized frequency provided by the synthesizer circuit 1106d. Amplifier circuit 1106b can be configured to amplify the down-converted signals, and filter circuit 1106c can be a low pass filter configured to remove unwanted signals from the down-converted signals to produce an output baseband signal (Low) -Pass Filter; referred to as LPF) or Band-Pass Filter (BPF). The output baseband signal can be provided to the baseband circuit 1104 for further processing. In some embodiments The output baseband signals may be zero frequency baseband signals, but this is not a requirement. In some embodiments, the mixer circuit 1106a that receives the signal path can include a passive mixer, although the scope of the embodiments is not limited in this respect.

In some embodiments, the transmit signal path mixer circuit 1106a can be configured to upconvert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1106d to generate a RF output signal for the FEM circuit 1108. . The baseband circuit 1104 can provide the baseband signals, and the baseband signals can be filtered by the filter circuit 1106c. Filter circuit 1106c may include a low pass filter (LPF), although the scope of such embodiments is not limited in this respect.

In some embodiments, the mixer circuit 1106a of the receive signal path and the mixer circuit 1106a of the transmit signal path may comprise two or more mixers, and may be for quadrature downscaling, respectively. Down-conversion) and/or upsizing is scheduled. In some embodiments, the mixer circuit 1106a of the receive signal path and the mixer circuit 1106a of the transmit signal path may comprise two or more mixers and may be for image rejection ( For example, Hartley inage rejection is arranged. In some embodiments, the mixer circuit 1106a of the receive signal path and the mixer circuit 1106a of the transmit signal path can be directed to direct down-conversion and/or direct up-- Conversion ) is arranged. In some embodiments, the mixer circuit 1106a of the receive signal path and the mixer circuit 1106a of the transmit signal path can be pinned. Configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, but the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternative embodiments, the RF circuit 1106 may include an Analog-to-Digital Converter (ADC) and a Digital-to-Analog Converter (DAC) circuit, and the fundamental frequency Circuitry 1104 can include a digital baseband interface for communicating with RF circuitry 1106.

In some dual mode embodiments, individual radio IC circuits for processing signals for each spectrum may be provided, although the scope of such embodiments is not limited in this respect.

In some embodiments, the synthesizer circuit 1106d can be a fractional-N synthesizer or a fractional N/N+1 synthesizer, but such implementations The scope of the examples is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 1106d can be a delta-sigma synthesizer, a frequency multiplier, or a phase-locked loop having a frequency divider. One of the synthesizers.

Synthesizer circuit 1106d can be configured to synthesize one of the output frequencies used by mixer circuit 1106a of RF circuit 1106 based on a frequency input and a frequency divider control input. In some embodiments, the synthesizer circuit 1106d It can be a fractional N/N+1 synthesizer.

In some embodiments, a frequency input can be provided by a Voltage Controlled Oscillator (VCO), but this is not a requirement. The baseband circuit 1104 or application processor 1102 can provide a divider control input based on the desired output frequency. In some embodiments, a divider control input (eg, N) can be determined from a look-up table based on a channel indicated by application processor 1102.

The synthesizer circuit 1106d of the RF circuit 1106 can include a frequency divider, a Delay Locked Loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider can be a Dual Modulus Divider (DMD), and the phase accumulator can be a Digital Phase Accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by N or N+1 (eg, according to carry out) to provide a fractional division ratio. In some embodiments, the DLL can include a set of tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. (D-type flip-flop). In these embodiments, the delay elements can be configured to divide a VCO period into phases of Nd equal packets, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback, which helps to ensure that the delay is passed. The total delay of the late line is a VCO period.

In some embodiments, synthesizer circuit 1106d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (eg, twice the carrier frequency, four The carrier frequency is doubled, and the output frequency can be used in conjunction with the quadrature generator and the divider circuit to produce a plurality of signals having a plurality of different phases with respect to each other at the carrier frequency. In some embodiments, the output frequency can be a local oscillator frequency (LO frequency; abbreviated as fLO). In some embodiments, RF circuit 1106 can include an IQ/polar coordinate converter.

FEM circuit 1108 can include a receive signal path, which can include circuitry configured to: operate on radio frequency signals received from one or more antennas 1110; amplify the received signals; The amplified received signals are provided to RF circuit 1106 for further processing. The FEM circuit 1108 can also include a transmit signal path, which can include a signal configured to transmit the signal provided by the RF circuit 1106 for transmission for transmission by one or more of the one or more antennas 1110 The circuit.

In some embodiments, FEM circuit 1108 can include a TX/RX switch for switching between transmission mode and receive mode operation. The FEM circuit can include a receive signal path and a transmit signal path. The received signal path of the FEM circuit may include a Low Noise Amplifier (LNA) for amplifying the received RF signal and providing the amplified RF signal as an output (eg, For example, output to RF circuit 1106). The transmission signal path of the FEM circuit 1108 can include: a power amplifier (PA) for amplifying (such as provided by the RF circuit 1106) an input RF signal, and for generating a radio frequency signal for (such as the one or One or more of the plurality of antennas 1110 perform one or more filters for subsequent transmissions.

Figure 12 provides an illustration of one of a wireless device such as a User Equipment (UE), a Mobile Station (MS), a mobile wireless device, a mobile communication device, a tablet, a mobile phone, or other type of wireless device. figure. The wireless device can include one or more antennas configured to interface with a node, a macro node, a low power node (LPN), or a base station (such as a base station) BS), an evolved Node B (eNB), a Baseband Processing Unit (BBU), a Wireless Wide Header (RRH), a Remote Radio (RRE), and a Repeater (RS) ), a radio (RE), or other type of wireless wide area network (WWAN) access point, etc. The wireless device can be configured to communicate using at least one wireless communication standard such as, but not limited to, 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device can communicate using a separate antenna for each wireless communication standard or a shared antenna for multiple wireless communication standards. The wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN. The wireless device can also include a wireless data unit. The wireless data machine can include, for example, a wireless radio A transceiver and a baseband circuit (eg, a baseband processor). In an example, the wireless data modem can modulate a signal transmitted by the wireless device via the one or more antennas and can demodulate the wireless device via a signal received by the one or more antennas.

Figure 12 also provides a diagram of one of the microphones and one or more speakers that can be used for audio input and output from the wireless device. The display screen can be a liquid crystal display (LCD) screen or other types of display screens such as an Organic Light Emitting Diode (OLED) display. The display screen can be configured as a touch screen. The touch screen can use capacitive technology, resistive technology, or another type of touch screen technology. An application processor and a graphics processor can be coupled to internal memory to provide processing and display functions. A non-volatile memory cartridge can also be used to provide data input/output options to the user. The non-volatile memory cartridge can also be used to expand the memory function of the wireless device. A keyboard can be integrated into the wireless device or wirelessly connected to the wireless device to provide additional user input. A touch keyboard can also be used to provide a virtual keyboard.

example

The examples below are for specific technical embodiments and are indicative of specific features, elements, or acts that may be used or otherwise combined in the practice of the embodiments.

Example 1 contains an operative to facilitate aggregation from a plurality of devices a device for signaling an eNodeB, the device comprising one or more processors and memory configured to: receive a connection request message from each of the plurality of devices on the eNodeB; use on the eNodeB a set of selection criteria for selecting a device from the plurality of devices; transmitting a connection rejection message to the selected device, the connection rejection information comprising causing the selected device to be formed to include one of the plurality of devices selected a configuration of one of a cell of the device of the subset; and means for transmitting a connection rejection message to the selected subset, the connection rejection information being redirected to one of the cells formed by the selected device, wherein Each device in the selected subset is configured to transmit a connection request message to the selected device based on the redirection to the cell.

Example 2 includes the apparatus of example 1, further configured to: receive an aggregate connection request message from the selected device, the aggregate connection request information including the connection request information for each device in the selected subset; Transmitting an acceptance message or a rejection message to each selected device in the selected subset, wherein the selected device is configured to forward the acceptance information or the rejection information to the selected device Each device in the subset.

Example 3 The apparatus of any of examples 1-2, further configured to: receive a connection request message from the selected device, the connection request information indicating that the selected device transmits connection request information to the eNodeB The number of devices targeted to the selected subset; and transmitting a connection establishment message to the selected device, the connection establishment information including an aggregate connection request message for transmitting the selected subset of devices One of the resources of interest.

Example 4 includes the apparatus of any of examples 1-3, wherein the aggregated connection request information received on the eNodeB from the selected device is prioritized over other received on the eNodeB from other devices in a network Connection request information.

Example 5 includes the apparatus of any of examples 1-4, further configured to: select the device from the plurality of devices based on a capability information received from the device, wherein the capability information indicates association with the device The type of power supply.

Example 6 includes the apparatus of any of examples 1-5, further configured to: select the device from the plurality of devices based on a capability information received from the device, wherein the capability information indicates that the device is capable of forming the device cell.

Example 7 includes the apparatus of any of Examples 1-6, further configured to: receive information from the selected subset of devices on the eNodeB via the selected device, wherein the selected sub- The set of devices is configured to transmit the data to the selected device based on the redirection to the cell formed by the selected device, wherein the selected device is configured to forward the aggregated data to the eNodeB .

Example 8 includes the apparatus of any of examples 1-7, wherein the configuration of the connection rejection information transmitted to the selected device comprises at least one of: for the selected A selected Evolutionary Global Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN), a selected Entity Cell Identification Number (PCI), And additional information for forming the cells.

Example 9 includes the apparatus of any of examples 1-8, wherein the connection rejection information of the device transmitted to the selected subset comprises a selected evolved global ground associated with the selected device An Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN) and a selected Physical Cell Identification Number (PCI), wherein the connection rejection information includes system information associated with the redirection.

Example 10 includes the apparatus of any of examples 1-9, wherein the acceptance information or the rejection information of each of the selected subsets transmitted to the selected device is included for the selected The subset of devices is commanded by one of the devices selected from the selected device.

Example 11 includes the apparatus of any of examples 1-10, wherein the connection request information received from each of the plurality of devices is one of: information of a tracking area update (TAU) information, Non-access stratum (NAS) information, or an upper layer application signaling information.

Example 12 includes the apparatus of any of examples 1-11, wherein the connection request information and the connection rejection information are Radio Resource Control (RRC) information.

Example 13 includes the apparatus of any of examples 1-12, wherein the eNodeB is operative to configure the defined device to form the cell during network congestion.

Example 14 includes the apparatus of any of examples 1-13, wherein the selected device is a machine type communication (MTC) device.

Example 15 contains a letter that is operable to aggregate a plurality of MTC devices A device of an aggregated machine type communication (MTC) device, the device including one or more processors and memory configured to: transmit a connection request message to an eNodeB; receive a connection reject message from the eNodeB, The connection reject message includes a configuration indicating that the aggregated MTC device forms a cell, wherein the eNodeB is configured to select the aggregated MTC device for forming the cell according to a set of selection criteria; receiving from the aggregated MTC device a connection request message for one or more MTC devices in the cell, wherein the eNodeB is configured to redirect control signaling from the one or more MTC devices in the cell to the aggregated MTC device; and from the aggregation The MTC device transmits an aggregate connection request message containing the connection request information received from the one or more MTC devices in the cell.

Example 16 includes the device of example 15, further configured to: receive an accept message or a reject message for each of the one or more MTC devices from the eNodeB; and forward the accept message or the reject message To each of the one or more MTC devices.

Example 17 includes the apparatus of any of examples 15-16, further configured to: responsive to the connection request information received from the one or more MTC devices, to transmit an acknowledgment (ACK) from the aggregated MTC device to The one or more MTC devices.

Example 18 includes the apparatus of any of examples 15-17, further configured to: transmit a connection request message to the eNodeB, the connection request information indicating that the aggregated MTC device transmits connection request information to the eNodeB The number of MTC devices; and from the eNodeB A connection setup message is received, the connection setup information including one of resources for transmitting the aggregate connection request information from the aggregated MTC device to the eNodeB.

Example 19 includes the apparatus of any of examples 15-18, further configured to: directly receive additional connection request information from the one or more MTC devices, wherein the one or more MTC devices are configured to skip the The eNodeB also transmits additional connection request information directly to the aggregated MTC device.

Example 20 includes the apparatus of any of examples 15-19, further configured to: communicate a capability information to the eNodeB, the capability information indicating a type of power source associated with the aggregated MTC device, wherein the eNodeB is configured The polymeric MTC device used to form the cells is selected based in part on the capability information received from the polymeric MTC device.

Example 21 includes the apparatus of any of examples 15-20, wherein the configuration in the connection rejection information received from the eNodeB includes an evolved global terrestrial radio access (E) selected for use in one of the aggregated MTC devices -UTRA) Absolute RF channel number (EARFCN) and a selected physical cell identifier (PCI).

Example 22 includes the apparatus of any of examples 15-21, wherein the aggregated connection request information includes a connection request information associated with the aggregated MTC device.

Example 23 includes the apparatus of any of examples 15-22, wherein the connection request information received from each of the one or more MTC devices is a Tracking Area Update (TAU) message.

Example 24 includes the apparatus of any of examples 15-23, further configured to: receive data from the one or more MTC devices, wherein the one or more MTC devices are configured to be formed by the aggregated MTC device One of the cells is redirected to transmit data for the eNodeB to the aggregated MTC device; and the data is forwarded from the aggregated MTC device to the eNodeB.

Example 25 includes the apparatus of any of examples 15-24, wherein the polymeric MTC device forms a lower capacity cell, and the polymeric MTC device is configured to transmit only a primary information block (MIB), a system information Block 1 (SIB1), and a SIB2.

Example 26 includes at least one machine readable storage medium having instructions embodied thereon for transmitting a small amount of data from a user equipment (UE) to an eNodeB, and when the instructions are executed, the following operations are performed: Receiving, by the one or more processors of the UE, a Radio Resource Control (RRC) reconfiguration information from the eNodeB, wherein the RRC reconfiguration information includes redirecting to one of the selected aggregated UEs that are hosting a cell And wherein the eNodeB selects the selected aggregated UE for hosting the cell according to the capability of the selected aggregated UE, and the eNodeB indicates that the selected aggregated UE is transmitted according to the selected aggregate from the eNodeB One of the UEs RRC reconfigures the information to host the cell; and one or more processors using the UE transmit a small amount of data via a device-to-device (D2D) connection between the UE and the selected aggregated UE Go to the selected aggregated UE, wherein the small amount of data is transmitted to the RRC reconfiguration information received from the eNodeB The selected aggregated UE, wherein the selected aggregated UE is configured to forward the small amount of data to the eNodeB.

Example 27 includes the at least one machine readable storage medium of example 26, wherein the redirect received from the eNodeB includes an evolved global terrestrial radio access (E- selected) associated with the selected aggregated UE UTRA) Absolute RF Channel Number (EARFCN) and a selected Entity Cell Identification Number (PCI).

Example 28 includes the at least one machine readable storage medium of any of Examples 26-27, wherein the UE and the selected aggregated UE are Machine Type Communication (MTC) devices.

The example 29 includes the at least one machine readable storage medium of any one of the examples 26-28, wherein the UE comprises an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application At least one of a processor, a baseband processor, an internal memory, a non-volatile memory, and a combination of the above.

Various techniques, or certain aspects or portions of such techniques, may be employed in a storage medium such as a floppy disk, a CD-ROM, a hard disk drive, a non-transitory computer readable storage, or any other machine readable medium. Taking the form of a code (ie, an instruction) implemented in a physical medium such as a storage medium, wherein when the code is loaded and executed by a machine such as a computer, the machine becomes used to implement the various One of the technologies of the device. The non-transitory computer readable storage medium may be a computer readable storage medium that does not contain signals. In the case of executing a code in a programmable computer, the computing device can include a processor that reads a storage medium (including volatiles and Non-volatile memory and/or storage element), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage element may be a Random Access Memory (RAM) or Erasable Programmable Read Only Memory (EPROM). ), flash discs, CD players, magnetic hard drives, solid state drives, or other media used to store electronic data. The node and the wireless device can also include a transceiver module (ie, a transceiver), a counter module (ie, a counter), a processing component (ie, a processor), and/or a clock component ( That is, the clock) or the timer component (ie, the timer). An interface of an Application Programming Interface (API) and reusable controls may be implemented or utilized by one or more of the various techniques described herein. These programs can be implemented in a high-level program or object-oriented programming language to communicate with a computer system. However, the one or more programs may be implemented in a combination of language or machine language, if desired. In any event, the language can be a compiled or literal language and can be combined with hardware embodiments.

In the usage of the present specification, the term "circuit" may mean the following or may be part of the following or may include the following: Application Specific Integrated Circuit (ASIC), electronic circuit, A processor (shared, dedicated, or group processor) and/or memory (shared, dedicated, or group memory) or combinational logic circuit that executes one or more software or firmware programs And/or provide the required functionality His proper hardware components. In some embodiments, the circuitry may be implemented in one or more software or firmware modules, or the functions associated with the circuitry may be implemented in one or more software or firmware modules. In some embodiments, the circuitry can include logic that can be at least partially hardware operable.

It should be understood that many of the functional units referred to in this specification have been referred to as modules to more specifically emphasize the independence of their implementation. For example, a module can be implemented as one of the ready-made semiconductor hardware circuits including a custom Very Large Scale Integration (VLSI) circuit or gate array, such as a logic chip, a transistor, or other discrete components. . A module can also be implemented by a programmable hardware device such as a field programmable gate array, programmable array logic, or programmable logic device.

It is also possible to implement modules in software that can be executed by various types of processors. A module of an identified executable code can include computer instructions, such as one or more entities or logical blocks, which can be organized, for example, as an object, program, or function. However, the executable code of an identified module may not be physically located in one place, but may contain some different instructions stored in different locations, and when the instructions are logically combined, The module is included and the stated purpose of the module is achieved.

Indeed, one of the executable code modules can be a single instruction or many instructions, and can even be spread across several different code segments, dispersed in different programs, and spanning several memory devices. . Likewise, the operational materials of the present invention can be identified and shown in some modules, and the operational data can be implemented in any suitable form and organized within any suitable type of data structure. Such operational data Collecting as a single data set, or dispersing the operational data in different locations including different storage devices, and such operational data may exist, at least in part, in the form of electronic signals on a system or network. The modules can be passive or active, including a proxy module that is operable to perform the required functions.

Reference is made to the "an example" or "an" or "an" or "an" or "an" or "an" Therefore, when the words "in an example" or "an"

In the usage of this specification, a plurality of items, structural elements, component elements, and/or materials may be presented in a common list for convenience. However, these lists should be interpreted in such a way that each member of the list is individually identified as a separate and unique member. Therefore, the individual members of such a list should not be presented in a common group based on the fact that, in the absence of the contrary indication, the de facto equivalent of interpreting individual members of such list as any other member of the same list Things. Further, in the description of the embodiments and examples of the present technology, reference may be made to the alternatives of the components of the embodiments. It is to be understood that the examples, examples, and alternatives are not to be construed as a

Furthermore, in one or more embodiments, the features, structures, or characteristics shown may be combined in any suitable manner. In the foregoing description, many specific details such as layout examples, distances, network examples, etc. are provided. In order to provide a thorough understanding of the embodiments of the present technology. It will be appreciated by those skilled in the art, however, that the invention may be practiced without one or more specific details of the specific details, or may be practiced with other methods, components, or arrangements. The technology of the invention. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring the inventive aspects.

Although the foregoing examples illustrate the principles of the techniques of the present invention in one or more specific applications, it will be apparent to those skilled in the art that the present invention may be practiced without the use of a Many modifications in form, use, and details of the implementation are made in the light of the principles and concepts of the invention. Therefore, the technology of the present invention is not intended to be limited except as limited by the scope of the appended claims.

110‧‧‧Evolved Node B

112‧‧‧Device A

114‧‧‧Device B

116‧‧‧Device C

118‧‧‧Device D

Claims (29)

An apparatus operable to facilitate aggregation of signaling from a plurality of devices, the device comprising one or more processors and memory configured to receive each of the plurality of devices on the eNodeB a connection request message; selecting a device from the plurality of devices on the eNodeB using a set of selection criteria; transmitting a connection rejection message to the selected device, the connection rejection message comprising forming the selected device Configuring one of a cell of the device comprising the selected subset of the plurality of devices; and means for transmitting a connection rejection message to the selected subset, the connection rejection information being included by the selected One of the cells formed by the device is redirected, wherein each device in the selected subset is configured to transmit a connection request message to the selected device based on the redirection to the cell. The device of claim 1, wherein the device is further configured to: receive, from the selected device, an aggregate connection request information, the aggregate connection request information including the connection request information of each device in the selected subset; And transmitting, to the selected device, an acceptance information or a rejection information for each of the selected subsets, wherein the selected device is configured to forward the acceptance information or the rejection information to the selected device Each device in the selected subset. The device of claim 1, wherein the device is further configured to: receive, from the selected device, a connection request message indicating that the selected device transmits the connection request information to the eNodeB for the The number of devices in the selected subset; and transmitting a connection establishment message to the selected device, the connection establishment information including one of the resources of the aggregate connection request information for transmitting the selected subset of devices. The device of claim 1, wherein the aggregated connection request information received on the eNodeB from the selected device is prioritized over other connection request information received on the eNodeB from other devices in a network. The device of claim 1 is further configured to: select the device from the plurality of devices based on a capability information received from the device, wherein the capability information indicates a type of power source associated with the device. The device of claim 1, wherein the device is further configured to: select the device from the plurality of devices based on a capability information received from the device, wherein the capability information indicates that the device is capable of forming the cell. The apparatus of claim 1, further configured to: receive information from the selected subset of devices on the eNodeB via the selected device, wherein the selected subset of devices are configured The data is transmitted to the selected device based on the redirection to the cell formed by the selected device, wherein the selected device is configured to forward the aggregated data to the eNodeB. The apparatus of claim 1, wherein the configuration of the connection rejection information transmitted to the selected device comprises at least one of: a selected one for the selected device Evolution of the Global Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN), a selected Physical Cell Identification Number (PCI), and additional information used to form the cell. The device of claim 1, wherein the connection rejection information of the device transmitted to the selected subset comprises a selected evolved global terrestrial radio access associated with the selected device (E) - UTRA) Absolute Radio Frequency Channel Number (EARFCN) and a selected Physical Cell Identification Number (PCI), wherein the connection rejection information contains system information associated with the redirection. The apparatus of claim 1, wherein the acceptance information or the rejection information of each of the selected subsets transmitted to the selected device comprises means for the selected subset An instruction is separated from the selected device. The device of claim 1, wherein the connection request information received from each of the plurality of devices is one of the following information: a Tracking Area Update (TAU) message, a non-access layer ( NAS) information, or an upper layer application signaling information. The device of claim 1, wherein the connection request information and the connection rejection information are Radio Resource Control (RRC) information. The device of claim 1, wherein the eNodeB is operable to configure the defined device to form the fine during network congestion Cell. The apparatus of claim 1, wherein the selected device is a machine type communication (MTC) device. An apparatus for an aggregated machine type communication (MTC) device operable to aggregate signaling of a plurality of MTC devices, the device including one or more processors and memory configured to: transmit a connection request message to an eNodeB Receiving, from the eNodeB, a connection reject message, the connection reject message including a configuration indicating that the aggregated MTC device forms a cell, wherein the eNodeB is configured to select the aggregated MTC for forming the cell according to a set of selection criteria Means receiving, on the aggregated MTC device, connection request information from one or more MTC devices in the cell, wherein the eNodeB is configured to weight control signaling from the one or more MTC devices in the cell Directing to the aggregated MTC device; and transmitting an aggregate connection request message from the aggregated MTC device, the aggregate connection request information including the connection request information received from the one or more MTC devices in the cell. The device of claim 15 is further configured to: receive an acceptance information or a rejection information from each of the one or more MTC devices from the eNodeB; and the acceptance information or the rejection Information is forwarded to each of the one or more MTC devices. The device of claim 15 is further configured to: respond to the connection request information received from the one or more MTC devices, and transmit an acknowledgement (ACK) from the aggregated MTC device to the one or more MTC device. The device of claim 15 is further configured to: transmit a connection request information to the eNodeB, the connection request information indicating a number of the MTC devices to which the aggregated MTC device transmits the connection request information to the eNodeB; And receiving, from the eNodeB, a connection setup message, the connection setup information including one of resources for transmitting the aggregate connection request information from the aggregated MTC device to the eNodeB. The device of claim 15 is further configured to: directly receive additional connection request information from the one or more MTC devices, wherein the one or more MTC devices are configured to skip the eNodeB and add additional The connection request information is directly transmitted to the aggregated MTC device. The device of claim 15 is further configured to: transmit a capability information to the eNodeB, the capability information indicating a type of power source associated with the aggregated MTC device, wherein the eNodeB is configured to be partially based on The capability information received by the polymeric MTC device selects the polymeric MTC device used to form the cell. The device of claim 15, wherein the configuration in the connection rejection information received from the eNodeB includes an evolved global terrestrial radio access (E- selected for one of the aggregated MTC devices) UTRA) Absolute RF Channel Number (EARFCN) and a selected Entity Cell Identification Number (PCI). The device of claim 15 wherein the aggregated connection request information includes a connection request information associated with the aggregated MTC device. The device of claim 15 wherein the connection request information received from each of the one or more MTC devices is a Tracking Area Update (TAU) message. The apparatus of claim 15 further configured to: receive data from the one or more MTC devices, wherein the one or more MTC devices are configured to be weighted according to one of the cells formed by the polymeric MTC device Orienting to transmit data for the eNodeB to the aggregated MTC device; and forwarding the data from the aggregated MTC device to the eNodeB. The device of claim 15, wherein the polymeric MTC device forms a lower capacity cell, and the polymeric MTC device is configured to transmit only one primary information block (MIB) and one system information block 1 (SIB1). ), and one SIB2. A non-transitory machine readable storage medium having instructions embodied thereon for transmitting a small amount of data from a User Equipment (UE) to an eNodeB, when the instructions are executed, performing the following operations: using the UE One or more processors receive a Radio Resource Control (RRC) reconfiguration information from the eNodeB, wherein the RRC reconfiguration The information is redirected to one of the selected aggregated UEs that are hosting a cell, wherein the eNodeB selects the selected aggregated UE for hosting the cell based on the capabilities of the selected aggregated UE, and the eNodeB Instructing the selected aggregated UE to host the cell based on RRC reconfiguration information transmitted from the eNodeB to the selected aggregated UE; and selecting, by the UE, one or more processors using the UE A device-to-device (D2D) connection between the aggregated UEs transmits a small amount of data to the selected aggregated UE, wherein the small one is small according to the redirection included in the RRC reconfiguration information received from the eNodeB The quantity data is transmitted to the selected aggregated UE, wherein the selected aggregated UE is configured to forward the small amount of data to the eNodeB. A non-transitory machine readable storage medium as claimed in claim 26, wherein the redirect received from the eNodeB comprises an evolved global terrestrial radio access selected in association with the selected aggregated UE ( E-UTRA) Absolute RF channel number (EARFCN) and a selected physical cell identifier (PCI). A non-transitory machine readable storage medium as claimed in claim 26, wherein the UE and the selected aggregated UE are machine type communication (MTC) devices. The non-transitory machine readable storage medium of claim 26, wherein the UE comprises an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, and a base. At least one of a frequency processor, an internal memory, a non-volatile memory, and a combination of the above.