Bandwidth portion switching delay for uplink transmission

By considering the timing advance value in the 3GPP technical standard and adjusting the bandwidth part switching time of the uplink, the problem of inaccurate delay in the prior art is solved, the delay requirements are met, and the link matching is improved.

CN112567863BActive Publication Date: 2024-11-08APPLE INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN201980053600.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-08-20
Filing Date
2019-08-19
Publication Date
2024-11-08
Estimated Expiration
2039-08-19

AI Technical Summary

Technical Problem

The existing 3GPP technical standards fail to consider timing advance (TA) in the uplink bandwidth part handover, resulting in inaccurate delays and cannot meet the delay requirements specified in R4-1809380 version.

Method used

In the bandwidth part switching of the uplink based on the downlink control information (DCI) and timer in the uplink, the handover timer is ensured that the handover delay meets the requirements, such as the last OFDM symbol of the DL The end time slot m+1 starts the UL switching, and completes the switching within the UL time slot m+Y.

Benefits of technology

By considering the timing advance value, the bandwidth part switching time is accurately adjusted, which meets the delay requirements in the 3GPP technical standards, and improves the matching of uplink and downlink delays by user equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112567863B_ABST
    Figure CN112567863B_ABST
Patent Text Reader

Abstract

The present invention discloses an apparatus of a user equipment (UE), the apparatus comprising one or more baseband processors for processing a bandwidth part (BWP) switching request from a serving cell at time slot n, and performing an active BWP switching to a new BWP on the serving cell no later than time slot n+Y, where Y is a BWP switching delay. The one or more baseband processors will adapt a timing advance (TA) value to determine when to perform an active BWP switching. The apparatus may include a memory for storing the BWP switching request.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 720,031 (AB4543-Z), filed on August 20, 2019. Said application No. 62 / 720,031 is hereby incorporated by reference in its entirety. Background Art

[0003] The Downlink Control Information (DCI)-based or timer-based Bandwidth Part (BWP) switching requirements for uplink (UL) defined in the 3rd Generation Partnership Project (3GPP) Technical Standard (TS) 38.133 do not take into account the effect of Timing Advance (TA), resulting in inaccuracies. From the user equipment (UE) perspective, the delay caused by BWP switching is an absolute number and is the same for uplink (UL) and downlink (DL). However, it is important to note that the timing of UL and DL differ by the value of TA. Therefore, the UE cannot meet the delay requirements specified in R4-1809380 (an updated version of 3GPP TS38.133). BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The claimed subject matter is particularly pointed out and distinctly described in the concluding portion of the specification. However, such subject matter may be understood by reference to the following detailed description when reading the accompanying drawings, wherein:

[0005] Figure 1 is a diagram showing start and end times of bandwidth part (BWP) switching based on downlink control information (DCI) in uplink according to one or more embodiments.

[0006] Figure 2 The architecture of a system of networks according to some embodiments is shown.

[0007] Figure 3 Example components of an apparatus according to some embodiments are shown.

[0008] Figure 4 An example interface of a baseband circuit according to some embodiments is shown.

[0009] It should be understood that for simplicity and / or clarity of illustration, the elements illustrated in the figures are not necessarily drawn to scale. For example, for clarity, the size of some elements may be enlarged relative to other elements. In addition, if deemed appropriate, reference numerals are repeated in the drawings to indicate corresponding and / or similar elements. DETAILED DESCRIPTION

[0010] In the following detailed description, a number of specific details are provided to provide a comprehensive understanding of the claimed subject matter. However, it will be appreciated by those skilled in the art that the claimed subject matter may be implemented without these specific details. In other cases, well-known methods, processes, components and / or circuits have not yet been described in detail.

[0011] In the following description and / or claims, the terms "coupled" and / or "connected" and their derivatives may be used. In a particular embodiment, "connected" may be used to indicate that two or more elements are in direct physical and / or electrical contact with each other. "Coupled" may represent that two or more elements are in direct physical and / or electrical contact. However, "coupled" may also refer to that two or more elements may not be in direct contact with each other, but may still cooperate and / or interact with each other. For example, "coupled" may refer to that two or more elements are not in direct contact with each other, but are indirectly joined together via another element or an intermediate element. Finally, the terms "on", "overlying" and "above" may be used in the following description and claims. "On", "overlying" and "above" may be used to indicate that two or more elements are in direct physical contact with each other. However, it should be noted that "above" may also refer to that two or more elements are not in direct contact with each other. For example, "above" may represent that an element is higher than another element but is not in contact with each other, and another one or more elements may be present between the two elements. Furthermore, the term "and / or" may mean "and", it may mean "or", it may mean "exclusive or", it may mean "one", it may mean "some but not all", it may mean "neither", and / or it may mean "both", but does not limit the scope of the claimed subject matter in this regard. In the following description and / or claims, the terms "include" and "comprising", along with their derivatives, may be used and are intended to be synonymous with each other.

