Scheduling New Radio (NR) shared channel transmissions

Abstract

In a general aspect, a user equipment (UE) in a cellular communication network receives a radio resource control (RRC) signaling message from a base station communicatively coupled to the UE via a communication channel. The UE accesses a search space in the RRC signaling message. The UE identifies a fallback downlink control information (DCI) information element (IE) included in the search space. The UE determines whether the fallback DCI IE indicates an aggregation factor for shared channel communication with the base station within multiple time slots in the communication channel. The UE determines an uplink / downlink (UL / DL) configuration for transmission on the communication channel. The UE schedules aggregated transmissions within multiple time slots in the communication channel based on the aggregation factor and the uplink / downlink configuration.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 826,799, filed on March 29, 2019, which is incorporated herein by reference in its entirety. Technical Field

[0003] The following disclosure relates generally to the field of wireless communications, and more particularly to methods, apparatus, and systems for scheduling New Radio (NR) shared channel transmissions in a cellular communication network. Background Art

[0004] Cellular or mobile communications have evolved from early voice systems to current integrated communication platforms. The next generation of wireless communication systems, namely 5th Generation (5G) or New Radio (NR), provides a variety of users and applications with access to information and data sharing anytime, anywhere. Summary of the Invention

[0005] In a general aspect, a user equipment (UE) in a cellular communication network receives a radio resource control (RRC) signaling message from a base station communicatively coupled to the UE via a communication channel. The UE accesses a search space in the RRC signaling message. The UE identifies a fallback downlink control information (DCI) information element (IE) included in the search space. The UE determines whether an aggregation factor is indicated in the fallback DCI IE, the aggregation factor being used for shared channel communication with the base station within a plurality of time slots in the communication channel. The UE determines an uplink / downlink (UL / DL) configuration for transmissions on the communication channel. The UE schedules aggregated transmissions within a plurality of time slots in the communication channel based on the aggregation factor and the uplink / downlink configuration.

[0006] Particular implementations may include one or more of the following features.In some implementations, accessing the search space includes accessing one of a common search space (CSS) or a UE-specific search space (USS) in an RRC signaling message.

[0007] In some implementations, identifying the fallback DCI IE included in the search space includes identifying one of a DCI format 0_0 IE or a DCI format 1_0 IE included in the search space.

[0008] In some implementations, determining the uplink / downlink configuration for transmission on the communication channel includes determining one of a TDD-UL-DL-ConfigurationCommon IE or a TDD-UL-DL-ConfigDedicated IE included in an RRC signaling message.

[0009] In some implementations, the fallback DCI IE includes a DCI format 1_0 IE and indicates an aggregation factor in one of the DCI format 1_0 IE or the DCI format 1_1 IE. In such implementations, scheduling the aggregate transmission includes: determining, using the aggregation factor, that the UE is scheduled to receive physical downlink shared channel (PDSCH) data in a plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol of a group of symbols in a particular time slot in the plurality of time slots is an uplink symbol; and in response to determining that the UE is scheduled to receive PDSCH data in the plurality of time slots and that at least one symbol of the particular time slot is an uplink symbol, scheduling the UE not to receive the PDSCH in the particular time slot.

[0010] In some implementations, the fallback DCI IE includes a DCI format 0_0 IE and indicates an aggregation factor in one of the DCI format 0_0 IE or the DCI format 0_1 ​​IE. In such implementations, scheduling aggregate transmission includes: determining, using the aggregation factor, that the UE is scheduled to transmit physical uplink shared channel (PUSCH) data in a plurality of time slots in a communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol in a group of symbols in a particular time slot from the plurality of time slots is a downlink symbol; and in response to determining that the UE is scheduled to transmit PUSCH data in the plurality of time slots and that at least one symbol of the particular time slot is a downlink symbol, scheduling the UE not to transmit PUSCH data in the particular time slot.

[0011] In some implementations, identifying the fallback DCI IE included in the search space includes identifying a DCI format 1_0 IE detected in the USS and indicating an aggregation factor in one of the DCI format 1_0 IE or the DCI format 1_1 IE. In such implementations, scheduling aggregate transmission includes: determining, using the aggregation factor, that the UE is scheduled to receive physical downlink shared channel (PDSCH) data in a plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol in a group of symbols in a particular time slot from the plurality of time slots is an uplink symbol; and in response to determining that the UE is scheduled to receive PDSCH data in the plurality of time slots and that at least one symbol of the particular time slot is an uplink symbol, scheduling the UE not to receive the PDSCH in the particular time slot.

[0012] In some implementations, identifying the fallback DCI IE included in the search space includes identifying a DCI format 0_0 IE detected in the USS and indicating an aggregation factor in one of the DCI format 0_0 IE or the DCI format 0_1 ​​IE. In such implementations, scheduling the aggregate transmission includes: determining, using the aggregation factor, that the UE is scheduled to transmit physical uplink shared channel (PUSCH) data in a plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol in a group of symbols in a particular time slot from the plurality of time slots is a downlink symbol; and in response to determining that the UE is scheduled to transmit PUSCH data in the plurality of time slots and that at least one symbol of the particular time slot is a downlink symbol, scheduling the UE not to transmit PUSCH data in the particular time slot.

[0013] In some implementations, identifying a fallback DCI IE included in the search space includes identifying a DCI format 1_0 IE detected in a USS. In such implementations, it is determined that the UE is configured with a pdsch-AggregationFactor. In response to the determination, the UE applies the same symbol allocation across multiple consecutive time slots corresponding to the pdsch-AggregationFactor. The UE receives one of the following: (i) PDSCH data scheduled by a physical downlink control channel (PDCCH), the PDCCH including one of a DCI format 1_1 IE or a DCI format 1_0 IE detected in the USS, and a cyclic redundancy check (CRC) scrambled by at least one of a cell radio network temporary identifier (C-RNTI), a modulation and coding scheme C-RNTI (MCS C-RNTI), or a configured scheduling RNTI (CS-RNTI), or (ii) PDSCH data scheduled using sps-Config without a corresponding PDCCH transmission. In some implementations, a transport block (TB) is repeated within each symbol allocation in each slot in consecutive slots, and the PDSCH is limited to a single transport layer.

[0014] In some implementations, identifying a fallback DCI IE included in the search space includes identifying a DCI format 0_0 IE detected in a USS. In such implementations, it is determined that the UE is configured with a pusch-AggregationFactor. In response to the determination, the UE applies the same symbol allocation across multiple consecutive time slots corresponding to the pusch-AggregationFactor and configures the PUSCH to a single transport layer. The UE transmits PUSCH data scheduled by a PDCCH, the PDCCH including one of a DCI format 0_1 ​​IE or a DCI format 0_0 IE detected in the USS, and a CRC scrambled with at least one of a C-RNTI or an MCS-C-RNTI. In some implementations, transmitting the PUSCH data includes: repeating the TB across consecutive time slots, and applying the same symbol allocation in each time slot in the consecutive time slots.

[0015] In some implementations, the fallback DCI IE is not configured to indicate an aggregation factor. In such implementations, it is determined that the UE is configured with a pdsch-AggregationFactor. In response to the determination, the UE applies the same symbol allocation across multiple consecutive time slots corresponding to the pdsch-AggregationFactor in the multiple time slots. The UE receives one of the following: (i) PDSCH data scheduled by a DCI format 1_1 IE in a PDCCH, the PDCCH including a CRC scrambled by at least one of a C-RNTI, an MCS C-RNTI, or a CS-RNTI, or (ii) PDSCH data scheduled using sps-Config without a corresponding PDCCH transmission. In some implementations, a transport block (TB) is repeated within each symbol allocation in each time slot in consecutive time slots, and the PDSCH is limited to a single transport layer.

[0016] In some implementations, the fallback DCI IE is not configured to indicate an aggregation factor. In such implementations, it is determined that the UE is configured with a pusch-AggregationFactor. In response to this determination, the UE applies the same symbol allocation across multiple consecutive slots corresponding to the pusch-AggregationFactor in the multiple slots and configures the PUSCH to a single transport layer. The UE transmits PUSCH data scheduled by the DCI format 0_1 ​​IE in a PDCCH that includes a CRC scrambled with at least one of a C-RNTI or an MCS-C-RNTI.

[0017] In some implementations, shared channel communication with the base station includes communication using one of a PDSCH or a PUSCH.

[0018] Similar operations and processes may be performed by one or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause the one or more processors to perform the operations and processes described above. In addition, similar operations may be performed by an apparatus or system comprising one or more processors and one or more computer-readable media. One or more computer-readable media store instructions that, when executed by one or more processors, cause the one or more processors to perform the operations and processes described above. In addition, similar operations may be associated with or provided as computer-implemented software embodied on a tangible, non-transitory medium that processes and converts the corresponding data, and some or all of these aspects may be computer-implemented methods or also included in corresponding systems or other devices for performing the functions described.

[0019] The details of one or more disclosed implementations are set forth in the following drawings and detailed description. Other features, aspects, and advantages will become apparent from the detailed description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 An exemplary architecture of a communication network system according to various implementations is shown.

[0021] Figure 2 An exemplary architecture of a system including a first core network according to various implementations is shown.

[0022] Figure 3 An exemplary architecture of a system including a second core network according to various implementations is shown.

[0023] Figure 4 Examples of infrastructure equipment according to various implementations are shown.

[0024] Figure 5 Examples of platforms (or "devices") according to various implementations are shown.

[0025] Figure 6 Exemplary components of a baseband circuit and a radio front-end module (RFEM) are shown according to various implementations.

[0026] Figure 7 Protocol functionality for use in a wireless communication device according to various implementations is shown.

[0027] Figure 8 is a block diagram illustrating components of an electronic device capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some exemplary implementations.

[0028] Figure 9 A flow chart illustrating a process for scheduling shared channel transmissions in a cellular communication network is shown.

[0029] Like reference numbers in the drawings indicate like elements. DETAILED DESCRIPTION

[0030] The following detailed description refers to the accompanying drawings. In the following description, specific details, such as specific structures, architectures, interfaces or technologies, etc., are set forth for purposes of illustration and not limitation, so as to provide a thorough understanding of various aspects of various specific implementations. However, it will be apparent to those skilled in the art who benefit from this disclosure that various aspects of various specific implementations can be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits and methods are omitted so as not to obscure the description of various specific implementations due to unnecessary details. For the purposes of this document, the phrase "A or B" means (A), (B) or (A and B).

[0031] 5G NR (or "5G" or "NR") wireless cellular technology provides a unified network / system that addresses distinct and sometimes conflicting performance dimensions and services. These diverse, multi-dimensional requirements are driven by different services and applications. 5G NR is based on the 3rd Generation Partnership Project (3GPP) Long Term Evolution Advanced (LTE Advanced) technology, with the addition of new radio access technologies (RATs) to provide better, simple, and seamless wireless connectivity solutions. 5G NR is designed to enable everything to connect wirelessly and deliver fast, rich content and services.

[0032] 5G NR supports scheduling PDSCH and PUSCH transmissions across multiple slots using an aggregation factor that is semi-statically configured in user equipment (UE)-specific RRC signaling. The aggregation factor can be configured in groups of 2, 4, or 8 slots. If no aggregation factor is provided, no aggregation is assumed (e.g., aggregation factor = 1).

[0033] The 3GPP Release 15 NR technical specification does not specify whether "fallback" DCI formats 0_0 and 1_0 can schedule aggregate transmissions due to inconsistencies in data and control programs. In this disclosure, a method for scheduling shared channel (e.g., PDSCH or PUSCH) transmissions in multiple time slots via DCI formats 0_0 and 1_0 is described, as detailed below.

[0034] Regardless of the search space type, aggregate transmission is scheduled by fallback DCI 0_0, 1_0

[0035] In some implementations, scheduling aggregated transmissions with fallback DCI formats 0_0 and 1_0 is allowed regardless of the search space type. In such implementations, the UE applies slot aggregation for PDSCH or PUSCH when scheduled with DCI formats 1_0 or 0_0, respectively. To enable such implementations, the specification for handling transmission and reception within multiple slots using UL-DL configurations in Section 11.1 of 3GPP TS 38.213 should be updated as described below.

[0036] In some cases, if a UE is scheduled by DCI format 1_0 or 1_1 to receive PDSCH in multiple time slots, and if TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated indicates that, for one time slot from the multiple time slots, at least one symbol from a set of symbols is an uplink symbol, in which the UE is scheduled for PDSCH reception in the time slot, the UE does not receive PDSCH in the time slot.

[0037] In some cases, if a UE is scheduled to transmit PUSCH in multiple time slots via DCI format 0_0 or 0_1, and if TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated indicates that, for one time slot from the multiple time slots, at least one symbol from a set of symbols is a downlink symbol, in which the UE is scheduled for PUSCH transmission in the time slot, the UE does not transmit PUSCH in the time slot.

[0038] Aggregate transmission is scheduled via fallback DCI 0_0, 1_0 when detected in the UE-specific search space

[0039] In some implementations, aggregated transmissions are allowed via fallback DCI 0_0, 1_0 scheduling when detected in the UE-specific search space (USS). In such implementations, the UE applies slot aggregation for PDSCH or PUSCH when scheduled via DCI format 1_0 or 0_0, respectively, detected in the UE-specific search space. To enable such implementations, the behavior for handling transmission and reception within multiple slots with UL-DL configuration in section 11.1 of 3GPP TS 38.213 should be updated as described below.

[0040] In some cases, if a UE is scheduled to receive PDSCH in multiple time slots by DCI format 1_1 or DCI format 1_0 detected in the USS, and if TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated indicates that, for one time slot from the multiple time slots, at least one symbol from a set of symbols is an uplink symbol, in which the UE is scheduled for PDSCH reception in the time slot, the UE does not receive PDSCH in the time slot.

[0041] In some cases, if a UE is scheduled to transmit PUSCH in multiple time slots by DCI format 0_1 ​​or DCI format 0_0 detected in the USS, and if TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated indicates that, for one time slot from the multiple time slots, at least one symbol from a set of symbols is a downlink symbol, where the UE is scheduled for PUSCH transmission in the time slot, the UE does not transmit PUSCH in the time slot.

[0042] Additionally, the procedure for using the aggregation factor described in 3GPP TS 38.214 should be updated as follows.

[0043] In some cases, when receiving PDSCH scheduled by PDCCH carrying DCI format 1_1 or DCI format 1_0 detected in USS and CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, or PDSCH scheduled without corresponding PDCCH transmission using sps-Config, if the UE is configured with pdsch-AggregationFactor, the same symbol allocation applies across pdsch-AggregationFactor consecutive slots. The UE can expect TBs to be repeated within each symbol allocation in each slot in pdsch-AggregationFactor consecutive slots, and the PDSCH is limited to a single transmission layer.

[0044] In some cases, when transmitting PUSCH scheduled by PDCCH carrying DCI format 0_1 ​​or DCI format 0_0 detected in the USS with CRC scrambled by C-RNTI, MCS-C-RNTI, if the UE is configured with pusch-AggregationFactor, the same symbol allocation is applied across pusch-AggregationFactor consecutive slots, and PUSCH is limited to a single transport layer. The UE will repeat TBs across pusch-AggregationFactor consecutive slots, applying the same symbol allocation in each slot.

[0045] Aggregate transmission scheduling via fallback DCI 0_0, 1_0 is not allowed

