Apparatus and method for dynamic uplink transmission handover

Abstract

A method of operating a user equipment (UE) configured to perform uplink (UL) transmission handover on more than two configured frequency bands includes configuring first and second transmission chains of the UE for transmission on at least one frequency band of a set of frequency bands including a first frequency band and a second frequency band, receiving an indication of UL transmission, the UL transmission requires the UE to perform transmission chain (Tx) switching to use a third frequency band different from the first frequency band and the second frequency band. The UE determines a handover gap duration based on the UL transmission requiring the UE to perform a Tx handover to use a third frequency band. And the UE executes Tx switching, and executes UL transmission after waiting for at least the switching gap duration.

Description

Technical Field

[0001] The present disclosure relates to wireless communication networks, and more particularly to systems and methods for performing uplink transmission switching. Background Art

[0002] Carrier aggregation (CA) is used in new radio NR (5G) and long term evolution (LTE) systems to improve the transmit / receive data rates of user equipment (UE) connected to the network. With CA, the UE typically initially operates on a single serving cell called a primary cell (or PCell). The PCell operates on a component carrier in a frequency band. The network then configures one or more secondary serving cells (SCells) for the UE. Each SCell can correspond to a component carrier (CC) in the same frequency band (intra-band CA) or in a different frequency band (inter-band CA) as the CC corresponding to the PCell. In order for the UE to send / receive data on the SCell (e.g., by receiving downlink (DL) information on the physical downlink shared channel (PDSCH) or by sending on the physical uplink shared channel (PUSCH)), the SCell needs to be activated by the network. The SCell can also be deactivated and then reactivated as needed by activation / deactivation signaling.

[0003] UL TX Switching

[0004] In Rel-15, UL transmission (Tx) switching between two configured frequency bands is implemented through radio resource control (RRC) configuration, that is, the transmitter chain switches from transmitting on one configured frequency band to transmitting on another configured frequency band.

[0005] 3GPP Rel-16 defines support for dynamic UL Tx switching between two uplink frequency bands in two cases (Case 1 and Case 2 in Table 1 below), where two Tx on one band can be switched to one Tx on the other band, or one Tx on each of the two bands, as shown in Figure 1 shown.

[0006] Rel-16 defines three different frameworks for UL Tx switching, including EN-DC (dual connectivity), where the UE can switch one Tx between LTE uplink and NR uplink, uplink CA, where the UE can switch one Tx between two NR uplinks within an NR CA configuration, and supplementary uplink, where the UE can switch one Tx between normal uplink and supplementary uplink in a cell with SUL configuration.

[0007] 3GPP Rel-17 introduces an additional handover case for switching from two Tx on one band to two Tx on another band (case 3 in the table below), thus expanding the handover cases to three cases, such as Figure 1 For the EN-DC case, no Rel-17 extension is performed.

[0008] In addition, two options for dynamic UL Tx switching for inter-band UL CA for case 1 are supported:

[0009] Option 1 (uplinkTxSwitchingOption=switchedUL): For case 1, simultaneous transmission on two carriers / bands is not supported.

[0010] Option 2 (uplinkTxSwitchingOption=dual UL): For case 1, simultaneous transmission on two carriers / bands is supported.

[0011] When the TX chain switches between two transmissions, the UE is not expected to transmit on any of the two bands during the interval according to the specification.

[0012] Table 1: Rel-17 dynamic UL Tx switching

[0013]

[0014] 3GPP Rel-18 work items on multi-carrier enhancements include the goal of investigating whether Rel-17 operation should be extended for switching between three or four bands. In the RAN1#109-e meeting, the proposed solutions for achieving dynamic UL Tx switching across 3 or 4 bands were discussed, and some agreement was reached to categorize the existing related proposals. In particular, companies are encouraged to study the advantages and disadvantages of the following possible mechanisms for dynamic Tx carrier switching across configured bands, and RAN1 is committed to screening the following alternatives at the RAN1#110 meeting:

[0015] Alternative 1: Dynamic Tx carrier switching can span all supported switching cases of the UE and is based on UL scheduling, ie, via UL grant and / or RRC configuration for UL transmission.

[0016] Alternative 2: The network (NW) indicates 2 of the configured frequency bands (3 or 4 frequency bands) via downlink control information (DCI) or medium access control (MAC) control element (CE) signaling, and indicates dynamic Tx carrier switching between frequency bands as in Rel-17.

[0017] Alternative 3: One anchor band is selected among the configured bands (3 or 4 bands), and dynamic Tx carrier switching can only be performed from the anchor band to the non-anchor band and from the non-anchor band to the anchor band.

[0018] The TX chain switching state diagram for the above alternatives is in Figure 2 , Figure 3 and Figure 4 The figure shows examples based on three frequency bands (represented by Bl, B2 and B3).

[0019] Figure 2 is an illustration of a TX chain switching state diagram for dynamic UL TX switching across three frequency bands B1, B2 and B3 based on Alternative Solution 1 described above. Figure 3 is an illustration of a TX chain switching state diagram for dynamic UL TX switching across 3 frequency bands based on alternative 2 above, where DCI / MAC-CE enables dynamic UL Tx switching across (Bl, B2) or (Bl, B3). Figure 4 is an illustration of a TX chain switching state diagram for dynamic UL TX switching across 3 bands based on Alternative Scheme 3, with Bl among Bl, B2 and B3 as the anchor band (Interpretation 2) (the two interpretations of Alternative Scheme 3 are shown corresponding to including or excluding the dashed line).

[0020] In these figures, state (Bi, Bj) means that the Tx chain in the UE is connected to frequency band Bi and another Tx chain in the UE is connected to frequency band Bj, where i=1, 2, 3 and j=1, 2, 3, which means that (one or more) remaining frequency bands are not connected to the Tx chain in the UE.

[0021] Figure 5 An example is shown to illustrate Tx chain switching from band B2 to B3 based on these alternatives. In particular, Figure 5 2-port transmission on different frequency bands requiring Tx chain switching based on alternatives 1, 2 and 3 is shown. Summary of the invention

[0022] A method of operating a user equipment (UE) configured to perform uplink (UL) transmission switching on more than two configured frequency bands includes: configuring first and second transmission chains of the UE to transmit on at least one frequency band in a set of frequency bands including a first frequency band and a second frequency band, and receiving an indication of a UL transmission, the UL transmission requiring the UE to perform a transmission chain (Tx) switching to use a third frequency band different from the first frequency band and the second frequency band. The UE determines a switching gap duration based on the UL transmission requiring the UE to perform Tx switching to use the third frequency band. The UE performs Tx switching and performs the UL transmission after waiting for at least the switching gap duration.