[0012] Reference now Figure 1 , a diagram showing the start and end times of bandwidth part (BWP) switching based on downlink control information (DCI) in the uplink according to one or more embodiments will be discussed. The bandwidth part (BWP) switching delay requirement for uplink (UL) transmissions as defined in the 3rd Generation Partnership Project (3GPP) Technical Standard (TS) 3 8.133 may be modified to take timing advance (TA) into account. Example TA 110 in Figure 1 100. The latest version of TS38.133, R4-1809380, states as follows.

[0013] For DCI-based BWP switching, after the UE receives a BWP switching request on a serving cell at time slot n, the UE shall be able to receive PDSCH (for DL ​​active BWP switching) or send PUSCH (for UL active BWP switching) on ​​a new BWP on a serving cell where the BWP switching occurs no later than time slot n+Y.

[0014] For timer-based BWP switching, the UE shall start BWP switching at timeslot n, where n is the start of the subframe (FR1) or half-subframe (FR2) immediately after the expiration of the BWP inactivity timer on the serving cell, and the UE shall be able to receive PDSCH (for DL ​​active BWP switching) or send PUSCH (for UL active BWP switching) on ​​the new BWP on the serving cell where the BWP switching occurs no later than timeslot n+Y.

[0015] The above paragraph in TS 38.133 does not consider the effect of timing advance (TA) 110 in UL 112. From the UE's perspective, the delay caused by BWP switching is an absolute number, and this number is the same for UL 112 and downlink (DL) 114, and the timing of UL 112 and DL 114 differs by the value of TA 110, such as Figure 1 Therefore, the UE cannot meet the delay requirement specified in version R4-1809380 of TS38.133.

[0016] In one example, the timing advance (TA) 110 may be taken into account as follows. For downlink control information (DCI) based BWP switching in UL 110, the UE may start the BWP switching at time slot m, where the timing of the end of the last orthogonal frequency division multiplexing (OFDM) symbol of the physical downlink control channel (PDCCH) carrying the active BWP switching DCI in DL 114 is within time slot m. If the end of the last OFDM symbol of the PDCCH carrying the active BWP switching DCI in DL 114 is perfectly aligned with the boundary between time slot m and time slot m+1, the UE may start the BWP switching at time slot m+1. The UE may send a physical uplink shared channel (PUSCH) for UL 112 active BWP switching on a new BWP on a serving cell where the BWP switching occurs no later than time slot m+Y, where Y represents the BWP switching delay of Y=2 milliseconds (ms).

[0017] In another example, the timing advance (TA) 110 may be taken into account as follows. For timer-based BWP switching in UL 112, the UE may start BWP switching at UL timeslot m, where m is the start of the subframe (FR1) or half-subframe (FR2) immediately after the expiration of the BWP inactivity timer on the serving cell, and the UE may send PUSCH for UL 112 active BWP switching on the new BWP on the serving cell where the BWP switching occurs no later than timeslot m+Y, where Y represents the BWP switching delay of Y=2ms.

[0018] Figure 1 100 shows the start and end time of UL DCI-based BWP switching in a carrier with 120 kHz subcarrier spacing (SCS). Figure 1 As shown, the BWP switching starts at time slot 0 in DL 114, but starts at time slot 1 in UL 112. With the same delay duration for BWP switching in DL 114 and UL 112, UL 112 can receive PDSHC on the new BWP on the serving cell at time slot 17 in UL 112, and can send PUSCH on the new BWP on the serving cell at time slot 18 in UL 112. The difference of one time slot between UL 112 and DL 114 is due to the presence of timing advance (TA) 110. Therefore, the first new BWP time slot of UL 112 is time slot 18, which is the same as the delay duration for BWP switching in DL 114 and UL 112. Figure 1 The first new BWP time slot for DL ​​114 is time slot 17, Figure 1 Shown as time slot 118.

