Preconfigured uplink (UL) resource (PUR) start time and offset

Abstract

A method for wireless communication is presented. The method includes receiving preconfigured uplink resource (PUR) configuration information including one or more least significant bits (LSBs) of a hyper-system frame number (H-SFN). The method also includes determining a PUR starting time based on the H-SFN identified by the one or more LSBs. The method further includes transmitting data to a base station on a PUR identified in the PUR configuration information at the PUR starting time.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Patent Application No. 17 / 229,635, filed April 13, 2021, entitled “PRE-CONFIGURED UPLINK(UL) RESOURCE(PUR) START TIME AND OFFSET,” which claims the benefit of U.S. Provisional Patent Application No. 63 / 009,909, filed April 14, 2020, entitled “PRE-CONFIGURED UPLINK(UL) RESOURCE(PUR) START TIME AND OFFSET,” the disclosure of which is expressly and entirely incorporated herein by reference. Technical Field

[0003] Various aspects of this disclosure generally relate to wireless communications, and more specifically to techniques and apparatus for pre-configured uplink (UL) resource (PUR) start times and offsets. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / improved LTE is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless communication network may include multiple base stations (BSs), which can support communication for multiple user equipments (UEs). UEs can communicate with the base stations (BSs) via downlink and uplink links. A downlink link (or forward link) refers to the communication link from the BS to the UE, and an uplink link (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Headend, Transmit / Receive Point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0006] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different user equipment to communicate at the city, national, regional, and even global levels. New Radio (NR) is a collection of enhancements to the LTE mobile standard issued by the 3rd Generation Partnership Project (3GPP), and NR can also be referred to as 5G. NR is designed to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and by better integrating with other open standards such as Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (DL) link and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies, and carrier aggregation. Summary of the Invention

[0007] In one aspect of this disclosure, a method for wireless communication performed by a user equipment (UE) is disclosed. The method includes receiving PUR configuration information, the PUR configuration information including one or more least significant bits (LSBs) of a supersystem frame number (H-SFN). The method further includes determining a PUR start time based on the H-SFN identified by the one or more LSBs. The method further includes transmitting a data message to a base station on the PUR indicated in the PUR configuration information at the PUR start time.

[0008] Another aspect of this disclosure relates to an apparatus for wireless communication performed by a UE. The apparatus includes units for receiving PUR configuration information including one or more LSBs comprising an H-SFN. The apparatus also includes units for determining a PUR start time based on the H-SFN identified by the one or more LSBs. Furthermore, the apparatus includes units for transmitting data messages to a base station on the PUR indicated in the PUR configuration information at the PUR start time.

[0009] In another aspect of this disclosure, a non-transitory computer-readable medium having non-transitory program code recorded thereon for wireless communication performed by a UE is disclosed. This program code is for wireless communication. The program code is executed by a processor and includes program code for receiving PUR configuration information including one or more LSBs comprising an H-SFN. The program code also includes program code for determining a PUR start time based on the H-SFN identified by one or more LSBs. The program code further includes program code for transmitting a data message to a base station on the PUR indicated in the PUR configuration information at the PUR start time.

[0010] Another aspect of this disclosure relates to an apparatus for wireless communication at a UE. The apparatus includes a processor, a memory coupled to the processor, and instructions stored in and operable in the memory, the instructions, when executed by the processor, causing the apparatus to receive PUR configuration information including one or more LSBs comprising an H-SFN. Execution of the instructions further causes the apparatus to determine a PUR start time based on the H-SFN identified by the one or more LSBs. Execution of the instructions further causes the apparatus to transmit a data message to a base station at the PUR start time on the PUR indicated in the PUR configuration information.

[0011] In one aspect of this disclosure, a method for a UE to perform wireless communication is disclosed. The method includes determining one or more LSBs of an H-SFN, wherein the UE receives a connection release message including PUR configuration information. The method also includes sending a signal including the one or more LSBs to a base station. This signal may be included in an RLC (Radio Link Control) message, an RRC message, or a similar type of message.

[0012] Another aspect of this disclosure relates to an apparatus for wireless communication performed by a UE. The apparatus includes a unit for determining one or more LSBs of an H-SFN, wherein the UE receives a connection release message including PUR configuration information. The apparatus also includes a unit for transmitting a signal including the one or more LSBs to a base station. This signal may be included in an RLC (Radio Link Control) message, an RRC message, or a similar type of message.

[0013] In another aspect of this disclosure, a non-transitory computer-readable medium is disclosed having non-transitory program code recorded thereon for wireless communication performed by a UE. This program code is used for wireless communication. The program code is executed by a processor and includes program code for determining one or more LSBs of an H-SFN, wherein the UE receives a connection release message including PUR configuration information. The program code also includes program code for sending a signal including the one or more LSBs to a base station. This signal may be included in an RLC (Radio Link Control) message, or an RRC message, or a similar type of message.

[0014] Another aspect of this disclosure relates to an apparatus for wireless communication at a UE. The apparatus includes a processor, a memory coupled to the processor, and instructions stored in and operable in the memory, the instructions, when executed by the processor, causing the apparatus to determine one or more LSBs of an H-SFN, wherein the UE receives a connection release message including PUR configuration information. Execution of the instructions also causes the apparatus to send a signal including the one or more LSBs to a base station. This signal may be included in an RLC (Radio Link Control) message, an RRC message, or a similar type of message.

