Mechanisms for handling uplink grants indicating different physical uplink shared channel starting positions in a same subframe

Methods, systems, and computer-readable storage media are provided for handling uplink grants indicating different physical uplink shared channel (PUSCH) starting positions in a same subframe of enhanced Licensed Assisted Access (eLAA) systems. In embodiments, a user equipment (UE) may receive Downlink Control Information (DCI). The DCI may indicate at least two uplink grants for one or more LAA secondary cell. Each of the at least two uplink grants may indicate different starting positions for PUSCH transmissions within a same subframe. The UE may align the different starting positions such that the UE is to transmit uplink transmissions according to the at least two uplink grants while the UE is in a transmission mode. Other embodiments may be described and/or claimed.

FIELD

Various embodiments of the present application generally relate to the field of wireless communications, and in particular, to conditional handovers and mobility state estimation.

BACKGROUND

Some Long Term Evolution (LTE) systems may operate in unlicensed spectrum, which are typically in the 5 gigahertz (GHz) frequency band. Licensed Assisted Access (LAA), enhanced LAA (eLAA), and further eLAA (feLAA) are Third Generation Partnership Project (3GPP) standards-based technology mechanisms that require an anchor in licensed spectrum to enable communications in the unlicensed spectrum. LAA, eLAA, and feLAA adhere to the listen-before-talk (LBT) protocol, where LAA adheres requires an LBT mechanism only for downlink (DL) communications, while eLAA and feLAA require LBT mechanisms for both DL and uplink (UL) communications. In addition to various regulatory requirements, such as indoor-only use, maximum in-band output power, in-band power spectral density, and out-of-band and spurious emissions, LTE operation in some unlicensed spectrum also implement dynamic frequency selection (DFS) and transmit power control (TPC) depending on the operating band to avoid interfering with radars.

Furthermore, some LTE systems, such as LTE-Advanced systems, support carrier aggregation (CA), which distinguishes between primary cells (PCells) and secondary cell (SCells). A PCell is a main cell with which a user equipment (UE) communicates and maintains the UE's connection with the network. One or more SCells may be allocated and activated to the UEs supporting CA for bandwidth extension. In LAA, some or all of the SCells may operate in the unlicensed spectrum (referred to as “LAA SCells”), where the LAA SCells are assisted by a licensed PCell via CA. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different Physical Uplink Shared Channel (PUSCH) starting positions within a same subframe.

DETAILED DESCRIPTION

Embodiments herein are related to situations in which a user equipment (UE) receives uplink (UL) grants on configured Licensed Assisted Access (LAA) secondary cells (SCells) indicating different PUSCH starting position within a same subframe. For example, Downlink Control Information (DCI) formats 0A, 0B, 4A and/or 4B may include a two-bit Physical Uplink Shared Channel (PUSCH) starting position field that indicates a starting position for transmitting UL data in a subframe. The possible PUSCH starting positions may include symbol0, 25 us in symbol0, (25+TA) us in symbol0, and symbol1. The DCI may indicate one out of four possible starting positions and, according to the current standards, there is no limitation on the possible combinations of PUSCH starting positions on different LAA SCells within a same subframe. Therefore, the UE could be required to transmit multiple UL transmissions at different starting positions within a same subframe. This may cause issues in LAA systems, when the UE is not capable of performing listen-before-talk (LBT) operations while in a transmission mode.

According to various embodiments, the UE is not expected to receive UL grants on LAA SCells indicating different PUSCH starting positions in the same subframe. In embodiments, when a UE receives UL grants indicating different PUSCH starting positions in the same subframe, the UE may align the PUSCH starting position to the earliest position among the indicated positions. In embodiments, when a UE receives UL grants indicating different PUSCH starting positions in the same subframe, the UE may align the PUSCH starting position to the latest position among the indicated positions. In embodiments, when a UE receives UL grants indicating different PUSCH starting positions in the same subframe, and if the UE is in a transmission mode to transmit PUSCH transmission on one or more LAA SCells, the UE may not be required to process the UL grants indicating PUSCH starting positions later in time. In these embodiments, the UE may not be required to perform LBT while in the transmission mode. In embodiments, if the UE fails LBT for all PUSCH starting positions earlier in time, the UE may continue to perform LBT for PUSCH starting positions later in time according to the UL grants. Other embodiments may be described and/or claimed.

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc., in order to provide a thorough understanding of the various aspects of the claimed invention. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the invention claimed may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.

The phrase “in various embodiments,” “in some embodiments,” and the like are used repeatedly. The phrase generally does not refer to the same embodiments; however, it may. The terms “comprising,” “having,” and “including” are synonymous, unless the context dictates otherwise. The phrase “A and/or B” means (A), (B), or (A and B). The phrases “A/B” and “A or B” mean (A), (B), or (A and B), similar to the phrase “A and/or B.” For the purposes of the present disclosure, the phrase “at least one of A and B” means (A), (B), or (A and B). The description may use the phrases “in an embodiment,” “in embodiments,” “in some embodiments,” and/or “in various embodiments,” which may each refer to one or more of the same or different embodiments. Furthermore, the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure, are synonymous.

Example embodiments may be described as a process depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel, concurrently, or simultaneously. In addition, the order of the operations may be re-arranged. A process may be terminated when its operations are completed, but may also have additional steps not included in the figure(s). A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, and the like. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function and/or the main function.

Example embodiments may be described in the general context of computer-executable instructions, such as program code, software modules, and/or functional processes, being executed by one or more of the aforementioned circuitry. The program code, software modules, and/or functional processes may include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular data types. The program code, software modules, and/or functional processes discussed herein may be implemented using existing hardware in existing communication networks. For example, program code, software modules, and/or functional processes discussed herein may be implemented using existing hardware at existing network elements or control nodes.

Referring now to the figures,FIG. 1Aillustrates an architecture of a system100A of a network, in accordance with various embodiments. The following description is provided for an example system100A that operates in conjunction with the Fifth Generation (5G) or New Radio (NR) system standards as provided by 3rd Generation Partnership Project (3GPP) technical specifications (TS). However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as Long Term Evolution (LTE), future (for example, Sixth Generation (6G)) systems, and the like.

As shown byFIG. 1A, the system100A may include user equipment (UE)101and UE102. As used herein, the term “user equipment” or “UE” may refer to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as client, mobile, 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 including a wireless communications interface. In this example, UEs101and102are illustrated as smartphones (for example, handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” appliances, machine-type communications (MTC) devices, machine-to-machine (M2M), Internet of Things (IoT) devices, and/or the like.

The UEs101and102may be configured to connect, for example, communicatively couple, with a access network (AN) or radio access network (RAN)110. In embodiments, the RAN110may be a next generation (NG) RAN or a 5G RAN, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), or a legacy RAN, such as a UTRAN (UMTS Terrestrial Radio Access Network) or GERAN (GSM (Global System for Mobile Communications or Groupe Spécial Mobile) EDGE (GSM Evolution) Radio Access Network). As used herein, the term “NG RAN” or the like may refer to a RAN110that operates in an NR or 5G system100A, and the term “E-UTRAN” or the like may refer to a RAN110that operates in an LTE or 4G system100A. The UEs101and102utilize connections (or channels)103and104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below). As used herein, the term “channel” may refer to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” may refer to a connection between two devices through a Radio Access Technology (RAT) for the purpose of transmitting and receiving information.

In this example, the connections103and104are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and/or any of the other communications protocols discussed herein. In embodiments, the UEs101and102may directly exchange communication data via a ProSe interface105. The ProSe interface105may alternatively be referred to as a sidelink (SL) interface105and may comprise one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

The UE102is shown to be configured to access an access point (AP)106(also referred to as also referred to as “WLAN node106”, “WLAN106”, “WLAN Termination106” or “WT106” or the like) via connection107. The connection107can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP106would comprise a wireless fidelity (WiFi®) router. In this example, the AP106is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). In various embodiments, the UE102, RAN110, and AP106may be configured to utilize LTE-WLAN aggregation (LWA) operation and/or WLAN LTE/WLAN Radio Level Integration with IPsec Tunnel (LWIP) operation. The LWA operation may involve the UE102in RRC_CONNECTED being configured by a RAN node111,112to utilize radio resources of LTE and WLAN. LWIP operation may involve the UE102using WLAN radio resources (for example, connection107) via Internet Protocol Security (IPsec) protocol tunneling to authenticate and encrypt packets (for example, internet protocol (IP) packets) sent over the connection107. IPsec tunneling may include encapsulating entirety of original IP packets and adding a new packet header thereby protecting the original header of the IP packets.

The RAN110can include one or more AN nodes or RAN nodes111and112that enable the connections103and104. As used herein, the terms “access node,” “access point,” or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users. These access nodes can be referred to as base stations (BS), next Generation NodeBs (gNBs), RAN nodes, evolved NodeBs (eNBs), NodeBs, Road Side Units (RSUs), Transmission Reception Points (TRxPs or TRPs), and so forth, and can comprise ground stations (for example, terrestrial access points) or satellite stations providing coverage within a geographic area (for example, a cell). The term “Road Side Unit” or “RSU” may refer to any transportation infrastructure entity implemented in or by an gNB/eNB/RAN node or a stationary (or relatively stationary) UE, where 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.” As used herein, the term “NG RAN node” or the like may refer to a RAN node111/112that operates in an NR or 5G system100A (for example a gNB), and the term “E-UTRAN node” or the like may refer to a RAN node111/112that operates in an LTE or 4G system100A (for example, an eNB). According to various embodiments, the RAN nodes111and/or112may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. In other embodiments, the RAN nodes111and/or112may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a cloud radio access network (CRAN). In other embodiments, the RAN nodes111and112may represent individual gNB-distributed units (DUs) that are connected to a gNB-centralized unit (CU) via an F1 interface (not shown byFIG. 1A).

Any of the RAN nodes111and112can terminate the air interface protocol and can be the first point of contact for the UEs101and102. In some embodiments, any of the RAN nodes111and112can fulfill various logical functions for the RAN110including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

According to various embodiments, the UEs101,102and the RAN nodes111,112communicate data (for example, transmit and receive) data over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band”) and an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band”). The licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band.

To operate in the unlicensed spectrum, the UEs101,102and the RAN nodes111,112may operate using Licensed Assisted Access (LAA), enhanced LAA (eLAA), and/or further eLAA (feLAA) mechanisms. In these implementations, the UEs101,102and the RAN nodes111,112may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum. The medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

