WO2024099812A1 - Incrément d'occasions de pusch à autorisation configurée - Google Patents

Incrément d'occasions de pusch à autorisation configurée Download PDF

Info

Publication number
WO2024099812A1
WO2024099812A1 PCT/EP2023/080229 EP2023080229W WO2024099812A1 WO 2024099812 A1 WO2024099812 A1 WO 2024099812A1 EP 2023080229 W EP2023080229 W EP 2023080229W WO 2024099812 A1 WO2024099812 A1 WO 2024099812A1
Authority
WO
WIPO (PCT)
Prior art keywords
pusch
puschs
host
harq
network node
Prior art date
Application number
PCT/EP2023/080229
Other languages
English (en)
Inventor
Bikramjit Singh
Jonas FRÖBERG OLSSON
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 WO2024099812A1 publication Critical patent/WO2024099812A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1893—Physical mapping arrangements

Definitions

  • the present disclosure relates to wireless communications, and in particular, to PUSCH occasions increment.
  • BACKGROUND [0002] The Third Generation Partnership Project (3GPP) has developed up to release 18 (Rel-18) for New Radio (NR) standard. In the ongoing Rel-18 study item on eXtended Reality (XR), several enhancements are being proposed to increase XR capacity of 5G- Advanced systems.
  • eXtended Reality includes services provided by computer technologies and wearables that allow for human-machine interaction in real/virtual mixed environments.
  • XR includes Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR), Cloud Gaming, and the areas interpolated among them. As such, XR is usually considered a mixed eMBB/URLLC service.
  • XR traffic is a mixture of heterogeneous uplink/downlink (UL/DL) data flows, including video, audio, and control traffic.
  • Table 1 - XR traffic characteristics and requirements identified by 3GPP [0004] Table 1 highlights that XR traffic flows have different characteristics, e.g., packet rate in frame per second [fps] and bit rate in bit per second [bps], and requirements in terms of packet delay budget (PDB) [ms].
  • PDB packet delay budget
  • Configured grants may be used to configure uplink transmission without dynamic grants according to two possible schemes.
  • the actual uplink grant may either be configured via RRC (type1) or provided via the physical downlink control channel (PDCCH) addressed to CS-RNTI (type2).
  • Multiple Configured Grant configurations may be configured in one BWP of a serving cell.
  • the benefit of using configured grants for uplink transmission is to reduce signaling overhead and to reduce latency before uplink data transmission, as no scheduling request/grant cycle is needed before data transmission.
  • ConfiguredGrantConfig IE which configures CG at the UE, is shown in Appendix A.
  • Hybrid automatic repeat request, HARQ, ID calculation for physical uplink shared channel (PUSCH) transmitted over NR CG is specified in 3GPP TS 38.214, 3GPP TS 38.213, and 3GPP TS 38.331.
  • the UE implementation selects an HARQ Process ID among the HARQ process IDs available for the configured grant configuration.
  • the UE shall prioritize retransmissions before initial transmissions.
  • the UE shall toggle the NDI in the CG-UCI for new transmissions and not toggle the NDI in the CG-UCI in retransmissions.
  • the RF is identified by system frame number (SFN) which can be from 0 to 1023.
  • SFN system frame number
  • the periodicity (the length of CG period) is in symbols.
  • the periodicity is defined in configured grant IE as shown in Table 2: Table 2 – Excerpt from 3GPP TS 38.331, ConfiguredGrantConfig IE: [0013]
  • the retransmissions are bulky, which is spectrally inefficient, because even if the subset of resource from the PUSCH allocation resource suffers channel errors, UE is forced to retransmit the whole PUSCH.
  • 3GPP is interested in utilizing Uplink Control Information, UCI, indication to notify a base station about unutilized resources in a CG period.
  • UCI Uplink Control Information
  • gNB is an example of a base station in NR scheme.
  • the resource configuration is based on single HARQ process allocation. This is because UE has to utilize whole resource every time whenever there is data, e.g., use padding bits to fill up PUSCH.
  • One aspect of the disclosure relates to a method performed by a user equipment.
  • the user equipment (UE) receives a CG configuration indicating an M number of PUSCHs allocated to the UE in a single CG period.
  • M is an integer larger than 1 and each of the M PUSCHs is associated with a HARQ process.
  • the UE then can determine HARQ process ID of each of the M PUSCHs.
  • HARQ ID of the first PUSCH among the M PUSCHs is determined by considering the number M in the legacy formula of the determining HARQ ID of the only PUSCH in a CG period.
  • M is multiplied prior to a modulo operation with a number of HARQ processes configured with the UE in determining HARQ ID of the first PUSCH.
  • HARQ IDs associated with the remaining PUSCHs are incremented by one based on the HARQ process ID associated with its preceding PUSCH.
  • Another aspect of the disclosure relates to a method performed by a network node from which a CG configuration is sent to a UE.
  • the CG configuration indicates an M number of PUSCHs allocated to the UE in a single CG period.
  • M is an integer larger than 1 and each of the M PUSCHs is associated with a HARQ process.
  • the network node should also be able to determine HARQ process ID of each of the M PUSCHs.
  • HARQ ID of the first PUSCH among the M PUSCHs is determined by considering the number M in the legacy formula of the determining HARQ ID of the only PUSCH in a CG period.
  • M is multiplied prior to a modulo operation with a number of HARQ processes configured with the UE in determining HARQ ID of the first PUSCH. Then, HARQ IDs associated with the remaining PUSCHs are incremented by one based on the HARQ process ID associated with its preceding PUSCH.
  • a user equipment and a network node related to CG PUSCH occasions increment are also introduced in other aspects of the disclosure.
  • Some embodiments provide mechanisms or framework to allocate multiple or incremented PUSCHs in a CG period using RRC and DCI based parameters.
  • a CG period can be allocated with multiple PUSCHs.
  • PUSCHs/TBs within a CG period can be based on resource configuration pattern, such as different TB sizes, multiple periodicities, different PDBs, priorities, etc.
  • RRC and DCI based mechanisms are provided for PUSCHs’ increment or allocation.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the entire data (bigger TB) needs to be retransmitted.
  • an gNB decides to prioritize some other transmission, the overlapping HARQ process(es) among the multiple HARQ processes can be preempted, while other HARQ processes remain unaffected. Otherwise, with a single HARQ process-based configuration (bigger TB), the entire data transmission will be deprioritized even though the overlap occurs over a small region of resource.
  • Utilization of a UCI indication to notify unused or unspent resources, for example PUSCH resources, in a CG period may not be possible if only a large TB is allocated as in legacy/existing CG, because the UE must utilize the entire resource as the TBS is mapped to the entire resource.
  • allocation of smaller TBs (multiple PUSCHs) instead of one large TB opens opportunities in the future for how a UE can autonomously utilize the unspent resources for different traffic. With a single PUSCH based configuration, it may not be possible to construct the PUSCH/TB with multiple data traffic if some logical channel (LCH) restrictions are applied.
  • LCH logical channel
  • Figure 1 illustrates a comparison of scheduling two consecutive PUSCHs between a legacy scheme and a multi-context scheme.
  • Figure 2 illustrates a comparison of multi-carrier scheduling between a legacy scheme and a multi-context scheme.
  • Figure 3 illustrates a flowchart of actions performed by a network node regarding a multi- PUSCH CG configuration in accordance with some embodiments of the disclosure.
  • Figure 4 illustrates a flowchart of actions performed by a user equipment regarding a multi- PUSCH CG configuration in accordance with some embodiments of the disclosure.
  • Figure 5 illustrates a flowchart of operations performed by a user equipment regarding a multi-PUSCH CG configuration in accordance with some embodiments of the disclosure.
  • Figure QQ1 shows an example of a communication system in accordance with some embodiments.
  • Figure QQ2 shows an example of a user equipment in accordance with some embodiments.
  • Figure QQ3 shows an example of a network node in accordance with some embodiments.
  • Figure QQ4 illustrates a block diagram of a host in Figure QQ1 in accordance with some embodiments.
  • Figure QQ5 illustrates a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the disclosure.
  • Figure QQ6 illustrates a communication diagram of a host communicating via a network node with a UE over a partially wirless connection in accordance with some embodiments.
  • Figure 6 illustrates a flowchart of actions performed by a user equipment regarding a multi- PUSCH CG configuration in accordance with some embodiments of the disclosure.
  • Figure 7 illustrates a flowchart of actions performed by a network node regarding a multi- PUSCH CG configuration in accordance with some embodiments of the disclosure.
  • DETAILED DESCRIPTION [0029] Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
  • multi-PUSCH allocation can also be termed as multi-slot or multi-HARQ or multi- transmission or multi-TB transmissions.
  • TB, HARQ process, and PUSCH are replaceable as they’re presented.
  • the essence is that a scheduled resource allocation can span over multiple scheduling time units (i.e., N time units, where N is an integer and N>1) in a CG period, where the time unit can be a slot (hence: multi-slot allocation), or the time unit can be a mini-slot (hence: multi-mini-slot allocation), or the time unit can be a set of N consecutive symbols.
  • N time units where N is an integer and N>1
  • the time unit can be a slot (hence: multi-slot allocation)
  • the time unit can be a mini-slot (hence: multi-mini-slot allocation)
  • the time unit can be a set of N consecutive symbols.
  • the scheduling need not be purely slot-based.
  • a CG period of 3 slots can have resource allocated for 3 PUSCHs within a period spanned over 1.5 slots, e.g., sym0 to sym 5 for TB1, sym6 to sym 13 for TB2 and sym 0 to sym 6 in the next slot for TB3, i.e., a type of multi-slot allocation with 3 PUSCHs or HARQ processes in each period.
  • CG PUSCH increment [0034]
  • the multiple PUSCHs are allocated in a CG period are applied to CG type 1 and Type 2 configuration.
  • This multi-PUSCH allocation can be indicated in DCI based activation for Type 2 CG allocation.
  • the multi-PUSCH allocation related information can be indicated by a bit or flag, which specifically indicates more than 1 PUSCH is allocated per CG period.
  • the multi-PUSCH allocation is indicated using a DCI which is scrambled new/special RNTI, CS-M-RNTI (where ‘-M-’ means multi).
  • the legacy CS- RNTI is used for single PUSCH allocation in the SPS/CG period.
  • the time domain resource allocation (TDRA) for multi- PUSCH in CG can be of based on following options.
  • a start and length indicator value (SLIV) is configured for each PUSCH. For example, if a row corresponds to M PUSCHs, then the row contains the SLIV of each PUSCH, as shown for example in Table 3.
  • the row describes only one SLIV, and there is an additional column that indicates ‘the number of PUSCHs’.
  • This means the SLIV is for the first PUSCH, and the remaining PUSCHs in a period have the same TB size (TBS) as the first PUSCH and are consecutive to each other in time domain in a CG period, as shown for example in Table 4.
  • TBS TB size
  • Table 3 illustrates an example in which a row in a TDRA table indicates four SLIVs, which corresponds to four PUSCHs in a CG period.
  • K2 is the time gap between DCI and the first PUSCH in the first CG period.
  • Table 4 illustrates an example in which a row in a TDRA table indicates one SLIV value pertaining to the first PUSCH of a number of PUSCHs in a CG period. An additional column indicates the number of PUSCHs in the period. The SLIV of other PUSCHs are derived using SLIV parameters of the first PUSCH, and assumes that all PUSCHs are consecutive and have same TBS.
  • a UE with default capability reads DCI format 0_X for a UL allocation scrambled with CS-RNTI, it is allocated with one PUSCH per CG period.
  • a UE configured with capability Q reads DCI 0_X for UL allocation scrambled with CS-M-RNTI, it will know it is allocated with a multi-PUSCH CG.
  • the functionality that specifies multi-PUSCH allocation in period (corresponding to increasing CG PUSCH transmissions in a duration as agreed in RAN1#110-bis-e) and the functionality that specifies UCI indication to notify unused PUSCH resources in period (correspond to point 1 in agreement, see below) can be configured using a single RRC parameter.
  • a gNB configures a UL transmission resource CG period. However, it is up to the UE to determine how it autonomously selects the resource for multiple PUSCHs.
  • a UE can use 2 PUSCHs with TBS (TB Size) of 20 PRBs for each PUSCH.
  • TBS TB Size
  • the UE will use the same resource to transmit 4 PUSCHs with TBS of 10 PRBs for each PUSCH.
  • a UE autonomously selects resources for multiple PUSCHs it can include some UCI to indicate how many PUSCHs UE is considering, e.g., in the previous embodiment, the UE can indicate UCI with parameter 2 or 4 in period X or Y respectively.
  • the HARQ process ID of remaining PUSCHs in a CG period is based on the following non-limiting options.
  • One option is to simply increment of ID by 1 with respect to the previous HARQ ID in a period. For example, if a CG period allocated is with 4 PUSCHs in a CG period X, the 1st PUSCH has HARQ ID is H, then HARQ IDs of remaining PUSCHs are H+1, H+2 and H+3.
  • the HARQ ID of each PUSCH can be derived considering the non- limited parameters of the resource (time and frequency) of the PUSCH, the period ID in a CG, e.g., period X, the number of allocated PUSCHs in a CG period, and other parameters, such as SFN, number of slots, numerology, etc.
  • HARQ IDs of PUSCHs in a CG period with M PUSCHs allocated is derived based on some agreed formulae.
  • the example of HARQ ID derivation formulae specified in 3GPP TS 38.321 may be modified by taking account M HARQ processes/PUSCHs per period instead of 1 PUSCH per period in existing spec.
  • the above will give the HARQ ID of the first PUSCH in the period.
  • the remaining PUSCHs in the CG period will have HARQ ID incremented.
  • Figure 6 and Figure 7 illustrate steps of the above embodiment respectively from a user equipment and a network node’s angle.
  • the user equipment receives (step 610) a CG configuration indicating an M number of PUSCHs allocated to the UE in a single CG period.
  • M is an integer larger than 1 and each of the M PUSCHs is associated with a HARQ process.
  • the UE then can determine HARQ process ID of each of the M PUSCHs.
  • HARQ ID of the first PUSCH among the M PUSCHs is determined by considering the number M in the legacy formula of the determining HARQ ID of the only PUSCH in a CG period.
  • the network node transmits (Step 710) a CG configuration to a UE.
  • the CG configuration indicates an M number of PUSCHs allocated to the UE in a single CG period.
  • M is an integer larger than 1 and each of the M PUSCHs is associated with a HARQ process.
  • the network node should also be able to determine HARQ process ID of each of the M PUSCHs.
  • HARQ ID of the first PUSCH among the M PUSCHs is determined by considering the number M in the legacy formula of the determining HARQ ID of the only PUSCH in a CG period. In particular, M is multiplied prior to a modulo operation with a number of HARQ processes configured with the UE in determining HARQ ID of the first PUSCH (Step 720). Then, HARQ IDs associated with the remaining PUSCHs are incremented by one based on the HARQ process ID associated with its preceding PUSCH (Step 730).
  • the slot with TB allocation is an odd slot.
  • the even slot in a period has no PUSCH allocation.
  • HARQ IDs for PUSCHs in a period X, which falls in slot number 2 and 3, and next period, i.e., X+1 (slot number 4 to slot 5) in SFN 2. Note, slots are numbered 0 to 13, SFN are numbered 0 to 1023.
  • the HARQ ID of the first PUSCH is calculated. Assume the CG can have a maximum of 16 HARQ IDs (0 to 15).
  • each PUSCH in a period can be accompanied by repetitions, which can be Type 1 and Type 2 based repetitions.
  • the PUSCHs in a CG period can be allocated in a consecutive manner or with some periodicity (i.e., another periodicity that is different from CG periodicity).
  • the PUSCHs in a CG period can have their own periodicity D. For example, assume a CG has some D periodicity, i.e., CG period length is D symbols/slots (the existing periodicity parameter), where each period has 4 PUSCHs allocated.
  • These 4 PUSCHs can be allocated in a period with some periodicity, say D time units (new proposed parameter), e.g., 5 symbols, i.e., the next PUSCH within period starts after 5 symbols from the end of previous PUSCH.
  • D time units new proposed parameter
  • the PUSCHs in a CG period can have PUSCH mapping Type A or B.
  • all the PUSCHs in a period may have (1) the same absolute end time of their CG timers (CGT), meaning that the last PUSCH have smallest CGT or (2) the same duration of their CGT timers, meaning that the absolute end time of PUSCHs’ CGT timers are different.
  • the PUSCHs in a CG period can have time-gaps.
  • the PUSCHs in a CG period can be allocated over different carriers.
  • the UE is configured with CG Type 2 configuration with a periodicity P. Additionally, the UE is configured with an “accumulate CG occasion pattern” configuration.
  • the UE if the UE has M occasions within a period activated and then receives a de-activation DCI the UE will assume the de-activation is for all occasions.
  • the joint de-activation of multiple CGs is replaced by joint de-activation of activation instances for the same CG configuration.
  • the UE may be configured to have up to M occasions within a period.
  • the HARQ process field in de-activation may indicate the activation instance 0 ⁇ i ⁇ M, where the first activation of the CG corresponds to instance 0 and so on.
  • the UE may be configured with a nrofDCIContexts for one or more DCI formats wherein one or more of the fields Field1, ..., FieldN has two or more contexts indicated by nrofDCIContexts.
  • DCI format 1_1 the fields Frequency domain resource assignment, Time domain resource assignment, ⁇ MCS, NDI, RV ⁇ for TB1 (and TB2) and ⁇ MCS, NDI, RV ⁇ for TB3 (and TB4)
  • UE knows that upcoming DCI may contain scheduling parameters/information for two contexts.
  • the number of contexts for multi-context DCI may be configured different for different CORESETs, search spaces, RNTI.
  • UE may be configured with a RNTI_SINGLE_CONTEXT used to receive DCIs comprising a single context and a RNTI_MULTI_CONTEXT used to receive DCIs comprising two or more contexts.
  • the time reference for PUSCH is w.r.t the time location for the scheduling DCI, e.g., the last symbol of the PDCCH comprising the scheduling DCI.
  • the time reference for first context may be same as for legacy DCI while other contexts may need a different time reference to avoid needing to increase the bit- width for fields such as a time domain resource assignment.
  • the new time reference could be with respect to an imaginary PDCCH with same start and end symbol as the PDCCH (scheduling PDCCH) with the scheduling DCI but located in a later slot n (or sub-slot) than the slot n_s scheduling PDCCH, wherein the later slot n for a DCI context i can be (1) n is the slot (sub-slot) after the slot n_e in which the last PUSCH for context i-1 has ended, or (2) n is the earliest slot (sub-slot) in which a legacy DCI could be sent on a PDCCH with respect to scheduling limitations.
  • the slot reference n for the imaginary PDCCH can be UL slot (sub-slot).
  • the DCI comprises a field nrofScheduledContexts that indicates number of contexts present in DCI. This enables a multi- context DCI to comprise a dynamic number of contexts.
  • the configured nrofContexts (some RRC parameter) would be a max number of contexts that can be scheduled by the multi-context DCI while nrofScheduledContexts (field in DCI) would indicate the number of context present in the multi-context DCI.
  • nrofContexts would hence determine (together with other configuration parameters) the size of the multi-context DCI.
  • the multi-context DCI would comprise un-used bits.
  • FIG. 3 illustrates a flow chart of operations that can be performed by a network node in accordance with some embodiments of the present disclosure.
  • the operations performed by the network node includes preparing (310) a CG configuration that allocates a plurality of PUSCHs to UE in a single CG period.
  • the operations further include transmitting (320) the CG configuration to the UE, and receiving (330) uplink communications from the UE in accordance with the CG configuration.
  • Figure 4 illustrates a flow chart of operations that can be performed by a user equipment in accordance with some embodiments of the present disclosure. For example, these operations could be performed by a UE that is in sidelink communication with another UE.
  • the operations performed by the UE includes preparing (410) a CG configuration that allocates a plurality of sidelink channels to a sidelink UE in a single CG period.
  • the operations further include transmitting (420) the CG configuration to the sidelink UE, and receiving (430) communications from the sidelink UE in accordance with the CG configuration.
  • Figure 5 illustrates a flow chart of operations that can be performed by a UE in accordance with some embodiments of the present disclosure.
  • the operations performed by the UE includes receiving (510) a CG configuration that indicates that a plurality of PUSCHs have been allocated for a single CG period.
  • the operations further include transmitting (520) uplink communications in accordance with the CG configuration.
  • Figure QQ1 shows an example of a communication system QQ100 in accordance with some embodiments.
  • the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108.
  • RAN radio access network
  • the access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3 rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • the network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 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 QQ100 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 QQ100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs QQ112 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 QQ110 and other communication devices.
  • the network nodes QQ110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs QQ112 and/or with other network nodes or equipment in the telecommunication network QQ102 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 QQ102.
  • the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116.
  • the core network QQ106 includes one more core network nodes (e.g., core network node QQ108) 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 QQ108.
  • 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 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
  • UPF User Plane Function
  • the host QQ116 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. [0086] As a whole, the communication system QQ100 of Figure QQ1 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 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.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 6G wireless local area network
  • WiFi wireless local area network
  • WiMax Worldwide Interoperability for Micro
  • the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 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 IoT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs QQ112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104.
  • 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 QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and/or QQ112d) and network nodes (e.g., network node QQ110b).
  • the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs.
  • the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114.
  • the hub QQ114 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 QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
  • the hub QQ114 may have a constant/persistent or intermittent connection to the network node QQ110b.
  • the hub QQ114 may also allow for a different communication scheme and/or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and/or QQ112d), and between the hub QQ114 and the core network QQ106.
  • the hub QQ114 is connected to the core network QQ106 and/or one or more UEs via a wired connection.
  • the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection.
  • the hub QQ114 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 QQ110b.
  • the hub QQ114 may be a non- dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • Figure QQ2 shows a UE QQ200 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 to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure QQ2. The level of integration between the components may vary from one UE to another UE.
  • the processing circuitry QQ202 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 QQ210.
  • the processing circuitry QQ202 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.
  • FPGAs field-programmable gate arrays
  • ASICs application specific integrated circuits
  • DSP digital signal processor
  • the processing circuitry QQ202 may include multiple central processing units (CPUs).
  • the input/output interface QQ206 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 QQ200.
  • 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.
  • the power source QQ208 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 QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and/or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208.
  • the memory QQ210 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 read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216.
  • the memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.
  • the memory QQ210 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
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off- load 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 QQ210, which may be or comprise a device-readable storage medium.
  • the processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212.
  • the communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222.
  • the communication interface QQ212 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 QQ218 and/or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface QQ212 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/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface QQ212, 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.
  • 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. In response to the received wireless input 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 (IoT) 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.
  • IoT Internet of Things
  • Non-limiting examples of such an IoT 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- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot.
  • UAV Un
  • a UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE QQ200 shown in Figure QQ2.
  • 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 3GPP 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.
  • 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.
  • Figure QQ3 shows a network node QQ300 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 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. 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 QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308.
  • the network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB 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 QQ300 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes. For example, 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 QQ300 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs).
  • the network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies.
  • RFID Radio Frequency Identification
  • the processing circuitry QQ302 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 QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.
  • the processing circuitry QQ302 includes a system on a chip (SOC).
  • the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314.
  • the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.
  • the memory QQ304 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 QQ302.
  • 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
  • the memory QQ304 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 QQ302 and utilized by the network node QQ300.
  • the memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and/or any data received via the communication interface QQ306.
  • the processing circuitry QQ302 and memory QQ304 is integrated.
  • the communication interface QQ306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface QQ306 comprises port(s)/terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310.
  • Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322.
  • the radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302.
  • the radio front-end circuitry QQ318 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 QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and/or amplifiers QQ322.
  • the radio signal may then be transmitted via the antenna QQ310.
  • the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318.
  • the digital data may be passed to the processing circuitry QQ302.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).
  • the antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.
  • the antenna QQ310, communication interface QQ306, and/or the processing circuitry QQ302 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.
  • the antenna QQ310, the communication interface QQ306, and/or the processing circuitry QQ302 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 QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein.
  • the network node QQ300 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 QQ308.
  • the power source QQ308 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 QQ300 may include additional components beyond those shown in Figure QQ3 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 QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.
  • Figure QQ4 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure QQ1, in accordance with various aspects described herein.
  • the host QQ400 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 QQ400 may provide one or more services to one or more UEs.
  • the host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments.
  • the memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE.
  • Embodiments of the host QQ400 may utilize only a subset or all of the components shown.
  • the host application programs QQ414 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 QQ414 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.
  • FIG. 1 is a block diagram illustrating a virtualization environment QQ500 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 QQ500 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
  • QQ500 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.
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Hardware QQ504 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 QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.
  • the VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506.
  • a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, 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 network function virtualization
  • 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.
  • a VM QQ508 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 QQ508, and that part of hardware QQ504 that executes that VM forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.
  • Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g.
  • hardware QQ504 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. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure QQ6 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.
  • Example implementations, in accordance with various embodiments, of the UE such as a UE QQ112a of Figure QQ1 and/or UE QQ200 of Figure QQ2), network node (such as network node QQ110a of Figure QQ1 and/or network node QQ300 of Figure QQ3), and host (such as host QQ116 of Figure QQ1 and/or host QQ400 of Figure QQ4) discussed in the preceding paragraphs will now be described with reference to Figure QQ6.
  • host QQ602 Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host QQ602 also includes software, which is stored in or accessible by the host QQ602 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 QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection QQ650.
  • the network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606.
  • connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure QQ1) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 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 QQ606 with the support of the host QQ602.
  • an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602.
  • 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 QQ650 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 connection QQ650.
  • the OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606.
  • the connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host QQ602 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 QQ606.
  • the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction.
  • the host QQ602 initiates a transmission carrying the user data towards the UE QQ606.
  • the host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606.
  • the request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606.
  • the transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.
  • the UE QQ606 executes a client application which provides user data to the host QQ602.
  • the user data may be provided in reaction or response to the data received from the host QQ602.
  • the UE QQ606 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 QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604.
  • the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602.
  • the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment.
  • factory status information may be collected and analyzed by the host QQ602.
  • the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 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.
  • 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 QQ602 and/or UE QQ606.
  • sensors may be deployed in or in association with other devices through which the OTT connection QQ650 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 QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. 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 QQ602.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.
  • the computing devices described herein e.g., UEs, network nodes, hosts
  • other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • 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.
  • some or all of the functionality described herein may be provided by 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.
  • Embodiments A1 A method performed by a user equipment, UE, comprising: preparing (410) a configured grant, CG, configuration for a sidelink UE that allocates a plurality of sidelink channels to the sidelink UE in a single CG period; transmitting (420) the CG configuration to the sidelink UE; and receiving (430) sidelink transmissions from the sidelink UE in accordance with the CG configuration.
  • a user equipment comprising: preparing (410) a configured grant, CG, configuration for a sidelink UE that allocates a plurality of sidelink channels to the sidelink UE in a single CG period; transmitting (420) the CG configuration to the sidelink UE; and receiving (430) sidelink transmissions from the sidelink UE in accordance with the CG configuration.
  • a method performed by a user equipment, UE comprising: receiving (510) a configured grant, CG, configuration that indicates that a plurality of physical uplink shared channels, PUSCHs, have been allocated to the UE for a single CG period; and transmitting (520) uplink communications in accordance with the CG configuration.
  • A3. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.
  • a method performed by a network node comprising: preparing (310) a configured grant, CG, configuration for a user equipment, UE, that allocates a plurality of physical uplink shared channels, PUSCHs, to the UE in a single CG period; transmitting (320) the CG configuration to the UE; and receiving (330) uplink transmissions from the UE in accordance with the CG configuration.
  • a user equipment comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry. C2.
  • a network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.
  • a user equipment comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.
  • the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.
  • the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • UE user equipment
  • the method of the previous embodiment further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • the method of the previous embodiment further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.
  • the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • UE user equipment
  • the method of the previous embodiment further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • C15 The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • the processing circuitry of the host is configured to execute a host application that provides the user data
  • the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • a communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • UE user equipment
  • the communication system of the previous embodiment further comprising: the network node; and/or the user equipment.
  • C23. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.
  • OTT over-the-top
  • the host of the previous 2 embodiments wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • the initiating receipt of the user data comprises requesting the user data.
  • C27. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.
  • ConfiguredGrantConfig information element -- ASN1START -- TAG-CONFIGUREDGRANTCONFIG-START
  • ConfiguredGrantConfig SEQUENCE ⁇ frequencyHopping ENUMERATED ⁇ intraSlot, interSlot ⁇ OPTIONAL, -- Need S cg-DMRS-Configuration DMRS-UplinkConfig, mcs-Table ENUMERATED ⁇ qam256, qam64LowSE ⁇ OPTIONAL, -- Need S mcs-TableTransformPrecoder ENUMERATED ⁇ qam256, qam64LowSE ⁇ OPTIONAL, -- Need S uci-OnPUSCH SetupRelease ⁇ CG-UCI-OnPUSCH ⁇ OPTIONAL, -- Need M resourceAllocation ENUMERATED ⁇ resourceAllocationType0, resourceAllocationType1, dynamicSwitch ⁇ , rbg-Size ENUMERATED ⁇ config2 ⁇ OPTIONAL, -- Need S powerControlLoopToUse ENUM
  • the field rityIndex- r16 is con The field rityIndex- r16 is con cg-COT- Indicates to indicate t itiating device in cg-COT- Indicates l to 14*n, where n i (see 37.213 [4 cg-DMRS DMRS co cg-minD Indicates ntaining the downl on is not considere nding on the config 15 kHz: 30 kHz: 60 kHz: 120 kHz: 29, 30, 31, 32 ⁇ 480 kHz: 04, 108, 112, 116, 960 kHz: 184, 192, 200, 208, cg-nrofP Indicates al PUSCH a Retransm cg-nrofS Indicates S 38.214 [19], clau cg-Retra Indicates Retransm th harq- ProcID-O cg-Starti This field applicabl or would share gN
  • frequencyDomainAllocation Indica frequ The v sent, frequ ], claus frequ Frequ frequ Indica ], claus hoppi harq- For o proce rq- procI harq- Indica g- Retra mapp Indica config PUSC mcs- Indica 4.
  • XR services include downlink (DL) and uplink (UL) traffic flows, e.g., DL/UL video application packets (also referred to as scene traffic in UL), DL audio application packets, and UL pose/control application packets. These flows have different characteristics (e.g., bit rate, periodicity, jitter) and requirements in terms of (application) packet delay budget (PDB) [5].
  • DL/UL video application packets also referred to as scene traffic in UL
  • DL audio application packets also referred to as scene traffic in UL
  • UL pose/control application packets e.g., DL/UL video application packets (also referred to as scene traffic in UL)
  • PDB packet delay budget
  • Observation 1 Dynamic Scheduling and Granting is a suitable transmission scheme to deal with varying and large-sized application packets and possible jitter for DL/UL video XR traffic.
  • Observation 2 Configured Grant is a suitable transmission scheme for predictable and fixed small-sized UL traffic, e.g., pose/control and BSRs triggered by UL video XR traffic.
  • CG Configured Grant
  • DG scheduling for improving the XR capacity is the delay due to SR and/or BSR for the gNB to determine the size of proper grant after receiving BSR. In our view, the delay can be diminished based on mechanisms using existing specifications with/without relying on XR awareness.
  • the network can implement DG scheduling in multiple ways. • For example, pre-scheduling based on dynamic allocation, being already available in gNB implementations, can be used to mimic configured scheduling while keeping the flexibility of granting dynamic resources to dynamic XR traffic.
  • XR awareness related information available to the gNB e.g., traffic periodicity information, and/or statistics on data packet size.
  • a UE can be allocated grants at regular periods without the UE needed to send an SR, while the dynamic scheduling properties are preserved by updating the link adaptation.
  • a normal DG scheme non-prescheduling
  • the gNB can provide an initial grant that enables the UE to initiate data transmission while sending the BSR.
  • the resource allocation in the initial grant (after the SR) can leverage information on XR packet size statistics (e.g., a grant fitting an XR packet of minimum size can be provided).
  • BSR can be used to decide if further resources are needed in the next slots to finalize the transmission of the XR packet.
  • Another DG implementation variant is to rely on CG resources to indicate to the gNB the arrival of new data instead of SR.
  • the NW can configure CG resources to not only receive indication of new data, but also receive an BSR to have an informed initial grant.
  • the gNB continues to serve the XR traffic using dynamic scheduling.
  • Case 1 Dynamic grant with SR followed by a small initial UL grant: o
  • the scheduling is based on dynamic grants where it is assumed an SR is triggered upon arrival of a new video packet in the UE buffer.
  • the network provides a small initial grant of size 288 bits, upon receiving the SR. No knowledge of XR traffic is assumed. See Figure 1.
  • Figure 1 Illustration of dynamic scheduling grant scheme with SR followed by initial small UL grant (Case 1)
  • Case 2 Dynamic grant with SR followed by a larger initial UL grant: o
  • the scheduling is based on dynamic grants where it is assumed an SR is triggered upon arrival of a new video packet in the UE buffer.
  • the network provides an initial grant of size 117 kbit as the minimum XR packet size used in simulation (See Note 1 below), upon receiving an SR. No knowledge of XR traffic periodicity is assumed. See Figure 2. ⁇ Note 1: Given the traffic model specified in 38.838 [4], frame rate of 60 fps and data rate of 10 Mbit/s give approximate average packet size of 167 kbit. The minimum and maximum packet size are derived in such a manner that 99% of range of the gaussian distribution centred around the mean is covered, i.e., from mean minus three times standard deviation to mean plus three times standard deviation. This gives minimum packet size 117 kbit and maximum size 217 kbit.
  • FIG. 2 Illustration of dynamic scheduling grant scheme with SR followed by initial larger UL grant (Case 2) • Case 3: Pre-scheduling dynamic grant (Pre-scheduling DG): o
  • the scheduling is based on dynamic grants where it is assumed that the network is provided with XR traffic periodicity. An initial grant to the UE when its traffic is expected is transmitted (implementation-based learning) without using SR.
  • the network provides an initial grant of size 117 kbit as the minimum XR packet size used in simulation. See Figure 3.
  • FIG. 3 Illustration of Pre-scheduling dynamic grant scheme (Case 3) • Case 4: Configured grant: o The scheduling is based on configured grants where it is assumed that the network uses information on traffic periodicity, size statistics, TDD pattern, PDB, etc., to derive proper configurations for CG size and periodicity. The initial transmissions happen only on CG occasions, and retransmissions can occur on dynamic grants. See Figure 4. o We have simulated the performance curves for the following CG configuration parameters, and picked the best configuration for comparison with other schemes.
  • ⁇ PDB 30 ms, CG with size / periodicity of (30 kbit / 2.5 ms), (60 kbit / 5 ms), and (90 kbit / 7.5 ms) • The CG configuration with 5 ms periodicity and 60 kbit occasion size outperforms other CG configurations.
  • ⁇ PDB 15 ms, CG with size / periodicity of (60 kbit / 2.5 ms) and (100 kbit / 2.5 ms) • The CG configuration with 2.5 ms periodicity and 60 Kbit occasion size outperforms the other CG configuration.
  • FIG. 4 Illustration of configured grant scheduling scheme (Case 4) • Case 5: Hybrid scheduling based configured and dynamic grant (Hybrid CG-DG): o
  • the scheduling is based on a combined use of configured and dynamic grants.
  • SR resources are not used. Instead, CG resources are configured with minimum size in every UL slot in order to transmit BSR and small amount of data when new data arrives.
  • a XR packet arrives in a buffer, the UE uses the nearest possible CG occasion for BSR transmission and possibly small amount of data. The network can thus use the BSR to provide dynamic grants for the following data transmission. No knowledge of XR traffic periodicity is assumed. See Figure 5.
  • FIG. 5 Illustration of Hybrid scheduling based configured and dynamic grant (Hybrid CG-DG) (Case 5) • Case 6: Dynamic scheduling with genie BSR (DG with genie BSR): o The scheduling is based on dynamic grants where it is assumed BSR is available with zero delay at the scheduler when a new packet arrives in the UE buffer, to be used for indicating UL grants to the UE. Hence, in this case, no SR or BSR delay is assumed. This case is simulated to show the upper bound on capacity performance. See Figure 6.
  • Proposal 2 To assess the necessity and benefit of the candidate CG enhancement techniques for improving capacity of XR video traffic, the CG-based transmissions for XR video traffic should be compared against DG-based transmissions for XR video traffic.
  • Proposal 3 The necessity and benefit of the candidate enhancement techniques of DG and CG schemes for XR services should be assessed as compared to existing schemes base d on Rel-17 specifications, and/or under the assumption of XR awareness at RAN. Moreover, based on the analysis and evaluation results for different study cases, we observe the following: Observation 3 Dynamicity of XR traffic with frequent/periodic occasions can be handled by existing specifications and gNB implementation. Observation 4 Necessity of supporting new features to enable dynamic adaptation of CG transmission is not justified.
  • Proposal 4 Deprioritize studying the enhancements based on dynamic adaptations for CG based transmissions. 2.2.2 Indication of unused CG occasion(s)/resource(s) by the UE From our CG and DG evaluations, the implementation of DG using hybrid method or pre-scheduling provides the largest gains. The capacity gains presented for any CG enhancement do not seem to surpass DG dramatically to justify the need for enhancements. With respect to the specific enhancement technique where the overbooked CG resources can be reused by enabling dynamic indication from the UE to provide information on the utility of the configured resources, we make the following observations: • The scheme is intended to diminish the SR/BSR delay when DG is applied but suffers from inefficient resource utilization.
  • the proposed solution to improve resource utilization is by signalling from the UE.
  • the usefulness of the scheme depends on the signalling delay. This is because, there will be always delay between CG indication transmission and sending DCI to other/same UE for utilization of unused resources and finally transmission by the UE on the unused resources.
  • CG indication functionality even we employ CG indication functionality, one cannot save the resource wastage fully.
  • the utilization of UCI will slightly impact the shared channel capacity negatively, which may be small but not zero.
  • the inclusion of dynamic signaling to CG will bring CG closer to DG and its existing implementation flavors.
  • the specification effort can be large except if the indication is based on exiting CG-UCI framework, which is already standardized for NR-U CG PUSCH transmission.
  • Proposal 6 The enhancements based on CG-UCI framework to provide indication of the unused CG PUSCH occasion(s) or resource(s) by the UE can be considered to study if the corresponding capacity performance gains with reasonable signalling delay assumptions are provided. 2.2.3 Increase CG PUSCH transmission occasions in a duration
  • One of the enhancements for CG discussed in the last meeting is the support of multiple PUSCH occasions per CG period to cater large video packets.
  • DG based allocation is already capable of supporting dynamic variations in XR video traffic, so any enhancement to CG cannot provide capacity higher than dynamic grant scheduling.
  • the network may need to spend signalling to allocate individual CG IDs, then configure a group ID mapping to a group of individual CG IDs, in order to activate/update/reactivate CGs with required parameters. • It may increase both delay and PDCCH resource usage as control signalling will be spent, at first, perhaps creating individual CGs. • It may also need modification of DCI, or even addition of fields for group activation. This is not similar to group deactivation, where many of the fields are not useful, and thus used for validation or indicate group ID in the HARQ bitfield provided by ConfiguredGrantConfigType2DeactivationStateList.
  • timing There are complicated timing rules already in current specification for, e.g., PUSCH preparation time.
  • the PUSCH preparation time has been discussed intensively in previous releases when new functionality has been introduced and the resulting rules have become more and more complicated. We expect it will be required to introduce additional time for the PUSCH preparation time if a TB would be re-transmitted on a carrier different from the carrier used for previous transmission.
  • gNB processing delay would also likely be impacted by that a TB is re-transmitted on a different carrier since soft bits to be combined do not originate from same carrier. Since timing restrictions impose scheduling restrictions and it in turn limits the potential gain with the functionality. Observation 6 Re-transmitting a TB on another carrier than the carrier used for initial transmission will likely lead to timing restrictions for both UE and gNB: - For uplink TB transmissions, additional UE restrictions w.r.t PUSCH preparation time are expected. - For downlink, additional UE restrictions w.r.t., PDSCH-to-HARQ feedback time are expected.
  • Proposal 9 Deprioritize the mechanism to enable HARQ retransmission of a TB on a different carrier.
  • MG Measurement Gap
  • SMTC window can be 1-5 ms and there are scenarios where MG is not needed.
  • RAN4 was not included in Rel-18 XR SI, such studies go beyond agreed Rel-18 scope and allocated resources. However, proper study involving all needed groups can be done in future. Proposal 10 RAN1 can recommend to RAN2 and RAN4 to study in future a need and possibility for potential improvements at least for some scenarios on scheduling restrictions due to measurements. 3 CONCLUSION In the previous sections we made the following observations: Observation 1 alone........ Dynamic Scheduling and Granting (DG) is a suitable transmission scheme to deal with varying and large-sized application packets and possible jitter for DL/UL video XR traffic. Observation 2..
  • DG Dynamic Scheduling and Granting
  • CG Configured Grant
  • Proposal 10 can recommend to RAN2 and RAN4 to study in future a need and possibility for potential improvements at least for some scenarios on scheduling restrictions due to measurements.