[0015] In one aspect of this disclosure, a method for wireless communication performed by a UE is disclosed. The method includes decoding a downlink (DL) transmission. The method further includes determining whether the DL transmission is a retransmission. The method further includes using the H-SFN of the DL transmission as a reference H-SFN for determining the PUR start time when the DL transmission is a retransmission. The method further includes transmitting data to a base station on the PUR at the PUR start time.

[0016] Another aspect of this disclosure relates to an apparatus for wireless communication performed by a UE. The apparatus includes a unit for decoding a DL transmission. The apparatus also includes a unit for determining whether the DL transmission is a retransmission. When the DL transmission is a retransmission, the apparatus further includes a unit for using the H-SFN of the DL transmission as a reference H-SFN for determining the PUR start time. The apparatus also includes a unit for transmitting data to a base station on the PUR at the PUR start time.

[0017] In another aspect of this disclosure, a non-transitory computer-readable medium is disclosed having non-transitory program code recorded thereon for wireless communication performed by a UE. This program code is used for wireless communication. The program code is executed by a processor and includes program code for decoding a DL transmission. The program code also includes program code for determining whether the DL transmission is a retransmission. When the DL transmission is a retransmission, the program code also includes program code for using the H-SFN of the DL transmission as a reference H-SFN for determining the PUR start time. The program code also includes program code for transmitting data to a base station on the PUR at the PUR start time.

[0018] Another aspect of this disclosure relates to an apparatus for wireless communication at a UE. The apparatus includes a processor, a memory coupled to the processor, and instructions stored in and operable in the memory, the instructions, when executed by the processor, causing the apparatus to decode a DL transmission. Execution of the instructions also causes the apparatus to determine whether the DL transmission is a retransmission. When the DL transmission is a retransmission, execution of the instructions further causes the apparatus to use the H-SFN of the DL transmission as a reference H-SFN for determining the PUR start time. Execution of the instructions further causes the apparatus to transmit data to a base station on the PUR at the PUR start time.

[0019] The features and technical advantages of examples according to this disclosure have been outlined quite extensively above to facilitate a better understanding of the specific embodiments described below. Further features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein (both their organization and manner of operation) along with their associated advantages will be better understood when considered in conjunction with the accompanying drawings, based on the description below. Each figure in the drawings is provided for illustrative and descriptive purposes and is not intended to limit the scope of the claims. Attached Figure Description

[0020] To provide a detailed understanding of the features of this disclosure, specific descriptions are made by reference to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain aspects of this disclosure, and since other equivalent aspects may be permitted in the specification, they should not be considered as limitations on the scope of protection. The same reference numerals in different drawings may identify the same or similar elements.

[0021] Figure 1 It is a block diagram that conceptually illustrates an example of a wireless communication network according to various aspects of this disclosure.

[0022] Figure 2 This is a block diagram conceptually illustrating an example of communication between a base station and a user equipment (UE) in a wireless communication network according to various aspects of this disclosure.

[0023] Figure 3 This is a schematic diagram of the PUR call process based on various aspects of this disclosure.

[0024] Figures 4-6 This is a schematic diagram illustrating an example process performed, for example, by a receiving device, according to various aspects of this disclosure. Detailed Implementation

[0025] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function given throughout this disclosure. These aspects are provided precisely so that this disclosure will be exhaustive and complete, and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover apparatus or methods practiced using other structures, functions, or structures and functions other than or different from the aspects of the set forth disclosure. It should be understood that any aspect of the disclosed disclosure may be embodied by one or more elements of the claims.

[0026] Several aspects of a telecommunications system will now be described with reference to various devices and techniques. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements may be implemented using hardware, software, or a combination thereof. Whether such an element is implemented in hardware or software depends on the specific application and design constraints imposed on the entire system.

[0027] It should be noted that while the aspects may be described using terms commonly associated with 5G and subsequent wireless technologies, the aspects of this disclosure may be applied to other generation-based communication systems, such as those including 3G and / or 4G technologies.

[0028] In some examples, a user equipment (UE) may request an offset for the start time of data transmission on a pre-configured uplink resource (PUR). In some such examples, a PUR configuration request sent by the UE may include a time offset request. Alternatively, a PUR configuration sent by the base station may include a time offset. In this disclosure, PUR configuration may refer to an initial PUR configuration or a PUR reconfiguration. In some examples, the PUR configuration may be sent by the base station regardless of whether the UE sends a PUR configuration request. The maximum PUR time offset range may be the same as the maximum PUR period. Future recurring PUR timings are based on the first PUR timing and PUR periodicity. In a configuration, a PUR configuration request may be sent in a PURConfigurationRequest message. The requestedTimeOffset field may request an offset. The base station may send the PUR start time in the pur-StartTime field of the PUR-Config information element. Additionally, the base station may configure and / or reconfigure a PUR with or without a UE request. PUR configuration and / or reconfiguration can be provided in the Radio Resource Control (RRC) connection release message. That is, the PUR-Config information element can be included in the RRCConnectionRelease message.

[0029] The network may not be aware of when the UE successfully received the RRC connection release message. The release message can be successfully received via a potential repetition of the initial transmission and one or more potential retransmissions, where the retransmissions may also include a repetition. After the UE successfully receives the release message, it enters idle mode without sending an acknowledgment RRC message to the network. In some examples, the UE may send acknowledgment via one or both of the physical layer acknowledgment (PHY ACK) or RLC polling bits (if configured).

