Determining and communicating control information in a wireless telecommunications network

Abstract

This disclosure relates to determining and transmitting control information in a wireless telecommunications network. A User Equipment (UE) can receive information about the search space of the 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 the Slot Format (SF) index in the DCI, the UE can determine the slot format for communication with the RAN node and communicate with the RAN node according to the slot format. Additionally, the UE can transmit UE capability information to the RAN node, which may include the maximum number of Blind Decoding Attempts (BDA). The UE can determine a shortened Channel Control Element (sCCE) to be used by the RAN node to transmit the shortened Downlink Control Information (sDCI) via the 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 filed on August 9, 2018, with application number 201880066120.8, entitled "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 August 11, 2017, and U.S. Provisional Patent Application No. 62 / 547,380, filed August 18, 2017, the contents of which are incorporated herein by reference as fully set forth herein. Background Technology

[0004] A wireless telecommunications network may include user equipment (UE) (e.g., smartphones, tablets, laptops, etc.), a radio access network (RAN) (which typically includes one or more base stations), and a core network. A UE connects to the core network by communicating with the RAN and registering with the core network. Communication between the UE and the RAN can be conducted via one or more radio channels.

[0005] In some cases, wireless telecommunications networks may provide control channel information to the UE. Generally, such information informs the UE how the network will transmit information to the UE and / or how each UE can transmit information to the network. Some of this information may be provided to the UE via the Physical Downlink Control Channel (PDCCH) and its corresponding information (such as Downlink Control Information (DCI)). Attached Figure Description

[0006] The embodiments described herein will be more readily understood through the following detailed description in conjunction with the accompanying drawings. For the sake of this description, similar reference numerals may be used to designate similar structural elements.

[0007] In the figures of the accompanying drawings, embodiments are shown by way of example rather than limitation.

[0008] Figure 1 The system architecture of the network according to some implementation schemes is shown;

[0009] Figure 2 This is a flowchart of an exemplary process for determining Slot Format Information (SFI) and communicating with Radio Access Network (RAN) nodes based on the SFI;

[0010] Figure 3 This is a flowchart illustrating an exemplary process for determining an SFI based on an SFI index;

[0011] Figure 4This is a flowchart of an exemplary process for determining the time slot format of multiple cells and / or component carriers (CCs);

[0012] Figure 5 This is a flowchart of another exemplary process for determining the time slot format of multiple cells and / or CCs;

[0013] Figure 6 This is a flowchart of an exemplary process for determining the slot format of CC and / or Bandwidth Component (BWP) with different subcarrier spacing (SCS);

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

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

[0016] Figure 11 This is a schematic diagram of an exemplary subframe for transmitting sDCI via a conventional PDCCH, according to some implementation schemes.

[0017] Figure 12 This is a schematic diagram illustrating an example of dynamic resource sharing of shortened physical downlink control channel (sPDCCH) resource block (RB) sets;

[0018] Figure 13 This is a block diagram of exemplary components of a device according to some implementation schemes;

[0019] Figure 14 This is a block diagram of an exemplary interface of a baseband circuit according to some implementation schemes;

[0020] Figure 15 This is a block diagram of an exemplary control plane protocol stack based on some implementation schemes;

[0021] Figure 16 This is a block diagram of an exemplary user plane protocol stack according to some implementation schemes;

[0022] Figure 17 The components of a core network according to some implementation schemes are shown;

[0023] Figure 18 This is a block diagram illustrating components of a system for supporting Network Functions Virtualization (NFV) according to some exemplary embodiments; and

[0024] Figure 19It is a block diagram of exemplary components according to some exemplary embodiments, 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 or more of the methods discussed herein. Detailed Implementation

[0025] The following detailed description relates to the accompanying drawings. The same reference numerals in different drawings identify the same or similar elements. It should be understood that other embodiments and structural or logical changes may be made without departing from the scope of this disclosure. Therefore, the following detailed description should not be construed as limiting, and the scope of the embodiments is defined only by the appended claims and their equivalents.

[0026] Telecommunications technologies may involve radio access network (RAN) nodes transmitting control information to user equipment (UE) via a physical downlink control channel (PDCCH). Control information may include various types of information, including information about how and when the RAN node and UE communicate with each other (e.g., scheduling information, formatting information, etc.). In some cases, new radio (NR) technologies enable RAN nodes to use a specific type of PDCCH (called a group common PDCCH (GC-PDCCH)) to transmit control information to one or more UEs in a cell. In some cases, the GC-PDCCH may be a specific example of a PDCCH carrying a specific downlink control information (DCI) format. RAN nodes can use the GC-PDCCH to transmit slot format information (or slot format indicator) (SFI), which can indicate, or be used by, 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) communication, which symbols are used for uplink (UL) communication, and which symbols have not yet been allocated for DL ​​or UL communication). The SFI can be transmitted to the UE as downlink control information (DCI). For example, to transmit the SFI to the UE, the RAN node can select a DCI format with one or more fields, which are assigned, distributed, etc., for transmitting the SFI (also known as the "SFI field"). The RAN node can populate the SFI field with the SFI and transmit the DCI to the UE via the GC-PDCCH.

[0027] The techniques described herein enable RAN nodes to provide SFI to UEs using PDCCH (or GC-PDCCH). For example, a UE can communicate with the RAN node to complete a Physical Random Access Channel (PRACH) procedure. The RAN node can provide the UE with a UE-specific PDCCH control resource set (CORESET) (or another type of SFI monitoring configuration) using UE-specific Radio Resource Control (RRC) signaling. This control resource set may include information for monitoring the PDCCH and obtaining SFI from the PDCCH (e.g., time-domain and frequency-domain information, Control Channel Elements (CCE) and Resource Element Groups (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 the PDCCH) that the UE can monitor for SFI intended for use by the UE.

[0028] As described above, the UE can 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 one or more time slots have been allocated to downlink (DL) communication, which symbols have been allocated to uplink (UL) communication, and which symbols have not yet been allocated for DL ​​or UL communication). Furthermore, after determining the SFI, the UE can continue communicating 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 can be used to reduce the overhead that might otherwise be involved in the RAN node providing SFIs to the UE. In some implementations, instead of providing format information separately for each time slot (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 for DL), the RAN node can use higher-layer signaling (e.g., UE-specific RRC signaling) to indicate that the time slot format indicated in one SFI field (in DCI format) may correspond to multiple time slots (e.g., time slots falling within the indicated duration). This reduces the total number of SFI fields used by the RAN node to transmit SFIs. In some implementations, 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 can determine the time slot format to use when communicating with the RAN node by matching the SFI index value and the SFI of the SFI index.

[0030] In some implementations, multiple component carriers (CCs) (e.g., carrier aggregation (CA) scenarios) or bandwidth components (BWPs) may be allocated for communication between the UE and the RAN node. In such scenarios, the RAN node can 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 can 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 communicating with the RAN node according to the SFI of each CC or BWP. Additionally or alternatively, the RAN node can transmit a common CORESET for each UE associated with a specific 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, so that although the common CORESET was initially received, the result may include each UE with a UE-specific CORESET. The UE can 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 as including UE 101 and UE 102. UE 101 and UE 102 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but these UEs may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), pager, laptop computer, desktop computer, wireless handheld terminal, or any computing device that includes a wireless communication interface.

[0032] In some implementations, either UE 101 or UE 102 may include an Internet of Things (IoT) UE or a narrowband (NB-IoT) UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may exchange data with an MTC server or device via technologies such as machine-to-machine (M2M), machine-type communication (MTC), enhanced MTC, via a public terrestrial mobile network (PLMN), proximity-based service (ProSe), or device-to-device (D2D) communication, sensor networks, or IoT networks. 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., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0033] UE 101 and UE 102 can be configured to connect to a radio access network (RAN) 110, for example, a communications-coupled RAN 110, which can be, for example, 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 connections 103 and 104, respectively, where each connection includes a physical communication interface or layer (discussed in further detail below); in this example, connections 103 and 104 are shown as air interfaces for communications coupling and can be consistent with cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Cellular PTT protocol (POC), Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long Term Evolution (LTE) protocol, 5G protocol, New Radio (NR) protocol, etc.

[0034] In this implementation, UE 101 and UE 102 can also directly exchange communication data via ProSe interface 105. ProSe interface 105 may alternatively be referred to as a sidelink interface including one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0035] UE 102 is shown configured to access access point (AP) 106 via connection 107. Connection 107 may include local wireless connectivity, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 106 will include Wireless Fidelity. Router. In this example, AP 106 is shown as the core network connected to the Internet but not to the wireless system (described in further detail below).

[0036] RAN 110 may include one or more access nodes that enable connectivity between 103 and 104. These access nodes (ANs) may be referred to as base stations (BS), 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). RAN 110 may include one or more RAN nodes (e.g., macro RAN node 111) for providing macro cells, and one or more RAN nodes (e.g., low-power (LP) RAN node 112) for providing femtocells or picocells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells).

