Determining and communicating control information in wireless telecommunications networks

Abstract

The present disclosure relates to determining and communicating control information in a wireless telecommunications network. A user equipment (UE) may receive information about a search space of a physical downlink control channel (PDCCH) via radio resource control (RRC) signaling for obtaining downlink control information (DCI) from a radio access network (RAN) node. Based on a slot format (SF) index in the DCI, the UE may determine a slot format for communicating with a RAN node and communicate with the RAN node according to the slot format. In addition, the UE may communicate UE capability information to the RAN node, which may include a maximum number of blind decoding attempts (BDA). The UE may determine a shortened channel control element (sCCE) to be used by the RAN node to transmit shortened downlink control information (sDCI) via a shortened physical downlink control channel (sPDCCH), obtain the sDCI by monitoring the sPDCCH according to the determined sCCE, and communicate with the RAN node according to the sDCI.

Description

[0001] This application is a divisional application of the invention patent application with the application date of August 9, 2018, application number 201880066120.8, and titled "Determining and Transmitting Control Information in a Wireless Telecommunications Network".

[0002] Related patent applications

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 544,505, filed on August 11, 2017, and U.S. Provisional Patent Application No. 62 / 547,380, filed on August 18, 2017, the contents of which are hereby incorporated by reference as if fully set forth herein. Background Art

[0004] A wireless telecommunications network may include a user equipment (UE) (e.g., a smartphone, tablet, laptop, etc.), a radio access network (RAN) (which typically includes one or more base stations), and a core network. The UE may connect to the core network by communicating with the RAN and registering with the core network. Communication between the UE and the RAN may be performed through one or more wireless channels.

[0005] In some cases, the wireless telecommunications network may provide control channel information to the UE. Generally speaking, such information may inform the UE how the network will transmit information to the UE and / or how each UE may transmit information to the network. Some of this information may be provided to the UE via a physical downlink control channel (PDCCH) and information corresponding thereto, such as downlink control information (DCI). BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The embodiments described herein will be more easily understood through the following detailed description in conjunction with the accompanying drawings. To facilitate this description, similar reference numerals may designate similar structural elements.

[0007] Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings.

[0008] Figure 1 illustrates the architecture of a system of networks according to some embodiments;

[0009] Figure 2 is a flow chart of an exemplary process for determining slot format information (SFI) and communicating with a radio access network (RAN) node based on the SFI;

[0010] Figure 3 is a flow chart of an exemplary process for determining an SFI based on an SFI index;

[0011] Figure 4is a flow chart of an exemplary process for determining a timeslot format for multiple cells and / or component carriers (CCs);

[0012] Figure 5 is a flow chart of another exemplary process for determining a timeslot format for multiple cells and / or CCs;

[0013] Figure 6 is a flow chart of an exemplary process for determining a slot format for CCs and / or bandwidth parts (BWPs) having different subcarrier spacings (SCSs);

[0014] Figure 7 is a sequence flow diagram of an exemplary process for providing downlink control information (DCI) via a shortened channel control entity (sCCE);

[0015] Figure 8-Figure 10 is a diagram of an exemplary shortened resource element group (sREG) according to one or more embodiments described herein;

[0016] Fig.11 is a diagram of an exemplary subframe for transmitting sDCI via a legacy PDCCH according to some embodiments.

[0017] Fig.12 is a schematic diagram of an example for dynamic resource sharing of a shortened physical downlink control channel (sPDCCH) resource block (RB) set;

[0018] Fig.13 is a block diagram of exemplary components of an apparatus according to some embodiments;

[0019] Fig.14 is a block diagram of an exemplary interface of a baseband circuit according to some embodiments;

[0020] Fig.15 is a block diagram of an exemplary control plane protocol stack according to some embodiments;

[0021] Fig.16 is a block diagram of an exemplary user plane protocol stack according to some embodiments;

[0022] Fig.17 illustrates components of a core network according to some embodiments;

[0023] Fig.18 is a block diagram illustrating components of a system for supporting network function virtualization (NFV) according to some exemplary embodiments; and

[0024] Fig.19is a block diagram of exemplary components 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 methodologies discussed herein, according to some exemplary embodiments. DETAILED DESCRIPTION

[0025] The following detailed description refers to the accompanying drawings. The same figure numbers in different drawings can identify the same or similar elements. It should be understood that other embodiments can be used and structural or logical changes can be made without departing from the scope of the present disclosure. Therefore, the following detailed description should not be understood as limiting, and the scope of the embodiments is limited only by the attached claims and their equivalents.

[0026] Telecommunication technology may involve a radio access network (RAN) node delivering control information to a user equipment (UE) via a physical downlink control channel (PDCCH). The control information may include a variety of information, including information about how and when the RAN node and the UE communicate with each other (e.g., scheduling information, format information, etc.). In some cases, new radio (NR) technology may enable a RAN node to use a specific type of PDCCH (referred to as a group common PDCCH (GC-PDCCH)) to deliver control information to one or more UEs in a cell. In some cases, the GC-PDCCH may be a specific example of a PDCCH that carries a specific downlink control information (DCI) format. The RAN node may use the GC-PDCCH to transmit slot format information (or slot format indicator) (SFI), which may indicate or be used by the UE to derive the number of symbols in a slot, and how the symbols within the slot are allocated (e.g., which symbols are used for downlink (DL) communications, which symbols are used for uplink (UL) communications, and which symbols have not yet been allocated for DL ​​or UL communications). The SFI may be delivered to the UE as downlink control information (DCI). For example, to convey the SFI to the UE, the RAN node may select a DCI format having one or more fields that are assigned, allocated, etc. for conveying the SFI (also referred to as an "SFI field"). The RAN node may populate the SFI field with the SFI and transmit the DCI to the UE via the GC-PDCCH.

[0027] The techniques described herein may enable a RAN node to provide an SFI to a UE using a PDCCH (or GC-PDCCH). For example, a UE may communicate with a RAN node to complete a physical random access channel (PRACH) procedure. The RAN node may provide a UE-specific PDCCH control resource set (CORESET) (or another type of SFI monitoring configuration) to the UE using UE-specific radio resource control (RRC) signaling, which may include information for monitoring the PDCCH and obtaining the SFI from the PDCCH (e.g., time domain and frequency domain information, control channel element (CCE) and resource element group (REG) mapping information, etc.). In other words, as described herein, the SFI monitoring configuration may include one or more PDCCH candidates (e.g., portions of a PDCCH), and the UE may monitor the SFI intended for the UE for the one or more PDCCH candidates.

[0028] As described above, the UE may use the SFI to determine the number of symbols in one or more time slots, and how each time slot is formatted (e.g., which symbols in the one or more time slots are allocated for downlink (DL) communications, which symbols are allocated for uplink (UL) communications, and which symbols are not yet allocated for DL ​​or UL communications). In addition, after determining the SFI, the UE may continue to communicate with the RAN node based on the SFI, which may include receiving DL information from the RAN node, transmitting UL information to the RAN node, etc.

[0029] In some cases, one or more techniques may be used to reduce the overhead that may otherwise be involved in a RAN node providing an SFI to a UE. In some embodiments, instead of providing format information for each time slot individually (e.g., whether symbols within each time slot are allocated for UL, DL, and which symbols within each time slot are allocated for UL and which symbols are allocated for DL), the RAN node may use higher layer signaling (e.g., UE-specific RRC signaling) to indicate that the time slot format indicated in one SFI field (of a DCI format) may correspond to multiple time slots (e.g., time slots that fall within the indicated duration). In this way, the RAN node may reduce the total number of SFI fields used to transmit the SFI. In some embodiments, the UE may receive an SFI index (e.g., a set of different SFIs each associated with an index value), the RAN node may provide the SFI as an SFI index value in the SFI field of the DCI format, and the UE may determine the time slot format to use when communicating with the RAN node by matching the SFI index value and the SFI index.

[0030] In some embodiments, there may be multiple component carriers (CCs) (e.g., carrier aggregation (CA) scenarios) or bandwidth parts (BWPs) allocated for communication between a UE and a RAN node. In such scenarios, the RAN node may use UE-specific higher layer signaling (e.g., UE-specific RRC signaling) to provide the UE with an appropriate CORESET (or another type of SFI monitoring configuration) for each CC or BWP. Based on the CORESET, the UE may monitor one or more GC-PDCCHs and obtain the SFI for each CC or BWP established between the UE and the RAN node, and continue to communicate with the RAN node based on the SFI for each CC or BWP. Additionally or alternatively, the RAN node may transmit a common CORESET for each UE associated with a particular CC or BWP, and use UE-specific RRC signaling to cause each UE receiving the common CORESET to modify the CORESET in a UE-specific manner, the result of which may include each UE having a UE-specific CORESET despite initially receiving the common CORESET. The UE may then use the UE-specific CORESET to obtain the SFI from the PDCCH (or GC-PDCCH).

[0031] Figure 1 The architecture of a system 100 of a network according to some embodiments is shown. System 100 is shown to include UE 101 and UE 102. UE 101 and UE 102 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but these UEs can also include any mobile or non-mobile computing devices, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handheld terminals, or any computing device that includes a wireless communication interface.

[0032] In some embodiments, any one of UE 101 and UE 102 may include an Internet of Things (loT) UE or a narrowband (NB-loT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as machine-to-machine (M2M), machine-type communication (MTC), enhanced MTC, and exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communication, a sensor network, or an IoT network. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0033] UE 101 and UE 102 may be configured to connect, e.g., be communicatively coupled, to a radio access network (RAN) 110—RAN 110 may be, e.g., an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NGRAN), or some other type of RAN. UE 101 and UE 102 utilize connection 103 and connection 104, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connection 103 and connection 104 are shown as air interfaces to achieve communicatively coupling, and may be consistent with a cellular communication protocol, such as a global system for mobile communications (GSM) protocol, a code division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, a cellular PTT protocol (POC), a universal mobile telecommunications system (UMTS) protocol, a 3GPP long term evolution (LTE) protocol, a fifth generation (5G) protocol, a new radio (NR) protocol, etc.

[0034] In this embodiment, UE 101 and UE 102 may also directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0035] UE 102 is shown as being configured to access access point (AP) 106 via connection 107. Connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 106 would include wireless fidelity. In this example, AP 106 is shown connected to the Internet and not to the core network of the wireless system (described in further detail below).

[0036] The RAN 110 may include one or more access nodes that enable connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BSs), Node Bs, eNBs, next generation Node Bs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). The RAN 110 may include one or more RAN nodes (e.g., macro RAN nodes 111) for providing macro cells, and one or more RAN nodes (e.g., low power (LP) RAN nodes 112) for providing femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells).

[0037] Either of the RAN node 111 and the RAN node 112 may terminate the air interface protocol and may be the first point of contact for the UE 101 and the UE 102. In some embodiments, either of the RAN nodes 111 and 112 may fulfill various logical functions of the RAN 110, including, but not limited to, functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management, data packet scheduling, and mobility management.

[0038] According to some embodiments, UE 101 and UE 102 may be configured to communicate with each other or with any of RAN nodes 111 and 112 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0039] In some embodiments, a downlink resource grid may be used for downlink transmissions from either of RAN node 111 and RAN node 112 to UE 101 and UE 102, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements. In the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0040] The physical downlink shared channel (PDSCH) may convey user data and higher layer signaling to UE 101 and UE 102. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocation related to the PDSCH channel. It may also inform UE 101 and UE 102 of the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 102 within a cell) may be performed at either RAN node 111 or RAN node 112 based on channel quality information fed back from either UE 101 or UE 102. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of UE 101 and UE 102.

[0041] The PDCCH may use control channel elements (CCEs) to convey control information. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to six sets of 12 physical resource elements.

[0042] (Each REG includes three resource elements for the PDCCH demodulation reference signal (DMRS)), called a resource element group (REG). Nine quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the downlink control information (DCI) and the channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be different PDCCH transmissions defined in NR with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, 8, or 16).

[0043] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. One or more enhanced control channel elements (ECCEs) may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to four sets of nine physical resource elements, referred to as enhanced resource element groups (EREGs). In some cases, ECCEs may have other numbers of EREGs.