[0030] Based on current Media Access Control (MAC) specifications, misalignment is possible. For example, a UE might receive downlink messages in the first Physical Downlink Shared Channel (PDSCH). In this example, the base station might miss an ACK and retransmit the downlink message. The UE might skip decoding the second downlink message, yet still send an ACK corresponding to the first downlink message. The base station might incorrectly assume the UE only received the second downlink message. Depending on when the downlink message is received by the UE, the understanding of the PUR start time (e.g., the first PUR timing) can be misaligned. An explicit reference time is desirable for determining the first PUR timing.

[0031] Figure 1 This is a schematic diagram illustrating a network 100 in which various aspects of this disclosure can be practiced. Network 100 can be a 5G or NR network or other wireless networks, such as an LTE network. Wireless network 100 can include multiple BS110s (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and can also be referred to as a base station, NR BS, Node B, gNB, 5G Node B (NB), access point, Transmit / Receive Point (TRP), etc. Each BS can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0032] A BS can provide communication coverage for macro cells, pico cells, femto cells, and / or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions. A pico cell can cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions. A femto cell can cover a relatively small geographic area (e.g., a residential area) and allow restricted access by UEs associated with the femto cell (e.g., UEs in a Closed User Group (CSG)). A BS used for macro cells can be called a macro BS. A BS used for pico cells can be called a pico BS. A BS used for femto cells can be called a femto BS or a home BS. Figure 1 In the example shown, BS110a can be a macro BS for macro cell 102a, BS110b can be a pico BS for pico cell 102b, and BS110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” can be used interchangeably herein.

[0033] In some respects, the cell may not necessarily be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile BS. In some respects, BSs may interconnect with each other and / or interconnect with one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) using any suitable transport network.

[0034] The wireless network 100 may also include a relay station. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and send data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay station 110d can communicate with macro BS110a and UE 120d to facilitate communication between BS110a and UE 120d. A relay station can also be referred to as a relay BS, relay base station, repeater, etc.

[0035] Wireless network 100 can be a heterogeneous network, including different types of base stations (BSs), such as macro BSs, pico BSs, femto BSs, repeater BSs, etc. These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and repeater BSs can have lower transmit power levels (e.g., 0.1 to 2 watts).

[0036] Network controller 130 can be coupled to a collection of BSs and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via backhaul. BSs can also communicate with each other, for example, directly or indirectly via wireless or wired backhaul.

[0037] UE 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless communication network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, user unit, station, etc. UE may be a cellular phone (e.g., a smartphone), personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, medical device or equipment, biometric sensor / device, wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), entertainment device (e.g., music or video device, or satellite wireless unit), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0038] Some UEs can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, instruments, monitors, location tags, etc., which can communicate with base stations, another device (e.g., a remote device), or other entities. For example, a wireless node can provide connectivity to or to a network (e.g., a wide area network, such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120, such as processor components, memory components, etc.

[0039] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0040] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary to communicate with each other). For example, UEs 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, mesh networks, etc.). In this case, UEs 120 can perform scheduling operations, resource selection operations, and / or other operations as described elsewhere herein, such as those performed by base station 110.

[0041] As indicated above, Figure 1 This is provided merely as an example. Other examples may be provided in conjunction with... Figure 1 The examples described are different.

[0042] Figure 2 A block diagram showing a design 200 for base station 110 and UE 120 is provided, which may be... Figure 1The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, wherein typically T≥1 and R≥1.

[0043] At base station 110, transmit processor 220 can receive data for one or more UEs from data source 212, select one or more modulation and decoding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper-layer signaling, etc.), and provide overhead symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding, if applicable) on data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its own output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted separately via T antennas 234a to 234t. Synchronization signals can be generated using position coding to convey additional information, according to various aspects described in more detail below.

[0044] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can condition (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain the received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols if applicable, and provide the detected symbols. Receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, and provide decoded data for UE 120 to data sink 260, and decoded control information and system information to controller / processor 280. The channel processor can determine the Received Reference Signal Power (RSRP), Received Signal Strength Indicator (RSSI), Received Reference Signal Quality (RSRQ), Channel Quality Indicator (CQI), etc. In some aspects, one or more components of UE120 may be included in a housing.

[0045] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). Transmit processor 264 can also generate reference symbols for one or more reference signals. Symbols from transmit processor 264 can be pre-coded (if applicable) by TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for DFS-s-OFDM, CP-OFDM, etc.), and transmitted to base station 110. At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 254, detected (if applicable) by MIMO detector 236, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. The receiver processor 238 can provide decoded data to the data sink 239 and decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and transmit data to the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0046] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2Any other components may perform one or more techniques associated with machine learning for nonlinearity, as described in more detail elsewhere. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component can execute or direct, for example Figure 6 -8 and / or other procedures as described. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. Scheduler 246 may schedule the UE for data transmission on the downlink and / or uplink.

[0047] In some aspects, UE 120 may include a unit for receiving PUR configuration information, the PUR configuration information including one or more LSBs of H-SFN, a unit for determining the PUR start time based on the H-SFN identified by one or more LSBs, and a unit for sending data messages to the base station on the PUR indicated in the PUR configuration information at the PUR start time.