[0037] Either RAN node 111 or RAN node 112 can terminate the air interface protocol and can be the first contact point for UE 101 and UE 102. In some implementations, either RAN node 111 or 112 can fulfill various logical functions of RAN 110, including but not limited to the functions of the 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 implementations, UE 101 and UE 102 can be configured to communicate with each other or with either RAN nodes 111 and 112 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals, based on various communication technologies, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication), but the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0039] In some implementations, the downlink resource grid can be used for downlink transmissions from either RAN node 111 or RAN node 112 to UE 101 and UE 102, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and 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 comprises multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements. In the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0040] The Physical Downlink Shared Channel (PDSCH) delivers user data and higher-layer signaling to UE101 and UE102. The Physical Downlink Control Channel (PDCCH) carries information about the transmission format and resource allocation associated with the PDSCH channel. It also notifies UE101 and UE102 of the transmission format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information associated with the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE102 within the cell) can be performed at either RAN Node 111 or RAN Node 112 based on channel quality information fed back from either UE101 or UE102. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., allocated to) each of UE101 and UE102.

[0041] The PDCCH can use Control Channel Elements (CCEs) to transmit control information. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to a set of 12 Physical Resource Elements (PRESIs).

[0042] Each REG (containing three resource elements of the PDCCH demodulation reference signal (DMRS)) is 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 channel conditions, one or more CCEs can be used to transmit the PDCCH. Different PDCCH transmissions with different numbers of CCEs as defined in the NR can exist (e.g., aggregation levels, L = 1, 2, 4, 8, or 16).

[0043] Some implementations can use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations can utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. EPDCCH can be transmitted using one or more enhanced control channel elements (ECCEs). Similarly, each ECCE can correspond to a set of nine physical resource elements, called an enhanced resource element group (EREG). In some cases, an ECCE can have a different number of EREGs.

[0044] RAN 110 is shown communicatively coupled to core network (CN) 120 via S1 interface 113. In this 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 serving gateway (S-GW) 122; and S1-Mobility Management Entity (MME) interface 115, which is the signaling interface between RAN nodes 111 and 112 and MME 121.

[0045] In this implementation, 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 functionally resemble the control plane of a legacy General Packet Radio Service (GPRS) Support Node (SGSN). MME 121 can manage mobility aspects of access, such as gateway selection and tracking area list management. HSS 124 may include a database for network users, containing subscription-related information to support network entities in handling communication sessions. Depending on the number of mobile subscribers, equipment capacity, network organization, etc., CN 120 may include one or more HSS 124s. For example, HSS 124 may provide support for routing / roaming authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0046] S-GW 122 can terminate the S1 interface 113 facing RAN 110 and route data packets between RAN 110 and CN 120. Additionally, S-GW 122 can serve as a local mobility anchor for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, billing, and enforcement of certain policies.

[0047] P-GW 123 can terminate the SGi interface toward the PDN. P-GW 123 can route data packets between EPC network 123 and external networks, such as networks including application server 130 (alternatively referred to as application function (AF)), via Internet Protocol (IP) interface 125. Generally, application server 130 can be an element that provides IP-bearing resources for use with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this embodiment, P-GW 123 is shown communicatively coupled to application server 130 via IP communication interface 125. Application server 130 can 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 UE 101 and UE 102 via CN 120.

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

[0049] Provided for illustrative purposes only Figure 1 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 [other devices and / or networks]. Figure 1The devices and / or networks are 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 in system 100 may be described as performing one or more functions by other devices in system 100. Additionally, the devices of system 100 may be interconnected with each other and / or with other devices via wired connections, wireless connections, or a combination of wired 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 physically attached to those other devices. Furthermore, although... Figure 1 While some devices may be shown to have a “direct” connection, in practice, some of these devices may communicate with each other via one or more additional devices and / or networks.

[0050] Figure 2 This is a flowchart of an exemplary procedure 200 for determining the SFI and communicating with RAN node 111 based on the SFI. Procedure 200 can be implemented by UE 101. In some implementations, Figure 2 One or more of the operations described herein may be wholly or partially performed by another device such as the one mentioned above. Figure 1 One or more of the aforementioned devices may be used to perform this action. Additionally... Figure 2 The examples provided are non-restrictive. In practice, Figure 2 Examples may include fewer, additional, and / or alternative operations and / or functions.

[0051] As shown in the figure, 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-specific SFI monitoring configuration (described below) to UE 101 using UE-specific RRC signaling. This monitoring configuration may indicate a set of PDCCH candidates using a specific aggregation level (AL) (e.g., GC-PDCCH) and the portion thereof to be used by RAN node 111 to transmit SFI to UE 101. As described herein, the SFI monitoring configuration may include receiving and / or implementing CORESET information in whole or in part.

[0052] Process 200 may also include monitoring the SFI using a PDCCH based on an SFI monitoring configuration (block 220). For example, the SFI monitoring configuration obtained by UE 101 may include a CORESET and a search space configuration. The CORESET may include information such as time-domain and frequency-domain information, control channel element (CCE) and resource element group (REG) mapping information, etc., and the search space configuration 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). Therefore, UE 101 can use the SFI monitoring configuration to determine, identify, monitor, etc., the PDCCH used by RAN node 111 and / or obtain the SFI intended for use by UE 101 from the PDCCH.

[0053] Process 200 may also include determining the time slot format for communication 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 time slots) have been assigned to DL transmissions, UL transmissions, and / or symbols that have not yet been assigned for either type of transmission (which may also be referred to as other symbols, open symbols, flexible symbols, unknown symbols, etc.). Therefore, UE 101 may use the SFI to determine the time slot format for communication with RAN node 111.

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

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

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

[0057] In some implementations, UE 101 and RAN node 111 may implement an indexing system for transmitting SFIs. For example, RAN node 111 may use UE-specific RRC signaling to provide UE 101 with indexes of different timeslot formats (and / or another type of data structure). Therefore, instead of transmitting an SFI that fully describes the timeslot format, RAN node 111 may instead provide an index value or another type of identifier (e.g., in the SFI field of a specific DCI format) that corresponds to the timeslot format of the index provided to UE 101, and UE 101 may use the index value from the DCI to determine the timeslot format to use for communication with RAN node 111. In scenarios involving multi-pole CCs or BWPs, RAN node 111 may provide an index value for each CC or BWP, and / or information that enables 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 timeslot format, RAN node 111 may transmit a single index value along with an indication of which CCs or BWPs correspond to the timeslot format of the index value.

[0058] Figure 3 This is a flowchart of an exemplary process 300 for determining an SFI based on an SFI index. Process 300 may be implemented by UE 101. In some implementations, Figure 3 One or more of the operations described herein may be wholly or partially performed by another device such as the one mentioned above. Figure 1 One or more of the aforementioned devices may be used to perform this action. Additionally... Figure 3 The examples provided are non-restrictive. Additionally, Figure 3 The examples provided are non-restrictive. In practice, Figure 3 Examples may include fewer, additional, and / or alternative operations and / or functions.

[0059] As shown in the figure, 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 specific aggregation level (AL) and the portion of them to be used by RAN node 111 to transmit SFI to UE 101.