[0044] RAN 110 is shown as being communicatively coupled to a core network (CN) 120 via an S1 interface 113. In an embodiment, CN 120 may be an evolved packet core (EPC) network, a next generation packet core (NPC) network, or some other type of CN. In this embodiment, S1 interface 113 is divided into two parts: S1-U interface 114, which carries traffic data between RAN nodes 111 and 112 and a serving gateway (S-GW) 122; and S1-Mobility Management Entity (MME) interface 115, which is a signaling interface between RAN nodes 111 and 112 and MME 121.

[0045] In this embodiment, CN 120 includes MME 121, S-GW 122, Packet Data Network (PDN) Gateway (P-GW) 123 and Home Subscriber Server (HSS) 124. MME 121 can be similar in function to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME 121 can manage mobility aspects in access, such as gateway selection and tracking area list management. HSS 124 can include a database for network users, which includes subscription-related information to support network entities in handling communication sessions. Depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc., CN 120 may include one or more HSS 124. For example, HSS 124 can provide support for routing / roaming authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0046] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies.

[0047] The P-GW 123 may terminate the SGi interface towards the PDN. The P-GW 123 may route data packets between the EPC network 123 and an external network such as a network including an application server 130 (alternatively referred to as an application function (AF)) via an Internet Protocol (IP) interface 125. Generally speaking, the application server 130 may be an element that provides an application that uses IP bearer resources with a core network (e.g., a UMTS packet service (PS) domain, a LTE PS data service, etc.). In this embodiment, the P-GW 123 is shown as being communicatively coupled to the application server 130 via an IP communication interface 125. The application server 130 may also be configured to support one or more communication services (e.g., voice over Internet protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 101 and UE 102 via the CN 120.

[0048] The P-GW 123 may also be a node for policy enforcement and charging data collection. The Policy and Charging Enforcement Function (PCRF) 126 is a policy and charging control element of the CN 120. In a non-roaming scenario, there may be a single PCRF in a domestic public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of the UE. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the UE's IP-CAN session: a domestic PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in a visited public land mobile network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 130 via the P-GW 123. The application server 130 may signal the PCRF 126 to indicate a new service flow and select appropriate quality of service (QoS) and charging parameters. PCRF 126 may provide the rules to a Policy and Charging Enforcement Function (PCEF) (not shown) using the appropriate Traffic Flow Template (TFT) and QoS Class of Identifier (QCI), as specified by application server 130, which initiates QoS and charging.

[0049] Provided for illustration purposes only Figure 1 The number of devices and / or networks shown is not limited to the number of devices and / or networks shown. In practice, system 100 may include additional devices and / or networks; fewer devices and / or networks; different devices and / or networks; or Figure 1Devices and / or networks arranged differently as shown. For example, although not shown, environment 100 may include devices that facilitate or enable communication between the various components shown in environment 100, such as routers, modems, gateways, switches, hubs, etc. Alternatively or additionally, one or more of the devices of system 100 may perform one or more functions described as being performed by another one or more of the devices of system 100. In addition, the devices of system 100 may be interconnected to each other and / or to other devices via wired connections, wireless connections, or a combination of wired connections and wireless connections. In some embodiments, one or more devices of system 100 may be physically integrated into one or more other devices of system 100 and / or may be physically attached to the one or more other devices. In addition, although Figure 1 Some of the devices in the drawings may be shown as being connected “directly” to each other, but in practice, some of the devices may communicate with each other via one or more additional devices and / or networks.

[0050] Figure 2 1 is a flow chart of an exemplary process 200 for determining an SFI and communicating with a RAN node 111 based on the SFI. Process 200 may be implemented by UE 101. In some embodiments, Figure 2 One or more of the operations described in the above may be performed in whole or in part by another device such as the one described above. Figure 1 In addition, Figure 2 The examples are provided as non-limiting examples. In practice, Figure 2 Examples may include fewer, additional, and / or alternative operations and / or functionality.

[0051] As shown, process 200 may include obtaining an SFI monitoring configuration via UE-specific RRC signaling (block 210). For example, UE 101 may communicate with RAN node 111 to perform a PRACH procedure. As part of or after the PRACH procedure, RAN node 111 may provide UE 101 with a UE-specific SFI monitoring configuration (described below) using UE-specific RRC signaling, which may indicate a set of PDCCH candidates (e.g., GC-PDCCH) using a particular aggregation level (AL) and a portion thereof to be used by RAN node 111 to transmit SFI to UE 101. As described herein, SFI monitoring configuration may include receiving and / or implementing CORESET information in whole or in part.

[0052] The process 200 may also include monitoring the PDCCH for the SFI based on the SFI monitoring configuration (block 220). For example, the SFI monitoring configuration obtained by the UE 101 may include a CORESET, which may include information (e.g., time domain and frequency domain information, control channel element (CCE) and resource element group (REG) mapping information, etc.), and a search space configuration, which may include information for monitoring the GC-PDCCH and obtaining the SFI from the GC-PDCCH (e.g., specific PDCCH candidates at certain indicated ALs). Thus, the UE 101 may use the SFI monitoring configuration to determine, identify, monitor, etc., the PDCCH used by the RAN node 111 and / or obtain the SFI intended for the UE 101 from the PDCCH.

[0053] Process 200 may also include determining a slot format for communicating with RAN node 111 based on the SFI (block 230). For example, based on the SFI, UE 101 may determine which symbols (e.g., in a slot) are allocated for DL ​​transmissions, UL transmissions, and / or symbols that have not been allocated for either type of transmission (which may also be referred to as other symbols, open symbols, flexible symbols, unknown symbols, etc.). Thus, UE 101 may use the SFI to determine a slot format for communicating with RAN node 111.

[0054] Process 200 may also include communicating with RAN node 111 according to the time slot format (block 240). For example, after determining the time slot format based on the SFI from RAN node 111, UE 101 may continue to communicate with RAN node 111 according to the time slot format.

[0055] Although the above Figure 2A general example of a process that may be performed by a UE 101 to determine an SFI and communicate with a RAN node 111 is provided. The exemplary process 200 may be performed in one or more of a variety of ways. For example, to transmit the SFI to the UE 101, the RAN node 111 may select a DCI format that includes one or more SFI fields and may include the SFI in the SFI field of the DCI format. In such an embodiment, the SFI monitoring configuration information previously obtained by the UE 101 may include information for monitoring a PDCCH (e.g., a GC-PDCCH) of the DCI format. Additionally or alternatively, the RAN node 111 may use UE-specific RRC signaling to indicate to the UE 101 the number of time slots corresponding to the SFI indicated in the one or more SFI fields of the DCI transmitted to the UE 101. For example, the SFI field may indicate a specific time slot format (e.g., a specific combination of DL, UL, or flexible symbols used for a time slot), and the RAN node 111 may use RRC signaling to indicate to the UE 101 the time slots corresponding to the specific time slot format (e.g., the number of consecutive time slots), thereby reducing the transmission overhead between the UE 101 and the RAN node 111.

[0056] In some embodiments, multiple CCs and / or BWPs may be established between the UE 101 and the RAN node 111. In such a scenario, the UE 101 may obtain an SFI monitoring configuration (e.g., CORESET) for each CC or BWP. In some embodiments, the UE 101 may obtain an SFI set for each CC or BWP. In other embodiments, one or more CCs or BWPs may correspond to the same SFI. Therefore, the RAN node 111 may use UE-specific RRC signaling to indicate to the UE 101 which CCs or BWPs use the same timeslot format, so that the UE 101 may obtain one instance of the SFI from the GC-PDCCH, but apply the SFI to multiple CCs or BWPs, thereby reducing the transmission overhead between the UE 101 and the RAN node 111.

[0057] In some embodiments, the UE 101 and the RAN node 111 may implement an indexing system for communicating the SFI. For example, the RAN node 111 may use UE-specific RRC signaling to provide the UE 101 with indices of different slot formats (and / or another type of data structure). Thus, instead of transmitting an SFI that fully describes the slot format, the RAN node 111 may instead provide an index value or another type of identifier (e.g., in an SFI field of a particular DCI format) that corresponds to the slot format of the index provided to the UE 101, and the UE 101 may use the index value from the DCI to determine the slot format to be used for communication with the RAN node 111. In scenarios involving multiple CCs or BWPs, the RAN node 111 may provide an index value for each CC or BWP, and / or information that enables the UE 101 to determine which index value maps to which CC or BWP. Additionally, where two or more CCs or BWPs may use the same slot format, the RAN node 111 may transmit a single index value and an indication of which CCs or BWPs correspond to the slot formats of the index value.

[0058] Figure 3 is a flow chart of an exemplary process 300 for determining an SFI based on an SFI index. Process 300 may be implemented by UE 101. In some embodiments, Figure 3 One or more of the operations described in the above may be performed in whole or in part by another device such as the one described above. Figure 1 In addition, Figure 3 The examples are provided as non-limiting examples. In addition, Figure 3 The examples are provided as non-limiting examples. In practice, Figure 3 Examples may include fewer, additional, and / or alternative operations and / or functionality.

[0059] As shown, process 300 may include obtaining an SFI monitoring configuration via UE-specific RRC signaling (block 310). For example, UE 101 may communicate with RAN node 111 to perform a PRACH procedure. As part of or after the PRACH procedure, RAN node 111 may provide UE 101 with an SFI monitoring configuration (described below) using UE-specific RRC signaling, which may indicate a set of PDCCH (e.g., GC-PDCCH) candidates using a particular aggregation level (AL) and a portion thereof to be used by RAN node 111 to deliver SFI to UE 101.

[0060] Process 300 may include obtaining SFI indexes corresponding to different slot formats via UE-specific RRC signaling (block 320). As described herein, the SFI index may include a list, table, array, or another type of data structure that includes one or more slot formats that are each associated with a different identifier (e.g., index value). For example, each slot format may include candidate or template slot formats (also referred to as "candidate slot formats" or "slot format candidates") for a plurality of slots. The number of slots (and / or portions of the PDCCH and / or GC-PDCCH) to which the candidate slot formats may be associated may be configured via higher layer signaling such as RRC signaling.

[0061] Process 300 may include receiving an SFI index from a PDCCH based on an SFI monitoring configuration (block 330). For example, UE 101 may monitor a GC-PDCCH used by RAN node 111 to convey control information. Additionally, based on the SFI monitoring configuration obtained from RAN node 111, UE 101 may determine an SFI in a GC-PDCCH of UE 101. In some embodiments, the SFI may include an SFI index. For example, the SFI may include a DCI format having one or more fields (e.g., one or more SFI fields) that include one or more SFI indexes. Thus, the SFI index may be provided as a specific field (SFI field) of a DCI format used by RAN node 111 to provide control information to UE 111.

[0062] Process 300 may include determining a slot format by mapping one or more SFI indexes to an SFI (block 340). For example, UE 101 may compare an SFI index obtained from a GC-PDCCH with an SFI index received via UE-specific RRC signaling. Additionally, when an SFI index obtained from a GC-PDCCH matches one of the SFI indexes received via UE-specific RRC signaling, UE 101 may determine a slot format based on which of the SFI indexes matches the SFI index obtained from the GC-PDCCH. In some embodiments, UE 101 may obtain multiple SFI indexes, which may be provided, for example, in a sequence-specific order. In such embodiments, the slot format determined by UE 101 may be a combination or sequence of slot formats (of SFI indexes) consistent with the sequence-specific SFI indexes obtained from the GC-PDCCH.

[0063] Process 300 may also include communicating with RAN node 111 according to the time slot format (block 350). For example, after determining the time slot format based on the SFI from RAN node 111, UE 101 may continue to communicate with RAN node 111 according to the time slot format.

[0064] Figure 44 is a flow chart of an exemplary process 400 for determining a time slot format for multiple cells and / or component carriers (CCs). Process 400 may be implemented by UE 101. In some embodiments, Figure 4 One or more of the operations described in the above may be performed in whole or in part by another device such as the one described above. Figure 1 In addition, Figure 4 The examples are provided as non-limiting examples. In practice, Figure 4 Examples may include fewer, additional, and / or alternative operations and / or functionality.

[0065] As shown, process 400 may include obtaining an SFI monitoring configuration via UE-specific RRC signaling (block 410). For example, UE 101 may communicate with RAN node 111 to perform a PRACH procedure. As part of or after the PRACH procedure, RAN node 111 may provide UE 101 with an SFI monitoring configuration (described below) using UE-specific RRC signaling, which may indicate a PDCCH (e.g., GC-PDCCH) and / or a portion thereof to be used by RAN node 111 to transmit an SFI to UE 101.

[0066] Process 400 may also include determining multiple cells and / or CCs associated with the SFI monitoring configuration via UE-specific RRC signaling (420). For example, the wireless telecommunications network may support carrier aggregation (CA), which may include a network that communicates with UE 101 via multiple cells and / or CCs. In some scenarios, two or more cells and / or CCs may use the same time slot format to communicate with UE 101. Therefore, RAN node 111 may use UE-specific RRC signaling to provide UE 101 with information indicating which cells and / or CCs may use the same time slot format. As described below, providing such information to UE 101 may enable UE 101 to determine the time slot formats of multiple cells and / or CCs based on a single time slot format (e.g., a single instance of SFI from RAN node 111). In some embodiments, the information received from RAN node 111 may include a time slot format and an indication of the cell and / or CC corresponding to (e.g., implementing) each time slot format.

[0067] Process 400 may include obtaining an SFI from a PDCCH based on an SFI monitoring configuration (block 430). For example, UE 101 may use the SFI monitoring configuration to determine which PDCCH and / or portion thereof (e.g., GC-PDCCH) the RAN node 111 may use to transmit an SFI to UE 101. Thus, UE 101 may monitor and receive an SFI from the indicated PDCCH.

[0068] Process 400 may include determining a slot format for multiple cells and / or CCs by mapping an SFI to a CC and / or cell (block 440). For example, UE 101 may determine the slot format indicated by the SFI from RAN node 111 via GC-PDCCH, and map the slot format to previously received information about which cells and / or CCs use each slot format via UE-specific RRC signaling. Upon determining a match between the SFI from the GC-PDCCH and the slot format from the UE-specific RRC signaling, UE 101 may determine each cell and / or CC to which the SFI belongs. In some embodiments, each cell and / or CC may implement a different slot format. In some embodiments, multiple cells and / or CCs may implement the same slot format.

[0069] Process 400 may also include communicating with the RAN according to the slot format (block 450). For example, after determining the slot formats of cells and / or CCs involved in the CA scenario between UE 101 and the RAN, UE 101 may continue to communicate with the RAN according to the slot format.

[0070] Figure 5 is a flow chart of an exemplary process 500 for determining a timeslot format for multiple cells and / or CCs. Process 500 may be implemented by UE 101. In some embodiments, Figure 5 One or more of the operations described in the above may be performed in whole or in part by another device such as the one described above. Figure 1 In addition, Figure 5 The examples are provided as non-limiting examples. In practice, Figure 5 Examples may include fewer, additional, and / or alternative operations and / or functionality.

[0071] As shown, process 500 may include obtaining an SFI monitoring configuration via UE-specific RRC signaling (block 510). As described herein, UE 101 may communicate with RAN node 111 to perform a PRACH procedure. As part of or after the PRACH procedure, RAN node 111 may provide UE 101 with an SFI monitoring configuration (described below) using UE-specific RRC signaling, which may indicate a set of PDCCH (e.g., GC-PDCCH) candidates using a particular aggregation level (AL) and / or a portion thereof to be used by RAN node 111 to deliver SFI to UE 101.

[0072] Process 500 may include obtaining an SFI from a PDCCH based on an SFI monitoring configuration (block 520). For example, UE 101 may use the SFI monitoring configuration to determine which PDCCH and / or portion thereof may be used by RAN node 111 to transmit an SFI to UE 101. UE 101 may monitor and receive the SFI from the indicated PDCCH. Additionally or alternatively, the SFI may indicate how symbols in a time slot are formatted for UL transmission, DL transmission, and / or symbols that have not been designated for UL transmission or DL ​​transmission. Additionally or alternatively, the SFI may also include other types of information, such as a time slot format identifier or index (which may be mapped to a specific time slot format). RAN node 111 may provide the SFI in a field of DCI information (e.g., as an SFI field of a specific DCI format). In some embodiments, as described herein, some or all of the SFI provided by RAN node 111 may be provided in additional or alternative forms, such as different types of DCI information, different fields of a specific DCI format, etc.

[0073] The process 500 may also include determining, via UE-specific RRC signaling, the time slots to which the SFI applies (block 530). For example, while the SFI may indicate a format for one or more time slots, the RAN node 111 may use RRC signaling to indicate to the UE 101 the time slots to which the SFI applies, which may include multiple or a series of consecutive time slots. Thus, the UE 101 may use the SFI to determine a specific time slot format (e.g., a specific combination of DL, UL, or flexible symbols for one or more time slots being transmitted by the RAN node 111), and the UE 101 may rely on the UE-specific RRC signaling to determine the specific time slots to which the SFI applies. In this way, the RAN node 111 may, for example, not transmit an SFI for every time slot. Instead, the RAN node 111 may use RRC signaling to indicate the time slots and / or the number of time slot formats of that type to which the time slot format applies, and then may transmit a type of time slot format via the PDCCH.

[0074] The process 500 may also include determining, via UE-specific RRC signaling, the cells and / or CCs to which the SFI applies (block 540). As described above, the UE 101 may operate in a CA scenario that may involve multiple cells and / or CCs, and some of the cells and / or CCs may use the same slot format. Therefore, the RAN node 111 may use RRC signaling to inform the UE 101 which cells and / or CCs are using the same slot format, such that, for example, the RAN node 111 does not transmit the same or similar SFI (e.g., redundant SFI) to the UE 101.

[0075] Process 500 may also include communicating with the RAN according to the provided timeslot format (block 550). For example, based on the SFI obtained from the GC-PDCCH and information received from UE-specific RRC signaling about timeslots, cells, and / or CCs to which the SFI is applicable, UE 101 may determine a timeslot format for communicating with the RAN, which may include multiple cells and / or CCs. Thus, UE 101 may continue to send and receive information from the RAN according to the timeslot format determined by UE 101.

[0076] Figure 6 6 is a flow chart of an exemplary process 600 for determining a slot format for CCs and / or BWPs with different subcarrier spacings (SCSs). Process 600 may be implemented by UE 101. In some embodiments, Figure 6 One or more of the operations described in the above may be performed in whole or in part by another device such as the one described above. Figure 1 In addition, Figure 6 The examples are provided as non-limiting examples. In practice, Figure 6 Examples may include fewer, additional, and / or alternative operations and / or functionality.

[0077] As shown, process 600 may include obtaining an SFI monitoring configuration via UE-specific RRC signaling (block 610). As described herein, UE 101 may communicate with RAN node 111 to perform a PRACH procedure. As part of or after the PRACH procedure, RAN node 111 may provide UE 101 with an SFI monitoring configuration (described below) using UE-specific RRC signaling, which may indicate a PDCCH and / or a portion thereof (e.g., GC-PDCCH) to be used by RAN node 111 to deliver SFI to UE 101.

[0078] Process 600 may include obtaining an SFI from a PDCCH based on an SFI monitoring configuration (block 620). For example, UE 101 may use the SFI monitoring configuration to determine which PDCCH and / or portion thereof may be used by RAN node 111 to transmit an SFI to UE 101. UE 101 may monitor and receive the SFI from the indicated PDCCH. Additionally or alternatively, the SFI may indicate the manner in which symbols in a time slot are formatted for UL transmission, DL transmission, and / or symbols that have not yet been designated for UL transmission or DL ​​transmission. Additionally or alternatively, the SFI may also include other types of information, such as a time slot format identifier or index (which may be mapped to a specific time slot format that has been previously provided to UE 101 by RAN node 111 via RRC signaling). RAN node 111 may provide the SFI in a field of the DCI (e.g., as an SFI field of a specific DCI format). In some embodiments, as described herein, some or all of the SFI provided by RAN node 111 may be provided in additional or alternative forms, such as different types of DCI, different fields of a specific DCI format, etc.

[0079] The process 600 may also include determining a slot format of a CC and / or BWP in a plurality of CCs and / or BWPs of the UE 101 based on the SFI and the UE-specific RRC signaling (block 630). For example, because the UE 101 may be configured to communicate with the network using a plurality of CCs and / or BWPs, the UE 101 may also be configured to determine a slot format for each CC and / or BWP. Thus, the UE 101 may use one or more of the techniques described herein to determine a slot format based on the SFI and the UE-specific RRC signaling from the RAN node 111, examples of which may include receiving explicit format information for each individual slot, mapping a slot format value (e.g., an index value of an SFI field) to an index of a template slot format, applying a type of slot format (e.g., a particular combination of DL, UL, or flexible symbols for a slot) to a plurality or a series of consecutive slots, and the like.

[0080] Process 600 may include adapting the determined slot format to CCs and / or BWPs having different SCSs (block 640). As described above, UE 101 may determine the slot format of a CC and / or BWP based on the SFI and UE-specific RRC signaling from RAN node 111. Although in some embodiments, RAN node 111 may provide an SFI and UE-specific RRC signaling for each CC and / or BWP assigned to UE 101 so that UE 101 may determine the slot format of each CC and / or BWP based on the SFI and UE-specific RRC signaling from RAN node 111, in some embodiments, UE 101 may determine the slot format of a CC and / or BWP based on the determined slot format of another CC and / or BWP.

[0081] The manner in which the UE 101 may adapt the determined slot format may be based on the SCS of the CC and / or BWP. For example, assume that the UE 101 has a BWP with an SCS of 15 kHz and a BWP with an SCS of 60 kHz, and the UE 101 has determined a slot format for the BWP with an SCS of 15 kHz, but has not determined a slot format for the BWP with an SCS of 60 kHz. In such a scenario, the UE 101 may determine that each slot of the BWP with an SCS of 15 kHz (and a corresponding slot format or symbol type (e.g., UL, DL, or other)) may be mapped or otherwise correspond to four slots of the BWP with an SCS of 60 kHz, because the ratio of 60 kHz to 15 kHz is 4 to 1. Therefore, the UE 101 may determine the slot formats of multiple CCs and / or BWPs by scaling the slot format of one CC and / or BWP to another CC and / or BWP based on the relative sizes of the SCSs of the CCs and / or BWPs.

[0082] Process 600 may also include communicating with the RAN according to the time slot format of the BWP and / or CC (block 650). For example, after determining the time slot format of the BWP and / or CC that UE 101 is to use to communicate with the RAN, UE 101 may continue by receiving information according to the time slot format and / or transmitting information to the RAN.

[0083] In addition to the above examples, a limited number of bits (e.g., 2 to 4 bits) of the SFI for a single CC or BWP may be used to indicate the total space of possible slot formats (e.g., 3 for 7-symbol slots and 14-symbol slots, respectively). 7 or 3 14 ) via higher layers (e.g., UE-specific RRC signaling). The candidate sets of slot formats may be configured separately for 7-symbol slots and 14-symbol slots.

