Method, system and apparatus for handling dynamic spectrum sharing and uplink subcarrier shifting

Abstract

Embodiments described herein include methods, systems, and apparatus for allowing user equipment (UE) supporting dynamic spectrum sharing (DSS) and uplink (UL) shifting to access a cell and prohibiting UEs that do not support DSS and UL shifting. Embodiments may use a cell barring field in a master information block and an additional filter to indicate the barring state of a network node.

Description

Technical Field

[0001] The present application generally relates to wireless communication systems, including preventing interference caused by downlink spectrum sharing and uplink shifting. Background Art

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is generally referred to by industry organizations as Worldwide Interoperability for Microwave Access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLANs), which is generally referred to by industry organizations as Wi-Fi. In the 3GPP radio access network (RAN) in an LTE system, a base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an evolved Node B, an enhanced Node B, an eNodeB, or an eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with a wireless communication device referred to as a user equipment (UE). In the fifth generation (5G) wireless RAN, the RAN nodes may include 5G nodes, NR nodes (also called next generation Node B or g NodeB (gNB)).

[0003] The RAN uses radio access technologies (RATs) to communicate between RAN nodes and UEs. The RAN may include a global system for mobile communications (GSM), an enhanced data rate for GSM evolution (EDGE) RAN (GERAN), a universal terrestrial radio access network (UTRAN), and / or an E-UTRAN, which provides access to communication services through a core network. Each RAN in the RAN operates according to a specific 3GPP RAT. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT, and NG-RAN implements 5G RAT. In some deployments, E-UTRAN may also implement 5G RAT.

[0004] The frequency bands for 5G NR can be divided into two different frequency ranges. Frequency range 1 (FR1) may include frequency bands operating at frequencies below 6 GHz, some of which may be used by previous standards and may potentially be expanded to cover new spectrum products from 410 MHz to 7125 MHz. Frequency range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. The frequency bands in the millimeter wave (mmWave) range of FR2 may have a smaller range but potentially higher available bandwidth than the frequency bands in FR1. The skilled person will recognize that these frequency ranges, which are provided by way of example, may vary from time to time or region to region. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0006] Figure 1 A frequency domain graph showing subcarrier mapping of an LTE signal according to one embodiment is shown.

[0007] Figure 2 A frequency domain graph showing subcarrier mapping for a New Radio (NR) signal without uplink shifting according to one embodiment is shown.

[0008] Figure 3 A downlink signal graph showing an NR signal and an LTE signal using downlink spectrum sharing (DSS) according to one embodiment.

[0009] Figure 4 Signal graphs showing an NR signal and an LTE signal using DSS according to one embodiment.

[0010] Figure 5 is a simplified signal flow diagram of a UE accessing a cell according to one embodiment.

[0011] Figure 6 is a simplified signal flow diagram for handover between a source gNB and a target gNB using DSS and uplink shift according to one embodiment.

[0012] Figure 7 A system according to one embodiment is shown.

[0013] Figure 8 Infrastructure equipment according to one embodiment is shown.

[0014] Fig. 9 A platform according to one embodiment is shown.

[0015] Fig.10 An apparatus according to one embodiment is shown.

[0016] Fig.11 An exemplary interface according to one embodiment is shown.

[0017] Fig.12 Components according to one embodiment are shown. DETAILED DESCRIPTION

[0018] Network communications have begun deploying 5G New Radio (NR) to improve performance. One limitation of using NR to update the network is that some spectrum may currently be used by Long Term Evolution (LTE). Simply using new spectrum can be costly for operators.

[0019] Therefore, operators want to integrate NR communications and LTE communications on the same spectrum. One way to integrate NR communications and LTE communications is downlink spectrum sharing (DSS). However, NR communications and LTE communications may interfere with each other. For example, uplink communications in NR and LTE may interfere. Therefore, NR user equipment (UE) can be configured with uplink shift to prevent such interference.

[0020] However, there are currently some in-service NR UEs that are not configured to provide uplink shifting. Therefore, if these current NR UEs are allowed to operate on the same spectrum as LTE UEs, there will be interference. In contrast, NR UEs using DSS and uplink shifting are able to share the same spectrum as LTE UEs. Therefore, there is a question of whether some, but not all, NR UEs should be allowed to operate simultaneously on the same spectrum as LTE UEs.

[0021] Embodiments herein relate to systems, methods, and apparatus for preventing interference from NR UEs that are not configured for uplink shifting (unconfigured UEs) while allowing access to those NR UEs that have such capabilities (configured UEs). In some embodiments, available information elements are used to prevent unconfigured NR UEs and allow configured UEs to access a cell.

[0022] Various operations will be described in sequence as multiple discrete operations in a manner that is most helpful for understanding the present disclosure. However, the order of description should not be understood to imply that these operations are necessarily order-dependent. Specifically, these operations do not necessarily need to be performed in the order presented.

[0023] Additional details and examples are provided with reference to the following figures. The embodiments of the present disclosure may be understood with reference to the accompanying drawings, wherein like parts are represented by like numbers throughout. The components of the embodiments of the present disclosure as generally described and illustrated in the drawings herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of the systems and methods of the present disclosure is not intended to limit the scope of the present disclosure protected by the claims, but merely represents possible embodiments.

[0024] Figure 1 A frequency domain graph 100 of an LTE signal subcarrier mapping is shown. As shown, an LTE signal uses orthogonal frequency division multiplexing (OFDM) to divide the signal into smaller subcarriers (eg, subcarrier 106 and center subcarrier 102).

[0025] In LTE, the carrier frequency and the center of the carrier (center subcarrier 102) are fixed based on the operating bandwidth of the carrier. The location of the carrier frequency and the center of the carrier is known to both the UE and the network. Placing a subcarrier at the zero frequency position 108 can cause complications for the network. In LTE, to avoid modulating the zero offset (DC) carrier, the subcarriers around the DC carrier are offset by half a subcarrier spacing 104 before applying single carrier (SC)-OFDM. In the illustrated embodiment, the subcarrier is 15kHz and the subcarrier is offset by 7.5kHz. In LTE, the UE is required to perform this uplink shift.

[0026] Figure 2 A frequency domain graph 200 of a NR signal subcarrier mapping without uplink shifting is shown. As shown, the NR signal uses OFDM to divide the signal into smaller subcarriers (e.g., subcarrier 204 and center subcarrier 202).

[0027] Unlike LTE, in NR, the UE can operate for multiple bandwidth parts (BWPs). In NR, the uplink offset of 7.5kHz is generally not implemented. This is because from the network perspective, the use of multiple BWPs means that different UEs operating in different BWPs will have different DC subcarriers. Therefore, the network may not be able to detect and skip the DC subcarrier for each uplink transmission from the UE uplink transmission. Since the position of the subcarriers will constantly change the position of the DC, in NR, the UL shift in LTE is no longer required. Therefore, NR does not have the conventional feature of uplink shifting, and the center subcarrier 202 can remain at the zero frequency position 208.