[0060] Process 300 may include obtaining an SFI index corresponding to different slot formats via UE-specific RRC signaling (box 320). As described herein, the SFI index may include a list, table, array, or another type of data structure comprising one or more slot formats, each associated with a different identifier (e.g., an 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 multiple slots. The number of slots (and / or portions of PDCCH and / or GC-PDCCH) associated with a candidate slot format may be configured via higher-level signaling such as RRC signaling.

[0061] Process 300 may include receiving an SFI index from the PDCCH based on an SFI monitoring configuration (box 330). For example, UE 101 may monitor the GC-PDCCH used by RAN node 111 to transmit control information. Additionally, based on the SFI monitoring configuration obtained from RAN node 111, UE 101 may determine the SFI in UE 101's GC-PDCCH. 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) containing one or more SFI indices. Thus, the SFI index may be provided as a specific field (SFI field) in the DCI format used by RAN node 111 to provide control information to UE 111.

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

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

[0064] Figure 4This is a flowchart of an exemplary procedure 400 for determining the time slot format of multiple cells and / or component carriers (CCs). Procedure 400 may be implemented by UE 101. In some implementations, Figure 4 One or more of the operations described herein may be wholly or partially performed by another device such as the one mentioned above. Figure 1 One or more of the aforementioned devices may be used to perform this action. Additionally... Figure 4 The examples provided are non-restrictive. In practice, Figure 4 Examples may include fewer, additional, and / or alternative operations and / or functions.

[0065] As shown in the figure, 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 the PDCCH (e.g., GC-PDCCH) and / or the portion thereof to be used by RAN node 111 to transmit 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, a wireless telecommunications network may support carrier aggregation (CA), which may include networks communicating with UE 101 via multiple cells and / or CCs. In some scenarios, two or more cells and / or CCs may use the same timeslot 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 timeslot format. As described below, providing such information to UE 101 enables UE 101 to determine the timeslot formats of multiple cells and / or CCs based on a single timeslot format (e.g., a single instance of SFI from RAN node 111). In some implementations, the information received from RAN node 111 may include timeslot formats and indications of cells and / or CCs corresponding to (e.g., implementations) each timeslot 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 a portion thereof (e.g., GC-PDCCH) RAN node 111 may use to transmit an SFI to UE 101. Thus, UE 101 may monitor and receive the SFI from the indicated PDCCH.

[0068] Process 400 may include determining the time slot format of multiple cells and / or CCs by mapping SFIs to CCs and / or cells (block 440). For example, UE 101 may determine the time slot format indicated by the SFI from RAN node 111 via GC-PDCCH and map that time slot format to previously received information about which cells and / or CCs use each time slot format via UE-specific RRC signaling. In determining the match between the SFI from GC-PDCCH and the time slot format from 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 time slot format. In some embodiments, multiple cells and / or CCs may implement the same time slot format.

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

[0070] Figure 5 This is a flowchart of an exemplary procedure 500 for determining the time slot format of multiple cells and / or CCs. Procedure 500 may be implemented by UE 101. In some embodiments, Figure 5 One or more of the operations described herein may be wholly or partially performed by another device such as the one mentioned above. Figure 1 One or more of the aforementioned devices may be used to perform this action. Additionally... Figure 5 The examples provided are non-restrictive. In practice, Figure 5 Examples may include fewer, additional, and / or alternative operations and / or functions.

[0071] As shown in the figure, process 500 may include obtaining an SFI monitoring configuration via UE-specific RRC signaling (box 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 specific aggregation level (AL) and / or the portion thereof to be used by RAN node 111 to transmit 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 part thereof RAN Node 111 may use 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 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). RAN Node 111 may provide the SFI in a field of DCI information (e.g., as an SFI field for a specific DCI format). In some implementations, as described herein, some or all of the SFIs provided by RAN Node 111 may be provided in an additional or alternative form, such as different types of DCI information, different fields for a specific DCI format, etc.

[0073] Process 500 may also include determining the time slots to which the SFI applies via UE-specific RRC signaling (block 530). For example, while the SFI may indicate the format of one or more time slots, RAN node 111 may use RRC signaling to indicate to UE 101 the time slots to which the SFI can be applied, which may include multiple or a series of consecutive time slots. Thus, 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 RAN node 111), and UE 101 may rely on UE-specific RRC signaling to determine the specific time slots to which the SFI applies. In this way, RAN node 111 may, for example, not transmit the SFI for each time slot. Instead, RAN node 111 may use RRC signaling to indicate the time slots and / or the number of slots to which that type of time slot format applies, and then transmit a type of time slot format via PDCCH.

[0074] Process 500 may also include determining the cell and / or CC to which the SFI applies via UE-specific RRC signaling (block 540). As described above, 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 timeslot format. Therefore, RAN node 111 may use RRC signaling to inform UE 101 which cells and / or CCs are using the same timeslot format, such that, for example, RAN node 111 does not transmit the same or similar SFIs to UE 101 (e.g., redundant SFIs).

