HK1177372B - Method and apparatus for supporting machine-type communications - Google Patents

Description

Method and apparatus for supporting machine type communication

Cross Reference to Related Applications

This application claims the benefit of U.S. provisional application No.61/304,383 filed on 12.2.2010, the contents of which are incorporated herein by reference.

Background

Machine Type Communication (MTC) is a communication involving one or more entities that do not necessarily require human interaction. MTC may involve a large number of communicating MTC devices (i.e., wireless transmit/receive units (WTRUs) equipped for MTC) that have no or a small amount of traffic destined for the MTC device (e.g., a sensor network). MTC devices may be battery operated, thus saving battery consumption and allowing longer operation without manual intervention.

In MTC, in some use cases, devices may be required to support mobile-originated-only communications (e.g., metering systems that periodically report measurements). In this case, it is desirable that the device can initiate or receive calls, even when the device is in idle mode, the network should know the location of the device (i.e. in which cell or area the device is located) so that when a call needs to be made to that device, the call can be completed in a timely manner. However, if a device only makes a call and never receives a call, the location of the device becomes less important because the network does not need to find the device. In other use cases, the device may be required to support infrequent mobile-terminated communications (e.g., to support a metering system for devices polled by the network).

Disclosure of Invention

Methods and apparatus for supporting machine type communications are disclosed. The WTRU may configure itself to operate in a mobile-originated-only mode based on the trigger. The WTRU may not perform Radio Resource Control (RRC) idle and/or non-access stratum (NAS) idle/standby state procedures, or a subset thereof, in the mobile-originated-only mode. For example, the WTRU may perform cell reselection in a mobile-originated-only mode but not perform paging monitoring. Alternatively, the WTRU may perform paging monitoring but not cell reselection and location update. Operation in the mobile-originated-only mode may be triggered explicitly or implicitly. For example, the WTRU may initiate operation in a mobile-originated-only mode if an inactivity timer expires. The WTRU may switch modes according to a pre-configured schedule. After the operation mode transition, the WTRU may or may not send a message to the network indicating such mode switching.

Operation in the mobile-originated-only mode may be supported by adding some modifications to the RRC and/or NAS procedures. To accomplish this, implementation may be through the use of a separate RRC idle state, an RRC idle mode with a profile configuration configured for a mobile-originated-only mode, or a mobile-originated-only state in an RRC idle mode. Similarly, NAS modifications may be made by supporting new NAS states in mobile-originated-only mode or by using new profile configurations.

Embodiments are disclosed that support a new mode of operation referred to as a "mobile-originated-only mode". This new mode of operation may be implemented using a new "mobile-originated-only state" or a new profile configuration for the RRC and/or NAS layers. The WTRU may send a message to the network indicating that the WTRU supports the mobile-originated-only mode and/or the functionality supported by the WTRU in the mobile-originated-only mode.

Drawings

A more detailed understanding can be obtained from the following description, given by way of example, in conjunction with the accompanying drawings, in which:

FIG. 1A is a system diagram of an example communication system in which one or more disclosed embodiments may be implemented;

FIG. 1B is a system diagram of an exemplary wireless transmit/receive unit (WTRU) that may be used within the communication system shown in FIG. 1A;

fig. 1C is a system diagram of an example radio access network and an example core network that may be used within the communication system shown in fig. 1A;

fig. 1D is an example communication scenario in which an MTC device communicates with an MTC server;

FIG. 2 illustrates a transition between a mobile-originated-only mode and a mobile-originated-and-terminated mode;

figure 3 is an example Universal Terrestrial Radio Access (UTRA) RRC state diagram according to one embodiment;

FIG. 4 is an example evolved universal terrestrial radio access (E-UTRA) RRC state diagram, according to one embodiment; and

FIG. 5 is an example reachable period and unreachable period.

Detailed Description

Fig. 1A is an illustration of an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to a plurality of wireless users. The communication system 100 enables multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, communication system 100 may use one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), and the like.

As shown in fig. 1A, the communication system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a Radio Access Network (RAN) 104, a core network 106, a Public Switched Telephone Network (PSTN) 108, the internet 110, and other networks 112, although it is understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. For example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include User Equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a Personal Digital Assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, consumer electronics, and the like.

Communication system 100 may also include base station 114a and base station 114 b. Each of the base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the core network 106, the internet 110, and/or the network 112. For example, the base stations 114a, 114B may be Base Transceiver Stations (BTSs), node B, e node Bs, home eNodeBs, site controllers, Access Points (APs), wireless routers, and so forth. Although the base stations 114a, 114b are each depicted as a single element, it should be understood that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

The base station 114a may be part of the RAN 104, where the RAN 104 may also include other base stations and/or network elements (not shown), such as Base Station Controllers (BSCs), Radio Network Controllers (RNCs), relay nodes, and so forth. Base station 114a and/or base station 114b may be configured to transmit and/or receive wireless signals within a particular geographic area referred to as a cell (not shown). The cell may also be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In another embodiment, the base station 114a may use multiple-input multiple-output (MIMO) technology and thus may use multiple transceivers for each sector in the cell.

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., Radio Frequency (RF), microwave, Infrared (IR), Ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable Radio Access Technology (RAT).

More specifically, as described above, communication system 100 may be a multiple access system and may use one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) terrestrial radio access (UTRA), which may use wideband cdma (wcdma) to establish the air interface 116. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and/or evolved HSPA (HSPA +). HSPA may then include High Speed Downlink Packet Access (HSDPA) and/or High Speed Uplink Packet Access (HSUPA).

In another embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as evolved UMTS terrestrial radio access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-advanced (LTE-a).

In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA 20001X, CDMA2000 EV-DO, Interim standard 2000 (IS-2000), Interim standard 95 (IS-95), Interim standard 856 (IS-856), Global System for Mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE Radio Access Network (GERAN), and so forth.

The base station 114B in fig. 1A may be, for example, a wireless router, a home nodeb, a home enodeb, or an access point, and may use any suitable RAT to facilitate wireless connectivity in a local area (e.g., business, residence, vehicle, campus, etc.). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may establish the pico cell or the femto cell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE-a, etc.). As shown in fig. 1A, the base station 114b may have a direct connection to the internet 110. Thus, the base station 114b may not need to access the internet 110 via the core network 106.

The RAN 104 may communicate with a core network 106, where the core network 106 may be any type of network configured to provide voice, data, application, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102 d. For example, the core network 106 may provide call control, billing services, mobile location-based services, pre-paid calling, internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in fig. 1A, it is to be understood that the RAN 104 and/or the core network 106 may communicate directly or indirectly with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to interfacing with the RAN 104, which may use E-UTRA radio technology, the core network 106 may also communicate with another RAN (not shown) that uses GSM radio technology.

