Transmission, retransmission and HARQ processes for preconfigured uplink resources in idle mode
By preconfiguring uplink resources for the UE in the wireless communication system and supporting HARQ and EDT fallback mechanisms, the UE data transmission efficiency and reliability problems in idle mode are solved, and efficient data transmission and multi-HARQ process support are achieved.
Patent Information
- Application Number
- CN201980072274.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-11-01
- Filing Date
- 2019-10-24
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2039-10-24
AI Technical Summary
In wireless communication systems, how UEs in idle mode efficiently utilize preconfigured uplink resources to support data transmission is a challenge, especially in the HARQ process, the existing technology lacks effective resource configuration and retransmission mechanisms, resulting in transmission Insufficient efficiency and reliability.
It provides pre-configured uplink resources for UE in idle mode, and supports the hybrid automatic retransmission request (HARQ) process, by redesigning the search space of the physical downlink control channel and introducing an early data transmission (EDT) fallback mechanism. Ensure that the UE can effectively use and manage uplink resources in idle mode, including configuring parameters such as transmission block size, periodicity and coverage enhancement level, and implementing multi-HARQ process support.
Improves the efficiency and reliability of UE data transmission in idle mode, supports multi-HARQ processes, enhances the segmentation and retransmission mechanism of transmission blocks, ensures that uplink data can be processed efficiently in idle mode, and improves the overall system Performance and user experience.
Smart Images