[0019] In some examples, if the start time of BWP switching in both DL 114 and UL 112 is all based on DL time slot n, the delay durations for DL ​​114 and UL 112 may be different. The relationship between the two delay durations for BWP switching of DL 114 and UL 112 may be as follows. If the UE starts BWP switching at time slot n of DL 114, the UE may receive PDSCH for DL ​​114 active BWP switching on a new BWP on a serving cell where BWP switching occurs no later than time slot n+Y, where Y represents a BWP switching delay of Y=2ms. Alternatively, the UE may send PUSCH for UL 112 active BWP switching on a new BWP on a serving cell where BWP switching occurs no later than time slot n+X, where X=Ceil(Y+TA) and is in units of time slots, and where the function Ceil(·) is a ceiling function.

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

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

[0022] UE 201 and UE 202 may be configured to connect, e.g., be communicatively coupled, to a radio access network (RAN) 210, which may be, e.g., an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NG RAN), or some other type of RAN. UE 201 and UE 202 utilize connection 203 and connection 204, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connection 203 and connection 204 are shown as air interfaces to achieve communicatively coupling, and may be consistent with a cellular communication protocol, such as a global system for mobile communications (GSM) protocol, a code division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, a cellular PTT (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, etc.

[0023] In this embodiment, UE 201 and UE 202 may also directly exchange communication data via ProSe interface 205. ProSe interface 205 may alternatively be referred to as a sidelink interface including 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).

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

[0025] The RAN 210 may include one or more access nodes that enable connection 203 and connection 204. These access nodes (ANs) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). The RAN 210 may include one or more RAN nodes (e.g., macro RAN nodes 211) for providing macro cells, and one or more RAN nodes (e.g., low power (LP) RAN nodes 212) for providing femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells).

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

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

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

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

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

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

[0032] RAN 210 is shown as being communicatively coupled to a core network (CN) 220 via an S1 interface 213. In various embodiments, CN 220 may be an evolved packet core (EPC) network, a next generation packet core (NPC) network, or some other type of CN. In this embodiment, S1 interface 213 is divided into two parts: S1-U interface 214, which carries traffic data between RAN node 211 and RAN node 212 and serving gateway (S-GW) 222; and S1-mobility management entity (MME) interface 215, which is a signaling interface between RAN node 211 and RAN node 212 and MME 221.

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

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

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

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

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

[0038] The application circuit 302 may include one or more application processors. For example, the application circuit 302 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include memory / storage devices and may be configured to execute instructions stored in the memory / storage devices to enable various applications or operating systems to run on the device 300. In some embodiments, the processor of the application circuit 302 may process IP data packets received from the EPC.

[0039] The baseband circuit 304 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 304 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 306 and generate baseband signals for the transmit signal path of the RF circuit 306. The baseband processing circuit 304 may interact with the application circuit 302 to generate and process baseband signals and control the operation of the RF circuit 306. For example, in some embodiments, the baseband circuit 304 may include a third generation (3G) baseband processor 304A, a fourth generation (4G) baseband processor 304B, a fifth generation (5G base) band processor 304C, or one or more other baseband processors 304D of other existing generations, generations under development or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 304 (e.g., one or more baseband processors in the baseband processors 304A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuit 306. In other embodiments, some or all of the functionality of baseband processors 304A-D may be included in a module stored in memory 304G and executed via central processing unit (CPU) 304E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 304 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuitry 304 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.

[0040] In some embodiments, the baseband circuit 304 may include one or more audio digital signal processors (DSPs) 304F. The audio DSP 304F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 304 and the application circuit 302 may be implemented together, such as on a system on a chip (SOC).

[0041] In some embodiments, baseband circuitry 304 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 304 may support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which baseband circuitry 304 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0042] RF circuit 306 can communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 306 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 306 may include a receive signal path, which may include circuits for down-converting RF signals received from FEM circuit 308 and providing baseband signals to baseband circuit 304. RF circuit 306 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by baseband circuit 304 and providing RF output signals for transmission to FEM circuit 308.

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

[0044] In some embodiments, mixer circuit 306a of the transmit signal path may be configured to up-convert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 306d to generate an RF output signal for FEM circuit 308. The baseband signal may be provided by baseband circuit 304 and may be filtered by filter circuit 306c.

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

[0046] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuit 306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 304 may include a digital baseband interface to communicate with RF circuit 306.