[0046] In some implementations, scheduling aggregated transmissions with fallback DCI formats 0_0, 1_0 is not allowed. In such implementations, the UE applies slot aggregation for PDSCH or PUSCH only when scheduled by DCI formats 1_1 or 0_1. To enable such implementations, the procedures for using aggregation factors described in 3GPP TS 38.214 should be updated as follows.

[0047] In some cases, when receiving a PDSCH scheduled by DCI format 1_1 in a PDCCH with a CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, or a PDSCH scheduled without a corresponding PDCCH transmission using sps-Config, if the UE is configured with pdsch-AggregationFactor, the same symbol allocation applies across pdsch-AggregationFactor consecutive slots. The UE can expect TBs to be repeated within each symbol allocation in each slot in pdsch-AggregationFactor consecutive slots, and the PDSCH is limited to a single transmission layer.

[0048] In some cases, when transmitting PUSCH scheduled by DCI format 0_1 ​​in PDCCH with CRC scrambled with C-RNTI, MCS-C-RNTI, if the UE is configured with pusch-AggregationFactor, the same symbol allocation is applied across pusch-AggregationFactor consecutive slots, and PUSCH is limited to a single transport layer. The UE will repeat the TB across pusch-AggregationFactor consecutive slots, applying the same symbol allocation in each slot.

[0049] Various specific implementations disclosed above are implemented using a wireless cellular communication network system and wireless cellular communication devices such as UE and base station (e.g., gNB), as described in the following sections.

[0050] Figure 1 An exemplary architecture of a communication network system 100 according to various implementations is shown. The following description is provided for an exemplary system 100 operating in conjunction with a cellular LTE system standard and / or a 5G or NR system standard provided by a 3GPP technical specification. However, the exemplary implementation is not limited in this regard and the implementation may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., 6G systems), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0051] like Figure 1 As shown, system 100 includes UE 101a and UE 101b (collectively referred to as "UEs 101" or "UE 101"). In some implementations, one or more of UEs 101 are configured to schedule shared channel transmissions of PDSCH or PUSCH or both as described in this disclosure. In the example shown, UE 101 is shown as a smart phone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a consumer electronic device, a cellular phone, a smart phone, a feature phone, a tablet computer, a wearable computer device, a personal digital assistant (PDA), a pager, a wireless handheld device, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-car entertainment (ICE) device, an instrument cluster (IC), a head-up display (HUD) device, an on-board diagnostic (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine electronic control unit (ECU), an electronic / engine electronic control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a connected or "smart" appliance, a machine type communication (MTC) device, a machine-to-machine (M2M) device, an Internet of Things (IoT) device, etc.

[0052] In some implementations, any of the UEs 101 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-lived UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a PLMN, ProSe or D2D communications, a sensor network, or an IoT network. The M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0053] The UE 101 may be configured to connect to, for example, be communicatively coupled to, the RAN 110. In a specific implementation, the RAN 110 may be an NG RAN or a 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or a GERAN. As used herein, the term "NG RAN" or the like may refer to the RAN 110 operating in an NR or 5G system 100, while the term "E-UTRAN" or the like may refer to the RAN 110 operating in an LTE or 4G system 100. Multiple UEs 101 utilize connections (or channels) 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0054] In this example, connections 103 and 104 are shown as air interfaces to achieve communication coupling and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In a specific implementation, the UE 101 may directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as an SL interface 105 and may include one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

[0055] UE 101b is shown as being configured to access access point AP 106 (also referred to as "WLAN node 106," "WLAN 106," "WLAN termination 106," "WT 106," etc.) via connection 107. Connection 107 may comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 106 would include Wireless Fidelity. router. In this example, AP 106 is connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various implementations, UE 101b, RAN 110, and AP 106 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 101b in an RRC_CONNECTED state being configured by RAN nodes 111a-b to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 101b using WLAN radio resources (e.g., connection 107) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent over connection 107. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0056] The RAN 110 includes one or more AN nodes or RAN nodes 111a and 111b (collectively, "RAN nodes 111") that enable connections 103 and 104. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node" and the like may refer to RAN nodes 111 (e.g., gNBs) operating in NR or 5G systems 100, while the terms "E-UTRAN node" and the like may refer to RAN nodes 111 (e.g., eNBs) operating in LTE or 4G systems 100. According to various specific implementations, the RAN node 111 may be realized as one or more of dedicated physical devices such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0057] In some implementations, all or part of the RAN nodes 111 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these implementations, the CRAN or vBBUP may implement a RAN functional split, such as a PDCP split, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 111; a MAC / PHY split, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 111; or a "lower PHY" split, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes 111. This virtualization framework allows idle processor cores of multiple RAN nodes 111 to execute other virtualized applications. In some implementations, individual RAN nodes 111 may represent a plurality of RAN nodes 111 connected to the RAN via individual F1 interfaces ( Figure 1 In these implementations, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 4 ), and the gNB-CU may be operated by a server (not shown) located in the RAN 110 or by a server pool in a manner similar to CRAN / vBBUP. Additionally or alternatively, one or more of the RAN nodes 111 may be a next generation eNB (ng-eNB), which is a next generation eNB that provides E-UTRA user plane and control plane protocol terminations to the UE 101 and is connected to the 5GC (e.g., NG-eNB) via an NG interface (discussed below). Figure 3 RAN node of CN 320).

[0058] In a V2X scenario, one or more of the RAN nodes 111 may be a roadside unit (RSU) or function as an RSU. The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU," an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU," an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to RF circuitry located on the roadside that provides connectivity support to passing vehicle UEs 101 (vUEs 101). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide extremely low latency communications for high-speed events, such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communication services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0059] Any of the RAN nodes 111 can serve as the endpoint for the air interface protocol and can be the first point of contact for the UE 101. In some implementations, any of the RAN nodes 111 can perform various logical functions of the RAN 110, including but not limited to functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0060] In a particular implementation, the UEs 101 may be configured to communicate with each other or with any of the RAN nodes 111 using OFDM communication signals over a multi-carrier communication channel in accordance with various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communication) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0061] In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 111 to the UE 101, while similar techniques can be used for uplink transmissions. 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 during each time slot. This type of time-frequency plane representation is common for OFDM systems and makes 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 includes multiple resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a collection of resource elements; in the frequency domain, this can represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0062] According to various implementations, the plurality of UEs 101 and the plurality of RAN nodes 111 communicate data (e.g., transmit data and receive data) over a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band") and / or an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum may include a 5 GHz band.

[0063] To operate in the unlicensed spectrum, the UE 101 and the RAN node 111 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 101 and the RAN node 111 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0064] LBT is a mechanism for a device (e.g., UE 101 or RAN node 111, etc.) to sense the medium (e.g., a channel or carrier frequency) and transmit when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine whether other signals are present on the channel to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an intended transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0065] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism known as CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 101, AP 106, etc.) intends to transmit, the WLAN node may first perform CCA before transmitting. In addition, in the event that more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a collision occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to CSMA / CA for WLAN. In some implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have an LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS for LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0066] The LAA mechanism is built on the carrier aggregation (CA) technology of the LTE-Advanced system. In CA, each aggregated carrier is called a component carrier (CC). A CC can have a bandwidth of 1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz or 20MHz, and up to five CCs can be aggregated, resulting in a maximum aggregate bandwidth of 100MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are usually the same for DL ​​and UL.

[0067] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL and may handle activities related to RRC and NAS. The other serving cells are called SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added or removed as needed, and changing the PCC may require the UE 101 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within the same subframe.

[0068] The PDSCH carries user data and higher layer signaling to multiple UEs 101. The PDCCH carries, among other information, information about the transport format and resource allocation associated with the PDSCH channel. It can also inform multiple UEs 101 about the transport format, resource allocation, and HARQ information associated with the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UEs 101b within a cell) can be performed at any of the RAN nodes 111 based on channel quality information fed back from any of the UEs 101. Downlink resource allocation information can be sent on the PDCCH for (e.g., allocated to) each of the UEs 101.

[0069] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruples, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and the channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

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

[0071] RAN nodes 111 may be configured to communicate with each other via interface 112. In a specific implementation where system 100 is an LTE system (eg, when CN 120 is a Figure 2 101 ), the interface 112 may be an X2 interface 112. The X2 interface may be defined between two or more RAN nodes 111 (e.g., two or more eNBs, etc.) connected to the EPC 120, and / or between two eNBs connected to the EPC 120. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface and may be used to convey information regarding the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information regarding user data transmitted from the MeNB to the SeNB; information regarding successful in-sequence delivery of PDCP PDUs for user data from the SeNB to the UE 101; information regarding PDCP PDUs that were not delivered to the UE 101; information regarding the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and the like. X2-C provides intra-LTE access mobility functions, including context transfer from the source eNB to the target eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.

[0072] When system 100 is a 5G or NR system (e.g., when CN 120 is Figure 3In some implementations (when the 5GC 320 in the 5GC 120 is connected), the interface 112 may be an Xn interface 112. The Xn interface is defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to the 5GC 120, between a RAN node 111 (e.g., a gNB) and an eNB connected to the 5GC 120, and / or between two eNBs connected to the 5GC 120. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for the UE 101 in connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected mode between one or more RAN nodes 111. This mobility support may include context transfer from the old (source) serving RAN node 111 to the new (target) serving RAN node 111; and control of the user plane tunnel between the old (source) serving RAN node 111 and the new (target) serving RAN node 111. The Xn-U protocol stack may include a transport network layer built on the Internet Protocol (IP) transport layer, and a GTP-U layer built on top of the UDP and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be built on top of the IP layer and may provide guaranteed delivery of application layer messages. Within the transport IP layer, signaling PDUs are delivered using point-to-point transport. In other implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0073] RAN 110 is shown as being communicatively coupled to a core network—in this embodiment, to a core network (CN) 120. CN 120 may include multiple network elements 122 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of multiple UEs 101) connected to CN 120 via RAN 110. Components of CN 120 may be implemented in one physical node or separate physical nodes, 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, NFV may be 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 a network slice, and a logical instance of a portion of CN 120 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively, performed by proprietary hardware). In other words, the NFV system can be used to perform virtual or reconfigurable implementations of one or more EPC components / functions.

[0074] Generally speaking, the application server 130 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 130 may also be configured to support one or more communication services for the UE 101 via the EPC 120 (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0075] In a specific implementation, the CN 120 may be a 5GC (referred to as "5GC 120" or the like), and the RAN 110 may be connected to the CN 120 via an NG interface 113. In a specific implementation, the NG interface 113 may be divided into two parts: an NG user plane (NG-U) interface 114, which carries traffic data between the RAN node 111 and the UPF; and an SI control plane (NG-C) interface 115, which is a signaling interface between the RAN node 111 and the AMF. Figure 3 Discussed in more detail, CN 120 is a specific implementation of 5GC 120.

[0076] In certain implementations, CN 120 may be a 5G CN (referred to as "5GC 120," etc.), while in other implementations, CN 120 may be an EPC. In the case where CN 120 is an EPC (referred to as "EPC 120," etc.), RAN 110 may be connected to CN 120 via an S1 interface 113. In certain implementations, S1 interface 113 may be divided into two parts: an S1 user plane (S1-U) interface 114, which carries traffic data between RAN node 111 and the S-GW; and an S1-MME interface 115, which is a signaling interface between RAN node 111 and the MME.

[0077] Figure 2 An exemplary architecture of a system 200 including a first core network (CN) 220 according to various implementations is shown. In this example, the system 200 may implement the LTE standard, wherein the CN 220 is a core network corresponding to the LTE standard. Figure 1 In addition, UE 201 can communicate with EPC 220 of CN 120. Figure 1 The UE 101 is the same as or similar to the UE 101, and the E-UTRAN 210 may be the same as Figure 1 The CN 220 may be a RAN that is the same as or similar to the RAN 110 of the mobile network, and may include the RAN node 111 discussed previously. The CN 220 may include an MME 221, an S-GW 222, a P-GW 223, an HSS 224, and an SGSN 225.

[0078] MME 221 may be functionally similar to the control plane of a traditional SGSN and may implement MM functionality to keep track of the current location of UE 201. MME 221 may perform various MM procedures to manage mobility aspects of access, such as gateway selection and tracking area list management. MM (also referred to as "EPS MM" or "EMM" in E-UTRAN systems) may refer to all applicable procedures, methods, data stores, etc. used to maintain knowledge of the current location of UE 201, provide user identity confidentiality to users / subscribers, and / or perform other similar services. Each UE 201 and MME 221 may include an MM or EMM sublayer, and upon successful completion of the attach procedure, an MM context may be established in both UE 201 and MME 221. An MM context may be a data structure or database object that stores MM-related information for UE 201. MME 221 may be coupled to HSS 224 via the S6a reference point, to SGSN 225 via the S3 reference point, and to S-GW 222 via the S11 reference point.

[0079] SGSN 225 may be a node that serves UE 201 by tracking the location of individual UE 201 and performing security functions. Furthermore, SGSN 225 may perform inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by MME 221; handling of UE 201 time zone capabilities, as specified by MME 221; and MME selection for handover to E-UTRAN 3GPP access networks. The S3 reference point between MME 221 and SGSN 225 may enable the exchange of user and bearer information for inter-3GPP access network mobility in idle and / or active states.

[0080] HSS 224 may include a database for network users, including subscription-related information used to support network entities handling communication sessions. EPC 220 may include one or several HSSs 224, depending on the number of mobile subscribers, device capabilities, network organization, and the like. For example, HSS 224 may provide support for routing / roaming, authentication, authorization, naming / addressing solutions, location dependencies, and the like. The S6a reference point between HSS 224 and MME 221 may enable the transfer of subscription and authentication data for authenticating / authorizing users to access EPC 220 between HSS 224 and MME 221.

[0081] The S-GW 222 may terminate the S1 interface 113 towards the RAN 210 (at Figure 2 The S-GW 222 is a RAN-based mobile gateway ("S1-U") and routes data packets between the RAN 210 and the EPC 220. Additionally, the S-GW 222 can serve as the local mobility anchor for inter-RAN node handovers and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and policy enforcement. The S11 reference point between the S-GW 222 and the MME 221 can provide the control plane between the MME 221 and the S-GW 222. The S-GW 222 can couple to the P-GW 223 via the S5 reference point.

[0082] The P-GW 223 may terminate the SGi interface towards the PDN 230. The P-GW 223 may communicate with the PDN 230 via the IP interface 125 (see, e.g., Figure 1 ) routes data packets between the EPC 220 and an external network such as a network including an application server 130 (alternatively referred to as "AF"). In a specific implementation, the P-GW 223 may communicate with the EPC 220 via the IP communication interface 125 (see, for example, Figure 1 ) is communicatively coupled to an application server ( Figure 1 Application server 130 or Figure 2230). The S5 reference point between the P-GW 223 and the S-GW 222 may provide user plane tunneling and tunnel management between the P-GW 223 and the S-GW 222. The S5 reference point may also be used for S-GW 222 relocation due to the mobility of the UE 201 and whether the S-GW 222 needs to connect to a non-collocated P-GW 223 for PDN connectivity. The P-GW 223 may also include nodes for policy enforcement and charging data collection, such as a PCEF (not shown). In addition, the SGi reference point between the P-GW 223 and the packet data network (PDN) 230 may be an operator external public, private PDN, or an intra-operator packet data network, for example, for providing IMS services. The P-GW 223 may be coupled to the PCRF 226 via a Gx reference point.

[0083] PCRF 226 is the policy and charging control element of EPC 220. In a non-roaming scenario, a single PCRF 226 may exist in the Home Public Land Mobile Network (HPLMN) associated with UE 201's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local traffic breakout, two PCRFs may be associated with UE 201's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). PCRF 226 may be communicatively coupled to application server 230 via P-GW 223. Application server 230 may signal PCRF 226 to indicate a new service flow and select appropriate QoS and charging parameters. PCRF 226 may configure the rules to a PCEF (not shown) with the appropriate TFT and QCI, which initiates QoS and charging as specified by application server 230. The Gx reference point between PCRF 226 and P-GW 223 may allow for the transfer of QoS policies and charging rules from PCRF 226 to PCEF in P-GW 223. The Rx reference point may reside between PDN 230 (or "AF 230") and PCRF 226.