[0084] In addition, for GC-PDCCH carrying SFI of cell and / or CC, UE 101 may be configured with CORESET. In some embodiments, for multiple UEs 101 monitoring GC-PDCCH, the CORESET may be a common CORESET type (e.g., the configuration of the CORESET may not be UE-specific). In another embodiment, instead of a single common CORESET for multiple UEs 101, multiple instances of GC-PDCCH may be transmitted by the RAN node 101 within a CC or BWP according to different UE-specific or common CORESETs, and corresponding CORESETs may be configured to different UEs 101 using UE-specific or UE group-specific higher layer signaling to monitor GC-PDCCH with SFI.

[0085] In addition, the SFI may be indicated for multiple time slots, where the number of time slots is indicated via the GC-PDCCH. For example, 2 bits may be used to indicate the number of time slots to which the SFI applies. In another embodiment of this example, 2 bits in the GC PDCCH may be used to indicate one of four values ​​for the number of time slots to which the SFI is applicable, where the four values ​​are configured via higher layers (e.g., via NR Minimum System Information (MSI), NR Remaining Minimum System Information (RMSI), NR System Information Block (SIB), or UE-specific Radio Resource Control (RRC) signaling). In some embodiments, the SFI for multiple time slots may not include the slot format of some reserved time slots (e.g., time slots used to transmit synchronization signal (SS) blocks, physical random access channels (PRACH), etc.). In another example, M bits may be used in the GC-PDCCH to indicate 2 of the number of time slots as described above. M -1 value, and one code point may be used to indicate that the number of time slots for the SFI is equal to the monitoring periodicity of the GC-PDCCH carrying the SFI. For the latter case, this may mean that the indicated SFI applies to all time slots within two consecutive monitoring instances of the GC-PDCCH carrying the SFI.

