Method for performing a paging procedure for a reduced bandwidth machine type communication (MTC) device and MTC device - Patents.com
The method of determining a paging narrowband for reduced bandwidth WTRUs in MTC systems based on WTRU-ID bits addresses the challenge of efficient resource allocation and battery conservation in MTC device paging, enhancing network efficiency and reducing costs.
Patent Information
- Application Number
- JP2023204570
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2016-03-14
- Filing Date
- 2023-12-04
- Publication Date
- 2025-05-22
- Estimated Expiration
- 2036-11-04
AI Technical Summary
Current wireless communication systems, such as LTE, face challenges in efficiently managing paging procedures for reduced bandwidth Machine Type Communication (MTC) devices, particularly in optimizing channel bandwidth and data rates to reduce network costs and maintenance needs.
A method for paging in reduced bandwidth wireless transmit/receive units (WTRUs) in machine type communication (MTC) systems, where the WTRU determines a paging narrowband (NB) based on the most significant bits of its identifier (WTRU-ID) to monitor the MTC physical downlink control channel (M-PDCCH), allowing for efficient resource allocation and reduced battery consumption.
This approach enables efficient resource allocation and reduced battery consumption for MTC devices, improving network efficiency and reducing operational costs by optimizing channel bandwidth usage.
Smart Images