[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 regarding the 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. Therefore, UE 101 may continue to send and receive information from the RAN according to the timeslot format determined by UE 101.

[0076] Figure 6 This is a flowchart of an exemplary procedure 600 for determining the slot format of a CC and / or BWP with different subcarrier spacings (SCS). Procedure 600 may be implemented by UE 101. In some embodiments, Figure 6 One or more of the operations described herein may be wholly or partially performed by another device such as the one mentioned above. Figure 1 One or more of the aforementioned devices may be used to perform this action. Additionally... Figure 6 The examples provided are non-restrictive. In practice, Figure 6 Examples may include fewer, additional, and / or alternative operations and / or functions.

[0077] As shown in the figure, 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 the PDCCH and / or the portion thereof to be used by RAN node 111 to transmit SFI to UE 101 (e.g., GC-PDCCH).

[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 part thereof RAN Node 111 may use 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 timeslot 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 timeslot format identifiers or indexes (which may be mapped to a specific timeslot format previously provided to UE 101 by RAN Node 111 via RRC signaling). RAN Node 111 may provide the SFI in a field of a DCI (e.g., as an SFI field for a specific DCI format). In some implementations, as described herein, some or all of the SFIs provided by RAN Node 111 may be provided in an additional or alternative form, such as different types of DCIs, different fields for a specific DCI format, etc.

[0079] Process 600 may also include determining the slot format of a CC and / or BWP among multiple CCs and / or BWPs of UE 101 based on SFI and UE-specific RRC signaling (block 630). For example, because UE 101 may be configured to use multiple CCs and / or BWPs to communicate with the network, UE 101 may also be configured to determine the slot format of each CC and / or BWP. Therefore, UE 101 may use one or more of the techniques described herein to determine the slot format based on SFI and UE-specific RRC signaling from RAN node 111, examples of which may include receiving explicit format information for each individual slot, mapping slot format values ​​(e.g., index values ​​of SFI fields) to indexes of template slot formats, applying a type of slot format (e.g., a specific combination of DL, UL, or flexible symbols for the slot) to multiple or a series of consecutive slots, etc.

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

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

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

[0083] In addition to the examples above, a finite number of bits (e.g., 2 to 4 bits) can be used in the SFI of a single CC or BWP to indicate the overall space from possible slot formats (e.g., 3 for a 7-symbol slot and 3 for a 14-symbol slot). 7 Or 3 14 The SFI of the time slot format set configured via a higher layer (e.g., UE-specific RRC signaling). The candidate set of time slot formats can be configured separately for 7-symbol time slots and 14-symbol time slots.

[0084] Additionally, for GC-PDCCH carrying SFI of the cell and / or CC, UE 101 may be configured with a CORESET. In some implementations, 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 implementation, instead of a single common CORESET for multiple UEs 101, multiple instances of GC-PDCCH may be transmitted by RAN node 101 within the CC or BWP according to different UE-specific or common CORESETs, and higher-layer signaling specific to UEs or UE groups may be used to configure the corresponding CORESET to different UEs 101 to monitor GC-PDCCH with SFI.

[0085] Additionally, an SFI can be indicated for multiple time slots, with the number of time slots indicated via the GC-PDCCH. For example, two bits can be used to indicate the number of time slots to which the SFI applies. In another implementation of this example, two bits in the GC PDCCH can be used to indicate one of four values ​​for the number of time slots to which the SFI can be applied, where the four values ​​are configured via higher layers (e.g., via NR Minimum System Information (MSI), NR Residual Minimum System Information (RMSI), NR System Information Block (SIB), or UE-specific Radio Resource Control (RRC) signaling). In some implementations, an SFI for multiple time slots may not include a time slot format for some reserved time slots (e.g., time slots used to transmit synchronization signal (SS) blocks, physical random access channels (PRACH), etc.). In another example, the M bit can be used in the GC-PDCCH to indicate the number of time slots as described above. M A value of -1 can be used, and a code point can be used to indicate that the number of slots for the SFI is equal to the monitoring periodicity of the GC-PDCCH carrying the SFI. In the latter case, this may mean that the indicated SFI applies to all 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 leveraging the availability of multiple transmit and / or receive antennas at the UE and / or RAN nodes. The 3GPP LTE communication standard introduces shorter or shortened transmission time intervals (sTTIs) (also known as microslots) to better accommodate services and devices with high latency requirements (e.g., services and devices that may be affected by latency). sTTIs can be implemented by dividing a 1-millisecond (ms) subframe into multiple TTIs, or in other words, by specifying TTIs with durations shorter than the subframe (e.g., 1 ms). For example, by dividing a subframe into 6 sTTIs, a 1-ms subframe with 14 symbols can be used to implement sTTIs, where 4 of the sTTIs are 2 symbols each, and 2 of the sTTIs are 3 symbols each (a total of 14 symbols). While using sTTIs increases the RAN's ability to accommodate services and devices with high latency requirements, it also increases 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, UE 101 may inform RAN node 111 about the UE's blind decoding capabilities (e.g., the maximum number of blind decoding attempts (BDAs) that UE 101 may make within an sTTI, subframe, or another reference time window). Alternatively, with respect to CA, the maximum number of BDAs for UE 101 may be indicated on a per CC basis. In some embodiments, UE 101 may determine its aggregation level (AL) and transmit it to RAN node 111, which may be based on the signal-to-noise ratio (SNR) measured by 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 can indicate or be used to indicate the number of shortened channel control entities (sCCEs) to be used to transmit DCI from RAN node 111 to UE 101. For example, an AL of 2 indicates that 2 sCCEs are to be used to transmit DCI, and an AL of 4 indicates that 4 sCCEs can be used to transmit DCI.

[0088] Based on the blind decoding capability of UE 101 and / or AL (and / or one or more other factors described herein), RAN node 111 can determine the location within the sPDCCH that includes DCI for UE 101 (e.g., which sTTI and / or CCE are used to transmit DCI within the sPDCCH). UE 101 can determine, based on the UE's AL, potential or candidate sPDCCH resources (e.g., sTTI, CCE, etc.) and / or DCI format that RAN node 111 can use to transmit DCI. Additionally, UE 101 can monitor the sPDCCH (based on the determined potential or candidate sPDCCH resources) to obtain DCI from RAN node 111 and use the DCI to further communicate with RAN node 111. References below. Figures 7-12 Discuss the details of this type of technology and other technologies.

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

[0090] As shown in the figure, UE 101 can transmit UE capability information to RAN node 111 (at 710). The UE capability information may include the maximum number of BDAs that UE 101 can be configured to use during the sTTI. In some implementations, the maximum number of BDAs can be indicated on a per CC basis, with respect to CA. The number of BDAs supported by the UE (e.g., for CC) can be a field value (X) to minimize control signaling overhead, where X can be an integer (e.g., X = 32). In some implementations, further reduction in signaling overhead can be achieved by defining an information element field (e.g., sMaxBlindDecoding) to indicate the maximum number of BDAs within 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 a conventional TTI length (e.g., 1 ms). This technique mitigates the need for UE 101 to send multiple messages to RAN node 101 for different sTTI lengths.

[0091] Additionally or alternatively, UE capability information may include the AL of UE 101. The UE's AL may be based on the SNR measured by the UE and may indicate (or be used to indicate) the number of sCCEs to be used to transmit the DCI from RAN node 111 to UE 101. For example, an AL of 1 may indicate that 1 sCCE is to be used to transmit the DCI, an AL of 2 may indicate that 2 sCCEs are to be used to transmit the DCI, and an AL of 4 may indicate that 4 sCCEs are to be used to transmit 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 can be organized into one or more resource element groups (REGs), and an sCCE may include a portion of a CCE.

[0092] RAN node 111 can determine sCCE candidates (including multiple candidates and their positions in the sPDCCH area) for transmission of shortened DCI (sDCI) (at 720 and 730) based on the maximum BDA capability reported by UE 101. For example, UE 101 may include formulas, procedures, and data structures (e.g., tables, arrays, etc.) that enable UE 101 to determine sCCE candidates based on the maximum BDA supported by UE 101. As described herein, CCE may include one or more resource elements (REs) that can be organized into one or more resource element groups (REGs). As described herein, sCCE may include a portion of a CCE. Additionally, sCCEs corresponding to sPDCCH candidates (e.g., a portion of the sPDCCH available for transmitting DCI information) can be determined based on various factors such as UE 101's AL, 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 sTTI, etc. For example, the sCCE corresponding to the sPDCCH candidate (m) at AL in the UE-specific sTTI search space can be given by the following formula:

[0093]

[0094] Where i = 0, ..., L-1 and N sCCE,P k can be the total number of sCCEs in the sPDCCH PRB set p, k can be the sTTI index (or another type of identifier value), and b = 0 is used for the self-scheduled case, and b = n CI Otherwise, where n CI This is the carrier indicator field value. M can include the maximum number of sPDCCH candidates that can be configured for sPDCCH monitoring in sTTI, and M (L) This may include a maximum number of sPDCCH candidates that can be configured for sPDCCH monitoring in a specific ALL at a given sTTI. Each sPDCCH PRB set can be configured for local or distributed sPDCCH transmission. In some implementations, Y P,k It can be configured to have higher layers (e.g., in) Figure 7 The value of the corresponding sPDCCH resource block (RB) set is set in a UE-specific manner before or during the RRC signaling process 700.

[0095] In some implementation schemes, Y P,k The following can be provided and / or determined:

[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 can be used to determine the number of sPDCCH candidates m E{0,1,...,M}. p (L) Configure the sPDCCH resource set (p) for a sTTI. In some implementations, UE 101 may be configured with M p (L) It can 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 can be the maximum number of sPDCCH candidates that can be configured for sPDCCH monitoring in sTTI, and ∑∑ L,p M p (L) ≤M. For the sPDCCH resource set, M p (L) At least one AL can be non-zero. Since different numbers of sTTIs can exist within a subframe for 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. Simultaneously, 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. These two sets of ALs may partially overlap or not. In other words, an element of one configuration may be a subset of the elements of another configuration (i.e., completely overlapping; for example, one configuration may include {1,2,4}, while another configuration may include {1,2,4,8}). In some other embodiments, elements of the two configurations may have at least one different value; for example, one configuration may include {1,2,4}, while the other may include {1,8}.

[0098] In some implementations, a subset of the first AL set and / or the second AL set may be configured by a higher layer, for example, based on the DL SNR, as part of the sPDCCH resource RB set configuration for UE 101. For example, for a 2-symbol sTTI operation, LE{1,2} may be configured for UE 101 with a high DL SNR; while LE{2,4} may be configured for UE 101 with a low DL SNR. Additionally or alternatively, 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 (i.e., M) per sTTI can be determined based on the sTTI length, and this maximum number may differ for 2-symbol sTTIs and slot-based sTTIs. In some implementations, M may be 4 or 6 for 2-symbol sTTIs, while M may be 16 or 18 for slot-based sTTIs, with the aim of having the same number of BDAs for 2-symbol and slot-based sPDCCHs on the subframe. In some implementations, for the sPDCCH resource set, the corresponding BDA for each AL can be configured by a higher layer (e.g., for UE101 with good SNR, BDA{3,2,1} is used for AL{1,2,4}, and for UE101 with poor SNR, BDA{0,4,2} is used for AL{1,2,4}). This approach provides RAN node 111 with sufficient flexibility to adapt to changes in radio channels in terms of available ALs and to reduce the probability of signal congestion occurring in terms of the location of sPDCCH candidates.

[0099] According to some implementation schemes, UE 101 operating in an sTTI system (e.g., an sTTI-enabled RAN) can be configured to have higher-level 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 the serving cell (e.g., RAN node 111). In such a scenario, the corresponding number of sPDCCH candidates can be determined as follows:

[0100]

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

[0102] The number of sPDCCH candidates has decreased. The value of a 0 0 1 0.33 2 0.66 3 1

[0103] Table 1: Scaling factor for reduced sPDCCH candidates

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

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

[0106] Figures 8-10 These are schematic diagrams of exemplary sREG 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 configuring two cell-specific reference signal (CRS) port transmission diversity, the first 10 available REs (e.g., SFBC pairs 810-850) can be grouped into 5 Spatial Frequency Block Coded (SFBC) pairs using Alamouti codes in the frequencies, which are labeled in REG 800 with a combination of uppercase letters A through E. For the remaining REs (sCCE 660, labeled E0), the modulation symbols transmitted in the first RE of the adjacent SFBC pair (e.g., E0 in SFBC pair 850) can be repeated and transmitted at each CRS antenna port, for example, to provide greater spatial diversity gain.

[0107] See Figure 9 In sREG 900, when configured with 4 CRS ports for transmission diversity, the first 8 available REs can be organized into two SFBC pairs, 910 and 920. For the remaining 3 available REs, the first three modulation symbols transmitted in the first three REs of adjacent SFBC pairs (e.g., sCCE B1, B3, and B2 of SFBC pair 920) can be repeated and transmitted in REG 930 respectively. Figure 10As shown, the exemplary sREG 1000 may include a similar arrangement of REs for 4-port SFBC pairs and SFBC pairs 1010 and 1020. However, the remaining REs 1030 may be repeated in different ways (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 repeating REs and / or RE sequences (e.g., B1, B2, B4, etc.) for repeating REs of adjacent SFBC pairs.

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

[0109] like Figure 11 As shown, in some implementations, the search space for sDCI in the PDCCH area can be a subset of the search space for the PDCCH used for DCI format monitoring. For example, suppose UE101 is configured to monitor M in the UE-specific search space (USS) on the PDCCH area. L Candidates, then UE 101 can search for M L The first set of PDCCH candidates within the candidate region is used for sDCI monitoring. In one implementation, the first set of PDCCH candidates within the PDCCH region can be the first set used to obtain sDCI. PDCCH candidates, among which This can be the number of sPDCCH candidates used for sDCI format monitoring, which can be configured by higher layers (e.g., via RRC signaling) on ​​a per AL and / or per UE 101 basis. Furthermore, UE 101 can be configured for continuous monitoring of the DCI format (M... L - PDCCH, where M L This can be the total number of candidates that the UE needs to monitor in the PDCCH area.

[0110] Therefore, 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 sDCI format in the PDCCH area 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 conventional) search space for DCI format monitoring. This provides 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 implementations, sDCI can be mapped to the same search space of the DCI format on the PDCCH. In such implementations, an indicator (e.g., a value of 0) can be appended to the sDCI format until the payload size is equal to the payload size of the DCI format, to, for example, avoid additional BDA from UE101. To distinguish it from the normal DCI format, a dedicated radio network temporary identifier (RNTI) can be assigned to UE101 and can be used to scramble the sDCI format cyclic redundancy check (CRC). In some implementations, a UE-specific search space (e.g., ...) is used for sDCI. Figure 11 Part 1110) can be determined based on the dedicated RNTI assigned to UE 101 for sTTI operations. Additionally or alternatively, the number of ALs and the number of PDCCH candidates per AL can be configured via RRC signaling.

[0112] In some implementations, the reduction of a single parameter PDCCH candidate can be configured by a higher layer (e.g., RRC signaling) and is typically applied to a UE-specific search space (e.g., Figure 11 Parts 1110 and 1120) are used for sDCI and DCI format monitoring performed by UE 101. In some implementations, the PDCCH candidate reduction may be 0.6 and / or for AL1 may be configured by a higher layer (e.g., RRC signaling). Additionally or alternatively, in a UE-specific search space (e.g., Figure 11 There can be 6 PDCCH candidates in a combination of parts 1110 and 1120. In such an implementation, a UE-specific search space (e.g., Figure 11 Part 1110) can be determined to consist of a first [0.6×6] = 4 PDCCH candidates, and another UE-specific search space (e.g., Figure 11 Part 1120) can be determined to consist of the remainder of the six PDCCH candidates (i.e., two PDCCH candidates) given an AL (e.g., AL 1). Furthermore, a UE-specific search space (e.g., for the PDCCH area used for sDCI monitoring) is also defined. Figure 11 The total number of PDCCH candidates in part 1110) can be less than the total number of PDCCH candidates in other sTTIs of the same subframe, so as to ensure, for example, that the total number of BDs per sTTI per CC is the same across all TTIs of the subframe.

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

[0114] Figure 12 This is a schematic diagram of Example 1200 for dynamic resource sharing of the sPDCCH RB set. As shown, the sPDCCH RB set may include 8 sCCEs indexed from 0-7 (in this case, N sCCE =8). sCCE can be arranged in 3 different sCCEGs indexed from 0 to 3. In addition, each sCCEG can correspond to a bitmap field (e.g., with a specific sDCI format) that includes three bitmap values ​​(bO, b1, and b2) corresponding to the different sCCEG indices.

[0115] Assuming that UE 101 uses sCCE 0 for sPDCCH transmission and UE 101 uses sCCE 4 and 5 for sPDCCH transmission, the bitmap field (e.g., bO) used to schedule the sPDSCH of UE 101 can be set to (1,1,0) (where "1" indicates that sCCEG is in use and "0" indicates that 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 allocated for sPDSCH to UE 101 overlap with the sPDCCH RB set, UE 101 can recognize that sCCEG 2 is available for sPDSCH.

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

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

[0118] In some implementations, one or more sPDCCH PRB sets may be assigned to UE 101 for sPDCCH monitoring, which may range from 0 to N. sCCE The set of logic sCCEs numbered -1, where N sCCE The number of sCCEs in an sPDCCH resource set can be specified, and each sPDCCH RB set can be configured as contiguous or non-contiguous PRBs. In such implementations, sCCEs can be logically grouped into sets of sCCE groups (sCCEGs). Additionally or alternatively, UE 101 and / or RAN node 111 can 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 B is the number of sCCEs of sCCEG x in the sPDCCH PRB set, and B can be a predefined value (e.g., a value defined by the 3GPP communication standard). Additionally or alternatively, B can be a function of system bandwidth (e.g., the bandwidth available to UE 101 and / or RAN node 111), or alternatively, B can be configured by a higher layer on a per-UE basis (e.g., configured by UE-specific RRC signaling).

[0123] Alternatively, in some implementations, RAN node 111 may use the following procedure to distribute the number of sCCEAs as evenly as possible among each sCCEG. There may be N + =N sCCE mod BsCCEG, where each is composed of C + =[N sCCE It consists of / r]sCCE. Simultaneously, it may exist that consists of [N] sCCE / r]sCCE composed of C_=rC + sCCEG. In some implementations, N sCCE It can be used to count sCCEs, in addition to the sCCEs detected by a given UE 101 for sPDCCH transmission.

[0124] In some implementation schemes, N sCCE sCCEs can be counted, except for those detected by a given UE for sPDCCH transmission.

[0125] Additionally, in sDCI for sPDSCH resource allocation based on sRBG, resource block sharing information includes a bitmap indicating unused sCCEGs in the sPDCCHPRB set, which can be allocated to the scheduled UE 101 for sPDSCH transmission. The bitmap size is r bits, with one bitmap bit for each sCCEG, making each sCCEG (if not used for sPDCCH in sTTI) addressable for Spdsch transmission. The order of sCCEG bitmap 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 in the bitmap is 1, the sCCEG can be allocated to the UE; otherwise, the sCCEG may not be allocated to the UE 101.

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

[0127] Application circuitry 1302 may include one or more application processors. For example, application circuitry 1302 may include circuitry 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 device 1300. In some embodiments, the processor of application circuitry 1302 may process IP data packets received from the EPC.

[0128] Baseband circuitry 1304 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 1304 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuitry 1306 and generate baseband signals for the transmit signal path of RF circuitry 1306. Baseband processing circuitry 1304 may interact with application circuitry 1302 to generate and process baseband signals and control the operation of RF circuitry 1306. For example, in some embodiments, baseband circuitry 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 existing, under development, or future generations of baseband processors 1304D (e.g., second-generation (2G), sixth-generation (6G), etc.). The baseband circuitry 1304 (e.g., one or more of baseband processors 1304A-1304D) can handle various radio control functions capable of communicating with one or more radio networks via RF circuitry 1306. In other embodiments, some or all of the functions of the baseband processors 1304A-1304D may be included in modules stored in memory 1304G and executed via a central processing unit (CPU) 1304E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, RF shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 1304 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 1304 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions.

[0129] Implementations of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other implementations.

[0130] In some embodiments, the baseband circuitry 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 in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all components of the baseband circuitry 1304 and the application circuitry 1302 may be implemented together, such as on a system-on-a-chip (SoC).

[0131] In some implementations, baseband circuitry 1304 can provide communication compatible with one or more radio technologies. For example, in some implementations, baseband circuitry 1304 can support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN). Implementations in which baseband circuitry 1304 is configured to support radio communication using more than one radio protocol may be referred to as multi-mode baseband circuitry.

[0132] RF circuit 1306 can communicate with a wireless network using modulated electromagnetic radiation over a non-solid medium. In various embodiments, RF circuit 1306 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 1306 may include a receive signal path that includes circuitry for frequency conversion of an RF signal received from FEM circuit 1308 and supplying a baseband signal to baseband circuit 1304. RF circuit 1306 may also include a transmit signal path that includes circuitry for frequency conversion of the baseband signal provided by baseband circuit 1304 and supplying an RF output signal for transmission to FEM circuit 1308.

[0133] In some embodiments, the receive signal path of RF circuit 1306 may include mixer circuit 1306a, amplifier circuit 1306b, and filter circuit 1306c. In some embodiments, the transmit signal path of RF circuit 1306 may include filter circuit 1306c and mixer circuit 1306a. RF circuit 1306 may also include synthesizer circuit 1306d for synthesizing the frequency used by mixer circuit 1306a in both the receive and transmit signal paths. In some embodiments, mixer circuit 1306a in the receive signal path may be configured to down-convert the RF signal received from FEM circuit 1308 based on the synthesized frequency provided by synthesizer circuit 1306d. Amplifier circuit 1306b may be configured to amplify the down-converted signal, and filter circuit 1306c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal can be provided to the baseband circuit 1304 for further processing. In some embodiments, although not required, the output baseband signal may be a zero-frequency baseband signal. In some embodiments, the mixer circuit 1306a receiving the signal path may include a passive mixer, but the scope of the embodiments is not limited in this respect.

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

[0135] In some embodiments, the mixer circuit 1306a for the receive signal path and the mixer circuit 1306a for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuit 1306a for the receive signal path and the mixer circuit 1306a for 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 for the receive signal path and the mixer circuit 1306a for the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 1306a for the receive signal path and the mixer circuit 1306a for 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, the RF circuit 1306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuit 1304 may include a digital baseband interface for communicating with the RF circuit 1306.

[0137] In some dual-mode implementations, separate radio IC circuits can be provided to process signals for each spectrum, but the scope of the implementation is not limited in this respect.

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

[0139] Synthesizer circuit 1306d can 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 can be a fractional N / N+1 synthesizer.

[0140] In some implementations, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not mandatory. The divider control input may be provided by the baseband circuit 1304 or the application processor 1302 according to the desired output frequency. In some implementations, 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 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 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 elements 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. Thus, 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 may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 1306 may include an IQ / polarity converter.

[0143] FEM circuit 1308 may include a receive signal path, which 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 RF circuit 1306 for further processing. FEM circuit 1308 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by RF circuit 1306 for transmission through one or more of the one or more antennas 1310. In various embodiments, amplification via the transmit or receive signal path may be performed only in RF circuit 1306, only in FEM 1308, or in both RF circuit 1306 and FEM 1308.

[0144] In some embodiments, FEM circuit 1308 may include a TX / RX switch to switch between transmit 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 the received RF signal and provide the amplified received RF signal as an output (e.g., provided to RF circuit 1306). The transmit signal path of FEM circuit 1308 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by RF circuit 1306); and one or more filters for generating RF signals for subsequent transmission (e.g., through one or more of one or more antennas 1310).

[0145] In some implementations, the PMC 1312 can manage the power supplied to the baseband circuitry 1304. Specifically, the PMC 1312 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 1312 is typically included when the device 1300 can be battery powered, for example, when the device is included in a UE. The PMC 1312 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0146] Although Figure 13 The PMC 1312 is shown coupled only to the baseband circuit 1304. However, in other embodiments, the 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 implementations, PMC 1312 can control or otherwise become part of various power-saving mechanisms of device 1300. For example, if device 1300 is in an RRC connected state, where the device remains connected to the RAN node as expected to receive traffic for short periods, it can enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, device 1300 can be powered down for short intervals, thereby saving power.