The core network 106 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the internet 110, and/or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides Plain Old Telephone Service (POTS). The internet 110 may include a worldwide system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) of the TCP/IP internet protocol suite. The network 112 may include wired or wireless communication networks owned and/or operated by other service providers. For example, the network 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities, i.e., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers that communicate with different wireless networks over different wireless links. For example, the WTRU102 c shown in fig. 1A may be configured to communicate with a base station 114a, which may use a cellular-based radio technology, and with a base station 114b, which may use an IEEE 802 radio technology.

Figure 1B is a system diagram of an example WTRU 102. As shown in fig. 1B, the WTRU102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripherals 138. It should be understood that WTRU102 may include any subcombination of the foregoing elements while maintaining a consistent implementation.

The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a Digital Signal Processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of Integrated Circuit (IC), a state machine, or the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functions that enable the WTRU102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120, and the transceiver 120 may be coupled to a transmit/receive element 122. Although fig. 1B depicts processor 118 and transceiver 120 as separate elements, it should be understood that processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

Transmit/receive element 122 may be configured to transmit signals to a base station (e.g., base station 114 a) or receive signals from a base station (e.g., base station 114 a) over air interface 116. For example, in one embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In another embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive, for example, IR, UV, or visible light signals. In another embodiment, the transmit/receive element 122 may be configured to transmit and receive both RF and optical signals. It should be appreciated that transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

Furthermore, although transmit/receive element 122 is depicted in fig. 1B as a single element, WTRU102 may include any number of transmit/receive elements 122. More specifically, the WTRU102 may use MIMO technology. Thus, in one embodiment, the WTRU102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

Transceiver 120 may be configured to modulate signals to be transmitted by transmit/receive element 122 and to demodulate signals received by transmit/receive element 122. As described above, the WTRU102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers that allow the WTRU102 to communicate via multiple RATs, such as UTRA and IEEE 802.11.

The processor 118 of the WTRU102 may be coupled to and may receive user input data from: a speaker/microphone 124, a keyboard 126, and/or a display/touch panel 128 (e.g., a Liquid Crystal Display (LCD) display unit or an Organic Light Emitting Diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. Further, the processor 118 may access information from, and store information in, any suitable memory (e.g., non-removable memory 130 and/or removable memory 132). The non-removable memory 130 may include Random Access Memory (RAM), Read Only Memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a Subscriber Identity Module (SIM) card, a memory stick, a Secure Digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memories that are not physically located on the WTRU102, such as on a server or home computer (not shown).

The processor 118 may receive power from the power source 134 and may be configured to distribute and/or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel cadmium (NiCd), nickel zinc (NiZn), nickel metal hydride (NiMH), lithium ion (Li-ion), etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) related to the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU102 may receive location information from base stations (e.g., base stations 114a, 114 b) over the air interface 116 and/or determine its location based on the timing of signals received from two or more nearby base stations. It should be appreciated that the WTRU102 may acquire location information via any suitable location determination method while maintaining consistent embodiments.