[0028] Figure 3A downlink signal graph 300 is shown of an NR signal 302 and an LTE signal 304 using downlink spectrum sharing (DSS). A network communication operator may already have spectrum for LTE UEs. The cost of adding new spectrum is very high. Therefore, some operators may want to implement NR on the same spectrum that currently supports LTE.

[0029] Simply switching from LTE to NR only on the required spectrum may cause connectivity issues for LTE UEs that are already in operation. Therefore, it is desirable to support both LTE and NR. One way to reuse the LTE spectrum for NR is to use DSS. DSS allows NR signals 302 to overlay LTE signals 304. If the network handles downlink traffic carefully, LTE UEs can be served without knowing that the network is also serving NR. Similarly, NR UEs may not be aware that LTE UEs are being served.

[0030] Therefore, DSS can be added in NR to allow operators to reuse existing LTE spectrum to deploy NR and still share the existing LTE spectrum with LTE UEs. Both LTE UEs and NR UEs can operate in a carrier using the same spectrum, with LTE UEs communicating with LTE base stations and NR UEs communicating with NR base stations. The same spectrum can be shared when LTE and NR use the same subcarrier spacing (e.g., 15kHz) and the subcarriers are orthogonal (time and frequency aligned). NR can also be operated with 30kHz subcarrier spacing if there is sufficient guard period in the frequency domain between the LTE subcarriers and the NR subcarriers.

[0031] As shown, since the LTE signal 304 and the NR signal 302 are orthogonal to each other, the downlink can be shared without worrying about interference. The orthogonal nature of the two signals minimizes cross-carrier interference. However, as shown in FIG. Figure 3 As mentioned above, there is a problem when considering uplink shift on LTE.

[0032] Figure 4 A signal graph 300 is shown of an NR signal 302 and an LTE signal 304 using DSS. As previously discussed, all LTE UEs use an UL shift (e.g., 7.5kHz), while NR UEs still use the original DC subcarrier. As shown, this makes it impossible for the LTE signal 304 and the NR signal 302 for the uplink to maintain orthogonality.

[0033] Therefore, when the network attempts to sample the carriers to perform a Fast Fourier Transform (FFT) on the received signal from the UE composite transmission, the LTE UE will experience cross-carrier interference due to the shift. In other words, since the LTE UE shifts the UL subcarriers by 7.5kHz, inter-subcarrier interference will occur between the LTE UL subcarriers and the NR UL subcarriers when the LTE UE and NR UE transmit simultaneously.

[0034] To address this issue, NR UEs may also implement a shift to the uplink subcarrier spacing (e.g., a shift of 7.5 kHz) to align with the LTE subcarriers to maintain orthogonality. However, uplink shifting requires new UE functionality in NR UEs to operate in DSS deployments. 3GPP has introduced several NR bands that can be used for DSS along with existing LTE bands. For example, NR bands n38, n40, n48 are expected to be used for DSS along with LTE bands 38, 40, 48, respectively.

[0035] Since the NR UE only needs to use uplink shift on the shared spectrum band, the NR UE can be informed when the uplink shift is adopted. For example, the operation of UL shift of 7.5kHz can be configured by the network in the operating BWP. For example, the shift can be configured via broadcast system information (e.g., in SIB1 in the initial uplink BWP) and / or in the UE-specific BWP using the frequencyShift7p5khz field in the information element. Based on the state of the frequencyShift7p5khz field in the FrequencyInfoUL information element, the NR UE can determine whether the cell is implementing DSS, and if the cell is implementing DSS, determine that the NR UE needs to shift to align its transmission with the LTE UE.

[0036] The introduction of uplink shifting for new and existing bands may cause issues for UEs that do not currently support uplink shifting. New bands may be introduced gradually over a period of time, and typically earlier versions of UEs may implement the newer bands that are introduced. For example, NR band n40 is planned to be introduced, but already released UEs may also implement / support NR band n40.

[0037] In addition, DSS support may be introduced for new or existing bands, and accordingly, uplink shifting functionality may be introduced for these new / existing bands. For example, for NR n40, uplink shifting support of subcarriers may be introduced. Similarly for existing NR bands (e.g., n38), DSS functionality may be introduced to operate with LTE band 38. Therefore, uplink subcarrier shifting functionality may also be introduced for these existing bands (e.g., n38).

[0038] To provide examples of some of the problems that may be introduced, the uplink subcarrier shift functionality introduced to NR band n38 is discussed below, but it should be recognized that this problem may also occur in other bands. If the DSS function is introduced in NR band n38, the uplink subcarrier shift function may also be introduced to prevent interference. However, since NR band n38 already exists, and there may be UEs that have already implemented this band, and these UEs have been provided to customers, support for uplink shift of DSS by UEs supporting n38 is considered non-mandatory. Therefore, there may be UEs that support n38 but do not support DSS and uplink shift, thereby causing interference. So far, 3GPP has introduced (and enforced) support for uplink shift for all frequency division duplex (FDD) bands. In time division duplex (TDD) bands, support for uplink shift of DSS is optional at the UE (as in the case of band n38).

[0039] Problems may arise when there are both UEs that support uplink shifting and UEs that do not support uplink shifting in DSS operation. In existing DSS deployments where UEs connect to the network using DSS, if there are UEs that perform uplink shifting of subcarriers, and if there are also UEs that do not perform uplink shifting, the network may not be able to decode the subcarriers from the UEs that do not perform uplink shifting. The network may perform demodulation of subcarriers using only uplink shifting or demodulation of subcarriers without uplink shifting, but not both at the same time. This may result in decoding errors in uplink transmissions from UEs that do not perform uplink shifting, resulting in loss of connection.

[0040] In order to prevent decoding errors, UEs that do not support uplink shifting can be prevented from residing in cells that operate DSS and uplink shifting. However, with the introduction of DSS / uplink shifting functions on existing frequency bands, there may be a situation where existing UEs that support the frequency band are unaware of the newly introduced DSS / uplink shifting functions in the existing frequency band. Therefore, when the UE attempts to access the network using the frequency band, it may result in loss of service. In addition, since these UEs have been taken away by users / customers for use, it cannot be assumed that these UEs will be updated to this information.

[0041] The following embodiments describe signaling enhancements to handle a situation where existing bands are allowed to use DSS and uplink shifting without causing loss of connectivity with existing UEs that do not support DSS and uplink shifting. These embodiments enable backward compatible adaptation.

[0042] Figure 55 is a simplified signal flow diagram 500 of a UE 502 accessing a cell. In this embodiment, the network node 504 uses cell-baring with additional filters to prevent or allow certain UEs to access the cell. For example, the network node 504 can configure the cell using cell-barring and additional filters to allow any UE to access the cell, restrict access to the cell to those UEs that support DSS and uplink shifting, or completely bar the UE.

