Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L27/00—Modulated-carrier systems
  • H04L27/26—Systems using multi-frequency codes
  • H04L27/2601—Multicarrier modulation systems
  • H04L27/2602—Signal structure
• • H—ELECTRICITY
  • H03—ELECTRONIC CIRCUITRY
  • H03G—CONTROL OF AMPLIFICATION
  • H03G3/00—Gain control in amplifiers or frequency changers
  • H03G3/20—Automatic control
  • H03G3/30—Automatic control in amplifiers having semiconductor devices
  • H03G3/3036—Automatic control in amplifiers having semiconductor devices in high-frequency amplifiers or in frequency-changers
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L27/00—Modulated-carrier systems
  • H04L27/26—Systems using multi-frequency codes
  • H04L27/2601—Multicarrier modulation systems
  • H04L27/2602—Signal structure
  • H04L27/2605—Symbol extensions, e.g. Zero Tail, Unique Word [UW]
  • H04L27/2607—Cyclic extensions
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L27/00—Modulated-carrier systems
  • H04L27/26—Systems using multi-frequency codes
  • H04L27/2601—Multicarrier modulation systems
  • H04L27/2602—Signal structure
  • H04L27/261—Details of reference signals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/0001—Arrangements for dividing the transmission path
  • H04L5/0003—Two-dimensional division
  • H04L5/0005—Time-frequency
  • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/003—Arrangements for allocating sub-channels of the transmission path
  • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/003—Arrangements for allocating sub-channels of the transmission path
  • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/14—Two-way operation using the same type of signal, i.e. duplex

Definitions