[0023] Configuring the first and second transmission chains may include configuring the first transmission chain to transmit on a first frequency band and configuring the second transmission chain to transmit on a second frequency band. In some embodiments, configuring the first transmission chain and the second transmission chain includes configuring both the first transmission chain and the second transmission chain to transmit on frequency bands.

[0024] Performing the Tx switching may include switching the first transmission chain or the second transmission chain to transmit on the third frequency band. In some embodiments, performing the Tx switching includes switching the first transmission chain and the second transmission chain to transmit on the third frequency band.

[0025] After performing the Tx switching, both the first transmission chain and the second transmission chain may be configured to transmit on a frequency band other than the first frequency band or the second frequency band.

[0026] At least one of the first and second frequency bands may be identified as an anchor frequency band. UL transmissions may not use the anchor frequency band.

[0027] The frequency band set including the first frequency band and the second frequency band may include the first frequency band set, and when the first frequency band set is different from the second frequency band set used in the UL transmission, the UL transmission may require Tx switching. The first frequency band set may include frequency bands not in the second frequency band set, or the second frequency band set may include frequency bands not in the frequency band set.

[0028] A method of operating a network node includes: configuring a UE to perform UL transmission on at least one frequency band in a frequency band set including a first frequency band and a second frequency band, and transmitting an indication of UL transmission to the UE, the UL transmission requiring the UE to perform Tx switching to use a third frequency band different from the first frequency band and the second frequency band. The network node determines a switching gap duration based on the UL transmission requiring the UE to perform Tx switching to use the third frequency band, and receives the UL transmission after waiting for at least the switching gap duration after the first UL transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 An uplink Tx switching example is illustrated, where two Tx on one band can be switched to one Tx on the other band, or one Tx on each of the two bands.

[0030] Figure 2 An example of a TX chain switching state diagram for dynamic UL TX switching across 3 frequency bands is illustrated.

[0031] Figure 3An example of a Tx chain switching state diagram for dynamic UL Tx switching across 3 UEs is illustrated, where DCI / MAC-CE enables dynamic UL Tx switching.

[0032] Figure 4 is an illustration of a TX chain switching state diagram for dynamic UL TX switching across 3 frequency bands.

[0033] Figure 5 The Tx chain switching from band B2 to B3 is illustrated.

[0034] Figure 6 Dynamic UL Tx switching across 3 frequency bands is illustrated in accordance with some embodiments.

[0035] Figure 7 The operation of a UE according to some embodiments is illustrated.

[0036] Figure 8 The operation of a network node according to some embodiments is illustrated.

[0037] Fig. 9 An example of a communication system in accordance with some embodiments is shown.

[0038] Fig.10 A UE according to some embodiments is shown.

[0039] Fig.11 A network node according to some embodiments is shown.

[0040] Fig.12 is a block diagram of a host computer according to various aspects described herein.

[0041] Fig.13 is a block diagram illustrating a virtualization environment in which functionality implemented by some embodiments may be virtualized.

[0042] Fig.14 A communication diagram is shown in which a host communicates with a UE via a network node over a partially wireless connection according to some embodiments. DETAILED DESCRIPTION

[0043] With regard to existing solutions for supporting dynamic UL TX switching across configured frequency bands, solutions where dynamic UL TX switching can span all switching cases (i.e., Alternative 1) do not address the UE implementation complexity for extending dynamic UL TX switching support to (multiple) additional frequency bands. Solutions that restrict valid switching cases to a subset of configured frequency bands (i.e., Alternative 2) via dynamic commands via DCI or MAC-CE, or constrain switching of the TX chain from / to an anchor frequency band (i.e., Alternative 3) cause scheduling complexity by adjusting the validity of the UL transmission to the previous UL transmission or the dynamic command used to identify the applicable frequency band. Therefore, the validity of the UL transmission will depend on the reception of the previous UL transmission or the dynamic command. These solutions may complicate scheduling and may also be affected by error propagation, where a valid UL grant is assumed to be invalid when it is detected at the UE due to misdetection of the UL grant or dynamic command at the UE.

[0044] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. In particular, some embodiments enable flexible dynamic UL TX switching across more than two frequency bands and provide the UE with the time required to switch (one or more) TX chains without imposing any dependencies in the transmission.

[0045] The concept of anchor band is used to identify situations where additional complexity is expected at the UE for switching TX chains. The recognition of these situations is reflected by ensuring that there is sufficient time for the UE to switch Tx chains to perform a transmission.

[0046] Certain embodiments may provide one or more technical advantages. In particular, some embodiments may facilitate reduced UE complexity and scheduling flexibility to benefit from dynamic UL TX switching across more than two frequency bands to improve capacity or coverage.

[0047] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings.The embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0048] Some embodiments are described generally and can be applied to both scheduled and configured UL transmissions. Some embodiments described herein are applicable to slot-based PUCCH and sub-slot-based PUCCH configurations. The applicable frequency bands are general and may include frequency division duplex (FDD) bands, time division duplex (TDD) bands, normal UL bands, supplementary UL bands, or any combination thereof.

[0049] The terms "carrier" and "frequency band" are used in this document with similar meanings, as the frequency band or range used by the Tx chain to transmit wireless signals. Moreover, in the context of UL Tx switching, the "operating state" refers to the state of the Tx chain on the two carriers or the two frequency bands before the indicated UL transmission. In addition, the "end state" refers to the state of the Tx chain on the two carriers or the two frequency bands after the transmission of the indicated UL transmission.

[0050]

[0046] A process for dynamic UL Tx switching across more than 2 frequency bands according to some embodiments will now be described in detail.

[0051] According to some embodiments, when the UE supports dynamic UL Tx switching across multiple two frequency bands and needs to switch Tx chains on some frequency bands to Tx chains on other frequency bands to perform UL transmission, then subject to the conditions described in this document for complex Tx switching, the UE should expect to provide a relaxed switching gap with a duration of X before the start of UL transmission, during which it is expected that no transmission will be performed on any frequency band. Otherwise, the normal switching gap (if any) applies after the normal UL Tx switching process.

[0052] The duration X may be defined in terms of seconds or milliseconds, or in terms of the number of symbols, or in terms of the number of slots using a given subcarrier spacing.

[0053] In other words, where the indicated UL Tx switching event is considered a complex Tx switching event as defined herein, a larger switching gap (during which the UE is expected not to perform transmissions on any frequency band) than would otherwise be applied will be defined to accommodate the complex Tx switching event.

[0054] Complex Tx switching may be defined based on determination of anchor band(s) among configured bands supporting dynamic UL Tx switching and an anchor state in applicable Tx chain states.