[0084] Figure 3The architecture of an exemplary system 300 including a second core network (CN) 320 according to various implementations is shown. System 300 is shown to include a UE 301, which can be the same as or similar to UE 102 and UE 201 discussed previously; an (R)AN 310, which can be the same as or similar to RAN 110 and RAN 210 discussed previously and can include RAN node 111 discussed previously; a DN 303, which can be, for example, an operator service, internet access, or a third-party service; and CN 320, which in some implementations is a 5GC. 5GC 320 includes AUSF 322; AMF 321; SMF 324; NEF 323; PCF 326; NRF 325; UDM 327; AF 328; UPF 302; and NSSF 329.

[0085] The UPF 302 can serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnecting with the DN 303, and a branching point supporting multi-homed PDU sessions. The UPF 302 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, perform lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF to QoS flow mapping), transport-level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 302 may include an uplink classifier to support routing of traffic flows to the data network. The DN 303 may represent various network operator services, internet access, or third-party services. The DN 303 may include or be similar to the application server 130 discussed previously. The UPF 302 may interact with the SMF 324 via the N4 reference point between the SMF 324 and the UPF 302.

[0086] The AUSF 322 may store data used for authentication of the UE 301 and handle authentication-related functions. The AUSF 322 may facilitate a common authentication framework for various access types. The AUSF 322 may communicate with the AMF 321 via the N12 reference point between the AMF 321 and the AUSF 322; and may communicate with the UDM 327 via the N13 reference point between the UDM 327 and the AUSF 322. In addition, the AUSF 322 may present an interface based on the NAUSF service.

[0087] AMF 321 may be responsible for registration management (e.g., responsible for registering UE 301, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, as well as access authentication and authorization. AMF 321 may be the termination point of the N11 reference point between AMF 321 and SMF 324. AMF 321 may provide transport for SM messages between UE 301 and SMF 324 and act as a transparent proxy for routing SM messages. AMF 321 may also provide communication between UE 301 and SMSF ( Figure 3 301). The AMF 321 may act as a SEAF, which may include interaction with the AUSF 322 and the UE 301, receiving intermediate keys established as a result of the UE 301 authentication process. In the case of using USIM-based authentication, the AMF 321 may retrieve security material from the AUSF 322. The AMF 321 may also include an SCM function that receives keys for deriving access network specific keys from the SEA. In addition, the AMF 321 may be the termination point of the RAN CP interface, which may include or be the N2 reference point between the (R)AN 310 and the AMF 321; and the AMF 321 may be the termination point of NAS (N1) signaling and perform NAS encryption and integrity protection.

[0088] The AMF 321 may also support NAS signaling with the UE 301 over the N3 IWF interface. The N3 IWF may be used to provide access to untrusted entities. The N3 IWF may be the termination point for the N2 interface between the (R)AN 310 and the AMF 321 for the control plane, and may be the termination point for the N3 reference point between the (R)AN 310 and the UPF 302 for the user plane. Thus, the AMF 321 may process N2 signaling for PDU sessions and QoS from the SMF 324 and the AMF 321, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and perform QoS corresponding to N3 packet markings, taking into account the QoS requirements associated with such markings received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between the UE 301 and the AMF 321 via the N1 reference point between the UE 301 and the AMF 321, and relay uplink and downlink user plane packets between the UE 301 and the UPF 302. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 301. The AMF 321 may present an interface based on Namf services and may be an N14 reference point between two AMFs 321 and an N14 reference point between the AMF 321 and the 5G-EIR ( Figure 3 The termination point of the N17 reference point between the two reference points (not shown).

[0089] UE 301 may need to register with AMF 321 in order to receive network services. RM is used to register UE 301 with the network (e.g., AMF 321) or deregister the UE and establish a UE context in the network (e.g., AMF 321). UE 301 may operate in RM-REGISTERED state or RM-DEREGISTERED state. In RM-DEREGISTERED state, UE 301 is not registered with the network, and the UE context in AMF 321 does not hold valid location or routing information of UE 301, so AMF 321 cannot reach UE 301. In RM-REGISTERED state, UE 301 is registered with the network, and the UE context in AMF 321 may hold valid location or routing information of UE 301, so AMF 321 can reach UE 301. In the RM-REGISTERED state, UE 301 may perform a mobility registration update procedure, perform a periodic registration update procedure triggered by the expiration of a periodic update timer (e.g., to inform the network that UE 301 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.

[0090] The AMF 321 may store one or more RM contexts for the UE 301, where each RM context is associated with a specific access to the network. The RM context may be a data structure, a database object, or the like that indicates or stores, among other things, the registration status and periodic update timer for each access type. The AMF 321 may also store a 5GC MM context that may be the same as or similar to the (E)MM context discussed previously. In various implementations, the AMF 321 may store the CE Mode B restriction parameters for the UE 301 in the associated MM context or RM context. The AMF 321 may also derive values ​​from the UE's usage setting parameters already stored in the UE context (and / or MM / RM context) when needed.

[0091] The CM can be used to establish and release a signaling connection between the UE 301 and the AMF 321 over the N1 interface. The signaling connection is used to enable NAS signaling exchanges between the UE 301 and the CN 320, and includes a signaling connection between the UE and the AN (e.g., an RRC connection or a UE-N3IWF connection for non-3GPP access) and the UE 301's N2 connection between the AN (e.g., the RAN 310) and the AMF 321. The UE 301 can operate in one of two CM states: CM-IDLE mode or CM-CONNECTED mode. When the UE 301 operates in the CM-IDLE state / mode, the UE 301 may not have a NAS signaling connection established with the AMF 321 over the N1 interface, and a (R)AN 310 signaling connection (e.g., an N2 and / or N3 connection) may exist for the UE 301. When the UE 301 operates in the CM-CONNECTED state / mode, the UE 301 may have a NAS signaling connection established with the AMF 321 through the N1 interface, and there may be a (R)AN 310 signaling connection (e.g., N2 and / or N3 connection) for the UE 301. Establishing an N2 connection between the (R)AN 310 and the AMF 321 may cause the UE 301 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the (R)AN 310 and the AMF 321 is released, the UE 301 may transition from the CM-CONNECTED mode to the CM-IDLE mode.

[0092] The SMF 324 may be responsible for SM (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring the UPF's traffic steering to route traffic to the correct destination; terminating the interface towards the policy control function; control portion of policy enforcement and QoS; lawful interception (for SM events and interface with the LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to the AN via the AMF over N2; and determining the SSC mode for the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 301 and the data network (DN) 303 identified by a data network name (DNN). A PDU session may be established upon request by UE 301, modified upon request by UE 301 and 5GC 320, and released upon request by UE 301 and 5GC 320 using NAS SM signaling exchanged between UE 301 and SMF 324 over the N1 reference point. Upon request from an application server, 5GC 320 may trigger a specific application in UE 301. In response to receiving the trigger message, UE 301 may deliver the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 301. The identified applications in UE 301 may establish a PDU session to a specific DNN. SMF 324 may check whether the UE 301 request complies with user subscription information associated with UE 301. In this regard, SMF 324 may retrieve and / or request to receive update notifications regarding SMF 324-level subscription data from UDM 327.

[0093] The SMF 324 may include the following roaming functions: handling local execution to apply QoS SLAs (VPLMN); charging data collection and billing interfaces (VPLMN); lawful interception (for SM events and interfaces with LI systems, in VPLMN); and support for interaction with external DNs to transport signaling for PDU session authorization / authentication through external DNs. In roaming scenarios, an N16 reference point between two SMFs 324 may be included in the system 300, which may be located between an SMF 324 in a visited network and another SMF 324 in a home network. In addition, the SMF 324 may present an interface based on Nsmf services.

[0094] NEF 323 may provide components for securely exposing services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, application functions (e.g., AF 328), edge computing or fog computing systems, and the like. In such implementations, NEF 323 may authenticate, authorize, and / or restrict the AF. NEF 323 may also convert information exchanged with AF 328 and information exchanged with internal network functions. For example, NEF 323 may convert between AF service identifiers and internal 5GC information. NEF 323 may also receive information from other network functions (NFs) based on their exposed capabilities. This information may be stored as structured data at NEF 323 or at a data storage NF using standardized interfaces. The stored information may then be re-exposed by NEF 323 to other NFs and AFs and / or used for other purposes such as analysis. In addition, NEF 323 may present an interface based on NNEF services.

[0095] NRF 325 can support service discovery functionality, receiving NF discovery requests from NF instances and providing information about discovered NF instances to NF instances. NRF 325 also maintains information about available NF instances and the services supported by these instances. As used herein, the term "instantiation" and the like can refer to the creation of an instance, and "instance" can refer to the specific occurrence of an object, which can occur, for example, during the execution of program code. In addition, NRF 325 can present an interface based on Nnrf services.

[0096] The PCF 326 may provide control plane functions for enforcing their policy rules and may also support a unified policy framework for managing network behavior. The PCF 326 may also enable the FE to access subscription information related to policy decisions in the UDM 327's UDR. The PCF 326 may communicate with the AMF 321 via the N15 reference point between the PCF 326 and the AMF 321, which may include the PCF 326 in the visited network and the AMF 321 in roaming scenarios. The PCF 326 may communicate with the AF 328 via the N5 reference point between the PCF 326 and the AF 328, and with the SMF 324 via the N7 reference point between the PCF 326 and the SMF 324. The system 300 and / or CN 320 may also include an N24 reference point between the PCF 326 (in the home network) and the PCF 326 in the visited network. In addition, the PCF 326 may present an Npcf service-based interface.

[0097] The UDM 327 may process subscription-related information to support network entities in handling communication sessions and may store subscription data for the UE 301. For example, subscription data may be transferred between the UDM 327 and the AMF 321 via the N8 reference point between the UDM 327 and the AMF. The UDM 327 may include two parts: the application FE and the UDR ( Figure 3 FE and UDR are not shown). The UDR can store subscription data and policy data of the UDM 327 and PCF 326, and / or structured data for exposure and application data of the NEF 323 (including PFD for application detection, application request information of multiple UEs 301). An interface based on Nudr service can be presented by the UDR 221 to allow the UDM 327, PCF 326 and NEF 323 to access specific sets of stored data, as well as read, update (e.g., add, modify), delete and subscribe to notifications of changes to relevant data in the UDR. The UDM may include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different front ends may serve the same user. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management and subscription management. The UDR can interact with the SMF 324 via the N10 reference point between the UDM 327 and the SMF 324. UDM 327 may also support SMS management, where SMS-FE implements similar application logic discussed previously. Additionally, UDM 327 may present an interface based on Nudm services.

[0098] AF 328 can provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE can be a mechanism that allows the 5GC 320 and AF 328 to provide information to each other via the NEF 323, which can be used in edge computing implementations. In such implementations, network operators and third-party services can be hosted near the UE 301 access point to achieve efficient service delivery with reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can select a UPF 302 near the UE 301 and perform traffic steering from the UPF 302 to the DN 303 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by the AF 328. In this way, the AF 328 can influence UPF (re)selection and traffic routing. Based on operator deployment, when the AF 328 is considered a trusted entity, the network operator may allow the AF 328 to interact directly with the relevant NF. In addition, the AF 328 can present an interface based on the NAF service.

[0099] The NSSF 329 may select a set of network slice instances to serve the UE 301. If required, the NSSF 329 may also determine the allowed NSSAIs and the mapping to the subscribed S-NSSAIs. The NSSF 329 may also determine the set of AMFs to serve the UE 301, or a list of candidate AMFs 321, based on appropriate configuration and possibly by querying the NRF 325. The selection of a set of network slice instances for the UE 301 may be triggered by the AMF 321, where the UE 301 registers by interacting with the NSSF 329, which may result in a change in the AMF 321. The NSSF 329 may interact with the AMF 321 via the N22 reference point between the AMF 321 and the NSSF 329; and may communicate via the N31 reference point ( Figure 3 The NSSF 329 may communicate with another NSSF 329 in the visited network (not shown). In addition, the NSSF 329 may present an interface based on the Nnssf service.

[0100] As previously discussed, CN 320 may include an SMSF that may be responsible for SMS subscription checking and verification, and relaying SM messages to / from UE 301 to / from other entities, such as SMS-GMSC / IWMSC / SMS routers. SMS may also interact with AMF 321 and UDM 327 for notification procedures that UE 301 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 327 when UE 301 is available for SMS).

[0101] CN 120 may also include Figure 3 Other elements not shown, such as data storage system / architecture, 5G-EIR, SEPP, etc. The data storage system may include SDSF, UDSF, etc. Any NF can communicate with any NF and UDSF ( Figure 3 The N18 reference point between the NF and the NF (not shown) stores or retrieves unstructured data into or from the UDSF (e.g., UE context). A single NF may share a UDSF for storing its respective unstructured data, or each NF may have its own UDSF located at or near a single NF. In addition, the UDSF may present an interface based on Nudsf services ( Figure 3 (not shown). The 5G-EIR may be a NF that checks the status of the PEI to determine whether to blacklist a specific device / entity from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface.

[0102] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Figure 3These interfaces and reference points are omitted. In one example, CN 320 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 221) and an AMF 321, to enable interworking between CN 320 and CN 220. Other example interfaces / reference points may include an interface based on N5g-EIR services presented by the 5G-EIR, an N27 reference point between an NRF in a visited network and an NRF in a home network; and an N31 reference point between an NSSF in a visited network and an NSSF in a home network.

[0103] Figure 4 An example of infrastructure equipment 400 according to various implementations is shown. Infrastructure equipment 400 (or "system 400") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 111 and / or AP 106 shown and described previously), an application server 130, and / or any other element / device discussed herein. In some cases, system 400 can be implemented in or by a UE.

[0104] System 400 includes application circuitry 405, baseband circuitry 410, one or more radio front-end modules (RFEMs) 415, memory circuitry 420, a power management integrated circuit (PMIC) 425, power tee circuitry 430, network controller circuitry 435, a network interface connector 440, satellite positioning circuitry 445, and a user interface 450. In some implementations, device 400 may include additional components such as, for example, memory / storage, a display, a camera, sensors, or input / output (I / O) interfaces. In other implementations, the components described below may be included in more than one device. For example, the circuitry may be separately included in more than one device for a CRAN, vBBU, or other similar implementation.

[0105] The application circuit 405 includes, but is not limited to, one or more processors (or processor cores), cache memory, and one or more low dropout regulators (LDOs), an interrupt controller, a serial interface such as SPI, 2C or general programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, general input / output (I / O or IO), a memory card controller such as a secure digital (SD) multimedia card (MMC) or similar product, a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a joint test access group (JTAG) test access port. The processor (or core) of the application circuit 405 can be coupled to or include a memory / storage element and can be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the system 400. In some embodiments, the memory / storage element can be an on-chip memory circuit that can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0106] The processor of the application circuit 405 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some implementations, the application circuit 405 may include or may be a dedicated processor / controller for operating in accordance with various implementations herein. As an example, the processor of the application circuit 405 may include one or more Intel or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU), or processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some implementations, the system 400 may not utilize the application circuit 405 and instead may include a dedicated processor / controller to process IP data received, for example, from the EPC or 5GC.

[0107] In some implementations, the application circuit 405 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs) and high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of the application circuit 405 may include logic blocks or logic architectures, as well as other interconnected resources that can be programmed to perform various functions, such as the processes, methods, functions, and the like of the various implementations discussed herein. In such a specific implementation, the circuitry of the application circuit 405 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in look-up tables (LUTs), etc.

[0108] The baseband circuit 410 may be implemented as, for example, a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module including two or more integrated circuits. Figure 6 The various hardware electronic components of baseband circuitry 410 are discussed.

[0109] User interface circuitry 450 may include one or more user interfaces designed to enable a user to interact with system 400 or peripheral component interfaces designed to enable peripheral components to interact with system 400. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touch screen, a speaker or other audio emitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power port, etc.

[0110] The radio front end module (RFEM) 415 may include a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separate from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, for example, below). Figure 6The antenna array 611 is configured such that the RFEM can be connected to multiple antennas. In an alternative embodiment, both millimeter-wave and sub-millimeter-wave radio functions can be implemented in the same physical RFEM 415, which combines both millimeter-wave antennas and sub-millimeter-wave antennas.