[0086] The additional techniques described herein enable effectively shortened PDCCH (sPDCCH) transmissions, thereby utilizing the availability of multiple transmit and / or receive antennas of UE and / or RAN nodes. The 3GPP LTE communication standard introduces shorter or shortened transmission time intervals (sTTIs) (also known as micro-time slots) to a certain extent to better meet services and devices with high latency requirements (e.g., services and devices that may be affected by latency). sTTI can be achieved by dividing a 1 millisecond (ms) subframe into multiple TTIs, or in other words, by specifying a TTI with a duration shorter than a subframe (e.g., 1ms). For example, by dividing a subframe into 6 sTTIs, sTTI can be achieved using a 1ms subframe of 14 symbols, where 4 of the sTTIs are 2 symbols each, and 2 of the sTTIs are 3 symbols each (a total of 14 symbols). Although the use of sTTIs can increase the ability of the RAN to meet services and devices with high latency requirements, it can also increase the time, resources, and complexity involved in the UE attempting to decode the PDCCH via blind decoding (BD).

[0087] The techniques described herein enable the use of sTTI in the PDCCH while minimizing the time, resources, and complexity required to do so. The sPDCCH may include a PDCCH that implements sTTI. As described herein, the UE 101 may notify the RAN node 111 about the UE's blind decoding capability (e.g., the maximum number of blind decoding attempts (BDA) that the UE 101 can perform within an sTTI, a subframe, or another reference time window). Alternatively, with respect to CA, the maximum number of BDAs for the UE 101 may be indicated on a per-CC basis. In some embodiments, the UE 101 may determine and transmit to the RAN node 111 an aggregation level (AL) of the UE 101, which may be based on a signal-to-noise ratio (SNR) measured by the UE 101. In some embodiments, a relatively low SNR may correspond to a higher AL (e.g., an AL of 2 or 4), and a relatively high SNR may correspond to a lower AL (e.g., an AL of 1). The AL of UE 101 may indicate or be used to indicate the number of shortened channel control entities (sCCEs) to be used to deliver DCI from RAN node 111 to UE 101. For example, an AL of 2 may indicate that 2 sCCEs are to be used to deliver DCI, and an AL of 4 may indicate that 4 sCCEs may be used to deliver DCI.

[0088] Based on the blind decoding capability and / or AL of UE 101 (and / or one or more other factors described herein), RAN node 111 may determine the location within the sPDCCH to include DCI for UE 101 (e.g., which sTTIs and / or CCEs are used to transmit DCI within the sPDCCH). UE 101 may determine potential or candidate sPDCCH resources (e.g., sTTIs, CCEs, etc.) and / or DCI formats that RAN node 111 may use to transmit DCI based on the AL of the UE. In addition, UE 101 may monitor the sPDCCH (based on the determined potential or candidate sPDCCH resources) to obtain DCI from RAN node 111 and further communicate with RAN node 111 using the DCI. Reference is made to hereinafter. Figure 7-Figure 12 Discuss the details of these and other techniques.

[0089] Figure 7 700 is a sequence flow chart of an exemplary process for providing DCI via sCCE. As shown in the figure, Figure 7 Examples may include UE 101 and RAN node 111. Figure 7 The examples are provided as non-limiting examples. In practice, Figure 7 Examples of may include fewer, additional, and / or alternative operations, functions, and / or transmissions. Figure 7 One or more of the operations or functions of may be performed by fewer, additional or alternative devices, which may include the above referenced Figure 1 One or more of the devices described.

[0090] As shown, UE 101 may transmit UE capability information to RAN node 111 (at 710). UE capability information may include the maximum number of BDAs that UE 101 may be configured to use during sTTI. In some embodiments, with respect to CA, the maximum number of BDAs may be indicated on a per-CC basis. The number of BDAs supported by the UE (e.g., for CC) may be a field value (X) to minimize control signaling overhead, where X may be an integer (e.g., X=32). In some embodiments, further reduction in signaling overhead may be achieved by defining an information element field (e.g., sMaxBlindDecoding) to indicate the maximum number of BDAs in a reference time window, which may be independent of the sTTI length and / or configured by RAN node 111 for UE 101 (via higher layer signaling or otherwise). Examples of reference time windows may include traditional TTI lengths (e.g., 1 ms). This technique may alleviate the need for UE 101 to send multiple messages to RAN node 101 for different sTTI length support.

[0091] Additionally or alternatively, the UE capability information may include an AL of the UE 101. The AL of the UE may be based on an SNR measured by the UE, and may indicate (or be used to indicate) the number of sCCEs to be used to deliver the DCI from the RAN node 111 to the UE 101. For example, an AL of 1 may indicate that 1 sCCE is to be used to deliver the DCI, an AL of 2 may indicate that 2 sCCEs are to be used to deliver the DCI, and an AL of 4 may indicate that 4 sCCEs may be used to deliver the DCI. In other embodiments, different numbers of ALs may indicate different numbers of sCCEs. As described herein, a CCE may include one or more resource elements (REs) that may be organized into one or more resource element groups (REGs), and an sCCE may include a portion of a CCE.

[0092] The RAN node 111 may determine sCCE candidates (including multiple candidates and their locations in the sPDCCH region) for sPDCCH based on the maximum BDA capability reported by the UE 101 for transmission of shortened DCI (sDCI) (at 720 and 730). For example, the UE 101 may include a formula, a process, a data structure (e.g., a table, an array, etc.) that enables the UE 101 to determine sCCE candidates based on the maximum BDA supported by the UE 101. As described herein, a CCE may include one or more resource elements (REs) that may be organized into one or more resource element groups (REGs). As described herein, an sCCE may include a portion of a CCE. In addition, the sCCE corresponding to an sPDCCH candidate (e.g., a portion of an sPDCCH that can be used to transmit DCI information) may be determined based on a variety of factors, such as the AL of the UE 101, the total number of sCCEs in the sPDCCH physical resource block (PRB) set, the maximum number of sPDCCH candidates that can be configured for sPDCCH monitoring in an sTTI, and the like. For example, the sCCE corresponding to the sPDCCH candidate (m) at the AL within the UE-specific sTTI search space may be given by:

[0093]