The processor 118 may also be coupled to other peripherals 138, which may include providing additional features, work, or other functionsAnd/or one or more software and/or hardware modules that can be connected by wire or wirelessly. For example, the peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and video), a Universal Serial Bus (USB) port, a vibration device, a television transceiver, a hands-free headset, BluetoothA module, a Frequency Modulation (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, and so forth.

Fig. 1C is a system diagram of RAN 104 and core network 106 according to an embodiment. As described above, the RAN 104 may use UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also communicate with a core network 106. As shown in fig. 1C, the RAN 104 may include node-bs 140a, 140B, 140C, and each of the node-bs 140a, 140B, 140C may include one or more transceivers for communicating with the WTRUs 102a, 102B, 102C over the air interface 116. Each node B140 a, 140B, 140c may be associated with a particular cell (not shown) in RAN 104. RAN 104 may also include RNC 142a and RNC 142 b. It is noted that RAN 104 may include any number of node bs and RNCs while maintaining compliance with the embodiments.

As shown in fig. 1C, node bs 140a, 140B may communicate with RNC 142 a. In addition, node B140 c may communicate with RNC 142B. The node bs 140a, 140B, 140c may communicate with respective RNCs 142a, 142B via an Iub interface. The RNCs 142a, 142b may communicate with each other via an Iur interface. Each of the RNCs 142a, 142B may be configured to control a respective node B140 a, 140B, 140c connected thereto. Further, each of the RNCs 142a, 142b may be configured to perform or support other functions, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, and so forth.

The core network 106 shown in fig. 1C may include a Media Gateway (MGW) 144, a Mobile Switching Center (MSC) 146, a Serving GPRS Support Node (SGSN) 148, and/or a Gateway GPRS Support Node (GGSN) 150. While each of the foregoing elements are described as being part of the core network 106, it should be appreciated that any of these elements may be owned and/or operated by entities other than the core network operator.

RNC 142a in RAN 104 may be connected to MSC 146 in core network 106 via an IuCS interface. MSC 146 may be connected to MGW 144. The MSC 146 and MGW 144 may provide the WTRUs 102a, 102b, 102c with access to a circuit-switched network, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and conventional landline communication devices.

The RNC 142a in the RAN 104 may also be connected to the SGSN148 in the core network 106 via an IuPS interface. The SGSN148 may be coupled to a GGSN 150. The SGSN148 and GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

As described above, the core network 106 may also be connected to a network 112, where the network 112 may include other wired or wireless networks owned and/or operated by other service providers.

Fig. 1D illustrates an example communication scenario in which MTC device 180 communicates with MTC server 160. The MTC device 180 is a WTRU equipped for machine type communication that may communicate through a Public Land Mobile Network (PLMN) with the MTC server 160 and/or other MTC devices 180. The MTC server 160 is a server that communicates with the PLMN itself and with the MTC device 180 through the PLMN. The MTC server 160 may have an interface accessible by the MTC user 170. The MTC user 170 uses a service provided by the MTC server 160. In this example, the MTC server 160 is located in the operator domain 165, but may also be located outside the operator domain 165. The MTC devices 160 may communicate with one or more MTC servers 160, and may also communicate with each other. The network operator provides network connectivity to the MTC server.

It should be noted that the embodiments disclosed herein may be implemented in any type of wireless communication system including, but not limited to, UMTS, Long Term Evolution (LTE), cdma2000, IEEE 802.16, GERAN, etc. It should be noted that the embodiments disclosed herein are applicable to both mobile-originated-only and non-frequent-mobile-terminated features, and the term "mobile-originated-only mode" also covers "non-frequent-mobile-terminated modes".

According to one embodiment, the WTRU may switch back and forth between the mobile-originated-only mode 210 and the mobile-originated-and-terminated mode 220 based on a predetermined trigger. Fig. 2 shows a transition between a mobile-originated-only mode 210 and a mobile-originated-and-terminated mode 220. Alternatively, the WTRU may configure itself or may be preconfigured to operate in the mobile-originated-only mode 210. Operation in the mobile-originated-only mode may be triggered by an explicit or implicit trigger (e.g., a command from the network, a pre-configured schedule, etc.). The WTRU may be configured to operate only in a mobile-originated-only mode. In this case, the trigger may not necessarily initiate or resume operation in the mobile-originated-only mode.

In the mobile originated and terminated mode 220, the WTRU may listen to a paging channel or paging indicator channel, etc. (hereinafter collectively referred to as a "paging channel"), and/or perform mobility management procedures. In the mobile originated and terminated mode 220, the network may reach the WTRU, for example, to perform tests, software updates, establish calls, and the like.

In the mobile-originated-only mode 210, the WTRU may not perform idle mode procedures, which may be performed in a mobile-originated and terminated mode, or perform a subset of the idle mode procedures. The WTRU may not perform a specific mobility management procedure because it does not need to update its location to the network, or the WTRU may not listen to the paging channel because it is assumed that the WTRU will not receive a call. The functions that may be performed in the mobile-originated-only mode will be described in detail below.

The WTRU may initially be in a mobile-originated-only mode 210 and, for example, may transition to a mobile-originated-and-terminated mode 220 once the WTRU initiates communication with the network. The network may detach the WTRU from the mobile-originated-only mode 210. The WTRU may exit the mobile-originated-only mode 210 based on a timer or event, etc.

In the mobile-originated-only mode 210, the WTRU may remain attached to the network (e.g., registered with and authenticated to the network). Since the WTRU remains attached, the transition to the connected state will be faster than in the case where the WTRU is detached.

While in the mobile-originated-only mode 210, the WTRU may not be reachable by the network. Alternatively, a WTRU in the mobile-originated-only mode 210 may support the network-reachable mechanisms in the same situation.

Power savings in the mobile-originated-only mode will be significant because the device does not need to perform scheduled or configured background activities, such as paging monitoring, intra-cell, inter-cell, or inter-Radio Access Technology (RAT) measurements, as compared to the normal idle mode.

The functionality supported in the mobile-originated-only mode is set forth below.

In mobile-originated-only mode, the WTRU may not perform paging monitoring. Thus, the WTRU may not receive a mobile terminated call and a notification of a change in system information via a paging channel.

In mobile-originated-only mode, the WTRU may not perform cell reselection. The WTRU may not perform neighbor cell measurements for the cell reselection. Alternatively, the WTRU may perform neighbor cell measurements to determine if a new cell needs to be selected, but the WTRU may not perform other procedures, such as location area update, routing area update, or tracking area update (hereinafter collectively referred to as "location area update"). The WTRU may acquire and store system information for a new cell if the WTRU reselects the new cell based on neighbor cell measurements, or alternatively, the WTRU may wait for a trigger (e.g., move out of mobile-originated-only mode, trigger for an RRC connection, etc.) before acquiring the system information.

In mobile-originated-only mode, the WTRU may not perform location area update even if a cell in a new location area, routing area, or tracking area (hereinafter collectively referred to as a "location area") is selected or a new Public Land Mobile Network (PLMN) is entered. Alternatively, entering the new PLMN may be a trigger to perform a location area update.

Alternatively, while in the mobile-originated-only mode, the WTRU may perform a subset of the functions performed in idle mode. For example, a WTRU in mobile-originated-only mode may not perform background checks for higher priority PLMN search, cell reselection, paging monitoring, or the like.

The WTRU may operate in a mobile-originated-only mode on a per PLMN basis. For example, the WTRU may have a list of allowed PLMNs that indicates the mode of operation for each PLMN (i.e., mobile-originated-only mode or mobile-originated-and-terminated mode for each allowed PLMN). The list may be maintained in the WTRU, for example in a Universal Subscriber Identity Module (USIM).

The WTRU (i.e., MTC device) may be mobile, may have limited mobility, or may be stationary. In the case where the WTRU may move around, no cell reselection implies no paging monitoring and no location area update. No location area update implies no paging because the network does not know where the WTRU is located. Conversely, a stationary WTRU may not perform mobility procedures such as cell reselection, location area update, etc. In this case, even if the WTRU does not perform location area update, the network can still find the WTRU because there is no change in location and therefore the WTRU can still monitor the paging channel. In this case, the WTRU may have a longer Discontinuous Reception (DRX) cycle length to allow for battery savings. If the WTRU has limited mobility (e.g., the WTRU remains in the same location area or the WTRU is restricted to a group of cells), the WTRU may not perform a location update, but the WTRU can be paged because the location is known.

The mobile-originated-only mode may support one or a combination of the above functions for a mobile, limited mobility, or stationary WTRU. Table 1 shows an example selection of functions supported by a WTRU for mobile, stationary and limited mobility in a mobile-originated-only mode. It should be noted that the functions listed in table 1 are not exhaustive and other functions may be added.

TABLE 1

In option 1, the WTRU may not perform paging monitoring, but may perform cell reselection and location update. Once the WTRU selects or reselects a cell, or when the WTRU moves out of the mobile-originated-only mode, the WTRU may read the broadcast channel, but the WTRU may not be notified of the change in broadcast channel information because the WTRU does not monitor the paging channel. When the WTRU needs to transmit, the WTRU may exit the mobile-originated-only mode and check if there is any change in the system information. For value tag System Information Blocks (SIBs), the WTRU may verify whether there is a change in the value tag. For periodic SIBs, the WTRU may read the SIB if the validity period expires. If there is any change, the WTRU acquires the system information and then begins transmission.

The WTRU may notify the network that the WTRU exits the mobile-originated-only mode. The network may then update the state information it has stored for the WTRU and may not wait for the WTRU to establish a connection with the network before sending downlink transmissions (signaling or data) to the WTRU. The indication may be sent to the network in a Radio Resource Control (RRC) or non-access stratum (NAS) message. If the indication is sent via an RRC message (e.g., RRCConnectionSetupComplete), the RAN node (e.g., RNC, enodeb) may forward this indication to the Mobility Management Entity (MME)/Serving GPRS Support Node (SGSN) via an S1/Radio Access Network Application Part (RANAP) message. Alternatively, the WTRU may send a NAS message (e.g., a Tracking Area Update (TAU) message with this indication) with the "(activeflag) active flag" bit in the TAU message set to 1 to indicate to the network to establish the user plane bearer after the TAU procedure is completed. This may be done instead of sending a service request message having a length of 4 octets and no space to include such an indication. Alternatively, an extended service request or modified service request message may be sent with an additional information element to provide this indication to the core network (e.g., MME or SGSN).

In option 2, the WTRU may not perform paging monitoring and location area update, but may perform neighbor cell measurements and cell reselection. Since the WTRU is performing cell reselection, the WTRU may read the broadcast channel each time the cell is reselected. However, the WTRU may not be notified of the broadcast information change because the WTRU is not monitoring the paging channel. Alternatively, the WTRU may perform cell reselection but not acquire and store system information. The WTRU may wait to transition out of the mobile-originated-only mode before acquiring and storing the system information, or until an uplink transmission is initiated.

When the WTRU needs to transmit, the WTRU may exit the mobile-originated-only mode and check if there is any change in the system information. For the value tag SIB, the WTRU may verify whether there is a change in the value tag. For periodic SIBs, the WTRU may read the SIB if the validity period expires. If the WTRU does not acquire some of the SIBs, the WTRU may read and acquire the remaining SIBs. The WTRU may perform a location update procedure if there is a change in the location area (i.e., location area, routing area, or tracking area). If the network detects a location area update, the network knows that the WTRU has data to transmit and may allocate resources for transmitting the data for the WTRU. Alternatively, the WTRU may explicitly indicate that it wants to perform uplink transmission with a location area update.

In option 3, the WTRU may not perform paging monitoring, cell reselection, or location update. When the WTRU needs to transmit, the WTRU may exit the mobile-originated-only mode and verify whether the current cell is still a suitable cell. If so, the WTRU may remain in the same cell. If not, the WTRU may perform a cell reselection procedure by performing measurements on neighboring cells. The WTRU may perform initial cell reselection if the neighboring cell is not suitable. The WTRU may read the broadcast channel in the selected cell. If the selected cell is the same as the previous cell, the WTRU may simply check if there is any change in the system information. For the value tag SIB, the WTRU may verify whether there is a change in the value tag. For periodic SIBs, the WTRU may read the SIB if the validity period has expired. The WTRU may perform a location update procedure if there is a change in location (location area, routing area, or tracking area). The WTRU may then start transmission.

In option 4, the WTRU may perform paging monitoring but may not perform cell reselection and location update. Option 4 is for a stationary WTRU. Since the WTRU is stationary, there is no need to perform cell reselection or location update. When the WTRU needs to transmit, the WTRU may exit the mobile-originated-only mode and may start transmitting.

In option 5, the WTRU may perform paging monitoring and cell reselection, but may not perform location update. Option 5 is for a WTRU with limited mobility (e.g., the WTRU remains in the same location area, or it is restricted to a group of cells (which may be a single cell)). Since the WTRU remains in the same location area, no location update need be performed and the WTRU may be paged without a location update since the location is known. When the WTRU needs to transmit, the WTRU may exit the mobile-originated-only mode and may start transmitting.

The WTRU may signal to the network that it supports a mobile-originated-only mode. This notification may imply a set of functions supported by the WTRU in the mobile-originated-only mode. Alternatively, the WTRU may exclusively advertise the functionality (e.g., paging monitoring, cell reselection, and/or location update) supported by the network by the WTRU in the mobile-originated-only mode.

To control the behavior of the WTRU in the mobile-originated-only mode, a new mobile-originated-only state or a new profile configuration (hereinafter referred to as "mobile-originated-only state or configuration") may be defined. The new mobile-originated-only state or configuration may be defined in the Radio Resource Control (RRC) and/or non-access stratum (NAS) layers. It should be noted that the mobile-originated-only state or configuration may be implemented without additional RRC and/or NAS states or configurations, and that the embodiments disclosed herein may be implemented with or without new RRC and/or NAS states or configurations.

According to one embodiment, the functionality for the mobile-originated-only mode may be supported by the new RRC state. Figure 3 is an example Universal Terrestrial Radio Access (UTRA) RRC state diagram according to one embodiment. Fig. 4 is an example evolved universal terrestrial radio access (E-UTRA) RRC state diagram according to another embodiment. In fig. 3 and 4, in addition to the conventional UTRA/E-UTRA RRC _ CONNECTED (UTRA/E-UTRA RRC _ CONNECTED) and UTRA/E-UTRA RRC IDLE (UTRA/E-UTRA RRC _ IDLE) states, a UTRA/E-UTRA RRC IDLE _ MO _ ONLY state is defined to control the behavior of the WTRU and the network in the mobile-originated-ONLY mode. RRC state transitions between RRC _ CONNECTED and RRC _ IDLE or RRC _ IDLE _ MO _ ONLY may be triggered by RRC connection establishment or release. The RRC state transition between RRC _ IDLE and RRC _ IDLE _ MO _ ONLY may be triggered by an explicit or implicit trigger, which will be explained in detail below.

According to another embodiment, functionality in the mobile-originated-only mode may be supported by an RRC IDLE (RRC IDLE) state with a new RRC profile configuration that captures all specific operations in the mobile-originated-only mode. When operating in mobile-originated-only mode, the WTRU may use the new RRC configuration in idle mode. The WTRU may store the new profile configuration in its memory and this new profile configuration will allow the WTRU to quickly switch from one mode to another without needing to acquire the new RRC configuration from the network. The mobile-originated-only profile configuration may be sent to the WTRU using a dedicated RRC signaling message encapsulated into a regular RRC message (e.g., an RRC connection release message or any other message). Alternatively, the network may send the mobile-originated-only profile configuration through the SIB. A WTRU operating for the first time in a mobile-originated-only mode may acquire the corresponding SIB. When the WTRU switches out of this mode, the WTRU may store a mobile-originated-only configuration profile in memory that allows the WTRU to switch back into this mode without interruption and without the need to reacquire the RRC configuration associated with this profile.

According to another embodiment, a new state of the RRC idle mode may be defined. In this case, the fact that the WTRU is in this state may or may not be known by the RRC entity on the network side, since from the network point of view the WTRU may simply be in RRC idle mode. The NAS state on the network side may be different than for the WTRU (e.g., even if no new RRC state is used).

For NAS support, functionality may be supported in a new NAS state. The WTRU may enter a new NAS state based on a trigger in the NAS message from the network. The NAS message may be an accept message (e.g., attach accept, location update accept, tracking area update accept, etc.) sent from the network to the WTRU. Alternatively, the transition to the new NAS state may be triggered by the WTRU (e.g., via an internal inactivity timer). In this case, the WTRU may advertise to the network that the WTRU enters a new NAS state. A certain period of time (e.g., a certain time of day) may be reserved for the WTRU to operate in this new NAS state. Transitioning out of this new NAS state may be coordinated with the network, for example, based on the time of day. When the WTRU exits the new NAS state and becomes reachable, the WTRU may send a notification to the network. The triggers applicable to RRC state transitions may be applied to NAS state transitions because the WTRU RRC and NAS may be synchronized (i.e., use the same mode of operation (same state or configuration) at any given time).

An equivalent new mobile-originated-only NAS state may be configured on the network side (e.g., in the MME, SGSN, etc.). The events applied to the WTRU may be applied to transition into and out of NAS state on the network (e.g., MME or SGSN). The new NAS state on the network may change for a particular WTRU based on network policies and events. This may trigger the network (e.g., MME or SGSN) to request the WTRU to exit or enter other states. Such an indication may be provided through a NAS message or through an RRC or OMA MD/OTA message. The RAN-based indication may also be forwarded over S1AP or RANAP or other equivalent messages.

Alternatively, the functionality may be supported by a NAS idle/standby state with a new NAS profile/configuration. New configurations may be provided to be supported in NAS Evolved Packet System (EPS) connection management (ECM) idle state (LTE), NAS Packet Mobility Management (PMM) idle state (Iu mode), or NAS standby state (a/Gb mode). The modification of this state may depend on the supported functionality as described above.

Since the SGSN/MME may perform implicit General Packet Radio Service (GPRS) detach at any time after the WTRU reachable timer expires, the network may increase the value of this timer or disable it during this configured mode of operation. The timer may be a mobile reachable timer and/or an implicit detach timer.

Triggers for transitioning between a mobile-originated-only mode and a mobile-originated-and-terminated mode (i.e., transitioning between RRC/NAS states or configurations), or for initiating and stopping operation in a mobile-originated-only mode, are set forth below. The trigger may be explicit or implicit. The triggers disclosed below may be used in any of the embodiments described above.

Transitions between the mobile-originated-only mode and the mobile-originated-and-terminated mode (i.e., transitions between RRC/NAS states or configurations) may be explicitly signaled via an RRC message (e.g., an RRC connection release message). New parameters, Information Elements (IEs), or fields may be included in the RRC message to trigger a transition from the RRC connected state to the mobile-originated-only state or configuration. Alternatively, the absence of a specific field in the RRC message may indicate to the WTRU that the WTRU should operate in a mobile-originated and terminated mode (i.e., a conventional RRC/NAS state).

The network may signal the WTRU to transition between the mobile-originated-only mode and the mobile-originated-and-terminated mode (i.e., transition between RRC/NAS states or configurations) by sending idle mode signaling (e.g., paging messages, broadcast messages, or Cell Broadcast Service (CBS) messages, etc.). The transition from the mobile-originated-only mode and the mobile-originated-and-terminated mode, i.e., from the normal idle state to the mobile-originated-only state or configuration (i.e., transition between RRC/NAS states or configurations), may be triggered by a paging message, any NAS message, or the like.

The decision to trigger a transition of the operational state/configuration may be based on network/operator policies (e.g., load conditions of the network). The radio access network (e.g., evolved node B (enb) or node B) may indicate this policy to the WTRU based on an indication received through an S1AP message in case of LTE or a Radio Access Network Application Part (RANAP) message in case of 3G system, respectively. For example, a Mobility Management Entity (MME) may send a request to the eNB to change the mode of operation of the WTRU to a mobile-originated-only mode, and this may be done by introducing a new IE on an S1AP message (e.g., (UEContextModifierRequest), etc.. this also applies to equivalent messages on 3G systems or GPRS EDGE Radio Access Network (GERAN) equivalent messages between the Radio Access Network (RAN) and the core network.

Alternatively, the WTRU may indicate to the network its previous mode or operational settings (e.g., respective RRC and NAS states or profile configurations) when registering (e.g., attach procedure) or location area update procedure (e.g., location area update, routing area update, or tracking area update, or a combination of these updates). The network (e.g., MME) may also indicate the mode of operation to be used by the WTRU in a response message or any other NAS message (e.g., EMM information or equivalent message). The WTRU may use the mode indicated by the network in a setting to operate in a particular mode.

Alternatively, the WTRU may comply with a network-proposed mode of operation (e.g., mobile-originated-only mode). When the NAS entity in the WTRU decides the mode of operation, e.g., based on an indication from the MME, the NAS entity may inform the Access Stratum (AS)/RRC about the selected mode of operation.

Alternatively, a NAS or RRC entity in the WTRU may receive an indication of the operational configuration or mode to be used. The indication may be received from the user via an interface (e.g., an interface on a vending machine) or may be received in accordance with a change in a setting of user medication (media). Alternatively, the indication may be received via a Short Message Service (SMS) message and/or an Open Mobile Alliance (OMA) Device Management (DM) or over-the-air (OTA) protocol.

The operating configuration or mode may be changed as a result of a change in the operating mode of the device. For example, if the WTRU is operating in a mobile-originated-only mode, a change in device operation mode from automatic to manual (e.g., requesting manual Closed Subscriber Group (CSG) selection or manual PLMN selection) may trigger the WTRU to exit the mobile-originated-only mode, and a change from manual to automatic mode may trigger the WTRU to operate in the mobile-originated-only mode.

The transition between the mobile originated and terminated mode and the mobile originated only mode may be implicitly triggered when certain conditions are met. For example, the condition may be based on an inactivity timer (e.g., if no downlink data is received within a preconfigured time). Once the inactivity timer expires or reaches a particular value, the WTRU may transition from a mobile-originated-only mode and a mobile-originated-and-terminated mode (i.e., transition between RRC/NAS states or configurations (i.e., from a normal idle state to a mobile-originated-only state or configuration)), and vice versa.

The inactivity timer may be restarted or reinitialized based on activity (e.g., transition from an RRC connected state to a normal RRC idle state). Alternatively, the network may send a paging message or idle mode signaling (e.g., CBS message) to restart or reinitialize the inactivity timer and keep the WTRU in mobile-originated and terminated mode. Alternatively, the inactivity timer may be restarted or reinitialized while the WTRU is in the RRC connected state.

When the inactivity timer expires, the WTRU may automatically transition to the mobile-originated-only state/configuration (with respective RRC and NAS states or profile configurations) without the need to advertise the transition to the network. Alternatively, the WTRU may automatically transition to a mobile-originated-only state or configuration and send a notification to the network regarding the transition. Alternatively, the WTRU may signal this trigger to the network and wait for an explicit trigger from the network to transition to the mobile-originated-only state or configuration.

Alternatively, the WTRU may transition from the mobile-originated-only mode to the mobile-originated-and-terminated mode in a periodic manner (e.g., once a day). Once the WTRU leaves the mobile-originated-only mode, the WTRU may perform all normal idle mode procedures (e.g., listening to a paging channel, performing cell reselection or location update, etc.), or a subset of the normal idle mode procedures. The WTRU may send a "poll" message to the network to indicate that the WTRU exits the mobile-originated-only mode and that the WTRU is now reachable. More particularly, when a periodic timer expires or when a certain time, as configured by the network or an application, is reached, the WTRU may transition to a normal idle mode and may initiate a transmission to announce to the network that the WTRU is operating in a mobile-originated and terminated mode. The transmitted message may be an RRC message, where a new establishment cause or a new IE may be included to indicate this trigger. Alternatively, the message may be a NAS message. The NAS message may contain a location area, a new cause, and/or additional information elements indicating that the WTRU has exited the mobile-originated-only mode. The network may then know that the WTRU is reachable and may page the WTRU if it needs to be reached.

Alternatively, the network may broadcast a new flag in a particular SIB, and the WTRU may receive a broadcast channel to monitor for SIBs according to a configured periodicity. The monitoring time may correspond to a periodic timer or an absolute time and length configured by the network. During this time, the WTRU may remain in the mobile-originated-only mode and monitor only the SIBs without transitioning to the RRC idle mode. If the flag in the SIB is set, the WTRU may move out of the mobile-originated-only mode, may read all SIBs and start monitoring the paging channel, etc. Alternatively, if the flag is set, the WTRU may trigger a "poll message" to indicate to the network that the WTRU has moved out of the mobile-originated-only mode and may now be paged for a predefined or configured period of time. When the WTRU leaves the mobile-originated-only mode and reads the SIB, a flag in the SIB may instruct the WTRU to monitor the paging channel, or send a "poll" message to announce that the WTRU becomes reachable, or return to the mobile-originated-only mode. When the length of the period expires and the WTRU does not receive any paging or no flag is set in the SIB, the WTRU may transition back to the mobile-originated-only mode.

An MTC subscriber may trigger a specific MTC device or MTC group to transition from a mobile-originated-only mode to a mobile-originated-and-terminated mode, and vice versa. An MTC subscriber is a legitimate entity having a contractual relationship with a network operator to provide services to one or more MTC devices. An MTC group is a group of MTC devices belonging to the same MTC subscriber. According to one embodiment, the address field of the message may allow MTC subscribers to send unicast, multicast and broadcast triggers to specific MTC devices or MTC groups. The address field may be partitioned to reserve an address range for unicast and broadcast addresses (e.g., the Most Significant Bit (MSB) of the address field may be used to indicate a multicast or unicast address). A specific address may be reserved to indicate a broadcast address (e.g., an "all ones" address).

The WTRU may periodically transition between a mobile-originated-and-terminated mode and a mobile-originated-only mode. When the WTRU is in the mobile-originated-only mode, it may refer to being in an unreachable period, and when the WTRU is away from the mobile-originated-only mode, it may refer to being in an reachable period. Fig. 5 shows an reachable period and a unreachable period. The WTRU may alternate between unreachable periods and reachable periods based on configured rules.

The WTRU may enter and exit the unreachable period based on any implicit or explicit trigger disclosed above. The WTRU may exit the unreachable period based on an reachable cycle or based on an event such as timer expiration or uplink activity. Once the WTRU exits the unreachable period, the WTRU may remain in the reachable period (i.e., in "regular" idle mode) until a new unreachable cycle begins. Alternatively, the network may command the WTRU to return to the unreachable period. This command may be sent via a broadcast message, a paging message, or the like. Alternatively, the network may instruct the WTRU to establish an RRC connection and enter an RRC connected mode.

The explicit trigger may be a message from the network to the WTRU. This message may be a NAS message, RRC dedicated message, broadcast message, paging message, etc. In case the trigger is from RNC/enodeb, the trigger information may also be propagated to the core network to let the SGSN/MME know the WTRU reachable status.

Implicit triggers may be events such as expiration of an activity timer or a preconfigured reachable loop. In the case of implicit triggering, the WTRU may advertise to the network that it is entering a non-reachable period or an reachable period. The WTRU may advertise both NAS or RRC entities. In the case where the WTRU advertises an RRC entity, information may be propagated to the core network to make the SGSN/MME aware of the WTRU reachable status. The WTRU's reachable cycle may be pre-configured in the network, in which case no notification from the WTRU may be needed.

For operation in a mobile-originated-only mode (including an infrequent mobile-terminated mode), the WTRU may receive from the network, or be pre-configured with a configuration including an unreachable cycle. The configuration may indicate a timing of a first cycle for activating the unreachable period, and/or a duration of the cycle. The WTRU may receive the configuration from the core network via a message (e.g., attach accept, location update accept, and tracking area update accept), or from the Radio Access Network (RAN) (e.g., via an RRC message). If the configuration is received from the RAN, the RAN may propagate the configuration to the core network node. If the WTRU has been preconfigured with an unreachable cycle, the WTRU may inform a network entity in the RAN (e.g., RNC or enodeb) and/or a network entity in the core network (e.g., SGSN, MME) of the parameters to be used. This notification may be part of a NAS message (e.g., attach, area update, and tracking area update) or an RRC message (e.g., RRC connection request). The notification may be propagated to the core network node if the notification is sent as an RRC message. The reachable period may be configured according to absolute time and period. More particularly, the network may specify an absolute time (e.g., 2 pm) and a period (e.g., X hours, minutes, or seconds). Multiple absolute times may be specified during a day or a particular time period. The WTRU configures its RRC and NAS entities according to the unreachable cycle to be used, and the RRC entity may then configure the lower layers to perform the functions as disclosed above.

The WTRU may go to sleep at the beginning of the unreachable cycle and wake up at the end of the unreachable cycle unless an application layer or other event triggers the WTRU to wake up in the middle of the unreachable period. The unreachable and reachable periods may define periods for the WTRU to transition between the mobile-originated-only mode and the mobile-originated-and-terminated mode.

Upon requesting a place call (e.g., an emergency call in a Packet Switched (PS) or Circuit Switched (CS) domain, or other distress signal that may be introduced for a low priority device), the WTRU may wake up (or exit the mobile-originated-only mode). The WTRU may not enter the mobile-originated-only mode until the call (e.g., emergency call) ends or until there are no more resources for the call (e.g., until a Packet Data Network (PDN) or Packet Data Protocol (PDP) context used for the emergency call is cleared or deactivated). The WTRU may not enter a mobile-originated-only mode if the WTRU is attached for emergency services.

At the end of the unreachable period, the WTRU wakes up and acquires network synchronization and underlay cell information using previously stored network information (e.g., carrier frequency, cell ID, PLMN ID, etc.). If the WTRU is still within range of the previous serving cell, the WTRU may verify whether the SIB has changed. The WTRU may use the previously stored SIB information if the SIB has not changed. The WTRU may reacquire SIB information if the SIB has changed. The WTRU may calculate the next start of the unreachable cycle and enter idle mode operation for the duration of the reachable period. The WTRU may resume paging monitoring, cell reselection, and other idle mode procedures. The WTRU may trigger a location area update if the location area has changed.

If the previous serving cell is no longer within range, the WTRU may undertake a full cell search while maintaining the PLMN. The WTRU may perform cell reselection and location area update.

At the end of the reachable period, the WTRU may end the idle mode procedure and enter the unreachable period, thereby entering sleep.

The WTRU may remain reachable for a certain period of time if the WTRU transitions out of the mobile-originated-only mode for transmission. The time period may be determined with respect to the initiation of the first transmission (e.g., RRC connection setup) in the transmission of NAS messages, in data transmissions, and so on. The time period may be reinitialized after each transmission or reception. Once the time period expires, the WTRU may automatically release the RRC connection (if applicable) and move to mobile-originated-only mode. Alternatively, after the expiration of the WTRU's transition to the mobile-originated-only mode, the WTRU may release the RRC connection, move to a mobile-originated-and-terminated mode (i.e., normal idle mode in this case), and monitor for additional inactivity timers.

The network may broadcast an indication that the WTRU in the mobile-originated-only mode is out of the mobile-originated-only mode. The node B may send a special information element, for example, in the system information (e.g., SIB 1) to request the WTRU to come out of the mobile-originated-only mode. This may be broadcast by all node bs or by the target node B. For example, the special information element may be sent by the node B where information about the number of WTRUs in the mobile-originated-only mode is needed. The special information element may include a flag indicating whether a mobile-originated-only mode WTRU is required to come out of the mobile-originated-only mode, a list of target WTRUs (which may be used if the network wants to reach a particular WTRU, for example, to track the location of the WTRU), or a group identity for a group of WTRUs (which may be a group identity related to the WTRU access category or some other WTRU-specific feature). The special information element may also include information regarding how and when the WTRU comes out of the mobile-originated-only mode. This may be necessary because the special information element may trigger more than one WTRU to come out of the mobile-originated-only mode, which allows the network to distribute (timely) the activation of these WTRUs, and has some control over the load that the activated WTRUs will generate on the access network.

A WTRU in a mobile-originated-only mode may monitor system information on a regular basis to obtain special information elements. In these cases, the WTRU may initially attempt to acquire system information from the last known cell in which the WTRU camped. If not feasible (e.g., if the last camped cell is no longer within range), the WTRU may perform cell selection to acquire system information. The WTRU may not camp on the new cell but may acquire the SIB containing the special information element.

Upon reading the special information element, the WTRU may estimate whether it needs to come out of the mobile-originated-only mode, for example, based on the type of information contained in the system information. If the network has targeted a particular WTRU (e.g., the special information element includes a particular WTRU address or group identity list), the WTRU may come out of the mobile-originated-only mode if the WTRU is included in the target list. If not, the WTRU may remain in the mobile-originated-only mode. The WTRU may determine a timing to transition out of the mobile-originated-only mode if the WTRU is in a target list. This may be immediate or based on some parameters included in the special information element.

Once the WTRU receives an indication to trigger mobile-originated communication (i.e., out of the mobile-originated-only mode), the WTRU may perform cell selection and initiate an RRC connection request to the network. Upon receiving the RRC connection request message, the network may determine whether it needs to move the WTRU out of the mobile-originated-only mode and send an RRC connection setup or RRC connection reject message to bring the WTRU out of the mobile-originated-only mode. The WTRU may be required to send a polling message to the network.

It should be noted that the above described embodiments may be used alone or in any combination.

Examples

1. A method for supporting machine type communication.

2. The method of embodiment 1 comprising a WTRU operating in a mobile-originated-only mode, wherein the WTRU does not perform RRC idle and/or NAS idle/standby state procedures, or performs a subset of the RRC idle and/or NAS idle/standby state procedures, in the mobile-originated-only mode.

3. The method of embodiment 2 further comprising the WTRU sending a message to a network indicating that the WTRU is operating in the mobile-originated-only mode or ceases operating in the mobile-originated-only mode.

4. A method as in any of embodiments 2-3 wherein operation in the mobile-originated-only mode is supported by one of a separate RRC idle state, an RRC idle mode with a profile configuration configured for the mobile-originated-only mode, or a mobile-originated-only state in an RRC idle mode.

5. A method as in any of embodiments 2-4 wherein operation in the mobile-originated-only mode is supported by a separate NAS state or a mobile-originated-only configuration supported in a NAS state.

6. The method as in any of embodiments 2-5 wherein the WTRU does not perform at least one of paging monitoring, cell reselection, or location update in the mobile-originated-only mode.

7. The method as in any of embodiments 2-6 further comprising the WTRU sending a message to a network indicating that the WTRU supports the mobile-originated-only mode and/or functions supported by the WTRU in the mobile-originated-only mode.

8. The method as in any of embodiments 2-7 wherein the WTRU configures itself to operate in the mobile-originated-only mode or to stop operating in the mobile-originated-only mode based on a preconfigured trigger or according to a message from a network.

9. The method of embodiment 8, wherein the message is at least one of a paging message, a broadcast message, an RRC message, a CBS message, a NAS message, an SMS message, or a message according to OMA DM or OTA protocol.

10. The method as in any of embodiments 2-9 wherein the WTRU operates in the mobile-originated-only mode based on network/operator policy or device operation mode, the device operation mode being automatic or manual CSG or PLMN selection.

11. The method as in any one of embodiments 2-10 wherein the WTRU operates in the mobile-originated-only mode on a condition that an inactivity timer expires.

12. The method as in any of embodiments 2-11 wherein the WTRU operates in the mobile-originated-only mode and stops operating in the mobile-originated-only mode according to a preconfigured schedule.

13. A WTRU supporting machine type communication.

14. The WTRU of embodiment 13 comprising a processor configured to operate in a mobile-originated-only mode, wherein the processor is configured to not perform RRC idle and/or NAS idle/standby state procedures, or to perform a subset of the RRC idle and/or NAS idle/standby state procedures, in the mobile-originated-only mode.

15. The WTRU of embodiment 14 wherein the processor is configured to send a message to a network indicating that the WTRU is operating in or ceases operating in the mobile-originated-only mode.

16. The WTRU as in any of embodiments 14-15 wherein operation in the mobile-originated-only mode is supported by one of a separate RRC idle state, an RRC idle mode with a profile configuration configured for the mobile-originated-only mode, or a mobile-originated-only state in an RRC idle mode.

17. The WTRU as in any one of embodiments 14-16 wherein operation in the mobile-originated-only mode is supported by a separate NAS state or a mobile-originated-only configuration supported in a NAS state.

18. The WTRU as in any one of embodiments 14-17 wherein the processor does not perform at least one of paging monitoring, cell reselection, or location update in the mobile-originated-only mode.

19. The WTRU as in any one of embodiments 14-18 wherein the processor is configured to send a message to a network indicating that the WTRU supports the mobile-originated-only mode and/or functions supported by the WTRU in the mobile-originated-only mode.

20. The WTRU as in any one of embodiments 14-19 wherein the processor is configured to operate in the mobile-originated-only mode or stop operating in the mobile-originated-only mode based on a preconfigured trigger or according to a message from a network.

21. The WTRU of embodiment 20 wherein the message is at least one of a paging message, a broadcast message, an RRC message, a CBS message, a NAS message, an SMS message, or a message according to OMA DM or OTA protocol.

22. The WTRU as in any one of embodiments 14-21 wherein the processor is configured to operate in the mobile-originated-only mode based on network/operator policy or device operation mode, the device operation mode being automatic or manual CSG or PLMN selection.

23. The WTRU as in any one of embodiments 14-22 wherein on a condition that an inactivity timer expires, the processor is configured to operate in the mobile-originated-only mode.

24. The WTRU as in any one of embodiments 14-23 wherein the processor is configured to operate in the mobile-originated-only mode and cease operating in the mobile-originated-only mode according to a preconfigured schedule.

Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with other features and elements. Furthermore, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer readable media include electrical signals (transmitted over a wired or wireless connection) and computer readable storage media. Examples of computer readable media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and Digital Versatile Disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims (17)

1. A method of supporting machine type communication, the method comprising:

a wireless transmit/receive unit (WTRU) transitions between a mobile originated and terminated mode and a mobile originated-only mode where the WTRU does not perform measurements for cell reselection, does not perform a location update procedure, does not perform system information monitoring, or does not perform paging on a condition that a timer reaches a predetermined trigger comprising a predetermined value.

2. The method of claim 1, further comprising:

the WTRU sending a message to a network instructing the WTRU to enter the mobile-originated-only mode.

3. The method of claim 1, wherein operation in the mobile-originated-only mode is supported by one of a separate Radio Resource Control (RRC) idle state, a Radio Resource (RRC) idle mode with a profile configuration configured for the mobile-originated-only mode, or a mobile-originated-only state in a Radio Resource Control (RRC) idle mode.

4. The method of claim 1, wherein operation in the mobile-originated-only mode is supported by a separate non-access stratum (NAS) state or a mobile-originated-only configuration supported in a NAS state.

5. The method of claim 1, further comprising:

the WTRU sending a message to a network indicating that the WTRU supports the mobile-originated-only mode and/or functions supported by the WTRU in the mobile-originated-only mode.

6. The method of claim 1 wherein the WTRU configures itself to operate or stop operating in the mobile-originated-only mode according to a message from a network, wherein the message is at least one of a paging message, a broadcast message, an RRC message, a cell broadcast service, CBS, message, a non-access stratum, NAS, message, a short message service, SMS, or a message according to an open mobile alliance, OMA, device management, DM, or over-the-air, OTA protocol.

7. The method of claim 1 wherein the WTRU operates in the mobile-originated-only mode based on network/operator policy or a device operation mode, the device operation mode being automatic or manual closed subscriber group, CSG, or public land mobile network, PLMN, selection.

8. The method of claim 1, wherein the WTRU operates in the mobile-originated-only mode according to a preconfigured schedule and stops operating in the mobile-originated-only mode according to a preconfigured schedule.

9. The method of claim 1, further comprising:

the WTRU sending a message to a network instructing the WTRU to exit the mobile-originated-only mode.

10. An apparatus for supporting machine type communication, the apparatus comprising:

means, in a wireless transmit/receive unit, WTRU, for transitioning between a mobile originated and terminated mode and a mobile originated-only mode on a condition that a timer reaches a predetermined trigger comprising a predetermined value, wherein the means for transitioning does not perform measurements for cell reselection, does not perform a location update procedure, does not perform system information monitoring, or does not perform paging in the mobile originated-only mode.

11. The apparatus of claim 10, wherein the means for transitioning further comprises means for sending a message to a network instructing the WTRU to enter or exit the mobile-originated-only mode.

12. The apparatus of claim 10, wherein operation in the mobile-originated-only mode is supported by one of a separate RRC idle state, an RRC idle mode with a profile configuration configured for the mobile-originated-only mode, or a mobile-originated-only state in an RRC idle mode.

13. The apparatus of claim 10, wherein operation in the mobile-originated-only mode is supported by a standalone NAS state, or a mobile-originated-only configuration supported in a NAS state.

14. The apparatus of claim 10, wherein the means for transitioning further comprises means for sending a message to a network indicating that the WTRU supports the mobile-originated-only mode and/or functions supported by the WTRU in the mobile-originated-only mode.

15. The apparatus of claim 10, wherein the means for converting is configured to operate in or stop operating in the mobile-originated-only mode according to a message from a network, wherein the message is at least one of a paging message, a broadcast message, an RRC message, a cell broadcast service, CBS, message, a non-access stratum, NAS, message, a short message service, SMS, or a message according to an open mobile alliance, OMA, device management, DM, or over-the-air, OTA protocol.

16. The apparatus according to claim 10, wherein the means for converting is configured to operate in the mobile-originated-only mode based on network/operator policy or a device operation mode, the device operation mode being automatic or manual closed subscriber group, CSG, or public land mobile network, PLMN, selection.

17. The apparatus of claim 10, wherein the means for transitioning is configured to operate in the mobile-originated-only mode according to a preconfigured schedule, and to cease operating in the mobile-originated-only mode according to a preconfigured schedule.