LBT is a mechanism whereby equipment (for example, UEs101,102, RAN nodes111,112, etc.) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation may include clear channel assessment (CCA), which utilizes at least energy detection (ED) to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear. This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks. ED may include sensing radiofrequency (RF) energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technologies. WLAN employs a contention-based channel access mechanism, called carrier sense multiple access with collision avoidance (CSMA/CA). Here, when a WLAN node (e.g., a mobile station (MS) such as UE101or102, AP106, or the like) intends to transmit, the WLAN node may first perform CCA before transmission. Additionally, a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time. The backoff mechanism may be a counter that is drawn randomly within the contention window size (CWS), which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds. The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN. In some implementations, the LBT procedure for DL or UL transmission bursts including PDSCH or PUSCH transmissions, respectively, may have an LAA contention window that is variable in length between X and Y extended CCA (ECCA) slots, where X and Y are minimum and maximum values for the CWSs for LAA. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (μs); however, the size of the CWS and a maximum channel occupancy time (MCOT) (for example, a transmission burst) may be based on governmental regulatory requirements.

The LAA mechanisms are built upon carrier aggregation (CA) technologies of LTE-Advanced systems. In CA, each aggregated carrier is referred to as a component carrier (CC). A CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz. In Frequency Division Duplexing (FDD) systems, 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, individual CCs can have a different bandwidth than other CCs. In Time Division Duplexing (TDD) systems, the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.

CA also comprises individual serving cells to provide individual CCs. The coverage of the serving cells may differ, for example, due to that CCs on different frequency bands will experience different pathloss. A primary service cell or primary cell (PCell) may provide a Primary CC (PCC) for both UL and DL, and may handle Radio Resource Control (RRC) and Non-Access Stratum (NAS) related activities. The other serving cells are referred to as secondary cells (SCells), and each SCell may provide an individual Secondary CC (SCC) for both UL and DL. The SCCs may be added and removed as required, while changing the PCC may require the UE101,102to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in the unlicensed spectrum (referred to as “LAA SCells”), and the LAA SCells are assisted by a PCell operating in the 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 Physical Uplink Shared Channel (PUSCH) starting positions within a same subframe.

The physical downlink shared channel (PDSCH) may carry user data and higher-layer signaling to the UEs101and102. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs101and102about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE102within a cell) may be performed at any of the RAN nodes111and112based on channel quality information fed back from any of the UEs101and102. The downlink resource assignment information may be sent on the PDCCH used for (for example, assigned to) each of the UEs101and102.

As an example, a subframe may include multiple physical resource block (PRB) pairs of a PDCCH and/or an EPDCCH, where one or more of the PRB pairs may carrier control information intended for the UE101,102. This subframe may be one of ten 1 millisecond (ms) subframes within a radio frame that is 10 millisecond (ms). The radio frame may be a frame structure 1 (FS1) radio frame, a frame structure 2 (FS2) radio frame, or a frame structure 3 (FS3) radio frame. An OFDMA sub-carrier spacing for the radio frame in the frequency domain may be 15 kilohertz (kHz). Twelve of these sub-carriers together allocated during a 0.5 ms timeslot are called a resource block, which may include a PRB pair. A UE101,102may be allocated, in the downlink or uplink, a minimum of two resources blocks during one subframe. According to existing standards, the PDSCH may be used for user data transmissions and the PDCCH and/or EPDCCH may be used for control information. The control information may specify the format of the data, and the location and timing of the radio resources allocated to the UE101,102for transmitting or receiving data. The control information may be in the form of a Downlink Control Information (DCI) message. The DCI message may be identified by a radio network temporary identifier (RNTI) encoded in the DCI message.

A DCI message may transport downlink, uplink, or sidelink scheduling information, requests for aperiodic Channel Quality Indicator (CQI) reports, Licensed Assisted Access (LAA) common information, notifications of Multicast Control Channel (MCCH) changes, or uplink power control commands for one cell and one Radio Network Temporary Identifier (RNTI). The RNTI may be implicitly encoded in the cyclic redundancy check (CRC) bits of the DCI.

DCI may be conveyed using a plurality of DCI formats. In particular, DCI format 0A may be used for the scheduling of PUSCH transmissions in a LAA SCell; DCI format 0B may be used for the scheduling of PUSCH in each of multiple subframes in a LAA SCell; DCI format 4A may be used for the scheduling of PUSCH in a LAA SCell with multi-antenna port transmission mode; and DCI format 4B may be used for the scheduling of PUSCH with multi-antenna port transmission mode in each of multiple subframes in a LAA SCell. Each of DCI format 0A, 0B, 4A, and 4B may include, inter alia, a one bit channel access type field, a two bit channel access priority class field, and a PUSCH starting position comprising two bits with values as specified by table 1.

As shown byFIG. 1B, issues may arise when the UE101,102receives multiple UL grants on configured LAA SCells indicating different PUSCH starting positions within a same subframe.

FIG. 1Bshows a scenario100B where a UE101,102is configured with more than one LAA SCells and receives multiple UL grants indicating different PUSCH starting positions. InFIG. 1B, the subframe n comprises a plurality of symbols140(labeled 1-11 inFIG. 1B). In this example, the UL grants received by the UE101may include a first UL grant (“UL grant1” inFIG. 1B) to start from symbol0and a second UL grant (“UL grant2” inFIG. 1B) to start from symbol1. Prior to transmitting on the indicated symbol, the UE101,102may perform LBT at the starting position to determine whether the channel is unoccupied. As discussed previously, the UL grants could indicate one out of four possible starting positions and, according to the current LTE standards, there is no limitation on the possible combinations of PUSCH starting positions on different LAA SCells within a same subframe.

One problem of the UL grants indicating different PUSCH starting positions is that the UE101,102may already be in a transmission mode at the indicated PUSCH starting position later in time within the same subframe. For example, the UE101,102may be in the transmission mode at the starting position for symbol1based on the UL grant1. The UE101,102performing LBT while in transmission mode may be considered equivalent to requiring the UE101,102to be capable of simultaneous reception and transmission. However, most LTE-capable UEs are not required to be capable of simultaneous transmission and reception.

One example where such a problem may arise is when the subframe n is part of an FS2 radio frame, where multiple cells with different uplink-downlink configurations in the current radio frame are aggregated. This is because, when multiple cells with different uplink-downlink configurations in the current radio frame are aggregated and the UE101,102is not capable of simultaneous reception and transmission in the aggregated cells, the UE101,102may be constrained as follows:if the subframe in the PCell is a DL subframe, the UE101,102shall not transmit any signal or channel on an SCell in the same subframe;if the subframe in the PCell is an UL subframe, the UE is not expected to receive any DL transmissions on an SCell in the same subframe; and/orif the subframe in the PCell is a special subframe and the same subframe in an SCell is a DL subframe, the UE101,102is not expected to receive PDSCH/EPDCCH/PMCH/PRS transmissions in the SCell in the same subframe, and the UE101,102is not expected to receive any other signals on the SCell in OFDM symbols that overlap with a guard period or Uplink Pilot Timeslot (UpPTS) in the PCell.

The embodiments discussed herein provide various mechanisms to remove considerations on simultaneous transmission and reception in eLAA UE implementations. In embodiments, the following relaxation may be applied: “A UE is not expected to receive UL grants on LAA SCells indicating different PUSCH starting positions in the same subframe.”

In order to remove considerations on simultaneous transmission and reception in eLAA UE implementations, the following relaxations can be considered.Embodiment 1: The UE101,102is not expected to receive UL grants on LAA SCells indicating different PUSCH starting positions in the same subframe.Embodiment 2: If UL grants indicating different PUSCH starting positions in the same subframe are received, the UE101,102may align the PUSCH starting position to an earliest position among the indicated starting positions.Embodiment 3: If UL grants indicating different PUSCH starting positions in the same subframe are received, the UE101,102may aligns the PUSCH starting position to a latest position among the indicated starting positions.Embodiment 4: If UL grants indicating different PUSCH starting positions in the same subframe are received and if the UE101,102is in transmission of PUSCH on one LAA SCell, the UE101,102is not required to process the UL grants indicating PUSCH starting positions later in time. In other words, the UE101,102is not required to perform LBT while in the transmission mode. If the UE fails LBT for all PUSCH starting positions earlier in time, the UE will continue to perform LBT for PUSCH starting positions later in time according to the UL grants.

The above relaxations may only apply to the LAA SCells belonging to the same RF band, for example, intra-band CA. If a subset of aggregated LAA SCells belongs to different RF band(s), for example, inter-band CA, the UE101,102may be able to simultaneously transmit and receive. For example, the UE101,102may be able to process UL grants indicating different PUSCH starting positions.

According to various implementations of embodiments 1-4, the UE101,102may operate as follows:

The UE101,102may access a carrier on which LAA Scell(s) UL transmission(s) are performed according to one of type 1 or type 2 UL channel access procedures. The type 1 channel access procedure may be as follows:

The UE101,102may perform a sensing operation and may transmit after sensing the channel to be idle during the slot durations of a defer duration Td; and after the counter N is zero (see step 4). The counter N may be adjusted by sensing the channel for additional slot duration(s) according to the following steps:

1) set counter N to be N=Ninit, where Ninitis a random number uniformly distributed between 0 and CWp, and go to step 4, where CWpis a contention window adjustment that is based on a channel access priority class p on a carrier (see e.g., table 2);

2) if N>0 and the UE101,102chooses to decrement the counter, set N=N−1;

3) sense the channel for an additional slot duration, and if the additional slot duration is idle, go to step 4; else, go to step 5;

5) sense the channel until either a busy slot is detected within an additional defer duration Tdor all the slots of the additional defer duration Tdare detected to be idle; and

6) if the channel is sensed to be idle during all the slot durations of the additional defer duration Td, go to step 4; else, go to step 5.

The type 2 channel access procedure may be as follows: If the UE101,102uses the type 2 channel access procedure for a transmission including PUSCH, the UE101,102may transmit the transmission including the PUSCH immediately after sensing the channel to be idle for at least a sensing interval Tshort_ul=25 μs. Tshort_ulcomprises a duration Tf=16 μs immediately followed by one slot duration Tsl=9 μs and Tfincludes an idle slot duration Tslat start of Tf. The channel is considered to be idle for Tshort_ulif it is sensed to be idle during the slot durations of Tshort_ul.