[0111] The memory circuit 420 may include one or more of the following: a volatile memory such as a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM), a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as a "flash memory"), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 420 may be implemented as one or more of the following: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0112] The PMIC 425 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as batteries or capacitors. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 430 may provide power drawn from the network cable to provide both power and data connectivity for the infrastructure equipment 400 using a single cable.

[0113] The network controller circuit 435 can provide connectivity to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on Multi-Protocol Label Switching (MPLS), or some other suitable protocol. Network connectivity can be provided to / from the infrastructure equipment 400 via the network interface connector 440 using a physical connection, which can be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 435 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the network controller circuit 435 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0114] The positioning circuit 445 includes circuitry for receiving and decoding signals transmitted / broadcasted by a positioning network of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., navigation using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radiolocation (DORIS), etc.). The positioning circuit 445 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network, such as navigation satellite constellation nodes. In some implementations, the positioning circuit 445 may include a micro technology (micro-PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 445 may also be part of or interact with the baseband circuit 410 and / or the RFEM 415 to communicate with nodes and components of the positioning network. The positioning circuit 445 may also provide location data and / or time data to the application circuit 405, which may use the data to synchronize operations with various infrastructure (e.g., the RAN node 111, etc.), etc.

[0115] Figure 4 The components shown may communicate with each other using interface circuitry that may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX may be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems may be included, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0116] Figure 5 Examples of platform 500 (or "device 500") according to various implementations are shown. In specific implementations, platform 500 may be suitable for use as UE 101, 201, 301, application server 130, and / or any other element / device discussed herein. Platform 500 may include any combination of the components shown in the examples. Components of platform 500 may be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted within computer platform 500, or as components otherwise incorporated within the chassis of a larger system. Figure 5The block diagram is intended to show a high-level view of the components of platform 500. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0117] Application circuit 505 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and LDO, interrupt controller, serial interface (such as SPI), I 2 The application circuit 505 may include one or more of a C or general programmable serial interface module, an RTC, a timer (including an interval timer and a watchdog timer), general I / O, a memory card controller (such as an SD MMC or similar controller), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of the application circuit 505 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 500. In some embodiments, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0118] The processor of the application circuit 405 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multi-threaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some specific implementations, the application circuit 405 may include or may be a dedicated processor / controller for operating according to various specific implementations herein.

[0119] As an example, the processor of the application circuit 505 may include a processor based on Architecture TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA The processor of application circuit 505 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, Snapdragon by Technologies, Inc. TM processors, Texas Instruments, Open Multimedia Applications Platform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some implementations, the application circuit 505 can be part of a system on a chip (SoC), in which the application circuit 505 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.

[0120] Additionally or alternatively, the application circuit 505 may include circuitry such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs such as structured ASICs; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of the application circuit 505 may include logic blocks or logic structures, as well as other interconnected resources that can be programmed to perform various functions, such as the processes, methods, functions, and the like of the various implementations discussed herein. In such implementations, the circuitry of the application circuit 505 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), antifuse), and the like) for storing logic blocks, logic structures, data, and the like in lookup tables (LUTs) and the like.

[0121] The baseband circuit 510 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module including two or more integrated circuits. Figure 6 The various hardware electronic components of baseband circuit 510 are discussed.

[0122] The RFEM 515 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separate from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, for example, below). Figure 6 The antenna array 611 is configured such that the RFEM can be connected to multiple antennas. In an alternative embodiment, both millimeter-wave and sub-millimeter-wave radio functions can be implemented in the same physical RFEM 515, which combines both millimeter-wave antennas and sub-millimeter-wave antennas.

[0123] The memory circuit 520 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuit 520 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM), and / or synchronous dynamic RAM (SDRAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as flash memory), phase-change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 520 may be developed according to a Joint Electron Device Engineering Council (JEDEC) low-power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 520 may be implemented as one or more of the following: a solder-in package integrated circuit, a single die package (SDP), a dual die package (DDP), or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 520 may be on-chip memory or registers associated with the application circuit 505. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 520 may include one or more mass storage devices, which may include, among others, a solid-state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 500 may be combined with a computer system obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0124] Removable memory circuitry 523 may include devices, circuitry, housings / casings, ports or receptacles, and the like for coupling portable data storage devices to platform 500. These portable data storage devices may be used for mass storage and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD picture cards, and the like), as well as USB flash drives, optical disks, external HDDs, and the like.

[0125] Platform 500 may also include an interface circuit (not shown) for connecting external devices to platform 500. External devices connected to platform 500 via the interface circuit include sensor circuit 521 and electromechanical components (EMC) 522, and a removable memory device coupled to removable memory circuit 523.

[0126] Sensor circuitry 521 comprises a device sensor, module, or subsystem designed to detect events or changes in its environment and to send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit (IMU) including an accelerometer, gyroscope, and / or magnetometer; a microelectromechanical system (MEMS) or nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a fluid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0127] The EMC 522 includes devices, modules, or subsystems designed to enable the platform 500 to change its state, position, and / or orientation, or to move or control mechanisms or (sub)systems. Furthermore, the EMC 522 can be configured to generate and send messages / signaling to other components of the platform 500 indicating the current state of the EMC 522. The EMC 522 includes one or more power switches, relays (including electromechanical relays (EMRs) and / or solid-state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and / or other similar electromechanical components. In specific implementations, the platform 500 is configured to operate one or more EMCs 522 based on one or more capture events and / or command or control signals received from service providers and / or various clients.

[0128] In some implementations, the interface circuitry may connect the platform 500 to the positioning circuitry 545. The positioning circuitry 545 includes circuitry for receiving and decoding signals transmitted / broadcasted by a GNSS positioning network. Examples of navigation satellite constellations (or GNSS) may include the United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.). The positioning circuitry 545 includes various hardware components (e.g., including hardware devices for facilitating over-the-air (OTA) communications, such as switches, filters, amplifiers, antenna elements, etc.) to communicate with components of the positioning network, such as nodes of the navigation satellite constellation. In some implementations, the positioning circuitry 545 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuitry 545 may also be part of or interact with the baseband circuitry 410 and / or the RFEM 515 to communicate with nodes and components of the positioning network. Positioning circuitry 545 may also provide position data and / or time data to application circuitry 505 , which may use the data to synchronize operations with various infrastructure (eg, radio base stations) for use in turn-by-turn navigation applications, and the like.

[0129] In some implementations, the interface circuitry can connect the platform 500 to a near-field communication (NFC) circuitry 540. The NFC circuitry 540 is configured to provide contactless, short-range communication based on the radio frequency identification (RFID) standard, where magnetic field induction is used to enable communication between the NFC circuitry 540 and an NFC-enabled device (e.g., an "NFC touchpoint") external to the platform 500. The NFC circuitry 540 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller can be a chip / IC that provides NFC functionality to the NFC circuitry 540 by executing NFC controller firmware and an NFC stack. The NFC stack can be executed by the processor to control the NFC controller, and the NFC controller firmware can be executed by the NFC controller to control the antenna element to transmit short-range RF signals. The RF signals can power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuitry 540, or initiate data transfer between the NFC circuitry 540 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) in close proximity to the platform 500.

[0130] Driver circuitry 546 may include software and hardware components for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to platform 500. Driver circuitry 546 may include various drivers to allow other components of platform 500 to interact with or control various input / output (I / O) devices that may be present within or connected to platform 500. For example, driver circuitry 546 may include a display driver for controlling and enabling access to a display device, a touch screen driver for controlling and enabling access to a touch screen interface of platform 500, a sensor driver for acquiring sensor readings from sensor circuitry 521 and controlling and enabling access to sensor circuitry 521, an EMC driver for acquiring actuator positions of EMC 522 and / or controlling and enabling access to EMC 522, a camera driver for controlling and enabling access to an embedded image capture device, and an audio driver for controlling and enabling access to one or more audio devices.

[0131] A power management integrated circuit (PMIC) 525 (also referred to as "power management circuit 525") can manage the power provided to various components of the platform 500. Specifically, the PMIC 525 can control power source selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuit 510. When the platform 500 is capable of being powered by a battery 530, for example, when the device is included in a UE 101, 201, or 301, the PMIC 525 is typically included.

[0132] In some implementations, the PMIC 525 can control or otherwise be part of various power-saving mechanisms of the platform 500. For example, if the platform 500 is in the RRC_Connected state, in which it remains connected to the RAN node because it expects to receive traffic soon, after a period of inactivity, the platform can enter a state known as discontinuous reception mode (DRX). During this state, the platform 500 can power down for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 500 can transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The platform 500 enters a very low-power state and performs paging, in which the device periodically wakes up again to listen to the network, and then powers down again. The platform 500 may not receive data in this state; to receive data, the platform transitions back to the RRC_Connected state. Additional power-saving modes can prevent the device from using the network for periods exceeding the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will incur significant delays, assuming that the delay is acceptable.

[0133] Battery 530 can power platform 500, but in some examples, platform 500 can be installed in a fixed location and can have a power source coupled to the power grid. Battery 530 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, battery 530 can be a typical lead-acid car battery.

[0134] In some implementations, the battery 530 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS may be included in the platform 500 to track the state of charge (SoCh) of the battery 530. The BMS may be used to monitor other parameters of the battery 530, such as the state of health (SoH) and state of function (SoF) of the battery 530 to provide fault prediction. The BMS may transmit information about the battery 530 to the application circuit 505 or other components of the platform 500. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 505 to directly monitor the voltage of the battery 530 or the current from the battery 530. The battery parameters may be used to determine actions that the platform 500 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0135] A power block or other power source connected to the grid can be coupled to the BMS to charge the battery 530. In some examples, the power block XS30 can be replaced with a wireless power receiver to wirelessly acquire power, for example, via a loop antenna in the computer platform 500. In these examples, wireless battery charging circuitry can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 530 and, therefore, the required current. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Consortium, or the Rezence charging standard published by the Wireless Power Consortium.