[0043] Using only cell barring does not provide the flexibility of allowing some UEs to access a cell while barring other UEs. Cell barring is used by the network as a tool to prevent UEs from accessing a cell. This may be useful for situations where the network may want to perform some bookkeeping activities before opening a cell or for various other reasons. Therefore, typically when the network node 504 is in a cell barring state, the network does not want any UE to randomly access the channel (RACH) and access the cell. In the case of using only cell barring, the network node 504 can only enter two states. For example, if the barring state only bars those UEs that do not support uplink shifting, the network node 504 will not be able to completely bar the cell, and the network node will not be able to prevent UEs that support DSS and uplink shifting from accessing the cell.

[0044] In this embodiment, the network node 504 uses cell barring with one or more additional filters to signal more than two states to the UE (e.g., complete barring, only UEs supporting DSS and uplink shifting, or no barring). To provide the cell barring variables and additional filters, the network node 504 may broadcast one or more messages (e.g., a master information block (MIB) 506 and a system information block (SIB) 508).

[0045] The network node 504 may broadcast the MIB 506. The UE 502 may receive and decode the MIB report 506. The MIB 506 may include a cellBarred field, which may be set to "allowed" or "notAllowed". Legacy UEs that do not support DSS and uplink shifting will not search for additional filters. Therefore, if the cellBarred field is set to "not allowed", the legacy UE will simply assume that the cell is barred and will not attempt to access the cell.

[0046] In contrast, new UEs that support DSS and uplink shifting may be configured to search for one or more additional filters to determine whether the cell is completely barred or only legacy UEs that do not support DSS and uplink shifting are barred. For example, the network node 504 may broadcast additional messages, such as SIB 508 (e.g., SIB1). The UE 502 may receive and decode the SIB 508. The SIB 508 may include the one or more additional filters that indicate to the UE 502 the status of the cell. The additional filters may be fields or information elements that are also broadcast by the network node 504 or sent to the UE 502 via a dedicated message.

[0047] For example, in some implementations, in addition to the FrequencyInfoUL information element in the SIB 508, the network node 504 may also use the cellBarred field in the MIB 506 to convey the cell barring status to the UE 502. The FrequencyInfoUL information element may include a frequencyShift7p5khz field. The frequencyShift7p5khz field may generally indicate that the cell supports frequency shift. However, in this implementation, the frequencyShift7p5khz field may also be used to provide more context about the cell barring status.

[0048] For example, if a network node 504 supporting DSS and uplink shifting wants to completely bar a cell, the network node 504 may broadcast that the cell is barred, and may also not broadcast that the network node supports DSS and uplink shifting even if the network node 504 supports DSS and uplink shifting. In other words, the network node 504 may set the cellBarred field to barred and the frequencyShift7p5khz field to false. In the case where these fields are set to barred and false, a UE 502 supporting DSS and uplink shifting will not attempt to access the cell.

[0049] If the network node 504 wants to allow access to UEs supporting DSS and uplink shift and prohibit legacy UEs that do not support DSS and uplink shift, the network node 504 may set the cellBarred field to prohibited and the frequencyShift7p5khz field to true. If these fields are set to prohibited and true, the network may indicate that UEs supporting DSS and uplink shift are allowed to access the cell. Therefore, if the UE 502 supporting DSS and uplink shift determines that these fields are set to prohibited and true, the UE 502 may access the cell.

[0050] If the network node 504 wants to allow all UEs to access the cell, the network node 504 may set the cellBarred field to “not-barred.” This setting may allow all UEs to access the cell.

[0051] In other embodiments, the one or more additional filters may be a new field that the network node 504 may broadcast. The new field may be an exemption field that explicitly indicates whether a UE supporting DSS and uplink shifting is allowed to reside when the cell barred field is set to barred. If a cell is barred (i.e., the cellBarred field is barred), but the new field indicates that the UE is allowed to reside if the UE supports DSS and uplink shifting, then a UE supporting DSS and uplink shifting may access the cell. If a cell is barred and the new field indicates that the UE is not allowed to reside even if the UE supports DSS and UL shifting, then the cell is considered completely barred and no UE is allowed to access the cell.

[0052] Adding this new field can provide the network with flexibility so that it can not modify any existing broadcasts, but only change the new field and the cell barring field. In this embodiment, the network node 504 sets cellBarred to barred and keeps the frequencyShift7p5khz value unchanged, but adds a new field in the broadcast message (e.g., SIB1) that indicates whether UEs supporting DSS and uplink shift are allowed to stay or whether these UEs are also barred. Therefore, in this embodiment, the initial BWP configuration carrying frequencyShift7p5khz is not changed.

[0053] The UE 502 may also check 510 support for BWP with respect to a specific subcarrier spacing to determine if the UE 502 is barred. An information element including a frequencyShift7p5khz field or a new exemption field may be defined per BWP.

[0054] In some embodiments, if the network node 504 intends to use DSS and uplink shift only with a specific subcarrier spacing (SCS) (e.g., with 15kHz SCS) but not with 30kHz SCS (configured using a separate BWP), then barring access to the cell by the UE may be based on the UE's support for uplink shift on the initial BWP. In other words, when the cellBarred field is set to true, the UE 502 may check support for DSS and uplink shift only for the initial BWP relative to the SCS configured by the initial BWP.

[0055] In some embodiments, if the network node 504 intends to use DSS and uplink shift only with a specific subcarrier spacing (SCS) (e.g., with 15kHz SCS) but not with 30kHz SCS (configured using a separate BWP), then barring access to the cell by the UE 502 may be based on the UE's support for DSS and uplink shift on the configured BWP. In other words, when the cellBarred field is set to true, the UE 502 may check support for DSS and uplink shift for all BWPs relative to the SCS provided by the broadcasted information. When the UE 502 supports DSS and uplink shift for all BWPs and SCSs supported by the UE, the UE 502 may access the cell.

[0056] After the UE 502 determines that it has an accessible cell, the UE 502 can communicate with the network node 504 and transmit 512 data.

[0057] Figure 6 600 is a simplified signal flow diagram of a handover between a source gNB 604 and a target gNB 606 using DSS and uplink shifting. As shown, a UE 602 can be in a connected mode 608 with the source gNB 604. The UE 602 and the source gNB 604 can perform data transmission 610.

[0058] The source gNB 604 may at some point intend 616 to perform a handover of the UE 602. However, the target gNB 606 may be using DSS and uplink shifting, while the source gNB 604 is not. Therefore, the source gNB 604 may not be aware of the UE's ability to use DSS and uplink shifting.

[0059] In the illustrated embodiment, the UE signals a report 614 to the source gNB 604 regarding its support for DSS and UL shifting. In some embodiments, the report 614 may indicate the DSS and uplink shifting capabilities for each band supported by the UE (e.g., whether DSS and uplink shifting are possible for each of these bands).