The UE101,102may use the type 1 or type 2 channel access procedure for transmitting transmissions including the PUSCH transmission when a UL grant scheduling a PUSCH transmission indicates the type 1 channel access procedure or the type 2 channel access procedure. The UE101,102may also use the type 1 channel access procedure for transmitting sounding reference signal (SRS) transmissions not including a PUSCH transmission. A channel access priority class of p=1 may be used for UL SRS transmissions that do not include a PUSCH transmission.

If the UE101,102is scheduled to transmit transmissions including PUSCH in a set subframes n0, n1,Λ, nw−1using PDCCH DCI Format 0B/4B, and if the UE101,102cannot access the channel for a transmission in subframe nk, the UE101,102may attempt to make a transmission in subframe nk+1 according to the channel access type indicated in the DCI, where k∈{0,1,Λ w−2}, and w is the number of scheduled subframes indicated in the DCI.

If the UE101,102is scheduled to transmit transmissions without gaps including PUSCH in a set of subframes n0, n1,Λ, nw−1using one or more PDCCH DCI Format 0A/0B/4A/4B and the UE101,102performs a transmission in subframe nkafter accessing the carrier according to one of type 1 or type 2 UL channel access procedures, the UE101,102may continue transmission in subframes after nkwhere k∈{0,1,Λ w−1}.

If the beginning of the UE transmission in subframe n+1 immediately follows the end of the UE transmission in subframe n, the UE101,102is not expected to be indicated with different channel access types for the transmissions in those subframes.

If the UE101,102is scheduled to transmit without gaps in subframes n0, n1,Λ, nw−1using one or more PDCCH DCI Format 0A/0B/4A/4B, and if the UE101,102has stopped transmitting during or before subframe nk1, k1∈{0,1,Λ w−2}, and if the channel is sensed by the UE101,102to be continuously idle after the UE101,102has stopped transmitting, the UE101,102may transmit in a later subframe nk2, k2∈{1,Λ w−1} using type 2 channel access procedure. If the channel sensed by the UE is not continuously idle after the UE has stopped transmitting, the UE101,102may transmit in a later subframe nk2, k2∈{1,Λw−1} using type 1 channel access procedure with the UL channel access priority class indicated in the DCI corresponding to subframe nk2.

If the UE101,102receives an UL grant and the DCI indicates a PUSCH transmission starting in subframe n using type 1 channel access procedure, and if the UE101,102has an ongoing type 1 channel access procedure before subframe n, and:

if the UL channel access priority class value p1used for the ongoing type 1 channel access procedure is same or larger than the UL channel access priority class value p2indicated in the DCI, the UE101,102may transmit the PUSCH transmission in response to the UL grant by accessing the carrier by using the ongoing type 1 channel access procedure.

if the UL channel access priority class value p1used for the ongoing type 1 channel access procedure is smaller than the UL channel access priority class value p2indicated in the DCI, the UE101,102may terminate the ongoing channel access procedure.

If the UE101,102is scheduled to transmit on a set of carriers C in subframe n, and if the UL grants scheduling PUSCH transmissions on the set of carriers C indicate type 1 channel access procedure, and if the same ‘PUSCH starting position’ is indicated for all carriers in the set of carriers C, and if the carrier frequencies of set of carriers C is a subset of one of a defined sets of carrier frequencies, then:

the UE101,102may transmit on carrier ci∈C using type 2 channel access procedure,

if type 2 channel access procedure is performed on carrier ciimmediately before the UE transmission on carrier ci∈C, i≠j, and:

if the UE101,102has accessed carrier cjusing type 1 channel access procedure,

where carrier cjis selected by the UE101,102uniformly randomly from the set of carriers C before performing type 1 channel access procedure on any carrier in the set of carriers C.

As an implementation of embodiment 1, the UE101,102may operate as follows: If the UE101,102is scheduled to transmit on a set of carriers C in subframe n, where the carrier frequencies of set of carriers C is a subset of one of the defined sets of carrier frequencies, the UE101,102is not expected to receive UL grants indicating different ‘PUSCH starting positions’ in the same subframe n.

A RAN node111,112(e.g., an eNB) may indicate type 2 channel access procedure in the DCI of an UL grant scheduling transmission(s) including PUSCH on a carrier in subframe n when the eNB111,112has transmitted on the carrier according to a channel access procedure discussed elsewhere, or the eNB111,112may indicate using the ‘UL duration and offset’ field that the UE101,102may perform a type 2 channel access procedure for transmissions(s) including PUSCH on a carrier in subframe n when the eNB111,112has transmitted on the carrier according to the channel access procedure described elsewhere, or the eNB111,112may schedule transmissions including PUSCH on a carrier in subframe n, that follows a transmission by the eNB111,112on that carrier with a duration of Tshort_ul=25 μs, if subframe n occurs within the time interval starting at t0and ending at t0+TCO, where TCO=Tmcot,p+Tg, where t0is the time instant when the eNB has started transmission, Tmcot,pvalue is determined by the eNB111,112, and Tgis the total duration of all gaps of duration greater than 25 μs that occur between the DL transmission of the eNB111,112and UL transmissions scheduled by the eNB, and between any two UL transmissions scheduled by the eNB111,112starting from t0.

The eNB111,112may schedule UL transmissions between t0and t0+TCOin contiguous subframes if they can be scheduled contiguously. For an UL transmission on a carrier that follows a transmission by the eNB on that carrier within a duration of Tshort_ul=25 μs, the UE101,102may use type 2 channel access procedure for the UL transmission. If the eNB111,112indicates type 2 channel access procedure for the UE101,102in the DCI, the eNB111,112may indicate the channel access priority class used to obtain access to the channel in the DCI.

Referring back toFIG. 1A, the RAN nodes111,112may be configured to communicate with one another via interface113X. In embodiments where the system100A is an LTE system, the interface113X may be an X2 interface113X. The X2 interface may be defined between two or more RAN nodes111,112(for example, two or more eNBs and the like) that connect to EPC120, and/or between two eNBs connecting to EPC120. 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 flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data transferred from a master eNB (MeNB) to a secondary eNB (SeNB); information about successful in sequence delivery of PDCP PDUs to a UE101/102from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE101/102; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs, user plane transport control, etc.; load management functionality; as well as inter-cell interference coordination functionality.