[0048] In some aspects, UE 120 may include units for receiving downlink messages including pre-configured uplink (UL) resource (PUR) configuration information; units for determining at least one least significant bit (LSB) of the supersystem frame number (H-SFN) corresponding to the received downlink message; and units for transmitting a signal including one or more LSBs to the base station. The signal may include an RLC (Radio Link Control) message, an RRC message, or a similar type of message.

[0049] In some aspects, UE 120 may include a unit for decoding downlink (DL) transmissions, a unit for determining whether a DL transmission is a retransmission, a unit for using the H-SFN of the DL transmission as a reference H-SFN for determining the PUR start time when the DL transmission is a retransmission, and a unit for sending data messages to the base station on the PUR indicated in the PUR configuration information at the PUR start time.

[0050] As indicated above, Figure 2 This is provided merely as an example. Other examples may be provided in conjunction with... Figure 2 The examples described are different.

[0051] Legacy uplink (UL) data transmission (up to version 14) employed a four-step UL random access procedure, allowing data transmission in the uplink transmission of message 5 (Msg 5). In at least version 15 (Rel-15), the earlier data transmission (EDT) was specified to support a two-step uplink access procedure, allowing data to be sent in the uplink transmission of message 3 (Msg 3). Data transmission in the uplink transmission of message 1 (Msg 1) (referred to as pre-configured uplink resources (PUR)) was specified in at least version 16 (Rel-16). In such examples, a UE in Radio Resource Control Idle (RRC_IDLE) mode can have effective timing advance (TA) and can use PUR for uplink data transmission. In some such examples, timing advance can be specified for a stationary UE. PUR can be an example of an permissionless method for uplink data transmission, and can improve uplink transmission efficiency and also reduce power consumption. For example, for enhanced machine-type communication / narrowband IoT (eMTC / NB-IoT) devices, PUR can improve transmission efficiency and reduce power consumption.

[0052] Based on various aspects of this disclosure, Figure 3 This shows an example of a PUR call flow 300. (Example follows) Figure 3 As shown, at time T1, the UE is in Radio Resource Control (RRC) connected mode. While in connected mode, at time T2, the UE can request pre-configured uplink resources (PURs) for uplink transmissions. In some examples, the resource request may include a PUR offset request, which indicates the requested offset relative to the PUR start time. As described, the PUR request at time T2 can be optional.

[0053] exist Figure 3In the example, the base station (e.g., eNB or gNB) sends an RRC connection release message to the UE at time T3. The RRC connection release message may include PUR configuration or reconfiguration. PUR configuration or reconfiguration may identify the PUR start time for performing uplink transmissions using the PUR. In some implementations, the base station may configure and / or reconfigure the PUR with or without a UE request (e.g., a UE request sent at time T2). In some implementations, PUR configuration and / or PUR reconfiguration includes one or more bits to indicate the least significant bit (LSB) of the current supersystem frame number (H-SFN) to resolve misalignment. In some such implementations, one bit is allocated to indicate the LSB. In other implementations, more than one least significant bit of the H-SFN may be indicated. In some such implementations, the remaining bits used to identify the H-SFN may exist in the system information block or be determined by the UE based on information in the system information block.