[0060] The source gNB 604 may use the DSS and uplink shift information to determine whether to proceed with the handover. In the illustrated embodiment, if the UE supports DSS and UL shift on the frequency band on which the target gNB 606 is operating, the handover is triggered 612. If the UE 602 does not support DSS and uplink shift, the source gNB 604 does not handover the UE 602 to the target gNB 606. In some embodiments, the source gNB 604 may check that the UE 602 supports uplink shift for all BWPs relative to the SCS. In some embodiments, the source gNB 604 may check that the UE 602 supports uplink shift only for the initial BWP relative to the specific SCS configured for the target network node for the initial BWP.

[0061] The source gNB 604 may perform 618 handover coordination and UE capability transmission. In some embodiments, this may include providing information from report 614 indicating the DSS for each band supported by the UE and the uplink shift capability. After the handover, the UE 602 and the target gNB 606 may transmit 620 data.

[0062] Figure 7 An exemplary architecture of a system 700 of a network according to various embodiments is shown. The following description is provided for an example system 700 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0063] like Figure 7As shown, system 700 includes UE 722 and UE 720. In this example, UE 722 and UE 720 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument clusters (ICs), heads-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0064] In some embodiments, UE 722 and / or UE 720 may be IoT UEs, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. IoT UEs may utilize technologies such as M2M or MTC to exchange data with MTC servers or devices via PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. IoT networks describe interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to IoT networks.

[0065] UE 722 and UE 720 may be configured to be connected, e.g., communicatively coupled, to an access node or radio access node (shown as (R) AN 708). In an embodiment, (R) AN 708 may be an NG RAN or SG RAN, an E-UTRAN, or a traditional RAN, such as a UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to an (R) AN 708 operating in an NR or SG system, and the term "E-UTRAN" or the like may refer to an (R) AN 708 operating in an LTE or 4G system. UE 722 and UE 720 utilize connections (or channels) (shown as connection 704 and connection 702, respectively), each of which includes a physical communication interface or layer (discussed in further detail below).

[0066] In this embodiment, connection 704 and connection 702 are air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a SG protocol, a NR protocol, and / or any of the other communication protocols discussed herein. In an embodiment, UE 722 and UE 720 may directly exchange communication data via a ProSe interface 710. The ProSe interface 710 may alternatively be referred to as a side link (SL) interface 110, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0067] UE 720 is shown as being configured to access AP 712 (also referred to as a "WLAN node," "WLAN," "WLAN terminal," "WT," etc.) via connection 724. Connection 724 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 712 would include Wireless Fidelity. router. In this example, AP 712 may be connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 720, (R) AN 708, and AP 712 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 720 in RRC_CONNECTED being configured by RAN node 714 or RAN node 716 to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 720 using WLAN radio resources (e.g., connection 724) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through connection 724. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0068] (R)AN 708 may include one or more nodes that implement connection 704 and connection 702, such as RAN node 714 and RAN node 716. As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functions for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, 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). As used herein, the terms "NG RAN node" and the like may refer to RAN nodes (e.g., gNBs) operating in NR or SG systems, while the terms "E-UTRAN nodes" and the like may refer to RAN nodes (e.g., eNBs) operating in LTE or 4G systems 700. According to various embodiments, the RAN node 714 or the RAN node 716 may be implemented as one or more of dedicated physical devices such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0069] In some embodiments, all or part of the RAN node 714 or RAN node 716 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional splits, such as PDCP splits, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes (e.g., RAN node 714 or RAN node 716); MAC / PHY splits, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes (e.g., RAN node 714 or RAN node 716); or "lower PHY" splits, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes. This virtualization framework allows idle processor cores of the RAN node 714 or RAN node 716 to execute other virtualized applications. In some specific implementations, each RAN node may represent a node via each F1 interface ( Figure 7In some implementations, the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CUs may be operated by a server (not shown) located in the (R)AN 708 or by a server pool in a manner similar to the CRAN / vBBUP. In addition or alternatively, the RAN node 714 or one or more of the RAN nodes 716 may be a next generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminations to the UE 722 and the UE 720 and is connected to the SGC via an NG interface (discussed below). In a V2X scenario, one or more of the RAN node 714 or the RAN node 716 may be an RSU or act as an RSU.

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

[0071] The RAN node 714 and / or the RAN node 716 may terminate the air interface protocol and may be the first point of contact for the UE 722 and the UE 720. In some embodiments, the RAN node 714 and / or the RAN node 716 may perform various logical functions of the (R)AN 708, 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.

[0072] In an embodiment, UE 722 and UE 720 may be configured to communicate with each other or with RAN node 714 and / or RAN node 716 over a multi-carrier communication channel using OFDM communication signals according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0073] In some embodiments, a downlink resource grid may be used for downlink transmissions from RAN node 714 and / or RAN node 716 to UE 722 and UE 720, 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 radio 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.

[0074] According to various embodiments, UE 722 and UE 720 and RAN node 714 and / or RAN node 716 communicate data (e.g., transmit data and receive data) through a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed frequency band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed frequency band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz frequency band.

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

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

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

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

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

[0080] The PDSCH carries user data and higher layer signaling to the UE 722 and UE 720. The PDCCH carries, among other information, information about the transport format and resource allocation related to the PDSCH channel. It may also inform the UE 722 and UE 720 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to the UE 720 within the cell) may be performed at either the RAN node 714 or the RAN node 716 based on channel quality information fed back from either the UE 722 and UE 720. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the UE 722 and UE 720.

[0081] PDCCH uses 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 nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and 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).

[0082] 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 EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0083] The RAN node 714 or the RAN node 716 may be configured to communicate with each other via the interface 730. In an embodiment where the system 700 is an LTE system (e.g., when the CN 706 is an EPC), the interface 730 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes (e.g., two or more eNBs, etc.) connected to the EPC, and / or between two eNBs connected to the EPC. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful delivery of PDCP PDUs from the SeNB to the UE 722 in sequence for user data; information about PDCP PDUs that are not delivered to the UE 722; information about the current minimum expected buffer size at the Se NB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from source eNB to target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0084] In an embodiment where the system 700 is an SG or NR system (e.g., when the CN 706 is an SGC), the interface 730 may be an Xn interface. The Xn interface is defined between two or more RAN nodes (e.g., two or more gNBs, etc.) connected to the SGC, between a RAN node 714 (e.g., a gNB) and an eNB connected to the SGC, and / or between two eNBs connected to a 5GC (e.g., CN 706). In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for the UE 722 in a connected mode (e.g., a CM connection) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 714 or RAN nodes 716. Mobility support may include context transfer from the old (source) service RAN node 714 to the new (target) service RAN node 716; and control of the user plane tunnel between the old (source) service RAN node 714 and the new (target) service RAN node 716. The protocol stack of Xn-U may include a transport network layer built on the Internet Protocol (IP) transport layer, and a GTP-U layer on top of the UDP and / or IP layer for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0085] (R)AN 708 is shown as being communicatively coupled to the core network—in this embodiment, communicatively coupled to CN 706. CN 706 may include one or more network elements 732 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 722 and UE 720) connected to CN 706 via (R)AN 708. The components of CN 706 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). The logical instantiation of CN 706 may be referred to as a network slice, and the logical instantiation of a portion of CN 706 may be referred to as a network sub-slice. The NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0086] In general, the application server 718 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 718 may also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.) for UE 722 and UE 720 via the EPC. The application server 718 may communicate with the CN 706 via the IP communication interface 736.