[0047] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect. In some embodiments, synthesizer circuit 306 d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 306 d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

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

[0049] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not required. The divider control input may be provided by the baseband circuit 304 or the application processor 302 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 302.

[0050] The synthesizer circuit 306d of the RF circuit 306 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

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

[0052] The FEM circuitry 308 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 310, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 306 for further processing. The FEM circuitry 308 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 306 for transmission through one or more of the one or more antennas 310. In various embodiments, amplification by the transmit or receive signal path may be accomplished only in the RF circuitry 306, only in the FEM 308, or in both the RF circuitry 306 and the FEM 308.

[0053] In some embodiments, the FEM circuit 308 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 306). The transmit signal path of the FEM circuit 308 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 306); and one or more filters for generating an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 310).

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

[0055] Although Figure 3The PMC 312 is shown coupled only to the baseband circuit 304, however, in other embodiments, the PMC 312 may be additionally or alternatively coupled to other components (such as, but not limited to, the application circuit 302, the RF circuit 306, or the FEM 308) and perform similar power management operations.

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

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

[0058] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0059] The processor of the application circuit 302 and the processor of the baseband circuit 304 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 304 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 304 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0060] Figure 4An example interface of a baseband circuit according to some embodiments is shown. As discussed above, Figure 3 The baseband circuit 304 may include processors 304A-304E and a memory 304G utilized by the processors. Each of the processors 304A-304E may include a memory interface 404A-404E, respectively, for sending / receiving data to / from the memory 304G.

[0061] The baseband circuit 304 may also include: one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 412 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 304); an application circuit interface 414 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 304); Figure 3 RF circuit interface 416 (for example, for sending / receiving data to / from the application circuit 302); Figure 3 an interface for sending / receiving data to / from a RF circuit 306); a wireless hardware connection interface 418 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g. Low Energy), components and other communication components to send / receive data); and a power management interface 420 (eg, an interface for sending / receiving power or control signals to / from PMC 312).

[0062] The following is an exemplary implementation of the subject matter described herein. In embodiment one, a device of a user equipment (UE) includes: one or more baseband processors, the one or more baseband processors being used to process a bandwidth part (BWP) switching request from a serving cell at time slot n, and to perform an active BWP switching to a new BWP on the serving cell at a time no later than time slot n+Y, where Y is a BWP switching delay, wherein the one or more baseband processors will adapt a timing advance (TA) value to determine when to perform the active BWP switching; and a memory for storing the BWP switching request. Embodiment two may include the subject matter of embodiment one or any one of the embodiments described herein, wherein the one or more baseband processors will receive a physical downlink shared channel (PDSCH) for a downlink (DL) at a time slot offset in time by the TA value relative to an uplink (UL). Embodiment three may include the subject matter of embodiment one or any one of the embodiments described herein, wherein the one or more baseband processors will send a physical uplink shared channel (PUSCH) for the uplink (UL) at a time slot advanced in time by the TA value relative to the downlink (DL).

[0063] In a fourth embodiment, a device of a user equipment (UE) includes: one or more baseband processors, the one or more baseband processors being used to process a bandwidth part (BWP) switching request from a serving cell in time slot m, and to perform an active BWP switching to transmit a physical uplink shared channel (PUSCH) in an uplink (UL) on a new BWP on the serving cell at a time no later than time slot m+Y, wherein Y is a BWP switching delay, wherein a downlink time slot is offset by a timing advance (TA) value relative to a UL time slot, and the one or more baseband processors will adapt the TA value to determine when to perform the active BWP switching; and a memory for storing the BWP switching request. A fifth embodiment may include the subject matter of the fourth embodiment or any one of the embodiments described herein, wherein the end of the last symbol of a physical downlink control channel (PDCCH) carrying active BWP switching downlink control information (DCI) in the DL is within time slot m. Embodiment six may include the subject matter of embodiment four or any one of the embodiments described herein, wherein when the end of the last symbol of the physical downlink control channel (PDCCH) carrying the active BWP switching downlink control information (DCI) in the DL is aligned with the boundary between time slot m and time slot m+1, the one or more baseband processors will start the BWP switching in time slot m+1. Embodiment seven may include the subject matter of embodiment four or any one of the embodiments described herein, wherein the one or more baseband processors will start the BWP switching in UL time slot m, where m is the starting point of a subframe (FR1) or half subframe (FR2) immediately after the expiration of the BWP inactivity timer on the serving cell for the timer-based BWP switching in the UL.