[0136] The user interface circuit 550 includes various input / output (I / O) devices present within or connected to the platform 500, and includes one or more user interfaces designed to implement user interaction with the platform 500 and / or peripheral component interfaces designed to implement interaction with peripheral components of the platform 500. The user interface circuit 550 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a trackpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary state indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as a display device or touch screen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, a projector, etc.), wherein the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the platform 500. The output device circuitry may also include a speaker or other audio emitting device, a printer, etc. In some implementations, the sensor circuitry 521 may function as an input device circuitry (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may function as output device circuitry (e.g., an actuator for providing tactile feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power port, etc.

[0137] Although not shown, the components of the platform 500 may communicate with each other using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a time-triggered protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus / IX may be a proprietary bus / IX, such as used in SoC-based systems. Other bus / IX systems, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0138] Figure 6 Exemplary components of a baseband circuit 610 and a radio front end module (RFEM) 615 are shown according to various implementations. The baseband circuit 610 corresponds to Figure 4 The baseband circuit 410 and Figure 5 Baseband circuit 510. RFEM 615 corresponds to Figure 4 RFEM 415 and Figure 5 RFEM 515. As shown, RFEM 615 may include at least a radio frequency (RF) circuit 606, a front end module (FEM) circuit 608, and an antenna array 611 coupled together as shown.

[0139] The baseband circuitry 610 includes circuitry and / or control logic configured to execute various radio / network protocols and radio control functions that enable communication with one or more radio networks via the RF circuitry 606. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, the modulation / demodulation circuitry of the baseband circuitry 610 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some implementations, the encoding / decoding circuitry of the baseband circuitry 610 may include convolution, tail-biting, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The specific implementations of the modulation / demodulation and encoder / decoder functions are not limited to these examples and may include other suitable functions in other aspects. The baseband circuitry 610 is configured to process baseband signals received from the receive signal path of the RF circuitry 606 and to generate baseband signals for the transmit signal path of the RF circuitry 606. The baseband circuitry 610 is configured to communicate with the application circuitry 405 / 505 (see Figure 4 and Figure 5 ) are connected to generate and process baseband signals and control the operation of RF circuit 606. Baseband circuit 610 can handle various radio control functions.

[0140] The aforementioned circuits and / or control logic components of the baseband circuitry 610 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 604A, a 4G / LTE baseband processor 604B, a 5G / NR baseband processor 604C, or some other baseband processor 604D for other existing, developing, or future generations (e.g., the sixth generation (6G), etc.). In other specific implementations, some or all of the functionality of the baseband processors 604A-D may be included in modules stored in the memory 604G and executed via the central processing unit (CPU) 604E. In other specific implementations, some or all of the functionality of the baseband processors 604A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with appropriate bitstreams or logic blocks stored in corresponding memory units. In various specific implementations, the memory 604G may store program code of a real-time OS (RTOS), which, when executed by the CPU 604E (or other baseband processor), enables the CPU 604E (or other baseband processor) to manage resources of the baseband circuit 610, schedule tasks, etc. Examples of RTOS may include Operating System Embedded (OSE) TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-Time Executive (VRTX) provided by Express ThreadX TM ,Depend on FreeRTOS and REX OS provided by OpenKernel (OK) The baseband circuit 610 may include one or more audio digital signal processors (DSPs) 604F. The audio DSPs 604F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other implementations.

[0141] In some implementations, each of the processors 604A-604E includes a corresponding memory interface to send data to / receive data from the memory 604G. The baseband circuit 610 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to the baseband circuit 610; an interface for sending data to / receiving data from a memory external to the baseband circuit; Figures 4 to 6Application circuit interface for sending data to / receiving data from the application circuit 405 / 505; Figure 6 RF circuit 606 to send data / receive data from the RF circuit RF circuit interface; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data / receive data from these wireless hardware elements; and a power management interface for sending power or control signals to / from the PMIC 525.

[0142] In an alternative embodiment (which may be combined with the above embodiment), the baseband circuit 610 includes one or more digital baseband systems that are coupled to each other and to the CPU subsystem, audio subsystem, and interface subsystem via an interconnect subsystem. The digital baseband subsystem may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, a point-to-point connection, a network on chip (NOC) structure, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 610 may include a protocol processing circuit having one or more control circuit instances (not shown) to provide control functions for the digital baseband circuit and / or the radio frequency circuit (e.g., the radio front end module 615).

[0143] although Figure 6Although not shown, in some implementations, the baseband circuitry 610 includes various processing devices (e.g., a "multi-protocol baseband processor" or "protocol processing circuitry") for operating one or more wireless communication protocols and various processing devices for implementing PHY layer functionality. In these implementations, the PHY layer functionality includes the aforementioned radio control functionality. In these implementations, the protocol processing circuitry operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuitry 610 and / or the RF circuitry 606 are part of millimeter wave communication circuitry or some other suitable cellular communication circuitry, the protocol processing circuitry may operate LTE protocol entities and / or 5G / NR protocol entities. In this first example, the protocol processing circuitry will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functionality. In a second example, when the baseband circuitry 610 and / or the RF circuitry 606 are part of a Wi-Fi communication system, the protocol processing circuitry may operate one or more IEEE-based protocols. In this second example, the protocol processing circuitry will operate Wi-Fi MAC and Logical Link Control (LLC) functionality. The protocol processing circuitry may include one or more memory structures (e.g., 604G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuitry 610 may also support radio communications for more than one wireless protocol.

[0144] The various hardware elements of the baseband circuit 610 discussed herein may be implemented as, for example, a solder-in substrate comprising one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module comprising two or more ICs. In one example, the components of the baseband circuit 610 may be appropriately combined in a single chip or a single chipset, or provided on the same circuit board. In another example, some or all of the components of the baseband circuit 610 and the RF circuit 606 may be implemented together, such as, for example, a system on a chip (SOC) or a system in a package (SiP). In another example, some or all of the components of the baseband circuit 610 may be implemented as a separate SoC communicatively coupled to the RF circuit 606 (or multiple instances of the RF circuit 606). In yet another example, some or all of the components of the baseband circuit 610 and the application circuit 405 / 505 may be implemented together as a separate SoC mounted to the same circuit board (e.g., a "multi-chip package").

[0145] In some implementations, the baseband circuitry 610 can provide communications compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 610 can support communications with E-UTRAN or other WMANs, WLANs, or WPANs. Implementations in which the baseband circuitry 610 is configured to support radio communications using more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0146] RF circuitry 606 can communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various implementations, RF circuitry 606 can include switches, filters, amplifiers, and the like to facilitate communication with the wireless network. RF circuitry 606 can include a receive signal path that can include circuitry for downconverting RF signals received from FEM circuitry 608 and providing baseband signals to baseband circuitry 610. RF circuitry 606 can also include a transmit signal path that can include circuitry for upconverting baseband signals provided by baseband circuitry 610 and providing an RF output signal to FEM circuitry 608 for transmission.

[0147] In some implementations, the receive signal path of RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b, and filter circuitry 606c. In some implementations, the transmit signal path of RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a. RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing frequencies for use by mixer circuitry 606a in the receive and transmit signal paths. In some implementations, mixer circuitry 606a in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d. Amplifier circuitry 606b may be configured to amplify the downconverted signal, and filter circuitry 606c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 610 for further processing. In some implementations, the output baseband signal can be a zero-frequency baseband signal.In some implementations, the mixer circuit 606a of the receive signal path can include a passive mixer, although the scope of the implementations is not limited in this respect.

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

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

[0150] In some implementations, the output baseband signal and the input baseband signal can be analog baseband signals, although the scope of the implementation is not limited in this respect. In some alternative implementations, the output baseband signal and the input baseband signal can be digital baseband signals. In these alternative implementations, the RF circuit 606 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and the baseband circuit 610 can include a digital baseband interface to communicate with the RF circuit 606.

[0151] In some dual-mode implementations, separate radio IC circuitry may be provided to process signals for each spectrum, although the scope of the implementations is not limited in this respect.

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

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

[0154] In some implementations, the frequency input is provided by a voltage controlled oscillator (VCO). The divider control input can be provided by the baseband circuit 610 or the application circuit 405 / 505 according to the desired output frequency. In some implementations, the divider control input (e.g., N) can be determined from a lookup table based on the channel indicated by the application circuit 405 / 505.

[0155] The synthesizer circuit 606d of the RF circuit 606 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some implementations, the frequency divider may be a dual-modulus divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some implementations, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some exemplary implementations, 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 implementations, 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. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0156] In some implementations, the synthesizer circuit 606d can be configured to generate a carrier frequency as the output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with multiple different phases relative to each other. In some implementations, the output frequency can be the LO frequency (fLO). In some implementations, the RF circuit 606 can include an IQ / polarity converter.

[0157] The FEM circuitry 608 may include a receive signal path that may include circuitry configured to operate on RF signals received from the antenna array 611, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 606 for further processing. The FEM circuitry 608 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 606 for transmission by one or more antenna elements in the antenna array 611. In various implementations, amplification by the transmit signal path or the receive signal path may be performed only in the RF circuitry 606, only in the FEM circuitry 608, or in both the RF circuitry 606 and the FEM circuitry 608.

[0158] In some implementations, the FEM circuitry 608 may include a TX / RX switch to switch between transmit and receive modes of operation. The FEM circuitry 608 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 608 may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 606). The transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuitry 606), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 611.

[0159] Antenna array 611 includes one or more antenna elements, each configured to convert electrical signals into radio waves for travel through the air and to convert received radio waves into electrical signals. For example, a digital baseband signal provided by baseband circuitry 610 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of antenna array 611, which includes one or more antenna elements (not shown). Antenna elements can be omnidirectional, directional, or a combination thereof. Antenna elements can be formed into various arrangements as known and / or discussed herein. Antenna array 611 can include microstrip antennas or printed antennas fabricated on the surface of one or more printed circuit boards. Antenna array 611 can be formed as patches of metal foil of various shapes (e.g., patch antennas) and can be coupled to RF circuitry 606 and / or FEM circuitry 608 using metal transmission lines or the like.

[0160] The processors of the application circuitry 405 / 505 and the processors of the baseband circuitry 610 may be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuitry 610 may be used, alone or in combination, to perform layer 3, layer 2, or layer 1 functions, while the processors of the application circuitry 405 / 505 may utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include the RRC layer, which is described in further detail below. As mentioned herein, layer 2 may include the MAC layer, the RLC layer, and the PDCP layer, which are described in further detail below. As mentioned herein, layer 1 may include the PHY layer of the UE / RAN node, which is described in further detail below.

[0161] Figure 7 The protocol functions used in wireless communication devices according to various specific implementations are shown. Specifically, Figure 7 The present invention includes an arrangement 700 showing the interconnection between various protocol layers / entities. The present invention provides various protocol layers / entities for operating in conjunction with the 5G / NR system standard and the LTE system standard. Figure 7The following description, but Figure 7 Some or all aspects of the present invention may also be applicable to other wireless communication network systems.

[0162] In addition to other higher layer functions not shown, the protocol layers of arrangement 700 may include one or more of PHY 710, MAC 720, RLC 730, PDCP 740, SDAP 747, RRC 755, and NAS layer 757. These protocol layers may include one or more service access points (e.g., Figure 7 Items 759, 756, 750, 749, 745, 735, 725, and 715).

[0163] The PHY 710 may send and receive physical layer signals 705, which may be received from or sent to one or more other communication devices. The physical layer signals 705 may include one or more physical channels, such as those discussed herein. The PHY 710 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers (e.g., RRC 755). The PHY 710 may further perform error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and MIMO antenna processing. In a specific implementation, an instance of the PHY 710 may process requests from an instance of the MAC 720 and provide instructions thereto via one or more PHY-SAPs 715. According to some specific implementations, the requests and instructions transmitted via the PHY-SAP 715 may include one or more transport channels.

[0164] Instances of MAC 720 may process requests from instances of RLC 730 and provide indications thereto via one or more MAC-SAPs 725. These requests and indications conveyed via MAC-SAP 725 may include one or more logical channels. MAC 720 may perform mapping between logical channels and transport channels, multiplexing MAC SDUs from one or more logical channels onto TBs to be delivered to PHY 710 via transport channels, demultiplexing MAC SDUs from TBs delivered from PHY 710 via transport channels onto one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via HARQ, and logical channel prioritization.

[0165] Instances of RLC 730 can process requests from instances of PDCP 740 and provide indications thereto via one or more Radio Link Control Service Access Points (RLC-SAPs) 735. These requests and indications conveyed via RLC-SAPs 735 can include one or more logical channels. RLC 730 can operate in multiple modes of operation, including Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). RLC 730 can perform transmission of upper 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 730 can also resegment RLC data PDUs for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.

[0166] An instance of PDCP 740 may process requests from an instance of RRC 755 and / or an instance of SDAP 747 and provide instructions thereto via one or more Packet Data Convergence Protocol Service Points (PDCP-SAPs) 745. These requests and instructions conveyed via PDCP-SAPs 745 may include one or more radio bearers. PDCP 740 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), enforce in-sequence delivery of upper layer PDUs upon lower layer reestablishment, eliminate duplication of lower layer SDUs upon lower layer reestablishment for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0167] An instance of SDAP 747 can process requests from one or more higher layer protocol entities and provide instructions to them via one or more SDAP-SAPs 749. These requests and instructions transmitted via SDAP-SAP 749 may include one or more QoS flows. SDAP 747 can map QoS flows to DRBs and vice versa, and can also mark the QFI in DL and UL packets. A single SDAP entity 747 can be configured for a separate PDU session. In the UL direction, NG-RAN 110 can control the mapping of QoS flows to DRBs in two different ways: reflective mapping or explicit mapping. For reflective mapping, SDAP 747 of UE 101 can monitor the QFI of DL packets for each DRB and apply the same mapping to packets flowing in the UL direction. For a DRB, SDAP 747 of UE 101 can map UL packets belonging to a QoS flow that corresponds to the QoS flow ID and PDU session observed in the DL packets of that DRB. To implement reflective mapping, the NG-RAN 310 may tag DL packets with a QoS flow ID over the Uu interface. Explicit mapping may involve the RRC 755 configuring the SDAP 747 with explicit mapping rules for QoS flows to DRBs, which may be stored and followed by the SDAP 747. In a specific implementation, the SDAP 747 may only be used in NR implementations and may not be used in LTE implementations.

[0168] The RRC 755 may configure aspects of one or more protocol layers, which may include one or more instances of the PHY 710, MAC 720, RLC 730, PDCP 740, and SDAP 747, via one or more Management Service Access Points (M-SAPs). In a specific implementation, an instance of the RRC 755 may process requests from one or more NAS entities 757 and provide instructions thereto via one or more RRC-SAPs 756. The main services and functions of the RRC 755 may include broadcasting of system information (e.g., included in a MIB or SIB related to the NAS), broadcasting of system information related to the access stratum (AS), paging, establishment, maintenance, and release of the RRC connection between the UE 101 and the RAN 110 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. These MIBs and SIBs may include one or more IEs, each of which may include a separate data field or data structure.

[0169] NAS 757 may form the highest layer of the control plane between UE 101 and AMF 321. NAS 757 may support mobility and session management procedures of UE 1701 to establish and maintain an IP connection between UE 101 and P-GW in the LTE system.

[0170] According to various implementations, one or more protocol entities of arrangement 700 may be implemented in UE 101, RAN node 111, AMF 321 in NR implementations or MME 221 in LTE implementations, UPF 302 in NR implementations or S-GW 222 and P-GW 223 in LTE implementations, etc., for control plane or user plane communication protocol stacks between the aforementioned devices. In such implementations, one or more protocol entities that may be implemented in one or more of UE 101, gNB 111, AMF 321, etc. may communicate with corresponding peer protocol entities that may be implemented in or on another device (using services of corresponding lower layer protocol entities to perform such communication). In some implementations, the gNB-CU of gNB 111 may host the gNB's RRC 755, SDAP 747, and PDCP 740 that control operations of one or more gNB-DUs, and the gNB-DUs of gNB 111 may each host the RLC 730, MAC 720, and PHY 710 of gNB 111.

[0171] In a first example, the control plane protocol stack may include, in order from highest layer to lowest layer, NAS 757, RRC 755, PDCP 740, RLC 730, MAC 720, and PHY 710. In this example, upper layers 760 may be built on top of NAS 757, including an IP layer 761, SCTP 762, and an application layer signaling protocol (AP) 763.

[0172] In an NR specific implementation, the application protocol layer AP 763 can be an NG application protocol layer (NGAP or NG-AP) 763 for the NG interface 113 defined between the NG-RAN node 111 and the AMF 321, or the AP 763 can be an Xn application protocol layer (XnAP or Xn-AP) 763 for the Xn interface 112 defined between two or more RAN nodes 111.

[0173] The NG-AP 763 may support the functionality of the NG interface 113 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN point 111 and the AMF 321. The NG-AP 763 services may include two groups: UE-associated services (e.g., services related to the UE 101) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 111 and the AMF 321). These services may include functions including, but not limited to: a paging function for sending a paging request to the NG-RAN node 111 involved in a specific paging area; a UE context management function for allowing the AMF 321 to establish, modify and / or release the UE context in the AMF 321 and the NG-RAN node 111; a mobility function for the UE 101 in ECM-CONNECTED mode, for intra-system HO to support mobility within the NG-RAN, and for inter-system HO to support mobility from / to the EPS system; a NAS signalling transport function for transferring or rerouting NAS messages between the UE 101 and the AMF 321; a NAS node selection function for determining the association between the AMF 321 and the UE 101; an NG interface management function for setting up the NG interface and monitoring errors over the NG interface; a warning message sending function for providing a means to transfer a warning message via the NG interface or to cancel an ongoing warning message broadcast; a NAS signalling transport function for transferring or rerouting NAS messages between the UE 101 and the AMF 321; a NAS node selection function for determining the association between the AMF 321 and the UE 101; a ... 120 is a configuration transmission function for requesting and transmitting RAN configuration information (eg, SON information, performance measurement (PM) data, etc.) between two RAN nodes 111; and / or other similar functions.

[0174] The XnAP 763 may support the functionality of the Xn interface 112 and may include XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may include procedures for handling UE mobility within the NG RAN 111 (or E-UTRAN 210), such as handover preparation and cancellation procedures, SN status transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, and procedures related to dual connectivity. The XnAP global procedures may include procedures unrelated to a specific UE 101, such as Xn interface setup and reset procedures, NG-RAN update procedures, and cell activation procedures.

[0175] In an LTE implementation, the AP 763 may be an S1 application protocol layer (S1-AP) 763 for the S1 interface 113 defined between the E-UTRAN node 111 and the MME, or the AP 763 may be an X2 application protocol layer (X2AP or X2-AP) 763 for the X2 interface 112 defined between two or more E-UTRAN nodes 111.

[0176] The S1 application protocol layer (S1-AP) 763 may support the functionality of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include an S1-AP EP. The S1-AP EP may be the interaction unit between the E-UTRAN node 111 and the MME 221 within the LTE CN 120. S1-AP 763 services may include two groups: 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, RAN Information Management (RIM), and configuration transfer.