[0087] In an embodiment, CN 706 may be an SGC, and (R)AN 116 may be connected to CN 706 via an NG interface 734. In an embodiment, NG interface 734 may be divided into two parts: an NG user plane (NG-U) interface 726, which carries traffic data between RAN node 714 or RAN node 716 and UPF; and an S1 control plane (NG-C) interface 728, which is a signaling interface between RAN node 714 or RAN node 716 and AMF.

[0088] In an embodiment, CN 706 may be an SG CN, while in other embodiments, CN 706 may be an EPC. In the case where CN 706 is an EPC, (R)AN 116 may be connected to CN 706 via an S1 interface 734. In an embodiment, S1 interface 734 may be divided into two parts: an S1 user plane (S1-U) interface 726, which carries traffic data between RAN node 714 or RAN node 716 and S-GW; and an S1-MME interface 728, which is a signaling interface between RAN node 714 or RAN node 716 and MME.

[0089] Figure 8 An example of infrastructure equipment 800 according to various embodiments is illustrated. The infrastructure equipment 800 can be implemented as a base station, a radio head, a RAN node, an AN, an application server, and / or any other element / device discussed herein. In other examples, the infrastructure equipment 800 can be implemented in or by a UE.

[0090] The infrastructure equipment 800 includes application circuits 802, baseband circuits 804, one or more radio front-end modules 806 (RFEM), memory circuits 808, power management integrated circuits (shown as PMIC 810), power tee circuits 812, network controller circuits 814, network interface connectors 820, satellite positioning circuits 816, and user interface circuits 818. In some embodiments, the infrastructure equipment 800 may include additional elements such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, these components may be included in more than one device. For example, the circuits may be included separately in more than one device for CRAN, vBBU, or other similar implementations. The application circuits 802 include circuits such as, but not limited to: one or more processors (or processor cores), cache memory, and one or more of the following: low dropout regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I 2C or general programmable serial interface module, real-time clock (RTC), timer-counter including interval timer and watchdog timer, general input / output (I / O or IO), memory card controller such as secure digital (SD) multimedia card (MMC) or similar products, universal serial bus (USB) interface, mobile industry processor interface (MIPI) interface and joint test access group (JTAG) test access port. The processor (or core) of the application circuit 802 can be coupled with or can include a memory / storage element and can be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the infrastructure equipment 800. In some specific implementations, the memory / storage element can be an on-chip memory circuit, which can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory and / or any other type of memory device technology, such as those discussed herein.

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

[0092] In some implementations, the application circuit 802 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs), and the like; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), and the like; ASICs, such as structured ASICs, and the like; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of the application circuit 802 may include logic blocks or logic structures, as well as other interconnected resources that may be programmed to perform various functions, such as the processes, methods, functions, and the like of the various embodiments discussed herein. In such embodiments, the circuitry of the application circuit 802 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, and the like)) for storing logic blocks, logic structures, data, and the like in a lookup table (LUT), and the like. Baseband circuitry 804 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0093] The user interface circuitry 818 may include one or more user interfaces designed to enable a user to interact with the infrastructure equipment 800 or a peripheral component interface designed to enable a peripheral component to interact with the infrastructure equipment 800. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touch pad, a touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0094] The radio front end module 806 may include a millimeter wave (mmWave) radio front end module (RFEM) and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 806 that combines both millimeter wave antennas and sub-millimeter waves.

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

[0096] The PMIC 810 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or capacitor. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 812 may provide power extracted from a network cable to provide both power and data connections for the infrastructure equipment 800 using a single cable.

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

[0098] The positioning circuit 816 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a global satellite navigation system (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's Beidou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc. for navigation), etc. The positioning circuit 816 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 816 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 816 may also be part of or interact with the baseband circuit 804 and / or the radio front end module 806 to communicate with nodes and components of the positioning network. The positioning circuit 816 may also provide location data and / or time data to the application circuit 802, which may use the data to synchronize operations with various infrastructures, etc. Figure 8 The components shown may communicate with each other using interface circuitry that may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCix), PCI express (PCie), or any number of other technologies. The bus / IX may be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems may be included, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0099] Fig. 9 An example of a platform 900 according to various embodiments is shown. In an embodiment, the computer platform 900 may be suitable for use as a UE, an application server, and / or any other element / device discussed herein. The platform 900 may include any combination of components shown in the example. The components of the platform 900 may be implemented as an integrated circuit (IC), part of an IC, a discrete electronic device, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 900, or implemented as components otherwise incorporated within the chassis of a larger system. Fig. 9 The block diagram is intended to show a high-level view of the components of computer platform 900. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

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

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

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

[0103] Additionally or alternatively, the application circuit 902 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, etc.; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 902 may include logic blocks or logic structures, and other interconnected resources that may be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 902 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in a lookup table (LUT), etc.

[0104] Baseband circuit 904 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0105] The radio front end module 906 may include a millimeter wave (mmWave) radio front end module (RFEM) and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 906 that combines both millimeter wave antennas and sub-millimeter waves.

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

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

[0108] Platform 900 may also include interface circuitry (not shown) for connecting external devices to platform 900. External devices connected to platform 900 via the interface circuitry include sensors 922 and electromechanical components (shown as EMC 924), as well as removable memory devices coupled to removable memory 926.

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

[0110] EMC 924 includes devices, modules or subsystems for the purpose of enabling platform 900 to change its state, position and / or orientation or to move or control mechanisms or (sub) systems. In addition, EMC 924 may be configured to generate messages / signaling and send messages / signaling to other components of platform 900 to indicate the current state of EMC 924. Examples of EMC 924 include one or more power switches, relays (including electromechanical relays (EMR) and / or solid-state relays (SSR)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks and / or other similar electromechanical components. In an embodiment, platform 900 is configured to operate one or more EMC 924 based on one or more capture events and / or instructions or control signals received from service providers and / or various clients. In some specific implementations, an interface circuit may connect platform 900 to positioning circuit 916. The positioning circuit 916 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) may include the United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's Beidou navigation satellite system, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.), etc. The positioning circuit 916 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 916 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 916 may also be part of or interact with the baseband circuit 904 and / or the radio front-end module 906 to communicate with nodes and components of the positioning network. Positioning circuitry 916 may also provide location data and / or time data to application circuitry 902, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations) for use in turn-by-turn navigation applications, and the like.