[0055] In some embodiments, for a set of M frequency bands (eg, M=3 or 4) configured to support dynamic UL TX switching, N frequency bands (eg, N=1 or 2) of the M frequency bands are determined as anchor frequency bands.

[0056] An anchored state may be defined as a Tx chain state having one or more Tx chains on one or more anchored frequency bands.

[0057] For example, based on the support of simultaneous transmission on two frequency bands or the capability of certain Tx state switching, a Tx chain state diagram of a set of M configured frequency bands consisting of applicable Tx states is determined.

[0058] RRC configuration signaling may be used to indicate the N anchor frequency bands to the UE. The indication may be explicit or implicit by using default assumptions or rules.

[0059] In one example, one or more configured frequency bands may be defined as possible anchor frequency bands. When any of the indicated frequency bands is configured for UL Tx switching, it will be assumed to be a candidate anchor frequency band.

[0060] If there are more than N candidate anchor bands, N can be selected as anchor bands from the candidate anchor bands, for example, based on a rule predefined or determined based on RRC configuration. Examples of rules for selection are starting from the lowest band in the frequency range, or the band with the smallest SCS, or an even-indexed or odd-indexed band by default or based on RRC configuration. In another example, the first N bands of the M configured bands can be assumed to be anchor bands.

[0061] In another example, N bands from the M configured bands may be considered anchor bands, starting with the lowest band in the frequency range of the M bands, or the band with the smallest SCS and / or the lower index of the configuration, or the even-indexed or odd-indexed band.

[0062] The Tx switching event may be determined as a complex Tx switching event based on one or more conditions of complex Tx switching.

[0063] For example, if, after a previous UL transmission, the UE was in an operational state that is different from the end state corresponding to the indicated UL transmission, the Tx switching event may be identified as complex.

[0064] In one example, if both the operating state (before the Tx switching event) and the ending state (after the Tx switching event) are not anchored states, the Tx switching event is identified as complex.

[0065] In another example, if the end state is not the anchored state, the Tx switching event is identified as complex.

[0066] In another example, if the operating state is not the anchored state, the Tx switching event is identified as complex.

[0067] In another example, if the operating state is the anchored state and the ending state is the anchored state, but their corresponding anchored frequency bands are different, the Tx switching event is identified as complex.

[0068] In another example, if the operating state is the anchored state and the ending state is the anchored state, but one Tx chain is on the same anchored frequency band in the operating state and the ending state, while the other Tx chain is on a different non-anchored frequency band in the operating state and the ending state, then the Tx switching event is identified as complex.

[0069] When it is determined that the indicated UL transmission requires a complex Tx chain state transition as described above, a relaxed switching gap of duration X will be applied. Therefore, the indicated UL transmission is expected to occur after the previous transmission after a relaxed switching gap of at least duration X. The UE is not expected to transmit on any of the M frequency bands during the switching gap.

[0070] The network (e.g., gNB) is responsible for ensuring that there is sufficient time provided to the UE to perform a complex Tx chain switch by satisfying the requirement to provide a relaxed switching gap of at least duration X before the indicated UL transmission that meets the complex Tx switching condition. If the UE determines that a relaxed switching gap is not provided, then performing the transmission of the indicated UL transmission is implemented by the UE.

[0071] In one example, the duration X of the switching gap for the complex Tx switching event may be configured through RRC signaling.

[0072] In another example, the gNB may ensure that the UE is able to perform complex Tx switching within a time period of at least X.

[0073] In some embodiments, the duration X is defined as the number of symbols or time slots using a given SCS. The SCS may be the smallest or largest SCS among the configured M frequency bands, or in an anchor frequency band, or in a non-anchor frequency band.

[0074] Figure 6 Dynamic UL Tx switching across 3 frequency bands according to some embodiments is illustrated. Figure 6 In the example shown, if neither the operational Tx chain state nor the ending Tx state associated with the indicated UL transmission includes an anchor band, then the Tx chain switching event is considered complex.

[0075] exist Figure 6 In FIG. 1 , band B1 is indicated as the anchor band, while bands B2 and B3 are non-anchor bands. Figure 6 In (a), after a 2-port transmission (2P TX) with two Tx chains on band B2, a 2P TX on band B3 is indicated. Because neither band B2 nor band B3 is an anchor band, the Tx switching event is considered a complex Tx switching event according to the specified conditions. Therefore, the UE expects that after the 2P TX on band B2, no UL transmission will occur within a duration X before the start of the indicated 2P TX on band B3.

[0076] exist Figure 6 In (b), the same requirements apply to the indicated UL transmission, which is a 2P TX on Band B2 followed by a 1-port transmission (1P TX) on both Band B2 and Band B3.

[0077] In an example, the UE may be configured with multiple uplink carriers, where the carriers belong to more than two frequency bands. The UE may also be configured with uplink Tx switching between multiple uplink carriers across more than two frequency bands. The UE may obtain information identifying a set of frequency bands from more than two frequency bands as anchor frequency bands.

[0078] When the operational state and the end state together include Tx chains on only two frequency bands and at least one of the two frequency bands is the anchor frequency band, the UE transmits the indicated UL transmission if a switching gap between an end of a previous UL transmission and a start of the indicated UL transmission is greater than a first switching gap value.

[0079] When the operating state and the ending state together include Tx chains on two or more frequency bands and at least two of the frequency bands are non-anchor frequency bands, the UE transmits the indicated UL transmission if a switching gap between an end of a previous UL transmission and a start of the indicated UL transmission is greater than a second gap value.

[0080] In an example, the second switching gap value is greater than the first switching gap value.

[0081] In a further example, the second switching gap value is given by an offset (eg, an additive offset) relative to the first switching gap value.

[0082] In an example, the first handover gap value and the second handover gap value may be indicated by the UE to the network as part of UE capability signaling.

[0083] In an example, the first switching gap value may be indicated by the UE to the network as part of UE capability signaling, and the second gap value may be given by an offset (e.g., an additive offset) relative to the first gap value, which is indicated by the UE as part of the UE capability signaling.

[0084] In an example, the first handover gap value may be indicated by the UE to the network as part of UE capability signaling, and the second handover gap value may be predetermined, fixed, or indicated by higher layer signaling.

[0085] In one example, when the operating state and the end state together include Tx chains only on two frequency bands and at least one of the two frequency bands is an anchor frequency band, a first switching gap duration may be applied between the end of the previous UL transmission and the start of the indicated UL transmission, so that the UE transmits the indicated UL transmission after the first switching gap duration after the previous UL transmission.