In embodiments where the system100A is a 5G or NR system, the interface113X may be an Xn interface113X. The Xn interface is defined between two or more RAN nodes111,112(for example, two or more gNBs and the like) that connect to 5GC120, between a RAN node111,112(for example, a gNB) connecting to 5GC120and an eNB, and/or between two eNBs connecting to 5GC120. 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 functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE101/102in a connected mode (for example, CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes211. The mobility support may include context transfer from an old (source) serving RAN node111,112to new (target) serving RAN node111,112; and control of user plane tunnels between old (source) serving RAN node111,112to new (target) serving RAN node111,112. A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on SCTP. The SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages. In the transport IP layer point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

The RAN110is shown to be communicatively coupled to a core network—in this embodiment, Core Network (CN)120. The CN120may comprise a plurality of network elements122, which are configured to offer various data and telecommunications services to customers/subscribers (for example, users of UEs101,102) who are connected to the CN120via the RAN110. The term “network element” may describe a physical or virtualized equipment used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, router, switch, hub, bridge, radio network controller, radio access network device, gateway, server, virtualized network function (VNF), network functions virtualization infrastructure (NFVI), and/or the like. The components of the CN120may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (for example, a non-transitory machine-readable storage medium). In some embodiments, Network Functions Virtualization (NFV) may be utilized to virtualize any or all of the above described network node functions via executable instructions stored in one or more computer readable storage mediums (described in further detail below). A logical instantiation of the CN120may be referred to as a network slice, and a logical instantiation of a portion of the CN120may be referred to as a network sub-slice. NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

In embodiments, the CN120may be a 5G CN (referred to as “5GC120” or the like), while in other embodiments, the CN120may be an Evolved Packet Core (EPC). Where CN120is an EPC (referred to as “EPC120” or the like), the RAN110may be connected with the CN120via an S1 interface113A. In embodiments, the S1 interface113A may be split into two parts, an S1 user plane (S1-U) interface114, which carries traffic data between the RAN nodes111and112and the serving gateway (S-GW), and the S1-mobility management entity (MME) interface115, which is a signaling interface between the RAN nodes111and112and MMEs.

In embodiments, the EPC120comprises the MMEs, the S-GW, the Packet Data Network (PDN) Gateway (P-GW), and a home subscriber server (HSS). The MMEs121may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs may perform various mobility management (MM) procedures to manage mobility aspects in 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 storage, etc. that are used to maintain knowledge about a present location of the UE101,102, provide user identity confidentiality, and/or other like services to users/subscribers. Each UE101,102and the MME121may include an MM or EMM sublayer, and an MM context may be established in the UE101,102and the MME when an attach procedure is successfully completed. The MM context may be a data structure or database object that stores MM-related information of the UE101,102.

The HSS may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The EPC network120may comprise one or several HSSs124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

The S-GW may terminate the S1 interface113A towards the RAN110, and routes data packets between the RAN110and the EPC120. In addition, the S-GW may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The P-GW may terminate an SGi interface toward a PDN. The P-GW may route data packets between the EPC network123and e2ernal networks such as a network including the application server130(alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface125. Generally, the application server130may be an element offering applications that use IP bearer resources with the core network (for example, UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW is shown to be communicatively coupled to an application server130via an IP communications interface125. The application server130can also be configured to support one or more communication services (for example, Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs101and102via the EPC120.

The P-GW may further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF) is the policy and charging control element of the EPC120. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with an RE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with an RE's IP-CAN session, a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF may be communicatively coupled to the application server130via the P-GW. The application server130may signal the PCRF to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF126may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server130.

Where CN120is a 5GC (referred to as “5GC120” or the like), the RAN110may be connected with the CN120via an NG interface113A. In embodiments, the NG interface113A may be split into two parts, an NG user plane (NG-U) interface114, which carries traffic data between the RAN nodes111and112and a user plane function (UPF), and the S1 control plane (NG-C) interface115, which is a signaling interface between the RAN nodes111and112and Access and Mobility Functions (AMFs). Embodiments where the CN120is a 5GC120are discussed in more detail with regard toFIG. 2.

FIG. 2illustrates an architecture of a system200of a 5G network in accordance with some embodiments. The system200is shown to include a UEs101and102(collectively referred to as “UEs101/102” or “UE101/102”) discussed previously; a RAN110discussed previously, and which may include RAN nodes111and112discussed previously; and a Data network (DN)203, which may be, for example, operator services, Internet access or 3rd party services; and a 5G Core Network (5GC or CN)120.

The CN120may include an Authentication Server Function (AUSF)222; an Access and Mobility Management Function (AMF)221; a Session Management Function (SMF)224; a Network Exposure Function (NEF)223; a Policy Control function (PCF)226; a Network Function (NF) Repository Function (NRF)225; a Unified Data Management (UDM)227; an Application Function (AF)228; a User Plane Function (UPF)202; and a Network Slice Selection Function (NSSF)229.

The UPF202may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to DN203, and a branching point to support multi-homed PDU session. The UPF202may also perform packet routing and forwarding, packet inspection, enforce user plane part of policy rules, lawfully intercept packets (UP collection); traffic usage reporting, perform QoS handling for user plane (e.g. packet filtering, gating, UL/DL rate enforcement), perform Uplink Traffic verification (for example, SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and downlink packet buffering and downlink data notification triggering. UPF202may include an uplink classifier to support routing traffic flows to a data network. The DN203may represent various network operator services, Internet access, or third party services. NY203may include, or be similar to application server130discussed previously. The UPF202may interact with the SMF224via an N4 reference point between the SMF224and the UPF202.

The AUSF222may store data for authentication of UE101/102and handle authentication related functionality. The AUSF222may facilitate a common authentication framework for various access types. The AUSF222may communicate with the AMF221via an N12 reference point between the AMF221and the AUSF222; and may communicate with the UDM227via an N13 reference point between the UDM227and the AUSF222. Additionally, the AUSF222may exhibit an Nausf service-based interface.

The AMF221may be responsible for registration management (for example, for registering UE101/102, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF221may be a termination point for the an N11 reference point between the AMF221and the SMF224. The AMF221may provide transport for Session Management (SM) messages between the UE101/102and the SMF224, and act as a transparent proxy for routing SM messages. AMF221may also provide transport for short message service (SMS) messages between UE101/102and an SMS function (SMSF) (not shown byFIG. 2). AMF221may act as Security Anchor Function (SEA), which may include interaction with the AUSF222and the UE101/102, receipt of an intermediate key that was established as a result of the UE101/102authentication process. Where USIM based authentication is used, the AMF221may retrieve the security material from the AUSF222. AMF221may also include a Security Context Management (SCM) function, which receives a key from the SEA that it uses to derive access-network specific keys. Furthermore, AMF221may be a termination point of RAN CP interface, which may include or be an N2 reference point between the (R)AN211and the AMF221; and the AMF221may be a termination point of NAS (N1) signalling, and perform NAS ciphering and integrity protection.

AMF221may also support NAS signalling with a UE101/102over an N3 interworking-function (IWF) interface. The N3IWF may be used to provide access to untrusted entities. N3IWF may be a termination point for the N2 interface between the (R)AN211and the AMF221for the control plane, and may be a termination point for the N3 reference point between the (R)AN211and the UPF202for the user plane. As such, the AMF221may handle N2 signalling from the SMF224and the AMF221for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated to such marking received over N2. N3IWF may also relay uplink and downlink control-plane NAS signalling between the UE101/102and AMF221via an N1 reference point between the UE101/102and the AMF221, and relay uplink and downlink user-plane packets between the UE101/102and UPF202. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE101/102. The AMF221may exhibit an Namf service-based interface, and may be a termination point for an N14 reference point between two AMFs221and an N17 reference point between the AMF221and a 5G-Equipment Identity Register (5G-EIR) (not shown byFIG. 2).

The UE101/102may need to register with the AMF221in order to receive network services. Registration Management (RM) is used to register or deregister the UE221with the network (for example, AMF221), and establish a UE context in the network (for example, AMF221). The UE101/102may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE101/102is not registered with the network, and the UE context in AMF221holds no valid location or routing information for the UE101/102so the UE101/102is not reachable by the AMF221. In the RM-REGISTERED state, the UE101/102is registered with the network, and the UE context in AMF221may hold a valid location or routing information for the UE101/102so the UE101/102is reachable by the AMF221. In the RM-REGISTERED state, the UE101/102may perform mobility Registration Update procedures, perform periodic Registration Update procedure triggered by expiration of the periodic update timer (for example, to notify the network that the UE101/102is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

The AMF221may store one or more RM contexts for the UE101/102, where each RM context is associated with a specific access to the network. The RM context may be a data structure, database object, etc. that indicates or stores, inter alia, a registration state per access type and the periodic update timer. The AMF221may also store a 5GC MM context that may be the same or similar to the (E)MM context discussed previously. In various embodiments, the AMF221may store a CE mode B Restriction parameter of the UE101/102in an associated MM context or RM context. The AMF221may also derive the value, when needed, from the UE's usage setting parameter {possible values: “Data Centric”, “Voice Centric”} already stored in the UE context (and/or MM/RM Context).

Connection Management (CM) may be used to establish and release a signaling connection between the UE101/102and the AMF221over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE101/102and the CN120, and comprises both the AN signaling connection between the UE and the Access Network (AN) (for example, RRC connection or UE-N3IWF connection for Non-3GPP access) and the N2 connection for the UE101/102between the AN (for example, RAN211) and the AMF221. The UE101/102may operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode. When the UE101/102is operating in the CM-IDLE state/mode, the UE101/102may have no NAS signaling connection established with the AMF221over the N1 interface, and there may be (R)AN211signaling connection (for example, N2 and/or N3 connections) for the UE101/102. When the UE101/102is operating in the CM-CONNECTED state/mode, the UE101/102may have an established NAS signaling connection with the AMF221over the N1 interface, and there may be a (R)AN211signaling connection (for example, N2 and/or N3 connections) for the UE101/102. Establishment of an N2 connection between the (R)AN211and the AMF221may cause the UE101/102to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE101/102may transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R)AN211and the AMF221is released.

The SMF224may be responsible for session management (for example, session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation & management (including optional Authorization); Selection and control of UP function; Configures traffic steering at UPF to route traffic to proper destination; termination of interfaces towards Policy control functions; control part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI System); termination of SM parts of NAS messages; downlink Data Notification; initiator of AN specific SM information, sent via AMF over N2 to AN; determine SSC mode of a session. The SMF224may include the following roaming functionality: handle local enforcement to apply QoS SLAB (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI System); support for interaction with external DN for transport of signalling for PDU session authorization/authentication by external DN. An N16 reference point between two SMFs224may be included in the system200, which may be between another SMF224in a visited network and the SMF224in the home network in roaming scenarios. Additionally, the SMF224may exhibit the Nsmf service-based interface.

The NEF223may provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, Application Functions (for example, AF228), edge computing or fog computing systems, etc. In such embodiments, the NEF223may authenticate, authorize, and/or throttle the AFs. NEF223may also translate information exchanged with the AF228and information exchanged with internal network functions. For example, the NEF223may translate between an AF-Service-Identifier and an internal 5GC information. NEF223may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF223as structured data, or at a data storage NF using a standardized interfaces. The stored information can then be re-exposed by the NEF223to other NFs and AFs, and/or used for other purposes such as analytics. Additionally, the NEF223may exhibit an Nnef service-based interface.

The NRF225may support service discovery functions, receive NF Discovery Requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF225also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate”, “instantiation”, and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF225may exhibit the Nnrf service-based interface.

The PCF226may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behaviour. The PCF226may also implement a front end (FE) to access subscription information relevant for policy decisions in a UDR of the UDM227. The PCF226may communicate with the AMF221via an N15 reference point between the PCF226and the AMF221, which may include a PCF226in a visited network and the AMF221in case of roaming scenarios. The PCF226may communicate with the AF228via an N5 reference point between the PCF226and the AF228; and with the SMF224via an N7 reference point between the PCF226and the SMF224. The system200and/or CN120may also include an N24 reference point between the PCF226(in the home network) and a PCF226in a visited network. Additionally, the PCF226may exhibit an Npcf service-based interface.

The UDM227may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE101/102. For example, subscription data may be communicated between the UDM227and the AMF221via an N8 reference point between the UDM227and the AMF221(not shown byFIG. 2). The UDM227may include two parts, an application FE and a User Data Repository (UDR) (the FE and UDR are not shown byFIG. 2). The UDR may store subscription data and policy data for the UDM227and the PCF226, and/or structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, application request information for multiple UEs201) for the NEF223. The Nudr service-based interface may be exhibited by the UDR221to allow the UDM227, PCF226, and NEF223to access a particular set of the stored data, as well as to read, update (for example, add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM FE, which is in charge of processing of credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing; user identification handling; access authorization; registration/mobility management; and subscription management. The UDR may interact with the SMF224via an N10 reference point between the UDM227and the SMF224. UDM227may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM227may exhibit the Nudm service-based interface.

The AF228may provide application influence on traffic routing, access to the Network Capability Exposure (NCE), and interact with the policy framework for policy control. The NCE may be a mechanism that allows the 5GC and AF228to provide information to each other via NEF223, which may be used for edge computing implementations. In such implementations, the network operator and third party services may be hosted close to the UE101/102access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF202close to the UE101/102and execute traffic steering from the UPF202to DN203via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF228. In this way, the AF228may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF228is considered to be a trusted entity, the network operator may permit AF228to interact directly with relevant NFs. Additionally, the AF228may exhibit an Naf service-based interface.

The NSSF229may select a set of network slice instances serving the UE101/102. The NSSF229may also determine allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to the Subscribed Single-NSSAIs (S-NSSAIs), if needed. The NSSF229may also determine the AMF set to be used to serve the UE101/102, or a list of candidate AMF(s)221based on a suitable configuration and possibly by querying the NRF225. The selection of a set of network slice instances for the UE101/102may be triggered by the AMF221with which the UE101/102is registered by interacting with the NSSF229, which may lead to a change of AMF221. The NSSF229may interact with the AMF221via an N22 reference point between AMF221and NSSF229; and may communicate with another NSSF229in a visited network via an N31 reference point (not shown byFIG. 2). Additionally, the NSSF229may exhibit an Nnssf service-based interface.

As discussed previously, the CN120may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE101/102to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF221and UDM227for notification procedure that the UE101/102is available for SMS transfer (for example, set a UE not reachable flag, and notifying UDM227when UE101/102is available for SMS).

The CN120may also include other elements that are not shown byFIG. 2, such as a Data Storage system/architecture, a 5G-Equipment Identity Register (5G-EIR), a Security Edge Protection Proxy (SEPP), and the like. The Data Storage system may include a Structured Data Storage network function (SDSF), an Unstructured Data Storage network function (UDSF), and/or the like. Any NF may store and retrieve unstructured data into/from the UDSF (for example, UE contexts), via N18 reference point between any NF and the UDSF (not shown byFIG. 2). Individual NFs may share a UDSF for storing their respective unstructured data or individual NFs may each have their own UDSF located at or near the individual NFs. Additionally, the UDSF may exhibit an Nudsf service-based interface (not shown byFIG. 2). The 5G-EIR may be an NF that checks the status of Permanent Equipment Identifiers (PEI) for determining whether particular equipment/entities are blacklisted from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.

Additionally, there may be many more reference points and/or service-based interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted fromFIG. 2for clarity. In one example, the CN120may include an Nx interface, which is an inter-CN interface between the MME (for example, MME121) and the AMF221in order to enable interworking between CN120and CN120. Other example interfaces/reference points may include an N5g-eir service-based interface exhibited by a 5G-EIR, an N27 reference point between NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.

FIG. 3illustrates an example of infrastructure equipment300in accordance with various embodiments. The infrastructure equipment300(or “system300”) may be implemented as a base station, radio head, RAN node, etc., such as the RAN nodes111and112, and/or AP106shown and described previously. In other examples, the system300could be implemented in or by a UE or a core network node/entity, such as those shown and described with regard toFIGS. 1A-2. The system300may include one or more of application circuitry305, baseband circuitry304, one or more radio front end modules315, memory320, power management integrated circuitry (PMIC)325, power tee circuitry330, network controller335, network interface connector340, satellite positioning circuitry345, and user interface350. In some embodiments, the device400may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (for example, said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as “processor circuitry.” As used herein, the term “processor circuitry” may refer to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations; recording, storing, and/or transferring 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.

Application circuitry305may include one or more central processing unit (CPU) cores and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or IO), memory card controllers such as Secure Digital (SD/)MultiMediaCard (MMC) or similar, Universal Serial Bus (USB) interfaces, Mobile Industry Processor Interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports. As examples, the application circuitry305may include one or more Intel Pentium®, Core®, or Xeon® processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s), Accelerated Processing Units (APUs), or Epyc® processors; and/or the like. In some embodiments, the system300may not utilize application circuitry305, and instead may include a special-purpose processor/controller to process IP data received from an EPC or 5GC, for example.

The baseband circuitry304may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. Although not shown, baseband circuitry304may comprise one or more digital baseband systems, which may be coupled via an interconnect subsystem to a CPU subsystem, an audio subsystem, and an interface subsystem. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband sub-system via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed herein. The audio sub-system may include digital signal processing circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components. In an aspect of the present disclosure, baseband circuitry304may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (for example, the radio front end modules315).

The radio front end modules (RFEMs)315may comprise a millimeter wave 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 separated from the millimeter wave RFEM. The RFICs may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module315. The RFEMs315may incorporate both millimeter wave antennas and sub-millimeter wave antennas.

The PMIC325may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor. The power alarm detection circuitry may detect one or more of brown out (under-voltage) and surge (over-voltage) conditions. The power tee circuitry330may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the infrastructure equipment300using a single cable.

The network controller circuitry335may provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to/from the infrastructure equipment300via network interface connector340using a physical connection, which may be electrical (commonly referred to as a “copper interconnect”), optical, or wireless. The network controller circuitry335may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned protocol. In some implementations, the network controller circuitry335may include multiple controllers to provide connectivity to other networks using the same or different protocols.

The positioning circuitry345, which may include circuitry to receive and decode signals transmitted by one or more navigation satellite constellations of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) may include United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (for example, Navigation with Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbitography and Radio-positioning Integrated by Satellite (DORIS), etc.), or the like. The positioning circuitry345may comprise various hardware elements (for example, including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate the communications over-the-air (OTA) communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes.

Nodes or satellites of the navigation satellite constellation(s) (“GNSS nodes”) may provide positioning services by continuously transmitting or broadcasting GNSS signals along a line of sight, which may be used by GNSS receivers (for example, positioning circuitry345and/or positioning circuitry implemented by UEs101,102, or the like) to determine their GNSS position. The GNSS signals may include a pseudorandom code (for example, a sequence of ones and zeros) that is known to the GNSS receiver and a message that includes a time of transmission (ToT) of a code epoch (for example, a defined point in the pseudorandom code sequence) and the GNSS node position at the ToT. The GNSS receivers may monitor/measure the GNSS signals transmitted/broadcasted by a plurality of GNSS nodes (for example, four or more satellites) and solve various equations to determine a corresponding GNSS position (for example, a spatial coordinate). The GNSS receivers also implement clocks that are typically less stable and less precise than the atomic clocks of the GNSS nodes, and the GNSS receivers may use the measured GNSS signals to determine the GNSS receivers' deviation from true time (for example, an offset of the GNSS receiver clock relative to the GNSS node time). In some embodiments, the positioning circuitry345may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance.

The GNSS receivers may measure the time of arrivals (ToAs) of the GNSS signals from the plurality of GNSS nodes according to its own clock. The GNSS receivers may determine ToF values for each received GNSS signal from the ToAs and the ToTs, and then may determine, from the ToFs, a three-dimensional (3D) position and clock deviation. The 3D position may then be converted into a latitude, longitude and altitude. The positioning circuitry345may provide data to application circuitry305which may include one or more of position data or time data. Application circuitry305may use the time data to synchronize operations with other radio base stations (for example, RAN nodes111,112,211or the like).

The components shown byFIG. 3may communicate with one another using interface circuitry. As used herein, the term “interface circuitry” may refer to, is part of, or includes circuitry providing for the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, input/output (I/O) interfaces, peripheral component interfaces, network interface cards, and/or the like. Any suitable bus technology may be used in various implementations, which may include any number of technologies, including 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 may be a proprietary bus, for example, used in a SoC based system. Other bus systems may be included, such as an I2C interface, an SPI interface, point to point interfaces, and a power bus, among others.

FIG. 4illustrates an example of a platform400(or “device400”) in accordance with various embodiments. In embodiments, the computer platform400may be suitable for use as UEs101,102,201, application servers130, and/or any other element/device discussed herein. The platform400may include any combinations of the components shown in the example. The components of platform400may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform400, or as components otherwise incorporated within a chassis of a larger system. The block diagram ofFIG. 4is intended to show a high level view of components of the computer platform400. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

The application circuitry405may include circuitry such as, but not limited to single-core or multi-core processors and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as serial peripheral interface (SPI), inter-integrated circuit (I2C) or universal programmable serial interface circuit, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input-output (IO), memory card controllers such as secure digital/multi-media card (SD/MMC) or similar, universal serial bus (USB) interfaces, mobile industry processor interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports. The processor(s) may include any combination of general-purpose processors and/or dedicated processors (for example, graphics processors, application processors, etc.). The processors (or cores) may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the platform400. In some embodiments, processors of application circuitry305/405may process IP data packets received from an EPC or 5GC.

Application circuitry405be or include a microprocessor, a multi-core processor, a multithreaded processor, an ultra-low voltage processor, an embedded processor, or other known processing element. In one example, the application circuitry405may include an Intel® Architecture Core™ based processor, such as a Quark™, an Atom™, an i3, an i5, an i7, or an MCU-class processor, or another such processor available from Intel® Corporation, Santa Clara, Calif. The processors of the application circuitry405may also be one or more of Advanced Micro Devices (AMD) Ryzen® processor(s) or Accelerated Processing Units (APUs); A5-A9 processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)™ processor(s); a MIPS-based design from MIPS Technologies, Inc; an ARM-based design licensed from ARM Holdings, Ltd.; or the like. In some implementations, the application circuitry405may be a part of a system on a chip (SoC) in which the application circuitry405and other components are formed into a single integrated circuit, or a single package, such as the Edison™ or Galileo™ SoC boards from Intel® Corporation.

The baseband circuitry404may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. Although not shown, baseband circuitry404may comprise one or more digital baseband systems, which may be coupled via an interconnect subsystem to a CPU subsystem, an audio subsystem, and an interface subsystem. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband sub-system via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed herein. The audio sub-system may include digital signal processing circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components. In an aspect of the present disclosure, baseband circuitry404may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (for example, the radio front end modules415).

The radio front end modules (RFEMs)415may comprise a millimeter wave 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 separated from the millimeter wave RFEM. The RFICs may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module415. The RFEMs415may incorporate both millimeter wave antennas and sub-millimeter wave antennas.

The memory circuitry420may include any number and type of memory devices used to provide for a given amount of system memory. As examples, the memory circuitry420may include one or more of volatile memory including be random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SDRAM), and nonvolatile 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 circuitry420may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry320may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA). In low power implementations, the memory circuitry420s storage108may be on-die memory or registers associated with the application circuitry405. To provide for persistent storage of information such as data, applications, operating systems and so forth, memory circuitry420may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others. For example, the computer platform400may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry423may include devices, circuitry, enclosures/housings, ports or receptacles, etc. used to coupled portable data storage devices with the platform400. These portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (for example, Secure Digital (SD) cards, microSD cards, xD picture cards, and the like), and USB flash drives, optical discs, external HDDs, and the like.

The platform400may also include interface circuitry (not shown) that is used to connect external devices with the platform400. The external devices connected to the platform400via the interface circuitry may include sensors421, such as accelerometers, level sensors, flow sensors, temperature sensors, pressure sensors, barometric pressure sensors, and the like. The interface circuitry may be used to connect the platform400to electro-mechanical components (EMCs)422, which may allow platform400to change its state, position, and/or orientation, or move or control a mechanism or system. The EMCs422may include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (for example, valve actuators, etc.), an audible sound generator, a visual warning device, motors (for example, DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components. In embodiments, platform400may be configured to operate one or more EMCs422based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients.

In some implementations, the interface circuitry may connect the platform400with positioning circuitry445, which may be the same or similar as the positioning circuitry445discussed with regard toFIG. 3.

In some implementations, the interface circuitry may connect the platform400with near-field communication (NFC) circuitry440, which may include an NFC controller coupled with an antenna element and a processing device. The NFC circuitry440may be configured to read electronic tags and/or connect with another NFC-enabled device.

The driver circuitry446may include software and hardware elements that operate to control particular devices that are embedded in the platform400, attached to the platform400, or otherwise communicatively coupled with the platform400. The driver circuitry446may include individual drivers allowing other components of the platform400to interact or control various input/output (I/O) devices that may be present within, or connected to, the platform400. For example, driver circuitry446may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform400, sensor drivers to obtain sensor readings of sensors421and control and allow access to sensors421, EMC drivers to obtain actuator positions of the EMCs422and/or control and allow access to the EMCs422, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC)425(also referred to as “power management circuitry425” or the like) may manage power provided to various components of the platform400. In particular, with respect to the baseband circuitry404, the PMIC425may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMIC425may often be included when the platform400is capable of being powered by a battery430, for example, when the device is included in a UE101,102,201.

A battery430may power the platform400, although in some examples the platform400may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery430may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery430may be a typical lead-acid automotive battery.

In some implementations, the battery430may be a “smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry. The BMS may be included in the platform400to track the state of charge (SoCh) of the battery430. The BMS may be used to monitor other parameters of the battery430to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery430. The BMS may communicate the information of the battery430to the application circuitry405or other components of the platform400. The BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry405to directly monitor the voltage of the battery430or the current flow from the battery430. The battery parameters may be used to determine actions that the platform400may perform, such as transmission frequency, network operation, sensing frequency, and the like.

A power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery430. In some examples, the power block128may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform400. In these examples, a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery430, and thus, the current required. The charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard, promulgated by the Alliance for Wireless Power, among others.

Although not shown, the components of platform400may communicate with one another using a suitable bus technology, which may include any number of technologies, including industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), a Time-Trigger Protocol (TTP) system, or a FlexRay system, or any number of other technologies. The bus may be a proprietary bus, for example, used in a SoC based system. Other bus systems may be included, such as an I2C interface, an SPI interface, point to point interfaces, and a power bus, among others.