[0094] where i=0, ..., L-1 and N sCCE,P may be the total number of sCCEs in sPDCCH PRB set p, k may be the sTTI index (or another type of identification value), and b=0 for the self-scheduling case, and b=n CI , otherwise n CI M may include the maximum number of sPDCCH candidates that can be configured for sPDCCH monitoring in an sTTI, and M (L) The maximum number of sPDCCH candidates that can be configured for sPDCCH monitoring in an sTTI at a particular ALL may be included. Each sPDCCH PRB set may be configured for localized transmission or distributed sPDCCH transmission. In some embodiments, Y P,k can be configured with a higher layer (e.g. Figure 7 The value of the corresponding sPDCCH resource block (RB) set in a UE-specific manner (RRC signaling before or during process 700).

[0095] In some embodiments, Y P,k May be provided and / or determined as follows:

[0096] Y p,k =(A p ·Υ p,k-1)mod D

[0097] where Y p,-1 =n RNTI , A0=39827, A1=39829, D=65537. Various techniques may be used to convert the number of sPDCCH candidates m E{0,1,...,M p (L)}Configure the sPDCCH resource set (p) for one sTTI. In some embodiments, UE 101 may be configured with M p (L) , which may indicate the maximum number of sPDCCH candidates in all sDCI formats associated with AL(L) in the sPDCCH PRB set (p), where M p (L) E{0,1,…,M) and M may be the maximum number of sPDCCH candidates that can be configured for sPDCCH monitoring in an sTTI, and ∑∑ L,p M p (L) ≤M. For sPDCCH resource set, M p (L) For at least one AL can be non-zero. Since different numbers of sTTIs may exist within the subframes of 2-symbol and slot-based sTTI configurations, different sets of ALs that the UE can monitor can be defined separately. In some designs, the first set of ALs may include ALs 1, 2, and 4 (i.e., LE{1,2,4}) applicable to sPDCCH monitoring in 2-symbol sTTIs. At the same time, the second set of ALs may include ALs 1, 2, 4, and 8 (i.e., LE{1,2,4,8}) applicable to slot-based sTTIs. The two AL sets may partially overlap or not overlap. In other words, an element of one configuration may be a subset of an element of another configuration (i.e., completely overlapping, for example, one configuration may include {1,2,4}, while a configuration may include {1,2,4,8}). In some other embodiments, the elements of the two configurations may have at least one different value, for example, one configuration may include {1,2,4}, while another may include {1,8}.

[0098] In some embodiments, a subset of the first AL set and / or the second AL set may be configured by a higher layer to the UE 101 as part of the sPDCCH resource RB set configuration, for example based on the DL SNR. For example, for 2-symbol sTTI operation, LE{1,2} may be configured for UE 101 with a high DL SNR; and LE{2,4} may be configured for UE 101 with a low DL SNR. Additionally or alternatively, the UE 101 may be configured to have a maximum number of ALs of 2 to further control blind decoding (BD) complexity. Therefore, the maximum number of BDAs per sTTI (i.e., M) may be determined based on the sTTI length, and the maximum number may be different for 2-symbol sTTI and slot-based sTTI. In some embodiments, for 2-symbol sTTI, M may be 4 or 6, and for slot-based sTTI, M may be 16 or 18, with the goal of using the same number of BDAs for 2-symbol and slot-based sPDCCH on a subframe. In some embodiments, for the sPDCCH resource set, the corresponding BDA for each AL may be configured by a higher layer (e.g., for UE 101 with good SNR, BDA {3, 2, 1} is used for AL {1, 2, 4}, and for UE 101 with poor SNR, BDA {0, 4, 2} is used for AL {1, 2, 4}). This approach may provide the RAN node 111 with sufficient flexibility to adapt to radio channel variations in terms of available ALs and to reduce the probability that signal blocking may occur in terms of the location of sPDCCH candidates.

[0099] According to some embodiments, a UE 101 operating in a sTTI system (e.g., a RAN supporting sTTI) may be configured with higher layer signaling (e.g., one or more RRC information elements (IEs), such as IE sPDCCH candidate reduction) for a specific search space at the AL (L) and sPDCCH PRB set (p) of a serving cell (e.g., RAN node 111). In such a scenario, the corresponding number of sPDCCH candidates may be determined by:

[0100]

[0101] The value of a can be determined according to Table 1 below.

[0102] sPDCCH candidate reduction The value of a 0 0 1 0.33 2 0.66 3 1

[0103] Table 1: Scaling factors for sPDCCH candidate reduction

[0104] Alternatively, the value of a may be configured using RRC signaling (for UE 101), and / or A reference number of sPDCCH candidates at ALL in sPDCCH-PRB set p may be represented, which may be tabulated according to the 3GPP communication standard and / or indicated by higher layers (e.g., RRC signaling) on ​​a per-sPDCCH RB set basis.

[0105] As shown, RAN node 111 may transmit sDCI to UE 101 via sCCE and sPDCCH (at 740). When RAN node 111 transmits sDCI, UE 101 may monitor sPDCCH for sDCI so that UE 101 can obtain sDCI from sCCE and sPDCCH (at 750). UE 101 and RAN node 111 may communicate with each other based on sDCI from RAN node 111 (at 760).

[0106] Figure 8-Figure 10 800, 900, and 1000 according to one or more embodiments described herein. As shown, each sREG 800, 900, and 1000 may include channel state information reference signal (CSI-RS) information and 11 available REs. In some embodiments, as depicted in sREG 800, when 2 cell-specific reference signal (CRS) port transmission diversity is configured, the first 10 available REs (e.g., SFBC pairs 810-850) may be grouped into 5 space-frequency block coded (SFBC) pairs using an Alamouti code in frequency, which are labeled in REG 800 with a combination of uppercase letters A to E. For the remaining REs (sCCE 660, labeled E0), the modulation symbol transmitted in the first RE of the adjacent SFBC pair (e.g., E0 in SFBC pair 850) may be repeated and transmitted by each CRS antenna port, for example to provide greater spatial diversity gain.

[0107] See also Fig. 9 In the sREG 900 of FIG. 1 , when 4 CRS port transmission diversity is configured, the first 8 available REs may be organized into 2 SFBC pairs 910 and 920. For the remaining 3 available REs, the first three modulation symbols transmitted in the first three REs of the adjacent SFBC pair (e.g., sCCE B1, B3, and B2 of SFBC pair 920) may be repeated and transmitted in REG 930, respectively. Fig.10As shown, the exemplary sREG 1000 may include a similar arrangement of REs for a 4-port SFBC pair and SFBC pairs 1010 and 1020. However, the remaining REs 1030 may be repeated in a different manner (e.g., B2, B3, and B1), which may be due to, for example, high channel correlation between consecutive frequency tones. The techniques described herein may include all other combinations of repeated REs and / or RE sequences (e.g., B1, B2, B4, etc.) for repeating REs of adjacent SFBC pairs.

[0108] Fig.11 1 is a schematic diagram of an exemplary subframe 1100 for transmitting sDCI via a legacy PDCCH. Subframe 1100 may correspond to a legacy TTI (e.g., 1 ms) and may include a portion 1110 of sDCI (which may correspond to sTTI) and another portion 1120 of DCI (e.g., LTE DCI). UE 101 may be configured to monitor subframe 1100 to obtain sDCI and / or additional DCI.

[0109] like Fig.11 As shown, in some embodiments, the search space for sDCI in the PDCCH region may be a subset of the search space for PDCCH used for DCI format monitoring. For example, assuming that UE 101 is configured to monitor M in the UE-specific search space (USS) on the PDCCH region. L candidates, UE 101 can search for M L In one embodiment, the first set of PDCCH candidates within the PDCCH region may be the first set of PDCCH candidates for obtaining sDCI. PDCCH candidates, among which The number of sPDCCH candidates for sDCI format monitoring may be configured by higher layers (e.g., via RRC signaling) on ​​a per AL and / or per UE 101 basis. In addition, UE 101 may be configured to continuously monitor for DCI formats. PDCCH, where M L It may be the total number of candidates that the UE needs to monitor in the PDCCH region.

[0110] Thus, subframe 1100 may include two UE-specific search spaces. One UE-specific search space may correspond to a portion 1110 of the sDCI, and the other UE-specific search space may correspond to a portion 1120 of the DCI (e.g., LTE DCI). The first UE-specific search space (e.g., portion 1110) and the second UE-specific search space (e.g., portion 1120) may be configured by a higher layer (e.g., via RRC signaling) and / or may partially overlap in terms of CCE candidates. The first search space for the sDCI format in the PDCCH region may be a subset of the second search space. In other words, the first UE-specific search space may be the same as the second (or legacy) search space for DCI format monitoring. This may provide the RAN node 111 with flexibility to, for example, allocate the number of PDCCH candidates for sDCI and DCI formats per subframe on the PDCCH candidates.

[0111] In some embodiments, the sDCI may be mapped to the same search space of the DCI format on the PDCCH. In such embodiments, an indicator (e.g., a value of 0) may be appended to the sDCI format until the payload size is equal to the payload size of the DCI format, e.g., to avoid additional BDA from the UE 101. To distinguish from the normal DCI format, a dedicated radio network temporary identifier (RNTI) may be assigned to the UE 101 and may be used to scramble the sDCI format cyclic redundancy check (CRC). In some embodiments, the UE-specific search space for the sDCI (e.g., Fig.11 Part 1110) may be determined based on a dedicated RNTI assigned to the UE 101 for sTTI operation. Additionally or alternatively, the number of ALs and the number of PDCCH candidates per AL may be configured via RRC signaling.

[0112] In some embodiments, a single parameter PDCCH candidate reduction may be configured by higher layers (e.g., RRC signaling) and is typically applied to a UE-specific search space (e.g., Fig.11 110 and 1120) for sDCI and DCI format monitoring by UE 101. In some embodiments, the PDCCH candidate reduction may be 0.6 and / or may be configured by higher layers (e.g., RRC signaling) for AL1. Additionally or alternatively, in a UE-specific search space (e.g., Fig.11 There may be 6 PDCCH candidates in the combination of parts 1110 and 1120 of . In such an embodiment, a UE-specific search space (e.g., Fig.11 The portion 1110 of may be determined to consist of the first [0.6×6]=4 PDCCH candidates, and another UE-specific search space (eg, Fig.11 The portion 1120 of may be determined to consist of the remaining portion of the 6 PDCCH candidates (i.e., 2 PDCCH candidates) for a given AL (e.g., AL 1). In addition, the UE-specific search space (e.g., Fig.11 The total number of PDCCH candidates in portion 1110) may be smaller than the total number of PDCCH candidates in other sTTIs of the same subframe, for example, to ensure that the total number of BDs per sTTI per CC is the same across all TTIs of the subframe.

[0113] As described herein, the system bandwidth (e.g., the bandwidth used by the UE 101 and / or the RAN node 111) may be divided into a plurality of shortened resource block groups (sRBGs), where an sRBG may be a set of contiguous resource blocks (RBs). The sRBG may be increased N times compared to the RBG size (e.g., 1 ms) of conventional normal TTI operation, for example to limit the number of resource allocation field bits in the sDCI. In some embodiments, the sDCI of different UEs 101 for the same sRBG may be multiplexed, for example to improve the efficiency of the achievable sTTI. The techniques described herein may include a dynamic resource sharing mechanism, for example to assist and / or enable the UE 101 to accurately utilize unused RBs in a reserved sPDCCH RB set (e.g., sRBG) to decode PDSCH transmissions.

[0114] Fig.12 1 is a schematic diagram of an example 1200 for dynamic resource sharing of an sPDCCH RB set. As shown, an sPDCCH RB set may include 8 sCCEs indexed from 0 to 7 (in this case, N sCCE =8). The sCCEs may be arranged in 3 different sCCEGs indexed from 0 to 3. In addition, each sCCEG may correspond to a bitmap field (e.g., having a specific sDCI format) including three bitmap values ​​(b0, b1, and b2) corresponding to different sCCEG indices.

[0115] Assuming that the first UE 101 uses sCCE 0 for sPDCCH transmission, and the second UE 101 uses sCCE 4 and 5 for sPDCCH transmission, the bitmap field (e.g., bO) for scheduling the sPDSCH of the first UE 101 may be set to (1,1,0) (where "1" indicates that the sCCEG is in use, and "0" indicates that the sCCEG is not in use) to indicate that sCCEG 0 and 1 are used for PDCCH; however, sCCEG 2 is not used for PDCCH. Therefore, if the resources of the sPDSCH allocated to the first UE 101 overlap with the sPDCCH RB set, the first UE 101 may be aware that sCCEG 2 can be used for sPDSCH.

[0116] In some embodiments, sCCE formation may further consider the AL of sPDCCH. For example, a sCCEG pattern set and corresponding sCCE may be defined based on the location and / or AL of sDCI detected by the UE.

[0117] Additionally or alternatively, the sCCEG may include multiple "basic unit" sCCEGs (e.g., a basic unit sCCEG may be composed of two consecutive sCCEs). For example, three sCCEGs may be formed with respective sCCEGs composed of sCCEs (0, 1, 2, 3), (4, 5), and (6, 7) to, for example, improve resource efficiency. In some embodiments, a one-to-one mapping may be generated to associate the state indicated by the bitmap field in the sDCI with a predefined sCCEG mode.

[0118] In some embodiments, one or more sPDCCH PRB sets may be allocated to UE 101 for sPDCCH monitoring, which may be from 0 to N. sCCE -1 numbered logical sCCE sets, where N sCCE It may be the number of sCCEs in the sPDCCH resource set, and each sPDCCH RB set may be configured as a continuous or non-contiguous PRB. In such an embodiment, the sCCEs may be logically grouped into a set of sCCE groups (sCCEGs). Additionally or alternatively, the UE 101 and / or the RAN node 111 may determine the total number of sCCE groups r of one or more sPDCCH PRB sets according to the following formula:

[0119] r=[N sCCE / B]

[0120] K x =B,0≤x≤[N sCCE / B]

[0121] K r-1 =N sCCE –B·[N sCCE / B]

[0122] Where K x is the number of sCCEs of sCCEG x in the sPDCCH PRB set, and B may be a predefined value (e.g., a value defined by a 3GPP communication standard). Additionally or alternatively, B may be a function of the system bandwidth (e.g., the bandwidth available to UE 101 and / or RAN node 111), or alternatively, B may be configured by a higher layer on a per-UE basis (e.g., by UE-specific RRC signaling).

[0123] Alternatively, in some embodiments, the RAN node 111 may use the following procedure to distribute the number of sCCEAs as evenly as possible into each sCCEG. + =N sCCE mod BsCCEG, each of which consists of C + =[N sCCE / r]sCCE. At the same time, there may be [N sCCE / r]sCCE composed of C_ = rC + sCCEG. In some embodiments, N sCCE Can be used to count sCCEs other than those detected by a given UE 101 for sPDCCH transmission.

[0124] In some embodiments, N sCCE sCCEs may be counted except for sCCEs detected by a given UE for sPDCCH transmission.

[0125] In addition, in the sDCI for sRBG-based sPDSCH resource allocation, the resource block sharing information includes a bitmap indicating unused sCCEGs in the sPDCCH PRB set, which can be allocated to the scheduled UE 101 for sPDSCH transmission. The size of the bitmap is r bits, and each sCCEG has a bitmap bit, so that each sCCEG (if not used for sPDCCH in sTTI) is addressable for Spdsch transmission. The order of sCCEG to bitmap bit mapping is as follows: sCCEG 0 to sCCEG r-1 can be mapped to the most significant bit (MSB) to the least significant bit (LSB) of the bitmap. If the corresponding bit value in the bitmap is 1, the sCCEG can be allocated to the UE, otherwise the sCCEG may not be allocated to UE 101.

[0126] Fig.13Exemplary components of a device 1300 according to some embodiments are shown. In some embodiments, the device 1300 may include an application circuit 1302, a baseband circuit 1304, a radio frequency (RF) circuit 1306, a front-end module (FEM) circuit 1308, one or more antennas 1310, and a power management circuit (PMC) 1312 (at least coupled together as shown). The components of the illustrated device 1300 may be included in a UE or a RAN node. In some embodiments, the device 1300 may include fewer elements (e.g., the RAN node cannot utilize the application circuit 1302, but includes a processor / controller to process IP data received from the EPC). In some embodiments, the device 1300 may include additional elements, such as, for example, a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the circuit may be separately included in more than one device for a specific implementation of a cloud-RAN (C-RAN)).

[0127] The application circuit 1302 may include one or more application processors. For example, the application circuit 1302 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor 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 1300. In some embodiments, the processor of the application circuit 1302 may process IP data packets received from the EPC.

[0128] The baseband circuit 1304 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 1304 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 1306 and generate baseband signals for the transmit signal path of the RF circuit 1306. The baseband processing circuit 1304 may interact with the application circuit 1302 to generate and process baseband signals and control the operation of the RF circuit 1306. For example, in some embodiments, the baseband circuit 1304 may include a third generation (3G) baseband processor 1304A, a fourth generation (4G) baseband processor 1304B, a fifth generation (5G) baseband processor 1304C, or other baseband processors 1304D 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 1304 (e.g., one or more of the baseband processors 1304A-1304D) may handle various radio control functions that can communicate with one or more radio networks via the RF circuit 1306. In other embodiments, some or all of the functions of the baseband processors 1304A-1304D may be included in modules stored in the memory 1304G and executed via the central processing unit (CPU) 1304E. 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 1304 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 1304 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions.

[0129] The implementation of the modulation / demodulation and encoder / decoder functionality is not limited to these examples and may include other suitable functionality in other implementations.

[0130] In some embodiments, the baseband circuit 1304 may include one or more audio digital signal processors (DSPs) 1304F. The audio DSP 1304F 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 1304 and the application circuit 1302 may be implemented together, such as on a system on a chip (SOC).

[0131] In some embodiments, baseband circuitry 1304 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 1304 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 baseband circuitry 1304 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0132] RF circuit 1306 can communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 1306 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 1306 may include a receive signal path, which may include circuits that downconvert an RF signal received from FEM circuit 1308 and provide a baseband signal to baseband circuit 1304. RF circuit 1306 may also include a transmit signal path, which may include circuits that upconvert a baseband signal provided by baseband circuit 1304 and provide an RF output signal for transmission to FEM circuit 1308.

[0133] In some embodiments, the receive signal path of the RF circuit 1306 may include a mixer circuit 1306a, an amplifier circuit 1306b, and a filter circuit 1306c. In some embodiments, the transmit signal path of the RF circuit 1306 may include a filter circuit 1306c and the mixer circuit 1306a. The RF circuit 1306 may also include a synthesizer circuit 1306d for synthesizing the frequencies used by the mixer circuit 1306a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 1306a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1308 based on the synthesized frequency provided by the synthesizer circuit 1306d. The amplifier circuit 1306b may be configured to amplify the down-converted signal, and the filter circuit 1306c 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 baseband circuit 1304 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, the mixer circuit 1306a of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this regard.

[0134] In some embodiments, mixer circuit 1306a of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 1306d to generate an RF output signal for FEM circuit 1308. The baseband signal can be provided by baseband circuit 1304 and can be filtered by filter circuit 1306c.

[0135] In some embodiments, the mixer circuit 1306a of the receive signal path and the mixer circuit 1306a of the transmit signal path may include two or more mixers and may be arranged for orthogonal down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 1306a of the receive signal path and the mixer circuit 1306a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 1306a of the receive signal path and the mixer circuit 1306a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 1306a of the receive signal path and the mixer circuit 1306a of the transmit signal path may be configured for superheterodyne operation.

[0136] 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, RF circuit 1306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 1304 may include a digital baseband interface to communicate with RF circuit 1306.

[0137] 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.

[0138] In some embodiments, synthesizer circuit 1306d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 1306d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0139] Synthesizer circuit 1306d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 1306a of RF circuit 1306. In some embodiments, synthesizer circuit 1306d may be a fractional-N / N+1 synthesizer.

[0140] 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 the baseband circuit 1304 or the application processor 1302 depending on 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 the application processor 1302.

[0141] The synthesizer circuit 1306d of the RF circuit 1306 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.

[0142] In some embodiments, the synthesizer circuit 1306d 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 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 1306 can include an IQ / polarity converter.

[0143] The FEM circuitry 1308 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 1310, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 1306 for further processing. The FEM circuitry 1308 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 1306 for transmission via one or more of the one or more antennas 1310. In various embodiments, amplification by the transmit or receive signal paths may be performed only in the RF circuitry 1306, only in the FEM 1308, or in both the RF circuitry 1306 and the FEM 1308.

[0144] In some embodiments, the FEM circuit 1308 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 1306). The transmit signal path of the FEM circuit 1308 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuit 1306); 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 1310).