[0086] When the operating state and the end state together include Tx chains on two or more frequency bands and at least two of the frequency bands are non-anchor frequency bands, a second switching gap duration can be applied between the end of the previous UL transmission and the start of the indicated UL transmission, so that the UE transmits the indicated UL transmission after the second switching gap duration after the previous UL transmission, wherein the second switching gap duration is greater than the first switching gap duration.

[0087] Figure 7 The operation of a UE according to some embodiments is illustrated.

[0088] Reference Figure 7 , a method of operating a UE configured to perform UL transmission switching on more than two configured frequency bands includes: configuring (702) first and second transmission chains of the UE to transmit on at least one frequency band in a set of frequency bands, the set of frequency bands including a first frequency band and a second frequency band, and receiving (704) an indication of an UL transmission for which Tx switching needs to be performed. The UE determines whether the Tx switching includes a complex Tx switching, for example, whether the UL transmission uses a third frequency band different from the first frequency band and the second frequency band.

[0089] The method determines the switching gap duration based on whether UL transmission requires complex Tx switching, for example, whether UL transmission requires the UE to perform Tx switching to use a third frequency band.

[0090] For example, if the UL transmission does not involve the UE using the third frequency band for transmission, a switching gap having a first switching gap duration is determined (708A); if the UL transmission does involve the UE using the third frequency band for transmission, a switching gap having a second switching gap duration is determined (708B).

[0091] The second switching gap duration may be longer than the first switching gap duration.

[0092] The UE performs (710) Tx switching during the switching gap, and performs (712) a second UL transmission after waiting for at least the switching gap duration.

[0093] Configuring the first and second transmission chains may include configuring the first transmission chain to transmit on a first frequency band and configuring the second transmission chain to transmit on a second frequency band. In some embodiments, configuring the first transmission chain and the second transmission chain includes configuring both the first transmission chain and the second transmission chain to transmit on frequency bands.

[0094] Performing Tx switching may include switching the first transmission chain or the second transmission chain to transmit on the third frequency band. In some embodiments, performing Tx switching includes switching the first transmission chain and the second transmission chain to transmit on the third frequency band.

[0095] After performing Tx switching, both the first transmission chain and the second transmission chain may be configured to transmit on a frequency band other than the first frequency band or the second frequency band.

[0096] At least one of the configured frequency bands may be identified as an anchor frequency band, and whether the Tx switching is complex Tx switching is determined based on whether one or more of the frequency bands used for the first UL transmission or the second UL transmission is the anchor frequency band.

[0097] In some embodiments, when neither the first uplink transmission nor the second uplink transmission uses the anchor frequency band, the Tx switching includes complex Tx switching.

[0098] In some embodiments, when the second uplink transmission does not use the anchor frequency band, the Tx switching includes complex Tx switching.

[0099] In some embodiments, when the first uplink transmission does not use the anchor frequency band, the Tx switching includes complex Tx switching.

[0100] In some embodiments, when the first uplink transmission uses a first anchor frequency band and the second uplink transmission uses a second anchor frequency band different from the first anchor frequency band, the Tx switching includes complex Tx switching.

[0101] In some embodiments, when the first uplink transmission uses the first anchor frequency band and the second uplink transmission uses the first anchor frequency band and a non-anchor frequency band not used in the first uplink transmission, the Tx switching includes complex Tx switching.

[0102] In some embodiments, when the second uplink transmission uses a non-anchor frequency band that is not used in the first uplink transmission, the Tx switching includes complex Tx switching.

[0103] In some embodiments, M of the configured frequency bands are identified as candidate anchor frequency bands, and the method further comprises identifying N of the M candidate anchor frequency bands as anchor frequency bands, where N and M are natural numbers and N is less than M. In some embodiments, the first N of the candidate anchor frequency bands are determined as anchor frequency bands. In some embodiments, the N frequency bands are determined as anchor frequency bands based on a frequency range, a subcarrier size, or a band index of the N frequency bands.

[0104] In some embodiments, when a first frequency band set used in a first uplink transmission is different from a second frequency band set used in a second uplink transmission, that is, when the first frequency band set includes frequency bands that are not in the second frequency band set, or the second frequency band set includes frequency bands that are not in the first frequency band set, the second uplink transmission requires Tx switching.

[0105] Figure 8 The operation of a network node according to some embodiments is illustrated. Figure 8 , a method of operating a network node includes: configuring (802) a UE to transmit on at least one of a first frequency band and a second frequency band. The network node transmits (804) to the UE an indication of an uplink transmission requiring Tx switching.

[0106] The network node determines (806) whether Tx switching involves complex Tx switching, for example, whether UL transmission uses the third frequency band, and determines a switching gap duration in response to determining whether Tx switching involves complex Tx switching. If the UL transmission does not use the third frequency band, a switching gap having a first switching gap duration is determined (808A), and if the UL transmission uses the third frequency band, a switching gap having a second switching gap duration is determined (808B). The second switching gap duration may be longer than the first switching gap duration.

[0107] The network node receives (810) a UL transmission after waiting for at least a switching gap duration.

[0108] Fig. 9 An example of a communication system 900 is shown in accordance with some embodiments.

[0109] In an example, a communication system 900 includes a telecommunications network 902 including an access network 904 such as a radio access network (RAN) and a core network 906 including one or more core network nodes 908. The access network 904 includes one or more access network nodes, such as network nodes 910a and 910b (one or more of which may be generally referred to as network nodes 910), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. The network nodes 910 facilitate direct or indirect connection of user equipment (UE), for example by connecting UEs 912a, 912b, 912c, and 912d (one or more of which may be generally referred to as UEs 912) to the core network 906 over one or more wireless connections.

[0110] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or conductors of other materials. In addition, in different embodiments, the communication system 900 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. The communication system 900 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0111] UE 912 can be any of a wide variety of communication devices, including wireless devices that are arranged, configured and / or operable to wirelessly communicate with network node 910 and other communication devices. Similarly, network node 910 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 912 and / or with other network nodes or devices in telecommunication network 902 to enable and / or provide network access, such as wireless network access, and / or perform other functions, such as management in telecommunication network 902.

[0112] In the depicted example, the core network 906 connects the network node 910 to one or more hosts, such as the host 916. These connections may be direct or indirect via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 906 includes one or more core network nodes (e.g., core network node 908) composed of hardware and software components. The features of these components may be substantially similar to the features described with respect to the UE, the network node and / or the host, so that the description is generally applicable to the corresponding components of the core network node 908. The exemplary core network node includes a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-hiding function (SIDF), a unified data management (UDM), a security edge protection agent (SEPP), a network open function (NEF) and / or a user plane function (UPF) One or more functions.