[0148] If there is no data traffic activity during the extended period, device 1300 can transition to the RRCJdle state, in which the device disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 1300 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network, and then powers off again. Device 1300 cannot receive data in this state; to receive data, it must transition back to the RRC connected state.

[0149] An additional power-saving mode allows the device to be unavailable from the network for periods exceeding the paging interval (ranging from seconds to hours). During this time, the device is completely unconnected to the network and can be completely powered off. Any data sent during this period will incur significant latency, which is assumed to be acceptable.

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

[0151] The application circuit 1304's processor can utilize data received from these layers (e.g., packet data) to perform Layer 3, Layer 2, or Layer 1 functions, 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 the Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, Layer 2 may include the Media Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, Layer 1 may include the Physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

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

[0153] Baseband circuit 1304 may further include: one or more interfaces for communicatively coupling to other circuits / devices, such as memory interface 1412 (e.g., an interface for sending / receiving data to / from a memory external to baseband circuit 1304); application circuit interface 1414 (e.g., for sending / receiving data to / from a memory external to baseband circuit 1304); and application circuit interface 1414 (e.g., for sending / receiving data to / from a memory external to baseband circuit 1304). Figure 13 Application circuit 1302 (interface for sending / receiving data); RF circuit interface 1416 (e.g., for sending / receiving data to / from...). Figure 13 The RF circuit 1306 is an interface for transmitting / receiving data; the wireless hardware connection interface 1418 (e.g., for transmitting / receiving data to / from near field communication (NFC) components, Components (e.g.) Low Energy) Interface for sending / receiving data to / from components and other communication components); and power management interface 1420 (e.g., an interface for sending / receiving power or control signals to / from PMC 1312).