[0111] In some implementations, the interface circuit may connect the platform 900 to a near field communication circuit (shown as NFC circuit 912). The NFC circuit 912 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, wherein magnetic field induction is used to enable communication between the NFC circuit 912 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 900. The NFC circuit 912 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to the NFC circuit 912 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit a short-range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 912, or initiate data transfer between the NFC circuit 912 and another active NFC device (e.g., a smart phone or an NFC-enabled POS terminal) near the platform 900.

[0112] The driver circuit 918 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 900. The driver circuit 918 may include separate drivers to allow other components of the platform 900 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 900. For example, the driver circuit 918 may include a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface of the platform 900, a sensor driver for obtaining sensor readings of a sensor 922 and controlling and allowing access to the sensor 922, an EMC driver for obtaining actuator positions of an EMC 924 and / or controlling and allowing access to the EMC 924, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0113] A power management integrated circuit (shown as PMIC 910) (also referred to as a "power management circuit") may manage the power provided to various components of the platform 900. Specifically, the PMIC 910 may control power selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuit 904. The PMIC 910 may typically be included when the platform 900 is capable of being powered by a battery 914, for example, when the device is included in a UE.

[0114] In some embodiments, the PMIC 910 may control or otherwise be part of various power saving mechanisms of the platform 900. For example, if the platform 900 is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the platform 900 may be powered off for short time intervals, thereby saving power. If there is no data service activity for an extended period of time, the platform 900 may transition to the RRC_Idle state, in which the device is disconnected from the network and no operations such as channel quality feedback, switching, etc. are performed. The platform 900 enters a very low power state and performs paging, in which the device wakes up again periodically to listen to the network and then powers off again. The platform 900 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to a few hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0115] The battery 914 can provide power to the platform 900, but in some examples, the platform 900 can be mounted and deployed in a fixed location and can have a power source coupled to the power grid. The battery 914 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, the battery 914 can be a typical lead-acid car battery.

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

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

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

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

[0120] Fig.10 Exemplary components of device 1000 according to some embodiments are shown. In some embodiments, device 1000 may include at least an application circuit 1006, a baseband circuit 1004, a radio frequency (RF) circuit (shown as RF circuit 1002), a front-end module (FEM) circuit (shown as FEM circuit 1032), one or more antennas 1030, and a power management circuit (PMC) (shown as PMC 1034) coupled together as shown in the figure. The components of the illustrated device 1000 may be included in a UE or a RAN node. In some embodiments, device 1000 may include fewer elements (for example, a RAN node may not utilize application circuit 1006, but include a processor / controller to process IP data received from an EPC). In some embodiments, device 1000 may include additional elements, such as a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the following components may be included in more than one device (for example, the circuit may be separately included in more than one device for a specific implementation of a cloud-RAN (C-RAN)).

[0121] The application circuit 1006 may include one or more application processors. For example, the application circuit 1006 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The one or more 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 1000. In some embodiments, the processor of the application circuit 1006 may process IP data packets received from the EPC.

[0122] The baseband circuit 1004 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 1004 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 1002 and generate baseband signals for the transmit signal path of the RF circuit 1002. The baseband circuit 1004 may interact with the application circuit 1006 to generate and process baseband signals and control the operation of the RF circuit 1002. For example, in some embodiments, the baseband circuit 1004 may include a third generation (3G) baseband processor (3G baseband processor 1008), a fourth generation (4G) baseband processor (4G baseband processor 1010), a fifth generation (5G) baseband processor (5G baseband processor 1012), or other baseband processors 1014 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 1004 (e.g., one or more baseband processors in the baseband processor) can handle various radio control functions that implement communication with one or more radio networks via the RF circuit 1002. In other embodiments, part or all of the functions of the exemplary baseband processor may be included in a module stored in the memory 1020 and executed via the central processing unit (CPU 1016). The 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 circuit of the baseband circuit 1004 may include a fast Fourier transform (FFT), precoding, or constellation mapping / demapping function. In some embodiments, the encoding / decoding circuit of the baseband circuit 1004 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.

[0123] In some embodiments, the baseband circuit 1004 may include a digital signal processor (DSP), such as one or more audio DSPs 1018. The one or more audio DSPs 1018 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 1004 and the application circuit 1006 may be implemented together, for example, on a system on a chip (SOC).

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

[0125] RF circuit 1002 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 1002 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 1002 may include a receive signal path, which may include circuitry for down-converting an RF signal received from FEM circuit 1032 and providing a baseband signal to baseband circuit 1004. RF circuit 1002 may also include a transmit signal path, which may include circuitry for up-converting a baseband signal provided by baseband circuit 1004 and providing an RF output signal for transmission to FEM circuit 1032.

[0126] In some embodiments, the receive signal path of the RF circuit 1002 may include a mixer circuit 1022, an amplifier circuit 1024, and a filter circuit 1026. In some embodiments, the transmit signal path of the RF circuit 1002 may include a filter circuit 1026 and the mixer circuit 1022. The RF circuit 1002 may also include a synthesizer circuit 1028 for synthesizing frequencies used by the mixer circuits 1022 of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 1022 of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1032 based on the synthesized frequency provided by the synthesizer circuit 1028. The amplifier circuit 1024 may be configured to amplify the down-converted signal, and the filter circuit 1026 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 1004 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 1022 of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0127] In some embodiments, mixer circuit 1022 of the transmit signal path may be configured to up-convert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 1028 to generate an RF output signal for FEM circuit 1032. The baseband signal may be provided by baseband circuit 1004 and may be filtered by filter circuit 1026.

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

[0129] 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 1002 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 1004 may include a digital baseband interface to communicate with RF circuit 1002.

[0130] 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.

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

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

[0133] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by baseband circuitry 1004 or application circuitry 1006 (such as an application processor) 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 application circuitry 1006.

[0134] The synthesizer circuit 1028 of the RF circuit 1002 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.

[0135] In some embodiments, the synthesizer circuit 1028 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 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 1002 can include an IQ / polarity converter.

[0136] FEM circuitry 1032 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 1030, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 1002 for further processing. FEM circuitry 1032 may also include a transmit signal path that may include circuitry configured to amplify a transmit signal provided by RF circuitry 1002 for transmission by one or more of one or more antennas 1030. In various embodiments, amplification by either the transmit signal path or the receive signal path may be performed only in RF circuitry 1002, only in FEM circuitry 1032, or in both RF circuitry 1002 and FEM circuitry 1032.

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

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

[0139] Fig.10 PMC 1034 is shown coupled only to baseband circuitry 1004. However, in other embodiments, PMC 1034 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 1006, RF circuitry 1002, or FEM circuitry 1032) and perform similar power management operations for these components.

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