[0113] The host 916 may be under the ownership or control of a service provider other than the operator or provider of the access network 904 and / or the telecommunications network 902, and may be operated by the service provider or a representative of the service provider. The host 916 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data about various environmental conditions detected by multiple UEs, analysis functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0114] As a whole, Fig. 9 The communication system 900 implements connectivity between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standards (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0115] In some examples, the telecommunication network 902 is a cellular network that implements 3GPP standardized features. Therefore, the telecommunication network 902 can support network slicing to provide different logical networks to different devices connected to the telecommunication network 902. For example, the telecommunication network 902 can provide ultra-reliable low-latency communication (URLLC) services to some UEs, while providing enhanced mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive IoT services to other UEs.

[0116] In some examples, the UE 912 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to the access network 904 according to a predetermined schedule when triggered by an internal or external event, or in response to a request from the access network 904. In addition, the UE may be configured to operate in a single RAT or multi-RAT or multi-standard mode. For example, the UE may operate with any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., be configured for multi-radio dual connectivity (MR-DC), such as new radio dual connectivity (EN-DC) of E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network).

[0117] In an example, the hub 914 communicates with the access network 904 to facilitate indirect communication between one or more UEs (e.g., UE 912c and / or 912d) and a network node (e.g., network node 910b). In some examples, the hub 914 may be a controller, a router, a content source and analysis, or any other communication device described herein with respect to the UE. For example, the hub 914 may be a broadband router that enables the UE to access the core network 906. As another example, the hub 914 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, the network node 910, or may be received through executable code, scripts, processes, or other instructions in the hub 914. As another example, the hub 914 may be a data collector that acts as a temporary storage for UE data, and in some embodiments, analysis or other processing of the data may be performed. As another example, the hub 914 may be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the hub 914 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and the hub 914 then provides it to the UE either directly, after performing local processing, and / or after adding additional local content. In another example, the hub 914 acts as a proxy server or orchestrator for the UE, particularly when one or more of the UEs are low-energy loT devices.

[0118] Hub 914 can have constant / continuous or intermittent connection to network node 910b. Hub 914 can also allow different communication schemes and / or scheduling between hub 914 and UE (e.g., UE 912c and / or 912d) and between hub 914 and core network 906. In other examples, hub 914 is connected to core network 906 and / or one or more UE via wired connection. In addition, hub 914 can be configured to be connected to M2M service provider and / or connected to another UE via direct connection through access network 904. In some scenes, UE can establish wireless connection with network node 910, while still connected via hub 914 via wired or wireless connection. In some embodiments, hub 914 can be a dedicated hub--that is, its main function is to route the hub of communication from network node 910b to UE or from UE to network node 910b. In other embodiments, hub 914 may be a non-dedicated hub - ie, a device operable to route communications between UEs and network node 910b, but which is additionally operable as a communications origin and / or destination for certain data channels.

[0119] Fig.10 UE 1000 according to some embodiments is shown. As used herein, UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playing appliances, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop computer mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted or vehicle-mounted embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0120] The UE may support device-to-device (D2D) communications, such as by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user owning and / or operating the associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user but may not be associated with or may not initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent an apparatus that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0121] UE 1000 includes a processing circuit 1002, which is operably coupled to an input / output interface 1006, a power supply 1008, a memory 1010, a communication interface 1012, and / or any other components or any combination thereof via a bus 1004. Some UEs may utilize Fig.10 All or a subset of the components shown in . The degree of integration between components may vary from one UE to another UE. Further, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0122] The processing circuit 1002 is configured to process instructions and data, and may be configured to implement any sequential state machine that operates to execute instructions stored as a machine-readable computer program in the memory 1010. The processing circuit 1002 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as microprocessors or digital signal processors (DSPs), together with appropriate software; or any combination of the above. For example, the processing circuit 1002 may include multiple central processing units (CPUs).

[0123] In an example, the input / output interface 1006 may be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1000. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, direction pads, trackpads, scroll wheels, smart cards, etc. A presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use an interface port of the same type as an input device. For example, a universal serial bus (USB) port may be used to provide input devices and output devices.

[0124] In some embodiments, the power supply 1008 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. The power supply 1008 may also include a power supply circuit for delivering power from the power supply 1008 itself and / or an external power supply to various parts of the UE 1000 via an input circuit or an interface such as a power cable. The delivered power may be, for example, for charging the power supply 1008. The power supply circuit may perform any formatting, conversion, or other modification on the power from the power supply 1008 to make the power suitable for the corresponding components of the UE 1000 being powered.

[0125] The memory 1010 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cartridge, a flash drive, etc. In one example, the memory 1010 includes one or more application programs 1014, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 1016. The memory 1010 may store any of a variety of operating systems or a combination of operating systems for use by the UE 1000.

[0126] The memory 1010 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory, such as a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more user identity modules (SIMs), such as USIM and / or ISIM, other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card". The memory 1010 may allow the UE 1000 to access instructions, applications, etc. stored on a temporary or non-temporary memory medium to offload data or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied as or in memory 1010, which may be or include a device-readable storage medium.

[0127] The processing circuit 1002 may be configured to communicate with an access network or other network using a communication interface 1012. The communication interface 1012 may include one or more communication subsystems and may include or be communicatively coupled to an antenna 1022. The communication interface 1012 may include one or more transceivers for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node in an access network). Each transceiver may include a transmitter 1018 and / or a receiver 1020 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 1018 and the receiver 1020 may be coupled to one or more antennas (e.g., antenna 1022) and may share circuit components, software or firmware, or may be implemented separately instead.

[0128] In the illustrated embodiment, the communication functionality of the communication interface 1012 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near field communication, location-based communication such as using a global positioning system (GPS) to determine location, another similar communication functionality, or any combination thereof. The communication may be implemented according to one or more communication protocols and / or standards such as IEEE 802. Fig.11As shown, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

[0129] Regardless of the type of sensor, the UE may provide an output of the data captured by its sensor via a wireless connection to a network node through its communication interface 1012. The data captured by the UE's sensor may be transmitted to the network node via another UE over a wireless connection. The output may be periodic (e.g., every 15 minutes if it reports a sensed temperature), random (e.g., to balance the load of reports from several sensors), in response to a trigger event (e.g., sending an alarm when moisture is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0130] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0131] When in the form of an Internet of Things (IoT) device, a UE may be a device for use in one or more application domains including, but not limited to, urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices such as or embedded in: a connected refrigerator or freezer, a television, connected lighting, an electric meter, a robotic vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for augmented reality (AR) or virtual reality (VR), a wearable display for tactile enhancement or sensory enhancement, a sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any kind of medical device such as a heart rate monitor or a teleoperated surgical robot. In addition to the above, the following descriptions are provided herein. Fig.10In addition to the other components described for UE 1000 shown in FIG. 1 , a UE in the form of an IoT device may also include circuits and / or software depending on the intended application of the IoT device.