[0145] In some embodiments, PMC 1312 can manage the power provided to baseband circuit 1304. Specifically, PMC 1312 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When device 1300 is capable of being powered by a battery, for example, when the device is included in a UE, PMC 1312 can generally be included. PMC 1312 can improve power conversion efficiency while providing a desired specific implementation size and heat dissipation characteristics.

[0146] Although Fig.13 PMC 1312 is shown coupled only to baseband circuit 1304. However, in other embodiments, PMC 1312 may be additionally or alternatively coupled to other components (such as, but not limited to, application circuit 1302, RF circuit 1306, or FEM 1308) and perform similar power management operations.

[0147] In some embodiments, the PMC 1312 may control or otherwise be part of various power saving mechanisms of the device 1300. For example, if the device 1300 is in an RRC connected state, where the device is still connected to a RAN node as expected to receive traffic for a short period of time, then after a period of inactivity, the device may enter a state known as discontinuous reception mode (DRX). During this state, the device 1300 may be powered off for short time intervals, thereby saving power.

[0148] If there is no data traffic activity for an extended period of time, the device 1300 can transition to the RRC_Done state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1300 enters a very low power state and performs paging, in which the device wakes up periodically again to listen to the network and then powers down again. The device 1300 cannot receive data in this state, and in order to receive data, it must transition back to the RRC_Connected state.

[0149] 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.

[0150] The processor of the application circuit 1302 and the processor of the baseband circuit 1304 may be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 1304 may be used alone or in combination.

[0151] The processor of the application circuit 1304 may 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.

[0152] Fig.14 An exemplary interface of a baseband circuit according to some embodiments is shown. As discussed above, Fig.13 The baseband circuit 1304 may include processors 1304A-1304E and a memory 1304G utilized by the processors. Each of the processors 1304A-1304E may include a memory interface 1404A-1404E, respectively, for sending / receiving data to / from the memory 1304G.

[0153] The baseband circuit 1304 may also include: one or more interfaces to communicate with other circuits / devices, such as a memory interface 1412 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1304); an application circuit interface 1414 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1304); Fig.13 RF circuit interface 1416 (for example, for sending / receiving data to / from the application circuit 1302); Fig.13 an interface for sending / receiving data to / from a RF circuit 1306); a wireless hardware connection interface 1418 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g. Energy), components and other communication components to send / receive data); and a power management interface 1420 (for example, an interface for sending / receiving power or control signals to / from PMC 1312).

[0154] Fig.15 15 is a diagram of a control plane protocol stack according to some embodiments. In this embodiment, the control plane 1500 is shown as a communication protocol stack between UE 101 (or alternatively, UE 102), RAN node 111 (or alternatively, RAN node 112) and MME 121.

[0155] The PHY layer 1501 may transmit or receive information used by the MAC layer 1502 over one or more air interfaces. The PHY layer 1501 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers such as the RRC layer 1505. The PHY layer 1501 may further perform error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and multiple-input multiple-output (MIMO) antenna processing.

[0156] The MAC layer 1502 can perform mapping between logical channels and transport channels, multiplex MAC service data units (SDUs) from one or more logical channels onto transport blocks (TBs) to be delivered to the PHY via transport channels, demultiplex MAC SDUs from transport blocks (TBs) delivered by the PHY via transport channels to one or more logical channels, multiplex MAC SDUs onto TBs, schedule information reporting, perform error correction through hybrid automatic repeat request (HARQ), and prioritize logical channels.

[0157] The RLC layer 1503 can operate in multiple operating modes, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). The RLC layer 1503 can perform transmission of higher layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. The RLC layer 1503 can also perform re-segmentation of RLC data PDUs for AM data transmission, reordering of RLC data PDUs for UM and AM data transmission, detection of duplicate data for UM and AM data transmission, discarding of RLC SDUs for UM and AM data transmission, detection of protocol errors for AM data transmission, and performing RLC re-establishment.

[0158] The PDCP layer 1504 can perform header compression and decompression of IP data, maintain the PDCP sequence number (SN), perform in-order delivery of upper layer PDUs when lower layers are re-established, eliminate duplication of lower layer SDUs when re-establishing lower layers for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0159] The main services and functions of the RRC layer 1505 may include broadcasting of system information (e.g., included in a master information block (MIB) or a system information block (SIB) related to a non-access stratum (NAS)), broadcasting of system information related to an access stratum (AS), paging, establishment, maintenance and release of an RRC connection between a UE and an E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification and RRC connection release), establishment, configuration, maintenance and release of point-to-point radio bearers, security functions including key management, mobility between radio access technologies and measurement configuration for UE measurement reporting. The MIB and SIB may include one or more information elements (IEs), each of which may include a separate data field or data structure.

[0160] UE 101 and RAN node 111 may utilize a Uu interface (eg, LTE-Uu interface) to exchange control plane data via a protocol stack including a PHY layer 1501 , a MAC layer 1502 , an RLC layer 1503 , a PDCP layer 1504 , and an RRC layer 1505 .

[0161] Non-Access Stratum (NAS) protocol 1506 forms the highest layer of the control plane between UE 101 and MME 121. NAS protocol 1506 supports mobility of UE 101 and session management procedures to establish and maintain IP connection between UE 101 and P-GW 123.

[0162] The S1 application protocol (S1-AP) layer 1515 may support the functions of the S1 interface and include an elementary procedure (EP). The EP is an interaction unit between the RAN node 111 and the CN 120. The S1-AP layer services may include two groups: UE-associated services and non-UE-associated services. The functions performed by these services include, but are not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM) and configuration transmission.

[0163] A stream control transmission protocol (SCTP) layer (also referred to as a SCTP / IP layer) 1514 may ensure reliable delivery of signaling messages between the RAN node 111 and the MME 121 based in part on the IP protocol supported by the IP layer 1513. The L2 layer 1512 and the L1 layer 1511 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

[0164] The RAN node 111 and the MME 121 may exchange control plane data via a protocol stack including an L1 layer 1511 , an L2 layer 1512 , an IP layer 1513 , an SCTP layer 1514 , and an S1-AP layer 1515 using an S1-MME interface.

[0165] Fig.16 1 is a diagram of a user plane protocol stack according to some embodiments. In this embodiment, the user plane 1600 is shown as a communication protocol stack between the UE 101 (or alternatively, the UE 102), the RAN node 111 (or alternatively, the RAN node 112), the S-GW 122 and the P-GW 123. The user plane 1600 may utilize at least some of the same protocol layers as the control plane 1500. For example, the UE 101 and the RAN node 111 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack including a PHY layer 1501, a MAC layer 1502, a RLC layer 1503, and a PDCP layer 1504.

[0166] The General Packet Radio Service (GPRS) Tunneling Protocol for User Plane (GTP-U) layer 1604 may be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data may be packets in IPv4, IPv6, or PPP format. The UDP and IP Security (UDP / IP) layer 1603 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication of selected data flows. The RAN node 111 and the S-GW 122 may exchange user plane data via a protocol stack including the L1 layer 1511, the L2 layer 1512, the UDP / IP layer 1603, and the GTP-U layer 1604 using the S1-U interface. S-GW 122 and S-GW 123 may exchange user plane data using an S5 / S8a interface via a protocol stack including L1 layer 1511, L2 layer 1512, UDP / IP layer 1603, and GTP-U layer 1604. Fig.15 As discussed, the NAS protocol supports the mobility of UE 101 and session management procedures to establish and maintain an IP connection between UE 101 and P-GW 123.

[0167] Fig.17 Components of a core network according to some embodiments are shown. The components of CN 120 can 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 120 can be referred to as a network slice 1701. A logical instance of a portion of CN 120 can be referred to as a network sub-slice 1702 (e.g., network sub-slice 1702 is shown as including PGW 123 and PCRF 126).

[0168] 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.

[0169] Fig.18 1800 , a virtualized network function (VNF) manager (VNFM) 1806 , a virtualized network function (VNF) 1808 , an element manager (EM) 1810 , a NFV orchestrator (NFVO) 1812 , and a network manager (NM) 1814 .

[0170] The VIM 1802 manages resources of the NFVI 1804. The NFVI 1804 may include physical or virtual resources and applications (including hypervisors) for executing the system 1800. The VIM 1802 may utilize the NFVI 1804 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.

[0171] The VNFM 1806 may manage the VNF 1808. The VNF 1808 may be used to perform EPC components / functions. The VNFM 1806 may manage the lifecycle of the VNF 1808 and track the performance, failures, and security of the virtual aspects of the VNF 1808. The EM 1810 may track the performance, failures, and security of the functional aspects of the VNF 1808. The tracking data from the VNFM 1806 and the EM 1810 may include, for example, performance measurement (PM) data used by the VIM 1802 or the NFVI 1804. The VNFM 1806 and the EM 1810 may both scale up / down the number of VNFs of the system 1800.

[0172] NFVO 1812 may coordinate, authorize, release, and engage resources of NFVI 1804 in order to provide requested services (e.g., execute EPC functions, components, or slices). NM 1814 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 1810).

[0173] Fig.19 is a block diagram illustrating components 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.19 A schematic diagram of hardware resources 1900 is shown, including one or more processors (or processor cores) 1910, one or more memory / storage devices 1920, and one or more communication resources 1930, each of which can be communicatively coupled via a bus 1940. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1902 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1900.