[0154] Figure 15 This is a diagram of a control plane protocol stack according to some implementation schemes. In this implementation scheme, 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] PHY layer 1501 can transmit or receive information used by MAC layer 1502 through one or more air interfaces. PHY layer 1501 can also perform link adaptive 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 RRC layer 1505). PHY layer 1501 can further perform error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, modulation / demodulation of the physical channel, interleaving, rate matching, mapping to the physical channel, 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 a transport block (TB) to be delivered to the PHY via the transport channel, demultiplex MACSDUs from the transport block (TB) delivered by the PHY via the transport channel to one or more logical channels, multiplex MAC SDUs onto the TB, schedule information reports, perform error correction through Hybrid Automatic Repeat Request (HARQ), and prioritize logical channels.

[0157] RLC layer 1503 can operate in multiple modes, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). RLC layer 1503 can perform the transmission of higher-layer Protocol Data Units (PDUs), error correction via Automatic Repeat Request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC layer 1503 can also perform resegmentation 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 RLC re-establishment.

[0158] PDCP layer 1504 can perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform sequential delivery of upper-layer PDUs during lower-layer re-establishment, eliminate duplication of lower-layer SDUs during lower-layer re-establishment of 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 discarding, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0159] The main services and functions of RRC layer 1505 may include broadcasting system information (e.g., included in the Master Information Block (MIB) or System Information Block (SIB) related to the Non-Access Layer (NAS), broadcasting system information related to the Access Layer (AS), paging, establishment, maintenance, and release of RRC connections between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and publication of point-to-point radio bearers, including security functions for 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 can use the Uu interface (e.g., the LTE-Uu interface) to exchange control plane data via a protocol stack including PHY layer 1501, MAC layer 1502, RLC layer 1503, PDCP layer 1504 and RRC layer 1505.

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

[0162] The S1 Application Protocol (S1-AP) layer 1515 can support the functions of the S1 interface and includes basic procedures (EPs). EPs are the interaction units between RAN node 111 and CN 120. S1-AP layer services can include two sets: UE-associated services and non-UE-associated services. These services perform functions including, but 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] The Flow Control Transmission Protocol (SCTP) layer (also known as the SCTP / IP layer) 1514 can be partially based on the IP protocol supported by the IP layer 1513 to ensure reliable delivery of signaling messages between the RAN node 111 and the MME 121. The L2 layer 1512 and the L1 layer 1511 can refer to the communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

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

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

[0166] The General Packet Radio Service (GPRS) tunneling protocol for the User Plane (GTP-U) layer 1604 can 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 can be packets in IPv4, IPv6, or PPP format. The UDP and IP Security (UDP / IP) layer 1603 can provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication for selected data streams. RAN node 111 and S-GW 122 can exchange user plane data via the S1-U interface through a protocol stack including L1 layer 1511, L2 layer 1512, UDP / IP layer 1603, and GTP-U layer 1604. S-GW 122 and S-GW 123 can exchange user plane data via the S5 / S8a interface through a protocol stack including L1 layer 1511, L2 layer 1512, UDP / IP layer 1603, and GTP-U layer 1604. As described above... Figure 15 The NAS protocol discussed here supports the mobility and session management process of UE 101 to establish and maintain the IP connection between UE 101 and P-GW 123.

[0167] Figure 17 Components of a core network according to some embodiments are shown. The components of CN 120 may be implemented in a physical node or a separate physical node, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, network function virtualization (NFV) is used to virtualize any or all of the aforementioned network node functions (described in further detail below) via executable instructions stored in one or more computer-readable storage media. A logical instance of CN 120 may be referred to as network slice 1701. A logical instance of a portion of CN 120 may be referred to as network subslice 1702 (e.g., network subslice 1702 is shown as including PGW 123 and PCRF 126).

[0168] NFV architectures and infrastructures can be used to virtualize one or more network functions onto physical resources that include a combination of industry-standard server hardware, storage hardware, or switches (or alternatively, proprietary hardware). In other words, NFV systems can be used to perform virtual or reconfigurable concrete implementations of one or more EPC components / functions.

[0169] Figure 18 This is a block diagram illustrating the components of an NFV-enabled system 1800 according to some example implementations. System 1800 is shown as including a Virtualization Infrastructure Manager (VIM) 1802, a Network Functions Virtualization Infrastructure (NFVI) 1804, a VNF Manager (VNFM) 1806, a Virtualized Network Function (VNF) 1808, an Element Manager (EM) 1810, an NFV Coordinator (NFVO) 1812, and a Network Manager (NM) 1814.

[0170] VIM 1802 manages the resources of NFVI 1804. NFVI 1804 may include physical or virtual resources and applications (including hypervisors) used to run System 1800. VIM 1802 can leverage NFVI 1804 to manage the lifecycle of virtual resources (e.g., the creation, maintenance, and teardown of virtual machines (VMs) associated with one or more physical resources), track VM instances, track the performance, failure, and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.

[0171] VNFM 1806 manages VNF 1808. VNF 1808 can be used to perform EPC components / functions. VNFM 1806 manages the lifecycle of VNF 1808 and tracks the performance, faults, and security of VNF 1808 virtualization. EM 1810 tracks the performance, faults, and security of VNF 1808 functionality. Tracking data from VNFM 1806 and EM 1810 may include, for example, performance measurement (PM) data used by VIM 1802 or NFVI 1804. Both VNFM 1806 and EM 1810 can scale the number of VNFs in System 1800.

[0172] NFVO 1812 can coordinate, authorize, release, and engage the resources of NFVI 1804 to provide requested services (e.g., perform EPC functions, components, or slices). NM 1814 can provide end-user function groups responsible for network management, which may include network elements with VNFs, non-virtualized network functions, or both (management of VNFs can occur via EM1810).

[0173] Figure 19 This is a block diagram illustrating components, according to some example embodiments, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of executing any or more of the methods discussed herein. Specifically, Figure 19 A schematic diagram of hardware resource 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 bus 1940. For implementations utilizing node virtualization (e.g., NFV), a hypervisor 1902 can be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resource 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] Communication resource 1930 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 1904 or one or more databases 1906 via network 1908. For example, communication resource 1930 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB), cellular communication components, NFC components, etc. Components (e.g.) Low Energy) Components and other communication components.