[0132] As another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement, and transmits the results of such monitoring and / or measurement to another UE and / or a network node. The UE in this case may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a means of transport, such as a car, bus, truck, ship, and airplane, or other devices capable of monitoring and / or reporting its operating status or other functions associated with its operation.

[0133] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE may be or be integrated in a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote control, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE may also include more than one of the above functions. For example, a UE may include a sensor and an actuator and handle data communications for both the speed sensor and the actuator.

[0134] Fig.11 A network node 1100 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0135] Base stations may be classified based on the amount of coverage they provide (or, in other words, their transmit power level), and therefore, depending on the amount of coverage provided, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Portions of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0136] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as an MSR BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile positioning center (E-SMLC)), and / or minimization of drive tests (MDT).

[0137] The network node 1100 includes a processing circuit 1102, a memory 1104, a communication interface 1106, and a power supply 1108. The network node 1100 may be composed of multiple physically separated components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In some cases where the network node 1100 includes multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In this case, each unique NodeB and RNC pair may be considered to be a single separate network node in some cases. In some embodiments, the network node 1100 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1104 for different RATs), and some components may be reused (e.g., the same antenna 1110 may be shared by different RATs). The network node 1100 may also include multiple sets of various components shown for different wireless technologies integrated into the network node 1100, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1100.

[0138] The processing circuit 1102 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic that is operable to provide network node 1100 functionality alone or in combination with other network node 1100 components.

[0139] In some embodiments, processing circuitry 1102 includes a system on a chip (SOC). In some embodiments, processing circuitry 1102 includes one or more of radio frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114. In some embodiments, radio frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114 may be on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of RF transceiver circuitry 1112 and baseband processing circuitry 1114 may be on the same chip or a set of chips, boards, or units.

[0140] The memory 1104 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, permanent memory, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data and / or instructions that can be used by the processing circuit 1102. The memory 1104 may store any suitable instructions, data or information, including computer programs, software, applications including one or more of logic, rules, codes, tables and / or other instructions that can be executed by the processing circuit 1102 and utilized by the network node 1100. The memory 1104 may be used to store any calculations performed by the processing circuit 1102 and / or any data received via the communication interface 1106. In some embodiments, the processing circuit 1102 and the memory 1104 are integrated.

[0141] The communication interface 1106 is used for wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown, the communication interface 1106 includes (one or more) ports / (one or more) terminals 1116, for example, to send data to the network and receive data from the network via a wired connection. The communication interface 1106 also includes a radio frequency front-end circuit 1118, which can be coupled to the antenna 1110, or in some embodiments, coupled to a part of the antenna 1110. The radio frequency front-end circuit 1118 includes a filter 1120 and an amplifier 1122. The radio frequency front-end circuit 1118 can be connected to the antenna 1110 and the processing circuit 1102. The radio frequency front-end circuit can be configured to adjust the signal transmitted between the antenna 1110 and the processing circuit 1102. The radio frequency front-end circuit 1118 can receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio frequency front-end circuit 1118 can use a combination of a filter 1120 and / or an amplifier 1122 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 1110. Similarly, when receiving data, antenna 1110 may collect the radio signal, which may then be converted into digital data by RF front end circuit 1118. The digital data may be passed to processing circuit 1102. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0142] In some alternative embodiments, the network node 1100 does not include a separate RF front end circuit 1118, and instead the processing circuit 1102 includes the RF front end circuit and is connected to the antenna 1110. Similarly, in some embodiments, all or part of the RF transceiver circuit 1112 is part of the communication interface 1106. In other embodiments, the communication interface 1106 includes one or more ports or terminals 1116, the RF front end circuit 1118, and the RF transceiver circuit 1112 as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuit 1114, which is part of the digital unit (not shown).

[0143] Antenna 1110 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1110 may be coupled to RF front-end circuit 1118 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1110 is separated from network node 1100 and may be connected to network node 1100 via an interface or port.

[0144] Antenna 1110, communication interface 1106 and / or processing circuit 1102 may be configured to perform any receiving operation and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signal may be received from a UE, another network node and / or any other network device. Similarly, antenna 1110, communication interface 1106 and / or processing circuit 1102 may be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal may be transmitted to a UE, another network node and / or any other network device.

[0145] The power supply 1108 provides power to the various components of the network node 1100 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply 1108 may further include or be coupled to a power management circuit to supply power to the components of the network node 1100 for performing the functionality described herein. For example, the network node 1100 may be connected to an external power source (e.g., a power grid, a power outlet) via an input circuit or an interface such as a cable, whereby the external power source supplies power to the power circuit of the power supply 1108. As another example, the power supply 1108 may include a power source in the form of a battery or battery pack connected to or integrated in the power circuit. If the external power source fails, the battery may provide backup power.

[0146] Embodiments of the network node 1100 may include, in addition to Fig.11 , to provide certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1100 may include a user interface device to allow information to be input into the network node 1100 and to allow information to be output from the network node 1100. This may allow a user to perform diagnostics, maintenance, repair, and other management functions on the network node 1100.

[0147] Fig.12 is a block diagram of a host 1200 according to various aspects described herein, which may be Fig. 9 1200 is an embodiment of a host 916. As used herein, the host 1200 can be or include various combinations of hardware and / or software, including processing resources in a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a server farm. The host 1200 can provide one or more services to one or more UEs.

[0148] The host 1200 includes a processing circuit 1202, which is operably coupled to an input / output interface 1206, a network interface 1208, a power supply 1210, and a memory 1212 via a bus 1204. Other components may be included in other embodiments. The features of these components may be substantially similar to the features described with respect to the devices of the previous figures, so that their description is generally applicable to the corresponding components of the host 1200.

[0149] The memory 1212 may include one or more computer programs, including one or more host applications 1214 and data 1216, which may include user data, such as data generated by the UE for the host 1200 or data generated by the host 1200 for the UE. An embodiment of the host 1200 may utilize only a subset or all of the components shown. The host application 1214 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different categories, types, or implementations of UEs (e.g., handhelds, desktop computers, wearable display systems, head-up display systems). The host application 1214 may also provide user authentication and license checks, and may periodically report health, routing, and content availability to a central node, such as a device in or on the edge of a core network. Thus, the host 1200 may select and / or indicate a different host for top-level services for the UE. The host application 1214 may support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0150] Fig.131300, wherein the functions implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization may be applied to any device or component thereof described herein, and relates to an implementation in which at least a portion of a function is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1300, the virtual environment being hosted by one or more of a hardware node, such as a hardware computing device operating as a network node, UE, core network node, or host. In addition, in an embodiment where a virtual node does not require radio connectivity (e.g., a core network node or host), the node may be fully virtualized.