[0141] If there is no data traffic activity for an extended period of time, the device 1000 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, handovers, etc. The device 1000 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 1000 cannot receive data in this state, and in order to receive data, the device must transition back to the RRC_Connected state.

[0142] 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.

[0143] The processor of the application circuit 1006 and the processor of the baseband circuit 1004 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 1004 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 1006 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.

[0144] Fig.11 An exemplary interface 1100 of a baseband circuit according to some embodiments is shown. As discussed above, Fig.10 The baseband circuit 1004 may include a 3G baseband processor 1008, a 4G baseband processor 1010, a 5G baseband processor 1012, other baseband processors 1014, a CPU 1016, and a memory 1020 utilized by the processors. As shown, each of the processors may include a corresponding memory interface 1102 for sending / receiving data to / from the memory 1020.

[0145] The baseband circuit 1004 may also include one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 1104 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1004), an application circuit interface 1106 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1004), and an application circuit interface 1107 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1004). Fig.10 The application circuit 1006 sends / receives data), the RF circuit interface 1108 (for example, for sending / receiving data to / from Fig.10 an interface for sending / receiving data to / from the RF circuit 1002), a wireless hardware connection interface 1110 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g. Low power consumption), components and other communication components to send / receive data) and a power management interface 1112 (for example, an interface for sending / receiving power or control signals to / from the PMC 1034).

[0146] Fig.12 1 is a block diagram illustrating a component 1200 capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Fig.12 A schematic diagram of hardware resources 1202 is shown, which includes one or more processors 1206 (or processor cores), one or more memory / storage devices 1214, and one or more communication resources 1224, each of which can be communicatively coupled via a bus 1216. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1222 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1202.

[0147] Processor 1206 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1208 and processor 1210.

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

[0149] The communication resources 1224 may include interconnect or network interface components or other suitable devices to communicate with one or more peripheral devices 1204 or one or more databases 1220 via the network 1218. For example, the communication resources 1224 may include wired communication components (e.g., for coupling via a universal serial bus (USB)), cellular communication components, NFC components, Parts (such as Low power consumption), components and other communication components.

[0150] The instructions 1212 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1206 to perform any one or more of the methods discussed herein. The instructions 1212 may reside completely or partially in at least one of the processors 1206 (e.g., within a cache memory of the processor), the memory / storage device 1214, or any suitable combination thereof. In addition, any portion of the instructions 1212 may be transmitted to the hardware resources 1202 from any combination of the peripheral device 1204 or the database 1220. Therefore, the memory of the processor 1206, the memory / storage device 1214, the peripheral device 1204, and the database 1220 are examples of computer-readable and machine-readable media.

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

[0152] Examples

[0153] The following examples relate to additional embodiments.

[0154] Embodiment 1 is a method for a user equipment (UE) supporting dynamic spectrum sharing (DSS) and uplink (UL) shift, the method comprising: receiving a first message from a network node, the first message comprising a cell prohibition field; decoding the first message and determining a state of the cell prohibition field; receiving a second message from the network node, the second message comprising a second field related to support for UL shift; decoding the second message and determining a state of the second field; accessing the cell when the cell prohibition field is set to prohibit and the second field indicates that a UE supporting DSS and UL shift is allowed to access the cell.

[0155] Embodiment 2 is a method according to embodiment 1, wherein the second field is a frequencyShift7p5khz field, wherein when the frequencyShift7p5khz field is set to false and the cell prohibition field is set to prohibit, the cell is completely prohibited, and wherein when the frequencyShift7p5khz field is set to true and the cell prohibition field is set to prohibit, these UEs supporting DSS and UL shift are allowed to access the cell.

[0156] Embodiment 3 is a method according to embodiment 1, wherein the second field is an exemption field, which explicitly indicates whether the UEs supporting DSS and UL shift are allowed to stay when the cell prohibition field is set to prohibit.

[0157] Embodiment 4 is a method according to Embodiment 1, further comprising checking whether the UE supports UL shift only for an initial bandwidth part (BWP) relative to a specific subcarrier spacing (SCS) configured for the initial BWP, and wherein when the UE supports UL shift for the initial BWP, the UE accesses the cell.

[0158] Embodiment 5 is a method according to embodiment 1, further comprising checking whether the UE supports UL shifting for all BWPs relative to the SCS provided by the broadcast information, and wherein the UE accesses the cell only when the UE supports UL shifting for all BWPs.

[0159] Embodiment 6 is a method according to embodiment 1, wherein the first message is a master information block (MIB) and the second message is a system information block 1 (SIB1).

[0160] Embodiment 7 is a method according to embodiment 1, wherein the second field is provided in a FrequencyInfoUL information element.

[0161] Embodiment 8 is a method according to embodiment 1, further comprising reporting to the network node a UL shift capability for each frequency band supported by the UE.

[0162] Embodiment 9 is a user equipment (UE) supporting dynamic spectrum sharing (DSS) and uplink (UL) shift, the UE comprising: a baseband processing unit; and a memory storing instructions which, when executed by the baseband processing unit, configure the UE to: receive a first message from a network node, the first message comprising a cell prohibition field; decode the first message and determine the state of the cell prohibition field; receive a second message from the network node, the second message comprising a second field related to support for UL shift; decode the second message and determine the state of the second field; and access the cell when the cell prohibition field is set to prohibit and the second field indicates that a UE supporting DSS and UL shift is allowed to access the cell.

[0163] Embodiment 10 is a calculation UE according to embodiment 9, wherein the second field is a frequencyShift7p5khz field, wherein when the frequencyShift7p5khz field is set to false and the cell prohibition field is set to prohibit, the cell is completely prohibited, and wherein when the frequencyShift7p5khz field is set to true and the cell prohibition field is set to prohibit, these UEs supporting DSS and UL shift are allowed to access the cell.

[0164] Embodiment 11 is a calculation UE according to embodiment 9, wherein the second field is an exemption field, and the exemption field explicitly indicates whether these UEs supporting DSS and UL shift are allowed to stay when the cell prohibition field is set to prohibit.

[0165] Embodiment 12 is a computing UE according to embodiment 9, wherein the instructions further configure the device to check whether the UE supports UL shift only for an initial bandwidth part (BWP) relative to a specific subcarrier spacing (SCS) configured for the initial BWP, and wherein when the UE supports UL shift for the initial BWP, the UE accesses the cell.

[0166] Embodiment 13 is a computing UE according to embodiment 9, wherein the instructions further configure the apparatus to check whether the UE supports UL shifting for all BWPs relative to the SCS provided by the broadcast information, and wherein the UE accesses the cell only if the UE supports UL shifting for all BWPs.

[0167] Embodiment 14 is a computing UE according to embodiment 9, wherein the first message is a master information block (MIB) and the second message is a system information block 1 (SIB1).

[0168] Embodiment 15 is a calculation UE according to embodiment 9, wherein the second field is provided in the FrequencyInfoUL information element.