Figure 0007681670000007 
Figure 0007681670000008 
Figure 0007681670000009
Abstract
Description
[Background technology]
[0001] The present invention relates to a method for performing a paging procedure for a reduced bandwidth Machine Type Communication (MTC) device and to an MTC device.
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 62 / 250,803, filed November 4, 2015, U.S. Provisional Patent Application No. 62 / 290,790, filed February 3, 2016, and U.S. Provisional Patent Application No. 62 / 308,042, filed March 14, 2016, the contents of which are incorporated herein by reference. As wireless communication systems, such as Long Term Evolution (LTE) systems, mature and their network deployments develop, it is beneficial for network operators to reduce the cost of the communication network, the need for maintenance of the communication network, or both. One technique for reducing the cost of the network can be to reduce the channel bandwidth and data rates used to communicate with devices.
[0003] For example, when communicating with such devices, a portion of the channel bandwidth rather than the entire channel bandwidth may be supported by devices in the network and / or the network itself. Current wireless communication systems, e.g., LTE, have recently considered bandwidth reduction for some devices, including machine type communication (MTC) devices, to a certain level, e.g., 1.4 megahertz (MHz). Summary of the Invention [Problem to be solved by the invention]
[0004] A method of paging for a machine type communication, reduced bandwidth wireless transmit / receive unit (WTRU) in an MTC is provided. [Means for solving the problem]
[0005] A method of paging for a reduced bandwidth wireless transmit / receive unit (WTRU) in machine type communication (MTC) is provided. The WTRU may determine a paging narrowband (NB) for the WTRU to use for monitoring an MTC physical downlink control channel (M-PDCCH) based on at least a most significant bit (MSB) of a function of a WTRU identifier (WTRU-ID). The WTRU may monitor for the M-PDCCH on the determined paging NB for the WTRU. The WTRU may then receive downlink control information (DCI) on the monitored M-PDCCH on the determined paging NB during a paging occasion (PO). The DCI may include a scrambled cyclic redundancy check (CRC). The CRC may be scrambled with a paging radio network temporary identifier (P-RNTI). The WTRU may also receive a physical downlink shared channel (PDSCH) associated with the M-PDCCH.
[0006] In an example, the WTRU may determine the paging NB based on at least the three MSBs of a function of the WTRU-ID. In another example, the WTRU may determine the paging NB based on at least the four MSBs of a function of the WTRU-ID.
[0007] Additionally, the PDSCH may be scheduled by the DCI. In an example, the DCI may include a paging message. In another example, the DCI may include system information update related information. In another example, the PDSCH may include a paging message. In a further example, the PDSCH may include system information update related information.
[0008] Further, the WTRU may monitor for an M-PDCCH within the M-PDCCH search space. The WTRU may receive an M-PDCCH within the M-PDCCH search space, the M-PDCCH having a starting enhanced control channel element (ECCE) index for a WTRU group that includes the WTRU. Further, the WTRU may decode the M-PDCCH, the M-PDCCH including DCI. Further, the WTRU may receive a PDSCH associated with the M-PDCCH.
[0009] Further, the WTRU may receive, decode, and / or demodulate a PDSCH based on the DCI, where the PDSCH includes a paging message. The WTRU may then change operation based on the paging message. For example, the WTRU may change from an idle mode to a connected mode based on the paging message. In an example, the ECCE aggregation level may be 16. Effect of the Invention
[0010] A novel machine type communication, reduced bandwidth wireless transmit / receive unit (WTRU) paging method in an MTC is provided. [Brief description of the drawings]
[0011] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which:
Figure 1A
Figure 1B
Figure 1C
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
[0012] 1A is a diagram 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 providing content, such as voice, data, video, messaging, broadcasts, etc., to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the 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), etc.
[0013] 1A, the communications 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 will be 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. By way of example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, mobile phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, consumer electronics devices, and the like.
[0014] The communications system 100 may also include a base station 114a and a base station 114b. Each of the base stations 114a, 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 communications networks, such as the core network 106, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each shown as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0015] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals within a particular geographic area, which may be referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, one for each sector of the cell. In other embodiments, the base station 114a may use multiple-input multiple-output (MIMO) technology and thus may utilize multiple transceivers for each sector of the cell.
[0016] 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).
[0017] More specifically, as noted above, the communication system 100 may be multiple access and may use one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. 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 establish the air interface 116 using Wideband CDMA (WCDMA). WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink Packet Access (HSDPA) and / or High Speed Uplink Packet Access (HSUPA).
[0018] In other embodiments, 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).
[0019] 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, CDMA2000 1X, 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 (GERAN), or the like.
[0020] The base station 114b of FIG. 1A may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity within a localized area, such as an office, a home, a vehicle, a 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 utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Therefore, the base station 114 b may not need to access the Internet 110 through the core network 106 .
[0021] The RAN 104 may communicate with a core network 106, which 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, 102d. For example, the core network 106 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A, it will be understood that the RAN 104 and / or the core network 106 may communicate, directly or indirectly, with other RANs that use the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may utilize E-UTRA radio technology, the core network 106 may also communicate with other RANs (not shown) that use GSM radio technology.
[0022] 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 providing plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) in 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 other core networks connected to one or more RANs that may use the same RAT as the RAN 104 or a different RAT.
[0023] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities, i.e., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links. For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a that may use a cellular-based wireless technology and with a base station 114b that may use IEEE 802 wireless technology.
[0024] 1B is a system diagram of an example WTRU 102. As shown in FIG. 1B, the WTRU 102 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 source 134, a Global Positioning System (GPS) chipset 136, and other peripherals 138. It will be understood that the WTRU 102 may include any subcombination of the above elements while remaining consistent with an embodiment.
[0025] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other function that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic circuit package or chip.
[0026] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over the 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 other embodiments, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In other embodiments, the transmit / receive element 122 may be configured to transmit and receive both RF and light signals. It will be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.
[0027] 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
[0028] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate over multiple RATs, such as UTRA and IEEE 802.11.
[0029] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 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 data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a 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, or the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
[0030] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control power to other components within 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 batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.
[0031] 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) regarding the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or may determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that the WTRU 102 may obtain location information by way of any suitable location determination method while remaining consistent with an embodiment.
[0032] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos or videos), a Universal Serial Bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.
[0033] 1C is a system diagram of the RAN 104 and the core network 106 according to an embodiment. As mentioned above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the core network 106.
[0034] The RAN 104 may include eNodeBs 140a, 140b, 140c, although it will be understood that the RAN 104 may include any number of eNodeBs while remaining consistent with an embodiment. The eNodeBs 140a, 140b, 140c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNodeBs 140a, 140b, 140c may implement MIMO technology. Thus, the eNodeB 140a may transmit wireless signals to, and receive wireless signals from, the WTRU 102a, for example, using multiple antennas.
[0035] Each of the eNodeBs 140a, 140b, 140c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users on the uplink and / or downlink, etc. As shown in FIG 1C, the eNodeBs 140a, 140b, 140c may communicate with one another over an X2 interface.
[0036] 1C may include a mobility management entity gateway (MME) 142, a serving gateway 144, and a packet data network (PDN) gateway 146. Although each of the above elements is shown as part of the core network 106, it will be understood that any one of these elements may be owned and / or operated by an entity other than the core network operator.
[0037] The MME 142 may be connected to each of the eNodeBs 140a, 140b, 140c in the RAN 104 through an S1 interface and may act as a control node. For example, the MME 142 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway upon initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 142 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that use other radio technologies, such as GSM or WCDMA.
[0038] The serving gateway 144 may be connected to each of the eNodeBs 140a, 140b, 140c in the RAN 104 through an S1 interface. The serving gateway 144 may generally route and forward user data packets to or from the WTRUs 102a, 102b, 102c. The serving gateway 144 may also perform other functions such as anchoring the user plane during inter-eNodeB handovers, triggering paging when downlink data for the WTRUs 102a, 102b, 102c is available, managing and storing the context of the WTRUs 102a, 102b, 102c, etc.
[0039] The serving gateway 144 may also be connected to a PDN gateway 146, which 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.
[0040] The core network 106 may facilitate communications with other networks. For example, the core network 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the core network 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the core network 106 and the PSTN 108. Additionally, the core network 106 may provide the WTRUs 102a, 102b, 102c with access to networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.
[0041] The other network 112 may further be connected to an IEEE 802.11 based wireless local area network (WLAN) 160. The WLAN 160 may include an access router 165. The access router may include a gateway function. The access router 165 may communicate with multiple access points (APs) 170a, 170b. The communication between the access router 165 and the APs 170a, 170b may be through wired Ethernet (IEEE 802.3 standard) or any type of wireless communication protocol. The AP 170a wirelessly communicates with the WTRU 102d over the air interface.
[0042] As wireless communication systems such as LTE systems mature and their network deployments develop, it may be beneficial for network operators to reduce the cost of the communication network, the need for maintenance of the communication network, or both. One technique for reducing the cost of the network may be to reduce the channel bandwidth and data rate used to communicate with devices. For example, when communicating with such devices, a portion of the channel bandwidth rather than the entire channel bandwidth may be supported by the devices in the network and / or the network itself. Current wireless communication systems, such as LTE, have recently been considering bandwidth reduction to a certain level, such as 1.4 megahertz (MHz), for some devices, including machine type communication (MTC) devices. Since, for example, LTE can already support operation with a system bandwidth of 1.4 MHz, the considered level may allow more compatibility with legacy systems and reduce new design time and / or cost. However, further bandwidth reduction may be desirable for some devices, such as smart watches and alarms, for example to further reduce costs. Further bandwidth reduction, for example to around 200 kilohertz (kHz), has been proposed. Further system design may be required to support operation with reduced bandwidth that may be less compatible with legacy system operation.
[0043] A reduced bandwidth (BW) WTRU may be a WTRU that may support or only support a certain limited number of resource blocks (RBs) in the downlink (DL) and / or uplink (UL), which may be independent of a certain restricted BW, e.g., RF BW, or BW of an eNodeB or cell with which the WTRU may communicate. For example, a reduced BW WTRU, which may also be referred to as a restricted BW WTRU, may support or only support a certain number of RBs, e.g., 6 RBs or 1 RB, or a certain BW, e.g., 1.4 MHz or 180 KHz, for transmission and / or reception. Such a WTRU may communicate with an eNodeB or cell for which the BW is larger, which may be, e.g., 20 MHz or 100 RBs.
[0044] An enhanced machine type communication (eMTC) WTRU may be a limited BW WTRU that may support a first number of RBs and / or a BW of a first bandwidth. The first number may be represented by N1, and the first bandwidth may be represented by B1. N1 may be, for example, 6, and B1 may be, for example, 1.4 MHz. In an example, 6 RBs may correspond to a BW of 1.4 MHz. An eMTC WTRU may be used to represent a non-limiting example of a limited BW WTRU. Another WTRU, which may be referred to as a Narrowband LTE (NB-LTE) or Narrowband Internet of Things (NB-IoT) WTRU, may be a limited BW WTRU that may support a second number of RBs and / or a BW of a second bandwidth. The second number may be represented by N2, and the second bandwidth may be represented by B2. N2 may be less than N1. B2 may be less than B1. N2 may be, for example, 1, and B2 may be, for example, 180 KHz. In an example, one RB may correspond to a BW of 180KHz. NB-LTE WTRU and / or NB-IoT WTRU may be used to represent non-limiting examples of limited BW WTRU. Narrowband (NB) WTRU may be used to represent non-limiting examples of WTRU or limited BW WTRU. WTRU, limited BW WTRU, BW-limited WTRU, reduced BW WTRU, limited capability WTRU, low-cost MTC (LC-MTC) WTRU, low-complexity WTRU, MTC WTRU, eMTC WTRU, NB-IoT WTRU, eMTC, NB-IoT, and NB WTRU may be used synonymously herein. An RB may be a physical RB (PRB). The terms RB and PRB may be used synonymously herein.
[0045] A limited BW WTRU may use or require special procedures to operate in a portion of the full BW of a cell. Reduced bandwidth, limited bandwidth, and bandwidth limit may be used synonymously herein. A WTRU that can support the full BW of a cell may be referred to as a full BW WTRU. The BW may include several RBs and / or a location within the band, such as the center of the band.
[0046] A WTRU may at least sometimes communicate, function, or operate in a manner that may be consistent, e.g., at least partially consistent, with that of a full BW WTRU, and may also at least sometimes communicate, function, or operate in a manner that may be consistent, e.g., at least partially consistent, with that of a reduced BW WTRU at some times other than, e.g., when operating as a full BW WTRU. For example, a WTRU that may support the full BW of a cell may communicate, function, or operate in a manner that may be consistent, e.g., at least partially consistent, with that of a reduced BW WTRU at some times, such as when it may be coverage limited or when it may operate in a coverage extension mode. A WTRU such as this example WTRU may be or be considered to be a full BW WTRU at times, and / or a reduced BW WTRU at other times, e.g.
[0047] A WTRU may be or be considered to be a reduced BW WTRU if it can, must, or is intended to, e.g., at least partially, function or operate like a reduced BW WTRU. A WTRU that may communicate, function, or operate, e.g., with an eNodeB, in a manner that may be consistent with or, e.g., at least partially consistent with, a reduced BW WTRU, e.g., at least sometimes when the WTRU may communicate, function, or operate in a manner that may be consistent, e.g., at least partially consistent with that of a reduced BW WTRU, may be or be considered to be a reduced BW WTRU.
[0048] It should be noted that the terms eNB, eNodeB, and cell may be used synonymously herein. Embodiments and examples described for a reduced BW WTRU may apply to a coverage-limited WTRU, and vice versa.
[0049] Coverage-limited and reduced BW WTRUs are examples of WTRUs that may use the example methods and procedures described herein. These coverage-limited and reduced BW WTRUs are non-limiting examples of such example WTRUs. Application of any capability or reduced capability to any type of WTRU may still be consistent with the example methods and procedures described herein.
[0050] The term physical downlink control channel (PDCCH) may be replaced by an enhanced PDCCH (EPDCCH), a machine type communication (MTC) physical downlink control channel (M-PDCCH), or other DL control channel, and vice versa, and still be consistent with the example methods and procedures described herein. The terms component carrier (CC) and serving cell may be used synonymously herein. The terms WTRU, WTRU medium access control (MAC) entity, and MAC entity may be used synonymously herein.
[0051] The terms WTRU, certain WTRU, or several WTRUs may be replaced by at least WTRU, at least certain WTRU, or at least several WTRUs and still be consistent with example methods and procedures described herein. The phrase "intends to" may be replaced by "at least intends to" or "intends at least to" and still be consistent with example methods and procedures described herein.
[0052] The exemplary methods and procedures described herein may be described for a random access response (RAR), a paging channel (PCH), or a physical downlink shared channel (PDSCH) that carries or may carry an RAR or a PCH. These are used as non-limiting examples. The RAR may be replaced by a PCH or a PCH PDSCH, or vice versa, and still be consistent with the exemplary methods and procedures described herein. The channel or other content carried by the PDSCH may be replaced by any channel or content and still be consistent with the exemplary methods and procedures described herein.
[0053] Exemplary methods and procedures involving coverage extension (CE) are disclosed herein. A coverage-extended WTRU may be a WTRU that may require coverage extension or that may use coverage extension techniques or may support a CE mode. The terms coverage-limited WTRU and coverage-extended WTRU may be used synonymously herein. CE may refer to extending or improving coverage, for example, for low data rate applications. CE may refer to extending or improving coverage, for example, to enable communication with devices having reduced capabilities, such as devices using a single receiver or devices using reduced bandwidth. CE may refer to extending or improving coverage, for example, to enable communication with devices for which communication may be impeded, such as indoor devices or devices in basements where penetration loss may impede communication. In at least some examples, CE may involve extending or improving coverage by reducing data rates. In at least some examples, CE may involve extending or improving coverage by using iterative techniques. In at least some examples, CE may be used for MTC applications. In at least some examples, CE may be used for NB or NB-IoT applications. The terms CE operation and coverage extension operation may be used synonymously herein.
[0054] For CE, repeated transmission of the physical channel may be used. For example, a CE level may be determined based on the number of repetitions that may be required or used to achieve the intended coverage improvement. The terms number of repetitions, number of repetitions, repetition level, and CE level may be used synonymously herein.
[0055] The CE mode may be used with one or more CE levels, or repetition levels, for example. The CE levels or repetition levels supported in the CE mode may be changed dynamically.
[0056] The eMTC WTRU may be, for example, a low-cost WTRU. The eMTC WTRU may be, for example, a WTRU with limited or reduced capabilities. The limited or reduced capabilities may include at least one of limited or reduced BW capabilities, for example, a BW with 6 RBs, low throughput performance, and a single RF chain at the receiver. The eMTC WTRU may be delay tolerant. The eMTC WTRU may be served in an LTE network that may or may not have a system BW larger than the eMTC supportable BW, which may be, for example, a BW of 1.4 MHz.
[0057] The eMTC WTRU may support coverage extension operation. Two CE operation modes may be supported, such as CE mode A and CE mode B. In CE mode A, standard and small CE levels may be supported, and in CE mode B, medium and large CE levels may be supported. Standard CE may be the same as standard operation or no CE, for example, no use of repetition for CE may be involved.
[0058] The NB-IoT WTRU may be, for example, a low-cost WTRU. The NB-IoT WTRU may be, for example, a WTRU with limited or reduced capabilities, which may be more limited or reduced in at least one aspect compared to the capabilities of an eMTC WTRU. For example, the NB-IoT WTRU may support or use a further reduced BW, for example, a BW of one RB, which may be smaller than the BW supportable for an eMTC WTRU.
[0059] The NB-IoT WTRU may support or be intended to support CEs with battery lives that may be longer than the intended or expected battery life of an eMTC WTRU, e.g., CEs up to 20 decibels (dB). The NB-IoT WTRU may be intended or expected to support a battery life of 10 years, etc. The population of NB-IoT WTRUs in a cell may be significantly larger than other types of devices.
[0060] Example methods and procedures for paging are discussed herein. Paging, as used herein, may refer to a connection setup initiated by the network. Paging, as used herein, may refer to a mechanism that the network may use to provide information, such as system information change information or warning system information, e.g., Earthquake and Tsunami Warning System (ETWS) information, to one or more WTRUs that may use techniques for battery conservation, such as, for example, discontinuous reception (DRX). In some examples, paging may be used when the WTRU is in an idle mode. In other examples, paging may be used when the WTRU is in a connected mode. The WTRU may, for example, periodically monitor the PDCCH, e.g., in idle mode and / or connected mode, for DL control information (DCI) or DL assignments on the PDCCH masked with a paging radio network temporary identifier (P-RNTI). When the WTRU detects or receives a DCI or DL assignment with the P-RNTI, the WTRU may demodulate an associated or indicated PDSCH RB and / or decode a paging channel (PCH) that may be carried on the associated or indicated PDSCH. A PDSCH that can carry a PCH may be referred to as a PCH PDSCH. The terms paging, paging message, and PCH may be used synonymously herein. As used herein, the terms downlink control channel, DL control channel for a NB WTRU, M-PDCCH, PDCCH, NB PDCCH (NB-PDCCH), Internet of Things PDCCH (IoT-PDCCH), and NB IoT-PDCCH (NB-IoT-PDCCH) may be used synonymously.
[0061] The paging frames (PFs) and subframes within that PF, e.g., paging occasions (POs), that the WTRU may monitor for a paging channel, e.g., in idle mode, may be determined based on a WTRU identifier (ID), e.g., WTRU_ID or UE_ID, and parameters that may be specified by the network. The parameters may include a paging cycle (PC) length in frames, which may be the same as a discontinuous reception (DRX) cycle, and another parameter, e.g., nB, which together may allow for the determination of the number of PFs per PC and the number of POs per PF that may exist in a cell. In an example, the WTRU ID may be the WTRU International Mobile Subscriber Identity (IMSI) mod 1024. The terms WTRU ID, WTRU-ID, and WTRU_ID may be used synonymously herein.
[0062] From the network perspective, there may be multiple PFs per paging cycle, and multiple POs within a PF, e.g., two or more subframes per paging cycle, may carry a PDCCH masked with a P-RNTI. Furthermore, from the WTRU perspective, the WTRU may monitor the PO per paging cycle, and such a PO may be determined based on parameters specified herein, which may be provided to the WTRU through system information, dedicated signaling information, etc. The POs may include pages for one or more WTRUs, or they may include system information change pages that may be directed to each of the WTRUs, multiple WTRUs, or all WTRUs. In idle mode, the WTRU may receive pages for reasons such as an incoming call or a system information update change.
[0063] In connected mode, the WTRU may receive pages related to, e.g., system information changes, and the WTRU may not receive WTRU-specific pages, such as those that may be used for incoming calls. Thus, in connected mode, the WTRU may not monitor a specific PO. Furthermore, for frequency division duplex (FDD), the PO subframes may be limited to certain subframes, such as subframes 0, 4, 5, and 9, and / or for time division duplex (TDD), the PO subframes may be limited to certain subframes, such as subframes 0, 1, 5, and 6.
[0064] DRX, as used herein, may refer to a WTRU monitoring for DL control signaling or DL control channels only at certain times, e.g., at certain times during a cycle. For example, a WTRU using DRX may monitor for DL control channels only during certain periods, e.g., during certain periods. During other periods, the WTRU may switch off at least a portion of its receiver circuitry to reduce power consumption. The periods may be, for example, subframes. Exemplary methods for operation with DRX are discussed herein.
[0065] In an idle mode, for example, a radio resource control (RRC) idle mode and / or an evolved packet system (EPS) connection management (ECM) idle mode, the WTRU may monitor or listen for paging messages to learn about one or more of an incoming call, a system information change, an Earthquake and Tsunami Warning System (ETWS) notification for a WTRU with ETWS capability, a Commercial Mobile Alert Service (CMAS) notification, and an Extended Access Barring (EAB) parameter change.
[0066] The WTRU may discontinuously monitor the PDCCH for the P-RNTI, e.g., to reduce battery consumption when there may be no page for the WTRU. DRX may or may not include a process for discontinuously monitoring the PDCCH. In idle mode, DRX may be or may include a process for discontinuously monitoring the PDCCH for the P-RNTI, e.g., to monitor or listen for paging messages during RRC idle state.
[0067] The terms idle mode, idle state, RRC idle mode, RRC idle state, and RRC_IDLE mode or state may be used synonymously herein. The terms RRC idle and ECM idle may be used synonymously herein. DRX may also be enabled and / or used in connected mode. If DRX is configured when in connected mode, the MAC entity may, for example, discontinuously monitor the PDCCH using DRX operation. The terms connected mode, connected state, and RRC_CONNECTED mode or state may be used synonymously herein.
[0068] Examples of operation in idle mode DRX are discussed herein. The WTRU may determine a PF and / or PO to monitor for paging using one or more DRX parameters, which may be broadcast in a system information block (SIB), such as SIB2. Alternatively, for example, the WTRU may use one or more WTRU-specific DRX cycle parameters, which may be signaled to the WTRU, for example, by the MME through non-access stratum (NAS) signaling.
[0069] Table 1 provides example DRX parameters, including example ranges, and example sources of the DRX parameters, such as, for example, an eNodeB or an MME.
[0070] [Table 1]
[0071] The DRX cycle T of the WTRU may indicate the number of radio frames within a paging cycle. A larger value of T may result in less WTRU battery power consumption. A smaller value of T may increase WTRU battery power consumption. The DRX cycle may be cell-specific or WTRU-specific.
[0072] The DRX cycle provided by the eNodeB may be cell-specific and may be provided to at least some, e.g., all, WTRUs in the cell. The DRX cycle provided by the eNodeB may be a default paging cycle. The DRX cycle provided by the MME may be WTRU-specific. The WTRU may use the smaller of the default paging cycle and the WTRU-specific DRX cycle as its DRX or paging cycle. The MME may provide the WTRU-specific DRX cycle to the WTRU using NAS signaling, e.g., as "WTRU-specific DRX cycle". The MME may provide the WTRU-specific DRX cycle to the eNodeB, e.g., as "Paging DRX" in a Paging S1 AP message for MME-initiated paging messages, which may be targeted to the WTRU.
[0073] The WTRU and / or eNodeB may use the minimum of the default and WTRU-specific DRX cycles. For example, T=Min(T WTRU ,T CELL ). A WTRU with a DRX cycle of N (e.g., 128) radio frames may be able to wake up or may need to wake up and look for paging messages every N×frame time (e.g., every 1.28 seconds for a 10 ms frame time).
[0074] The parameter nB may indicate the number of paging occasions or POs within a cell-specific DRX cycle. The parameter may be cell-specific. The configuration of the nB value may depend on the paging capacity that may be desired or used in the cell. For example, to increase the paging capacity, a larger value of nB may be used. For example, for a smaller paging capacity, a smaller value of nB may be used.
[0075] The eNodeB and / or WTRU may calculate the PF of the WTRU according to the following relationship, i.e., the PF is given by the following equation or occurs when SFN mod T=(T div N)×(WTRU_ID mod N), where N=min(T,nB), and div may represent division. A WTRU-specific PO within the PF may be determined from a set of paging subframes. The set may be a function of predefined allowed subframes for paging, and / or the number of POs per PF, which may be a function of at least nB and / or T. The system frame number (SFN) may have a range of values, such as from 0 to 1023.
[0076] An example of connected mode DRX is discussed herein. In connected mode, the PF and PO may be determined in a similar manner to idle mode. DRX cycle parameters may be different for idle and connected modes. The WTRU may monitor a PO, e.g., any PO in a PC in connected mode, e.g., to obtain system information change information.
[0077] Extended DRX (eDRX) is disclosed herein. For devices such as MTC devices, it may be desirable to have an extended or longer DRX cycle. An extended or longer DRX cycle may be useful for some devices, such as delay tolerant devices, for example to reduce battery consumption and / or increase battery life of those devices. A new time unit, such as a hyperframe (HF), may be used, for example, as an extension of or in addition to radio frames and / or SFN timing, such as legacy SFN timing.
[0078] FIG. 2 is an exemplary timing diagram illustrating HFs and paging within the HFs. One HF may include a SFN cycle, e.g., 1024 radio frames or 10.24 s. The HF may have a hyper system frame number (H-SFN). The H-SFN cycle may be 1024 SFN cycles. The H-SFN cycle may last 1024×1024×10 ms, e.g., 174.76 minutes. In the example shown in timing diagram 200, HF 210 may have H-SFN0 and may include a SFN cycle of 1024 radio frames from radio frame 0 to radio frame 1023. Similarly, HF 220 may have H-SFN1023 and may include its own SFN cycle of 1024 radio frames. H-SFN cycle 230 may include 1024 HFs, including HF 210 to HF 220.
[0079] An idle mode extended DRX (I-eDRX) cycle may include up to 256 H-SFN cycles and may last, for example, 256 x 1024 x 10 ms, e.g., 43.69 minutes. The H-SFN may be broadcast by the cell. The H-SFN may be incremented at the SFN cycle boundary.
[0080] The H-SFN at which the WTRU may be reachable for paging may be referred to as a paging hyperframe (PH), or the WTRU's PH. The PH may be applicable in ECM-IDLE or may be applicable only in it. The PH may be calculated as a function of the extended DRX cycle and / or the WTRU ID, e.g., IMSI mod 1024. The determination of the PF and / or PO within the PH may follow normal DRX rules and / or formulas. The WTRU's paging window (PW) may be a window or time span corresponding to a set of PFs within the WTRU's PH during which the WTRU may monitor for paging and / or may be paged. The PW may include a subset of the available PFs within the PH. In the example shown in timing diagram 200, PW 250 may include PF 260, PF 270, and PF 280. PF 260, PF 270, and PF 280 may be PFs within PH 290. The eDRX cycle 295 may include PH 290. The PW may be signaled to the WTRU, for example, by the MME in a NAS message. Within a PF, the WTRU may monitor one PO or may monitor only one. Paging to the WTRU may be repeated in one or more of its PFs within its PW, for example if the WTRU does not respond to a previous page.
[0081] A cell's support for idle mode extended DRX may be implicit by broadcasting the H-SFN. For long DRX cycles, it may be useful for the MME to have some knowledge of when the WTRU may be reachable, e.g. to avoid storing paging requests in the eNodeB for a long time. In connected mode, the DRX cycle may be extended up to the SFN limit, e.g. by extending the value range up to 10.24 seconds for long DRX cycles.
[0082] A large population of NB WTRUs may be multiplexed within a limited number of paging resources. If the distribution of WTRUs among paging resources is based on WTRU-ID, e.g., IMSI or IMSI modulo 1024, there may still be a large number of WTRUs sharing the same paging resource, e.g., in time and / or frequency, e.g., sharing the same PO and / or paging NB.
[0083] The NB WTRU may monitor the M-PDCCH in the PO or each of its POs. If the M-PDCCH, or a DCI in the M-PDCCH, indicates scheduling of an associated PDSCH for a paging message, the NB WTRU may, for example, receive the associated PDSCH to check whether a paging message targeted to the NB WTRU may be present.
[0084] Since multiple NB WTRUs may share the same paging resource, the NB WTRU may receive the associated PDSCH when the paging message may not be targeted to the NB WTRU. Receiving the associated PDSCH that may not be targeted to the WTRU may, for example, unnecessarily increase the battery consumption of the WTRU. If the NB WTRU is in a CE level that may use multiple repetitions, the impact on the WTRU may be worse, for example significantly worse.
[0085] A NB WTRU may, for example, monitor the M-PDCCH within a PO or within each PO in an NB WTRU-specific or NB WTRU group-specific manner. The M-PDCCH may, for example, implicitly or explicitly indicate a need by a WTRU or group of WTRUs to receive and / or decode the M-PDCCH and / or associated PDSCH. For example, the M-PDCCH may implicitly or explicitly indicate an intended recipient of the M-PDCCH, an associated PDSCH, a page, a paging message, or a PDSCH carrying a paging message or channel. Additionally, an implicit indication of paging reception, the need for paging reception, or the intended recipient of an M-PDCCH, PDSCH, page, paging message, or PDSCH carrying a paging message or channel may be used, which uses one or more of the following: a scrambling indication; a scrambling sequence, such as a scrambling sequence for M-PDCCH randomization, a WTRU group-specific or WTRU-specific scrambling sequence, an information type specific scrambling sequence, or a scrambling sequence for paging reception; a starting enhanced control channel element (ECCE) index for M-PDCCH randomization, a bit interleaver for M-PDCCH randomization; and / or one or more Radio Network Temporary Identifiers (RNTIs).
[0086] In an example, a scrambling sequence may be used to randomize the bit sequence of the M-PDCCH. WTRUs that descramble the received bits with the same scrambling sequence may receive or be able to receive the M-PDCCH. In an example, only WTRUs that descramble the received bits with the same scrambling sequence may receive or be able to receive the M-PDCCH.
[0087] The bit sequence of the M-PDCCH may be the bit sequence before modulation of the M-PDCCH. For example, the bit sequence of the M-PDCCH may be the bit sequence after rate matching. The coded bit sequence may be the input bit sequence of the rate matching, and the output bit sequence of the rate matching may be the bit sequence of the M-PDCCH. The DCI with a cyclic redundancy check (CRC) scrambled by the RNTI may be the input bit sequence of the channel coding block, and the output bit sequence may be the coded bit sequence.
[0088] The bit sequence of the M-PDCCH may be a bit sequence before channel coding, for example, DCI whose CRC is scrambled by the RNTI.
[0089] For the RNTI, one or more of the following examples may apply: For example, if DCI may be used for paging, the RNTI may be a P-RNTI. In another example, the RNTI may be a group-specific P-RNTI that may be associated with a scrambling sequence. In another example, the RNTI may be the N least significant bits (LSBs) of a WTRU-ID that may be used for paging. N may be the number of CRC bits, which may be referred to as NCRC. For example, the 16 LSBs of the WTRU-ID may be used, e.g., the IMSI or System Architecture Evolution (SAE) Temporary Mobile Subscriber Identity (s-TMSI). The N bits used for the RNTI may be the same N bits corresponding to the WTRU-ID modulo (2^N), e.g., the IMSI modulo (2^N), where N may be 16.
[0090] In the example, the bit sequence of M-PDCCH is b(0), , b(M bit−1) can be scrambled with a constant scrambling sequence c(i), where M bit may be the number of bits in the bit sequence of the M-PDCCH. The result of the WTRU-specific or WTRU group-specific scrambling sequence is
[0091]
number
[0092] It may be referred to as:
[0093] In the example
[0094]
number
[0095] The bit sequence is
[0096]
number
[0097] where mod 2 may be a modulo 2 operation. Furthermore, the scrambling sequence c(i) may be determined based on an initialization value c init where i may be a bit index of the bit sequence.
[0098] The certain scrambling sequence may be determined based on at least one of whether the M-PDCCH or scrambling sequence is WTRU-specific or WTRU group-specific, an information type in the associated DCI, or an information type in the associated PDSCH. init) may be determined based on at least the WTRU-ID, at least the associated WTRU group number, at least the information type in the associated DCI, at least the information type of the associated PDSCH and / or the RNTI.
[0099] A WTRU that may monitor or attempt to decode a bit sequence of an M-PDCCH in an example may use its associated scrambling sequence. The associated scrambling sequence may be determined based on at least one of whether the M-PDCCH or scrambling sequence is WTRU-specific or WTRU group-specific and / or the type of information in the DCI. For example, the associated scrambling sequence may be determined based on the type of information in the DCI for which the WTRU may monitor WTRU-specific or WTRU group-specific paging. In an example, the WTRU may descramble with an input bit sequence of a channel decoder. The WTRU may also descramble with an output bit sequence of a channel decoder. In an example, the bit sequence of an M-PDCCH received at a WTRU receiver may be d(0),...,d(M bit -1),
[0100]
number
[0101] The sequence may be referred to as a descrambled bit sequence with an associated scrambling sequence c(i).
[0102]
number
[0103] Descrambling can be performed by
[0104] A WTRU-specific scrambling sequence and / or a WTRU group-specific scrambling sequence may be provided and / or used. In an example, a WTRU-specific or WTRU group-specific scrambling sequence, e.g., a first scrambling sequence, may be used to scramble a bit sequence of an M-PDCCH, e.g., in a PO or each PO. In an example, a WTRU or a WTRU group that may use the same scrambling sequence, e.g., the first scrambling sequence, may decode or be able to decode the M-PDCCH. For example, only a WTRU or a WTRU group that may use the same scrambling sequence, e.g., the first scrambling sequence, may decode or be able to decode the M-PDCCH.
[0105] In an example using a WTRU group-specific scrambling sequence, g The scrambling sequences are g WTRU groups, g A bit sequence of an M-PDCCH intended or targeted for a WTRU group, e.g., a first WTRU group, in the WTRU groups may be scrambled with a corresponding scrambling sequence, e.g., a first scrambling sequence. In an example, the WTRU group using the corresponding scrambling sequence, e.g., the first scrambling sequence, may receive or be able to receive the M-PDCCH. In another example, only the WTRU group using the corresponding scrambling sequence, e.g., the first scrambling sequence, may receive or be able to receive the M-PDCCH. The WTRU group-specific scrambling sequence may be determined based on at least one of the following: g and a modulo operation that may be based on the WTRU-ID; e.g., N g and a hash function that may be based on the WTRU-ID; and a WTRU group number, which may be determined based on, for example, at least, the CE level.
[0106] Modulo arithmetic is at least N g and WTRU-ID(N WTRUID ), modulo arithmetic may be used. group ) is the WTRU-ID modulo N g (e.g., N group =(N WTRUID ) mod N g ). Subframe number and / or frame number (e.g., SFN) may be used. For example, N group =(N WTRUID N Frame ) mod N g .
[0107] A hash function can be used, where the hash function is N g and the WTRU-ID. In this case, for example, group =(A N WTRUID ) mod N g , where A can be a prime number (e.g., A=39,827), or N group =((A N WTRUID ) mod D) mod N g , where D is a prime number that may be different from A (eg, D may be 65,537). The hash function may be based on the subframe number and / or the frame number.
[0108] The WTRU group number may be determined based on at least the CE level, for example, WTRUs having a first CE level (e.g., CE level 1) may be grouped into a first WTRU group, and WTRUs having a second CE level (e.g., CE level 2) may be grouped into a second WTRU group.
[0109] The WTRU-ID may be at least one of the RNTI, IMSI, and s-TMSI allocated for the WTRU, and / or a portion of at least one of the allocated RNTI, IMSI, and s-TMSI. For example, the WTRU-ID may be an IMSI modulo M, or an s-TMSI modulo N. M and / or N may be 1024. A and / or D may be N. g A and / or D may be fixed and / or configurable by the eNodeB, for example through signaling. WTRUID may be a portion or function of the WTRU-ID, or the IMSI or s-TMSI of the WTRU. WTRUID can be IMSI-10, or IMSI modulo X, where X can be a number less than or equal to 1024.
[0110] In an example using a WTRU-specific scrambling sequence, the WTRU-specific scrambling sequence may be used for a bit sequence of an M-PDCCH intended or targeted for the WTRU, and the WTRU-specific scrambling sequence may be determined based on at least a WTRU-ID or a portion of the WTRU-ID. In MME initiated paging, the WTRU-ID may be provided by the MME to the eNodeB in an S1 paging message or request.
[0111] In an example, the scrambling sequence may be determined based on a particular information type that may be carried within the DCI, e.g., a first scrambling sequence may be used for a bit sequence of an M-PDCCH in which the DCI may carry a first information type, and a second scrambling sequence may be used for a bit sequence of an M-PDCCH in which the DCI may carry a second information type.
[0112] The first information type may include, but is not limited to, at least one or more system information update displays such as system information change display, ETWS display, CMAS display, and EAB parameter change display. One or more system information displays can be a single bit for indicating system information update, or multiple bits for indicating system information updates of multiple SIs, such as SIB or SI messages. Additional indicators, such as flag bits for indicating DCI format or DCI type, may be included. The scrambling sequence for the first information type can be based on at least one cell-specific parameter, such as a physical cell ID, etc.
[0113] The second information type can be at least the scheduling information of the associated PDSCH. The scrambling sequence for the second information type can be based on at least one of the WTRU-specific parameters, such as the WTRU-ID, etc.
[0114] In other examples, the scrambling sequence can be determined based on the information type carried within the DCI and / or WTRU-ID. For example, the first scrambling sequence can be used for the bit sequence of the M-PDCCH in which the DCI can carry the first information type, and the second scrambling sequence can be used for the bit sequence of the M-PDCCH in which the DCI can carry the second information type. The first scrambling sequence can be predefined. The second scrambling sequence can be determined based on the WTRU-ID.
[0115] In an example, the POs for the first and second information types may be the same. Furthermore, the WTRU may monitor the M-PDCCH for both the first and second information types. Or, the WTRU may monitor the M-PDCCH for the first information type in a subset of the POs or all POs. The WTRU may monitor the M-PDCCH for the second information type in a subset of the POs or all POs.
[0116] In other examples, the PO for the first information type and the second information type may be different. The time and / or frequency location of the PO for the first information type may be determined based on at least one cell-specific parameter. The cell-specific parameters may include, for example, a physical cell ID, a system bandwidth, a subframe number, a frame number such as SFN, etc. The time and / or frequency location of the PO for the second information type may be determined based on at least one WTRU-specific parameter, for example, a WTRU-ID.
[0117] Examples including the use of scrambling sequences for paging reception are disclosed herein. The WTRU can determine a bit scrambling sequence, e.g., an M-PDCCH bit scrambling sequence, according to one or more examples described herein. In an example, the WTRU can monitor for the M-PDCCH in a PO. The WTRU can use the bit scrambling sequence to descramble the received signal or the M-PDCCH. The WTRU can determine whether the descrambled M-PDCCH can carry a DCI masked with an RNTI that the WTRU can use for paging. The RNTI can be, for example, a P-RNTI. If the WTRU determines that the DCI is masked with an RNTI, e.g., a P-RNTI, the WTRU can read the contents of the DCI to obtain one or more of system information update information and / or PDSCH scheduling information. The WTRU can use the scheduling information to receive an associated PDSCH that can carry one or more paging records or paging messages.
[0118] An example of the use of a starting ECCE index for M-PDCCH randomization is disclosed herein. In an example, an M-PDCCH search space can be used to monitor for M-PDCCH or DCI, e.g., a starting ECCE index for monitoring can be determined based on at least one WTRU-specific parameter. For example, a WTRU can use an M-PDCCH search space for monitoring for M-PDCCH or DCI, e.g., a starting ECCE index for monitoring can be determined based on at least one WTRU-specific parameter. As used herein, control channel element (CCE), ECCE, and NB-IoT control channel element (NCCE) may be used synonymously.
[0119] FIG. 3 is an example diagram illustrating a WTRU group specific starting ECCE index. Diagram 300 illustrates an example of an ECCE in a subframe 310 at ECCE aggregation level 16. In other examples, other ECCE aggregation levels such as 1, 2, 4, 8, and 32 may be used. In the example illustrated in FIG. 3, the WTRUs may use different starting ECCE indexes depending on the group in which the WTRU resides. For example, the WTRUs may be divided into four WTRU groups, numbered WTRU group #1 through WTRU group #4. The WTRUs in WTRU group #1 may use a starting ECCE index 330 having a starting ECCE of 1, the WTRUs in WTRU group #2 may use a starting ECCE index 350 having a starting ECCE of 5, the WTRUs in WTRU group #3 may use a starting ECCE index 370 having a starting ECCE of 9, and the WTRUs in WTRU group #4 may use a starting ECCE index 390 having a starting ECCE of 12.
[0120] 4 is a diagram of an example flow chart illustrating a WTRU receiving a machine type communication (MTC) physical downlink control channel (M-PDCCH) with a starting ECCE index based on the WTRU's WTRU group. In the example shown in chart 400, the WTRU may monitor for an M-PDCCH in an M-PDCCH search space 410. The WTRU may monitor for an M-PDCCH using a starting ECCE index for the WTRU group that includes the WTRU. The WTRU may then receive an M-PDCCH in the M-PDCCH search space, which may have a starting ECCE index for the WTRU group that includes the WTRU 420. In an example corresponding to the WTRU group shown in FIG. 3, the WTRU may be in WTRU group #2 and therefore may monitor and / or receive for an M-PDCCH with a starting ECCE index 350 of 5. Additionally, at 430, the WTRU may decode the M-PDCCH, which includes DCI. At 440, the WTRU may receive a PDSCH associated with the M-PDCCH or DCI, e.g., a PDSCH scheduled by the M-PDCCH or DCI. In an example, the WTRU may receive, decode, attempt to decode, demodulate, and / or attempt to demodulate a PDSCH based on the DCI, which may include a paging message. As a result, the WTRU may change its operation based on the paging message. For example, the WTRU may change from an idle mode to a connected mode based on the paging message. The WTRU may then start transmitting and receiving in the connected mode. In another example, the WTRU may already be in a connected mode and may change its system operation based on the system information change information in the page message.
[0121] In other examples, an M-PDCCH search space can be used for DCI monitoring, and to determine M-PDCCH candidates, a starting ECCE index and an ordering (e.g., ascending, descending, random order, and / or a predefined order) can be used. For example, the number N of ECCEs ECCE is available in the search space, and when the ECCE aggregation level is the same as N for an M-PDCCH candidate ECCE one or more M-PDCCH candidates can be determined based on the starting ECCE index and / or the ordering.
[0122] M-PDCCH candidates can be aggregated in ascending order, descending order, ascending order by the starting ECCE index, or descending order by the starting ECCE index, with N ECCE ECCEs defined or configured by the number of ECCEs. In an example, the starting ECCE index and / or the ordering can be determined based on at least one WTRU-specific parameter. In other examples, the starting ECCE index and / or the ordering can be determined based at least on the type of information carried within the DCI.
[0123] In other examples, an M-PDCCH search space can be used for DCI monitoring, and ECCE aggregation can be sequence-based. The sequence for ECCE ordering can be determined based on at least one WTRU-specific parameter.
[0124] FIG. 5 is an example diagram illustrating WTRU group-specific random ECCE ordering. The sequence for ECCE ordering may be determined based on at least one WTRU-specific parameter as shown in diagram 500. Similar to FIG. 3, FIG. 5 illustrates an example 510 of ECCE in a subframe at ECCE aggregation level 16. In an example, the sequence may determine the ECCE ordering for ECCE aggregation. In another example, the sequence for ECCE ordering may be determined based on at least one of a WTRU-specific parameter, an information type carried in the DCI, an RNTI that may be used for CRC scrambling, a DCI format used, and a CE level or a repetition number, such as the number of repetitions of M-PDCCH candidates.
[0125] In other examples, a set of random sequences may be predefined or configured, for example, for a group of WTRUs. The sequence may correspond to a starting ECCE index. The sequence may correspond to an ECCE aggregation ordering.
[0126] In the example shown in FIG. 5, WTRUs may use different starting ECCE indices depending on the random sequences that may be defined, configured, and / or used by or for the group the WTRU resides in. For example, WTRUs may be divided into four WTRU groups, numbered WTRU group #1 through WTRU group #4. WTRUs in WTRU group #1 may use a first random sequence 530 that may correspond to a starting ECCE index of 4, WTRUs in WTRU group #2 may use a second random sequence 550 that may correspond to a starting ECCE index of 5, WTRUs in WTRU group #3 may use a third random sequence 570 that may correspond to a starting ECCE index of 9, and WTRUs in WTRU group #4 may use a fourth random sequence 590 that may correspond to a starting ECCE index of 12. For example, the random sequences in the set may be determined based on at least one of a WTRU-specific parameter, an information type carried in the DCI, an RNTI that may be used for CRC scrambling, a DCI format used, or a CE level, or a number of repetitions, e.g., the number of repetitions of M-PDCCH candidates.
[0127] An example using a bit interleaver for M-PDCCH randomization is disclosed herein. In an example, a bit sequence for the M-PDCCH may be interleaved by an interleaving sequence. The interleaving sequence may be a sequence having a length of the bit sequence. Bit positions may be interleaved based on the interleaving sequence. In an example, the interleaving sequence may be determined based on at least one or more of at least one WTRU-specific parameter, an information type carried in the DCI, an RNTI that may be used for CRC scrambling, a DCI format used, and a CE level or a repetition number, such as a repetition number of M-PDCCH candidates. In another example, the WTRU may deinterleave a received bit sequence with the interleaving sequence before attempting to decode the received bit sequence.
[0128] In an example, one or more RNTIs may be used for the DCI, for example to indicate to the WTRU whether to decode the associated PDSCH. For example, a cell-specific P-RNTI and one or more WTRU group-specific P-RNTIs may be used. The WTRU may attempt to decode the M-PDCCH with the cell-specific P-RNTI and / or the associated WTRU group-specific P-RNTI in the PO. In an example, a first P-RNTI may be used for the DCI carrying a first information type. In another example, a second P-RNTI may be used for the DCI carrying a second information type. Also in the PO, the WTRU may attempt to decode the DCI with the first P-RNTI and / or the second P-RNTI.
[0129] The first P-RNTI may be used for a DCI carrying a first information type. The first P-RNTI may be a cell-specific P-RNTI. The first information type may include at least one or more system information update indications, such as, but not limited to, a system information change indication, an ETWS indication, a CMAS indication, and an EAB parameter change indication. The one or more system information indications may be a single bit to indicate a system information update, or multiple bits to indicate a system information update, such as multiple SIs, e.g., SIBs or SI messages. Additional indicators, such as flag bits to indicate a DCI format or DCI type, may be included. The first P-RNTI may be based on at least one cell-specific parameter, such as a physical cell ID.
[0130] The second P-RNTI may be used for the DCI carrying the second information type. A set of P-RNTIs may be predefined or configured for the second P-RNTI, and one of the predefined or configured P-RNTIs may be determined in a WTRU-specific or WTRU group specific manner. A modulo operation with the WTRU-ID and / or the number of configured P-RNTIs may be used to determine the associated P-RNTI. A hash function may be used with the configured WTRU-ID and / or the number of P-RNTIs to determine the associated P-RNTI.
[0131] Within the PO, the WTRU may attempt to decode the DCI via a first P-RNTI. The WTRU may also attempt to decode the DCI via a second P-RNTI, which may be associated with the WTRU. If the WTRU is able to successfully decode the DCI via the first P-RNTI, the WTRU may not monitor the DCI via the second P-RNTI. If the WTRU is unable to successfully decode the DCI via the second P-RNTI, the WTRU may assume that the associated PDSCH may not be scheduled.
[0132] Explicit indications of paging reception are disclosed herein including the use of, among others: paging occasion type, monitoring indicator for paging occasion, paging type, paging message, paging window; multiple monitoring indicators; and multiple monitoring indicators having explicit and implicit indications. In examples, one or more paging occasion types may be used, configured or defined, e.g., for an RRC idle WTRU and / or an RRC connected WTRU.
[0133] A first paging occasion type may be used for paging message transmission in which the WTRU may monitor for paging messages. The paging message may include one or more paging records and / or one or more system information update indications. In an example, the paging message may be carried in a DCI. In another example, the paging message may be carried in a PDSCH, and scheduling information for the PDSCH may be provided in an associated DCI. Also, the paging message may be carried in a PDSCH without an associated DCI for scheduling information. Furthermore, the content of the paging message may be indicated from the associated DCI. For example, the DCI may indicate the information type included in the paging message.
[0134] In an example, a second paging occasion type may be used for one or more system information update indications. In another example, one or more paging occasion types may be located within the same time / frequency resource and monitored separately.
[0135] The time / frequency locations for one or more paging occasion types may be determined independently. The time / frequency location of a first paging occasion type may be determined based on at least one WTRU-specific parameter, such as, for example, a WTRU-ID. The time / frequency location of a second paging occasion type may be determined based on at least one cell-specific parameter, such as, for example, a physical cell ID, (e)DRX cycle, system bandwidth, etc.
[0136] In an example, the DCI format or DCI content may differ according to the paging occasion type, and further, the associated RNTI may differ according to the paging occasion type.
[0137] In an example, an indication for monitoring, e.g., one or more of a PO type, a monitoring indicator may be transmitted in a broadcast channel, e.g., in a MIB, in a DCI in a common search space, etc. For example, the broadcast channel may be transmitted every xms, and one or more POs may be associated with the broadcast transmission. The broadcast transmission may indicate whether the WTRU may need to monitor one or more POs associated with the broadcast transmission. The WTRU may attempt to decode or read the broadcast channel, which may carry the monitoring indicator, before it may monitor the one or more POs. In an example, the monitoring indicator may be associated with one or more PO types. For example, the monitoring indicator may be associated with a first PO type. In another example, the monitoring indicator may be associated with only the first PO type. In another example, the monitoring indicator may be associated with a second PO type. In another example, the monitoring indicator may be associated with only the second PO type. In an example, the monitoring indicator may be set to TRUE or FALSE. Based on the monitoring indicator, the WTRU may monitor a WTRU group-specific PO, which may be determined based on at least one of a WTRU-specific parameter, such as a WTRU-ID, or a cell-specific PO, which may be determined based on at least one cell-specific parameter, such as a physical cell ID.
[0138] The monitoring indicator may be associated with one or more POs. For example, the monitoring indicator may be associated with a PO within a certain time window. If the WTRU receives a monitoring indicator, the WTRU may attempt to receive or monitor the PO within the certain time window.
[0139] The monitoring indicator may indicate a WTRU group index, and the WTRU group associated with the monitoring indicator may monitor the PO. In an example, the monitoring indicator may indicate which WTRU group needs to monitor the PO. The WTRU group may include all WTRU groups for system information updates. In another example, the monitoring indicator may have several states, such as four states, and may indicate at least one of the states. The states may include, for example, cell-common paging, a first WTRU group, a second WTRU group, and a third WTRU group. In an example, the cell-common page may exist or occur in a cell-specific PO. The WTRU may monitor the PO or monitor a page according to the monitoring indicator state.
[0140] The monitoring indicator may indicate a PO type, and the WTRU may monitor the PO corresponding to the PO type. In an example, the WTRU may receive a monitoring indicator indicating a first PO type, and then the WTRU may monitor the PO corresponding to the first PO type. Further, the WTRU may receive a monitoring indicator indicating the first PO type, and then the WTRU may monitor only the PO corresponding to the first PO type.
[0141] In other examples, the monitoring indicator may be used with a WTRU group-specific M-PDCCH scrambling sequence, a WTRU group-specific RNTI, a WTRU group-specific starting ECCE index, and / or a WTRU group-specific interleaver. The monitoring indicator may be used to indicate whether the WTRU may need to monitor a PO associated with it, and an implicit indication of the paging reception scheme may be used in each PO. The WTRU may attempt to decode, receive, or monitor, for example, the monitoring indicator, and if the monitoring indicator indicates that the WTRU may need to monitor a PO, the WTRU may attempt to decode or monitor the PO with its associated scrambling sequence, starting ECCE index, RNTI, and / or interleaving sequence, for example, for the M-PDCCH. Further, the WTRU may first attempt to decode, receive, or monitor the monitoring indicator, and if the monitoring indicator indicates that the WTRU may need to monitor the PO, the WTRU may attempt to decode or monitor the PO, for example, for the M-PDCCH, with its associated scrambling sequence, starting ECCE index, RNTI, and / or interleaving sequence.
[0142] In an example, one or more monitoring indicators may be used to allow the WTRU to determine whether it needs to monitor, receive, or attempt to decode an M-PDCCH and / or a PDSCH carrying paging related information. To determine whether the WTRU needs to monitor or attempt to decode an M-PDCCH in a PO, a monitoring indicator may be used, which may be referred to as a PO (Paging Occasion) monitoring indicator. To determine whether the WTRU needs to receive an associated PDSCH that may carry a paging message (PM), a monitoring indicator may be used, which may be referred to as a PM monitoring indicator. To determine whether the WTRU needs to monitor a PO in a paging window (PW), a monitoring indicator may be used, which may be referred to as a PW monitoring indicator. A PW may include one or more POs for the WTRU. A PW may be defined or determined based on the number of POs. For example, a PW may be defined based on the number of POs for a WTRU. PO POs, N PO can be a positive integer.
[0143] The monitoring indicator may be used to determine whether the WTRU needs to receive, attempt to decode, or monitor a subsequent monitoring indicator. The WTRU may receive the monitoring indicator before it may decode, monitor, attempt to decode, receive, or attempt to receive a signal in a PO, e.g., M-PDCCH or PDSCH. Two monitoring indicators may be used, where the first monitoring indicator may be a PO monitoring indicator and the second monitoring indicator may be a PM monitoring indicator. The first monitoring indicator may be transmitted in a broadcast channel. The second monitoring indicator may be transmitted in a DCI, e.g., M-PDCCH.
[0144] The PM monitoring indicator may be composed of one or more bits to indicate at least one of the following: the presence of an associated PDSCH that may carry the paging message; a WTRU group index, or a WTRU group ID, that may be associated with the paging message; and the type of information carried in the paging message.
[0145] In other examples, one or more monitoring indicators may be used, and each monitoring indicator may be used to indicate a WTRU group, a WTRU group index, or a WTRU group ID. A WTRU that may be associated with a WTRU group, a WTRU group index, or a WTRU group ID may need to monitor or receive a paging message, for example, when the monitoring indicator for the WTRU group, the WTRU group index, or the WTRU group ID indicates to monitor or read the paging message. A hierarchical WTRU group index may be used, and a first WTRU group index may include a set of WTRUs or WTRU-IDs, and a second WTRU group index may include a subset of WTRUs or WTRU-IDs in the set of WTRUs or WTRU-IDs indicated from the first WTRU group index. The first WTRU group index may be determined based on a WTRU-ID, e.g., an IMSI, and the second WTRU group index may be determined based on a different WTRU-ID, e.g., an s-TMSI. The first WTRU group index may be determined based on a modulo operation based on the WTRU-ID and the number of WTRU groups for the first WTRU group index, and the second WTRU group index may be determined based on a hash function of the WTRU-ID and the number of WTRU groups for the second WTRU group index.
[0146] A combination of the first and second monitoring indicators may be used to determine the WTRU group index. If N1 WTRU groups are used for the first monitoring indicator and N2 WTRU groups for the second monitoring indicator, the combined WTRU groups may be denoted as N1×N2 WTRU groups.
[0147] Examples using multiple monitoring indicators for paging with explicit and implicit indications are discussed herein. In examples, one or more monitoring indicators can be used, where a first monitoring indicator can be based on one or more explicit bits, while a second monitoring indicator can be based on an RNTI. For example, a WTRU can receive or receive an indication from a PO monitoring indicator in a first channel, and a WTRU can receive or receive an indication from a PM monitoring indicator in a second channel.
[0148] In an example, the first channel can be a broadcast channel and the second channel can be a physical downlink control channel, e.g., M-PDCCH. In another example, the first channel can be an M-PDCCH monitored in a cell-specific time / frequency resource, e.g., a common search space, and the second channel can be an M-PDCCH monitored in a WTRU-specific or WTRU group-specific time / frequency resource, e.g., a WTRU-specific or WTRU group-specific search space. In another example, the PO monitoring indicator can be one or more bits transmitted in the broadcast channel. And, the PM monitoring indicator can be a set of RNTIs reserved for PM monitoring indications.
[0149] Exemplary methods for a WTRU to make a paging NB determination are discussed herein. The WTRU may determine a NB to use for paging in its PO based on, for example, at least one of its WTRU ID, the number of paging NBs, and DL system bandwidth. The WTRU ID may be an IMSI or s-TMSI. For example, an option is to use the IMSI modulo 1024 to determine the NB, since the IMSI modulo 1024 may be used to determine the PO of the WTRU. The number of paging NBs may be broadcast, may be received through broadcast signaling, and / or may be received through system information. The paging NB may be a NB that may be used for paging. In an example, the NB may be or represent a set of RBs or subcarriers in the system BW.
[0150] Parameters used for paging may include DRX cycle, nB, etc. However, depending on the parameters that may be used for paging and the number of NBs, using the IMSI modulo 1024 to determine the NB may result in some or all WTRUs in a given PO determining the same NB, which may defeat the purpose of having multiple NBs for paging.
[0151] Several example solutions for the WTRU to better determine the NB for paging are discussed herein. In the example solutions, IMSI-10 may be used to represent the IMSI modulo 1024, or the least significant 10 bits of the IMSI. For MME-initiated paging of the WTRU, the MME may include the IMSI-10 and / or s-TMSI for the WTRU in an S1 paging message to the eNodeB to request the page. When paging the WTRU, the eNodeB may know the IMSI-10 and / or s-TMSI of the WTRU. The WTRU and / or eNodeB may use one or both of these values to determine the WTRU's NB for paging. For example, the WTRU and / or eNodeB may use one or both of these values to determine the WTRU's NB for paging within the WTRU's PO.
[0152] To determine the NB for paging, a function such as a hash function may be used by the WTRU and / or eNodeB that may be based at least on the WTRU ID. For example, the function may be based at least on the IMSI-10 or the IMSI modulo X. In an example, the hash function may be based at least on the IMSI-10 or the IMSI modulo X.
[0153] For example, a function such as a hash function is b and / or based on the WTRU ID. b can be the number of NB. b may be the number of NBs to be used for paging or that can be used for paging, e.g., NB for the WTRU, NB WTRU may be determined, for example, by the WTRU and / or the eNodeB according to: N.B. WTRU =(A N WTRUID ) mod N b Formula (1) where A is a prime number, e.g. A=39827. In another example, NB WTRU can be determined according to: N.B. WTRU =((A N WTRUID ) mod D) mod N b Formula (2) where D is a prime number that may be different from A, for example D=65537.
[0154] A and / or D are N b A and / or D may be fixed and / or configurable by the eNodeB, for example through signaling. WTRUID may be a portion or function of the WTRU ID, or the IMSI or s-TMSI of the WTRU. WTRUID may be IMSI-10, IMSI modulo X, where X may be a number less than or equal to 1024, or IMSI modulo Y, where Y may be a number less than or equal to 16,384. The number of NBs for paging may be provided by the eNodeB and / or received by the WTRU by signaling, such as higher layer signaling, which may be broadcast in system information.
[0155] Additional IMSI bits or additional parts or functions of the IMSI may be used by the WTRU and / or the eNodeB to determine the NB for paging. The MME may include additional bits in an S1 paging message to the eNodeB. The eNodeB may receive the additional bits and use them to determine the NB for paging the WTRU.
[0156] For example, to determine the NB for paging, the most significant B bits of the IMSI modulo Z may be used, where Z may be at least one of (2^B) x 1024, (2^C) x 1024, and a number less than or equal to 16,384. In the example, C may be a number or integer that may be different from B. The B MSBs, e.g., the value of the B MSBs, MB, may be, e.g., MB modulo N b can be used to determine NB according to
[0157] In the example, if there are up to 16 narrowbands for paging, then B can be 4. To determine the NB for paging, the four MSBs of the IMSI modulo 16,384 can be used, where IMSI modulo 16,384 can be derived from IMSI modulo Z and Z=(2^B)×1024. Since B can be 4, then (2^4)×1024=16×1024=16,384. Furthermore, since B can be 4, the four MSBs, M4, can be, for example, M4 modulo N b M4 may be used to represent the 4 MSBs, or the value of the 4 MSBs.
[0158] In another example, B can be 3 and C can be 4. To determine the NB for paging, the three MSBs of the IMSI modulo 16,384 can be used, where IMSI modulo 16,384 can be derived from IMSI modulo Z and Z=(2^C)×1024. C can be 4, so (2^4)×1024=16×1024=16,384. Furthermore, B can be 3, so the three MSBs, M3, can be, for example, M3 modulo N. b M3 may be used to represent the 3 MSBs, or the value of the 3 MSBs.
[0159] In other examples, different numbers of narrow bands can be used for paging and can still be consistent with the examples discussed herein. Further, in other examples, different values can be used for B, for C, or for both.
[0160] The 14-bit IMSI-14, which can correspond to the IMSI modulo 16,384, can be used, for example, as the IMSI-14 modulo N b to determine NB. Further, the 14-bit IMSI-14, which can correspond to the IMSI modulo 16,384, can be used, for example, as the IMSI-14 modulo N b modified by one or more other parameters to determine NB.
[0161] FIG. 6 is a diagram of an example flowchart illustrating a WTRU using a WTRU-ID to determine a paging NB to use to monitor the M-PDCCH. As shown in flowchart 600, at 610, the WTRU may determine a paging NB for the WTRU to use to monitor the M-PDCCH based on at least the MSB of a function of the WTRU-ID. At 620, the WTRU may monitor for the M-PDCCH on the determined paging NB for the WTRU. For example, the WTRU may monitor for the M-PDCCH on the determined paging NB within or during a PO, which may be the WTRU's PO. The WTRU may monitor for the M-PDCCH masked with the P-RNTI, or for the M-PDCCH or DCI with a CRC scrambled with the P-RNTI. The WTRU may then receive DCI on the monitored M-PDCCH on the determined paging NB during a PO, which may be the WTRU's PO, at 630. The DCI may include a CRC, which may be scrambled with the P-RNTI. At 650, the WTRU may receive a physical downlink shared channel (PDSCH) associated with the M-PDCCH or DCI, e.g., a PDSCH scheduled by the M-PDCCH or DCI. The WTRU may receive system information update related information and / or paging messages in or from the DCI or PDSCH.
[0162] In another example, the most significant N bits of the IMSI-10 may be used to determine the NB for paging, where N may be a function of the number of NBs configured or available within the PO for paging, for example.
[0163] In the embodiments and examples described herein, the term Mobile Subscriber Identity Number (MSIN) may be substituted for IMSI and vice versa and still be consistent with the embodiments and examples disclosed herein. Additionally, various example numbers of digits may be used for the MSIN and IMSI, including but not limited to 8, 10, 14, 16, 32, 64, etc.
[0164] An example of a WTRU determining a paging HF is discussed herein. Within a PH, WTRUs with the same IMSI modulo 1024 may determine the same PF and the same PO. Depending on the paging parameters, the WTRUs may not be well distributed among the PFs and POs.
[0165] The IMSI may be composed of decimal digits (0 to 9) and may include one or more of a Mobile Country Code (MCC), a Mobile Network Code (MNC), and an MSIN. The IMSI may use a binary-coded decimal (BCD) representation. The IMSI may comprise 64 bits, and each digit may be coded across four separate bits. Digits 0 to 9 may be encoded from 0000 to 1001, and there may be two digits per octet. For the function IMSI modulo X, the IMSI may be a decimal representation of the IMSI, a BCD representation of the IMSI, a hexadecimal representation of the IMSI, or other representation of the IMSI.
[0166] One or more of the examples described herein, e.g., for paging NB determination for and / or by the WTRU, may be applied to one or more of PH, PF, and PO determination for and / or by the WTRU, e.g., for each of the PH and PF determinations for and / or by the WTRU, a separate, different function, aspect, or portion of the WTRU-ID, e.g., IMSI or s-TMSI, may be used.
[0167] WTRU_ID PH may represent a function, aspect, or portion of the WTRU-ID that may be used in the PH calculation. PF may represent a function, aspect, or portion of the WTRU-ID that may be used in the PF calculation. PH -10 is WTRU_ID PH May represent modulo 1024. WTRU_ID PF -10 is WTRU_IDPF may represent a modulo of 1024. For MME initiated paging of a WTRU, the MME may include the WTRU_ID in an S1 paging message to the eNodeB to request the page. PH -10 and / or WTRU_ID PF Can include -10.
[0168] WTRU_ID PH -10 and / or WTRU_ID PF -10 may be provided by the MME to the eNodeB. WTRU_ID PH -10 and / or WTRU_ID PF -10 may be provided by the MME to the eNodeB as a bit string of size 10. The bits may follow standard binary representation, or BCD representation.
[0169] When paging a WTRU, the eNodeB uses the WTRU_ID PH -10 and / or WTRU_ID PF −10. The WTRU and / or eNodeB may use one or both of these values to determine the PH and / or PF of the WTRU. PH -10 to determine the PH of the WTRU for paging. The WTRU and / or eNodeB may use the WTRU_ID PF -10 may be used to determine the PF of the WTRU for paging.
[0170] In this example, WTRU_ID PH may be the MSIN of the WTRU. The MSIN may be N1, e.g., the 9 least significant decimal digits of the IMSI in decimal representation, e.g., if the concatenation of MCC and MNC is 6 digits. The MSIN may be N2, e.g., the 10 least significant decimal digits of the IMSI, e.g., if the IMSI is 15 digits. WTRU_ID PF may be the IMSI of the WTRU. PH-10 can be the MSIN modulo 1024 and / or the WTRU_ID PF -10 can be the IMSI modulo 1024.
[0171] In other examples, the WTRU_ID PH can be the IMSI, and the WTRU_ID PF can be the MSIN. In other examples, if the concatenation of the MCC and MNC parts of the IMSI is even, the IMSI can be transformed such that the concatenation of the MCC and MNC parts of the IMSI is odd. For example, 1 can be added to or subtracted from the concatenation of the MCC and MNC parts of the IMSI.
[0172] In other examples, MSIN - 10Q can be used to represent FLOOR[MSIN / 1024] or (FLOOR[MSIN / 1024]) modulo 1024. The WTRU_ID PH -10 can be the MSIN - 10Q.
[0173] Examples of modified paging reception are disclosed herein. In an example, the WTRU can determine PH, PF, and PO according to a set of rules, such as normal rules. The WTRU can receive and / or use additional configuration or information to determine when to monitor or skip monitoring for paging, for example, when to monitor or skip monitoring for an M - PDCCH masked with a paging RNTI, and / or when to receive or skip receiving an associated PDSCH or PCH.
[0174] At least some of the configurations and / or information may be provided by or received from the MME through NAS signaling or through the eNodeB through RRC signaling. The WTRU may maintain the configurations and / or information while in idle mode. The WTRU may monitor for paging within the PF of its PW within one PH per I-eDRX cycle. In an example, the WTRU may be configured to skip its PH in one or more I-eDRX cycles and / or skip one or more PFs within its PW.
[0175] In an example, whether the WTRU ID is odd or even may be used to determine whether the WTRU may read or receive, or skip reading or receiving, a page in the PF and / or PH. Reading and / or receiving a page may correspond to monitoring for an M-PDCCH by a paging RNTI. Reading and / or receiving a page may correspond to receiving, decoding, and / or reading a PDSCH that may be associated with, indicated by, or allocated by an M-PDCCH by a paging RNTI. Reading and / or receiving a page may correspond to receiving, decoding, and / or reading a PDSCH that may carry a paging message. Skipping reading or receiving a page may be the same as not reading or receiving, or not attempting to read or receive, a page. Skipping reading or receiving a page may be the same as skipping one or more of the PO, PF, or PH.
[0176] A WTRU may, for example, read or monitor a page in a PO if the WTRU ID is odd, and may, for example, skip reading or monitoring a page in a PO if the WTRU ID is even, e.g., a read and / or monitoring by a WTRU with an odd WTRU ID is indicated. A WTRU may, for example, read or monitor a page in a PO if the WTRU ID is even, and may, for example, skip reading or monitoring a page in a PO if the WTRU ID is odd, e.g., a read and / or monitoring by a WTRU with an even WTRU ID is indicated.
[0177] WTRU_ID PH -10 and / or WTRU_ID PF The -10 may be replaced with the WTRU ID and still be consistent with this disclosure. The WTRU ID may be the IMSI modulo 1024, the MSIN modulo 1024, and / or the FLOOR[MSIN / 1024], among others.
[0178] Whether an odd-numbered WTRU or an even-numbered WTRU may receive a page within a PF or a PO may be determined based on one or more of a WTRU ID odd / even indicator, a PH odd / even indicator, and / or a PF odd / even indicator.
[0179] One bit may be used for the indicator. One state of the bit may be used to indicate an even number and the other state may be used to indicate an odd number. 0 may be used for even numbers and 1 for odd numbers or vice versa. One or more of the indicators may be signaled, for example by the eNodeB, for example in the MIB for paging, in the SIB, or in the M-PDCCH.
[0180] The WTRU may read one or more of the indicators prior to at least one of its PH and / or PF and / or PO. The WTRU may read one or more of the indicators in the M-PDCCH for paging in one of its POs. The WTRU may determine a state of one or more of the indicators, and based on the state, the WTRU may determine whether to monitor for a page and / or receive a PDSCH that may carry a page. An indicator in the MIB may be used by the WTRU to determine whether to monitor for a paging M-PDCCH in one or more POs. An indicator in the M-PDCCH for paging may be used by the WTRU to determine whether to read a PDSCH associated with an M-PDCCH that may carry a paging message.
[0181] For example, for WTRU ID odd / even=even and PH odd / even=odd, a WTRU with an even WTRU ID may read or monitor pages in, e.g., only, odd-numbered PHs. The WTRU may skip reading or monitoring pages in even-numbered PHs. A WTRU with an odd WTRU ID may skip reading or monitoring pages when, e.g., WTRU odd / even is set to even in one or more, e.g., both odd and even, PHs.
[0182] In an example, (0,0) may mean that the WTRU ID is even and the PH is even, (1,0) may mean that the WTRU ID is odd and the PH is even, (0,1) may mean that the WTRU ID is even and the PH is odd, and (1,1) may mean that the WTRU ID and the PH is odd. The eNodeB may use one of these codes as a paging read indicator, for example, at any point in time.
[0183] In other examples, a single bit may be used for odd / even WTRU ID. A WTRU with an even WTRU ID may read or monitor for a page when the WTRU odd / even is set to even, and may skip reading or monitoring for a page when the WTRU odd / even is set to odd. A WTRU with an odd WTRU ID may read or monitor for a page when the WTRU odd / even is set to odd, and may skip reading or monitoring for a page when the WTRU odd / even is set to even.
[0184] The eNodeB may signal some or all of the bits of the current value of the paging read indicator in the MIB, or in the SIB, or in the M-PDCCH (or PDCCH). The WTRU may make a decision to skip PH based on the value of the paging indicator signaled by the eNodeB. The WTRU may make a decision to skip PF based on the value of the paging read indicator.
[0185] The eNodeB may use a paging read indicator to indicate to one or more WTRUs to skip or read a page in a PH and / or a PF. The eNodeB may use separate paging read indicators to indicate to skip or read a page in a PF and to skip or read pages in all PFs within a PH.
[0186] The odd / even indication may be replaced by a Group ID, which may represent another means for distinguishing groups. More bits may be used as appropriate. For example, there may be four groups, and the least significant two bits of the WTRU ID may be used to determine which WTRUs can read or monitor for the page.
[0187] Within a PO, multiple paging messages targeted to multiple WTRUs can be multiplexed into a transport block and jointly coded by a channel encoder, and the WTRUs may have different coverage levels, thus requiring iterations to target the worst coverage case, which may result in resource waste for paging transmissions.
[0188] In an example, multiple paging messages may be individually encoded as code block segments within a PDSCH transmission. For example, a PDSCH, e.g., a NB-PDSCH carrying one or more paging messages, may be scheduled by an associated PDCCH, e.g., the NB-PDCCH, within each PO. The paging messages multiplexed within the PDSCH may be divided into one or more code block segments.
[0189] Each code block segment may be individually coded by a channel code, e.g., a turbo code, a convolutional code, or a block code. A CRC may be appended to each code block segment. A code block segment may be associated with one or more paging messages. A code block segment may be associated with one or more coverage levels. A code block segment may be associated with a WTRU-ID. The WTRU-IDs used for the PO determination and the code block segment determination may be different. For example, the PO may be determined based on a first WTRU-ID, e.g., IMSI-10, while the code block segment may be determined based on a second WTRU-ID, e.g., s-TMSI.
[0190] 7 is a diagram illustrating an example of code block segment multiplexing in a PDSCH that may be scheduled by an associated PDCCH in a PO. Paging message, paging information, and paging record may be used synonymously. As shown in diagram 700, code block segments 710, 720, and 780 may each be associated with one or more respective coverage levels or CE levels. For example, code block segment 710 may be associated with CE level 1, code block segment 720 may be associated with CE level 2, and code block segment 780 may be associated with CE level 3.
[0191] A PDSCH carrying one or more paging messages may be transmitted over multiple subframes. The number of subframes used for PDSCH transmission may be indicated from the associated PDCCH. The number of subframes for PDSCH transmission may be determined based on a transport block size, which may include all code block segments multiplexed in the PDSCH. The number of repetitions may be indicated from the associated PDCCH. For example, the number of subframes Ns for PDSCH transmission may be determined as a function of the transport block size, and the number of repetitions Nrep may be indicated from the associated PDCCH. The total number of subframes used for PDSCH transmission including repetitions may be Ns × Nrep.
[0192] The NB subframe may include one or more subframes, and the NB subframe length may be determined based on the transport block size of the PDSCH transmission.
[0193] A code block segment may be transmitted within an NB subframe, and an NB subframe length, e.g., as a number of subframes, TTI, ms, etc., may be determined based on a size of the code block segment. Multiple code block segments may be multiplexed within a PDSCH. In the example shown in FIG. 7, code block segments 710, 720, and 780 may be multiplexed within a PDSCH 790. If Nc code block segments are multiplexed within a PDSCH in the example, the PDSCH may be transmitted across Nc NB subframes. An NB subframe length associated with a code block segment may be determined based on the code block segment size. The size of the code block segment may be indicated in an associated PDCCH. Based on the code block segment size, the WTRU may determine an NB subframe length for each code block segment.
[0194] One or more code block segments may be multiplexed in the PDSCH, and the time / frequency resource location for each code block segment may be predefined. The WTRU may monitor all code block segments in the PDSCH, or the WTRU may monitor a subset of the code block segments. Each code block segment may be associated with a CE level, and a WTRU with a certain CE level may monitor, attempt to decode, or receive the code block segment associated with the CE level. Each code block segment may be associated with a WTRU-ID or a WTRU group ID, and the WTRU may monitor, attempt to decode, or receive the code block segment associated with the WTRU-ID or WTRU group ID.
[0195] In an example, multiple paging messages can be individually coded as code block segments, and each code block segment can be transmitted in a PDSCH. For example, if Nc code block segments are transmitted, Nc PDSCHs can be transmitted, and the Nc PDSCHs can be scheduled in an associated PDCCH in a PO. Each PDSCH carrying a code block segment can be transmitted in one or more subframes. A starting subframe of each PDSCH carrying a code block segment can be determined based on the last subframe of the associated PDCCH. Alternatively, a starting subframe of each PDSCH carrying a code block segment can be determined based on the last subframe of the associated PDCCH and the size of the code block segment. The number of subframes for the PDSCH carrying the code block segment can be determined based on the size of the code block segment. The size of the code block segment can be the number of bits for the code block segment after encoding and rate matching.
[0196] 8 is a diagram illustrating an example of code block segments transmitted over multiple PDSCHs that may be scheduled by associated PDCCHs in a PO. The associated PDCCHs transmitted in a PO may schedule one or more PDSCHs carrying paging messages. The PDSCHs may be associated with the code block segments.
[0197] As shown in diagram 800, similar to that of Figure 7, code block segments 810, 820, and 860 may each be associated with one or more respective coverage levels or CE levels. For example, code block segment 810 may be associated with CE level 1, code block segment 820 may be associated with CE level 2, and code block segment 860 may be associated with CE level 3. However, in Figure 8, each different respective PDSCH may be associated with each different respective code block segment. For example, code block segment 810 may be associated with PDSCH 870, code block segment 820 may be associated with PDSCH 880, and code block segment 860 may be associated with PDSCH 890.
[0198] The PDSCHs may be multiplexed in the time domain. For example, the PDSCHs may be transmitted at different times (e.g., different time windows). The starting subframe of the PDSCH may be predetermined based on the last subframe of the associated PDCCH.
[0199] In other examples, a PDSCH carrying a code block segment may be transmitted without an associated PDCCH. One or more time windows may be configured, used, or allocated within each PO, and the WTRU may attempt to decode, monitor, or receive a PDSCH carrying a code block segment within the time window. The code block segment size for the PDSCH may be predefined. One or more code block segment sizes may be used, and the WTRU may attempt to decode all candidate code block segment sizes. The time windows for the PDSCH may be non-overlapping. Each time window may be associated with a CE level or a WRTU-ID.
[0200] In another example, one or more PDSCHs carrying code block segments may be transmitted, where a first PDSCH may be scheduled by an associated PDCCH, and a subsequent PDSCH may be scheduled based on a previous PDSCH. An indication may be transmitted within the PDSCH to indicate whether a subsequent PDSCH carrying a code block segment may follow or be transmitted. The indication may be based on a sequence masked in the CRC. For example, if the CRC is masked with a first sequence, there may be no subsequent PDSCH, but if the CRC is masked with a second sequence, there may be a subsequent PDSCH. The indication may be a bit transmitted within the code block segment. Scheduling information may be transmitted with the indication. The first PDSCH may be based on the highest CE level, e.g., the largest number of repetitions, and the subsequent PDSCHs may be based on a lower CE level. The terms code block segment and paging message may be used synonymously herein.
[0201] The following examples include sending an indication directly in the paging DCI without PDSCH scheduling. When the eNodeB updates or changes the frequency location of an anchor RB, e.g., an anchor PRB, which may include synchronization signals and / or broadcast signals such as the NB Master Information Block (NB-MIB) and / or NB-SIB, the eNodeB may need to indicate the update or change through paging to WTRUs in RRC idle mode. If the indication bit is sent in the paging message, the eNodeB may need to send this signal in every PO, and thus the resource overhead may be significantly increased.
[0202] In an example, the WTRU can monitor or attempt to decode a DCI located within an NB-PDCCH search space. The NB-PDCCH can be within a PO. The NB-PDCCH and / or the PO can be targeted to the WTRU. The DCI can carry one or more information types. The terms information type and DCI content can be used synonymously herein. One or more of the following exemplary parameters can apply.
[0203] The first information type can be scheduling information for an associated PDSCH carrying a paging message. The second information type can be a direct indication related to the system configuration. The second information type may not include scheduling information for an associated PDSCH.
[0204] An information type related to the system configuration can include at least one of the following parameters or indications: a system information update indication; a public warning indication such as an ETWS or CMAS indication; an access prohibition parameter such as an EAB parameter change indication; scheduling information for one or more SIBs, where one or more SIBs can be transmitted without an associated DL control channel (NB-PDCCH); configuration information related to an anchor RB, such as an anchor PRB for NB-IoT; an identical physical cell ID (PCI) indicator that can indicate whether the PCI for a cell-specific reference signal (CRS) port is the same as the PCI for an NB reference signal (NB-RS); and a value tag that can include one or more bits to indicate which SIBs are updated.
[0205] The scheduling information of the SIB may include at least one of the following parameters: transport block size (TBS), frequency location, frequency hopping related information, and coverage level, which may be, for example, a repetition number. The anchor RB, e.g., anchor PRB, as described herein may include or include the transmission of at least one of the following: synchronization signals (e.g., NB Primary Synchronization Signal (NB-PSS), NB Secondary Synchronization Signal NB-SSS, etc.), broadcast signals (e.g., NB Physical Broadcast Channel (NB-PBCH), NB-SIB, etc.), and NB-PDCCH common search space. The configuration information for the anchor RB, e.g., anchor PRB, may include at least one of the following parameters: RB location, e.g., PRB location, raster offset, and PCI of NB-Sync within the system bandwidth.
[0206] In an example, the information type for the DCI may be determined based on a flag field in the DCI. For example, the flag field may indicate the information type being carried. In another example, the information type for the DCI may be determined based on an RNTI used for the DCI. If the DCI carries scheduling information for a corresponding PDSCH, a first RNTI (e.g., P-RNTI-1) may be used. If the DCI carries direct information, such as one or more indications related to a system configuration, a second RNTI (e.g., P-RNTI-2) may be used. In another example, the information type for the DCI may be determined based on a scrambling sequence used for the DCI, or a starting ECCE index used.
[0207] The eNodeB may page one or more WTRUs to indicate or provide a broadcast or multicast transmission. The eNodeB may or may need to page all WTRUs in a group of WTRUs or a cell, e.g., for a downlink burst transmission to all WTRUs in a group of WTRUs or a cell, e.g., for or to perform a software update of one or more NB-IoT devices. The eNodeB may need to page all WTRUs in a group of WTRUs or a cell, e.g., when the WTRUs are in RRC idle. The eNodeB may need to transmit a downlink burst to each WTRU over WTRU-dedicated resources. This may result in inefficient resource utilization and WTRU battery consumption. Downlink burst transmission may be used herein as a non-limiting example of a broadcast or multicast transmission.
[0208] In an example, a common PO may be used for downlink burst transmission. For example, a DCI scrambled with a certain RNTI, e.g., a downlink burst RNTI (DB-RNTI), may be monitored by the WTRU in a PDCCH search space within the common PO. The DCI may schedule a PDSCH carrying downlink burst traffic.
[0209] The WTRU may monitor or attempt to decode the DCI within a PDCCH search space. The PDCCH search space may be located within certain time / frequency resources configured or used for the common PO. The time / frequency resources for the common PO may be determined based on at least one of the following parameters: system parameters, such as system bandwidth, physical cell ID, duplex mode, TDD subframe configuration, etc.; subframe number and / or radio frame number, such as SFN; WTRU-ID, such as full or partial information, such as IMSI, s-TMSI, etc.; operation mode, such as in-band, guard band, and standalone operation; one or more coverage levels, which may be represented, for example, by a repetition number; WTRU category and / or WTRU capability; and paging NB, which may be configured or determined.
[0210] The DCI may activate and / or deactivate a PDSCH transmission for a downlink burst transmission. The PDSCH may be transmitted within predefined time / frequency resources. The predefined time / frequency resources may be transmitted with a duty cycle.
[0211] In an example, the scheduling information of the downlink burst may be transmitted in a broadcast channel or in system information, e.g., in a MIB or SIB. The WTRU may receive an indication or may be indicated, triggered, or informed to read the broadcast channel or system information. The indication may be signaled in a paging message or as a direct indication in the DCI for paging. The scheduling information of the downlink burst may be transmitted in a broadcast channel or in system information. If the WTRU receives a system information update indication, the WTRU may attempt to receive or decode the broadcast channel or system information.
[0212] In an example, for downlink burst transmission, an ordered PDSCH transmission may be used. For example, downlink burst traffic may be divided into N_burst transport blocks, numbered in increasing order. Each transport block may be transmitted within a PDSCH transmission. Scheduling information for the downlink burst transmission may indicate the number of transport blocks, e.g., represented by N_burst, for the downlink burst transmission. Scheduling information for a PDSCH carrying one or more downlink burst transport blocks may indicate an ordering number for the PDSCH.
[0213] Each transport block may be transmitted within a certain time and / or frequency resource. A transport block with a certain transport block number may be associated with a certain subframe number, a certain SFN, and / or a certain hyperframe number. Thus, the WTRU may determine, assume, or understand which transport blocks may be transmitted within a certain time / frequency resource for a burst transmission. If the WTRU fails to receive a subset of the transport blocks of the N_burst transport blocks, the WTRU may receive the failed transport blocks within the next downlink burst transmission. A transport block with a certain transport block number may be associated with a certain frequency resource. The certain time / frequency resource may be configured through higher layer signaling.
[0214] Each PDSCH carrying a transport block may be transmitted with repetition, and the number of repetitions may be indicated in the scheduling information. The number of repetitions may include a value of "1" for no repetition.
[0215] In an example, a WTRU that fails to receive one or more PDSCH transmissions for a downlink burst transmission may take one or more of the following actions: The WTRU may attempt to receive the failed PDSCH transmission in the next subsequent transmission or in the next subsequent transmission window. The maximum number of attempts may be predefined or configured by higher layers. The maximum number of attempts may include a value of "1".
[0216] If the WTRU fails to receive one or more PDSCH transmissions after a maximum number of attempts, the WTRU may attempt to change the operating mode, e.g., from RRC idle mode to RRC connected mode, and / or the WTRU may initiate a random access or random access channel (RACH) procedure.
[0217] In another example, a WTRU that fails to receive one or more PDSCH transmissions for a downlink burst transmission may take one or more of the following actions: The WTRU may send a corresponding Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) transmission in the associated HARQ-ACK resource. The HARQ transmission for the failed reception may be a Negative Acknowledgement (NACK). A subset of Physical Random Access Channel (PRACH) resources may be reserved as the associated HARQ-ACK resource for the downlink burst transmission. For example, the WTRU may send a HARQ transmission, which may be a NACK, on the PRACH resource upon failing to receive one or more PDSCH transmissions for the downlink burst transmission. A set of Physical Uplink Control Channel (PUCCH) resources may be configured, indicated, or used for the HARQ transmission, e.g., for a NACK transmission. For example, the WTRU may send a HARQ transmission, which may be a NACK, on a PUCCH resource, which may be configured or indicated, upon failing to receive one or more PDSCH transmissions for the downlink burst transmission.
[0218] Although the features and elements have been described above in certain combinations, one skilled in the art will understand that each feature or element may be used alone or in any combination with the other features and elements. Furthermore, the methods described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections), and computer-readable storage media. Examples of computer-readable storage 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 may be used in conjunction with software to execute a radio frequency transceiver for use in a WTRU, UE, terminal device, base station, RNC, or any host computer. [Industrial Applicability]
[0219] The present invention can be generally applied to wireless communication systems. [Explanation of symbols]
[0220] 100 Communication Systems 102, 102a~102d 104 RAN 106 Core Network 108 PSTN 110 Internet 112 Other Networks 114a, 114b base station 118 processors 120 Transmitter / Receiver 122 Antenna 140a~140c Node B 160 WLAN
Claims
1. 1. A method for use in a wireless transmit / receive unit (WTRU), comprising: receiving paging occasion (PO) monitoring indication information in a first downlink control information (first DCI); determining a first paging occasion (first PO), the first PO being based on a WTRU identifier (WTRU-ID) for the WTRU; monitoring a second DCI in the first PO based on the PO monitoring indication information; receiving the second DCI in the first PO; receiving a physical downlink shared channel transmission (PDSCH transmission) based on the second DCI; A method for providing the above.
2. The method of claim 1 , wherein the PDSCH transmission comprises a paging message.
3. The method of claim 1 , wherein the first PO is in a paging frame (PF) and the PO monitoring indication information is received prior to the first PO.
4. not monitoring a second PO prior to the first PO based on the PO monitoring indication information; The method of claim 1 further comprising:
5. The method of claim 4 , wherein the PO monitoring indication information includes a WTRU group index for a WTRU group the WTRU is part of, and the PO monitoring is further based on the WTRU group index.
6. The method of claim 5, wherein the WTRU group is one of a plurality of WTRU groups, and the WTRU group index is based on the WTRU-ID and the plurality of WTRU groups.
7. 2. The method of claim 1, wherein the first DCI is scrambled with a WTRU group-specific Radio Network Temporary Identifier (RNTI) and the second DCI is scrambled with a Paging RNTI (P-RNTI).
8. monitoring for the first DCI in a first search space, the first search space being a common search space; monitoring for the second DCI in a second search space within the first PO; The method of claim 1 further comprising:
9. The method of claim 1, wherein the WTRU-ID is a RNTI assigned to the WTRU.
10. The method of claim 9, wherein the RNTI assigned to the WTRU is a P-RNTI.
11. 1. A wireless transmit / receive unit (WTRU), comprising: A transceiver; a processor operably coupled to the transceiver. The transceiver is configured to receive paging occasion (PO) monitoring indication information in a first downlink control information (first DCI); The processor is configured to determine a first paging occasion (first PO), the first PO being based on a WTRU identifier (WTRU-ID) for the WTRU; the processor and the transceiver are configured to monitor for a second DCI in the first PO based on the PO monitoring indication information; the transceiver is configured to receive the second DCI in the first PO; The transceiver is configured to receive a physical downlink shared channel transmission (PDSCH transmission) based on the second DCI. WTR U.
12. The WTRU of claim 11 , wherein the PDSCH transmission includes a paging message.
13. The WTRU of claim 11 , wherein the first PO is in a paging frame (PF) and the PO monitoring indication information is received prior to the first PO.
14. The processor and the transceiver are further configured to not monitor a second PO prior to the first PO based on the PO monitoring indication information. The WTRU of claim 11.
15. The WTRU of claim 14, wherein the PO monitoring indication information includes a WTRU group index for a WTRU group for which the WTRU is part, and the PO monitoring is further based on the WTRU group index.
16. The WTRU of claim 15, wherein the WTRU group is one of a plurality of WTRU groups, and the WTRU group index is based on the WTRU-ID and the plurality of WTRU groups.
17. The WTRU of claim 11, wherein the first DCI is scrambled with a WTRU group-specific Radio Network Temporary Identifier (RNTI) and the second DCI is scrambled with a Paging RNTI (P-RNTI).
18. the processor and the transceiver are further configured to monitor for the first DCI in a first search space, the first search space being a common search space; The processor and the transceiver are further configured to monitor for the second DCI in a second search space within the first PO. The WTRU of claim 11.
19. The WTRU of claim 11, wherein the WTRU-ID is a RNTI assigned to the WTRU.
20. The WTRU of claim 19, wherein the RNTI assigned to the WTRU is a P-RNTI.
21. 1. A method for use in a base station, comprising: transmitting paging occasion (PO) monitoring indication information in a first downlink control information (first DCI) to a wireless transmit / receive unit (WTRU); transmitting a second DCI to the WTRU in a paging occasion (PO) associated with a WTRU identifier (WTRU-ID) for the WTRU; transmitting a physical downlink shared channel transmission (PDSCH transmission) associated with the second DCI; A method for providing the above.
22. 22. The method of claim 21, wherein the PDSCH transmission comprises a paging message.
23. 22. The method of claim 21, wherein the PO is in a paging frame (PF), and the PO monitoring indication information is transmitted prior to the PO.
24. 22. The method of claim 21, wherein the first DCI is scrambled with a WTRU group-specific Radio Network Temporary Identifier (RNTI) and the second DCI is scrambled with a Paging RNTI (P-RNTI).
25. The method of claim 21, wherein the WTRU-ID is a RNTI assigned to the WTRU.
26. The method of claim 25, wherein the RNTI assigned to the WTRU is a P-RNTI.
27. A base station, A transceiver; a processor operably coupled to the transceiver. The transceiver and the processor are configured to transmit paging occasion (PO) monitoring indication information in a first downlink control information (first DCI) to a wireless transmit / receive unit (WTRU); The transceiver and the processor are configured to transmit a second DCI to the WTRU in a paging occasion (PO) associated with a WTRU identifier (WTRU-ID) for the WTRU; The transceiver and the processor are configured to transmit a physical downlink shared channel transmission (PDSCH transmission) associated with the second DCI. Base station.
28. 30. The base station of claim 27, wherein the PDSCH transmission includes a paging message.
29. 28. The base station of claim 27, wherein the PO is in a paging frame (PF), and the PO monitoring indication information is transmitted prior to the PO.
30. 28. The base station of claim 27, wherein the first DCI is scrambled with a WTRU group specific Radio Network Temporary Identifier (RNTI) and the second DCI is scrambled with a Paging RNTI (P-RNTI).
31. The base station of claim 27, wherein the WTRU-ID is an RNTI assigned to the WTRU.
32. The base station of claim 31, wherein the RNTI assigned to the WTRU is a P-RNTI.
Citation Information
Patent Citations
Group procedures for machine type communication devices
JP2015146623A
Method and apparatus for controlling connectivity to network
JP2015149754A
Method of transmitting group paging message, base station and mobile station
KR1020120124042A