[0064] In an eighth embodiment, a device of a user equipment includes: one or more baseband processors, the one or more baseband processors being used to process a bandwidth part (BWP) switching request from a serving cell at time slot n, and to perform an active BWP switching to a new BWP on the serving cell no later than time slot n+Y, where Y is a BWP switching delay, wherein the one or more baseband processors will adapt a timing advance (TA) value to determine when to perform the active BWP switching, and start the BWP switching at time slot n for downlink (DL); and a memory for storing the BWP switching request. An ninth embodiment may include the subject matter of the eighth embodiment or any one of the embodiments described herein, wherein the one or more baseband processors will receive a downlink physical shared channel (PDSCH) on the new BWP on the serving cell no later than time slot n+Y. Embodiment ten may include the subject matter of embodiment eight or any one of the embodiments described herein, wherein the one or more baseband processors will send a physical uplink shared channel (PUSCH) on the new BWP on the serving cell no later than time slot n+X, where X=Ceil(Y+TA) and is in units of time slots, where Ceil(·) is a ceiling function.

[0065] In an eleventh embodiment, one or more machine-readable media store instructions thereon, which, when executed by a device of a user equipment (UE), result in: processing a bandwidth part (BWP) switching request from a serving cell at time slot n; performing an active BWP switching to a new BWP on the serving cell no later than time slot n+Y, where Y is a BWP switching delay; and adapting a timing advance (TA) value to determine when to perform the active BWP switching. An eleventh embodiment may include the subject matter of an eleventh embodiment or any one of the embodiments described herein, wherein the instructions, when executed, further result in receiving a physical downlink shared channel (PDSCH) for a downlink (DL) at a time slot offset in time by the TA value relative to an uplink (UL). An thirteenth embodiment may include the subject matter of an eleventh embodiment or any one of the embodiments described herein, wherein the instructions, when executed, further result in sending a physical uplink shared channel (PUSCH) for the uplink (UL) at a time slot advanced in time by the TA value relative to the downlink (DL).

[0066] In the fourteenth embodiment, one or more machine-readable media store instructions, which, when executed by a device of a user equipment (UE), result in: processing a bandwidth part (BWP) switching request from a serving cell at time slot m; performing an active BWP switching to transmit a physical uplink shared channel (PUSCH) in an uplink (UL) on a new BWP on the serving cell at a time no later than time slot m+Y, where Y is a BWP switching delay, where a downlink time slot is offset relative to a UL time slot by a timing advance (TA) value; and adapting the TA value to determine when to perform the active BWP switching. The fifteenth embodiment may include the subject matter of the fourteenth embodiment or any one of the embodiments described herein, wherein the end of the last symbol of a physical downlink control channel (PDCCH) carrying active BWP switching downlink control information (DCI) in the DL is within time slot m. Embodiment sixteen may include the subject matter of embodiment fourteen or any one of the embodiments described herein, wherein the instructions, when executed, further result in starting the BWP switching in time slot m+1 when the end of the last symbol of the physical downlink control channel (PDCCH) carrying the active BWP switching downlink control information (DCI) in the DL is aligned with the boundary between time slot m and time slot m+1. Embodiment seventeen may include the subject matter of embodiment fourteen or any one of the embodiments described herein, wherein the instructions, when executed, further result in starting the BWP switching in UL time slot m, wherein m is the starting point of a subframe (FR1) or half subframe (FR2) immediately after the expiration of the BWP inactivity timer on the serving cell for the timer-based BWP switching in the UL.

[0067] In the eighteenth embodiment, one or more machine-readable media store instructions, which, when executed by a device of a user equipment (UE), result in: processing a bandwidth part (BWP) switching request from a serving cell at time slot n; and performing an active BWP switching to a new BWP on the serving cell no later than time slot n+Y, where Y is a BWP switching delay; adapting a timing advance (TA) value to determine when to perform the active BWP switching; and starting the BWP switching at time slot n for downlink (DL). The nineteenth embodiment may include the subject matter of the eighteenth embodiment or any one of the embodiments described herein, wherein the instructions, when executed, further result in receiving a downlink physical shared channel (PDSCH) on the new BWP on the serving cell no later than time slot n+Y. Embodiment 20 may include the subject matter of embodiment 18 or any one of the embodiments described herein, wherein the instruction, when executed, further results in sending a physical uplink shared channel (PUSCH) on the new BWP on the serving cell no later than time slot n+X, where X=Ceil(Y+TA) and is in units of time slots, where Ceil(·) is a ceiling function.