Landscapes

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

Abstract

La divulgation concerne des procédés pour un nœud de réseau et un équipement utilisateur associé à un incrément d'occasions de CG de PUSCH. Un nœud de réseau transmet une configuration de CG à un UE indiquant de multiples occasions de PUSCH dans une période de CG déterminant un ID de processus de HAQR associé à chacune des multiples occasions de PUSCH en tenant compte du nombre de multiples occasions de PUSCH planifiées pour l'UE.
PCT/EP2023/080229 2022-11-07 2023-10-30 Incrément d'occasions de pusch à autorisation configurée WO2024099812A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263423183P 2022-11-07 2022-11-07
US63/423,183 2022-11-07

Publications (1)

Publication Number Publication Date
WO2024099812A1 true WO2024099812A1 (fr) 2024-05-16

Family

ID=88650734

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/080229 WO2024099812A1 (fr) 2022-11-07 2023-10-30 Incrément d'occasions de pusch à autorisation configurée

Country Status (1)

Country Link
WO (1) WO2024099812A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022031102A1 (fr) * 2020-08-06 2022-02-10 엘지전자 주식회사 Procédé de transmission de canal de liaison montante, dispositif utilisateur, dispositif de traitement, support de stockage, programme informatique, procédé de réception de canal de liaison montante, et station de base
WO2022084525A1 (fr) * 2020-10-23 2022-04-28 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareils pour une meilleure autorisation configurée pour des applications à faible latence

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022031102A1 (fr) * 2020-08-06 2022-02-10 엘지전자 주식회사 Procédé de transmission de canal de liaison montante, dispositif utilisateur, dispositif de traitement, support de stockage, programme informatique, procédé de réception de canal de liaison montante, et station de base
US20230309090A1 (en) * 2020-08-06 2023-09-28 Lg Electronics Inc. Method for transmitting uplink channel, user device, processing device, storage medium and computer program, and method for receiving uplink channel, and base station
WO2022084525A1 (fr) * 2020-10-23 2022-04-28 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareils pour une meilleure autorisation configurée pour des applications à faible latence

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.211
3GPP TS 38.213
3GPP TS 38.214
3GPP TS 38.321
3GPP TS 38.331