[0174] Processor 1910 (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 1912 and processor 1914.

[0175] The memory / storage device 1920 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1920 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 memory, etc.

[0176] The communication resources 1930 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 1904 or one or more databases 1906 via the network 1908. For example, the communication resources 1930 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Components (e.g. Low Energy), components and other communication components.

[0177] The instructions 1950 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1910 to perform any one or more of the methodologies discussed herein. The instructions 1950 may reside in whole or in part in at least one of the processor 1910 (e.g., in a cache memory of the processor), the memory / storage device 1920, or any suitable combination thereof. In addition, any portion of the instructions 1950 may be transmitted to the hardware resources 1900 from any combination of the peripheral device 1904 or the database 1906. Thus, the memory of the processor 1910, the memory / storage device 1920, the peripheral device 1904, and the database 1906 are examples of computer-readable and machine-readable media.

[0178] Next, a number of examples related to implementation of the above-mentioned technology will be given.

[0179] In a first embodiment, a device of a user equipment (UE) may include: an interface to a radio frequency (RF) circuit; and one or more processors controlled to: process information about a search space of a physical downlink control channel (PDCCH) received via the interface to the RF circuit for obtaining downlink control information (DCI) from a radio access network (RAN) node; determine a time slot format for communicating with the RAN node based on the DCI obtained from the RAN node, wherein the time slot format of the time slot indicates symbols allocated for uplink (UL) communication, symbols allocated for downlink (DL) communication, and symbols identified as flexible symbols; and communicate with the RAN node according to the time slot format via the interface to the RF circuit.

[0180] In embodiment 2, the subject matter of embodiment 1 or any one of the embodiments herein, wherein a slot format indicator (SFI) monitoring configuration is received via higher layer signaling.

[0181] In embodiment 3, the subject matter of embodiment 1 or any one of the embodiments herein, wherein in order to determine a time slot format, one or more processors are controlled to: receive multiple time slot formats including the time slot format via an interface to an RF circuit; and map an SFI index field value of a DCI format corresponding to the DCI to the time slot format among the multiple time slot formats.

[0182] In embodiment 4, the subject matter of embodiment 1 or any one of the embodiments herein, wherein one or more processors are further controlled to: determine time slot format information of one or more consecutive time slots based on higher layer signaling from a RAN node and a PDCCH carrying a DCI format with an SFI.

[0183] In embodiment 5, the subject matter of embodiment 1 or any one of the embodiments herein, wherein the one or more processors are further controlled to: determine the serving cell corresponding to the time slot format based on higher layer signaling from the RAN node.

[0184] In embodiment 6, the subject matter of embodiment 1 or any one of the embodiments herein, wherein the search space corresponds to a BWP among a plurality of bandwidth parts (BWPs) used for communication between the UE and the RAN node.

[0185] In embodiment 7, the subject matter of embodiment 1 or any one of the embodiments herein, wherein one or more processors are further controlled to: determine the time slot format of another BWP among multiple BWPs based on the determined time slot format of the BWP, the subcarrier spacing (SCS) of the BWP, and the SCS of the other BWP.

[0186] In an eighth embodiment, a device of a user equipment (UE) may include: an interface to a radio frequency (RF) circuit; and one or more processors controlled to: enable UE capability information to be passed to a radio access network (RAN) node via the interface to the RF circuit, the information regarding the maximum number of blind decoding attempts (BDA) supported by the UE; determine a shortened channel control element (sCCE) to be used by the RAN node based on the maximum BDA to transmit shortened downlink control information (sDCI) via a shortened physical downlink control channel (sPDCCH); and obtain the sDCI by monitoring the sPDCCH based on the determined sCCE.

[0187] In embodiment 9, the subject matter of embodiment 8 or any one of the embodiments herein, wherein the one or more processors are further controlled to: communicate with the RAN node according to the sDCI via an interface to the RF.

[0188] In embodiment 10, the subject matter of embodiment 8 or any one of the embodiments herein, wherein the number of blind decodings corresponds to a UE-specific search space of a subframe.

[0189] In embodiment 11, the subject matter of embodiment 8 or any one of the embodiments herein, wherein the maximum number of BDAs is provided via a field of a radio resource control (RRC) information element (IE) in a reference window.

[0190] In embodiment 12, the subject matter of embodiment 8 or any one of the embodiments herein, wherein the sDCI indicates at least one sCCE of a sPDCCH resource block (RB) set corresponding to a determined sCCE, which is used to transmit information via a physical downlink shared channel (PDSCH).

[0191] In embodiment 13, the subject matter of embodiment 8 or any one of the embodiments herein, wherein the sCCE of the sPDCCH is based at least in part on determining the sCCE of the sPDCCH candidate among multiple sPDCCH candidates at an aggregation level (AL) of the UE.

[0192] In embodiment 14, the subject matter of embodiment 8 or any one of the embodiments herein, wherein the multiple sPDCCH candidates at the AL correspond to a specific DCI format.

[0193] In embodiment 15, the subject matter of embodiment 8 or any one of the embodiments herein, wherein multiple sPDCCH candidates are provided to the UE via higher layer signaling.

[0194] In embodiment 16, the subject matter of embodiment 8 or any one of the embodiments herein, wherein the DCI format is provided to the UE via higher layer signaling.

[0195] In embodiment 17, the subject matter of embodiment 8 or any one of the embodiments herein, wherein the search space for sDCI in the PDCCH includes a subset of the search space of the PDCCH used for DCI format monitoring.

[0196] In Embodiment 18, the subject matter of Embodiment 8 or any one of the embodiments herein, wherein the search space of the PDCCH for DCI format monitoring includes a portion for sDCI monitoring and another portion for DCI format monitoring.

[0197] In embodiment 19, the subject matter of embodiment 8 or any one of the embodiments herein, wherein: the sCCEs of the sPDCCH RB set are arranged in a set of sCCE groups (sCCEGs); and the resource block sharing information in the sDCI includes a bitmap indicating unused sCCEGs in the sPDCCH PRB set used for sPDSCH transmission.

[0198] In a twentieth embodiment, a computer-readable medium may include program instructions for causing one or more processors associated with a user equipment (UE) to: process information about a search space of a physical downlink control channel (PDCCH) received from a radio access network (RAN) node for obtaining downlink control information (DCI) from the RAN node; determine a time slot format for communicating with the RAN node based on the DCI obtained from the RAN node, wherein the time slot format indicates for a time slot whether a corresponding symbol is allocated for uplink (UL) communication, downlink (DL) communication, or is identified as a flexible symbol; and communicate with the RAN node according to the time slot format.

[0199] In Embodiment 21, the subject matter of Embodiment 20 or any one of the embodiments herein, wherein a slot format indicator (SFI) monitoring configuration is received via higher layer signaling.

[0200] In embodiment 22, the subject matter of embodiment 20 or any one of the embodiments herein, wherein in order to determine a time slot format, one or more processors are to: receive multiple time slot formats including the time slot format; and map the SFI index field value of the DCI format corresponding to the DCI to the time slot format in the multiple time slot formats.

[0201] In embodiment 23, the subject matter of embodiment 20 or any one of the embodiments herein, wherein the one or more processors are further to: determine time slot format information of one or more consecutive time slots based on higher layer signaling from the RAN node and a PDCCH carrying a DCI format with an SFI.

[0202] In embodiment 24, the subject matter of embodiment 20 or any one of the embodiments herein, wherein the one or more processors are further to: determine the serving cell corresponding to the time slot format based on higher layer signaling from the RAN node.

[0203] In embodiment 25, the subject matter of embodiment 20 or any one of the embodiments herein, wherein the search space corresponds to a BWP among a plurality of bandwidth parts (BWPs) used for communication between the UE and the RAN node.

[0204] In embodiment 26, the subject matter of embodiment 20 or any one of the embodiments herein, wherein the one or more processors are further to: determine the time slot format of another BWP among the multiple BWPs based on the determined time slot format of the BWP, the subcarrier spacing (SCS) of the BWP, and the SCS of the other BWP.

[0205] In a twenty-seventh embodiment, a computer-readable medium may include program instructions for causing one or more processors associated with a user equipment (UE) to: cause UE capability information to be communicated to a radio access network (RAN) node, the information regarding a maximum number of blind decoding attempts (BDA) supported by the UE; determine, based on the maximum BDA, a shortened channel control element (sCCE) to be used by the RAN node to transmit shortened downlink control information (sDCI) via a shortened physical downlink control channel (sPDCCH); and obtain the sDCI by monitoring the sPDCCH based on the determined sCCE.

[0206] In embodiment 28, the subject matter of embodiment 27 or any one of the embodiments herein, wherein the one or more processors further: communicate with the RAN node based on the sDCI.

[0207] In embodiment 29, the subject matter of embodiment 27 or any one of the embodiments herein, wherein the number of blind decodings corresponds to a UE-specific search space of a subframe.

[0208] In embodiment 30, the subject matter of embodiment 27 or any one of the embodiments herein, wherein the maximum number of BDAs is provided via a field of a radio resource control (RRC) information element (IE) in a reference window.

[0209] In embodiment 31, the subject matter of embodiment 27 or any one of the embodiments herein, wherein the sDCI indicates at least one sCCE of a sPDCCH resource block (RB) set corresponding to a determined sCCE, which is used to transmit information via a physical downlink shared channel (PDSCH).

[0210] In embodiment 32, the subject matter of embodiment 27 or any of the embodiments herein, wherein the sCCE of the sPDCCH is based at least in part on determining the sCCE of the sPDCCH candidate among multiple sPDCCH candidates at an aggregation level (AL) of the UE.

[0211] In embodiment 33, the subject matter of embodiment 27 or any one of the embodiments herein, wherein the multiple sPDCCH candidates at the AL correspond to a specific DCI format.

[0212] In embodiment 34, the subject matter of embodiment 27 or any one of the embodiments herein, wherein multiple sPDCCH candidates are provided to the UE via higher layer signaling.

[0213] In embodiment 35, the subject matter of embodiment 27 or any one of the embodiments herein, wherein the DCI format is provided to the UE via higher layer signaling.

[0214] In embodiment 36, the subject matter of embodiment 27 or any one of the embodiments herein, wherein the search space for sDCI in the PDCCH includes a subset of the search space of the PDCCH used for DCI format monitoring.

[0215] In Embodiment 37, the subject matter of Embodiment 27 or any one of the embodiments herein, wherein the search space of the PDCCH for DCI format monitoring includes a portion for sDCI monitoring and another portion for DCI format monitoring.

[0216] In embodiment 38, the subject matter of embodiment 27 or any one of the embodiments herein, wherein: the sCCEs of the sPDCCH RB set are arranged in a set of sCCE groups (sCCEGs); and the resource block sharing information in the sDCI includes a bitmap indicating unused sCCEGs in the sPDCCH PRB set used for sPDSCH transmission.

[0217] In a thirty-ninth embodiment, a device of a user equipment (UE) may include: a device for processing information about a search space of a physical downlink control channel (PDCCH) received from a radio access network (RAN) node for obtaining downlink control information (DCI) from the RAN node; a device for determining a time slot format for communicating with the RAN node based on the DCI obtained from the RAN node, wherein the time slot format indicates for a time slot whether a corresponding symbol is allocated for uplink (UL) communication, downlink (DL) communication, or is identified as a flexible symbol; and a device for communicating with the RAN node according to the time slot format.

[0218] In Embodiment 40, the subject matter of Embodiment 39 or any one of the embodiments herein, wherein a slot format indicator (SFI) monitoring configuration is received via higher layer signaling.

[0219] In embodiment 41, the subject matter of embodiment 39 or any one of the embodiments herein, wherein the device for determining a time slot format includes: a device for receiving multiple time slot formats including the time slot format; and a device for mapping the SFI index field value of the DCI format corresponding to the DCI to the time slot format in the multiple time slot formats.

[0220] In embodiment 42, the subject matter of embodiment 39 or any one of the embodiments herein further includes: a device for determining time slot format information of one or more consecutive time slots based on higher layer signaling from a RAN node and a PDCCH carrying a DCI format with an SFI.

[0221] In Embodiment 43, the subject matter of Embodiment 39 or any one of the embodiments herein further includes: a device for determining a serving cell corresponding to the time slot format based on higher layer signaling from a RAN node.

[0222] In embodiment 44, the subject matter of embodiment 39 or any one of the embodiments herein, wherein the search space corresponds to a BWP among a plurality of bandwidth parts (BWPs) used for communication between the UE and the RAN node.

[0223] In Example 45, the subject matter of Example 39 or any one of the embodiments herein further includes: a device for determining the time slot format of another BWP among multiple BWPs based on the determined time slot format of the BWP, the subcarrier spacing (SCS) of the BWP, and the SCS of the other BWP.

[0224] In a forty-sixth embodiment, a device of a user equipment (UE) may include: a device for enabling UE capability information to be communicated to a radio access network (RAN) node, the information regarding the maximum number of blind decoding attempts (BDA) supported by the UE; a device for determining, based on the maximum BDA, a shortened channel control element (sCCE) to be used by the RAN node to transmit shortened downlink control information (sDCI) via a shortened physical downlink control channel (sPDCCH); and a device for obtaining the sDCI by monitoring the sPDCCH based on the determined sCCE.

[0225] In Embodiment 47, the subject matter of Embodiment 46 or any one of the embodiments herein further includes: a device for communicating with a RAN node according to sDCI.

[0226] In embodiment 48, the subject matter of embodiment 46 or any one of the embodiments herein, wherein the number of blind decodings corresponds to a UE-specific search space of a subframe.

[0227] In Embodiment 49, the subject matter of Embodiment 46 or any one of the embodiments herein, wherein the maximum number of BDAs is provided via a field of a radio resource control (RRC) information element (IE) in a reference window.

[0228] In embodiment 50, the subject matter of embodiment 46 or any one of the embodiments herein, wherein the sDCI indicates at least one sCCE of a sPDCCH resource block (RB) set corresponding to a determined sCCE, which is used to transmit information via a physical downlink shared channel (PDSCH).

[0229] In embodiment 51, the subject matter of embodiment 46 or any of the embodiments herein, wherein the sCCE of the sPDCCH is based at least in part on determining the sCCE of the sPDCCH candidate among multiple sPDCCH candidates at an aggregation level (AL) of the UE.

[0230] In embodiment 52, the subject matter of embodiment 46 or any one of the embodiments herein, wherein the multiple sPDCCH candidates at the AL correspond to a specific DCI format.

[0231] In embodiment 53, the subject matter of embodiment 46 or any one of the embodiments herein, wherein multiple sPDCCH candidates are provided to the UE via higher layer signaling.

[0232] In embodiment 54, the subject matter of embodiment 46 or any one of the embodiments herein, wherein the DCI format is provided to the UE via higher layer signaling.

[0233] In embodiment 55, the subject matter of embodiment 46 or any one of the embodiments herein, wherein the search space for sDCI in the PDCCH includes a subset of the search space of the PDCCH used for DCI format monitoring.

[0234] In Embodiment 56, the subject matter of Embodiment 46 or any one of the embodiments herein, wherein the search space of the PDCCH for DCI format monitoring includes a portion for sDCI monitoring and another portion for DCI format monitoring.

[0235] In embodiment 57, the subject matter of embodiment 46 or any one of the embodiments herein, wherein: the sCCEs of the sPDCCH RB set are arranged in a set of sCCE groups (sCCEGs); and the resource block sharing information in the sDCI includes a bitmap indicating unused sCCEGs in the sPDCCH PRB set used for sPDSCH transmission.

[0236] In a fifty-eighth embodiment, a method performed by a user equipment (UE) may include: processing information about a search space of a physical downlink control channel (PDCCH) received from a radio access network (RAN) node for obtaining downlink control information (DCI) from the RAN node; determining a time slot format for communicating with the RAN node based on the DCI obtained from the RAN node, wherein the time slot format indicates for a time slot whether a corresponding symbol is allocated for uplink (UL) communication, downlink (DL) communication, or is identified as a flexible symbol; and communicating with the RAN node according to the time slot format.

[0237] In Embodiment 59, the subject matter of Embodiment 58 or any one of the embodiments herein, wherein a slot format indicator (SFI) monitoring configuration is received via higher layer signaling.

[0238] In embodiment 60, the subject matter of embodiment 58 or any one of the embodiments herein, wherein the device for determining a time slot format includes: receiving multiple time slot formats including the time slot format; and mapping the SFI index field value of the DCI format corresponding to the DCI to the time slot format in the multiple time slot formats.

[0239] In Embodiment 61, the subject matter of Embodiment 58 or any one of the embodiments herein further includes: determining time slot format information of one or more consecutive time slots based on higher layer signaling from the RAN node and a PDCCH carrying a DCI format with an SFI.

[0240] In Embodiment 62, the subject matter of Embodiment 58 or any one of the embodiments herein further includes: determining a serving cell corresponding to the time slot format based on higher layer signaling from a RAN node.

[0241] In embodiment 63, the subject matter of embodiment 58 or any one of the embodiments herein, wherein the search space corresponds to a BWP of a plurality of bandwidth parts (BWPs) used for communication between the UE and the RAN node.

[0242] In Example 64, the subject matter of Example 58 or any one of the embodiments herein further includes: determining the time slot format of another BWP among multiple BWPs based on the determined time slot format of the BWP, the subcarrier spacing (SCS) of the BWP, and the SCS of the other BWP.

[0243] In a sixty-fifth embodiment, a method performed by a user equipment (UE) may include: causing UE capability information to be communicated to a radio access network (RAN) node, the information regarding the maximum number of blind decoding attempts (BDA) supported by the UE; determining a shortened channel control element (sCCE) to be used by the RAN node based on the maximum BDA to transmit shortened downlink control information (sDCI) via a shortened physical downlink control channel (sPDCCH); and obtaining the sDCI by monitoring the sPDCCH based on the determined sCCE.

[0244] In Embodiment 66, the subject matter of Embodiment 65 or any one of the embodiments herein further includes: a device for communicating with a RAN node based on sDCI.

[0245] In embodiment 67, the subject matter of embodiment 65 or any one of the embodiments herein, wherein the number of blind decodings corresponds to a UE-specific search space of a subframe.

[0246] In Embodiment 68, the subject matter of Embodiment 65 or any one of the embodiments herein, wherein the maximum number of BDAs is provided via a field of a radio resource control (RRC) information element (IE) in a reference window.

[0247] In embodiment 69, the subject matter of embodiment 65 or any one of the embodiments herein, wherein the sDCI indicates at least one sCCE of a sPDCCH resource block (RB) set corresponding to a determined sCCE, which is used to transmit information via a physical downlink shared channel (PDSCH).

[0248] In embodiment 70, the subject matter of embodiment 65 or any of the embodiments herein, wherein the sCCE of the sPDCCH is based at least in part on determining the sCCE of the sPDCCH candidate among multiple sPDCCH candidates at an aggregation level (AL) of the UE.

[0249] In Embodiment 71, the subject matter of Embodiment 65 or any of the embodiments herein, wherein the multiple sPDCCH candidates at the AL correspond to a specific DCI format.

[0250] In embodiment 72, the subject matter of embodiment 65 or any one of the embodiments herein, wherein multiple sPDCCH candidates are provided to the UE via higher layer signaling.

[0251] In Embodiment 73, the subject matter of Embodiment 65 or any one of the embodiments herein, wherein the DCI format is provided to the UE via higher layer signaling.

[0252] In embodiment 74, the subject matter of embodiment 65 or any one of the embodiments herein, wherein the search space for sDCI in the PDCCH includes a subset of the search space of the PDCCH used for DCI format monitoring.

[0253] In embodiment 75, the subject matter of embodiment 65 or any one of the embodiments herein, wherein the search space of the PDCCH for DCI format monitoring includes a portion for sDCI monitoring and another portion for DCI format monitoring.

[0254] In embodiment 76, the subject matter of embodiment 65 or any one of the embodiments herein, wherein: the sCCEs of the sPDCCH RB set are arranged in a set of sCCE groups (sCCEGs); and the resource block sharing information in the sDCI includes a bitmap indicating unused sCCEGs in the sPDCCH PRB set used for sPDSCH transmission.

[0255] In the foregoing description, various embodiments have been described with reference to the accompanying drawings. However, it will be apparent that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope set forth in the appended claims. Therefore, the description and drawings should be regarded as illustrative rather than restrictive.

[0256] For example, although reference has been made to Figure 2-Figure 7 A series of signals and / or operations are described, but in other implementations, the order of the signals / operations may be modified. In addition, non-dependent signals may be executed in parallel.

[0257] It will be apparent that in the embodiments shown in the accompanying drawings, the exemplary aspects described above may be implemented in a variety of different forms of software, firmware, and hardware. The actual software code or dedicated control hardware used to implement these aspects should not be construed as limiting. Therefore, the operation and behavior of various aspects are described without reference to specific software code, and it should be understood that software and control hardware can be designed to implement various aspects based on the description herein.

[0258] Although particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to be limiting. In fact, many of these features can be combined in ways not specifically recited in the claims and / or disclosed in the specification.

[0259] Unless explicitly described, no element, action, or instruction used in this application should be construed as critical or essential. As used herein, an instance using the term "and" does not necessarily exclude an interpretation in which the phrase "and / or" is intended for that instance. Similarly, as used herein, an instance using the term "or" does not necessarily exclude an interpretation in which the phrase "and / or" is intended for that instance. In addition, as used herein, the article "a" is intended to include one or more items and may be used with

[0260] The phrase "one or more" is used interchangeably. Where only one item is intended, the term "one," "single," "only" or similar language is used.

Claims

1. An apparatus for a user equipment UE, comprising a baseband processor, the baseband processor being coupled to a memory, the baseband processor being configured to perform operations, the operations comprising: causing UE capability information to be communicated to a radio access network RAN ​​node, the UE capability information relating to a maximum number of blind decoding attempts BDA supported by the UE; determining, based on the maximum number of BDAs, a shortened channel control element sCCE to be used by the RAN node for transmitting shortened downlink control information sDCI via a shortened physical downlink control channel sPDCCH; as well as The sDCI is obtained by monitoring the sPDCCH according to the determined sCCE.

2. The apparatus of claim 1, wherein the operations further comprise: and communicating with the RAN node according to the sDCI. 3 . The apparatus of claim 1 , wherein a maximum number of BDAs corresponds to a UE-specific search space of a subframe. 4 . The apparatus of claim 1 , wherein the maximum number of BDAs is provided via a field of a radio resource control (RRC) information element (IE) in a reference window.

5. The apparatus according to claim 1, wherein the sDCI indicates at least one sCCE of the sPDCCH physical resource block (PRB) set corresponding to the determined sCCE, and the at least one sCCE is used to transmit information via a physical downlink shared channel (PDSCH).

6. An apparatus according to claim 1, wherein the sCCE of the sPDCCH is determined at least in part based on determining the sCCE of an sPDCCH candidate among multiple sPDCCH candidates at an aggregation level AL of the UE.

7. The apparatus of claim 6, wherein the plurality of sPDCCH candidates at the aggregation level AL correspond to a specific DCI format.

8. The apparatus of claim 7, wherein the plurality of sPDCCH candidates are provided to the UE via high-layer signaling.

9. The apparatus according to claim 7, wherein the specific DCI format is provided to the UE via higher layer signaling.

10. The apparatus of claim 1, wherein the search space for the sDCI in the sPDCCH comprises a subset of the search space for the PDCCH used for DCI format monitoring.

11. The apparatus of claim 10, wherein the search space of the PDCCH for DCI format monitoring includes a portion for sDCI monitoring and another portion for DCI format monitoring.

12. The device according to claim 1, wherein: The sCCEs of the sPDCCH physical resource block PRB set are arranged in a set of sCCE groups (sCCEG); and The resource block sharing information in the sDCI includes a bitmap indicating the unused sCCE groups (sCCEGs) in the sPDCCH PRB set used for sPDSCH transmission.

13. A method for user equipment UE, comprising: causing UE capability information to be communicated to a radio access network RAN ​​node, the UE capability information relating to a maximum number of blind decoding attempts BDA supported by the UE; determining, based on the maximum number of BDAs, a shortened channel control element sCCE to be used by the RAN node for transmitting shortened downlink control information sDCI via a shortened physical downlink control channel sPDCCH; as well as The sDCI is obtained by monitoring the sPDCCH according to the determined sCCE.

14. The method according to claim 13, further comprising: and communicating with the RAN node according to the sDCI.

15. The method of claim 13, wherein the maximum number of BDAs corresponds to a UE-specific search space of a subframe.

16. A method for a base station BS, comprising: receiving capability information from a user equipment UE, the capability information relating to a maximum number of blind decoding attempts BDA supported by the UE; determining a shortened channel control element sCCE to be used based on the maximum number of BDAs for transmitting shortened downlink control information sDCI via a shortened physical downlink control channel sPDCCH; as well as The sDCI is transmitted via the sPDCCH according to the determined sCCE.

17. The method of claim 16, wherein the maximum number of BDAs corresponds to a UE-specific search space of a subframe.

18. The method of claim 16, wherein the sCCE of the sPDCCH is determined at least in part based on determining the sCCE of an sPDCCH candidate among a plurality of sPDCCH candidates at an aggregation level AL of the UE.

19. The method of claim 16, wherein the search space of the sDCI in the sPDCCH comprises a subset of the search space of the PDCCH used for DCI format monitoring.

20. The method of claim 16, wherein: The sCCEs of the sPDCCH physical resource block PRB set are arranged in a set of sCCE groups (sCCEG); and The resource block sharing information in the sDCI includes a bitmap indicating the unused sCCE groups (sCCEGs) in the sPDCCH PRB set used for sPDSCH transmission.

Images