[0169] Embodiment 16 is a computing UE according to embodiment 9, wherein the instructions further configure the apparatus to report to the network node the UL shift capability for each frequency band supported by the UE.

[0170] Embodiment 17 is a method for a source network node, the method comprising: connecting with a UE; determining that the source network node intends to switch the UE to a target network node using dynamic spectrum sharing (DSS) and uplink (UL) shift; receiving a report indicating whether the UE supports DSS and UL shift; and if the UE supports DSS and UL shift, performing switching of the UE to the target network node.

[0171] Embodiment 18 is a method according to embodiment 17, further comprising checking that the UE supports UL shifting only for an initial bandwidth part (BWP) relative to a specific subcarrier spacing (SCS) configured for the target network node for the BWP.

[0172] Embodiment 19 is a method according to embodiment 17, further comprising checking, relative to an SCS for the network node, that the UE supports UL shifting for all BWPs.

[0173] Embodiment 20 is a method according to embodiment 17, wherein the report indicates DSS and UL shift capability for each frequency band supported by the UE.

[0174] Embodiment 21 may include an apparatus comprising means for performing one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0175] Embodiment 22 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0176] Embodiment 23 may include a device comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of the above embodiments or any other method or process described herein.

[0177] Embodiment 24 may include methods, techniques or processes described in or related to any of the above embodiments, or parts or components thereof.

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

[0179] Embodiment 26 may include signals or parts or components thereof as described in or related to any of the above embodiments.

[0180] Embodiment 27 may include a datagram, packet, frame, segment, protocol data unit (PDU) or message or a portion or component thereof as described in or related to any of the above embodiments, or content otherwise described in the present disclosure.

[0181] Embodiment 28 may include a signal encoded with data or a portion or component thereof as described in or related to any of the above embodiments, or content described in other ways in this disclosure.

[0182] Embodiment 29 may include a signal or a portion or component thereof encoded with a datagram, packet, frame, segment, PDU or message as described in or related to any of the above embodiments, or content described in other ways in the present disclosure.

[0183] Embodiment 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any of the above embodiments.

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

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

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

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

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

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

[0190] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations, or may include a combination of hardware, software, and / or firmware.

[0191] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment.

[0192] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0193] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method for a user equipment UE supporting dynamic spectrum sharing (DSS) and uplink (UL) shift, the method comprising: receiving a first message from a network node, the first message comprising a cell barring field; decoding the first message and determining a state of the cell barring field; receiving a second message from the network node, the second message comprising a second field related to prohibiting UEs supporting DSS and UL shifting, and a third field related to support for UL shifting; decoding the second message and determining the states of the second field and the third field, wherein the second field is an exemption field, the exemption field explicitly indicating whether the UE supporting DSS and UL shift is allowed to stay when the cell barring field is set to barred, and wherein the third field is frequencyShift7p5khz Fields; as well as When the cell barring field is set to barring and the second field indicates that the UE supporting DSS and UL shift is allowed to access the cell, and the third field is set to true, access the cell.

2. The method according to claim 1 also includes checking whether the UE supports UL shifting only for the initial bandwidth part BWP relative to a specific subcarrier spacing SCS configured for the initial BWP, and wherein when the UE supports UL shifting for the initial BWP, the UE accesses the cell.

3. The method according to claim 1, further comprising checking whether the UE supports UL shifting for all BWPs with respect to the SCS provided by broadcast information, and wherein the UE accesses the cell only when the UE supports UL shifting for all BWPs. 4 . The method of claim 1 , wherein the first message is a Master Information Block (MIB) and the second message is a System Information Block 1 (SIB1).

5. The method according to claim 1, wherein FrequencyInfoUL The second field is provided in an information element.

6. The method of claim 1, further comprising reporting to the network node a UL shift capability for each frequency band supported by the UE.

7. A user equipment UE supporting dynamic spectrum sharing DSS and uplink UL shift, the UE comprising: Baseband processing unit; and A memory storing instructions, which, when executed by the baseband processing unit, configure the UE to: receiving a first message from a network node, the first message comprising a cell barring field; decoding the first message and determining a state of the cell barring field; receiving a second message from the network node, the second message comprising a second field related to prohibiting UEs supporting DSS and UL shifting, and a third field related to support for UL shifting; decoding the second message and determining the states of the second field and the third field, wherein the second field is an exemption field, the exemption field explicitly indicating whether the UE supporting DSS and UL shift is allowed to stay when the cell barring field is set to barred, and wherein the third field is frequencyShift7p5khz Fields; as well as When the cell barring field is set to barring and the second field indicates that the UE supporting DSS and UL shift is allowed to access the cell, and the third field is set to true, access the cell.

8. The UE according to claim 7, wherein the instruction further configures the UE to check whether the UE supports UL shifting only for the initial bandwidth part BWP relative to a specific subcarrier spacing SCS configured for the initial BWP, and wherein when the UE supports UL shifting for the initial BWP, the UE accesses the cell.

9. The UE of claim 7, wherein the instruction further configures the UE to check whether the UE supports UL shifting for all BWPs relative to the SCS provided by broadcast information, and wherein the UE accesses the cell only if the UE supports UL shifting for all BWPs.

10. The UE of claim 7, wherein the first message is a master information block (MIB), and the second message is a system information block 1 (SIB1).

11. The UE according to claim 7, wherein FrequencyInfoUL The second field is provided in an information element.

12. The UE of claim 7, wherein the instructions further configure the UE to report to the network node a UL shift capability for each frequency band supported by the UE.

13. A method for a source network node, the method comprising: Connect with UE; Determining that the source network node is to hand over the UE to a target network node using dynamic spectrum sharing (DSS) and uplink (UL) shift; receiving a report indicating whether the UE supports DSS and UL shift; as well as If the UE supports DSS and UL shift, performing handover of the UE to the target network node includes: receiving a first message from the target network node, the first message comprising a cell barring field; decoding the first message and determining a state of the cell barring field; receiving a second message from the target network node, the second message comprising a second field related to disabling UEs supporting DSS and UL shifting, and a third field related to support for UL shifting; decoding the second message and determining the states of the second field and the third field, wherein the second field is an exemption field, the exemption field explicitly indicating whether the UE supporting DSS and UL shift is allowed to stay when the cell barring field is set to barred, and wherein the third field is frequencyShift7p5khz Fields; and When the cell barring field is set to barring and the second field indicates that the UE supporting DSS and UL shifting is allowed to access the cell, and the third field is set to true, the handover of the UE to the target network node is performed.

14. The method according to claim 13, further comprising checking that the UE supports UL shifting only for an initial bandwidth part BWP relative to a specific subcarrier spacing SCS configured for the target network node.

15. The method of claim 13, further comprising checking that the UE supports UL shifting for all BWPs relative to an SCS for the network node.

16. The method of claim 13, wherein the report indicates DSS and UL shift capability for each frequency band supported by the UE.

Images