[0054] In response to receiving an RRC connection release, the UE enters RRC idle mode at time T4. While in idle mode, the UE transmits uplink data to the base station on pre-configured uplink resources (PUR) at the PUR start time (indicated as time T5). The PUR start time can be a specific subframe from a set of subframes within a frame. In some examples, the UE uses the PUR to perform uplink data transmission to the base station. Figure 3 In the example, at time T6, the PUR is released after the UE performs an idle mode transmission (e.g., RRC_IDLE mode transmission). In one configuration, the PUR can be released in response to the UE receiving a PUR release message from the base station (in... Figure 3 (Not shown in the image) and is released. Alternatively, the UE can release the PUR autonomously without receiving a PUR release message. In some examples, after the PUR is released, the UE can enter a connected mode (e.g., RRC connected mode).

[0055] As discussed, the UE can request an offset for the PUR start time. A PUR configuration request sent by the UE may include a time offset request. A PUR configuration sent by the base station may include a time offset. The maximum PUR time offset range may be the same as the maximum PUR periodicity. Future recurring PUR timings are based on the first PUR timing and the PUR periodicity. In a configuration, the PUR configuration request may be sent in a PURConfigurationRequest message. The requestedTimeOffset field can request an offset. The base station may send the PUR start time in the pur-StartTime field of the PUR-Config information element. Alternatively, the base station may configure and / or reconfigure the PUR with or without a UE request. PUR configuration and / or reconfiguration may be provided in an RRC connection release message. That is, the PUR-Config information element may be included in an RRCConnectionRelease message.

[0056] The network may not be aware of when the UE successfully received the RRC connection release message. The release message can be successfully received via a potential repetition of the initial transmission and one or more potential retransmissions. In some examples, one or more retransmissions may also be a repetition. After the UE successfully receives the release message, it enters idle mode without sending an acknowledgment RRC message to the network. Acknowledgment can be a physical layer ACK (PHY ACK) or an RLC polling bit (if configured).

[0057] In traditional systems, misalignment is possible based on current Media Access Control (MAC) specifications. For example, a UE might receive downlink messages in the first Physical Downlink Shared Channel (PDSCH). In this example, the base station might miss the acknowledgment (ACK) and retransmit the downlink message. The UE might skip decoding the second downlink message, yet still send an ACK corresponding to the first downlink message. The base station might incorrectly assume the UE only received the second downlink message. Depending on when the downlink message is received by the UE, the understanding of the PUR start time (e.g., the first PUR timing) can be misaligned. An explicit reference time is desirable for determining the first PUR timing.

[0058] The offset time can be provided based on a relative delay and / or gap relative to the current time. To reduce ambiguity, one or more solutions can be used. In one configuration, one or more least significant bits (LSBs) of the current supersystem frame number (H-SFN) can be included in the PUR configuration message to indicate the reference time of the initial downlink (DL) message sent by the base station.

[0059] In some implementations, based on the received PUR configuration (e.g., pur-Config) or reconfiguration, the UE determines that the PUR start time (e.g., the first PUR timing) occurs after a cycle of FLOOR(offset / 1024)H-SFN(rounded down (offset / 1024)H-SFN) = H-SFN. Ref +offset)mod 1024(H-SFN=(H-SFN Ref The H-SFN is determined by (+offset) modulo 1024), where the offset can be determined by an identifier in the PUR configuration, such as the periodicityAndOffset identifier. Furthermore, H-SFN... Ref The H-SFN corresponds to the last subframe of the first transmission containing the RRC connection release message (e.g., RRCConnectionRelease) with the PUR configuration, while also taking into account the H-SFN LSB information. In some examples, the H-SFN cycle corresponds to a duration of 1024 H-SFNs. Alternatively, the system frame number (SFN) and the subframe used for the PUR start time can be indicated by a start SFN indicator (e.g., startSFN) and a start subframe indicator (e.g., startSubframe).

[0060] The number of bits used for the LSB can be based on the length of time used to determine the initial DL message. For example, one LSB can be used to determine the initial DL message after one or more DL retransmissions. The same LSB with the H-SFN corresponding to the initial DL message can be included in subsequent retransmissions of the same DL message. Both the network and the UE determine the first PUR timing based on the reference H-SFN corresponding to the initial DL message. That is, the retransmitted message has the same H-SFN value as in the initial transmission of the message.

[0061] Alternatively or concurrently, the value of the LSB can be the LSB of the H-SFN following the current H-SFN (e.g., following the initial PUR configuration message transmission). In some examples, the value of the LSB can be the LSB of the H-SFN preceding the current H-SFN. In some implementations, if a one-bit LSB is used, this bit can be set to (H-SFN logical AND 0000000001b) if the reference point is the start of the current H-SFN. Alternatively, if the reference point is the start of a subsequent H-SFN, this bit can be set to ((H-SFN+1) logical AND 0000000001b). In such examples, the H-SFN is 10 bits. The H-SFN is not limited to 10 bits; more or fewer bits can be used for the H-SFN.

[0062] In one configuration, if the UE sends a Radio Link Control (RLC) status report, the report may include the LSB of the H-SFN on which the UE received a connection release (e.g., RRC connection release). The base station and the UE can use the indicated H-SFN as a reference time.

[0063] In one configuration, if the UE decodes a DL transmission, it can determine whether the DL transmission is a DL retransmission. For example, an indication from the Media Access Control (MAC) layer to the Radio Resource Control (RRC) layer in the UE can instruct the base station to attempt to retransmit the H-SFN. Therefore, the UE should use the new H-SFN as the reference H-SFN, rather than the previously decoded H-SFN.

[0064] For each transmission and retransmission, the MAC Protocol Data Unit (PDU) containing the downlink message may be repeated in multiple subframes (e.g., 1, 2, 4, 8, etc.) to extend coverage. The H-SFN can be changed for each repeated subframe. In one configuration, the mapping from the reference H-SFN to a specific shared downlink channel (e.g., Physical Downlink Shared Channel (PDSCH)) repeated subframe is fixed. For example, the reference H-SFN can be designated as the H-SFN corresponding to the last subframe of the PDSCH repetition. Alternatively, the SFN can be designated as the H-SFN corresponding to the first subframe of the PDSCH repetition. Additionally or alternatively, in a PUR configuration, the actual subframe within the H-SFN is indicated for the first PUR timing.

[0065] In one configuration, the start time of the first PUR is provided based on the absolute number of H-SFNs rather than relative to the current time. For example, the number of H-SFNs could be two hundred. If the current number of H-SFNs is one thousand, the UE will wait until the number of H-SFNs reaches two hundred (this occurs after the H-SFNs have looped back). The start time based on the absolute number of H-SFNs can be included in the PUR configuration sent by the base station or in the PUR configuration request sent by the UE.

[0066] In LTE, for example, the H-SFN length is 10.24 seconds and the H-SFN is 10 bits. Accordingly, the H-SFN wraps around every 2.9 hours (e.g., 10.24 seconds * 1024 = 2.9127 hours). Relative to the current time, the H-SFN can wrap around once or more before the first PUR. Therefore, the UE can be notified of the number of H-SFN wrap-around processes skipped from the current time until the first occurrence of the PUR.

[0067] In a PUR configuration, a specific subframe (e.g., a specific number of subframes) within an H-SFN is indicated for the first PUR timing. That is, a specific subframe (e.g., an actual subframe) within an H-SFN can be indicated as the PUR start time.

[0068] In one configuration, the start time of the first PUR is provided based on an absolute timestamp (e.g., UTC time). The start time based on an absolute timestamp can be included in the PUR configuration sent by the base station or in the PUR configuration request sent by the UE.

[0069] In some implementations, specific subframes within the H-SFN can be excluded from the PUR configuration request message. The granularity based on the H-SFN duration may be sufficient for the request.

[0070] For a PUR configuration request sent by the UE, indications for subframes within the H-SFN used for the first PUR timing can be excluded. The granularity based on the H-SFN duration may be sufficient for the request. As discussed, the offset is used to request the PUR start time based on the H-SFN gap or relative time gap relative to the current H-SFN or the current absolute time. The offset can also be related to segments of the H-SFN (e.g., subframes).

[0071] Figure 4 This is a schematic diagram illustrating, for example, an example process 400 performed by a UE according to various aspects of this disclosure. Figure 4As shown, at block 402, the UE (e.g., using antenna 252, demodulator (DEMOD) 254, RX processor 258, controller / processor 280, memory 282, etc.) receives PUR configuration information, which includes one or more LSBs referencing the H-SFN. In some implementations, the values ​​of one or more LSBs correspond to the LSB of the H-SFN corresponding to the last subframe of the initial DL message transmission. In other implementations, the values ​​of one or more LSBs correspond to the LSB of the H-SFN corresponding to the first subframe of the initial DL message transmission. Alternatively, the LSB values ​​correspond to the H-SFN following the initial DL message transmission. In other implementations, one or more LSBs indicate the reference time of the initial downlink message. In such implementations, the initial DL message includes PUR configuration information. In some such implementations, the initial downlink message is an RRC connection release message, such as in... Figure 3 The RRC connection release message is received at time T3. In this implementation, the retransmission of the initial DL message includes one or more LSBs.

[0072] At block 404, the UE (e.g., using controller / processor 280, memory 282, etc.) determines the PUR start time based on the H-SFN identified by one or more LSBs. In some implementations, the H-SFN may be further determined based on a specific subframe in a set of repeating subframes used for the Physical Downlink Shared Channel (PDSCH). At block 406, the UE (e.g., using antenna 252, modulator (MOD) 254, TX processor 264, controller / processor 280, memory 282, etc.) transmits data to the base station on the PUR indicated in the PUR configuration information at the PUR start time.

[0073] Figure 5 A schematic diagram illustrating, for example, an example process 500 performed by a UE according to various aspects of this disclosure. Figure 5 As shown, at block 502, the UE (e.g., using antenna 252, DEMOD 254, RX processor 258, controller / processor 280, memory 282, etc.) receives a downlink message that includes pre-configured uplink (UL) resource (PUR) configuration information. In some examples, the downlink message is a Radio Resource Control (RRC) connection release message.

[0074] exist Figure 5In the example, at block 504, the UE (e.g., using controller / processor 280, memory 282, etc.) determines one or more LSBs in which the UE receives an H-SFN including a connection release message containing PUR configuration information. In some implementations, the UE determines the PUR start time based on the H-SFN corresponding to at least one LSB. In some implementations, the UE may determine the H-SFN based on a specific subframe within a set of repeating subframes used for the Physical Downlink Shared Channel (PDSCH). The specific subframe may be the first subframe in the set of repeating subframes used for the PDSCH. In some implementations, the specific subframe may be the last subframe in the set of repeating subframes used for the PDSCH. In other implementations, the UE receives a message identifying the subframe of the H-SFN, the identified subframe corresponding to the PUR start time.

[0075] At block 506, the UE (e.g., using antenna 252, MOD 254, TX processor 264, controller / processor 280, memory 282, etc.) transmits a signal including one or more LSBs to the base station. This signal can be included in an RLC message, an RRC message, or another type of signal. The base station can align the PUR start time with the UE based on the one or more LSBs included in the message.

[0076] Figure 6 A schematic diagram illustrating, for example, an example process 600 performed by a UE according to various aspects of this disclosure is shown. Figure 6 As shown, at block 602, the UE (e.g., using controller / processor 280, memory 282, etc.) decodes the downlink (DL) transmission. At block 604, the UE (e.g., using controller / processor 280, memory 282, etc.) determines whether the DL transmission is a retransmission. In some examples, the UE determines whether the DL transmission is a retransmission based on the RRC message.

[0077] At block 606, when the DL transmission is a retransmission, the UE (e.g., using controller / processor 280, memory 282, etc.) uses the H-SFN of the DL transmission as a reference H-SFN for determining the PUR start time. In some implementations, the UE determines the H-SFN based on a specific subframe within repeating subframes used for the Physical Downlink Shared Channel (PDSCH). In some such implementations, the specific subframe is the first subframe among the repeating subframes used for PDSCH. In other such implementations, the specific subframe is the last subframe among the repeating subframes used for PDSCH. In other implementations, the UE receives PUR configuration information from the base station and determines the subframe corresponding to the PUR start time based on the PUR configuration information. Still in other implementations, the UE receives a message for identifying the subframe of the H-SFN. In such implementations, the identified subframe corresponds to the PUR start time. At box 608, the UE (e.g., using antenna 252, MOD 254, TX processor 264, controller / processor 280, memory 282, etc.) sends data to the base station on the PUR at the PUR start time.

[0078] Examples of implementation methods are described in the following numbered clauses:

[0079] 1. A method for wireless communication, comprising:

[0080] Receive pre-configured uplink resource (PUR) configuration information, the PUR configuration information including at least one least significant bit (LSB) of the supersystem frame number (H-SFN);

[0081] The PUR start time is determined based on the H-SFN identified at least by the LSB; and

[0082] At the start time of the PUR, a data message is sent to the base station on the PUR indicated in the PUR configuration information.

[0083] 2. The method according to Clause 1, wherein the value of the LSB corresponds to the LSB of the current H-SFN or the last H-SFN.

[0084] 3. The method according to any one of clauses 1-2, wherein:

[0085] The LSB indicates the reference time for the initial downlink message; and

[0086] The initial downlink message includes the PUR configuration information.

[0087] 4. The method according to Clause 3, wherein the initial downlink message includes a Radio Resource Control (RRC) connection release message.

[0088] 5. The method according to Clause 3, wherein the retransmission of the initial downlink message includes the LSB.

[0089] 6. The method according to any one of clauses 1-5, wherein the value of the LSB corresponds to the H-SFN following the initial downlink message.

[0090] 7. The method according to any one of clauses 1-6 further comprises: determining the H-SFN based on a specific subframe in a set of repeating subframes used for the Physical Downlink Shared Channel (PDSCH).

[0091] 8. The method according to Clause 7, wherein the particular subframe is the first subframe in the set of subframes.

[0092] 9. The method according to Clause 7, wherein the particular subframe is the last subframe in the set of subframes used.

[0093] 10. The method according to any one of clauses 1-9, wherein the PUR configuration information includes initial configuration information or reconfiguration information.

[0094] 11. A method for wireless communication, comprising:

[0095] Receive downlink messages that include pre-configured uplink resource (PUR) configuration information;

[0096] Determine at least one least significant bit (LSB) of the supersystem frame number (H-SFN) corresponding to the received downlink message; and

[0097] Send a signal including at least one LSB to the base station.

[0098] 12. The method according to Clause 11, wherein the downlink message includes a Radio Resource Control (RRC) connection release message.

[0099] 13. The method according to any one of clauses 11-12 further comprises: determining the PUR start time based on the H-SFN corresponding to the at least one LSB.

[0100] 14. The method according to any one of clauses 11-13 further comprises: determining the H-SFN based on a specific subframe within a set of repeating subframes used for the Physical Downlink Shared Channel (PDSCH).

[0101] 15. The method according to Clause 14, wherein the particular subframe is the first subframe in a set of repeating subframes used for the PDSCH.

[0102] 16. The method according to Clause 14, wherein the particular subframe is the last subframe in the set of repeated subframes used for the PDSCH.

[0103] 17. The method according to any one of clauses 11-16 further comprises: receiving a message for identifying a subframe of the H-SFN, the identified subframe corresponding to the PUR start time.

[0104] 18. A method for wireless communication, comprising:

[0105] Decode the downlink transmission;

[0106] Determine whether the downlink transmission is a retransmission;

[0107] When the downlink transmission is a retransmission, the pre-configured uplink resource (PUR) start time is determined as a reference H-SFN based on the supersystem frame number (H-SFN) of the downlink transmission; and

[0108] At the start time of the PUR, data is sent to the base station on the PUR.

[0109] 19. The method according to Clause 18 further comprises: determining whether the downlink transmission is a retransmission based on a Radio Resource Control (RRC) message.

[0110] 20. The method according to any one of clauses 18-19 further comprises: determining the H-SFN based on a specific subframe in a set of repeating subframes used for the Physical Downlink Shared Channel (PDSCH).

[0111] 21. The method according to Clause 20, wherein the particular subframe is the first subframe in a set of repeating subframes used for the PDSCH.

[0112] 22. The method according to Clause 20, wherein the particular subframe is the last subframe in the set of repeated subframes used for the PDSCH.

[0113] 23. The method according to any one of clauses 18-22 further comprises:

[0114] Receive PUR configuration information from the base station; and

[0115] The subframe corresponding to the PUR start time is determined based on the PUR configuration information.

[0116] 24. The method according to any one of clauses 18-23 further comprises: receiving a message for identifying a subframe of the H-SFN, the identified subframe corresponding to the PUR start time.

[0117] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the parties to the precise form disclosed. Modifications and changes may be made based on the foregoing disclosure or may be derived from practice in the parties involved.

[0118] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented in a combination of hardware, firmware, and / or hardware and software.

[0119] Some aspects are described in conjunction with thresholds in this paper. As used in this paper, depending on the context, satisfying a threshold can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0120] It will be apparent that the systems and / or methods described herein can be implemented in various forms, including hardware, firmware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited to any particular aspect. Therefore, the operation and behavior of the systems and / or methods are described without mentioning any specific software code herein—it is to be understood that software and hardware can be designed to implement systems and / or methods at least in part based on those described herein.