FIG. 5illustrates example components of baseband circuitry304/404and radio front end modules (RFEM)315/415in accordance with some embodiments. As shown, the RFEM315/415may include Radio Frequency (RF) circuitry506, front-end module (FEM) circuitry508, one or more antennas510coupled together at least as shown.

The baseband circuitry304/404may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry304/404may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry506and to generate baseband signals for a transmit signal path of the RF circuitry506. Baseband processing circuity304/404may interface with the application circuitry305/405for generation and processing of the baseband signals and for controlling operations of the RF circuitry506. For example, in some embodiments, the baseband circuitry304/404may include a third generation (3G) baseband processor504A, a fourth generation (4G) baseband processor504B, a fifth generation (5G) baseband processor504C, or other baseband processor(s)504D for other existing generations, generations in development or to be developed in the future (for example, second generation (2G), si5h generation (6G), etc.). The baseband circuitry304/404(for example, one or more of baseband processors504A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry506. In other embodiments, some or all of the functionality of baseband processors504A-D may be included in modules stored in the memory504G and executed via a Central Processing Unit (CPU)504E. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry304/404may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry304/404may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry304/404may include one or more audio digital signal processor(s) (DSP)504F. The audio DSP(s)504F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry304/404and the application circuitry305/405may be implemented together such as, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry304/404may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry304/404may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry304/404is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry506may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry506may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry506may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry508and provide baseband signals to the baseband circuitry304/404. RF circuitry506may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry304/404and provide RF output signals to the FEM circuitry508for transmission.

In some embodiments, the receive signal path of the RF circuitry506may include mixer circuitry506a, amplifier circuitry506band filter circuitry506c. In some embodiments, the transmit signal path of the RF circuitry506may include filter circuitry506cand mixer circuitry506a. RF circuitry506may also include synthesizer circuitry506dfor synthesizing a frequency for use by the mixer circuitry506aof the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry506aof the receive signal path may be configured to down-convert RF signals received from the FEM circuitry508based on the synthesized frequency provided by synthesizer circuitry506d. The amplifier circuitry506bmay be configured to amplify the down-converted signals and the filter circuitry506cmay be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry304/404for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry506aof the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry506aof the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry506dto generate RF output signals for the FEM circuitry508. The baseband signals may be provided by the baseband circuitry304/404and may be filtered by filter circuitry506c.

The synthesizer circuitry506dmay be configured to synthesize an output frequency for use by the mixer circuitry506aof the RF circuitry506based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry506dmay be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry304/404or the applications processor305/405depending on the desired output frequency. In some embodiments, a divider control input (for example, N) may be determined from a look-up table based on a channel indicated by the applications processor305/405.

FEM circuitry508may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas510, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry506for further processing. FEM circuitry508may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry506for transmission by one or more of the one or more antennas510. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry506, solely in the FEM508, or in both the RF circuitry506and the FEM508.

FIG. 6illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry304/404ofFIGS. 3-4may comprise processors504A-504E and a memory504G utilized by said processors. Each of the processors504A-504E may include a memory interface,604A-604E, respectively, to send/receive data to/from the memory504G.

The baseband circuitry304/404may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface612(for example, an interface to send/receive data to/from memory external to the baseband circuitry304/404), an application circuitry interface614(for example, an interface to send/receive data to/from the application circuitry305/405ofFIGS. 3-4), an RF circuitry interface616(for example, an interface to send/receive data to/from RF circuitry506ofFIG. 5), a wireless hardware connectivity interface618(for example, an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (for example, Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface620(for example, an interface to send/receive power or control signals to/from the PMIC425.

FIG. 7is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (for example, a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically,FIG. 7shows a diagrammatic representation of hardware resources700including one or more processors (or processor cores)710, one or more memory/storage devices720, and one or more communication resources730, each of which may be communicatively coupled via a bus740. As used herein, the term “computing resource”, “hardware resource”, etc., may refer to a physical or virtual device, a physical or virtual component within a computing environment, and/or physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time and/or processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, and/or the like. For embodiments where node virtualization (for example, NFV) is utilized, a hypervisor702may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources700. A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.

The memory/storage devices720may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices720may include, but are 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.

The communication resources730may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices704or one or more databases706via a network708. For example, the communication resources730may include wired communication components (for example, for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (for example, Bluetooth® Low Energy), Wi-Fi® components, and other communication components. As used herein, the term “network resource” or “communication resource” may refer to computing resources that are accessible by computer devices via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as 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.

Instructions750may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors710to perform any one or more of the methodologies discussed herein. The instructions750may reside, completely or partially, within at least one of the processors710(for example, within the processor's cache memory), the memory/storage devices720, or any suitable combination thereof. Furthermore, any portion of the instructions750may be transferred to the hardware resources700from any combination of the peripheral devices704or the databases706. Accordingly, the memory of processors710, the memory/storage devices720, the peripheral devices704, and the databases706are examples of computer-readable and machine-readable media.

FIGS. 8-9illustrate processes800-900, respectively, for handling multiple UL grants on configured LAA SCells indicating different PUSCH starting positions, according to various embodiments. For illustrative purposes, the operations of processes800-900are described as being performed by a UE101with a RAN node111, and/or various components discussed with regard toFIGS. 4-6. However, process800-900may be performed by various other devices discussed with regard toFIGS. 1A-7. Moreover, while particular examples and orders of operations are illustrated inFIGS. 8-9, the depicted orders of operations should not be construed to limit the scope of the embodiments in any way. Rather, the depicted operations may be re-ordered, broken into additional operations, combined, and/or omitted altogether while remaining within the spirit and scope of the present disclosure.

FIG. 8shows an example procedure800for handling multiple UL grants on configured LAA SCells indicating different PUSCH starting positions. Procedure800may begin at operation805where communications circuitry of UE101(for example, RFEM415ofFIGS. 4-5, RF circuitry506ofFIG. 5, or the like) may receive Downlink Control Information (DCI) of one or more Licensed Assisted Access (LAA) Secondary Cells (SCells). In embodiments, processor circuitry of the UE101(for example, baseband circuitry404ofFIGS. 4-5) may monitor a control region of a primary serving cell (PCell), where the control region comprises a set of Control Channel Elements (CCEs) or enhanced CCEs (ECCEs) of a PDCCH or EPDCCH, respectively. In embodiment, the CCEs/ECCEs may be referred to as PDCCH candidate or EPDCCH candidates, and the processor circuitry may monitor a set of (E)PDCCH candidates for the DCI on a PCell operating in a licensed spectrum as configured by higher layer signaling. The term “monitoring,” as used herein, may imply attempting by the processor circuitry of the UE101to decode each of the (E)PDCCH candidates according to various DCI formats. In embodiments, the DCI may be transmitted by the RAN node111according to a selected one of DCI format 0A, 0B, 4A, or 4B.

At operation810, the processor circuitry of the UE101may identify uplink (UL) grants and starting positions for transmitting over the LAA SCells. In embodiments, the processor circuitry may identify the starting positions based on a value of the Physical Uplink Shared Channel (PUSCH) starting position field in the DCI, which is discussed previously with regard to table 1. The possible PUSCH starting positions may include symbol0, 25 μs in symbol0, (25+a timing advance (TA))μs in symbol0, and symbol1.

At operation815, the processor circuitry of the UE101may determine whether more than one UL grant is indicated within a same subframe. If at operation815the processor circuitry determines that more than one UL grant are not indicated within a same subframe, then the processor circuitry may proceed to operation818to perform a listen-before-talk (LBT) operation at the indicated starting position and may then proceed to operation830to control the communication circuitry of the UE101to transmit the UL transmission when the channel is detected to be idle.

If at operation815the processor circuitry determines that more than one UL grant are indicated within a same subframe, then the processor circuitry may proceed to operation820align the multiple indicated starting positions. According to various embodiments, the UE101is not expected to receive UL grants on LAA SCells indicating different PUSCH starting positions in the same subframe. However, handling of UL grants indicating different PUSCH starting positions in the same subframe may be up to UE101implementation since full duplex capability is not mandated.

According to first embodiments, the processor circuitry may align the PUSCH starting positions to an earliest starting position among the indicated PUSCH starting positions for handling UL grants indicating different PUSCH starting positions in the same subframe. According to second embodiments, the processor circuitry may align the PUSCH starting positions to a latest starting position among the indicated PUSCH starting positions. In the first and second embodiments, the processor circuitry of the UE101may align the starting positions by adjusting the UL transmission timing for the PUSCH using a timing advance (TA). The TA may be a fixed timing offset or a timing offset between UL and DL radio frames, subframes, or symbols at the UE101. In some first embodiments, the processor circuitry of the UE101may align each UL transmission to be spaced apart by the TA starting from the earliest starting position among the indicated PUSCH starting positions. In some second embodiments, the processor circuitry of the UE101may align each UL transmission to be spaced apart by the TA starting from the latest starting position among the indicated PUSCH starting positions. For example, if the TA is 25 μs, the processor circuitry of the UE101may align each UL transmission to be 25 μs apart from one another beginning at the earliest indicated starting position or the latest indicated starting position. In various embodiments, the TA may be predefined or preconfigured at the UE101, and in other embodiments, the TA may be signaled to the UE101using higher layer signaling (for example, using a suitable RRC message). Other mechanisms for aligning the starting positions may be used in other embodiments.

After aligning the starting positions at operation820, the processor circuitry of the UE101may proceed to operation825to perform an LBT operation at the aligned starting position, and may then proceed to operation830to control the communication circuitry of the UE101to transmit the UL transmission when the channel is detected to be idle. After performance of operation818or operation830, process800may end or repeat as necessary.

FIG. 9shows another example procedure900for handling multiple UL grants on configured LAA SCells indicating different PUSCH starting positions. Procedure900may begin at operation905where communications circuitry of UE101(for example, RFEM415ofFIGS. 4-5, RF circuitry506ofFIG. 5, or the like) may receive DCI of one or more LAA SCells. At operation910, the processor circuitry of the UE101may identify UL grants and starting positions for transmitting over the LAA SCells. At operation915, the processor circuitry of the UE101may determine whether more than one UL grant is indicated within a same subframe. If at operation915the processor circuitry determines that more than one UL grant are not indicated within a same subframe, then the processor circuitry may proceed to operation918to perform a listen-before-talk (LBT) operation at the indicated starting position and may then proceed to operation930to control the communication circuitry of the UE101to transmit the UL transmission when the channel is detected to be idle. Operations905,910,915, and918may be performed in a same or similar manner as discussed previously with regard to operations805,810,815, and818ofFIG. 8.

If at operation915the processor circuitry determines that more than one UL grant are indicated within a same subframe, then the processor circuitry may proceed to operation920identify an earliest indicated starting position. At operation925, the processor circuitry of the UE101may control the communication circuitry to perform an LBT operation at the earliest identified starting position.

At operation930, the processor circuitry may determine whether the LBT operation failed, or whether the sensed channel was determined not to be idle or unoccupied. If at operation930the processor circuitry determines that the LBT operation has not failed, the processor circuitry may proceed to operation940to control the communication circuitry to transmit the UL transmission on the unoccupied channel at the earliest starting position.

If at operation930the processor circuitry determines that the LBT operation has failed or determines that the channel is occupied, the processor circuitry may proceed to operation935to perform an LBT at a next earliest identified starting position of the indicated starting positions. After performance of operation935, the processor circuitry may proceed back to operation930to determine whether the LBT operation at the next earliest identified starting position has failed or not, and may then operate as discussed previously. After performance of operation918and/or operation940, process900may end or repeat as necessary.

Some non-limiting examples are provided infra. The following examples pertain to further embodiments. Specifics in the examples may be used anywhere in one or more embodiments discussed previously. All optional features of devices described herein may also be implemented with respect to one or more methods or processes, and vice versa.

Example 1 may include one or more computer-readable storage media (CRSM) including instructions, wherein execution of the instructions by one or more processors of a user equipment (UE) is to cause the UE to: control receipt of Downlink Control Information (DCI) wherein the DCI is to indicate at least two uplink grants for one or more licensed assisted access (LAA) secondary cells (SCells) wherein each of the at least two uplink grants indicate different starting positions for Physical Uplink Shared Channel (PUSCH) transmissions within a same subframe; and align the different starting positions to provide for the UE to transmit uplink transmissions according to the at least two uplink grants while the UE is in a transmission mode.

Example 2 may include the one or more CRSM of example 1 and/or some other examples herein, wherein execution of the instructions is to cause the UE to align the different starting positions to an earliest starting position among the indicated starting positions.

Example 3 may include the one or more CRSM of example 1 and/or some other examples herein, wherein execution of the instructions is to cause the UE to align the different starting positions to a latest starting position among the indicated starting positions.

Example 4 may include the one or more CRSM of examples 1-3 and/or some other examples herein, wherein execution of the instructions is to cause the UE to control performance of a listen-before-talk (LBT) operation at the aligned starting positions prior to transmission of the PUSCH transmissions.

Example 5 may include the one or more CRSM of example 1 and/or some other examples herein, wherein execution of the instructions is to cause the UE to: identify an earliest starting position among the indicated starting positions; control performance of an LBT operation at the earliest starting position; and control non-performance of an LBT operation at other starting positions among the indicated starting positions.

Example 6 may include the one or more CRSM of example 5 and/or some other examples herein, wherein execution of the instructions is to cause the UE to control performance of an LBT operation at each indicated starting position, in turn, when the LBT operated performed at the earliest starting position is determined to have failed.

Example 7 may include the one or more CRSM of example 1 and/or some other examples herein, wherein the UE is not capable of simultaneous reception and transmission.

Example 8 may include the one or more CRSM of example 7 and/or some other examples herein, wherein the subframe is part of a Frame Structure type 2 (FS2) radio frame or part of a Frame Structure type 3 (FS3) radio frame.

Example 9 may include the one or more CRSM of examples 1-8 and/or some other examples herein, wherein the DCI is a DCI format 0A message, a DCI format 0B message, a DCI format 4A message, or a DCI format 4B message.

Example 10 may include the one or more CRSM of example 9 and/or some other examples herein, wherein the DCI comprises individual two bit PUSCH starting position fields for each indicated starting position, wherein the individual two bit PUSCH starting position fields are to include: a value of “00” to indicate a starting position of symbol0; a value of “01” to indicate a starting position of 25 microseconds (us) in symbol0; a value of “10” to indicate a starting position of 25 μs plus a timing advance (TA) in symbol0; or a value of “11” to indicate a starting position of symbol1.

Example 11 may include a system on chip (SoC) to be implemented in a user equipment (UE) the SoC comprising: baseband circuitry and memory circuitry, the baseband circuitry to: control receipt of Downlink Control Information (DCI) wherein the DCI is to indicate at least two uplink grants for one or more licensed assisted access (LAA) secondary cells (SCells) wherein each of the at least two uplink grants indicate different starting positions for Physical Uplink Shared Channel (PUSCH) transmissions within a same subframe; control storage of each of the at least two uplink grants in the memory circuitry; and align the different starting positions to provide for the UE to transmit uplink transmissions according to the at least two uplink grants while the UE is in a transmission mode.

Example 12 may include the SoC of example 11 and/or some other examples herein, wherein, to align the different starting positions, the baseband circuitry is to: align the different starting positions to an earliest starting position among the indicated starting positions. Example 13 may include the SoC of example 11 and/or some other examples herein, wherein, to align the different starting positions, the baseband circuitry is to: align the different starting positions to a latest starting position among the indicated starting positions.

Example 14 may include the SoC of examples 11-13 and/or some other examples herein, wherein the baseband circuitry is to: perform a listen-before-talk (LBT) operation at the aligned starting positions prior to transmission of the PUSCH transmissions.

Example 15 may include the SoC of example 11 and/or some other examples herein, wherein, to align the different starting positions, the baseband circuitry is to: identify an earliest starting position among the indicated starting positions; control performance of an LBT operation at the earliest starting position; and not perform an LBT operation at other starting positions among the indicated starting positions.

Example 16 may include the SoC of example 15 and/or some other examples herein, wherein the baseband circuitry is to: control performance of LBT operation at each indicated starting position, in turn, when the LBT performed at the earliest starting position is determined to have failed.

Example 17 may include the SoC of example 11 and/or some other examples herein, wherein the UE is not capable of simultaneous reception and transmission, and wherein the subframe is part of a Frame Structure type 2 (FS2) radio frame or part of a Frame Structure type 3 (FS3) radio frame.

Example 18 may include the SoC of examples 11-17 and/or some other examples herein, wherein the DCI is a DCI format 0A message, a DCI format 0B message, a DCI format 4A message, or a DCI format 4B message, and wherein the DCI comprises individual two bit PUSCH starting position fields for each indicated starting position, wherein the individual two bit PUSCH starting position fields are to include: a value of “00” to indicate a starting position of symbol0; a value of “01” to indicate a starting position of 25 microseconds (μs) in symbol0; a value of “10” to indicate a starting position of 25 μs plus a timing advance (TA) in symbol0; or a value of “11” to indicate a starting position of symbol1.

Example 19 may include an apparatus to be employed as a user equipment (UE) the apparatus comprising: communication means for receiving Downlink Control Information (DCI) wherein the DCI is to indicate at least two uplink grants for one or more licensed assisted access (LAA) secondary cells (SCells) wherein each of the at least two uplink grants indicate different starting positions for Physical Uplink Shared Channel (PUSCH) transmissions within a same subframe; and processing means for: performing a decode attempt on a set of Physical Downlink Control Channel (PDCCH) candidates or a set of enhanced PDCCH (EPDCCH) candidates to obtain the DCI, and aligning the different starting positions to provide for the UE to transmit uplink transmissions according to the at least two uplink grants while the UE is in a transmission mode.

Example 20 may include the apparatus of example 19 and/or some other examples herein, wherein the processing means is for aligning the different starting positions to an earliest starting position among the indicated starting positions or align the different starting positions to a latest starting position among the indicated starting positions.

Example 21 may include the apparatus of examples 19-20 and/or some other examples herein, wherein the communication means is for performing a listen-before-talk (LBT) operation at the aligned starting positions prior to transmission of the PUSCH transmissions.

Example 22 may include the apparatus of example 19 and/or some other examples herein, wherein the processing means is for identifying an earliest starting position among the indicated starting positions, and the communication means is for performing an LBT operation at the earliest starting position; and for not performing an LBT operation at other starting positions among the indicated starting positions.

Example 23 may include the apparatus of example 22 and/or some other examples herein, wherein the communication means is for performing an LBT operation at each indicated starting position, in turn, when the LBT operated performed at the earliest starting position is determined to have failed.

Example 24 may include the apparatus of example 19 and/or some other examples herein, wherein the UE is not capable of simultaneous reception and transmission, and wherein the subframe is part of a Frame Structure type 2 (FS2) radio frame or part of a Frame Structure type 3 (FS3) radio frame.

Example 25 may include the apparatus of examples 19-24 and/or some other examples herein, wherein the DCI is a DCI format 0A message, a DCI format 0B message, a DCI format 4A message, or a DCI format 4B message, and wherein the DCI comprises individual two bit PUSCH starting position fields for each indicated starting position, wherein the individual two bit PUSCH starting position fields are to include: a value of “00” to indicate a starting position of symbol0; a value of “01” to indicate a starting position of 25 microseconds (us) in symbol0; a value of “10” to indicate a starting position of 25 μs plus a timing advance (TA) in symbol0; or a value of “11” to indicate a starting position of symbol1.

Example 26 may include an apparatus to be employed as a user equipment (UE) the apparatus comprising: communication circuitry to receive Downlink Control Information (DCI) wherein the DCI is to indicate at least two uplink grants for one or more licensed assisted access (LAA) secondary cells (SCells) wherein each of the at least two uplink grants indicate different starting positions for Physical Uplink Shared Channel (PUSCH) transmissions within a same subframe; and processor circuitry communicatively coupled with the communication circuitry, the processor circuitry is to: perform a decode attempt on a set of Physical Downlink Control Channel (PDCCH) candidates or a set of enhanced PDCCH (EPDCCH) candidates to obtain the DCI, and align the different starting positions to provide for the UE to transmit uplink transmissions according to the at least two uplink grants while the UE is in a transmission mode.

Example 27 may include the apparatus of example 26 and/or some other examples herein, wherein the processor circuitry is to align the different starting positions to an earliest starting position among the indicated starting positions or align the different starting positions to a latest starting position among the indicated starting positions.

Example 28 may include the apparatus of examples 26-27 and/or some other examples herein, wherein the communication circuitry is to perform a listen-before-talk (LBT) operation at the aligned starting positions prior to transmission of the PUSCH transmissions.

Example 29 may include the apparatus of example 26 and/or some other examples herein, wherein: the processor circuitry is to identify an earliest starting position among the indicated starting positions, and the communication circuitry is to perform an LBT operation at the earliest starting position; and for not performing an LBT operation at other starting positions among the indicated starting positions.

Example 30 may include the apparatus of example 29 and/or some other examples herein, wherein the processor circuitry is to control the communication circuitry to perform an LBT operation at each indicated starting position, in turn, when the LBT operated performed at the earliest starting position is determined to have failed.

Example 31 may include the apparatus of example 26 and/or some other examples herein, wherein the UE is not capable of simultaneous reception and transmission, and wherein the subframe is part of a Frame Structure type 2 (FS2) radio frame or part of a Frame Structure type 3 (FS3) radio frame.

Example 32 may include the apparatus of examples 26-31 and/or some other examples herein, wherein the DCI is a DCI format 0A message, a DCI format 0B message, a DCI format 4A message, or a DCI format 4B message, and wherein the DCI comprises individual two bit PUSCH starting position fields for each indicated starting position, wherein the individual two bit PUSCH starting position fields are to include: a value of “00” to indicate a starting position of symbol0; a value of “01” to indicate a starting position of 25 microseconds (μs) in symbol0; a value of “10” to indicate a starting position of 25 μs plus a timing advance (TA) in symbol0; or a value of “11” to indicate a starting position of symbol1.

Example 33 may include an apparatus to be employed as a user equipment (UE) the apparatus comprising: communication means for receiving Downlink Control Information (DCI) wherein the DCI is to indicate at least two uplink grants for one or more licensed assisted access (LAA) secondary cells (SCells) wherein each of the at least two uplink grants indicate different starting positions for Physical Uplink Shared Channel (PUSCH) transmissions within a same subframe; and alignment means for aligning the different starting positions to provide for the UE to transmit uplink transmissions according to the at least two uplink grants while the UE is in a transmission mode.

Example 34 may include the apparatus of example 33 and/or some other examples herein, wherein the alignment means is for aligning the different starting positions to an earliest starting position among the indicated starting positions.

Example 35 may include the apparatus of example 33 and/or some other examples herein, wherein the alignment means is for aligning the different starting positions to a latest starting position among the indicated starting positions.

Example 36 may include the apparatus of examples 33-35 and/or some other examples herein, wherein the communication means is for performing a listen-before-talk (LBT) operation at the aligned starting positions prior to transmission of the PUSCH transmissions.

Example 37 may include the apparatus of example 33 and/or some other examples herein, further comprising: identification means for identifying an earliest starting position among the indicated starting positions, and wherein the communication means is for: performing an LBT operation at the earliest starting position; and not performing an LBT operation at other starting positions among the indicated starting positions.

Example 38 may include the apparatus of example 37 and/or some other examples herein, wherein the communication means is for performing an LBT operation at each indicated starting position, in turn, when the LBT operated performed at the earliest starting position is determined to have failed.

Example 39 may include the apparatus of example 33 and/or some other examples herein, wherein the UE is not capable of simultaneous reception and transmission, and wherein the subframe is part of a Frame Structure type 2 (FS2) radio frame or part of a Frame Structure type 3 (FS3) radio frame.

Example 40 may include the apparatus of examples 33-39 and/or some other examples herein, wherein the DCI is a DCI format 0A message, a DCI format 0B message, a DCI format 4A message, or a DCI format 4B message, wherein the DCI comprises individual two bit PUSCH starting position fields for each indicated starting position, wherein the individual two bit PUSCH starting position fields are to include: a value of “00” to indicate a starting position of symbol0; a value of “01” to indicate a starting position of 25 microseconds (us) in symbol0; a value of “10” to indicate a starting position of 25 μs plus a timing advance (TA) in symbol0; or a value of “11” to indicate a starting position of symbol1.

Example 41 may include a method comprising: receiving or causing to receive Downlink Control Information (DCI) wherein the DCI is to indicate at least two uplink grants for one or more licensed assisted access (LAA) secondary cells (SCells) wherein each of the at least two uplink grants indicate different starting positions for Physical Uplink Shared Channel (PUSCH) transmissions within a same subframe; and aligning or causing to align the different starting positions to provide for the UE to transmit uplink transmissions according to the at least two uplink grants while the UE is in a transmission mode.

Example 42 may include the method of example 41 and/or some other examples herein, further comprising: aligning or causing to align the different starting positions to an earliest starting position among the indicated starting positions.

Example 43 may include the method of example 41 and/or some other examples herein, further comprising: aligning or causing to the different starting positions to a latest starting position among the indicated starting positions.

Example 44 may include the method of examples 41-43 and/or some other examples herein, further comprising: performing or causing to perform a listen-before-talk (LBT) operation at the aligned starting positions prior to transmission of the PUSCH transmissions.

Example 45 may include the method of example 41 and/or some other examples herein, further comprising: identifying or causing to identify an earliest starting position among the indicated starting positions; performing or causing to perform an LBT operation at the earliest starting position; and not performing or causing to not perform an LBT operation at other starting positions among the indicated starting positions.

Example 46 may include the method of example 45 and/or some other examples herein, further comprising: performing or causing to perform an LBT operation at each indicated starting position, in turn, when the LBT operated performed at the earliest starting position is determined to have failed.

Example 47 may include the method of example 41 and/or some other examples herein, wherein the UE is not capable of simultaneous reception and transmission.

Example 48 may include the method of example 47 and/or some other examples herein, wherein the subframe is part of a Frame Structure type 2 (FS2) radio frame or part of a Frame Structure type 3 (FS3) radio frame.

Example 49 may include the method of examples 41-48 and/or some other examples herein, wherein the DCI is a DCI format 0A message, a DCI format 0B message, a DCI format 4A message, or a DCI format 4B message.

Example 50 may include the method of example 49 and/or some other examples herein, wherein the DCI comprises individual two bit PUSCH starting position fields for each indicated starting position, wherein the individual two bit PUSCH starting position fields are to include: a value of “00” to indicate a starting position of symbol0; a value of “01” to indicate a starting position of 25 microseconds (μs) in symbol0; a value of “10” to indicate a starting position of 25 μs plus a timing advance (TA) in symbol0; or a value of “11” to indicate a starting position of symbol1.

Example 51 may include may include the method of examples 41-50 and/or some other examples herein, further comprising: storing or causing to store each of the at least two uplink grants in the memory circuitry.

Example 52 may include may include the method of examples 41-51 and/or some other examples herein, further comprising: performing or causing to perform a decode attempt on a set of Physical Downlink Control Channel (PDCCH) candidates or a set of enhanced PDCCH (EPDCCH) candidates to obtain the DCI.

Example 53 may include may include the method of examples 44-52 and/or some other examples herein, wherein the LBT operation comprises: sensing or causing to sense a radiofrequency energy of a transmission band for a period of time; and determining whether the radiofrequency energy is greater than or equal to a threshold value.

Example 54 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-53, or any other method or process described herein.

Example 56 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-53, or any other method or process described herein.

Example 57 may include a method, technique, or process as described in or related to any of examples 1-53, or portions or parts thereof.

Example 58 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-53, or portions thereof.

Example 59 may include a signal as described in or related to any of examples 1-53, or portions or parts thereof.

Example 60 may include a signal in a wireless network as shown and described herein. Example 61 may include a method of communicating in a wireless network as shown and described herein. Example 62 may include a system for providing wireless communication as shown and described herein. Example 63 may include a device for providing wireless communication as shown and described herein.

The foregoing description of the above examples provides illustration and description for the example embodiments disclosed herein, but the above examples are not intended to be exhaustive or to limit the scope of the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings and/or may be acquired from practice of various implementations of the embodiments discussed herein.