[0177] The X2AP 763 may support the functionality of the X2 interface 112 and may include X2AP basic mobility procedures and X2AP global procedures. The X2AP basic mobility procedures may include procedures for handling UE mobility within the E-UTRAN 120, such as handover preparation and cancellation procedures, SN status transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, and procedures related to dual connectivity. The X2AP global procedures may include procedures unrelated to a specific UE 101, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, and cell activation procedures.

[0178] The SCTP layer (alternatively referred to as the SCTP / IP layer) 762 can provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). SCTP 762 can ensure reliable delivery of signaling messages between the RAN node 111 and the AMF 321 / MME 221 based in part on the IP protocol supported by IP 761. The Internet Protocol layer (IP) 761 can be used to perform packet addressing and routing functions. In some implementations, the IP layer 761 can use point-to-point transport to deliver and transmit PDUs. In this regard, the RAN node 111 can include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.

[0179] In a second example, the user plane protocol stack may include, in order from highest layer to lowest layer, SDAP 747, PDCP 740, RLC 730, MAC 720, and PHY 710. The user plane protocol stack may be used for communication between UE 101, RAN node 111, and UPF 302 in an NR implementation, or between S-GW 222 and P-GW 223 in an LTE implementation. In this example, upper layers 751 may be built on top of SDAP 747 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 752, a general packet radio service (GPRS) tunneling protocol for the user plane layer (GTP-U) 753, and a user plane PDU layer (UP PDU) 763.

[0180] The transport network layer 754 (also known as the "transport layer") can be built on top of the IP transport, and the GTP-U 753 can be used on top of the UDP / IP layer 752 (including the UDP layer and the IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also known as the "Internet layer") can be used to perform packet addressing and routing functions. The IP layer can assign IP addresses to user data packets in any of the formats, such as IPv4, IPv6, or PPP.

[0181] GTP-U 753 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 any of the IPv4, IPv6, or PPP formats. UDP / IP 752 can provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication for selected data flows. The RAN node 111 and the S-GW 222 can exchange user plane data using the S1-U interface via a protocol stack including the L1 layer (e.g., PHY 710), the L2 layer (e.g., MAC 720, RLC 730, PDCP 740, and / or SDAP 747), the UDP / IP layer 752, and GTP-U 753. The S-GW 222 and the P-GW 223 can exchange user plane data using the S5 / S8a interface via a protocol stack including the L1 layer, the L2 layer, the UDP / IP layer 752, and GTP-U 753. As previously discussed, the NAS protocol may support mobility and session management procedures for UE 101 to establish and maintain an IP connection between UE 101 and P-GW 223 .

[0182] In addition, despite Figure 7Not shown, but an application layer may exist above the AP 763 and / or transport network layer 754. The application layer may be the layer where a user of the UE 101, RAN node 111, or other network element interacts with, for example, software applications executed by the application circuitry 405 or the application circuitry 505, respectively. The application layer may also provide one or more interfaces for the software applications to interact with the communication system of the UE 101 or RAN node 111, such as the baseband circuitry 610. In some implementations, the IP layer and / or the application layer may provide functionality that is the same as or similar to layers 5 through 7 of the Open Systems Interconnection (OSI) model, or portions thereof (e.g., OSI layer 7—application layer, OSI layer 6—presentation layer, and OSI layer 5—session layer).

[0183] Figure 8 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some exemplary implementations. Specifically, Figure 8 A schematic diagram of hardware resources 800 is shown, including one or more processors (or processor cores) 810, one or more memory / storage devices 820, and one or more communication resources 830, each of which can be communicatively coupled via a bus 840. For implementations in which node virtualization (e.g., NFV) is utilized, a hypervisor 802 can be executed to provide an execution environment for one or more network slices / subslices to utilize the hardware resources 800.

[0184] Processor 810 may include, for example, processor 812 and processor 814. Processor 810 may be, for example, 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 DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0185] The memory / storage device 820 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 820 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0186] The communication resources 830 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 804 or one or more databases 806 via the network 808. For example, the communication resources 830 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or Low power consumption) components, components and other communication components.

[0187] The instructions 850 may include software, a program, an application, an applet, an application, or other executable code for causing at least one of the processors 810 to perform any one or more of the methods discussed herein. The instructions 850 may reside entirely or partially within at least one of the processors 810 (e.g., within a cache memory of the processor), the memory / storage device 820, or any suitable combination thereof. In addition, any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the database 806. Thus, the memory of the processor 810, the memory / storage device 820, the peripheral devices 804, and the database 806 are examples of computer-readable media and machine-readable media.

[0188] In some specific implementations, Figures 1 to 8 An electronic device, network, system, chip or component or part thereof or a specific implementation thereof that performs one or more processes, techniques or methods described herein or parts thereof. Figure 9 A flow chart of a process 900 for scheduling shared channel transmissions in a cellular communication network is shown. For example, in some implementations, the process 900 is used to schedule PDSCH or PUSCH transmissions or both in a 5G NR network. In some implementations, the process 800 is performed by one or more of the UEs 101. In other implementations, the process 900 is performed by a UE 101. Figures 1 to 8 Other electronic devices disclosed herein are implemented.

[0189] The process 900 includes processing a signaling message (902). For example, one of the UEs 101 receives an RRC signaling message from one of the AN nodes 111 in the RAN 110 of the system 100, the signal including one or more DCI IEs. In some implementations, the UE 101a receives an RRC message signal from the RAN node 111a that is a gNB, the RRC message signal including one or more of a DCI format 0_0, 0_1, or 1_1 IE in a common search space or a UE-specific search space (USS) in the message.

[0190] Process 900 continues with the UE accessing the search space in the signaling message (904).For example, in some implementations, upon receiving the RRC signaling message from RAN node 111a, UE 101a checks whether the RRC signaling message includes a common search space or a USS or both.

[0191] Process 900 continues with the UE determining whether the fallback DCI is included in the search space (906). For example, in some implementations, UE 101a determines that one or both of the DCI format 0_0 IE or the DCI format 1_0 IE are included in the search space in the RRC signaling message, where the search space is the CSS or the USS. In some implementations, UE 101a detects that one or both of the DCI format 0_0 IE or the DCI format 1_0 IE are included in the USS but not in the CSS. In some implementations, the fallback DCI IE is included in the signaling message in addition to the DCI format 0_1 ​​IE or the DCI format 1_1 IE or both.

[0192] Process 900 continues with the UE determining whether the fallback DCI indicates an aggregation factor for shared channel communication within the multiple time slots (908). For example, in some implementations, UE 101a determines that the RRC signaling message includes a DCI format 1_0 IE that includes an aggregation factor for scheduling PDSCH reception within the multiple time slots from RAN node 111a. In some implementations, UE 101a determines that the RRC signaling message includes a DCI format 1_1 IE that includes an aggregation factor for scheduling PDSCH reception within the multiple time slots from RAN node 111a. In some implementations, UE 101a determines that the RRC signaling message includes a DCI format 0_0 IE that includes an aggregation factor for scheduling PUSCH transmission within the multiple time slots to RAN node 111a. In some implementations, the UE 101a determines that the RRC signaling message includes a DCI format 0_1 ​​IE that includes an aggregation factor for scheduling PUSCH transmissions in multiple time slots to the RAN node 111a.

[0193] Process 900 continues with the UE determining the UL / DL configuration for communication channel transmission (910). For example, in some implementations, UE 101a determines a TDD-UL-DL-ConfigurationCommon IE or a DD-UL-DL-ConfigDedicated IE corresponding to the UE. In some implementations, the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE is included in an RRC signaling message. In some implementations, the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE is determined from a different signaling message.

[0194] Process 900 continues with the UE scheduling aggregate transmissions within the plurality of time slots based on the aggregation factor and the UL / DL configuration (912). For example, in some implementations, UE 101a determines that the RRC signaling message includes a DCI format 1_0 IE or a DCI format 1_1 IE, the DCI format including an aggregation factor for scheduling PDSCH reception within the plurality of time slots from RAN node 111a. UE 101a uses the aggregation factor to determine that UE 101a is scheduled to receive PDSCH data from RAN node 111a within the plurality of time slots in the communication channel. UE 101a also uses one of a TDD-UL-DL-ConfigurationCommon IE or a TDD-UL-DL-ConfigDedicated IE to determine that at least one symbol of a group of symbols from a particular time slot in the plurality of time slots is an uplink symbol. In response to determining that UE 101a is scheduled to receive PDSCH data in a plurality of time slots and at least one symbol of a particular time slot is an uplink symbol, UE 101a is scheduled not to receive PDSCH data in the particular time slot.

[0195] In some implementations, UE 101a determines that the RRC signaling message includes a DCI format 0_0 IE or a DCI format 0_1 ​​IE, the DCI format including an aggregation factor for scheduling PUSCH transmissions within a plurality of time slots to RAN node 111a. UE 101a uses the aggregation factor to determine that UE 101a is scheduled to transmit PUSCH data within a plurality of time slots to RAN node 111a in a communication channel. UE 101a also uses one of a TDD-UL-DL-ConfigurationCommon IE or a TDD-UL-DL-ConfigDedicated IE to determine that at least one symbol from a group of symbols for a particular time slot in the plurality of time slots is a downlink symbol. In response to determining that UE 101a is scheduled to transmit PUSCH data within the plurality of time slots and that at least one symbol of the particular time slot is a downlink symbol, UE 101a is scheduled not to transmit PUSCH data in the particular time slot.

[0196] In some implementations, UE 101a detects a DCI format 1_0 IE in a USS in an RRC signaling message and determines that an aggregation factor is indicated in the DCI format 1_0 IE or the DCI format 1_1 IE. UE 101a uses the aggregation factor to determine that UE 101a is scheduled to receive PDSCH data from RAN node 111a in a plurality of time slots in the communication channel. UE 101a also uses one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE to determine that at least one symbol from a set of symbols for a particular time slot in the plurality of time slots is an uplink symbol. In response to determining that UE 101a is scheduled to receive PDSCH data in the plurality of time slots and that at least one symbol of the particular time slot is an uplink symbol, UE 101a is scheduled not to receive PDSCH data in the particular time slot.

[0197] In some implementations, UE 101a detects a DCI format 1_0 IE in a USS in an RRC signaling message and determines that an aggregation factor is indicated in a DCI format 0_0 IE or a DCI format 0_1 ​​IE. UE 101a uses the aggregation factor to determine that UE 101a is scheduled to transmit PUSCH data in a plurality of time slots to RAN node 111a in a communication channel. UE 101a also uses one of a TDD-UL-DL-ConfigurationCommon IE or a TDD-UL-DL-ConfigDedicated IE to determine that at least one symbol from a set of symbols in a particular time slot in the plurality of time slots is a downlink symbol. In response to determining that UE 101a is scheduled to transmit PUSCH data in the plurality of time slots and that at least one symbol of the particular time slot is a downlink symbol, UE 101a is scheduled not to transmit PUSCH data in the particular time slot.

[0198] In some implementations, UE 101a detects a DCI format 1_0 IE in a USS in an RRC signaling message and determines that UE 101a is configured with a pdsch-AggregationFactor. Upon determination, UE 101a applies the same symbol allocation across multiple consecutive time slots corresponding to the pdsch-AggregationFactor. The UE receives one of: (i) PDSCH data scheduled by a PDCCH that includes one of the DCI format 1_1 IE or the DCI format 1_0 IE detected in the USS and a CRC scrambled by at least one of the C-RNTI, MCS C-RNTI, or CS-RNTI, or (ii) PDSCH data scheduled using sps-Config without a corresponding PDCCH transmission. The PDSCH is limited to a single transport layer. UE 101a expects TBs to be repeated within each symbol allocation in each time slot in consecutive time slots.

[0199] In some implementations, UE 101a detects a DCI format 0_0 IE in a USS in an RRC signaling message and determines that UE 101a is configured with a pusch-AggregationFactor. Upon determining this, UE 101a applies the same symbol allocation across multiple consecutive time slots corresponding to the pusch-AggregationFactor and configures the PUSCH in a single transport layer. UE 101a transmits PUSCH data scheduled by a PDCCH that includes one of the DCI format 0_1 ​​IE or the DCI format 0_0 IE detected in the USS and a CRC scrambled with at least one of a C-RNTI or an MCS C-RNTI. In some cases, UE 101a repeats the TB across consecutive time slots, thereby applying the same symbol allocation in each of the consecutive time slots.

[0200] In some implementations, the fallback DCI in the RRC signaling message (e.g., one of the DCI format 0_0 IE or the DCI format 1_0 IE) is not configured to indicate an aggregation factor. In some of these implementations, the UE 101a determines that the UE 101a is configured with a pdsch-AggregationFactor. Upon determination, the UE 101a applies the same symbol allocation across multiple consecutive time slots corresponding to the pdsch-AggregationFactor. The UE receives one of the following: (i) PDSCH data scheduled by a DCI format_1_IE in a PDCCH, the PDCCH including a CRC scrambled by at least one of a C-RNTI, an MCS C-RNTI, or a CS-RNTI, or (ii) PDSCH data scheduled using sps-Config without a corresponding PDCCH transmission. The PDSCH is limited to a single transport layer. In some cases, the UE 101a expects a TB to be repeated within each symbol allocation in each time slot in consecutive time slots. In some of these implementations, UE 101a determines that UE 101a is configured with a pusch-AggregationFactor. Upon determining, UE 101a applies the same symbol allocation across multiple consecutive time slots corresponding to the pusch-AggregationFactor and configures the PUSCH in a single transmission layer. UE 101a transmits PUSCH data scheduled by a DCI format 0_1 ​​IE in a PDCCH that includes a CRC scrambled with at least one of a C-RNTI or an MCS C-RNTI. In some cases, UE 101a repeats the TB across consecutive time slots, thereby applying the same symbol allocation in each of the consecutive time slots.

[0201] For one or more specific implementations, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the following embodiments. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate in accordance with one or more of the embodiments described below. For another example, circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate in accordance with one or more of the embodiments described below in the embodiments section.

[0202] For one or more specific implementations, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the following embodiments. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate in accordance with one or more of the embodiments described below. For another example, circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate in accordance with one or more of the embodiments described below in the embodiments section.

[0203] It should be noted that although process steps, method steps, algorithms or the like may be described in the order described above, such processes, methods and algorithms may typically be configured to work in alternative orders unless specifically stated to the contrary.

[0204] The disclosed examples and other examples may be implemented as one or more computer program products, such as one or more modules of computer program instructions encoded on a computer-readable medium, for execution by a data processing apparatus or for controlling the operation of the data processing apparatus. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, or a combination of one or more of these. The term "data processing apparatus" encompasses all apparatuses, devices, and machines for processing data, including, for example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the apparatus may also include code that creates an execution environment for the computer program under consideration, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of these.

[0205] A system may encompass all devices, apparatuses, and machines for processing data, including, for example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the system may also include code that creates an execution environment for the computer program in question, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of these.

[0206] A computer program (also referred to as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, subroutines, or code portions). A computer program may be deployed to execute on one computer or on multiple computers located at the same site or distributed across multiple sites and interconnected by a communications network.

[0207] The processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform the functions described herein. The processes and logic flows can also be performed by, and apparatus can be implemented as, special purpose logic circuitry, such as an FPGA or ASIC (application-specific integrated circuit).

[0208] Processors suitable for executing a computer program include, for example, both general-purpose and special-purpose microprocessors, and any one or more processors of any kind of digital computer. Computer-readable media suitable for storing computer program instructions and data may include all forms of nonvolatile memory, media, and storage devices. The processor and memory may be supplemented by, or incorporated in, special-purpose logic circuitry.