[0121] Even if a particular combination of features is recited in the claims and / or disclosed in the description, such combinations are not intended to limit the disclosure of the aspects. In fact, many of these features can be combined in ways not specifically recited in the claims and / or disclosed in the description. While each dependent claim listed below may directly depend on only one claim, the disclosure of the aspects includes each dependent claim in combination with each other claim in the claim set. The phrase referred to as “at least one of” in the list of items refers to any combination of these items, including single members. For example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a–b, a–c, bc, and abc, as well as any combination of the same elements in multiples (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0122] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as definitive or essential. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “has,” “have,” “having,” etc., are intended to be open-ended terms. Further, unless otherwise explicitly stated, the phrase “based on” is intended to mean “at least partially based on.”

Claims

1. A method for wireless communication, comprising: Receive pre-configured uplink resource (PUR) configuration information, the PUR configuration information including at least one least significant bit (LSB) of the supersystem frame number (H-SFN). Based on the H-SFN corresponding to the last subframe of the first transmission containing the Radio Resource Control (RRC) connection release message that is at least identified by the LSB and at least based on the PUR configuration information. Ref The H-SFN is determined to determine the PUR start time; as well as At the start time of the PUR, a data message is sent to the base station on the PUR indicated in the PUR configuration information.

2. The method according to claim 1, wherein, The value of the LSB corresponds to the LSB of the current H-SFN or the previous H-SFN.