[0177] Instruction 1950 may include software, programs, applications, applets, or other executable code for causing at least one of processors 1910 to perform any or more of the methods discussed herein. Instruction 1950 may reside wholly or partially within processor 1910 (e.g., within the processor's cache), memory / storage device 1920, or any suitable combination thereof. Furthermore, any portion of instruction 1950 may be transferred to hardware resource 1900 from any combination of peripheral device 1904 or database 1906. Thus, the memory of processor 1910, memory / storage device 1920, peripheral device 1904, and database 1906 are examples of computer-readable and machine-readable media.

[0178] The following will provide several embodiments related to the implementation of the above-described technology.

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

[0180] In Example 2, the subject of Example 1 or any of the examples herein, is receiving the Slot Format Indicator (SFI) monitoring configuration via higher-layer signaling.

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

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

[0183] In Example 5, the subject of Example 1 or any of the examples herein, one or more processors are further controlled to: determine the serving cell corresponding to the timeslot format based on higher-layer signaling from the RAN node.

[0184] In Example 6, the subject of Example 1 or any of the examples herein is provided, wherein the search space corresponds to a BWP among a plurality of bandwidth components (BWPs) used for communication between the UE and the RAN node.

[0185] In Example 7, the subject of Example 1 or any of the examples herein, one or more processors are further controlled to: determine the slot format of another BWP among a plurality of BWPs based on the determined slot format of the BWP, the subcarrier spacing (SCS) of the BWP, and the SCS of another BWP.

[0186] In the eighth embodiment, the means of the user equipment (UE) may include: an interface to a radio frequency (RF) circuit; and one or more processors controlled to: transmit UE capability information via the interface to the RF circuit to a radio access network (RAN) node, the information relating to a 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 to transmit shortened downlink control information (sDCI) via a shortened physical downlink control channel (sPDCCH) based on the maximum BDA; and obtain the sDCI by monitoring the sPDCCH according to the determined sCCE.

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

[0188] In Example 10, the subject of Example 8 or any of the examples herein, the number of blind decodes corresponds to the UE-specific search space of the subframe.

[0189] In Example 11, the subject of Example 8 or any of the embodiments herein, the maximum number of BDAs is provided via a field of the Radio Resource Control (RRC) Information Element (IE) in the reference window.

[0190] In Example 12, the subject of Example 8 or any of the embodiments herein, sDCI indicates at least one sCCE corresponding to the set of sPDCCH resource blocks (RBs) of the determined sCCE, which is used to transmit information via the Physical Downlink Shared Channel (PDSCH).

[0191] In Example 13, the subject of Example 8 or any of the examples herein, the sCCE of sPDCCH is based at least in part on the sCCE of the sPDCCH candidate among a plurality of sPDCCH candidates at the aggregation level (AL) of the UE.

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

[0193] In Example 15, the subject of Example 8 or any of the examples herein, a plurality of sPDCCH candidates are provided to the UE via higher-layer signaling.

[0194] In Example 16, the subject of Example 8 or any of the examples herein is provided to the UE in DCI format via higher-layer signaling.

[0195] In Example 17, the subject of Example 8 or any of the examples herein, the search space of sDCI in PDCCH includes a subset of the search space of PDCCH for DCI format monitoring.

[0196] In Example 18, the subject of Example 8 or any 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 Example 19, the subject matter of Example 8 or any of the examples 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 for sPDSCH transmission.

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

[0199] In Example 21, the subject of Example 20 or any of the embodiments herein, the Slot Format Indicator (SFI) monitoring configuration is received via higher-layer signaling.

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

[0201] In Example 23, the subject of Example 20 or any of the examples herein, one or more processors further require: determining slot format information for one or more consecutive slots based on higher-layer signaling from the RAN node and a PDCCH carrying a DCI format with SFI.

[0202] In Example 24, the subject of Example 20 or any of the embodiments herein, one or more processors further require: determining the serving cell corresponding to the timeslot format based on higher-layer signaling from the RAN node.

[0203] In Example 25, the subject of Example 20 or any of the examples herein, the search space corresponds to a BWP among a plurality of bandwidth components (BWPs) used for communication between the UE and the RAN node.

[0204] In Example 26, the subject of Example 20 or any of the embodiments herein, wherein one or more processors further require: determining the slot format of another BWP among a plurality of BWPs based on the determined slot format of the BWP, the subcarrier spacing (SCS) of the BWP, and the SCS of another BWP.

[0205] In the 27th embodiment, the computer-readable medium may contain program instructions for causing one or more processors associated with a user equipment (UE) to: transmit UE capability information to a radio access network (RAN) node 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 to transmit shortened downlink control information (sDCI) via a shortened physical downlink control channel (sPDCCH) based on the maximum BDA; and obtain the sDCI by monitoring the sPDCCH according to the determined sCCE.

[0206] In Example 28, the subject of Example 27 or any of the embodiments herein, one or more processors further require: communicating with RAN nodes according to sDCI.

[0207] In Example 29, the subject of Example 27 or any of the examples herein, the number of blind decodes corresponds to the UE-specific search space of the subframe.

[0208] In Example 30, the subject of Example 27 or any of the embodiments herein, the maximum number of BDAs is provided via a field of the Radio Resource Control (RRC) Information Element (IE) in the reference window.

[0209] In Example 31, the subject of Example 27 or any of the embodiments herein, sDCI indicates at least one sCCE corresponding to the set of sPDCCH resource blocks (RBs) of the determined sCCE, which is used to transmit information via the Physical Downlink Shared Channel (PDSCH).

[0210] In Example 32, the subject of Example 27 or any of the examples herein, the sCCE of sPDCCH is based at least in part on the sCCE of the sPDCCH candidate among a plurality of sPDCCH candidates at the aggregation level (AL) of the UE.

[0211] In Example 33, the subject of Example 27 or any of the examples herein, the multiple sPDCCH candidates at AL correspond to a specific DCI format.

[0212] In Example 34, the subject of Example 27 or any of the examples herein, a plurality of sPDCCH candidates are provided to the UE via higher-layer signaling.

[0213] In Example 35, the subject of Example 27 or any of the examples herein, the DCI format is provided to the UE via higher-layer signaling.

[0214] In Example 36, the subject of Example 27 or any of the examples herein, the search space of sDCI in PDCCH includes a subset of the search space of PDCCH for DCI format monitoring.

[0215] In Example 37, the subject of Example 27 or any of the examples 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 of embodiment 27 or any 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 for sPDSCH transmission.

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

[0218] In Example 40, the subject of Example 39 or any of the embodiments herein, the Slot Format Indicator (SFI) monitoring configuration is received via higher-layer signaling.

[0219] In embodiment 41, the subject of embodiment 39 or any of the embodiments herein, the means for determining a time slot format includes: means for receiving a plurality of time slot formats including the time slot format; and means for mapping an SFI index field value corresponding to a DCI format to the time slot format among the plurality of time slot formats.

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

[0221] In embodiment 43, the subject matter of embodiment 39 or any of the embodiments herein further includes: means for determining the serving cell corresponding to the timeslot format based on higher-layer signaling from the RAN node.

[0222] In Example 44, the subject of Example 39 or any of the examples herein, the search space corresponds to a BWP among a plurality of bandwidth components (BWPs) used for communication between the UE and the RAN node.

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

[0224] In the forty-sixth embodiment, the means of the user equipment (UE) may include: means for transmitting UE capability information to a radio access network (RAN) node, the information relating to a maximum number of blind decoding attempts (BDA) supported by the UE; means 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 means for obtaining the sDCI by monitoring the sPDCCH according to the determined sCCE.

[0225] In embodiment 47, the subject matter of embodiment 46 or any of the embodiments herein also includes: means for communicating with RAN nodes according to sDCI.

[0226] In Example 48, the subject of Example 46 or any of the examples herein, the number of blind decodes corresponds to the UE-specific search space of the subframe.

[0227] In Example 49, the subject of Example 46 or any of the embodiments herein, the maximum number of BDAs is provided via a field of the Radio Resource Control (RRC) Information Element (IE) in the reference window.

[0228] In Example 50, the subject of Example 46 or any of the embodiments herein, sDCI indicates at least one sCCE corresponding to the set of sPDCCH resource blocks (RBs) of the determined sCCE, which is used to transmit information via the Physical Downlink Shared Channel (PDSCH).

[0229] In Example 51, the subject of Example 46 or any of the examples herein, the sCCE of sPDCCH is based at least in part on the sCCE of the sPDCCH candidate among a plurality of sPDCCH candidates at the aggregation level (AL) of the UE.

[0230] In Example 52, the subject of Example 46 or any of the examples herein, the plurality of sPDCCH candidates at AL correspond to a specific DCI format.

[0231] In Example 53, the subject of Example 46 or any of the examples herein, a plurality of sPDCCH candidates are provided to the UE via higher-layer signaling.

[0232] In Example 54, the subject of Example 46 or any of the examples herein, the DCI format is provided to the UE via higher-layer signaling.

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

[0234] In Example 56, the subject of Example 46 or any of the examples herein, 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 Example 57, the subject of Example 46 or any of the examples 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 for sPDSCH transmission.

[0236] In the fifty-eighth embodiment, the method performed by the user equipment (UE) may include: processing information received from a radio access network (RAN) node regarding the search space of the physical downlink control channel (PDCCH) 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 whether the corresponding symbols are assigned for uplink (UL) communication, downlink (DL) communication, or identified as flexible symbols; and communicating with the RAN node according to the time slot format.

[0237] In Example 59, the subject of Example 58 or any of the embodiments herein, the Slot Format Indicator (SFI) monitoring configuration is received via higher-layer signaling.

[0238] In embodiment 60, the subject of embodiment 58 or any of the embodiments herein, the means for determining a time slot format includes: receiving a plurality of time slot formats including the time slot format; and mapping an SFI index field value of a DCI format corresponding to the DCI to the time slot format among the plurality of time slot formats.

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

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

[0241] In Example 63, the subject of Example 58 or any of the examples herein, the search space corresponds to a BWP among a plurality of bandwidth components (BWPs) used for communication between the UE and the RAN node.

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

[0243] In the sixty-fifth embodiment, the method performed by the user equipment (UE) may include: transmitting UE capability information to a radio access network (RAN) node, the 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 by the RAN node to transmit shortened downlink control information (sDCI) via a shortened physical downlink control channel (sPDCCH) based on the maximum BDA; and obtaining the sDCI by monitoring the sPDCCH according to the determined sCCE.

[0244] In embodiment 66, the subject matter of embodiment 65 or any of the embodiments herein further includes: means for communicating with RAN nodes according to sDCI.

[0245] In Example 67, the subject of Example 65 or any of the examples herein, the number of blind decodes corresponds to the UE-specific search space of the subframe.

[0246] In Example 68, the subject of Example 65 or any of the embodiments herein, the maximum number of BDAs is provided via a field of the Radio Resource Control (RRC) Information Element (IE) in the reference window.

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

[0248] In Example 70, the subject of Example 65 or any of the examples herein, the sCCE of sPDCCH is based at least in part on the sCCE of a candidate among a plurality of sPDCCH candidates at the aggregation level (AL) of the UE.

[0249] In Example 71, the subject of Example 65 or any of the examples herein, the plurality of sPDCCH candidates at AL correspond to a specific DCI format.

[0250] In Example 72, the subject of Example 65 or any of the examples herein, a plurality of sPDCCH candidates are provided to the UE via higher-layer signaling.

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

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

[0253] In Example 75, the subject of Example 65 or any of the examples herein, 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 of embodiment 65 or any 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 for sPDSCH transmission.

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

[0256] For example, although it has been referenced Figures 2-7 A series of signals and / or operations are described, but in other implementations, the order of signals / operations can be modified. Additionally, independent signals can be executed in parallel.

[0257] It is evident that, in the embodiments shown in the accompanying drawings, the exemplary aspects described above can 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, while the operation and behavior of the aspects have been described without reference to specific software code, it should be understood that software and control hardware can be designed to implement the aspects based on the description herein.

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

[0259] Unless explicitly described herein, no element, action, or instruction used in this application should be construed as critical or necessary. As used herein, instances of the use of the term “and” do not necessarily exclude the intended interpretation of the phrase “and / or” for that instance. Similarly, as used herein, instances of the use of the term “or” do not necessarily exclude the intended interpretation of the phrase “and / or” for that instance. Additionally, 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. When the subject matter is only a single project, use the terms "one," "single," "only," or similar language.

Claims

1. An apparatus for a radio access network (RAN) node, the apparatus comprising: Interface to RF circuitry; and One or more processors, said one or more processors being controlled to: The Group Common Physical Downlink Control Channel (GC-PDCCH), including Downlink Control Information (DCI), is transmitted via the interface to the RF circuit. Information about the search space used for monitoring the GC-PDCCH is transmitted via the interface to the RF circuit; The UE-specific higher-layer signaling is sent to the user equipment (UE) via the interface to the RF circuitry, the UE-specific higher-layer signaling indicating a portion of the GC-PDCCH carrying a slot format indicator (SFI); as well as The UE communicates via the interface to the RF circuit according to a time slot format based on the SFI, wherein the time slot format indicates the allocation of symbols for uplink UL communication, the allocation of symbols for downlink DL communication, and symbols identified as flexible symbols, and wherein the serving cell corresponding to the time slot format is based on information provided by higher-layer signaling specific to the UE.

2. The apparatus of claim 1, wherein the portion of the GC-PDCCH is indicated by an SFI monitoring configuration in higher-layer signaling specific to the UE.

3. The apparatus according to claim 1 or 2, wherein the one or more processors are further controlled to: The interface to the RF circuit sends to the UE a plurality of time slot formats including the time slot format, wherein the time slot format is based on an SFI index field value corresponding to the DCI format of the DCI, and the SFI index field value is mapped to the time slot format among the plurality of time slot formats.

4. The apparatus of claim 3, wherein the time slot format information of one or more consecutive time slots is based on the UE-specific higher-layer signaling and the GC-PDCCH carrying the DCI format with the SFI.

5. The apparatus of claim 1 or 2, wherein the search space corresponds to a BWP in a plurality of bandwidth portions BWPs used for communication between the UE and the RAN node.

6. The apparatus of claim 5, wherein the slot format of another BWP of the plurality of BWPs is based on the slot format of the BWP, the subcarrier spacing SCS of the BWP, and the SCS of the other BWP.

7. A method for a radio access network (RAN) node, the method comprising: Transmit the Group Common Physical Downlink Control Channel (GC-PDCCH) which includes Downlink Control Information (DCI); Send information about the search space used for monitoring the GC-PDCCH; Send UE-specific higher-layer signaling to the user equipment (UE), the UE-specific higher-layer signaling indicating a portion of the GC-PDCCH carrying a slot format indicator (SFI); as well as The communication with the UE is based on a time slot format according to the SFI, wherein the time slot format indicates the allocation of symbols for uplink UL communication, the allocation of symbols for downlink DL communication, and symbols identified as flexible symbols, and wherein the serving cell corresponding to the time slot format is based on information provided by higher-layer signaling specific to the UE.

8. The method of claim 7, wherein the portion of the GC-PDCCH is indicated by an SFI monitoring configuration in higher-layer signaling specific to the UE.

9. The method according to claim 7 or 8, further comprising: The UE is sent a plurality of time slot formats including the time slot format, wherein the time slot format is based on the SFI index field value corresponding to the DCI format of the DCI, and the SFI index field value is mapped to the time slot format among the plurality of time slot formats.

10. The method of claim 9, wherein the slot format information of one or more consecutive slots is based on the UE-specific higher-layer signaling and the GC-PDCCH carrying the DCI format with the SFI.

11. The method of claim 7 or 8, wherein the search space corresponds to a BWP in a plurality of bandwidth portions BWPs used for communication between the UE and the RAN node.

12. The method of claim 11, wherein the slot format of another BWP among the plurality of BWPs is based on the slot format of the BWP, the subcarrier spacing (SCS) of the BWP, and the SCS of the other BWP.

13. A computer-readable medium comprising program instructions for causing one or more processors associated with a radio access network (RAN) node to: Transmit the Group Common Physical Downlink Control Channel (GC-PDCCH) which includes Downlink Control Information (DCI); Send information about the search space used for monitoring the GC-PDCCH; Sending UE-specific higher-layer signaling to the User Equipment (UE), the UE-specific higher-layer signaling indicating a portion of the GC-PDCCH carrying a Slot Format Indicator (SFI); and The communication with the UE is based on a time slot format according to the SFI, wherein the time slot format indicates the allocation of symbols for uplink UL communication, the allocation of symbols for downlink DL communication, and symbols identified as flexible symbols, and wherein the serving cell corresponding to the time slot format is based on information provided by higher-layer signaling specific to the UE.

14. The computer-readable medium of claim 13, wherein the portion of the GC-PDCCH is indicated by an SFI monitoring configuration in higher-layer signaling specific to the UE.

15. The computer-readable medium of claim 13 or 14, wherein the program instructions are further configured to cause the one or more processors to: The UE is sent a plurality of time slot formats including the time slot format, wherein the time slot format is based on the SFI index field value corresponding to the DCI format of the DCI, and the SFI index field value is mapped to the time slot format among the plurality of time slot formats.

16. The computer-readable medium of claim 15, wherein the time slot format information of one or more consecutive time slots is based on the UE-specific higher-layer signaling and the GC-PDCCH carrying the DCI format with the SFI.

17. The computer-readable medium of claim 13 or 14, wherein the search space corresponds to a BWP in a plurality of bandwidth portions BWPs for communication between the UE and the RAN node.

18. The computer-readable medium of claim 17, wherein the slot format of another BWP of the plurality of BWPs is based on the slot format of the BWP, the subcarrier spacing (SCS) of the BWP, and the SCS of the other BWP.

Images