[0151] Application 1302 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment Q400 to implement some features, functions and / or benefits of some embodiments disclosed herein.

[0152] Hardware 1304 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 1306 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1308a and 1308b (one or more of which may be generally referred to as VMs 1308), and / or perform any of the functions, features, and / or benefits described in connection with some embodiments described herein. Virtualization layer 1306 may present a virtual operating platform that appears to be networked hardware to VMs 1308.

[0153] The VMs 1308 include virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 1306. Different embodiments of instances of virtual devices 1302 may be implemented on one or more of the VMs 1308, and may be implemented in different ways. Virtualization of hardware is referred to in some contexts as network function virtualization (NFV). NFV may be used to consolidate many network device types onto industry standard high-capacity server hardware, physical switches, and physical storage, which may be located in data centers as well as customer premises equipment.

[0154] In the context of NFV, VMs 1308 can be software implementations of physical machines that run programs as if they were executed on physical, non-virtualized machines. Each of VMs 1308 and the portion of hardware 1304 on which the VM executes is hardware dedicated to the VM and / or hardware shared by the VM with other VMs, forming a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function that runs in one or more VMs 1308 on top of hardware 1304 and corresponds to an application 1302.

[0155] Hardware 1304 may be implemented in a standalone network node with general or specific components. Hardware 1304 may implement some functions via virtualization. Alternatively, hardware 1304 may be part of a larger hardware cluster (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1310, which oversees, among other things, the lifecycle management of application 1302. In some embodiments, hardware 1304 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces, and may be used in combination with virtual components to provide radio capabilities to virtual nodes, such as radio access nodes or base stations. In some embodiments, some signaling may be provided by using a control system 1312, which may alternatively be used for communication between hardware nodes and radio units.

[0156] Fig.14 A communication diagram is shown in which a host 1402 communicates with a UE 1406 via a network node 1404 over a partially wireless connection according to some embodiments. Fig.14 Describe the UE discussed in the previous paragraph (such as Fig. 9 UE 912a and / or Fig.10 UE 1000), network nodes (such as Fig. 9 The network node 910a and / or Fig.11 network nodes 1100) and hosts (such as Fig. 9 Host 916 and / or Fig.12 Host 1200) is implemented according to examples of various embodiments.

[0157] As with the host 1200, embodiments of the host 1402 include hardware, such as a communication interface, a processing circuit, and a memory. The host 1402 also includes software that is stored in or accessible by the host 1402 and that is executable by the processing circuit. The software includes a host application that is operable to provide services to a remote user, such as a UE 1406 connected via an over-the-top (OTT) connection 1450 extending between the UE 1406 and the host 1402. In providing services to the remote user, the host application can provide user data sent using the OTT connection 1450.

[0158] The network node 1404 includes hardware that enables it to communicate with the host 1402 and the UE 1406. The connection 1460 can be direct or through a core network (such as Fig. 9 The core network 906 of the present invention) and / or one or more other intermediate networks, such as one or more public, private or managed networks. For example, the intermediate network can be a backbone network or the Internet.

[0159] UE 1406 includes hardware and software that is stored in or accessible by UE 1406 and can be executed by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "app", which is operable to provide services to human or non-human users via UE 1406 with the support of host 1402. In host 1402, the executing host application can communicate with the executing client application via an OTT connection 1450 terminated at UE 1406 and host 1402. When providing services to the user, the client application of the UE can receive request data from the host application of the host and provide user data in response to the request data. OTT connection 1450 can transmit request data and user data. The client application of the UE can interact with the user to generate user data that it provides to the host application via OTT connection 1450.

[0160] The OTT connection 1450 may extend via a connection 1460 between the host 1402 and the network node 1404 and via a wireless connection 1470 between the network node 1404 and the UE 1406 to provide connectivity between the host 1402 and the UE 1406. The connection 1460 and the wireless connection 1470 through which the OTT connection 1450 is provided have been drawn abstractly to illustrate communications between the host 1402 and the UE 1406 via the network node 1404 without explicitly involving any intermediate devices and the precise routing of messages via those devices.

[0161] As an example of transmitting data via the OTT connection 1450, in step 1408, the host 1402 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with the UE 1406. In other embodiments, the user data is associated with the UE 1406, which shares data with the host 1402 without explicit human interaction. In step 1410, the host 1402 initiates a transmission carrying the user data to the UE 1406. The host 1402 may initiate the transmission in response to a request sent by the UE 1406. The request may be caused by human interaction of the UE 1406 or by the operation of a client application executed on the UE 1406. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be delivered via the network node 1404. Therefore, according to the teachings of the embodiments described throughout the present disclosure, in step 1412, the network node 1404 sends the user data carried in the transmission initiated by the host 1402 to the UE 1406. In step 1414 , UE 1406 receives the user data carried in the transmission, which may be performed by a client application executing on UE 1406 that is associated with a host application executed by host 1402 .

[0162] In some examples, UE 1406 executes a client application that provides user data to host 1402. The user data may be provided as a reaction or response to data received from host 1402. Thus, in step 1416, UE 1406 may provide the user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via the input / output interface of UE 1406. Regardless of the specific manner in which the user data is provided, in step 1418, UE 1406 initiates a transmission of user data to host 1402 via network node 1404. In step 1420, in accordance with the teachings of the embodiments described throughout the present disclosure, network node 1404 receives user data from UE 1406 and initiates a transmission of the received user data toward host 1402. In step 1422, host 1402 receives the user data carried in the transmission initiated by UE 1406.

[0163] One or more of the various embodiments improves the performance of OTT services provided to UE 1406 using OTT connection 1450, where wireless connection 1470 forms the last leg. More specifically, the teachings of these embodiments can improve the performance of dynamic UL switching and provide scheduling flexibility to improve capacity or coverage, thereby providing benefits such as improved throughput and responsiveness.

[0164] In an example scenario, plant status information may be collected and analyzed by host 1402. As another example, host 1402 may process audio and video data that has been retrieved from the UE for use in creating a map. As another example, host 1402 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host 1402 may store surveillance videos uploaded by the UE. As another example, host 1402 may store or control access to media content such as video, audio, VR, or AR that it may broadcast, multicast, or unicast to the UE. As other examples, host 1402 may be used for energy pricing, remote control of non-time-critical electrical loads to balance power generation demand, location services, presentation services (such as compiling charts based on data collected from remote devices, etc.), or any other function for collecting, retrieving, storing, analyzing, and / or transmitting data.

[0165] In some examples, a measurement process may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 1450 between the host 1402 and the UE 1406 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection may be implemented in software and hardware of the host 1402 and / or the UE 1406. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 1450 passes; the sensors may participate in the measurement process by providing the values ​​of the monitored quantities illustrated above, or providing the values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1450 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 1404. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which prompts the host 1402 to measure throughput, propagation time, latency, etc. The measurements may be achieved by software using the OTT connection 1450 to cause messages to be transmitted, particularly empty or "dummy" messages, while monitoring propagation times, errors, etc.

[0166] Although the computing devices (e.g., UE, network nodes, hosts) described herein may include combinations of hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any appropriate combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by a processing circuit, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing. In addition, although the components are depicted as being located within a larger box or a single box nested within multiple boxes, in reality, the computing device may include multiple different physical components that make up a single illustrated component, and functionality may be divided between separate components. For example, a communication interface may be configured to include any component described herein, and / or the functions of the components may be partitioned between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0167] In some embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by a processing circuit without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those specific embodiments, the processing circuit may be configured to perform the described functions regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to separate processing circuits or other components of a computing device, but are generally enjoyed by the computing device as a whole and / or by end users and wireless networks.