Similar Documents

Publication Publication Date Title
WO2023209668A1 (fr) Signalisation et mécanismes pour scénarios de liaison latérale à sauts multiples de transmission de message de découverte d'ue relais
WO2024099812A1 (fr) Incrément d'occasions de pusch à autorisation configurée
WO2024099921A1 (fr) Procédé de transmission d'informations de commande de liaison montante et dispositif de communication
WO2024099218A1 (fr) Communication de liaison latérale avec de multiples ressources de rétroaction
WO2023170664A1 (fr) États de tci unifiés pour pdsch à multiples trp
WO2024003382A1 (fr) Modification d'attributions périodiques à intervalles multiples
WO2024033821A1 (fr) Transmission à créneaux multiples avec une attribution préconfigurée
WO2024102058A1 (fr) Indication de planification d'une priorisation d'ensemble de pdu en liaison montante
WO2024096807A1 (fr) Pdsch pour équipement utilisateur à capacité réduite
WO2023166497A1 (fr) Transmission et réception de csi-rs avec états tci unifiés pour de multiples trps
WO2023166498A1 (fr) Systèmes et procédés d'association implicite entre une transmission pusch à trp multiples et des états tci unifiés
WO2023052049A1 (fr) Indication de prise en charge de réseau de diverses fonctionnalités de liaison latérale (sl)
WO2022254406A1 (fr) Démarrage dynamique du temporisateur de retransmission drx pour des applications à latence limitée
WO2023073677A2 (fr) Mesures dans un réseau de communication
WO2024110017A1 (fr) Transmissions autonomes sur des ressources partagées
WO2023095093A1 (fr) Signalisation mac ce destinée à supporter des fonctionnements à la fois conjoints et séparés de tci dl/ul
WO2024096811A1 (fr) Mesure et rapport de rvqoe pour connectivité double
WO2024035292A1 (fr) Configuration de ressource adaptative de domaine fréquentiel pour attribution multi-créneau
WO2023083882A1 (fr) Autorisation configurée pour une transmission de liaison montante multi-panneau
WO2023152197A1 (fr) Gestion de temporisateur de réception discontinue avec retour de demande automatique de répétition hybride de planification semi-persistante
WO2023069005A1 (fr) Configurations de drx multiples avec informations de flux de trafic
JP2024520904A (ja) 半静的に設定された周期的ｐｕｃｃｈについてのｐｕｃｃｈキャリア切替え
WO2024096789A1 (fr) Accès aléatoire pendant cg-sdt
WO2024035312A1 (fr) Dispositifs et procédés de commutation de transmission de liaison montante dynamique
WO2023048629A1 (fr) Procédés, appareil et supports lisibles par ordinateur se rapportant à la congestion dans des réseaux sans fil