3. The method according to claim 1, wherein: The LSB indicates the reference time for the initial downlink message; and The initial downlink message includes the PUR configuration information.

4. The method according to claim 3, wherein, The initial downlink message includes the RRC connection release message.

5. The method according to claim 3, wherein, The retransmission of the initial downlink message includes the LSB.

6. The method according to claim 1, wherein, The value of the LSB corresponds to the H-SFN following the initial downlink message.

7. The method according to claim 1, further comprising: The H-SFN is determined based on a specific subframe from the set of repeating subframes used for the Physical Downlink Shared Channel (PDSCH).

8. The method according to claim 7, wherein, The specific subframe is the first subframe in the set of subframes.

9. The method according to claim 7, wherein, The specific subframe is the last subframe in the set of subframes used.

10. The method according to claim 1, wherein, The PUR configuration information includes initial configuration information or reconfiguration information.

11. A method for wireless communication, comprising: Receive downlink messages that include pre-configured uplink resource (PUR) configuration information; Determine at least one least significant bit (LSB) of the supersystem frame number (H-SFN) corresponding to the received downlink message, wherein the H-SFN is identified at least by the LSB and corresponds at least to the H-SFN of the last subframe of the first transmission containing the Radio Resource Control (RRC) connection release message containing the PUR configuration information. Ref It is determined; as well as Send a signal including at least one LSB to the base station.