[0168] Abbreviation illustrate

[0169] TBS Transport Block Size

[0170] SCS Subcarrier Spacing

[0171] eMBB Enhanced Mobile Broadband

[0172] LTE Long Term Evolution

[0173] NR Next Generation Radio

[0174] PDCCH Physical Downlink Control Channel

[0175] PDSCH Physical Downlink Shared Channel

[0176] PUSCH Physical Uplink Shared Channel

[0177] UE User Equipment

[0178] CC Component Carrier

[0179] FDD Frequency Division Duplex

[0180] TDD Time Division Duplex

[0181] SRS Sounding Reference Signal

[0182] UL Uplink

[0183] BWP Bandwidth Part

[0184] DSS Dynamic Spectrum Sharing

[0185] DL Downlink

[0186] UL Uplink

Claims

1. A method of operating a user equipment (UE), the user equipment (UE) being configured to perform uplink (UL) transmission switching on more than two configured frequency bands, the method comprising: configuring (702) first and second transmission chains of the UE to transmit on at least one frequency band of a set of frequency bands, the set of frequency bands comprising a first frequency band and a second frequency band; receiving (704) an indication of an UL transmission requiring the UE to perform a transmit chain Tx switch to use a third frequency band different from the first frequency band and the second frequency band; determining (708A, 708B) a switching gap duration based on requiring the UE to perform Tx switching to use the UL transmission of the third frequency band; Execute (710) Tx switching; as well as The UL transmission is performed (712) after waiting at least the switching gap duration.

2. The method according to claim 1, wherein: Configuring the first and second transmit chains includes configuring the first transmit chain to transmit on the first frequency band and configuring the second transmit chain to transmit on the second frequency band.

3. The method according to claim 1, wherein: Configuring the first and second transmit chains includes configuring both the first transmit chain and the second transmit chain to transmit over a frequency band.

4. The method according to any one of claims 1 to 3, wherein: Performing the Tx switching includes switching the first transmission chain or the second transmission chain to transmit on the third frequency band.

5. The method according to any one of claims 1 to 3, wherein: Performing the Tx switching includes switching the first transmission chain and the second transmission chain to transmit on the third frequency band.

6. The method according to any one of claims 1 to 5, wherein: After performing the Tx switching, both the first transmission chain and the second transmission chain are configured to transmit on a frequency band other than the first frequency band or the second frequency band.

7. The method of claim 1, wherein at least one of the first and second frequency bands is identified as an anchor frequency band.

8. The method according to claim 7, characterized in that The UL transmission does not use the anchor frequency band.

9. A method according to any preceding claim, wherein: The frequency band set including the first frequency band and the second frequency band includes a first frequency band set, and wherein when the first frequency band set is different from a second frequency band set used in UL transmission, the UL transmission requires Tx switching.

10. The method according to claim 9, wherein: The first frequency band set includes frequency bands that are not in the second frequency band set, or the second frequency band set includes frequency bands that are not in the frequency band set.

11. A user equipment, comprising: A processing circuit configured to perform any one of the steps according to any one of claims 1 to 10; as well as The power supply circuit is configured to supply power to the processing circuit.

12. A method of operating a network node, the method comprising: Configuring (802) a user equipment UE to perform uplink (UL) transmission on at least one frequency band in a frequency band set, the frequency band set comprising a first frequency band and a second frequency band; transmitting (806) to the UE an indication of an UL transmission, the UL transmission requiring the UE to perform a transmit chain Tx switch to use a third frequency band different from the first frequency band and the second frequency band; determining (810A, 810B) a switching gap duration based on requiring the UE to perform Tx switching to use the UL transmission of the third frequency band; as well as The UL transmission is received (812) after waiting at least the switching gap duration.

13. The method according to claim 12, wherein: Configuring the UE includes configuring the UE to transmit on the first frequency band using a first transmit chain and to transmit on the second frequency band using a second transmit chain.

14. The method according to claim 12, wherein: Configuring the UE includes configuring the UE to transmit on the first frequency band using a first transmit chain and to transmit on the first frequency band using a second transmit chain.

15. The method according to any one of claims 12 to 14, wherein: In order to perform the Tx switching, the UE is required to switch the first transmission chain or the second transmission chain to transmit on the third frequency band.

16. The method according to any one of claims 12 to 14, wherein: In order to perform the Tx switching, the UE is required to switch both the first transmission chain and the second transmission chain to transmit on the third frequency band.

17. The method according to claim 15 or 16, wherein: After performing the Tx switching, both the first transmission chain and the second transmission chain are configured to transmit on a frequency band other than the first frequency band or the second frequency band.

18. The method according to claim 12, characterized in that At least one of the first and second frequency bands is identified as an anchor frequency band.

19. The method according to claim 18, characterized in that The UL transmission does not use the anchor frequency band.

20. The method according to any one of claims 12 to 19, wherein: The frequency band set including the first frequency band and the second frequency band includes a first frequency band set, and wherein when the first frequency band set is different from a second frequency band set used in UL transmission, the UL transmission requires Tx switching.

21. The method according to claim 20, wherein: The first frequency band set includes frequency bands that are not in the second frequency band set, or the second frequency band set includes frequency bands that are not in the frequency band set.

22. A network node, comprising: A processing circuit configured to perform any of the steps according to any one of claims 12 to 21; as well as The power supply circuit is configured to supply power to the processing circuit.

Images