[0209] Example

[0210] Embodiment 1 may include a method for performing physical shared channel scheduling in multiple time slots by using fallback DCI, the method comprising:

[0211] Procedure for receiving fallback DCI for transmitting / receiving a shared channel in multiple time slots; procedure for applying an aggregation factor; procedure for handling conflicts with the UL-DL direction when scheduling a shared channel in multiple time slots.

[0212] Embodiment 2 may include the method of embodiment 1 or some other embodiment herein, wherein fallback DCI formats 0_0 and 1_0 may schedule a shared channel within multiple time slots.

[0213] Embodiment 3 may include a method according to embodiment 2 or some other embodiment herein, wherein if a UE is scheduled to receive PDSCH in a plurality of time slots via DCI format 1_0 or 1_1, and if TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated indicates that, for a time slot from the plurality of time slots, at least one symbol from a set of symbols is an uplink symbol, wherein the UE is scheduled for PDSCH reception in the time slot, then the UE does not receive PDSCH in the time slot.

[0214] Embodiment 4 may include a method according to embodiment 2 or some other embodiment herein, wherein if a UE is scheduled to transmit PUSCH in a plurality of time slots via DCI format 0_0 or 0_1, and if TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated indicates that, for a time slot from the plurality of time slots, at least one symbol from a set of symbols is a downlink symbol, wherein the UE is scheduled for PUSCH transmission in the time slot, then the UE does not transmit PUSCH in the time slot.

[0215] Embodiment 5 may include the method of embodiment 1 or some other embodiment herein, wherein fallback DCI formats 0_0 and 1_0 detected in the UE-specific search space may schedule a shared channel within multiple time slots.

[0216] Embodiment 6 may include a method according to embodiment 5 or some other embodiment herein, wherein if a UE is scheduled to receive PDSCH in a plurality of time slots by DCI format 1_1 or DCI format 1_0 detected in the USS search space, and if TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated indicates that, for a time slot from the plurality of time slots, at least one symbol from a set of symbols is an uplink symbol, wherein the UE is scheduled for PDSCH reception in the time slot, then the UE does not receive PDSCH in the time slot.

[0217] Embodiment 7 may include a method according to embodiment 5 or some other embodiment herein, wherein if a UE is scheduled to transmit PUSCH in a plurality of time slots by DCI format 0_1 ​​or DCI format 0_0 detected in a USS, and if TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated indicates that, for a time slot from the plurality of time slots, at least one symbol from a set of symbols is a downlink symbol, wherein the UE is scheduled for PUSCH transmission in the time slot, then the UE does not transmit PUSCH in the time slot.

[0218] Embodiment 8 may include a method according to embodiment 5 or some other embodiment herein, wherein when receiving a PDSCH scheduled by a PDCCH carrying DCI format 1_1 or DCI format 1_0 detected in the USS and a CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, or a PDSCH scheduled using sps-Config without a corresponding PDCCH transmission, if the UE is configured with a pdsch-AggregationFactor, the same symbol allocation is applied across these pdsch-AggregationFactor consecutive time slots.

[0219] Embodiment 9 may include a method according to embodiment 5 or some other embodiment herein, wherein when transmitting a PUSCH scheduled by a PDCCH carrying DCI format 0_1 ​​or DCI format 0_0 detected in the USS and a CRC scrambled by C-RNTI, MCS-C-RNTI, if the UE is configured with pusch-AggregationFactor, the same symbol allocation is applied across these pusch-AggregationFactor consecutive time slots, and the PUSCH is limited to a single transport layer.

[0220] Embodiment 10 may include the method of embodiment 1 or some other embodiment herein, wherein fallback DCI formats 0_0 and 1_0 may not schedule the shared channel within multiple time slots.

[0221] Embodiment 11 may include a method according to embodiment 10 or some other embodiment herein, wherein when receiving a PDSCH scheduled by DCI format 1_1 in a PDCCH with a CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, or a PDSCH scheduled without a corresponding PDCCH transmission using sps-Config, if the UE is configured with a pdsch-AggregationFactor, the same symbol allocation is applied across these pdsch-AggregationFactor consecutive time slots.

[0222] Embodiment 12 may include a method according to embodiment 10 or some other embodiment herein, wherein when transmitting a PUSCH scheduled by DCI format 0_1 ​​in a PDCCH with a CRC scrambled by C-RNTI, MCS-C-RNTI, if the UE is configured with pusch-AggregationFactor, the same symbol allocation is applied across these pusch-AggregationFactor consecutive time slots, and the PUSCH is limited to a single transport layer.

[0223] Embodiment 13 may include a method comprising: processing control information having DCI format 0_0 or 1_0; and determining to schedule shared channel transmission within a plurality of time slots based on the control information.

[0224] Embodiment 14 may include a method according to embodiment 13 or some other embodiment herein, wherein the shared channel transmission is a PDCCH transmission or a PDSCH transmission.

[0225] Embodiment 15 may include a method as described in embodiment 13 or some other embodiment herein, wherein the shared channel transmission is in an aggregate transmission.

[0226] Embodiment 16 may include the method according to embodiment 15 or some other embodiment herein, further comprising: detecting the control information in a UE-specific search space.

[0227] Embodiment Z01 may comprise an apparatus comprising means for performing one or more elements of the method described in or related to any of Embodiments 1-16, or any other method or process described herein.

[0228] Embodiment Z02 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any one of Embodiments 1 to 16 or any other method or process described herein.

[0229] Embodiment Z03 may comprise an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in accordance with or related to any of Embodiments 1 to 16, or any other method or process described herein.

[0230] Embodiment Z04 may include a method, technique, or process as described or related to any one of Embodiments 1 to 16, or a portion or component thereof.

[0231] Embodiment Z05 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any one of Embodiments 1 to 16, or a portion thereof.

[0232] Embodiment Z06 may include a signal as described or related to any one of embodiments 1 to 16, or a portion or component thereof.

[0233] Embodiment Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU) or message as described or related to any one of embodiments 1 to 16, or a part or component thereof, or otherwise described in this disclosure.

[0234] Embodiment Z08 may include a signal encoded with data as described or associated with any one of Embodiments 1 to 16, or a portion or component thereof, or as otherwise described in this disclosure.

[0235] Embodiment Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU) or message as described or associated with any of embodiments 1 to 16, or a portion or component thereof, or otherwise described in this disclosure.

[0236] Embodiment Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform the methods, techniques, or processes described in or related to any one of embodiments 1 to 16, or portions thereof.

[0237] Embodiment Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of embodiments 1 to 16, or a portion thereof.

[0238] Embodiment Z12 may include signals in a wireless network as shown and described herein.

[0239] Embodiment Z13 may include a method of communicating in a wireless network as shown and described herein.

[0240] Embodiment Z14 may include a system for providing wireless communications as shown and described herein.

[0241] Embodiment Z15 may include an apparatus for providing wireless communications as shown and described herein.

[0242] Unless expressly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the specific implementations to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various specific implementations.

[0243] Although this document may describe many details, these details should not be understood as limitations on the scope of the claimed invention or the scope of the claims, but rather as descriptions of features specific to particular embodiments. Certain features described in this document in the context of different implementations may also be implemented in combination in a single implementation. On the contrary, the various features described in the context of a single implementation may also be implemented in multiple implementations individually or in the form of any suitable sub-combination. In addition, although certain features may be described above as working in certain combinations and even initially claimed in this way, one or more features of the claimed combination may be removed from the combination in some cases, and the claimed combination may involve a sub-combination or a variation of the sub-combination. Similarly, although operations are shown in a particular order in the accompanying drawings, this should not be understood as requiring such operations to be performed in a sequential order or in the particular order shown, or requiring all shown operations to be performed to achieve the desired result.

[0244] Only a few examples and implementations are disclosed. Variations, modifications, and enhancements to the examples and implementations, as well as other implementations, may be made based on what is disclosed.

[0245] the term

[0246] For the purposes of this document, the following terms and definitions apply to the examples and implementations discussed herein.

[0247] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or memory (shared, dedicated, or group) configured to provide the described functionality, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a digital signal processor (DSP), etc. In some implementations, the circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these implementations, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0248] As used herein, the term "processor circuitry" means, is part of, or includes circuitry that is capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and / or transmitting digital data. The term "processor circuitry" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes). The terms "application circuitry" and / or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as "processor circuitry."

[0249] As used herein, the term "interface circuitry" refers to circuitry that enables, is part of, or includes information exchange between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and the like.

[0250] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can represent a remote user of network resources in a communication network. Furthermore, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0251] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as networked computers, networking hardware, network equipment, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN equipment, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, and the like.

[0252] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to one another and configured to share computing and / or networking resources.

[0253] As used herein, the terms "appliance," "computer appliance," and the like refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

[0254] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time and / or processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database, and application, workload units, etc. "Hardware resources" may refer to the computing, storage, and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to the computing, storage, and / or network resources provided by a virtualization infrastructure to applications, devices, systems, etc. The terms "network resources" or "communication resources" may refer to resources accessible to a computer device / system via a communication network. The term "system resources" may refer to any type of shared entity that provides a service and may include computing resources and / or network resources. System resources may be considered a set of coherent functions, network data objects, or services accessible through a server, where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0255] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar terms indicating a path or medium through which data is transmitted. In addition, the term "link" as used herein refers to a connection between two devices over a RAT for transmitting and receiving information.

[0256] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0257] The terms "coupled," "communicatively coupled," and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by means of communication, including through wires or other interconnections, through wireless communication channels or links, etc.

[0258] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents.

[0259] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0260] The term "SSB" refers to SS / PBCH block.

[0261] The term "primary cell" refers to an MCG cell operating on a primary frequency, where the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0262] The term "primary SCG cell" refers to an SCG cell in which a UE performs random access when reconfiguration is performed using a synchronization procedure for DC operation.

[0263] The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured with CA.

[0264] The term "secondary cell group" refers to a subset of serving cells including a PSCell and zero or more secondary cells for a UE configured with DC.

[0265] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED without CA / DC configured, where there is only one serving cell including the primary cell.

[0266] The term "serving cell" refers to a cell group including a special cell for a UE configured with CA and in RRC_CONNECTED and all secondary cells.

[0267] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG for dual connectivity operation; otherwise, the term "special cell" refers to the Pcell.

Claims

1. A method for communication, the method comprising: receiving a radio resource control (RRC) signaling message from a base station at a user equipment (UE) in a cellular communication network; Accessing, by the UE, a search space in the RRC signaling message; identifying, by the UE, a fallback downlink control information (DCI) information element (IE) included in the search space; determining, by the UE, whether an aggregation factor is indicated in the fallback DCI IE, the aggregation factor being used for shared channel communication with the base station in a plurality of time slots in a communication channel; determining, by the UE, an uplink / downlink (UL / DL) configuration for transmission on the communication channel; as well as Aggregate transmission within a plurality of time slots in the communication channel is determined by the UE based on the aggregation factor and the uplink / downlink configuration.

2. The method of claim 1 , wherein accessing the search space comprises: One of a common search space (CSS) or a UE-specific search space (USS) in the RRC signaling message is accessed. 3 . The method of claim 1 , wherein identifying the fallback DCI IE included in the search space comprises identifying one of a DCI format 0_0 IE or a DCI format 1_0 IE included in the search space.

4. The method of claim 1 , wherein determining the uplink / downlink configuration for transmission on the communication channel comprises determining one of a TDD-UL-DL-ConfigurationCommon IE or a TDD-UL-DL-ConfigDedicated IE included in the RRC signaling message.