Figure CN112997432B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 754,479, filed on November 1, 2018, which is hereby incorporated by reference in its entirety. Technical Field
[0003] The present application relates generally to wireless communication systems, and more particularly to using preconfigured uplink resources in idle mode. Background Art
[0004] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is often referred to as Worldwide Interoperability for Microwave Access (WiMAX) by industry organizations; and the IEEE 802.11 standard for wireless local area networks (WLANs), which is often referred to as Wi-Fi by industry organizations. In the 3GPP radio access network (RAN) in the LTE system, the base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also often referred to as an Evolved Node B, an Enhanced Node B, an eNodeB, or an eNB) and / or a Radio Network Controller (RNC) in the E-UTRAN, which communicates with a wireless communication device referred to as a user equipment (UE). In the fifth generation (5G) wireless RAN, the RAN node may include a 5G node, a new radio (NR) node, or a gNodeB (gNB).
[0005] The RAN uses radio access technologies (RATs) to communicate between RAN nodes and UEs. The RAN may include a Global System for Mobile Communications (GSM), an Enhanced Data Rate for GSM Evolution (EDGE) RAN (GERAN), a Universal Terrestrial Radio Access Network (UTRAN), and / or an E-UTRAN, which provides access to communication services through a core network. Each of the RANs operates according to a specific 3GPP RAT. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements the Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, and the E-UTRAN implements the LTE RAT.
[0006] The core network may be connected to the UE via a RAN node. The core network may include a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an access network detection and selection function (ANDSF) server, an enhanced packet data gateway (ePDG) and / or a mobility management entity (MME). BRIEF DESCRIPTION OF THE DRAWINGS
[0007] Figure 1 is a flow chart illustrating a method for a UE in a wireless network according to one embodiment.
[0008] Figure 2 is a flow chart illustrating another method for a UE in a wireless network according to one embodiment.
[0009] Figure 3 is a flow chart illustrating a method for a base station (e.g., an eNB or gNB) in a wireless network, according to one embodiment.
[0010] Figure 4 A system according to one embodiment is shown.
[0011] Figure 5 An apparatus according to one embodiment is shown.
[0012] Figure 6 An exemplary interface according to one embodiment is shown.
[0013] Figure 7 Components according to one embodiment are shown.
[0014] Figure 8 A system according to one embodiment is shown.
[0015] Fig. 9 Components according to one embodiment are shown. DETAILED DESCRIPTION
[0016] A cell provides a communication link between a base station and a UE in a wireless network. A UE in a cell generally has two working states: a connected state and an idle state. The cell configures a cell radio network temporary identity (C-RNTI) that can uniquely identify the UE in the cell for a UE in a connected state, and the UE can use dedicated uplink / downlink resources to perform data communication in the cell based on the C-RNTI. When the UE has no service or the UE's service is not in use, the wireless network can instruct the UE to enter an idle state. When a UE in an idle state needs to send uplink data or receive downlink data, the UE initiates a random access (RA) and radio resource control (RRC) connection setup process so that the UE can regain the C-RNTI and enter a connected state. Then, the UE can use dedicated uplink / downlink resources again to perform data communication.
[0017] Certain embodiments herein provide for transmission in dedicated preconfigured uplink resources in an idle state (also referred to herein as idle mode) for UEs with valid timing advance (TA).While the initial focus may be on dedicated preconfigured uplink resources in idle mode, shared resources may also be considered.
[0018] In idle mode, hybrid automatic repeat request (HARQ) may be supported for transmission in dedicated pre-configured uplink resources. For example, a single HARQ process may be supported. In other embodiments, more than one HARQ process may be supported. Certain embodiments may include a redesign of the corresponding machine type communication (MTC) physical downlink control channel (MPDCCH) search space.
[0019] In idle mode, according to certain embodiments, dedicated preconfigured uplink resources (PURs) are supported and may include at least one of a contention-free shared PUR and a cell broadcast service (CBS) PUR.
[0020] For uplink (UL) transmissions in preconfigured resources, according to certain embodiments, fallback mechanisms for Random Access Channel (RACH) and / or Early Data Transfer (EDT) procedures are supported.
[0021] For transmissions in pre-configured UL resources, according to certain embodiments, an RRC Idle UE may use the latest TA that passes the validation criteria.
[0022] In certain embodiments, the preconfigured UL resources for transmitting data are indicated by RRC signaling.At least UE-specific RRC signaling may be supported.
[0023] Previously, the UE had no HARQ configuration for use in idle mode. In certain embodiments herein, when in connected mode, preconfigured uplink resources (PUR) may be configured for use by the UE in idle mode. When a HARQ process supports transmissions in a PUR in idle mode, the HARQ process may be similar or identical to a HARQ process in random access or a normal HARQ process in connected mode. Embodiments disclosed herein may apply the HARQ process and handle retransmissions for transmissions in a PUR.
[0024] When PUR is configured by dedicated RRC signaling or broadcast, parameters such as transport block size (TBS), periodicity and allowed coverage enhancement (CE) level, number of HARQ processes, etc. may be configured for PUR in idle mode.
[0025] If the UE has UL data larger than the size indicated in the TBS parameters, the UE may send an RRC Connection Request message plus a Buffer Status Report (BSR) plus a segment of the UL data using a PUR.
[0026] For the control plane (CP) solution, according to certain embodiments, the UE may send an RRC connection request (i.e., RRC Early Data Request) with a non-access stratum (NAS) protocol data unit (PDU) with or without a BSR. If the CP data in the NAS PDU is not suitable for the TBS for the PUR, the UE may send an RRC connection request message with or without a BSR and only with a NAS service request.
[0027] The interaction between NAS and access stratum (AS) may be used to decide whether to transmit CP data plus NAS signaling, only NAS signaling, or only NAS service request in PUR based on the TBS size limit of PUR. In certain embodiments, the interaction between NAS and AS may depend on the UE specific implementation.
[0028] For the user plane (UP) solution, according to certain embodiments, if the UE has received a Next Hop Chain Counter (NCC) in the previous connection before transmitting an RRC Connection Resumption Request message with or without multiplexing user plane data and / or BSR, the UE may activate AS security. A new message class for the RRC Connection Resumption Request message may be used to indicate to the base station (e.g., eNB or gNB) that security has been activated. If the user data is larger than the TBS for PUR, segmentation may be performed and the segmented data may be multiplexed with the RRC Resumption Request message.
[0029] In another embodiment, the UE may activate AS security only when the UE is able to send multiplexed user UL data in the PUR, otherwise the UE sends a traditional RRCConnectionResume message with or without BSR in the PUR.
[0030] HARQ Process
[0031] Certain embodiments apply a HARQ process that is the same or similar to the HARQ process used in the random access process.
[0032] Other embodiments modify the HARQ process used in the random access process. For example, if multiple HARQ processes are supported, a separate random access process may be initiated for each HARQ process. HARQ feedback (e.g., acknowledgment (ACK) information or negative acknowledgment (NACK) information) and / or a new grant for transmission or retransmission in response to a transmission in a PUR may indicate a HARQ process identifier (ID).
[0033] In certain embodiments, after the UL transmission in the PUR, the UE starts a new retransmission timer. The UE monitors the physical downlink control channel (PDCCH) in the common search space (CSS) provided in the public configuration using the new RNTI provided in the PUR configuration. If the retransmission timer expires and no information is received (e.g., ACK / NACK or other messages are not received from the eNB), the UE determines that the transmission in the PUR has failed and generates a retransmission in another PUR. After each retransmission, according to certain embodiments, the PUR retransmission timer is restarted. In addition or in another embodiment, if the retransmission timer expires and the UE does not receive any information, the UE can autonomously fall back to initiate a traditional / EDT random access. In another embodiment, if the retransmission timer expires and the UE does not receive any information, the UE can assume that the transmission in the PUR is successful.
[0034] While the retransmission timer is running, according to certain embodiments, the base station (e.g., eNB or gNB) may take certain actions. For example, the base station may provide a retransmission grant addressed to the new RNTI. In certain embodiments, the base station may provide a NACK to the UE indicating that the UE falls back to initiate a traditional / EDT random access. The base station may also provide a successful ID or an indication that may be similar or identical to a contention resolution MAC CE, so the UE can go to sleep immediately. In certain embodiments, the base station may schedule an RRC message that instructs the UE to remain in idle mode (e.g., similar to an EarlyDataComplete message or an RRCConnectionRelease message in EDT) or to move to connected mode (e.g., an RRCConnectionSetup message or an RRCConnectionResume message). As described above, after each retransmission, the PUR retransmission timer may be restarted.
[0035] In some embodiments, the HARQ process in idle mode may follow UL HARQ. For example, after UL transmission, the UE may start a HARQ RTT timer and then start a discontinuous reception mode (DRX) retransmission timer, wherein: if the timer expires and the UE does not receive any information, the UE determines that the transmission failed and generates a retransmission in another PUR; if the timer expires and the UE does not receive any information, the UE may fall back to traditional / EDT random access; or if the timer expires and the UE does not receive any information, the UE may assume that the transmission was successful.
[0036] In certain embodiments, the HARQ process in idle mode may be similar or identical to UL HARQ, where the HARQ process corresponds to a transmission time interval (TTI). After the last repetition of the physical uplink shared channel (PUSCH), the UE monitors the PDCCH for ACK / NACK in a predefined search space, such as the same search space as the CSS for random access response. Monitoring of the PDCCH may start at the xth TTI (e.g., the fourth TTI) after the last repetition of the PUSCH. If the UE does not receive any information, the UE may consider the transmission to have failed and retransmit in the next PUR, or initiate a new traditional RACH / EDT. If a NACK is received, the UE retransmits using the same resource configuration in the TTI corresponding to the same HARQ process of the initial transmission. If an ACK is received, the UE considers the transmission to be successful.
[0037] PUR transmission successful
[0038] In certain embodiments, if the UE receives an RRC message in response to a transmission in a PUR (indicating that the UE remains idle or moves to RRC_CONNECTED), the RRC message may include a new TA command and / or NCC, and the TA validity timer may be restarted. Based on the BSR, the base station (e.g., eNB or gNB) may provide the UE with an additional UL grant to transmit the remaining UL data indicating the new HARQ process.
[0039] In another embodiment, if the UE does not receive any information or ACK in response to the transmission in the PUR and considers the transmission successful, the UE may return to idle mode.
[0040] In certain embodiments, if the UE is using UP Cellular Internet of Things (C-IoT) optimization and has activated security for transmissions in a PUR, the UE may use the same existing keys in the next PUR while the current TA is still valid if the UE still has additional data to transmit. In order to use EDT in a PUR, a condition for initiating EDT may be added - EDT may be used for a PUR even if there are multiple packets to transmit.
[0041] In certain implementations, for a single HARQ process, HARQ process ID=0 may be used.
[0042] In certain embodiments, for multiple HARQ processes, the HARQ process ID may be determined as follows: HARQ process ID = [(CURRENT_TTI / PURinterval) lower limit] modulo numberOfHARQ-Processes, where CURRENT_TTI = [(SFN*10)+subframe number], where SFN is the system frame number, and CURRENT_TTI refers to the subframe in which the first transmission of the bundle occurs.
[0043] For synchronous HARQ, according to certain embodiments, HARQ process ID = CURRENT_TTI modulo numberOfHARQ-Processes.
[0044] Certain embodiments provide for the release of a PUR in idle mode. For example, in one embodiment, if the UE determines to release the PUR and the TA validity timer is still running, the UE may send a new RRC message, a medium access control (MAC) control element (CE), or layer 1 (L1) signaling in the PUR to indicate the release of the PUR to a base station (e.g., an eNB or gNB). In another embodiment, the PUR may be released if the UE initiates a legacy RRC connection / resumption establishment procedure using a legacy physical RACH (PRACH) resource or initiates an EDT using an EDT PRACH resource.
[0045] Exemplary Methods
[0046] Figure 1 1 is a flowchart 100 of a method for a UE in a wireless network according to an embodiment. In box 102, the UE stores configuration data for preconfigured uplink resources. The configuration data includes a radio network temporary identifier (RNTI) for idle mode communication. In box 104, in idle mode, the UE generates an uplink transmission using the preconfigured uplink resources. In box 106, after performing an uplink transmission using the preconfigured uplink resources in idle mode, the UE starts a retransmission timer. In box 108, the UE monitors a physical downlink control channel (PDCCH) in a common search space (CSS) using the RNTI provided in the configuration data for a hybrid automatic repeat request (HARQ) acknowledgment (ACK) or negative acknowledgment (NACK). In box 110, in response to the retransmission timer expiring before receiving an ACK or NACK, the UE determines that the uplink transmission has failed and generates a retransmission in another preconfigured uplink resource. In box 112, after generating the retransmission, the UE restarts the retransmission timer.
[0047] Figure 2 2 is a flow chart of a method 200 for a UE in a wireless network according to another embodiment. In box 202, the UE stores configuration data for pre-configured uplink resources. The configuration data includes a radio network temporary identifier (RNTI) for idle mode communication. In box 204, in idle mode, the UE generates an uplink transmission using the pre-configured uplink resources. In box 206, after uplink transmission using the pre-configured uplink resources in idle mode, the UE starts a retransmission timer. In box 208, the UE monitors the physical downlink control channel (PDCCH) in the common search space (CSS) using the RNTI provided in the configuration data for hybrid automatic repeat request (HARQ) acknowledgment (ACK) or negative acknowledgment (NACK). In box 210, in response to the retransmission timer expiring before receiving an ACK or NACK, the UE initiates a fallback to an early data transmission (EDT) or random access procedure.
[0048] Figure 3is a flow chart illustrating a method 300 for a base station (e.g., an eNB or gNB) in a wireless network, according to one embodiment. In block 302, the method 300 configures a UE with preconfigured uplink resources and a radio network temporary identifier (RNTI) for idle mode communications. In block 304, the method 300 processes an uplink transmission from the UE in the radio network temporary identifier (RNTI) for idle mode communications. In block 306, in response to the uplink transmission, the method 300 generates a message for the UE using the RNTI.
[0049] Exemplary Systems and Apparatus
[0050] Figure 4 The architecture of a system 400 of a network according to some embodiments is shown. The system 400 is shown to include a UE 402; a 5G access node or RAN node (shown as (R) AN node 408); a user plane function (shown as UPF 404); a data network (DN 406), which can be, for example, an operator service, Internet access, or a third-party service; and a 5G core network (5GC) (shown as CN 410).
[0051] CN 410 may include an authentication server function (AUSF 414); a core access and mobility management function (AMF 412); a session management function (SMF 418); a network exposure function (NEF 416); a policy control function (PCF 422); a network function (NF) repository function (NRF 420); a unified data management (UDM 424); and an application function (AF 426). CN 410 may also include other elements not shown, such as a structured data storage network function (SDSF), an unstructured data storage network function (UDSF), etc.
[0052] The UPF 404 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with the DN 406, and a branch point to support multi-homed PDU sessions. The UPF 404 may also perform packet routing and forwarding, packet inspection, user plane portion of policy rule enforcement, lawful interception of packets (UP collection); traffic usage reporting, QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic validation (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 404 may include an uplink classifier to support routing of traffic flows to the data network. The DN 406 may represent various network operator services, Internet access, or third-party services.
[0053] AUSF 414 may store data and handle authentication-related functions for authentication of UE 402. AUSF 414 may facilitate a common authentication framework for various access types.
[0054] AMF 412 may be responsible for registration management (e.g., responsible for registering UE 402, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, as well as access authentication and authorization. AMF 412 may provide the delivery of SM messages for SMF 418 and act as a transparent proxy for routing SM messages. AMF 412 may also provide a communication channel between UE 402 and SMS function (SMSF) ( Figure 4 The AMF 412 may provide for the transmission of short message service (SMS) messages between the AUSF 414 and the UE 402 (not shown). The AMF 412 may act as a security anchor function (SEA), which may include interaction with the AUSF 414 and the UE 402, receiving intermediate keys established as a result of the UE 402 authentication process. In the case of using USIM-based authentication, the AMF 412 may retrieve security materials from the AUSF 414. The AMF 412 may also include a secure content management (SCM) function that receives keys from the SEA for deriving access network-specific keys. In addition, the AMF 412 may be the termination point for the RAN CP interface (N2 reference point), the termination point for NAS (NI) signaling, and perform NAS encryption and integrity protection.
[0055] AMF 412 may also support NAS signaling with UE 402 via the N3 interworking function (IWF) interface. N3IWF may be used to provide access to untrusted entities. N3IWF may be an endpoint of the N2 and N3 interfaces for the control plane and user plane, respectively, and may therefore handle N2 signaling for PDU sessions and QoS from SMF and AMF, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and enforce QoS corresponding to the N3 packet marking taking into account the QoS requirements associated with such markings received via N2. N3IWF may also relay uplink and downlink control plane NAS (NI) signaling between UE 402 and AMF 412, and relay uplink and downlink user plane packets between UE 402 and UPF 404. N3IWF also provides a mechanism for establishing an IPsec tunnel with UE 402.
[0056] SMF 418 may be responsible for session management (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes); UE IP address allocation & management (including optional authorization); selection and control of UP functions; configuring traffic steering at UPF to route traffic to the correct destination; terminating the interface towards the policy control function; control part of policy enforcement and QoS; lawful interception (for SM events and interface with LI system); terminating the SM part of NAS messages; downlink data notification; initiator of AN-specific SM information sent to AN via AMF over N2; determining the SSC mode of the session. SMF 418 may include the following roaming functions: handling local execution to apply QoS SLA (VPLMN); charging data collection and charging interface (VPLMN); lawful interception (for SM events and interface with LI system, in VPLMN); supporting interaction with external DNs to transmit signaling for PDU session authorization / authentication over external DNs.
[0057] NEF 416 may provide a means for securely exposing services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, application functions (e.g., AF 426), edge computing or fog computing systems, etc. In such embodiments, NEF 416 may authenticate, authorize and / or restrict AF. NEF 416 may also convert information exchanged with AF 426 and information exchanged with internal network functions. For example, NEF 416 may convert between AF service identifiers and internal 5GC information. NEF 416 may also receive information from other network functions (NFs) based on their exposure capabilities. The information may be stored at NEF 416 as structured data or at a data storage NF using a standardized interface. The stored information may then be re-exposed to other NFs and AFs by NEF 416 and / or used for other purposes such as analysis.
[0058] NRF 420 may support a service discovery function, receive an NF discovery request from an NF instance, and provide information of the discovered NF instance to the NF instance. NRF 420 also maintains information of available NF instances and services supported by the available NF instances.
[0059] PCF 422 may provide policy rules for control plane functions to perform these functions and may also support a unified policy framework for managing network behavior. PCF 422 may also implement a front end (FE) to access subscription information related to policy decisions in the UDR of UDM 424.
[0060] The UDM 424 may process subscription-related information to support the handling of communication sessions by network entities, and may store subscription data for the UE 402. The UDM 424 may include two parts: an application FE and a user data repository (UDR). The UDM may include a UDM FE that is responsible for handling credentials, location management, subscription management, and the like. In different transactions, several different front ends may serve the same user. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing; user identity processing; access authorization; registration / mobility management; and subscription management. The UDR may interact with the PCF 422. The UDM 424 may also support SMS management, where the SMS-FE implements similar application logic discussed previously.
[0061] AF 426 can provide the influence of applications on traffic routing, access network capability exposure (NCE), and interact with the policy framework for policy control. NCE can be a mechanism that allows 5GC and AF 426 to provide information to each other via NEF 416, which can be used for edge computing implementation. In such implementations, network operators and third-party services can be hosted near the UE 402 access point of the attachment to achieve effective service delivery through reduced end-to-end delay and load on the transmission network. For edge computing implementations, 5GC can select UPF 404 near UE 402 and perform traffic steering from UPF 404 to DN 406 via the N6 interface. This can be based on UE subscription data, UE location and information provided by AF 426. In this way, AF 426 can affect UPF (re) selection and traffic routing. Based on operator deployment, when AF 426 is considered a trusted entity, the network operator can allow AF 426 to interact directly with the relevant NF.
[0062] As previously discussed, CN 410 may include SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to / from UE 402 to / from other entities, such as SMS-GMSC / IWMSC / SMS routers. SMS may also interact with AMF 412 and UDM 424 for notification procedures so that UE 402 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 424 when UE 402 is available for SMS).
[0063] System 400 may include the following service-based interfaces: Namf: a service-based interface presented by AMF; Nsmf: a service-based interface presented by SMF; Nnef: a service-based interface presented by NEF; Npcf: a service-based interface presented by PCF; Nudm: a service-based interface presented by UDM; Naf: a service-based interface presented by AF; Nnrf: a service-based interface presented by NRF; and Nausf: a service-based interface presented by AUSF.
[0064] System 400 may include the following reference points: N1: a reference point between UE and AMF; N2: a reference point between (R)AN and AMF; N3: a reference point between (R)AN and UPF; N4: a reference point between SMF and UPF; and N6: a reference point between UPF and data network. There may be more reference points and / or service-based interfaces between NF services in these NFs, however, these interfaces and reference points are omitted for clarity. For example, the NS reference point may be between PCF and AF; the N7 reference point may be between PCF and SMF; the N11 reference point may be between AMF and SMF, etc.; In one embodiment, CN 410 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 714) and AMF 412 to enable interworking between CN 410 and CN 706.
[0065] although Figure 4 Not shown, the system 400 may include multiple RAN nodes (such as (R)AN node 408), wherein the Xn interface is defined between two or more (R)AN nodes 408 (e.g., gNBs, etc.) connected to the 5GC 410, between the (R)AN node 408 (e.g., gNBs) connected to the CN 410 and an eNB, and / or between two eNBs connected to the CN 410.
[0066] In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE402 in connected mode (e.g., CM connection) includes functions for managing UE mobility in connected mode between one or more (R)AN nodes 408. The mobility support may include context transfer from an old (source) serving (R)AN node 408 to a new (target) serving (R)AN node 408; and control of a user plane tunnel between the old (source) serving (R)AN node 408 and the new (target) serving (R)AN node 408.
[0067] The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U layer for carrying user plane PDUs on top of a UDP and / or IP layer. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on an SCTP layer. The SCTP layer may be located on top of the IP layer. The SCTP layer provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.
[0068] Figure 5 Exemplary components of a device 500 according to some embodiments are shown. In some embodiments, the device 500 may include an application circuit 502, a baseband circuit 504, a radio frequency (RF) circuit (shown as RF circuit 520), a front-end module (FEM) circuit (shown as FEM circuit 530), one or more antennas 532, and a power management circuit (PMC) (shown as PMC 534) (at least coupled together as shown). The components of the illustrated device 500 may be included in a UE or a RAN node. In some embodiments, the device 500 may include fewer elements (e.g., the RAN node cannot utilize the application circuit 502, but includes a processor / controller to process IP data received from the EPC). In some embodiments, the device 500 may include additional elements, such as a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the following components may be included in more than one device (e.g., the circuit may be separately included in more than one device for a cloud-RAN (C-RAN) specific implementation).
[0069] The application circuit 502 may include one or more application processors. For example, the application circuit 502 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The one or more processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include a memory / storage device, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the device 500. In some embodiments, the processor of the application circuit 502 may process IP data packets received from the EPC.
[0070] The baseband circuit 504 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 504 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 520 and generate baseband signals for the transmit signal path of the RF circuit 520. The baseband circuit 504 may interact with the application circuit 502 to generate and process baseband signals and control the operation of the RF circuit 520. For example, in some embodiments, the baseband circuit 504 may include a third generation (3G) baseband processor (3G baseband processor 506), a fourth generation (4G) baseband processor (4G baseband processor 508), a fifth generation (5G) baseband processor (5G baseband processor 510), or other baseband processors 512 of other existing generations, generations under development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 504 (e.g., one or more of the baseband processors) may handle various radio control functions that can communicate with one or more radio networks via the RF circuit 520. In other embodiments, some or all of the functions of the illustrated baseband processor may be included in a module stored in the memory 518 and executed via the central processing unit (CPU 514). The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 504 may include a fast Fourier transform (FFT), precoding, or constellation mapping / demapping function. In some embodiments, the encoding / decoding circuit of the baseband circuit 504 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.
[0071] In some embodiments, the baseband circuit 504 may include a digital signal processor (DSP), such as one or more audio DSPs 516. The one or more audio DSPs 516 may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 504 and the application circuit 502 may be implemented together, such as on a system on a chip (SOC).
[0072] In some embodiments, the baseband circuit 504 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 504 may support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which the baseband circuit 504 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.
[0073] The RF circuit 520 may communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, the RF circuit 520 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 520 may include a receive signal path, which may include circuits for down-converting RF signals received from the FEM circuit 530 and providing baseband signals to the baseband circuit 504. The RF circuit 520 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by the baseband circuit 504 and providing an RF output signal for transmission to the FEM circuit 530.
[0074] In some embodiments, the receive signal path of the RF circuit 520 may include a mixer circuit 522, an amplifier circuit 524, and a filter circuit 526. In some embodiments, the transmit signal path of the RF circuit 520 may include a filter circuit 526 and a mixer circuit 522. The RF circuit 520 may also include a synthesizer circuit 528 for synthesizing frequencies used by the mixer circuits 522 of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 522 of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 530 based on the synthesized frequency provided by the synthesizer circuit 528. The amplifier circuit 524 may be configured to amplify the down-converted signal, and the filter circuit 526 may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 504 for further processing. In some embodiments, although this is not required, the output baseband signal may be a zero frequency baseband signal. In some embodiments, mixer circuit 522 of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.
[0075] In some embodiments, mixer circuit 522 of the transmit signal path may be configured to up-convert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 528 to generate an RF output signal for FEM circuit 530. The baseband signal may be provided by baseband circuit 504 and may be filtered by filter circuit 526.
[0076] In some embodiments, the mixer circuit 522 of the receive signal path and the mixer circuit 522 of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 522 of the receive signal path and the mixer circuit 522 of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 522 of the receive signal path and the mixer circuit 522 may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 522 of the receive signal path and the mixer circuit 522 of the transmit signal path may be configured for superheterodyne operation.
[0077] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 520 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 504 may include a digital baseband interface to communicate with the RF circuit 520.
[0078] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.
[0079] In some embodiments, synthesizer circuit 528 may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this regard, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 528 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.
[0080] Synthesizer circuit 528 may be configured to synthesize an output frequency based on a frequency input and a divider control input for use by mixer circuit 522 of RF circuit 520. In some embodiments, synthesizer circuit 528 may be a fractional-N / N+1 synthesizer.
[0081] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by baseband circuitry 504 or application circuitry 502 (such as an application processor) according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application circuitry 502.
[0082] The synthesizer circuit 528 of the RF circuit 520 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
[0083] In some embodiments, the synthesizer circuit 528 can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 520 can include an IQ / polarity converter.
[0084] The FEM circuitry 530 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 532, amplify the receive signals, and provide an amplified version of the receive signals to the RF circuitry 520 for further processing. The FEM circuitry 530 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 520 for transmission by one or more of the one or more antennas 532. In various embodiments, amplification by the transmit or receive signal path may be accomplished only in the RF circuitry 520, only in the FEM circuitry 530, or in both the RF circuitry 520 and the FEM circuitry 530.
[0085] In some embodiments, the FEM circuit 530 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 530 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 530 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 520). The transmit signal path of the FEM circuit 530 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by the RF circuit 520), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 532).
[0086] In some embodiments, PMC 534 can manage the power provided to baseband circuit 504. Specifically, PMC 534 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When device 500 is capable of being powered by a battery, for example, when device 500 is included in a UE, PMC 534 can generally be included. PMC 534 can improve power conversion efficiency while providing a desired specific implementation size and heat dissipation characteristics.
[0087] Figure 5 PMC 534 is shown coupled only to baseband circuitry 504. However, in other embodiments, PMC 534 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 502, RF circuitry 520, or FEM circuitry 530) and perform similar power management operations for these components.
[0088] In some embodiments, the PMC 534 may control or otherwise be part of various power saving mechanisms of the device 500. For example, if the device 500 is in the RRC_Connected state, where the device is still connected to the RAN node as expected to receive traffic in the near future, then after a period of inactivity, the device may enter a state known as discontinuous reception mode (DRX). During this state, the device 500 may be powered off for short time intervals, thereby saving power.
[0089] If there is no data traffic activity for an extended period of time, the device 500 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 500 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 500 cannot receive data in this state, and in order to receive data, the device must transition back to the RRC_Connected state.
[0090] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.
[0091] The processor of the application circuit 502 and the processor of the baseband circuit 504 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 504 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 502 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.
[0092] Figure 6 An exemplary interface 600 of a baseband circuit according to some embodiments is shown. As described above, Figure 5 The baseband circuit 504 may include a 3G baseband processor 506, a 4G baseband processor 508, a 5G baseband processor 510, other baseband processors 512, a CPU 514, and a memory 518 used by the processors. As shown, each of the processors may include a corresponding memory interface 602 for sending / receiving data to / from the memory 518.
[0093] The baseband circuit 504 may also include: one or more interfaces to communicate with other circuits / devices, such as a memory interface 604 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 504); an application circuit interface 606 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 504); Figure 5 RF circuit interface 608 (for example, for sending / receiving data to / from the application circuit 502); Figure 5 an interface for sending / receiving data to / from a RF circuit 520); a wireless hardware connection interface 610 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Parts (e.g. Low power consumption), components and other communication components to send / receive data); and a power management interface 612 (for example, an interface for sending / receiving power or control signals to / from PMC 534).
[0094] Figure 7 Components 700 of a core network according to some embodiments are shown. Components of CN 706 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, network function virtualization (NFV) is used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 706 may be referred to as a network slice 702 (e.g., network slice 702 is shown to include HSS 708, MME 714, and S-GW 712). A logical instance of a portion of CN 706 may be referred to as a network sub-slice 704 (e.g., network sub-slice 704 is shown to include P-GW 716 and PCRF 710).
[0095] NFV architecture and infrastructure can be used to virtualize one or more network functions onto physical resources including a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system can be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.
[0096] Figure 8 800 , a virtualized network function (VNF) manager (VNFM 806), a virtualized network function (VNF 808), an element manager (EM 810), a NFV orchestrator (NFVO 812), and a network manager (NM 814).
[0097] The VIM 802 manages resources of the NFVI 804. The NFVI 804 may include physical or virtual resources and applications (including hypervisors) for executing the system 800. The VIM 802 may utilize the NFVI 804 to manage the lifecycle of virtual resources (e.g., creation, maintenance, and teardown of virtual machines (VMs) associated with one or more physical resources), track VM instances, track performance, failures, and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.
[0098] The VNFM 806 can manage the VNF 808. The VNF 808 can be used to perform EPC components / functions. The VNFM 806 can manage the life cycle of the VNF 808 and track the performance, failures, and security of the VNF 808 in terms of virtualization. The EM 810 can track the performance, failures, and security of the VNF 808 in terms of functions. The tracking data from the VNFM 806 and the EM 810 can include, for example, performance measurement (PM) data used by the VIM 802 or the NFVI 804. Both the VNFM 806 and the EM 810 can scale up / down the number of VNFs of the system 800.
[0099] NFVO 812 may coordinate, authorize, release, and engage resources of NFVI 804 in order to provide requested services (e.g., execute EPC functions, components, or slices). NM 814 may provide an end-user functional grouping responsible for network management, which may include network elements with VNFs, non-virtualized network functions, or both (management of VNFs may occur via EM 810).
[0100] Fig. 9 is a block diagram illustrating a component 900 capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some example embodiments. Specifically, Fig. 9 A schematic diagram of hardware resources 902 is shown, which includes one or more processors 912 (or processor cores), one or more memory / storage devices 918, and one or more communication resources 920, each of which can be communicatively coupled via a bus 922. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 904 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 902.
[0101] Processor 912 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 914 and processor 916.
[0102] The memory / storage device 918 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 918 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.
[0103] The communication resources 920 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 906 or one or more databases 908 via the network 910. For example, the communication resources 920 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Parts (e.g. Low power consumption), components and other communication components.
[0104] The instructions 924 may include software, programs, applications, applets, applications, or other executable code for causing at least any one of the processors 912 to perform any one or more of the methodologies discussed herein. The instructions 924 may reside completely or partially in at least one of the processors 912 (e.g., in a cache memory of the processor), the memory / storage device 918, or any suitable combination thereof. In addition, any portion of the instructions 924 may be transmitted to the hardware resources 902 from any combination of the peripheral devices 906 or the database 908. Thus, the memory of the processor 912, the memory / storage device 918, the peripheral devices 906, and the database 908 are examples of computer-readable and machine-readable media.
[0105] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following examples section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments shown in the examples section below.
[0106] Examples
[0107] The following examples relate to additional embodiments.
[0108] Embodiment 1 is a device for a user equipment (UE) in a wireless network. The device includes a memory interface and a processor. The memory interface is used to send or receive configuration data of pre-configured uplink resources to or from the memory device. The configuration data includes a radio network temporary identifier (RNTI) for idle mode communication. The processor is used to: generate an uplink transmission using the pre-configured uplink resources in idle mode; start a retransmission timer after performing the uplink transmission using the pre-configured uplink resources in the idle mode; and monitor a physical downlink control channel (PDCCH) using the RNTI provided in the configuration data for hybrid automatic repeat request (HARQ) confirmation (ACK) or negative confirmation (NACK).
[0109] Embodiment 2 is an apparatus according to embodiment 1, wherein the processor is further configured to: in response to the retransmission timer expiring before receiving the ACK or the NACK, determine that the uplink transmission has failed and generate a retransmission in another preconfigured uplink resource.
[0110] Embodiment 3 is the apparatus of embodiment 2, wherein the processor is further configured to restart the retransmission timer after the retransmission.
[0111] Embodiment 4 is the apparatus of embodiment 1, wherein the processor is further configured to initiate a fallback to an early data transmission (EDT) or a random access procedure in response to the retransmission timer expiring before receiving the ACK or the NACK.
[0112] Embodiment 5 is an apparatus according to embodiment 1, wherein the processor is further configured to: process a retransmission grant of an uplink resource while the retransmission timer is running; and generate a retransmission using the uplink resource of the retransmission grant.
[0113] Embodiment 6 is a device according to embodiment 1, wherein the processor is further configured to: receive the NACK while the retransmission timer is running, the NACK indicating a fallback to initiate an early data transmission (EDT) or a random access process; and initiate the fallback to the EDT or the random access process in response to the NACK.
[0114] Embodiment 7 is a device according to embodiment 1, wherein the processor is further configured to: receive at least one of a success identifier (ID) and an indication of completion of a contention resolution process while the retransmission timer is running; and enter a sleep mode in response to the success ID or the indication of completion of the contention resolution process.
[0115] Embodiment 8 is the apparatus of embodiment 1, wherein the processor is further configured to process a radio resource configuration (RRC) message including an instruction to remain in the idle mode while the retransmission timer is running.
[0116] Embodiment 9 is the apparatus of embodiment 1, wherein the processor is further configured to process a radio resource configuration (RRC) message including an instruction to move from the idle mode to a connected mode while the retransmission timer is running.
[0117] Embodiment 10 is the apparatus of embodiment 1, wherein multiple HARQ processes are supported in the idle mode, and wherein the processor is further configured to initiate a different random access process for each of the multiple HARQ processes.
[0118] Embodiment 11 is a device according to embodiment 10, wherein at least one of the HARQ feedback message, the first grant of first uplink resources for new transmission, and the second grant of second uplink resources in response to the retransmission of the uplink transmission using the preconfigured uplink resources includes a HARQ process identifier (ID).
[0119] Embodiment 12 is an apparatus according to embodiment 1, wherein the processor is further configured to: when a timing advance (TA) validity timer is running, generate a message to a base station in the pre-configured uplink resource to release the pre-configured uplink resource.
[0120] Embodiment 13 is an apparatus according to embodiment 12, wherein generating the message includes generating at least one of a radio resource control (RRC) message, a medium access control (MAC) control element (CE), and layer 1 (L1) signaling in the pre-configured uplink resources.
[0121] Embodiment 14 is a non-transitory computer-readable storage medium. The computer-readable storage medium includes instructions, which, when executed by a processor of a user equipment (UE) in a wireless network, causes the processor to: store configuration data for pre-configured uplink resources, the configuration data including a radio network temporary identifier (RNTI) for idle mode communication; in idle mode, generate an uplink transmission using the pre-configured uplink resources; after performing the uplink transmission using the pre-configured uplink resources in the idle mode, start a retransmission timer; and monitor a physical downlink control channel (PDCCH) in a common search space (CSS) using the RNTI provided in the configuration data for a hybrid automatic repeat request (HARQ) acknowledgment (ACK) or negative acknowledgment (NACK).
[0122] Embodiment 15 is a computer-readable storage medium according to embodiment 14, wherein the instructions further configure the processor to: in response to the retransmission timer expiring before receiving the ACK or the NACK, determine that the uplink transmission has failed and generate a retransmission in another preconfigured uplink resource.
[0123] Embodiment 16 is the computer-readable storage medium of embodiment 15, wherein the instructions further configure the processor to restart the retransmission timer after generating the retransmission.
[0124] Embodiment 17 is a computer-readable storage medium according to embodiment 14, wherein the instructions further configure the processor to: in response to the retransmission timer expiring before receiving the ACK or the NACK, initiate a fallback to an early data transmission (EDT) or a random access process.
[0125] Embodiment 18 is a method for a base station in a wireless network. The method includes: configuring a user equipment (UE) with pre-configured uplink resources for idle mode communication and a radio network temporary identifier (RNTI); processing an uplink transmission from the UE in the pre-configured uplink resources for the idle mode communication; and generating a message for the UE using the RNTI in response to the uplink transmission.
[0126] Embodiment 19 is a method according to embodiment 18, wherein configuring the UE using the pre-configured uplink resources includes generating a radio resource control (RRC) message, the RRC message includes configuration data of the pre-configured uplink resources, and the configuration data includes the RNTI.
[0127] Embodiment 20 is a method according to embodiment 18, wherein configuring the UE using the pre-configured uplink resources includes generating a broadcast message, the broadcast message includes configuration data of the pre-configured uplink resources, and the configuration data includes the RNTI.
[0128] Embodiment 21 is a method according to embodiment 18, wherein generating the message for the UE using the RNTI includes generating a retransmission grant for uplink resources.
[0129] Embodiment 22 is a method according to embodiment 18, wherein generating the message for the UE using the RNTI includes generating a negative acknowledgement (NACK), the NACK including an indication for the UE to fall back to an early data transmission (EDT) or a random access procedure.
[0130] Embodiment 23 is a method according to embodiment 18, wherein generating the message for the UE using the RNTI includes generating at least one of a success identifier (ID) and an indication of completion of a contention resolution process to indicate that the UE enters a sleep mode.
[0131] Embodiment 24 is a method according to embodiment 18, wherein generating the message for the UE using the RNTI includes generating a radio resource configuration (RRC) message, the RRC message including instructions to keep the UE in the idle mode.
[0132] Embodiment 25 is a method according to embodiment 18, wherein generating the message for the UE using the RNTI includes generating a radio resource configuration (RRC) message, the RRC message including instructions to move the UE from the idle mode to a connected mode.
[0133] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.
[0134] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations, or may include a combination of hardware, software, and / or firmware.
[0135] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters / attributes / aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters / attributes / aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters / attributes / aspects, etc. may be combined with or substituted for parameters / attributes, etc. of another embodiment.
[0136] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Claims
1. An apparatus for a user equipment (UE) in a wireless network, the apparatus comprising: a memory interface for sending to or receiving from a memory device configuration data for pre-configuring uplink resources, the configuration data for pre-configuring uplink resources comprising a radio network temporary identifier (RNTI) for idle mode communications; and A processor, the processor being configured to: in idle mode, generating an uplink transmission using the preconfigured uplink resources; After performing the uplink transmission using the preconfigured uplink resources in the idle mode, starting a retransmission timer; as well as A physical downlink control channel (PDCCH) in a common search space (CSS) is monitored for a hybrid automatic repeat request (HARQ) acknowledgement (ACK) or negative acknowledgement (NACK) using the RNTI provided in the configuration data for idle mode communications.
2. The apparatus of claim 1, wherein the processor is further configured to: in response to the retransmission timer expiring before receiving the ACK or the NACK, determine that the uplink transmission has failed and generate a retransmission in another preconfigured uplink resource.
3. The apparatus of claim 2, wherein the processor is further configured to restart the retransmission timer after the retransmission.
4. The apparatus of claim 1, wherein the processor is further configured to initiate a fallback to an early data transmission (EDT) or a random access procedure in response to the retransmission timer expiring before receiving the ACK or the NACK.
5. The apparatus of claim 1, wherein the processor is further configured to: processing a retransmission grant of uplink resources while the retransmission timer is running; and A retransmission is generated using the uplink resources of the retransmission grant.
6. The apparatus of claim 1, wherein the processor is further configured to: receiving the NACK while the retransmission timer is running, the NACK indicating a fallback to initiate an early data transfer (EDT) or a random access procedure; and In response to the NACK, the fallback to the EDT or the random access procedure is initiated.
7. The apparatus of claim 1, wherein the processor is further configured to: receiving at least one of a success identifier (ID) and an indication of completion of a contention resolution procedure while the retransmission timer is running; and Responsive to the success ID or the indication that the contention resolution process is complete, entering a sleep mode.
8. The apparatus of claim 1, wherein the processor is further configured to process a radio resource configuration (RRC) message including an instruction to remain in the idle mode while the retransmission timer is running.
9. The apparatus of claim 1, wherein the processor is further configured to process a radio resource configuration (RRC) message including an instruction to move from the idle mode to a connected mode while the retransmission timer is running.
10. The apparatus of claim 1, wherein a plurality of HARQ processes are supported in the idle mode, and wherein the processor is further configured to initiate a different random access procedure for each of the plurality of HARQ processes.
11. The apparatus of claim 10, wherein at least one of a HARQ feedback message, a first grant of first uplink resources for a new transmission, and a second grant of second uplink resources in response to a retransmission of the uplink transmission using the preconfigured uplink resources comprises a HARQ process identifier (ID).
12. The apparatus of claim 1, wherein the processor is further configured to generate a message to a base station in the pre-configured uplink resources to release the pre-configured uplink resources when a timing advance (TA) validity timer is running.
13. The apparatus of claim 12, wherein generating the message comprises generating at least one of a radio resource control (RRC) message, a medium access control (MAC) control element (CE), and layer 1 (L1) signaling in the preconfigured uplink resources.
14. A non-transitory computer-readable storage medium comprising instructions that, when executed by a processor of a user equipment (UE) in a wireless network, cause the processor to: storing configuration data for pre-configuring uplink resources, the configuration data for pre-configuring uplink resources comprising a radio network temporary identifier (RNTI) for idle mode communications; in idle mode, generating an uplink transmission using the preconfigured uplink resources; After performing the uplink transmission using the preconfigured uplink resources in the idle mode, starting a retransmission timer; as well as A physical downlink control channel (PDCCH) in a common search space (CSS) is monitored for a hybrid automatic repeat request (HARQ) acknowledgement (ACK) or negative acknowledgement (NACK) using the RNTI provided in the configuration data for idle mode communications.
15. The computer-readable storage medium of claim 14, wherein the instructions further configure the processor to: in response to the retransmission timer expiring before receiving the ACK or the NACK, determine that the uplink transmission has failed and generate a retransmission in another preconfigured uplink resource.
16. The computer-readable storage medium of claim 15, wherein the instructions further configure the processor to restart the retransmission timer after generating the retransmission.
17. The computer-readable storage medium of claim 14, wherein the instructions further configure the processor to: in response to the retransmission timer expiring before receiving the ACK or the NACK, initiate a fallback to an early data transmission (EDT) or a random access procedure.
18. A method for a base station in a wireless network, the method comprising: configuring a user equipment (UE) with preconfigured uplink resources and a radio network temporary identifier (RNTI) for idle mode communications; processing an uplink transmission from the UE in the preconfigured uplink resources for the idle mode communication; as well as In response to the uplink transmission, a message for the UE is generated using the RNTI for idle mode communications included in the configuration data for pre-configuring uplink resources.
19. The method of claim 18, wherein configuring the UE with the pre-configured uplink resources comprises generating a radio resource control (RRC) message, the RRC message comprising the configuration data for the pre-configured uplink resources.
20. The method of claim 18, wherein configuring the UE with the pre-configured uplink resources comprises generating a broadcast message including the configuration data for the pre-configured uplink resources.
21. The method of claim 18, wherein generating the message for the UE using the RNTI comprises generating a retransmission grant of uplink resources.
22. The method of claim 18, wherein generating the message for the UE using the RNTI comprises generating a negative acknowledgement (NACK), the NACK comprising an indication for the UE to fall back to an early data transfer (EDT) or random access procedure.
23. The method of claim 18, wherein generating the message for the UE using the RNTI comprises generating at least one of a success identifier (ID) and an indication of contention resolution process completion to instruct the UE to enter a sleep mode.
24. The method of claim 18, wherein generating the message for the UE using the RNTI comprises generating a radio resource configuration (RRC) message including instructions to keep the UE in the idle mode.
25. The method of claim 18, wherein generating the message for the UE using the RNTI comprises generating a radio resource configuration (RRC) message including instructions for the UE to move from the idle mode to a connected mode.