• embodiments described herein are directed to the management of transmit/receive (TX/RX) switching gaps and automatic gain control (AGC) adaptation.
• Embodiments of the present disclosure may be used in conjunction with new radio (NR) vehicle- to-every thing (V2X) systems.
• NR new radio
• V2X vehicle- to-every thing
• FIGS 1 and 2, and 3 illustrate examples of operation flow/algorithmic structures in accordance with some embodiments.
• FIG. 4A illustrates an example of time resource allocation in accordance with some embodiments
• Figure 4B illustrates an example of different options for slot format optimization in accordance with some embodiments.
• FIG. 4C illustrates examples of different demodulation reference signal (DMRS) patterns in accordance with some embodiments.
• DMRS demodulation reference signal
• Figure 4D illustrates performance comparisons of rank 1 transmissions with NR type 1 orthogonal frequency division multiplexing (OFDM) DMRS.
• OFDM orthogonal frequency division multiplexing
• Figure 5 depicts an architecture of a system of a network in accordance with some embodiments.
• Figure 6 depicts an example of components of a device in accordance with some embodiments.
• Figure 7 depicts an example of interfaces of baseband circuitry in accordance with some embodiments.
• Figure 8 depicts a block diagram illustrating components, according to some embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
• a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
• Embodiments discussed herein may relate to the management of transmit/receive (TX/RX) switching gaps and automatic gain control (AGC) adaptation for new radio (NR) systems. Other embodiments may be described and/or claimed.
• TX/RX transmit/receive
• AGC automatic gain control
• the phrase“in various embodiments,”“in some embodiments,” and the like may refer to the same, or different, embodiments.
• 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.”
• the phrase“at least one of A and B” means (A), (B), or (A and B).
• Examples of 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.
• Examples of 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.
• Device-to-device transmissions such as the SL (sidelink) of new radio-vehicle-to- every thing (NR-V2X), may be inherently different to the DL (downlink) or UL (uplink), in the sense that different devices may transmit in the same slots.
• the uplink there will be in many cases no power-control and time advance. Therefore, the AGC (Automatic Gain Control) needs to adapt to the current receive power level at the start of each slot. Due to the NR-V2X SL requirement of a maximum range of 1 km, the difference in power of the received signal from different transmitters in each slot can be rather large.
• This adaptation of the AGC to this power difference needs to be foreseen in the design of the symbol structure within a slot, because the different transmitting devices cannot be fully synchronized to unified timing (ad hoc network) and there is possibly a large propagation delay between the signals from different users. There is also a need to have a guard time interval without any additional transmissions separating consecutive slots (or set of slots) to enable the devices to switch from transmission to reception mode or vice versa. This time without transmission also needs to account for the maximum transmission distance and the possible timing synchronization error of the devices as otherwise there would be interference from the previous slot.
• the TX/RX switching gap should be at most 13 us and the AGC adaptation may be performed within 15 us for the case of carrier frequencies below 6 GHz.
• Previous solutions are in line with the design of LTE V2X, where the first orthogonal frequency division multiplexing (OFDM) symbol of a slot would be used for the adaptation of the AGC and the last OFDM symbol would be left without transmission.
• OFDM orthogonal frequency division multiplexing
• embodiments of the present disclosure can provide one symbol could account for both these functionalities, and may result in a decrease overhead from 14% to 7%, which can significantly improve the available resources for data transmission (for the case of 30 kHz subcarrier spacing).
• TX/RX switching occasions occurring at the slot boundaries are shown.
• TX/RX switching options may include a transmit-to- receive switching operation or a receive-to-transmit switching operation.
• the TX/RX switching occasions could potentially happen in any part of the spectrum.
• the version in a) illustrates the same behavior as in LTE V2X. As we can see if one OFDM symbol is already sufficient to cover both the TX/RX switching as well as the AGC adaptation this is basically an unnecessary waste of resources.
• the cases b) to d) it is illustrated how the parts of a symbol can be distributed in the case that the time of half of an OFDM symbol is enough accommodate each of the functionalities. It is also possible that one third of an OFDM symbol possible distribution of resource are illustrated in e) to h). It is possible to extend that even further and the design should follow the same principal as the TX/RX switching gap also needs to be directly before the AGC adaptation part of symbol.
• These signals could be derived from different reference sequences like gold sequences or Zadoff-Chu sequences.
• the main purpose is to adapt to the power of the transmission, therefore they need to be transmitted with the same power as the following data or control channel by the same devices.
• the normal CP (cyclic prefix) of 2.34 microseconds (us) duration may not be enough to accommodate all possible operating conditions for a system utilizing 30 kHz as SCS (Sub- Carrier Spacing), for example. Therefore, an extended cyclic prefix may be used or supported. However, this would lead to a CP duration of 8.33 us. For a practical system, a CP duration of approximately 4.0 us should be enough to cover propagation distance up to 1.2 km and, therefore, a solution with an extended CP and 30 kHz SCS would incur on a large overhead.
• the optimized slot structures presented in this disclosure help address these and other issues.
• DMRSs NR demodulation reference signals
• the system would also benefit from an optimized DMRS pattern as described for some embodiments of the present disclosure.
• the previous solution relied only on enabling longer CP duration. For example, a longer or extended CP for 30 kHz SCS in the SL was proposed in a similar way it is already allowed for 60 kHz SCS in NR DL and UL. With an extended CP, however, its duration would be 8.33 us, for example. This is about twice the duration actually necessary for NR-V2X SL requirements and makes it inefficient in terms of overhead.
• Described herein are different options for the slot structure that are optimized to satisfy additional constraints and requirements of the NR-V2X SL in, for example, Rel. 16 (relative to Rel. 15 NR-DL and UL).
• the slot structures may also be applicable for the case of shared UL and SL in a licensed band. Therefore, the slot length of UL and DL transmissions may be kept the same.
• a device may be in a longer period of intermittent transmission of multiple slots and not interested/required to receive data during the intervals it is not transmitting.
• slot format optimization in accordance with embodiments of this disclosure may be applicable to a variety of different configurations of an NR-V2X SL system. These are examples that keep the duration of a slot constant. This is necessary to enable a seamless replacement of NR slots in the case NR-V2X SL is operating in combination with UL and DL in the licensed band. Thus the examples are designed for this case, but in principle these techniques can be used to design any frame structure with the specific requirements of V2X.
• Figure 4B illustrates some exemplary combinations of the listed techniques. From top to bottom the following bullet points describe the properties of these solutions.
• Option 1 In this option there are 12 OFDM symbols in a slot and the CP has slightly shorter duration than the extended CP. In addition, there is a time reserved for Tx/Rx switching at the end of the slot. This structure is optimal, if the AGC can be adapted/settled during the CP interval of the first OFDM symbol. As there are also 12 OFDM symbols like in the case of extended CP, the relative CP shortening is the time interval reserved for Tx/Rx switching divided by 12. This format can also be used for the last slot in a multi-slot transmission as there is no dedicated AGC adaptation time.
• Option 2 In this option, there are 13 OFDM symbols in a slot. Thus, compared to Option 1, the CP duration is shorter and is roughly half way between an extended CP and the normal CP of Rel. 15 NR.
• Option 3 There are also 12 OFDM symbols, but in contrast to Option 1, there is some time at the start of the first symbol in the slot reserved for the adaptation of the AGC. During this time, for example, synchronization reference symbols could be transmitted. Depending on the duration of the AGC settling and of the Tx/Rx switching, the resulting CP duration is in between the normal and the extended CP. If the two guard intervals are very short and the requirements on the CP duration not high, it might be an option to use 13 OFDM symbols.
• Option 6 In this case, the Tx/Rx switching time and the AGC adaptation are at the start of a slot. In addition, depending on the CP duration requirement more or less OFDM symbols could be used in the rest of the slot.
• Option 7 This option is similar to Option 6, but for this case the Tx/Rx switching and the AGC adaptation are at the end of a slot.
• the extended CP designed using the same rule as for 60 kHz in NR would last 256 k for all 12 OFDM symbols in a slot.
• the first (or the last) symbol of a slot with new extended CP may be of duration different to other symbol CPs in the slot.
• the CP durations in this case may fulfill the following equality:
• the first CPi may be of length 120 ⁇ k ⁇ T c and the second CP2 may be of length 118 ⁇ k ⁇ T c .
• This CP structure may be alternatively described by the following equation using notations from TS 38.211:
• N p L is the number of T c base durations in a CP of numerology m in symbol l of a slot.
• the first symbol is utilized for TX-RX switching and/or AGC purposes, and the respective times for these procedures are less than the resulting duration of the first symbol, it may have shorter effective duration than other 12 OFDM symbols.
• An example with the first CP shorter than other CPs is the following:
• the spacing in the time direction should cover the worst case Doppler spread.
• the maximum spacing between DMRS in the time direction is— .
• the spacing should be in the range of— to— .
• the spacing of the DMRS should be in the range of 91.5 to 137 us. In case if gNB or SLSS are used for synchronization the Doppler spread will be even larger.
• the maximum delay spread r m leads to the maximum spacing between DMRS in the frequency direction of -— .
• the Doppler spread to enable proper operation of the system
• the spacing should be in the range for— to— .
• Variant a) is the classical case not considering the special case of AGC adaptation and Tx/Rx switching. This is the basic pattern from which the other ones are derived. In case of b) this is does include the current assumptions for AGC adaption and Tx/Rx switching. Case c) also contains the TDMed PSCCH. In variant d) there are two MIMO layers which are CDMed in time direction. It is important to keep in mind that for 15 kHz at high speed this might not be applicable. Variant e) is using CDM in frequency direction. This can be combined with variant d) to support 4 antenna ports with orthogonal reference signals. Variant f) does contain a second group of DRMS. If we combine this with the possibility of using CDM in both time and frequency direction we can reach a maximum of 8 orthogonal layers. The last Variants g) and h) show an ECP and a mimi slot.
• the block error rate (BLER) plots in Figure 4D compares the performance of the new pattern in rank 1 transmissions.
• the number of for the type 1 NR CP-OFDM DMRS describe the position of reference signals in terms of OFDM symbols (numbering starting at 0). Since each of the configurations has a different reference overhead we compare at the same TBS.
• the TBS is chosen in a ways that the system with the smallest overhead has a code-rate of 0.75. Due to the better time direction spacing a largely improved performance can be observed. Since it has a reduced overhead compared to NR type 1 NR CP-OFDM DMRS with 3 symbols it can achieve an improved performance even for larger subcarrier spacing, where the time spacing may not be as important.
• FIG. 5 illustrates an architecture of a system 500 of a network in accordance with some embodiments.
• the system 500 is shown to include a user equipment (UE) 501 and a UE 502.
• the UEs 501 and 502 are illustrated as smartphones (e.g., 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 Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
• PDAs Personal Data Assistants
• pagers pagers
• laptop computers desktop computers
• wireless handsets or any computing device including a wireless communications interface.
• any of the UEs 501 and 502 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
• An IoT UE can utilize technologies such as machine-to- machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
• M2M or MTC exchange of data may be a machine-initiated exchange of data.
• An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
• the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
• the UEs 501 and 502 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 510—
• the RAN 510 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
• UMTS Evolved Universal Mobile Telecommunications System
• E-UTRAN Evolved Universal Mobile Telecommunications System
• NG RAN NextGen RAN
• the UEs 501 and 502 utilize connections 503 and 504, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 503 and 504 are 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, aNew Radio (NR) protocol, and the like.
• GSM Global System for Mobile Communications
• CDMA code-division multiple access
• PTT Push-to-Talk
• POC PTT over Cellular
• UMTS Universal Mobile Telecommunications System
• LTE Long Term Evolution
• 5G fifth generation
• NR New Radio
• the UEs 501 and 502 may further directly exchange communication data via a ProSe interface 505.
• the ProSe interface 505 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
• PSCCH Physical Sidelink Control Channel
• PSSCH Physical Sidelink Shared Channel
• PSDCH Physical Sidelink Discovery Channel
• PSBCH Physical Sidelink Broadcast Channel
• the UE 502 is shown to be configured to access an access point (AP) 506 via connection 507.
• the connection 507 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 506 would comprise a wireless fidelity (WiFi®) router.
• WiFi® wireless fidelity
• the AP 506 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
• the RAN 510 can include one or more access nodes that enable the connections 503 and 504. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
• BSs base stations
• eNBs evolved NodeBs
• gNB next Generation NodeBs
• RAN nodes and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
• the RAN 510 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 511, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 512.
• macro RAN node 511 e.g., macro RAN node 511
• femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
• LP low power
• any of the RAN nodes 511 and 512 can terminate the air interface protocol and can be the first point of contact for the UEs 501 and 502.
• any of the RAN nodes 511 and 512 can fulfill various logical functions for the RAN 510 including, 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.
• RNC radio network controller
• the UEs 501 and 502 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 511 and 512 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC- FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
• OFDM signals can comprise a plurality of orthogonal subcarriers.
• a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 511 and 512 to the UEs 501 and 502, while uplink transmissions can utilize similar techniques.
• the grid can be a time-frequency grid, called a resource grid or time- frequency resource grid, which is the physical resource in the downlink in each slot.
• a time- frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
• Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
• the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
• the smallest time-frequency unit in a resource grid is denoted as a resource element.
• Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
• Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
• the physical downlink shared channel may carry user data and higher-layer signaling to the UEs 501 and 502.
• 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 UEs 501 and 502 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
• downlink scheduling (assigning control and shared channel resource blocks to the UE 502 within a cell) may be performed at any of the RAN nodes 511 and 512 based on channel quality information fed back from any of the UEs 501 and 502.
• the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 501 and 502.
• the PDCCH may use control channel elements (CCEs) to convey the control information.
• CCEs control channel elements
• the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
• Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
• RAGs resource element groups
• QPSK Quadrature Phase Shift Keying
• the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
• DCI downlink control information
• There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L l, 2, 4, or 8).
• Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
• the EPDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
• EPCCH enhanced physical downlink control channel
• ECCEs enhanced control channel elements
• each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs).
• EREGs enhanced resource element groups
• An ECCE may have other numbers of EREGs in some situations.
• the RAN 510 is shown to be communicatively coupled to a core network (CN) 520— via an Sl interface 513.
• the CN 520 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
• EPC evolved packet core
• NPC NextGen Packet Core
• the Sl interface 513 is split into two parts: the Sl-U interface 514, which carries traffic data between the RAN nodes 511 and 512 and the serving gateway (S-GW) 522, and the Sl-mobility management entity (MME) interface 515, which is a signaling interface between the RAN nodes 511 and 512 and MMEs 521.
• S-GW serving gateway
• MME Sl-mobility management entity
• the CN 520 comprises the MMEs 521, the S-GW 522, the Packet Data Network (PDN) Gateway (P-GW) 523, and a home subscriber server (HSS) 524.
• the MMEs 521 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
• the MMEs 521 may manage mobility aspects in access such as gateway selection and tracking area list management.
• the HSS 524 may comprise a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
• the CN 520 may comprise one or several HSSs 524, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
• the HSS 524 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
• the S-GW 522 may terminate the Sl interface 513 towards the RAN 510, and routes data packets between the RAN 510 and the CN 520.
• the S-GW 522 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
• the P-GW 523 may terminate an SGi interface toward a PDN.
• the P-GW 523 may route data packets between the EPC network and external networks such as a network including the application server 530 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 525.
• the application server 530 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
• PS UMTS Packet Services
• LTE PS data services etc.
• the P-GW 523 is shown to be communicatively coupled to an application server 530 via an IP communications interface 525.
• the application server 530 can also be configured to support one or more communication services (e.g., Voice-over-Intemet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 501 and 502 via the CN 520.
• VoIP Voice-over-Intemet Protocol
• PTT sessions PTT sessions
• group communication sessions social networking services, etc.
• the P-GW 523 may further be anode for policy enforcement and charging data collection.
• Policy and Charging Enforcement Function (PCRF) 526 is the policy and charging control element of the CN 520.
• PCRF Policy and Charging Enforcement Function
• HPLMN Home Public Land Mobile Network
• IP-CAN Internet Protocol Connectivity Access Network
• HPLMN Home Public Land Mobile Network
• V-PCRF Visited PCRF
• VPLMN Visited Public Land Mobile Network
• the PCRF 526 may be communicatively coupled to the application server 530 via the P-GW 523.
• the application server 530 may signal the PCRF 526 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
• the PCRF 526 may 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 server 530.
• PCEF Policy and Charging Enforcement Function
• TFT traffic flow template
• QCI QoS class of identifier
• FIG. 6 illustrates example components of a device 600 in accordance with some embodiments.
• the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown.
• the components of the illustrated device 600 may be included in a UE or a RAN node.
• the device 600 may include fewer elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor/controller to process IP data received from an EPC).
• the device 600 may include additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
• additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
• the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C- RAN) implementations).
• C- RAN Cloud-RAN
• the application circuitry 602 may include one or more application processors.
• the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
• the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
• the processors 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 device 600.
• processors of application circuitry 602 may process IP data packets received from an EPC.
• the baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
• the baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606.
• Baseband processing circuitry 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606.
• the baseband circuitry 604 may include a third generation (3G) baseband processor 604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
• the baseband circuitry 604 e.g., one or more of baseband processors 604A-D
• baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E.
• the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
• modulation/demodulation circuitry of the baseband circuitry 604 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
• encoding/decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
• LDPC Low Density Parity Check
• the baseband circuitry 604 may include one or more audio digital signal processor(s) (DSP) 604F.
• the audio DSP(s) 604F 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.
• some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 may be implemented together such as, for example, on a system on a chip (SOC).
• SOC system on a chip
• the baseband circuitry 604 may provide for communication compatible with one or more radio technologies.
• the baseband circuitry 604 may 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).
• EUTRAN evolved universal terrestrial radio access network
• WMAN wireless metropolitan area networks
• WLAN wireless local area network
• WPAN wireless personal area network
• multi-mode baseband circuitry Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol.
• RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
• the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
• RF circuitry 606 may include a receive signal path which may include circuitry to down- convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604.
• RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.
• the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c.
• the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a.
• RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path.
• the mixer circuitry 606a of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d.
• the amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c may 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 circuitry 604 for further processing.
• the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
• mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
• the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608.
• the baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.
• the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
• the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
• the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively.
• the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super heterodyne operation.
• the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
• the output baseband signals and the input baseband signals may be digital baseband signals.
• the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.
• ADC analog-to-digital converter
• DAC digital-to-analog converter
• a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
• the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
• synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
• the synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606d may be a fractional N/N+l synthesizer.
• frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
• VCO voltage controlled oscillator
• Divider control input may be provided by either the baseband circuitry 604 or the applications processor 602 depending on the desired output frequency.
• a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 602.
• Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
• the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
• the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
• the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
• the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
• Nd is the number of delay elements in the delay line.
• synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
• the output frequency may be a LO frequency (fLO).
• the RF circuitry 606 may include an IQ/polar converter.
• FEM circuitry 608 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing.
• FEM circuitry 608 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610.
• the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.
• the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation.
• the FEM circuitry 608 may include a receive signal path and a transmit signal path.
• the receive signal path of the FEM circuitry 608 may include a low noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606).
• the transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).
• PA power amplifier
• the PMC 612 may manage power provided to the baseband circuitry 604.
• the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
• the PMC 612 may often be included when the device 600 is capable of being powered by a battery, for example, when the device is included in a UE.
• the PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
• FIG. 6 shows the PMC 612 coupled only with the baseband circuitry 604.
• the PMC 612 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.
• the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power.
• DRX Discontinuous Reception Mode
• the device 600 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
• the device 600 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
• the device 600 may not receive data in this state, in order to receive data, it must transition back to RRC Connected state.
• An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
• Processors of the application circuitry 602 and processors of the baseband circuitry 604 may be used to execute elements of one or more instances of a protocol stack.
• processors of the baseband circuitry 604 alone or in combination, may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 602 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
• Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
• RRC radio resource control
• Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
• Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
• FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
• the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors.
• Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory 604G.
• the baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 712 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604), an application circuitry interface 714 (e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6), an RF circuitry interface 716 (e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
• a memory interface 712 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604
• an application circuitry interface 714 e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6
• an RF circuitry interface 716 e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
• a wireless hardware connectivity interface 718 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
• a power management interface 720 e.g., an interface to send/receive power or control signals to/from the PMC 612.
• FIG. 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
• FIG. 8 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory /storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840.
• node virtualization e.g., NFV
• a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 800.
• the processors 810 may include, for example, a processor 812 and a processor 814.
• CPU central processing unit
• RISC reduced instruction set computing
• CISC complex instruction set computing
• GPU graphics processing unit
• DSP digital signal processor
• ASIC application specific integrated circuit
• RFIC radio-frequency integrated circuit
• the memory /storage devices 820 may include main memory, disk storage, or any suitable combination thereof.
• the memory /storage devices 820 may 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.
• DRAM dynamic random access memory
• SRAM static random-access memory
• EPROM erasable programmable read-only memory
• EEPROM electrically erasable programmable read-only memory
• Flash memory solid-state storage, etc.
• the communication resources 830 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 via a network 808.
• the communication resources 830 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
• wired communication components e.g., for coupling via a Universal Serial Bus (USB)
• cellular communication components e.g., for coupling via a Universal Serial Bus (USB)
• NFC components e.g., NFC components
• Bluetooth® components e.g., Bluetooth® Low Energy
• Wi-Fi® components e.g., Wi-Fi® components
• Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein.
• the instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor’s cache memory), the memory /storage devices 820, or any suitable combination thereof.
• any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory /storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media.
• the devices/components of Figures 5-8, and particularly the baseband circuitry of Figure 7, may be used to practice, in whole or in part, any of the operation flow/algorithmic structures depicted in Figures 1-3.
• operation flow/algorithmic structure 100 may include, at 105, retrieving, from memory, information to support automatic gain control (AGC) adaptation.
• Operation flow/algorithmic structure 100 may further include, at 110, performing, within a first portion of an orthogonal frequency division multiplexing (OFDM) symbol period, a transmit-to-receive switching operation or a receive-to-transmit switching operation.
• Operation flow/algorithmic structure 100 may further include, at 115, performing, based on the information to support AGC adaptation, an AGC adaptation within a second portion of an OFDM symbol period.
• OFDM orthogonal frequency division multiplexing
• operation flow/algorithmic structure 200 may include, at 205, performing a transmit-to-receive switching operation or a receive-to-transmit switching operation within a first portion of an orthogonal frequency division multiplexing (OFDM) symbol period.
• Operation flow/algorithmic structure 200 may further include, at 210, encoding information to support AGC adaptation in one or more signals for transmission within a second portion of an OFDM symbol period.
• OFDM orthogonal frequency division multiplexing
• operation flow/algorithmic structure 300 may include, at 305, performing a transmit-to-receive switching operation or a receive-to-transmit switching operation within a first portion of an orthogonal frequency division multiplexing (OFDM) symbol period in a slot.
• Operation flow/algorithmic structure 300 may further include, at 310, performing an automatic gain control (AGC) adaptation within a second portion of an OFDM symbol period in the slot.
• AGC automatic gain control
• Example 1 includes an apparatus comprising: memory to store information to support automatic gain control (AGC) adaptation; and processing circuitry, coupled with the memory, to: perform, within a first portion of an orthogonal frequency division multiplexing (OFDM) symbol period, a transmit-to-receive switching operation or a receive-to-transmit switching operation; and perform, based on the information to support AGC adaptation, an AGC adaptation within a second portion of an OFDM symbol period.
• AGC automatic gain control
• Example 2 includes the apparatus of example 1 or some other example herein, wherein the first portion and the second portion are within the same OFDM symbol period.
• Example 3 includes the apparatus of example 1 or some other example herein, wherein the first portion is within a first OFDM symbol period and the second portion is within a second OFDM symbol period.
• Example 4 includes the apparatus of example 1 or some other example herein, wherein a length of the first portion of the OFDM symbol is thirteen microseconds or less.
• Example 5 includes the apparatus of example 1 or some other example herein, wherein a length of the second portion is fifteen microseconds or less.
• Example 6 includes the apparatus of example 1 or some other example herein, wherein the processing circuitry is further to perform a device-to-device transmission within a third portion of an OFDM symbol period.
• Example 7 includes the apparatus of example 1 or some other example herein, wherein the first portion immediately precedes the second portion.
• Example 8 includes the apparatus of example 1 or some other example herein, wherein the apparatus is an apparatus of a first user equipment (UE) and the one or more signals are encoded for transmission to a second UE.
• UE user equipment
• Example 9 includes the apparatus of example 1 or some other example herein, wherein the processing circuitry is further to encode for transmission, during the AGC adaptation portion of the signal: control channel information, a shared channel signal, a reference signal, a synchronization signal, or an AGC training sequence.
• Example 10 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a first user equipment (UE) to: perform a transmit-to- receive switching operation or a receive-to-transmit switching operation within a first portion of an orthogonal frequency division multiplexing (OFDM) symbol period; and encode information to support AGC adaptation in one or more signals for transmission within a second portion of an OFDM symbol period.
• UE user equipment
• Example 11 includes the one or more computer-readable media of example 10 or some other example herein, wherein the first portion and the second portion are within the same OFDM symbol period.
• Example 12 includes the one or more computer-readable media of example 10 or some other example herein, wherein the first portion is within a first OFDM symbol period and the second portion is within a second OFDM symbol period.
• Example 13 includes the one or more computer-readable media of example 10 or some other example herein, wherein a length of the first portion of the OFDM symbol is thirteen microseconds or less, and a length of the second portion is fifteen microseconds or less.
• Example 14 includes the one or more computer-readable media of example 10 or some other example herein, wherein the one or more computer-readable media further stores instructions to perform a device-to-device transmission within a third portion of an OFDM symbol period.
• Example 15 includes the one or more computer-readable media of example 10 or some other example herein, wherein the one or more computer-readable media further stores instructions to encode for transmission, during the AGC adaptation portion of the signal: control channel information, a shared channel signal, a reference signal, a synchronization signal, or an AGC training sequence.
• Example 16 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a first user equipment (UE) to: perform a transmit-to- receive switching operation or a receive-to-transmit switching operation within a first portion of an orthogonal frequency division multiplexing (OFDM) symbol period in a slot; and perform an automatic gain control (AGC) adaptation within a second portion of an OFDM symbol period in the slot.
• UE user equipment
• AGC automatic gain control
• Example 17 includes the one or more computer-readable media of example 16 or some other example herein, wherein the first portion is within a last OFDM symbol in the slot.
• Example 18 includes the one or more computer-readable media of example 16 or some other example herein, wherein the slot comprises twelve or thirteen OFDM symbols.
• Example 19 includes the one or more computer-readable media of example 16 or some other example herein, wherein AGC adaptation is performed during a cyclic prefix (CP) interval of a first OFDM symbol in the slot.
• CP cyclic prefix
• Example 20 includes the one or more computer-readable media of example 16 or some other example herein, wherein the slot has a 30 kHZ subcarrier spacing (SCS) or a 60 kHZ SCS.
• SCS subcarrier spacing
• Example 21 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
• Example 22 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
• Example 23 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
• Example 24 may include a method, technique, or process as described in or related to any of examples 1-20, or portions or parts thereof.
• Example 25 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-20, or portions thereof.
• Example 26 may include a method of communicating in a wireless network as shown and described herein.
• Example 27 may include a system for providing wireless communication as shown and described herein.
• Example 28 may include a device for providing wireless communication as shown and described herein.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)

Priority Applications (2)

Applications Claiming Priority (4)

Publications (1)

Family

ID=69949931

Family Applications (1)

Country Status (2)

Cited By (2)

Citations (2)

• 2019
  • 2019-09-27 EP EP19866594.5A patent/EP3857834A4/en active Pending
  • 2019-09-27 WO PCT/US2019/053653 patent/WO2020069441A1/en unknown

Patent Citations (2)

Non-Patent Citations (4)

Also Published As

Similar Documents

Legal Events