5. The method of claim 4 , wherein the fallback DCI IE comprises a DCI format 1_0 IE and the aggregation factor is indicated in one of the DCI format 1_0 IE or the DCI format 1_1 IE, and wherein determining the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to receive physical downlink shared channel (PDSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol from a set of symbols of a particular time slot from the plurality of time slots is an uplink symbol; and In response to determining that the UE is scheduled to receive PDSCH data within the plurality of time slots and at least one symbol of the specific time slot is an uplink symbol, the UE is scheduled not to receive PDSCH in the specific time slot.

6. The method of claim 4 , wherein the fallback DCI IE comprises a DCI format 0_0 IE and the aggregation factor is indicated in one of the DCI format 0_0 IE or a DCI format 0_1 ​​IE, and wherein determining the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to transmit physical uplink shared channel (PUSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol in a set of symbols from a particular time slot of the plurality of time slots is a downlink symbol; and In response to determining that the UE is scheduled to transmit PUSCH data within the plurality of time slots and at least one symbol of the particular time slot is a downlink symbol, the UE is scheduled not to transmit PUSCH data in the particular time slot.

7. The method of claim 4 , wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 1_0 IE detected in a USS, and indicating the aggregation factor in one of the DCI format 1_0 IE or the DCI format 1_1 IE, and wherein scheduling the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to receive physical downlink shared channel (PDSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol from a set of symbols of a particular time slot from the plurality of time slots is an uplink symbol; and In response to determining that the UE is scheduled to receive PDSCH data within the plurality of time slots and at least one symbol of the specific time slot is an uplink symbol, the UE is scheduled not to receive PDSCH in the specific time slot.

8. The method of claim 4 , wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 0_0 IE detected in a USS, and indicating the aggregation factor in one of the DCI format 0_0 IE or a DCI format 0_1 ​​IE, and wherein determining the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to transmit physical uplink shared channel (PUSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol in a set of symbols from a particular time slot of the plurality of time slots is a downlink symbol; and In response to determining that the UE is scheduled to transmit PUSCH data within the plurality of time slots and at least one symbol of the particular time slot is a downlink symbol, the UE is scheduled not to transmit PUSCH data in the particular time slot.

9. The method of claim 1 , wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 1_0 IE detected in a USS, the method further comprising: Determining that the UE is configured with a pdsch-AggregationFactor; In response to the determining, applying the same symbol allocation across a plurality of consecutive time slots corresponding to the pdsch-AggregationFactor; and Receive one of the following: (i) PDSCH data scheduled by a physical downlink control channel (PDCCH), wherein the PDCCH includes one of a DCI format 1_1IE or a DCI format 1_0IE detected in the USS, and a cyclic redundancy check (CRC) scrambled by at least one of a cell radio network temporary identifier (C-RNTI), a modulation and coding scheme C-RNTI (MCS C-RNTI), or a configured scheduling RNTI (CS-RNTI); or (ii) PDSCH data scheduled using sps-Config without a corresponding PDCCH transmission.

10. The method of claim 9, wherein a transport block (TB) is repeated within each symbol allocation in each of the consecutive slots, and wherein the PDSCH is limited to a single transmission layer.

11. The method of claim 1 , wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 0_0 IE detected in a USS, the method further comprising: Determining that the UE is configured with a pusch-AggregationFactor; In response to the determination, applying the same symbol allocation across a plurality of consecutive time slots corresponding to the pusch-AggregationFactor and configuring the PUSCH to a single transmission layer; as well as PUSCH data scheduled by a PDCCH including one of a DCI format 0_1 ​​IE or a DCI format 0_0 IE detected in a USS and a CRC scrambled with at least one of a C-RNTI or an MCS-C-RNTI is transmitted.

12. The method of claim 11, wherein transmitting the PUSCH data comprises: Repeating TB is applying the same symbol allocation in each of the consecutive time slots across the consecutive time slots.

13. The method of claim 1 , wherein the fallback DCI IE is not configured to indicate an aggregation factor, the method further comprising: Determining that the UE is configured with a pdsch-AggregationFactor; In response to the determining, applying a same symbol allocation across a plurality of consecutive time slots of the plurality of time slots corresponding to the pdsch-AggregationFactor; and Receive one of the following: (i) PDSCH data scheduled by DCI format 1_1IE in PDCCH, wherein the PDCCH includes a CRC scrambled by at least one of C-RNTI, MCS C-RNTI or CS-RNTI, or (ii) PDSCH data scheduled using sps-Config without corresponding PDCCH transmission.

14. The method of claim 13, wherein a transport block (TB) is repeated within each symbol allocation in each of the consecutive time slots, and wherein the PDSCH is limited to a single transmission layer.

15. The method of claim 1 , wherein the fallback DCI IE is not configured to indicate an aggregation factor, the method further comprising: Determining that the UE is configured with a pusch-AggregationFactor; In response to the determining, applying the same symbol allocation across a plurality of consecutive time slots corresponding to the pusch-AggregationFactor among the plurality of time slots, and configuring the PUSCH to a single transmission layer; as well as PUSCH data scheduled by a DCI format 0_1 ​​IE in a PDCCH including a CRC scrambled with at least one of a C-RNTI or an MCS-C-RNTI is transmitted.

16. The method of claim 1, wherein the shared channel communication with the base station comprises communication using one of a PDSCH or a PUSCH.

17. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, are configured to cause the one or more processors to perform operations comprising: receiving a radio resource control (RRC) signaling message from a base station at a user equipment (UE) in a cellular communication network; Accessing, by the UE, a search space in the RRC signaling message; identifying, by the UE, a fallback downlink control information (DCI) information element (IE) included in the search space; determining, by the UE, whether an aggregation factor is indicated in the fallback DCI IE, the aggregation factor being used for shared channel communication with the base station in a plurality of time slots in a communication channel; determining, by the UE, an uplink / downlink (UL / DL) configuration for transmission on the communication channel; as well as Aggregate transmission within a plurality of time slots in the communication channel is determined by the UE based on the aggregation factor and the uplink / downlink configuration.

18. The one or more non-transitory computer-readable media of claim 17, wherein accessing the search space comprises accessing one of a common search space (CSS) or a UE-specific search space (USS) in the RRC signaling message.

19. The one or more non-transitory computer-readable media of claim 17, wherein identifying the fallback DCI IE included in the search space comprises identifying one of a DCI format 0_0 IE or a DCI format 1_0 IE included in the search space.

20. The one or more non-transitory computer-readable media of claim 17, wherein determining the uplink / downlink configuration for transmission on the communication channel comprises determining one of a TDD-UL-DL-ConfigurationCommon IE or a TDD-UL-DL-ConfigDedicated IE included in the RRC signaling message.

21. The one or more non-transitory computer-readable media of claim 20, wherein the fallback DCI IE comprises a DCI format 1_0 IE, and the aggregation factor is indicated in one of the DCI format 1_0 IE or the DCI format 1_1 IE, and wherein determining the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to receive physical downlink shared channel (PDSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol from a set of symbols of a particular time slot from the plurality of time slots is an uplink symbol; and In response to determining that the UE is scheduled to receive PDSCH data within the plurality of time slots and at least one symbol of the specific time slot is an uplink symbol, the UE is scheduled not to receive PDSCH in the specific time slot.

22. The one or more non-transitory computer-readable media of claim 20, wherein the fallback DCI IE comprises a DCI format 0_0 IE, and the aggregation factor is indicated in one of the DCI format 0_0 IE or a DCI format 0_1 ​​IE, and wherein determining the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to transmit physical uplink shared channel (PUSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol in a set of symbols from a particular time slot of the plurality of time slots is a downlink symbol; and In response to determining that the UE is scheduled to transmit PUSCH data within the plurality of time slots and at least one symbol of the particular time slot is a downlink symbol, the UE is scheduled not to transmit PUSCH data in the particular time slot.

23. The one or more non-transitory computer-readable media of claim 20, wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 1_0 IE detected in a USS and indicating the aggregation factor in one of the DCI format 1_0 IE or the DCI format 1_1 IE, and wherein determining the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to receive physical downlink shared channel (PDSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol from a set of symbols of a particular time slot from the plurality of time slots is an uplink symbol; and In response to determining that the UE is scheduled to receive PDSCH data within the plurality of time slots and at least one symbol of the specific time slot is an uplink symbol, the UE is scheduled not to receive PDSCH in the specific time slot.

24. The one or more non-transitory computer-readable media of claim 20, wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 0_0 IE detected in a USS and indicating the aggregation factor in one of the DCI format 0_0 IE or a DCI format 0_1 ​​IE, and wherein determining the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to transmit physical uplink shared channel (PUSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol in a set of symbols from a particular time slot of the plurality of time slots is a downlink symbol; and In response to determining that the UE is scheduled to transmit PUSCH data within the plurality of time slots and at least one symbol of the particular time slot is a downlink symbol, the UE is scheduled not to transmit PUSCH data in the particular time slot.

25. The one or more non-transitory computer-readable media of claim 17, wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 1_0 IE detected in a USS, the operations further comprising: Determining that the UE is configured with a pdsch-AggregationFactor; In response to the determining, applying the same symbol allocation across a plurality of consecutive time slots corresponding to the pdsch-AggregationFactor; and Receive one of the following: (i) PDSCH data scheduled by a physical downlink control channel (PDCCH), wherein the PDCCH includes one of a DCI format 1_1IE or a DCI format 1_0IE detected in the USS, and a cyclic redundancy check (CRC) scrambled by at least one of a cell radio network temporary identifier (C-RNTI), a modulation and coding scheme C-RNTI (MCS C-RNTI), or a configured scheduling RNTI (CS-RNTI); or (ii) PDSCH data scheduled using sps-Config without a corresponding PDCCH transmission.

26. The one or more non-transitory computer-readable media of claim 25, wherein a transport block (TB) is repeated within each symbol allocation in each of the consecutive time slots, and wherein the PDSCH is limited to a single transport layer.

27. The one or more non-transitory computer-readable media of claim 17, wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 0_0 IE detected in a USS, the operations further comprising: Determining that the UE is configured with a pusch-AggregationFactor; In response to the determination, applying the same symbol allocation across a plurality of consecutive time slots corresponding to the pusch-AggregationFactor and configuring the PUSCH to a single transmission layer; as well as PUSCH data scheduled by a PDCCH including one of a DCI format 0_1 ​​IE or a DCI format 0_0 IE detected in a USS and a CRC scrambled with at least one of a C-RNTI or an MCS-C-RNTI is transmitted.

28. The one or more non-transitory computer-readable media of claim 27, wherein transmitting the PUSCH data comprises: Repeating TB is applying the same symbol allocation in each of the consecutive time slots across the consecutive time slots.

29. The one or more non-transitory computer-readable media of claim 17, wherein the fallback DCI IE is not configured to indicate an aggregation factor, the operations further comprising: Determining that the UE is configured with a pdsch-AggregationFactor; In response to the determining, applying a same symbol allocation across a plurality of consecutive time slots of the plurality of time slots corresponding to the pdsch-AggregationFactor; and Receive one of the following: (i) PDSCH data scheduled by DCI format 1_1IE in PDCCH, wherein the PDCCH includes a CRC scrambled by at least one of C-RNTI, MCS C-RNTI or CS-RNTI, or (ii) PDSCH data scheduled using sps-Config without corresponding PDCCH transmission.

30. The one or more non-transitory computer-readable media of claim 29, wherein a transport block (TB) is repeated within each symbol allocation in each of the consecutive time slots, and wherein the PDSCH is limited to a single transport layer.

31. The one or more non-transitory computer-readable media of claim 17, wherein the fallback DCI IE is not configured to indicate an aggregation factor, the operations further comprising: Determining that the UE is configured with a pusch-AggregationFactor; In response to the determining, applying the same symbol allocation across a plurality of consecutive time slots corresponding to the pusch-AggregationFactor among the plurality of time slots, and configuring the PUSCH to a single transmission layer; as well as PUSCH data scheduled by a DCI format 0_1 ​​IE in a PDCCH including a CRC scrambled with at least one of a C-RNTI or an MCS-C-RNTI is transmitted.

32. The one or more non-transitory computer-readable media of claim 17, wherein the shared channel communication with the base station comprises communication using one of a PDSCH or a PUSCH.

33. An apparatus for communication, the apparatus comprising: one or more processors; as well as One or more computer-readable media storing instructions that, when executed by the one or more processors, are configured to cause the one or more processors to perform operations including: receiving a radio resource control (RRC) signaling message from a base station at a user equipment (UE) in a cellular communication network; Accessing, by the UE, a search space in the RRC signaling message; identifying, by the UE, a fallback downlink control information (DCI) information element (IE) included in the search space; determining, by the UE, whether an aggregation factor is indicated in the fallback DCI IE, the aggregation factor being used for shared channel communication with the base station in a plurality of time slots in a communication channel; determining, by the UE, an uplink / downlink (UL / DL) configuration for transmission on the communication channel; as well as Aggregate transmission within a plurality of time slots in the communication channel is determined by the UE based on the aggregation factor and the uplink / downlink configuration.

34. The apparatus of claim 33, wherein accessing the search space comprises accessing one of a common search space (CSS) or a UE-specific search space (USS) in the RRC signaling message.

35. The apparatus of claim 33, wherein identifying the fallback DCI IE included in the search space comprises identifying one of a DCI format 0_0 IE or a DCI format 1_0 IE included in the search space.

36. The apparatus of claim 33, wherein determining the uplink / downlink configuration for transmission on the communication channel comprises determining one of a TDD-UL-DL-ConfigurationCommon IE or a TDD-UL-DL-ConfigDedicated IE included in the RRC signaling message.

37. The apparatus of claim 36, wherein the fallback DCI IE comprises a DCI format 1_0 IE, and the aggregation factor is indicated in one of the DCI format 1_0 IE or the DCI format 1_1 IE, and wherein determining the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to receive physical downlink shared channel (PDSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol from a set of symbols of a particular time slot from the plurality of time slots is an uplink symbol; and In response to determining that the UE is scheduled to receive PDSCH data within the plurality of time slots and at least one symbol of the specific time slot is an uplink symbol, the UE is scheduled not to receive PDSCH in the specific time slot.

38. The apparatus of claim 36, wherein the fallback DCI IE comprises a DCI format 0_0 IE, and the aggregation factor is indicated in one of the DCI format 0_0 IE or a DCI format 0_1 ​​IE, and wherein determining the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to transmit physical uplink shared channel (PUSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol in a set of symbols from a particular time slot of the plurality of time slots is a downlink symbol; and In response to determining that the UE is scheduled to transmit PUSCH data within the plurality of time slots and at least one symbol of the particular time slot is a downlink symbol, the UE is scheduled not to transmit PUSCH data in the particular time slot.

39. The apparatus of claim 36 , wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 1_0 IE detected in a USS, and indicating the aggregation factor in one of the DCI format 1_0 IE or the DCI format 1_1 IE, and wherein determining the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to receive physical downlink shared channel (PDSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol from a set of symbols of a particular time slot from the plurality of time slots is an uplink symbol; and In response to determining that the UE is scheduled to receive PDSCH data within the plurality of time slots and at least one symbol of the specific time slot is an uplink symbol, the UE is scheduled not to receive PDSCH in the specific time slot.

40. The apparatus of claim 36, wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 0_0 IE detected in a USS and indicating the aggregation factor in one of the DCI format 0_0 IE or a DCI format 0_1 ​​IE, and wherein determining the aggregate transmission comprises: determining, using the aggregation factor, that the UE is scheduled to transmit physical uplink shared channel (PUSCH) data within the plurality of time slots in the communication channel; determining, using one of the TDD-UL-DL-ConfigurationCommon IE or the TDD-UL-DL-ConfigDedicated IE, that at least one symbol in a set of symbols from a particular time slot of the plurality of time slots is a downlink symbol; and In response to determining that the UE is scheduled to transmit PUSCH data within the plurality of time slots and at least one symbol of the particular time slot is a downlink symbol, the UE is scheduled not to transmit PUSCH data in the particular time slot.

41. The apparatus of claim 33, wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 1_0 IE detected in a USS, the operations further comprising: Determining that the UE is configured with a pdsch-AggregationFactor; In response to the determining, applying the same symbol allocation across a plurality of consecutive time slots corresponding to the pdsch-AggregationFactor; and Receive one of the following: (i) PDSCH data scheduled by a physical downlink control channel (PDCCH), wherein the PDCCH includes one of a DCI format 1_1IE or a DCI format 1_0IE detected in the USS, and a cyclic redundancy check (CRC) scrambled by at least one of a cell radio network temporary identifier (C-RNTI), a modulation and coding scheme C-RNTI (MCS C-RNTI), or a configured scheduling RNTI (CS-RNTI); or (ii) PDSCH data scheduled using sps-Config without a corresponding PDCCH transmission.

42. The apparatus of claim 41, wherein a transport block (TB) is repeated within each symbol allocation in each of the consecutive slots, and wherein the PDSCH is restricted to a single transmission layer.

43. The apparatus of claim 33, wherein identifying the fallback DCI IE included in the search space comprises identifying a DCI format 0_0 IE detected in a USS, the operations further comprising: Determining that the UE is configured with a pusch-AggregationFactor; In response to the determination, applying the same symbol allocation across a plurality of consecutive time slots corresponding to the pusch-AggregationFactor and configuring the PUSCH to a single transmission layer; as well as PUSCH data scheduled by a PDCCH including one of a DCI format 0_1 ​​IE or a DCI format 0_0 IE detected in a USS and a CRC scrambled with at least one of a C-RNTI or an MCS-C-RNTI is transmitted.

44. The apparatus of claim 43, wherein transmitting the PUSCH data comprises: Repeating TB is applying the same symbol allocation in each of the consecutive time slots across the consecutive time slots.

45. The apparatus of claim 33, wherein the fallback DCI IE is not configured to indicate an aggregation factor, the operations further comprising: Determining that the UE is configured with a pdsch-AggregationFactor; In response to the determining, applying a same symbol allocation across a plurality of consecutive time slots of the plurality of time slots corresponding to the pdsch-AggregationFactor; and Receive one of the following: (i) PDSCH data scheduled by DCI format 1_1IE in PDCCH, wherein the PDCCH includes a CRC scrambled by at least one of C-RNTI, MCS C-RNTI or CS-RNTI, or (ii) PDSCH data scheduled using sps-Config without corresponding PDCCH transmission.

46. ​​The apparatus of claim 45, wherein a transport block (TB) is repeated within each symbol allocation in each of the consecutive slots, and wherein the PDSCH is restricted to a single transport layer.

47. The apparatus of claim 33, wherein the fallback DCI IE is not configured to indicate an aggregation factor, the operations further comprising: Determining that the UE is configured with a pusch-AggregationFactor; In response to the determining, applying the same symbol allocation across a plurality of consecutive time slots corresponding to the pusch-AggregationFactor among the plurality of time slots, and configuring the PUSCH to a single transmission layer; as well as PUSCH data scheduled by a DCI format 0_1 ​​IE in a PDCCH including a CRC scrambled with at least one of a C-RNTI or an MCS-C-RNTI is transmitted.

48. The apparatus of claim 33, wherein the shared channel communication with the base station comprises communication using one of a PDSCH or a PUSCH.

Images