[0068] Although the claimed subject matter has been described with a certain degree of specificity, it will be appreciated that elements of the claimed subject matter may be varied by one skilled in the art without departing from the spirit and / or scope of the claimed subject matter. It is believed that the subject matter associated with bandwidth portion switching delay for uplink transmissions and its many attendant utilities will be understood from the foregoing description, and it will be apparent that various changes may be made to the form, construction and / or arrangement of its components without departing from the scope and / or spirit of the claimed subject matter, or without sacrificing all of its material advantages, the forms described above being merely illustrative embodiments of the components and / or further providing no substantial changes thereto. It is the intent of the claims to cover and / or include such variations.

Claims

1. A device for user equipment UE, include: one or more baseband processors, the one or more baseband processors to process a bandwidth portion BWP handover request from a serving cell at time slot n and perform an active BWP handover to a new BWP on the serving cell no later than time slot n+Y, where Y is a BWP handover delay of 2 milliseconds; wherein the one or more baseband processors will adapt a timing advance TA value to determine when to perform the active BWP switch, and start the BWP switch at time slot n for a downlink DL, wherein the one or more baseband processors will send a physical uplink shared channel PUSCH on the new BWP on the serving cell no later than time slot n+X, where X=Ceil(Y+TA) and is in units of time slots, where Ceil(·) is a ceiling function; and A memory is used to store the BWP switching request.

2. The apparatus according to claim 1, wherein the one or more baseband processors are used to process a BWP switching request from a serving cell in time slot m, and perform an active BWP switching to send a physical uplink shared channel (PUSCH) in an uplink (UL) on a new BWP on the serving cell no later than time slot m+Y, wherein the end of the last symbol of a physical downlink control channel (PDCCH) carrying active BWP switching downlink control information (DCI) in DL is within time slot m.

3. The apparatus according to claim 2, wherein when the end of the last symbol of the physical downlink control channel (PDCCH) carrying the active BWP switching downlink control information (DCI) in the DL is aligned with the boundary between time slot m and time slot m+1, the one or more baseband processors will start the BWP switching in time slot m+1.

4. The apparatus of claim 2, wherein the one or more baseband processors are to start the BWP switching at UL timeslot m, where m is a starting point of a subframe FR1 or a half-subframe FR2 immediately after expiration of a BWP inactivity timer on the serving cell for the timer-based BWP switching in the UL.

5. One or more machine-readable media having instructions stored thereon, which, when executed by a device of a user equipped UE, result in: Processing bandwidth part BWP switching request from serving cell in time slot n; performing an active BWP switch to a new BWP on the serving cell no later than time slot m+Y, where Y is a BWP switch delay of 2 milliseconds; Adapting a timing advance TA value to determine when to perform the active BWP switching; Starting the BWP switching at time slot n for downlink DL; as well as A physical uplink shared channel PUSCH is transmitted on the new BWP on the serving cell no later than time slot n+X, where X=Ceil(Y+TA) and is in units of time slots, where Ceil(·) is a ceiling function.

6. The one or more machine-readable media of claim 5, wherein the instructions, when executed, further result in: Processing the BWP switching request from the serving cell in time slot m; Performing an active BWP switch at a time no later than time slot m+Y to transmit a physical uplink shared channel (PUSCH) in an uplink (UL) on a new BWP on the serving cell; and The end of the last symbol of the physical downlink control channel PDCCH carrying the active BWP switching downlink control information DCI in DL is within the time slot m.

7. One or more machine-readable media according to claim 6, wherein the instructions, when executed, further cause the BWP switching to start in time slot m+1 when the end of the last symbol of the physical downlink control channel (PDCCH) carrying the active BWP switching downlink control information (DCI) in the DL is aligned with the boundary between time slot m and time slot m+1.

8. The one or more machine-readable media of claim 6, wherein the instructions, when executed, further cause the BWP switching to start at UL time slot m, wherein m is a starting point of a subframe FR1 or a half-subframe FR2 immediately after expiration of a BWP inactivity timer on the serving cell for a timer-based BWP switching in the UL.

Citation Information

Patent Citations

  • Paging method, communication timing method and apparatuses

    CN108012329A

  • Apparatuses for transmission of paging blocks in swept downlink beams

    WO2018144873A1