12. The method according to claim 11, wherein, The downlink message includes the RRC connection release message.

13. The method of claim 11, further comprising: The PUR start time is determined based on the H-SFN corresponding to the at least one LSB.

14. The method of claim 11, further comprising: The H-SFN is determined based on a specific subframe within a set of repeating subframes used for the Physical Downlink Shared Channel (PDSCH).

15. The method according to claim 14, wherein, The specific subframe is the first subframe in the set of repeating subframes used for the PDSCH.

16. The method of claim 14, wherein, The specific subframe is the last subframe in the set of repeating subframes used for the PDSCH.

17. The method of claim 11, further comprising: Receive a message for identifying the subframe of the H-SFN, the identified subframe corresponding to the PUR start time.

18. A method for wireless communication, comprising: Decode the downlink transmission; Determine whether the downlink transmission is a retransmission; When the downlink transmission is a retransmission, a pre-configured uplink resource (PUR) start time is determined as a reference H-SFN based on the supersystem frame number (H-SFN) of the downlink transmission. This H-SFN is identified at least by the least significant bit (LSB) and corresponds at least to the H-SFN of the last subframe of the first transmission containing the Radio Resource Control (RRC) connection release message containing PUR configuration information. Ref Determined; and At the start time of the PUR, data is sent to the base station on the PUR.

19. The method of claim 18, further comprising: The downlink transmission is determined as a retransmission based on the RRC connection release message.

20. The method of claim 18, further comprising: The H-SFN is determined based on a specific subframe from the set of repeating subframes used for the Physical Downlink Shared Channel (PDSCH).

21. The method according to claim 20, wherein, The specific subframe is the first subframe in the set of repeating subframes used for the PDSCH.

22. The method according to claim 20, wherein, The specific subframe is the last subframe in the set of repeating subframes used for the PDSCH.

23. The method of claim 18, further comprising: Receive the PUR configuration information from the base station; as well as The subframe corresponding to the PUR start time is determined based on the PUR configuration information.

24. The method of claim 18, further comprising: Receive a message for identifying the subframe of the H-SFN, the identified subframe corresponding to the PUR start time.

25. A user equipment (UE), comprising: At least one transceiver; At least one processor; as well as At least one memory includes instructions executable by the at least one processor to cause the UE to perform the following operations: The at least one transceiver receives pre-configured uplink resource (PUR) configuration information, which includes at least one least significant bit (LSB) of the supersystem frame number (H-SFN). Based on the H-SFN corresponding to the last subframe of the first transmission containing the Radio Resource Control (RRC) connection release message that is at least identified by the LSB and at least based on the PUR configuration information. Ref The H-SFN is determined to determine the PUR start time; as well as Data is transmitted via the at least one transceiver and to the base station at the PUR start time indicated in the PUR configuration information.

26. The UE according to claim 25, wherein: The LSB indicates the reference time for the initial downlink message; and The initial downlink message includes the PUR configuration information.

27. The UE according to claim 26, wherein, The initial downlink message includes the RRC connection release message.

28. The UE according to claim 26, wherein, The retransmission of the initial downlink message includes the LSB.

29. The UE according to claim 25, further comprising: The H-SFN is determined based on the first subframe in the set of repeating subframes used for the Physical Downlink Shared Channel (PDSCH).

30. The UE according to claim 25, further comprising: The H-SFN is determined based on the last subframe in the set of repeating subframes used for the Physical Downlink Shared Channel (PDSCH).

Images