WO2024035312A1 - Dispositifs et procédés de commutation de transmission de liaison montante dynamique - Google Patents

Dispositifs et procédés de commutation de transmission de liaison montante dynamique Download PDF

Info

Publication number
WO2024035312A1
WO2024035312A1 PCT/SE2023/050794 SE2023050794W WO2024035312A1 WO 2024035312 A1 WO2024035312 A1 WO 2024035312A1 SE 2023050794 W SE2023050794 W SE 2023050794W WO 2024035312 A1 WO2024035312 A1 WO 2024035312A1
Authority
WO
WIPO (PCT)
Prior art keywords
switching
frequency band
transmission
band
bands
Prior art date
Application number
PCT/SE2023/050794
Other languages
English (en)
Inventor
Sorour Falahati
Ravikiran Nory
Ajit Nimbalker
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2024035312A1 publication Critical patent/WO2024035312A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands

Definitions

  • the present disclosure relates to wireless communication networks, and in particular to systems and methods for performing uplink transmission switching.
  • CA Carrier Aggregation
  • 5G New Radio NR
  • LTE Long Term Evolution
  • UE user equipment
  • the UE typically operates initially on a single serving cell called a primary cell (or PCell).
  • the PCell is operated on a component carrier in a frequency band.
  • the UE is then configured by the network with one or more secondary serving cells (SCell(s)).
  • SCell can correspond to a component carrier (CC) in the same frequency band (intra-band CA) or a different frequency band (inter-band CA) from the frequency band of the CC corresponding to the PCell.
  • CC component carrier
  • intra-band CA intra-band CA
  • inter-band CA different frequency band
  • the SCell(s) need to be activated by the network.
  • the SCell(s) can also be deactivated and later reactivated as needed via activation/deactivation signaling.
  • RRC radio resource control
  • 3GPP Rel-16 defines support for dynamic UL Tx switching between two uplink bands for two cases (Case 1 and Case 2 in Table 1 below) where two Tx on one band can be switched to one Tx on another band, or one Tx on each of the two bands as shown in Figure 1.
  • Rel-16 defines the UL Tx Switching for three different frameworks, including EN-DC (dual connectivity), in which the UE may switch one Tx between the LTE uplink and NR uplink, uplink CA, in which the UE may switch one Tx between two NR uplinks within an NR CA configuration, and supplemental uplink, in which the UE may switch one Tx between the regular uplink and supplemental uplink in a SUL-configured cell.
  • EN-DC dual connectivity
  • uplink CA in which the UE may switch one Tx between two NR uplinks within an NR CA configuration
  • supplemental uplink in which the UE may switch one Tx between the regular uplink and supplemental uplink in a SUL-configured cell.
  • 3GPP Rel-17 introduced an additional switching case for switching from two Tx on one band to two Tx on another band (Case 3 in table below), and hence extended the switching cases to three cases as shown in Figure 1. The Rel-17 extension was not done for the EN-DC case.
  • uplinkTxSwitchingOption dual UL: For case 1, simultaneous transmission on both carriers/bands is supported.
  • the 3GPP Rel-18 work item on multi-carrier enhancements includes the objective of investigating if the Rel-17 operation should be extended for switching between three or four bands.
  • RANl#109-e meetings the proposed solutions to enable dynamic UL Tx switching across 3 or 4 bands were discussed and certain agreements were made to categorize the existing related proposals.
  • companies are encouraged to investigate pros and cons of following possible mechanisms for dynamic Tx carrier switching across the configured bands, and RANI strives for the down-selection at RAN1#110 of the following alternatives:
  • Dynamic Tx carrier switching can be across all the supported switching cases by the UE and based on the UL scheduling, i.e., via UL grant and/or RRC configuration for UL transmission.
  • NW The network
  • DCI downlink control information
  • MAC medium access control
  • CE control element
  • Figure 2 is an illustration of a TX chain switching state diagram for dynamic UL TX switching across 3 bands Bl, B2 and B3 based on Alt.1 above.
  • Figure 3 is an illustration of a TX chain switching state diagram for dynamic UL TX switching across 3 bands based on Alt. 2 above with DCI/MAC-CE enabling 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 Alt. 3 above, with Bl as the anchor band among Bl, B2 and B3 (interpretation 2) (two interpretations of Alt. 3 are illustrated corresponding to including or excluding the dashed lines).
  • Figure 5 shows an example to illustrate a Tx chain switch from band B2 to B3 based on these alternatives.
  • Figure 5 illustrates 2-ports transmissions on different bands that require Tx chain switching based on Alt. 1, Alt. 2 and Alt. 3.
  • a method of operating a user equipment (UE) that is configured to perform uplink (UL) transmission switching on more than two configured frequency bands includes configuring first and second transmission chains of the UE for transmitting on at least one frequency band of a set of frequency bands that includes a first frequency band and a second frequency band, and receiving an indication of a UL transmission that requires the UE to perform transmit chain (Tx) switching to use a third frequency band that is 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 the Tx switching, and performs the UL transmission after waiting at least the switching gap duration.
  • Configuring the first and second transmission chains may include configuring the first transmission chain to transmit on the first frequency band and configuring the second transmission chain to transmit on the second frequency band.
  • configuring the first and second transmission chains includes configuring both the first transmission chain and the second transmission chain to transmit on the frequency band.
  • 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.
  • 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.
  • At least one of the first and second frequency bands may be identified as an anchor band.
  • the UL transmission may not use an anchor band.
  • the set of frequency bands including the first frequency band and the second frequency band may include a first set of frequency bands, and the UL transmission may require Tx switching when the first set of frequency bands is not identical to a second set of frequency bands used in the UL transmission.
  • the first set of frequency bands may include a frequency band not in the second set of frequency bands, or the second set of frequency bands may include a frequency band not in the set of frequency bands.
  • a method of operating a network node includes configuring a UE to perform UL transmission on at least one frequency band of a set of frequency bands that includes a first frequency band and a second frequency band, and transmitting an indication to the UE of a UL transmission that requires the UE to perform Tx switching to use a third frequency band that is 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 at least the switching gap duration following the first UL transmission.
  • Figure 1 illustrates uplink Tx switching examples in which two Tx on one band can be switched to one Tx on another band, or one Tx on each of the two bands.
  • Figure 2 illustrates an example of a TX chain switching state diagram for dynamic UL TX switching across 3 bands.
  • Figure 3 illustrates an example of a TX chain switching state diagram for dynamic UL TX switching across 3 with DCI/MAC-CE enabling dynamic UL Tx switching.
  • Figure 4 is an illustration of a TX chain switching state diagram for dynamic UL TX switching across 3 bands.
  • Figure 5 illustrates a Tx chain switch from band B2 to B3.
  • Figure 6 illustrates dynamic UL Tx switching across 3 bands according to some embodiments.
  • Figure 7 illustrates operations of a UE according to some embodiments.
  • Figure 8 illustrates operations of a network node according to some embodiments.
  • Figure 9 shows an example of a communication system in accordance with some embodiments.
  • Figure 10 shows a UE in accordance with some embodiments.
  • Figure 11 shows a network node in accordance with some embodiments.
  • Figure 12 is a block diagram of a host in accordance with various aspects described herein.
  • Figure 13 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Figure 14 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • the solutions that dynamic UL TX switching can be across all the switching cases do not address the UE implementation complexity for extending the dynamic UL TX switching support for additional band(s).
  • the solutions that limit the effective switching cases by a dynamic command via DCI or MAC-CE to a sub-set of the configured bands i.e. Alt. 2), or constrain the switch of the TX chain from/to an anchor band (i.e. Alt. 3)
  • cause scheduling complexity by conditioning a validity of a UL transmission to preceding UL transmissions or the dynamic command for identifying the applicable bands.
  • Certain embodiments may provide one or more technical advantage(s).
  • some embodiments may facilitate reduced UE complexity UE as well as scheduling flexibility to benefit from dynamic UL TX switching across more than two bands to improve capacity or coverage.
  • Some embodiments are described in general 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 configuration.
  • the applicable bands are general, and can include a frequency division duplexing (FDD) band, a time division duplexing (TDD) band, a normal UL band, a supplementary UL band, or any combination thereof.
  • carrier and “band” are used with similar meanings herein as a frequency band or range used by a Tx chain to transmit wireless signals.
  • an “operation state” refers to the state of Tx chains on two carriers or two bands before an indicated UL transmission.
  • an “ending state” refers to the state of Tx chains on two carriers or two bands after transmission of an indicated UL transmission.
  • a UE when a UE supports dynamic UL Tx switching across more than two bands and requires switching the Tx chain(s) on some band(s) to Tx chain(s) on other band(s) to perform a UL transmission, then subject to satisfying the condition(s) described herein for complex Tx switching, the UE shall expect that a relaxed switching gap having a duration X, during which no transmission is expected on any of the bands, is provided prior to the start of the UL transmissions. Otherwise, a conventional switching gap, if any, is applicable following conventional UL Tx switching procedures.
  • the duration X may be defined in terms of seconds or milliseconds, or in terms of a number of symbols, or in terms of a number of slots using a given subcarrier spacing (SCS).
  • SCS subcarrier spacing
  • an indicated UL Tx switching event is deemed to be a complex Tx switching event as defined herein
  • a larger switching gap (during which no transmission is expected to be performed by the UE on any band) than would otherwise apply will be defined to accommodate the complex Tx switching event.
  • Complex Tx switching can be defined based of determination of anchor band(s) among configured bands that support dynamic UL Tx switching and the anchor states among the applicable Tx chain states.
  • N of the bands among the M bands are determined to be anchor bands.
  • An anchor state may be defined as a Tx chain state with one or more Tx chain(s) on one or more anchor band(s).
  • a Tx chains state diagram for the set of M configured bands is determined that consists of the applicable Tx states, for example based on the support of simultaneous transmission on two bands or capability of certain Tx states switching.
  • RRC configuration signalling may be used to indicate the N anchor band(s) to the UE.
  • the indication may be explicit or implicit by using default assumptions or rules.
  • one or more configured bands may be defined as possible anchor bands.
  • any of the indicated bands is configured for UL Tx switching, it would be assumed to be a candidate anchor band.
  • N of the candidate anchor bands may be selected as anchor bands, for example based on a rule that is pre-defined or determined based on RRC configuration. Examples of rules for selection are to start with the lowest band in the frequency range, or the band with the smallest SCS, or even indexed or odd indexed bands by default or based on RRC configurations.
  • the first N band(s) from M configured bands a set may be assumed to be the anchor band(s).
  • the N band(s) from M configured bands may be considered as anchor bands, starting from the lowest band in the frequency range among the M bands, or the band with the smallest SCS and/or lower indexed, or even indexed or odd indexed band(s) configured.
  • a Tx switching event may be determined to be a complex Tx switching event based on one or more conditions for complex Tx switching.
  • the Tx switching event can be identified as complex.
  • the Tx switching event is identified as complex.
  • the Tx switching event is identified as complex.
  • the Tx switching event is identified as complex.
  • the Tx switching event is identified as complex.
  • the Tx switching event is identified as complex.
  • an indicated UL transmission requires a complex Tx chain state transition as described above, a relaxed switching gap of duration X will be applied.
  • the indicated UL transmission is expected to occur after a relaxed switching gap of at least duration X after the preceding transmission.
  • the UE is not expected to transmit on any of the M bands during the switching gap.
  • the network e.g., the gNB
  • the network e.g., the gNB
  • the network e.g., the gNB
  • it is the responsibility of the network (e.g., the gNB) to ensure that there is sufficient time provided for the UE to perform a complex Tx chain switching by fulfilling the requirement of providing a relaxed switching gap of at least duration X before an indicated UL transmission that satisfies the conditions of complex Tx switching. If the UE determines that a relaxed switching gap is not provided, it is up to UE implementation to perform transmission of the indicated UL transmission.
  • the duration X of the switching gap for complex Tx switching events can be configured by RRC signalling.
  • the gNB may ensure that the UE is capable to perform complex Tx switching within a time of duration at least X.
  • the duration X is defined in number of symbols, or slots using a given SCS.
  • the SCS can be the smallest or the largest SCs among the configured M bands, or among the anchor bands, or among the non-anchor bands.
  • FIG. 6 illustrates dynamic UL Tx switching across 3 bands according to some embodiments.
  • a Tx chain switching event is considered to be complex if neither the operating Tx chain state nor the ending Tx state associated to an indicated UL transmission include an anchor band.
  • Band Bl is indicated as an anchor band, while Bands B2 and B3 are non-anchor bands.
  • 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 to be a complex Tx switching event according to the specified condition.
  • UE expects that after the 2P TX on Band B2, no UL transmission will occur within a duration of X before the start of the indicated 2P TX on Band B3.
  • a UE may be configured with multiple uplink carriers, wherein the carriers belong to more than two frequency bands.
  • the UE may further be configured with uplink Tx switching between the multiple uplink carriers across the more than two frequency bands.
  • the UE may acquire information identifying a set of band(s) from the more than two bands as anchor band(s).
  • the UE transmits an indicated UL transmission if the switching gap between the end of a preceding UL transmission and the beginning of the indicated UL transmission is larger than a first switching gap value when the operation state and the ending state together include Tx chains on only two bands and at least one band of the two bands is the anchor band.
  • the UE transmits the indicated UL transmission if the switching gap between the end of the preceding UL transmission and the beginning of the indicated UL transmission is larger than a second gap value, when the operation state and the ending state together comprise Tx chains on two or more bands and at least two of the bands are non-anchor bands.
  • the second switching gap value is larger than the first switching gap value.
  • the second switching gap value is given by an offset (e.g. additive offset) relative to the first switching gap value.
  • the first switching gap value and the second switching gap value may be indicated by the UE to the network as part of UE capability signaling.
  • the first switching gap value may be indicated by the UE to the network as part of UE capability signaling
  • the second gap value may be given by an offset (e.g. additive offset) relative to the first gap value, that is indicated by the UE as part of UE capability signaling.
  • the first switching gap value may be indicated by the UE to the network as part of UE capability signaling, and the second switching gap value may be predetermined, fixed or indicated by higher layer signaling.
  • a first switching gap duration may be applied between the end of a preceding UL transmission and the beginning of an indicated UL transmission, such that the UE transmits the indicated UL transmission after the first switching gap duration following the preceding UL transmission.
  • a second switching gap duration may be applied between the end of the preceding UL transmission and the beginning of the indicated UL transmission, such that the UE transmits the indicated UL transmission after the second switching gap duration following the preceding UL transmission, where the second switching gap duration is greater than the first switching gap duration.
  • Figure 7 illustrates operations of a UE according to some embodiments.
  • a method of operating a UE that is configured to perform UL transmission switching on more than two configured frequency bands includes configuring (702) first and second transmission chains of the UE for transmitting on at least one frequency band of 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 a UL transmission that requires Tx switching to perform.
  • the UE determines if the Tx switching comprises complex Tx switching, e.g., if the UL transmission uses a third frequency band that is different from the first frequency band and the second frequency band.
  • the method determines a switching gap duration based on whether the UL transmission requires complex Tx switching, e.g., whether the UL transmission requires the UE to perform Tx switching to use the third frequency band.
  • a switching gap having a first switching gap duration is determined (708 A)
  • a switching gap having a second switching gap duration is determined (708B).
  • the second switching gap duration may be longer than the first switching gap duration.
  • the UE performs (710) the Tx switching during the switching gap, and performs (712) the second UL transmission after waiting at least the switching gap duration.
  • Configuring the first and second transmission chains may include configuring the first transmission chain to transmit on the first frequency band and configuring the second transmission chain to transmit on the second frequency band.
  • configuring the first and second transmission chains includes configuring both the first transmission chain and the second transmission chain to transmit on the frequency band.
  • 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.
  • 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.
  • At least one of the configured frequency bands may be identified as an anchor band, and determining whether the Tx switching is complex Tx switching is based on whether one or more of the frequency bands used for the first UL transmission or the second UL transmission is an anchor band.
  • the Tx switching comprises complex Tx switching when neither the first uplink transmission nor the second uplink transmission uses an anchor band.
  • the Tx switching comprises complex Tx switching when the second uplink transmission does not use an anchor band.
  • the Tx switching comprises complex Tx switching when the first uplink transmission does not use an anchor band.
  • the Tx switching comprises complex Tx switching when the first uplink transmission uses a first anchor band and the second uplink transmission uses a second anchor band that is different than the first anchor band.
  • the Tx switching comprises complex Tx switching when the first uplink transmission uses a first anchor band and the second uplink transmission uses the first anchor and a non-anchor band that was not used in the first uplink transmission. [0098] In some embodiments, the Tx switching comprises complex Tx switching when the second uplink transmission uses a non-anchor band that was not used in the first uplink transmission.
  • M of the configured frequency bands are identified as candidate anchor bands, and the method further comprises identifying N of the M candidate anchor bands as anchor bands, where N and M are natural numbers and N is less than M.
  • the first N frequency bands of the candidate anchor bands are determined to be anchor bands.
  • the N frequency bands are determined to be anchor bands based on frequency range, subcarrier size or band index of the N frequency bands.
  • the second uplink transmission requires Tx switching when a first set of frequency bands used in the first uplink transmission is not identical to a second set of frequency bands used in the second uplink transmission, that is, when the first set of frequency bands includes a frequency band not in the second set of frequency bands, or the second set of frequency bands includes a frequency band not in the first set of frequency bands.
  • Figure 8 illustrates operations of a network node according to some embodiments.
  • 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) an indication to the UE of a uplink transmission that requires Tx switching to perform.
  • the network node determines (806) whether the Tx switching involves complex Tx switching, e.g., whether the UL transmission uses a third frequency band, and determines a switching gap duration in response to determining whether the 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.
  • the network node receives (810) the UL transmission after waiting at least the switching gap duration.
  • Figure 9 shows an example of a communication system 900 in accordance with some embodiments.
  • the communication system 900 includes a telecommunication network 902 that includes an access network 904, such as a radio access network (RAN), and a core network 906, which includes 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 3 rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3 rd Generation Partnership Project
  • the network nodes 910 facilitate direct or indirect connection of user equipment (UE), such as 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.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • 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 wired or wireless connections.
  • 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.
  • the UEs 912 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 910 and other communication devices.
  • the network nodes 910 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 912 and/or with other network nodes or equipment in the telecommunication network 902 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 902.
  • the core network 906 connects the network nodes 910 to one or more hosts, such as host 916. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 906 includes one more core network nodes (e.g., core network node 908) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 908.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 916 may be under the ownership or control of a service provider other than an operator or provider of the access network 904 and/or the telecommunication network 902, and may be operated by the service provider or on behalf of the service provider.
  • the host 916 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 900 of Figure 9 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are 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 standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Micro wave 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.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 902 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 902 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 902. For example, the telecommunications network 902 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 912 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 904 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 904.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • 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 network nodes (e.g., network node 910b).
  • the hub 914 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 914 may be a broadband router enabling access to the core network 906 for the UEs.
  • the hub 914 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 914 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 914 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 914 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 914 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 914 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 914 may have a constant/persistent or intermittent connection to the network node 910b.
  • the hub 914 may also allow for a different communication scheme and/or schedule between the hub 914 and UEs (e.g., UE 912c and/or 912d), and between the hub 914 and the core network 906.
  • the hub 914 is connected to the core network 906 and/or one or more UEs via a wired connection.
  • the hub 914 may be configured to connect to an M2M service provider over the access network 904 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 910 while still connected via the hub 914 via a wired or wireless connection.
  • the hub 914 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 910b.
  • the hub 914 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 910b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • Figure 10 shows a UE 1000 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle- to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale
  • the UE 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input/output interface 1006, a power source 1008, a memory 1010, a communication interface 1012, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 1002 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1010.
  • the processing circuitry 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 a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 1002 may include multiple central processing units (CPUs).
  • the input/output interface 1006 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 1000.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, 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 the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 1008 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 1008 may further include power circuitry for delivering power from the power source 1008 itself, and/or an external power source, to the various parts of the UE 1000 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1008.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1008 to make the power suitable for the respective components of the UE 1000 to which power is supplied.
  • the memory 1010 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1010 includes one or more application programs 1014, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1016.
  • the memory 1010 may store, for use by the UE 1000, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1010 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory 1010 may allow the UE 1000 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to offload data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1010, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1002 may be configured to communicate with an access network or other network using the communication interface 1012.
  • the communication interface 1012 may comprise 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 used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 1018 and/or a receiver 1020 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1018 and receiver 1020 may be coupled to one or more antennas (e.g., antenna 1022) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1012 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/intemet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 1012, via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot 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 electrical door lock, a connected doorbell, an air conditioning system like 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 for tactile augmentation or sensory enhancement, a water sprinkler, an animal-
  • AR Augmented Reality
  • VR
  • a UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1000 shown in Figure 10.
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3 GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • 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 the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG 11 shows a network node 1100 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • 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 NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, 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 controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi- TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 1100 includes a processing circuitry 1102, a memory 1104, a communication interface 1106, and a power source 1108.
  • the network node 1100 may be composed of multiple physically separate components (e.g., aNodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 1100 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1100 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1104 for different RATs) and some components may be reused (e.g., a same antenna 1110 may be shared by different RATs).
  • the network node 1100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1100, for example 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 chip or set of chips and other components within network node 1100.
  • RFID Radio Frequency Identification
  • the processing circuitry 1102 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1100 components, such as the memory 1104, to provide network node 1100 functionality.
  • the processing circuitry 1102 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1102 includes one or more of radio frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114. In some embodiments, the radio frequency (RF) transceiver circuitry 1112 and the baseband processing circuitry 1114 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1112 and baseband processing circuitry 1114 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 1102 includes one or more of radio frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114.
  • the radio frequency (RF) transceiver circuitry 1112 and the baseband processing circuitry 1114 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of
  • the memory 1104 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1102.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-
  • the memory 1104 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1102 and utilized by the network node 1100.
  • the memory 1104 may be used to store any calculations made by the processing circuitry 1102 and/or any data received via the communication interface 1106.
  • the processing circuitry 1102 and memory 1104 is integrated.
  • the communication interface 1106 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1106 comprises port(s)/terminal(s) 1116 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1106 also includes radio front-end circuitry 1118 that may be coupled to, or in certain embodiments a part of, the antenna 1110. Radio front-end circuitry 1118 comprises filters 1120 and amplifiers 1122.
  • the radio front-end circuitry 1118 may be connected to an antenna 1110 and processing circuitry 1102.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1110 and processing circuitry 1102.
  • the radio front-end circuitry 1118 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 1118 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1120 and/or amplifiers 1122.
  • the radio signal may then be transmitted via the antenna 1110.
  • the antenna 1110 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1118.
  • the digital data may be passed to the processing circuitry 1102.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 1100 does not include separate radio front-end circuitry 1118, instead, the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106. In still other embodiments, the communication interface 1106 includes one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112, as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown).
  • the antenna 1110 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1110 may be coupled to the radio front-end circuitry 1118 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1110 is separate from the network node 1100 and connectable to the network node 1100 through an interface or port.
  • the antenna 1110, communication interface 1106, and/or the processing circuitry 1102 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1110, the communication interface 1106, and/or the processing circuitry 1102 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 1108 provides power to the various components of network node 1100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1108 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1100 with power for performing the functionality described herein.
  • the network node 1100 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1108.
  • the power source 1108 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 1100 may include additional components beyond those shown in Figure 11 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 1100 may include user interface equipment to allow input of information into the network node 1100 and to allow output of information from the network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1100.
  • FIG 12 is a block diagram of a host 1200, which may be an embodiment of the host 916 of Figure 9, in accordance with various aspects described herein.
  • the host 1200 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 1200 may provide one or more services to one or more UEs.
  • the host 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a network interface 1208, a power source 1210, and a memory 1212.
  • processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a network interface 1208, a power source 1210, and a memory 1212.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 11, such that the descriptions thereof are generally applicable to the corresponding components of host 1200.
  • the memory 1212 may include one or more computer programs including one or more host application programs 1214 and data 1216, which may include user data, e.g., data generated by a UE for the host 1200 or data generated by the host 1200 for a UE.
  • Embodiments of the host 1200 may utilize only a subset or all of the components shown.
  • the host application programs 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 classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 1214 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 1200 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1214 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 13 is a block diagram illustrating a virtualization environment 1300 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality 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 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 1302 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1304 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • 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 relation with some embodiments described herein.
  • the virtualization layer 1306 may present a virtual operating platform that appears like networking hardware to the VMs 1308.
  • the VMs 1308 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1306.
  • a virtualization layer 1306 Different embodiments of the instance of a virtual appliance 1302 may be implemented on one or more of VMs 1308, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • NFV network function virtualization
  • a VM 1308 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 1308, and that part of hardware 1304 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1308 on top of the hardware 1304 and corresponds to the application 1302.
  • Hardware 1304 may be implemented in a standalone network node with generic or specific components. Hardware 1304 may implement some functions via virtualization. Alternatively, hardware 1304 may be part of a larger cluster of hardware (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, among others, oversees lifecycle management of applications 1302.
  • hardware 1304 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 1312 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 14 shows a communication diagram of a host 1402 communicating via a network node 1404 with a UE 1406 over a partially wireless connection in accordance with some embodiments.
  • host 1402 Like host 1200, embodiments of host 1402 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1402 also includes software, which is stored in or accessible by the host 1402 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1406 connecting via an over-the-top (OTT) connection 1450 extending between the UE 1406 and host 1402.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 1450.
  • the network node 1404 includes hardware enabling it to communicate with the host 1402 and UE 1406.
  • the connection 1460 may be direct or pass through a core network (like core network 906 of Figure 9) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 906 of Figure 9
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1406 includes hardware and software, which is stored in or accessible by UE 1406 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1406 with the support of the host 1402.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1406 with the support of the host 1402.
  • an executing host application may communicate with the executing client application via the OTT connection 1450 terminating at the UE 1406 and host 1402.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1450 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT
  • 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 the connection between the host 1402 and the UE 1406.
  • the connection 1460 and wireless connection 1470, over which the OTT connection 1450 may be provided, have been drawn abstractly to illustrate the communication between the host 1402 and the UE 1406 via the network node 1404, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1402 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1406.
  • the user data is associated with a UE 1406 that shares data with the host 1402 without explicit human interaction.
  • the host 1402 initiates a transmission carrying the user data towards the UE 1406.
  • the host 1402 may initiate the transmission responsive to a request transmitted by the UE 1406.
  • the request may be caused by human interaction with the UE 1406 or by operation of the client application executing on the UE 1406.
  • the transmission may pass via the network node 1404, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1412, the network node 1404 transmits to the UE 1406 the user data that was carried in the transmission that the host 1402 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE 1406 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1406 associated with the host application executed by the host 1402. [0158] In some examples, the UE 1406 executes a client application which provides user data to the host 1402. The user data may be provided in reaction or response to the data received from the host 1402.
  • the UE 1406 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1406.
  • the UE 1406 initiates, in step 1418, transmission of the user data towards the host 1402 via the network node 1404.
  • the network node 1404 receives user data from the UE 1406 and initiates transmission of the received user data towards the host 1402.
  • the host 1402 receives the user data carried in the transmission initiated by the UE 1406.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1406 using the OTT connection 1450, in which the wireless connection 1470 forms the last segment. More precisely, the teachings of these embodiments may improve the performance of dynamic UL switching and to provide scheduling flexibility to improve capacity or coverage and thereby provide benefits such as improved throughput and responsiveness.
  • factory status information may be collected and analyzed by the host 1402.
  • the host 1402 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1402 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1402 may store surveillance video uploaded by a UE.
  • the host 1402 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 1402 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1402 and/or UE 1406.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1450 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1450 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1404. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1402.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1450 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

Landscapes

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

Abstract

L'invention concerne un procédé d'exploitation d'un équipement utilisateur (UE) configuré pour effectuer une commutation de transmission de liaison montante (UL) sur plus de deux bandes de fréquences configurées comprenant la configuration des première et deuxième chaînes de transmission de l'UE pour la transmission sur au moins une bande de fréquences d'un ensemble de bandes de fréquences qui comprend une première bande de fréquences et une deuxième bande de fréquences, et la réception d'une indication d'une transmission UL qui nécessite que l'UE effectue une commutation de chaîne de transmission (Tx) pour utiliser une troisième bande de fréquences différente de la première bande de fréquences et de la deuxième bande de fréquences. L'UE détermine une durée d'intervalle de commutation sur la base de la transmission UL demandant à l'UE d'effectuer une commutation Tx pour utiliser la troisième bande de fréquence. L'UE effectue la commutation Tx, et effectue la transmission UL après avoir attendu au moins la durée d'intervalle de commutation.
PCT/SE2023/050794 2022-08-12 2023-08-08 Dispositifs et procédés de commutation de transmission de liaison montante dynamique WO2024035312A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263397577P 2022-08-12 2022-08-12
US63/397,577 2022-08-12

Publications (1)

Publication Number Publication Date
WO2024035312A1 true WO2024035312A1 (fr) 2024-02-15

Family

ID=87576008

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050794 WO2024035312A1 (fr) 2022-08-12 2023-08-08 Dispositifs et procédés de commutation de transmission de liaison montante dynamique

Country Status (1)

Country Link
WO (1) WO2024035312A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021162620A1 (fr) * 2020-02-14 2021-08-19 Telefonaktiebolaget Lm Ericsson (Publ) Procédés prenant en charge une transmission de liaison montante à commutation rapide sur des porteuses
US20210274483A1 (en) * 2018-11-19 2021-09-02 Huawei Technologies Co., Ltd. Uplink Switching Method, Communication Apparatus, And Communication System

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210274483A1 (en) * 2018-11-19 2021-09-02 Huawei Technologies Co., Ltd. Uplink Switching Method, Communication Apparatus, And Communication System
WO2021162620A1 (fr) * 2020-02-14 2021-08-19 Telefonaktiebolaget Lm Ericsson (Publ) Procédés prenant en charge une transmission de liaison montante à commutation rapide sur des porteuses

Similar Documents

Publication Publication Date Title
WO2024035312A1 (fr) Dispositifs et procédés de commutation de transmission de liaison montante dynamique
WO2023207433A1 (fr) Procédés et appareils de communication dans un système de communication sans fil avec une caractéristique d'économie d'énergie de réseau
WO2023063859A1 (fr) Temporisateur de désactivation de cellule secondaire (scell) dans une programmation inter-porteuse
WO2023095093A1 (fr) Signalisation mac ce destinée à supporter des fonctionnements à la fois conjoints et séparés de tci dl/ul
WO2023073677A2 (fr) Mesures dans un réseau de communication
WO2023211358A1 (fr) Détermination d'espace de recherche pour des informations de commande de liaison descendante uniques planifiant plusieurs cellules
WO2024096807A1 (fr) Pdsch pour équipement utilisateur à capacité réduite
WO2024062268A1 (fr) Système de réglage de cellules secondaires disponibles d'un dispositif de communication
WO2024062269A1 (fr) Ajustement de cellules secondaires disponibles d'un dispositif de communication
WO2023211337A1 (fr) Procédés de détermination du retard d'application pour une commutation de groupe d'ensembles d'espaces de recherche
WO2023012731A1 (fr) Surveillance de canal de commande de liaison descendante physique pour une planification inter-porteuses améliorée
WO2023211347A1 (fr) États de déclenchement apériodiques inactifs pour économie d'énergie
WO2022238944A1 (fr) Commutation de porteuse de pucch pour pucch périodique à configuration semi-statique
WO2023211357A1 (fr) Sélection de porteuse pour des informations de commande de liaison descendante uniques planifiant de multiples cellules
WO2023209686A1 (fr) Systèmes et procédés de signalisation d'invalidation
WO2023083882A1 (fr) Autorisation configurée pour une transmission de liaison montante multi-panneau
WO2023062509A1 (fr) Activation de cellule secondaire basée sur un signal de référence temporaire par l'intermédiaire d'une commande de ressources radio
WO2022238943A1 (fr) Dispositifs et procédés de configuration de motif semi-statique pour commutation de porteuses de pucch
WO2024028838A1 (fr) Économie d'énergie de réseau dans un ng-ran scindé
WO2024033731A1 (fr) Rapport de faisceau basé sur un groupe pour une transmission et une réception simultanées à panneaux multiples
WO2023148705A1 (fr) Conception conjointe de disponibilité dans le domaine temporel et fréquentiel
WO2023079525A1 (fr) Ressources de pucch pour dispositifs sans fil à largeur de bande réduite
WO2023165970A1 (fr) Mise en œuvre d'une transmission ou transmission d'un bloc de signal de synchronisation de liaison latérale
WO2023053098A1 (fr) Commande améliorée de la puissance de pucch lors du mélange d'uci de différentes priorités
WO2023166498A1 (fr) Systèmes et procédés d'association implicite entre une transmission pusch à trp multiples et des états tci unifiés

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23755182

Country of ref document: EP

Kind code of ref document: A1