WO2024011244A1 - Commande de puissance et chronologie pour ordonnancement multi-cellules pour des opérations de nouvelle radio - Google Patents

Commande de puissance et chronologie pour ordonnancement multi-cellules pour des opérations de nouvelle radio Download PDF

Info

Publication number
WO2024011244A1
WO2024011244A1 PCT/US2023/069814 US2023069814W WO2024011244A1 WO 2024011244 A1 WO2024011244 A1 WO 2024011244A1 US 2023069814 W US2023069814 W US 2023069814W WO 2024011244 A1 WO2024011244 A1 WO 2024011244A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
scheduling
pdsch
cell
ack
Prior art date
Application number
PCT/US2023/069814
Other languages
English (en)
Inventor
Yi Wang
Yingyang Li
Gang Xiong
Original Assignee
Intel Corporation
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 Intel Corporation filed Critical Intel Corporation
Publication of WO2024011244A1 publication Critical patent/WO2024011244A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • 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/1861—Physical mapping arrangements
    • 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
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/26—TPC being performed according to specific parameters using transmission rate or quality of service QoS [Quality of Service]
    • H04W52/267—TPC being performed according to specific parameters using transmission rate or quality of service QoS [Quality of Service] taking into account the information rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/30—TPC using constraints in the total amount of available transmission power
    • H04W52/32—TPC of broadcast or control channels
    • H04W52/325—Power control of control or pilot channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/38—TPC being performed in particular situations
    • H04W52/48—TPC being performed in particular situations during retransmission after error or non-acknowledgment

Definitions

  • This disclosure generally relates to systems and methods for wireless communications and, more particularly, to power control and timeline for multi-cell scheduling for new radio (NR) operations.
  • NR new radio
  • FIGs. 1-4 depict illustrative schematic diagrams for advanced multi-cell scheduling and power control, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 5 illustrates a flow diagram of a process for an illustrative advanced multi-cell scheduling and power control system, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6 illustrates an example network architecture, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7 schematically illustrates a wireless network, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 8 illustrates components of a computing device, in accordance with one or more example embodiments of the present disclosure.
  • the new radio (NR) architecture is designed to support a wide array of devices with vastly different capabilities and requirements. It's flexible and scalable to accommodate the high demand of future network usage, including Internet of Things (loT) devices, and use cases such as machine-to-machine communication.
  • LoT Internet of Things
  • NR supports a wide range of spectrum in different frequency ranges. It is expected that there will be increasing availability of spectrum in the market for 5G Advanced possibly due to re-farming from the bands originally used for previous cellular generation networks.
  • FR1 bands the available spectrum blocks tend to be more fragmented and scattered with narrower bandwidths.
  • FR2 bands and some FR1 bands the available spectrum can be wider such that intra-band multi-carrier operation is necessary.
  • the current scheduling mechanism only allows scheduling of single cell physical uplink shared channel (PUSCH)/ physical downlink shared channel (PDSCH) per a scheduling downlink control information (DCI).
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • DCI scheduling downlink control information
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • DCI scheduling downlink control information
  • a DCI is used to schedule PDSCH or PUSCH transmissions in more than one cell or component carrier (CC), where each PDSCH or PUSCH is scheduled in one cell or CC.
  • Example embodiments of the present disclosure relate to systems, methods, and devices for power control and timeline for multi-cell scheduling for NR operations.
  • an advanced multi-cell scheduling and power control system may facilitate mechanisms for UL power determination and timeline for multi-cell scheduling.
  • an advanced multi-cell scheduling and power control system may facilitate UL power control for PUCCH carrying HARQ-ACK for PDSCHs scheduled by multi-cell scheduling downlink control information (DCI).
  • DCI downlink control information
  • a DCI format is a structured format of bits used in wireless communication protocols, such as those used in LTE and 5 G NR networks, to convey control information from the base station to the user equipment (UE).
  • an advanced multi-cell scheduling and power control system may facilitate a timeline for PDSCH/PUSCH scheduled by multi-cell scheduling DCI.
  • FIGs. 1-4 depict illustrative schematic diagrams for advanced multi-cell scheduling and power control, in accordance with one or more example embodiments of the present disclosure.
  • a DL downlink DCI only schedules a PDSCH or multiple PDSCHs on an active DL BWP of a cell.
  • the UE may generate HARQ- ACK and report HARQ-ACK by PUCCH.
  • a data packet is transmitted from a source (e.g., a base station) to a destination (e.g., a user equipment or UE), the destination sends back an acknowledgement signal (HARQ-ACK) to the source. This signal indicates whether the data packet was received correctly or not.
  • a source e.g., a base station
  • a destination e.g., a user equipment or UE
  • HARQ-ACK acknowledgement signal
  • the Hybrid Automatic Repeat Request is a mechanism for error correction that ensures reliable data transmission.
  • An ACK is sent back from the receiver to the sender to confirm successful receipt of data.
  • the “codebook” refers to the predefined set of codes or patterns used for this acknowledgment process.
  • the “type-2 HARQ-ACK codebook” refers to a specific format or structure of these acknowledgment codes that is used under certain conditions or in certain scenarios. This type of codebook typically includes different sub-codebooks for different situations - for example, there might be one sub-codebook used for single cell scheduling and another used for multi-cell scheduling.
  • a DCI for multi-cell scheduling the DL transmissions or UL transmissions on the multiple cells can be scheduled by a single DCI.
  • a transport block (TB) that is scheduled by a DCI for multi-cell scheduling can be only mapped to time/frequency resources on one of the multiple cells.
  • the PDSCHs/PUSCHs on the different cells are considered as different PDSCHs/PUSCHs that carry different TBs. For each PDSCH, either one or two TB can be scheduled. For each PUSCH, one TB can be scheduled.
  • an advanced multi-cell scheduling and power control system may facilitate UL power control for PUCCH carrying HARQ-ACK for PDSCHs scheduled by a DCI for multi-cell scheduling.
  • a UE transmits a PUCCH on active UL BWP b of carrier f in the primary cell c using PUCCH power control adjustment state with index I , the UE determines the PUCCH transmission power in PUCCH transmission occasion i as: where, depends on the number of UCI bits. If Reed-muller (RM) coding is applied, the number of UCI bits for depends on number of valid HARQ-ACK bits, where the number of valid HARQ-ACK bits can be derived by the received PDCCH and PDSCH.
  • RM Reed-muller
  • a UE is configured with type-2 HARQ-ACK codebook, and for a PUCCH transmission using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 and for a number of UCI bits smaller than or equal to 11, according to the following embodiment.
  • IV RE (i) is a number of resource elements for UCI transmission.
  • the UE determines where is the number of HARQ-ACK bits determined for PDSCHs with single-cell scheduling, and is the number of HARQ-ACK bits determined for PDSCHs with multi-cell scheduling.
  • Singlecell scheduling includes a PDSCH scheduled by a single-cell scheduling DCI format and/or a PDSCH scheduled by a multi-cell scheduling DCI format scheduling only one cell.
  • HARQ-ACK sub-codebook for single cell PDSCH includes the sub-codebook for TB-based HARQ-ACK feedback
  • HARQ-ACK sub-codebook for single cell PDSCH includes a sub-codebook for CBG-based HARQ-ACK feedback and a subcodebook for TB-based HARQ-ACK feedback
  • HARQ-ACK sub-codebook for single cell PDSCH includes at least a sub-codebook for TB-based HARQ-ACK feedback for single - PDSCH scheduling and a sub-codebook for HARQ-ACK feedback for single cell multi- PDSCH scheduling, where
  • 1S the value of the T-DA1 in the last DC1 format in the last PDCCH monitoring occasion (MO) scheduling PDSCH receptions on more than one serving cells. if the UE does not detect any DCI scheduling PDSCH receptions on more than one serving cells in any of the M PDCCH MOs. is the total number of DCI formats scheduling PDSCH receptions on more than one serving cells, that the UE detects within the M PDCCH MOs. if the UE does not detect any DCI format scheduling PDSCH receptions on more than one serving cells in any of the M PDCCH MOs.
  • the serving cell r for a multi-cell scheduling DCI format scheduling PDSCH receptions on more than one serving cells is the serving cell for reference PDSCH of the scheduled PDSCH receptions.
  • the reference PDSCH can be the PDSCH with smallest or largest serving cell index of co-scheduled PDSCH receptions by a DCI, or the PDSCH configured as reference PDSCH, or the PDSCH with smallest/largest SCS of co-scheduled PDSCH receptions by a DCI, or the PDSCH with last ending symbol of co-scheduled PDSCH receptions by a DCI.
  • the reference PDSCH can be same as reference PDSCH for DAI ordering and/or PUCCH slot determination for type-2 HARQ-ACK codebook.
  • (6) is the number of DCI formats detected on s-th scheduling cell within M PDCCH MOs scheduling PDSCH receptions on more than one serving cells and u s ’ S is the number of scheduling serving cells configured for multi-cell scheduling DCI.
  • a UE is configured with 5 DL cells, cell 1 ⁇ cell 5, and each cell is configured with single TB transmission.
  • gNB configures one multi-cell DCI1 on serving cell 1 to schedule one or multiple cells from cell 1, cell 2 and cell 3, and gNB configures another multi-cell DCI2 on serving cell 4 to schedule one or multiple cells from cell 4 and cell 5.
  • a PDCCH MO m if a UE receives DCI1 scheduling cell 1 & cell2 & cell 3, and receives DCI2 scheduling cell where the number of bits for the counter DAI field in multi-cell scheduling DCI. is lhe total maximum number of configured TBs of the multiple PDSCHs scheduled by a multi-cell scheduling DCI.
  • ⁇ the maximum number of PDSCHs scheduled by a DCI for multi-cell scheduling (e.g., the maximum number of PDSCHs for each row in the cell index table for multi-cell scheduling) or the total number of serving cells configured for multi-cell scheduling (e g., the union of all rows in the cell index table for multi-cell scheduling)
  • N ⁇ ax is the maximum configured number of TBs for a PDSCH scheduled by a DCI for multi-cell scheduling.
  • N is the maximum configured number of TBs for i-th PDSCH of j-th set of PDSCHs.
  • a set of PDSCHs can be derived by a row in the cell index table scheduling PDSCH receptions on more than one serving cells. is the number of TBs in PDSCHs that the UE receives by multi-cell scheduling DCI(s) in PDCCH MO m and the UE reports corresponding HARQ-ACK information in the PUCCH.
  • Equation (9) can be expressed by the sum of received TBs in PDSCHs scheduled by multi-cell scheduling DCIs detected on s-th scheduling cell, e.g., as shown in equation (9), where is the number of scheduling serving cells configured for multicell scheduling DCI, and is the number of TBs in PDSCHs that the UE receives by a multi-cell scheduling DCI on 5-th serving cell in PDCCH MO m and the UE reports corresponding HARQ-ACK information in the PUCCH.
  • a UE is configured with 5 DL cells, cell 1 ⁇ cell 5, and each cell is configured with single TB transmission.
  • gNB configures one multi-cell DCI1 to schedule one or multiple cells from cell 1, cell 2 and cell 3, and gNB configures another multi-cell DCI2 to schedule one or multiple cells from cell 4 and cell 5.
  • a PDCCH MO m if a UE receives DCI1 scheduling cell 1 & cell2 & cell 3, and receives DCI2 scheduling cell 4&5, and UE is expected to report corresponding HARQ-ACK for all these 5 cells in one PUCCH. According t .o equa where is the number of received TBs on serving ' cell c.
  • type-2 HARQ-ACK codebook consists of two sub-codebooks, one is for single-cell scheduling with TB-based transmission and another is for multi-cell scheduling with TB-based transmission, , where is determined by equation (1) and is determined by equation (4).
  • a UE can be configured with multi-cell scheduling and also configured with multi-PDSCH scheduling in at least one serving cells in one PUCCH group.
  • Multi-PDSCH scheduling indicates one DCI schedules multiple PDSCHs in the same serving cell.
  • a DCI format is for either multi-cell scheduling or multi-PDSCH scheduling.
  • HARQ-ACK for PDSCHs by multi-cell scheduling and HARQ-ACK for PDSCHs by multi-PDSCH scheduling is in the same HARQ-ACK the UE determines determines for , where is the number of HARQ-ACK bits determined for PDSCHs with single-cell single-PDSCH scheduling as shown in equation (1), and nHARQ-ACK, group2 ' s the number of HARQ-ACK bits determined for PDSCHs with multi-cell scheduling and single-cell scheduling with multi-PDSCH scheduling.
  • Single-cell single-PDSCH scheduling includes a PDSCH scheduled by a single-cell scheduling DCI format, a PDSCH scheduled by a multi-cell scheduling DCI format scheduling only one cell, and a PDSCH bundle scheduled by a multi-PDSCH scheduling DCI format configured with single PDSCH bundle.
  • NC-DM the number of bits for the counter DAI field in multi-cell scheduling DCI or multi- PDSCH scheduling DCI.
  • A/°-DAI is the same for multi-cell scheduling DCI or multi- number PDSCH scheduling DCI.
  • is the maximum or minimum number of bits for the counter DAI field in multi-cell scheduling DCI and multi- number PDSCH scheduling DCI. is the maximum value between the maximum total number of configured TBs of the multiple PDSCHs scheduled by a multi-cell scheduling DCI anc ⁇ the maximum total number of configured TBs of the multiple PDSCHs or bundled PDSCH groups scheduled by a multi-PDSCH scheduling DCI is the number of TBs in PDSCHs that the UE receives by multi-cell scheduling DCI(s) in PDCCH MO m and the UE reports corresponding HARQ-ACK information in the PUCCH as provided above.
  • HARQ-ACK information in the PUCCH is the number of TBs in PDSCHs or bundling PDSCH groups on serving cell c that the UE receives by multi-PDSCH scheduling DCI in PDCCH MO m and the UE reports corresponding HARQ-ACK information in the PUCCH as provided above.
  • HARQ-ACK for PDSCHs by singlecell scheduling and HARQ-ACK for PDSCHs by multi-cell scheduling is in the same HARQ- ACK sub-codebook, if the UE determines for according to equation (11).
  • T-DAI the value of the T-DAI in the last DCI format in the last PDCCH MO scheduling PDSCH receptions or PDCCH receptions associated with HARQ-ACK feedback.
  • the only difference from equation (5) is, is the total number of DCI formats scheduling PDSCH receptions or PDCCH receptions associated with HARQ-ACK feedback which is associated with serving cell r. If the DCI schedules PDSCH receptions If the DCI schedules PDSCH receptions on more than one serving cells, the serving cell r is the serving cell for reference PDSCH of the scheduled PDSCH receptions. If the DCI schedules a PDSCH on single cell, the serving cell r is the serving cell to receive the PDSCH. in equation (5) is replaced which is the number of DL serving cells configured for UE within a PUCCH group, which includes the serving cell configured for multi-cell scheduling and single-cell scheduling.
  • the number of bits for the counter DAI field in multi-cell scheduling DCI or single-cell scheduling DCI. is the total maximum value between the maximum number of configured TBs of the multiple PDSCHs scheduled by a multi-cell scheduling DCI a n h the maximum number of configured TBs of single PDSCH scheduled by a single-cell scheduling DCI i s the number of TBs in PDSCHs that the UE receives by multi-cell scheduling DCI(s) in PDCCH MO m and the UE reports corresponding HARQ-ACK information in the PUCCH as provided above.
  • the number of TBs in PDSCHs is the number of TBs in PDSCHs that the UE receives by single-cell scheduling DCI(s) in PDCCH MO m for serving cell c and the UE reports corresponding HARQ-ACK information in the PUCCH as provided above.
  • the number of TBs per PDSCH is 1, otherwise, it can be 1 or 2 according to configured maximum codeword.
  • a UE can be configured with multi-cell scheduling and also configured with multi-PDSCH scheduling in at least one serving cells in one PUCCH group.
  • Multi-PDSCH scheduling means one DCI schedules multiple PDSCHs in the same serving cell.
  • Single-cell and multi-cell scheduling without multi-PDSCH scheduling includes PDSCH scheduled by single-cell or multi-cell scheduling DCI format without multi-PDSCH, and a PDSCH bundle scheduled by a multi-PDSCH scheduling DCI format scheduling only single PDSCH bundle.
  • HARQ-ACK for PDSCHs by single-cell and multi-cell scheduling without multi- PDSCH scheduling is in the same sub-codebook and HARQ-ACK for PDSCHs by multi- PDSCH scheduling is in another HARQ-ACK sub-codebook
  • the UE determines • is the number of HARQ-ACK bits determined for PDSCHs with multi- PDSCH scheduling as shown in equation (12), and is the number of HARQ- ACK bits determined for PDSCHs with multi-cell scheduling and single-cell scheduling with multi-PDSCH scheduling, determined by equation (11).
  • equation (12) is the value of the T-DAI in the last DCI format in the last PDCCH MO scheduling more than one PDSCH receptions in one serving cell.
  • l the number of bits for the counter DAI field in multi- PDSCH scheduling DCI.
  • lola l maximum value between the maximum number of configured TBs of the multiple PDSCHs or multiple PDSCH bundles scheduled by a multi- PDSCH scheduling DCI . is number of TBs in PDSCHs or bundling PDSCH groups on serving cell c that the UE receives by multi-PDSCH scheduling DCI in PDCCH MO m and the UE reports corresponding HARQ-ACK information in the PUCCH as provided above.
  • the received TBs or TBGs in PDSCHs For the above embodiments for power control, the received TBs or TBGs in PDSCHs
  • the received TBs or TBGs in PDSCHs is the received TBs or TBGs in scheduled PDSCHs, e.g., according to SLIVs indicated in TDRA table and carrier indicator in received DCIs.
  • SLIVs Start and Length Indicator Values
  • TDRA Time Domain Resource Allocation
  • TDRA table provides crucial details about temporal allocation of resources. This table outlines when these resources are designated for utilization within the wireless communication network, contributing to efficient time domain resource management.
  • Downlink Control information (DCI) formats are transmitted from the network infrastructure to the user equipment (UE) and encompass vital control information, which may comprise resource allocation for scheduling data transmissions. DCIs also possess carrier indicators, determining on which carrier frequency the allocation is executed.
  • resource allocation for the UE is determined in accordance with the SLIVs indicated in the TDRA table, the carrier frequency as indicated in the received DCIs, and frequency domain resource allocation within the indicated carrier. In essence, these parameters collectively dictate the temporal, spatial, and frequency aspects of resource allocation within the 5G NR environment or other comparable wireless communication systems.
  • an advanced multi-cell scheduling and power control system may facilitate a timeline for multi-cell scheduling.
  • the scheduling should ensure sufficient time for processing. For example, KI should ensure the gap between PDSCH and PUCCH is not smaller than PDSCH processing time and K2 should ensure the gap between PDCCH and PUSCH is not smaller than PUSCH processing time In one option, for more than one PDSCHs/PUSCHs scheduled by a multi-cell scheduling DCI, the processing time is separately determined for each scheduled cell, and sufficient time no smaller than processing time should be ensured for each PDSCH/PUSCH.
  • the PIPDSCH corresponds to the subcarrier spacing of the scheduled PDSCH
  • ptup corresponds to the subcarrier spacing of the uplink channel with which the HARQ-ACK is to be transmitted.
  • the gap between each co-scheduled PDSCH and PUCCH should be not smaller than the respective .
  • N2 is based on which corresponds to the one of (pop, ptuT) resulting with the largest where the corresponds to the subcarrier spacing of the PDCCH scheduling the PUSCH, and pup corresponds to the subcarrier spacing of the PUSCH.
  • the gap between PDCCH and each co-scheduled PUSCH should be not smaller than the respective T
  • the processing time is commonly determined for all scheduled cells, and sufficient time no smaller than processing time should be ensured for each PDSCH/PUSCH. For example, t is calculated which is common to all PDSCHs, where Ni is based on pi which corresponds to the one of piPDSCH, pup) resulting with the largest where the ppoccn corresponds to the subcarrier spacing of the PDCCH scheduling the PDSCH, the PPDSCH corresponds to the set of subcarrier spacings of the co-scheduled PDSCHs, and corresponds to the subcarrier spacing of the uplink channel with which the HARQ-ACK is to be transmitted.
  • the gap between each coscheduled PDSCH and PUCCH should be not smaller than largest .
  • the temporary may need to be calculated assuming PPDCCH, PPDSCH, c and meme. The largest is the maximum number of all temporary
  • N 2 is based on pi which corresponds to the one of resulting with the largest where the UDL corresponds to the subcarrier spacing of the PDCCH scheduling the PUSCH, and LIUL corresponds to the subcarrier spacings of the co-scheduled PUSCH.
  • the gap between PDCCH and each co-scheduled PUSCH should be not smaller than the respective T prO c,2.
  • KI should ensure the gap between valid PDSCH and PUCCH is not smaller than PDSCH processing time T prO c,i., and K2 should ensure the gap between PDCCH and valid PUSCH is not smaller than PUSCH processing time T prO c,2.
  • K2 should ensure the gap between the scheduled PDSCH and PUCCH is not smaller than PDSCH processing time Tproc.i., and K2 should ensure the gap between PDCCH and the scheduled PUSCH is not smaller than PUSCH processing time T pr oc,2.
  • UE does not expect any of the scheduled PDSCHs (or PUSCHs), the scheduling DCIs and the corresponding PUCCHs to lead to out-of-order scheduling. It may include at least one of the scheduling orders for PDCCH to PDSCH, PDSCH to PUCCH with HARQ-ACK, PDCCH to PUSCH, and CG PUSCH/SPS PDSCH overridden by DG PUSCH/DG PDSCH.
  • UE does not expect any of the scheduled PDSCHs (or PUSCHs) and the scheduling DCIs to lead to out-of-order scheduling, if at least one DCI is multi-cell scheduling DCI and one DCI is single-cell scheduling DCI, or all DCIs are multi-cell scheduling DCI, where the scheduled PDSCHs or PUSCHs is the PDSCHs or PUSCHs based on the configured SLIV.
  • UE does not expect any of the scheduled PDSCHs (or PUSCHs) and the scheduling DCIs to lead to out-of-order scheduling, if at least one DCI is multi-cell scheduling DCI and one DCI is single-cell scheduling DCI, or all DCIs are multi-cell scheduling DCI, where the scheduled PDSCHs or PUSCHs is the PDSCHs or PUSCHs based on the valid SLIV.
  • a valid SLIV for PDSCH is the configured SLIV which does not collide with UL symbol configured by tdd-UL-DL-ConflgurationCommon or tdd-UL-DL- ConflgurationDedicated
  • a valid SLIV for PUSCH is the configured SLIV which does not collide with DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- ConfigurationDedicated and does not collide with SSB symbols indicated by ssb- PositionsInBurst in SIB1 or in ServingCellConfigCommon and/or by NonCellDefiningSSB.
  • UE does not expect any of the scheduled PDSCHs and the corresponding PUCCHs to lead to out-of-order scheduling, if at least one PDSCH is scheduled by multi-cell scheduling DCI and at least one PDSCH is scheduled by single-cell scheduling DCI, or all PDSCHs are scheduled by multi-cell scheduling DCIs, where the scheduled PDSCHs is the PDSCHs based on the configured SLIV.
  • UE does not expect any of the scheduled PDSCHs and the corresponding PUCCHs to lead to out-of-order scheduling, if at least one PDSCH is scheduled by multi-cell scheduling DCI and at least one PDSCH is scheduled by single-cell scheduling DO, or all PDSCHs are scheduled by multi-cell scheduling DCIs, where the scheduled PDSCHs are the PDSCHs based on the valid SLIV.
  • the out-of-order is defined per serving cell of PDSCH reception.
  • the case shown in FIG. I and FIG. 3 is valid case (not out of order), because for each serving cell of PDSCH reception (serving cell 3), the PDSCH starts earlier is scheduled by the PDCCH starts earlier.
  • the case shown in FIG. 2 and FIG. 4 is out-of-order, because PDSCH 5 comes earlier than PDSCH 1 on serving cell #3 while the PDCCH for PDSCH 5 comes later than PDCCH for PDSCH 1 in FIG. 2, and PDSCH 3 comes earlier than PDSCH 1 on serving cell #3 while the PDCCH for PDSCH 3 comes later than PDCCH for PDSCH 1 in FIG. 4.
  • the out-of-order is defined across all serving cells of co-scheduled PDSCH reception.
  • the case shown in FIG. 1 is invalid case (e.g., it is out-of-order), because PDSCHs scheduled by DCI2 which comes later than DCI1 should not start earlier than any of the PDSCHs scheduled by DCI1, i.e., if PDSCH 3 or PDSCH4 or PDSCH5 starts earlier than PDSCH1 or PDSCH2, it is out-of-order.
  • the case shown in FIGs. 2, 3 and 4 are also invalid cases.
  • the UE may receive the configuration of a search space set of a DCI format for multicell scheduling.
  • the UE may detect a DCI format for multi-cell scheduling and receives one or multiple PDSCH(s) or transmits one or multiple PUSCH(s) accordingly following the Downlink (DL) assignment or Uplink (UL) grant in the detected DCI format.
  • a search space set refers to a group of such search spaces in which the UE should look for DCI. This set could be defined by the network based on various factors such as the capabilities of the UE, the current network conditions, the specific communication needs, etc. In other words, the search space set dictates where within a given transmission frame a UE should be searching for DCI, which in turn, instructs the UE on how to operate for subsequent transmissions or receptions.
  • the UE may transmit HARQ-ACK for received PDSCHs with type-2 HARQ-ACK codebook, and if the total number of UCI bits is no larger than 11 bits, the number of HARQ- ACK bits to determine PUCCH power control depends on the sub-codebooks for HARQ-ACK feedback, number of received DCI formats and the number of identified mis-detected DCI formats.
  • a sub-codebook refers to a subset of the main HARQ-ACK codebook (in this case, the type-2 HARQ-ACK codebook) that is designed for a specific use case or scenario. Each sub-codebook contains sets of HARQ-ACK information bits that are utilized under certain conditions.
  • the type-2 HARQ-ACK codebook mentioned here comprises of at least two subcodebooks: one for single cell scheduling and another for multi-cell scheduling for PDSCH. This means the device uses different subsets of the main codebook, depending on whether it's based on a single cell or multi-cell scheduling.
  • a DCI format carries scheduling information in wireless communication systems like LTE or 5G NR. For instance, it may instruct a UE device on how to transmit or receive data, specifying parameters like frequency, time, power level, etc.
  • a mis-detection of DCI formats implies that the UE either failed to detect a DCI format that was transmitted (a missed detection) or erroneously detects a DCI format that was not transmitted (a false alarm). Both scenarios can lead to communication errors or inefficiencies, such as unnecessary power usage, decreased data rates, or increased latency.
  • type-2 HARQ-ACK codebook consists of one sub-codebook for single cell single PDSCH scheduling and another sub-codebook for multi-cell scheduling
  • the number of HARQ-ACK bits to determine PUCCH power control n HARQ.ACK depends on n HARQ-ACK, groupi f° r single cell scheduling sub-codebook and ⁇ HARQ-ACK, groupz f° r multi-cell scheduling sub-codebook.
  • the n HAR Q. ACK group2 may be determined by the number of received DCI formats for multi-cell scheduling, the number of received TBs for multi-cell scheduling, the number of identified missed DCI formats for multi-cell scheduling, the maximum number of HARQ-ACK bits per DAI value for multi-cell scheduling.
  • type-2 HARQ-ACK codebook consists of one subcodebook for single cell single PDSCH scheduling and another sub-codebook for multi-cell scheduling and single cell multi-PDSCH scheduling
  • the number of HARQ-ACK bits to determine PUCCH power control n HAR Q. ACK depends on H HAR Q.
  • ACK groupl for single cell single PDSCH scheduling sub-codebook and n HAR Q.
  • ACK group2 for multi-cell scheduling and single cell multi-PDSCH scheduling sub-codebook.
  • ihiARQ-ACK,group2 may be determined by the number of received DCI formats for multi-cell or single cell multi-PDSCH scheduling, the number of received TBs for multi-cell or single cell multi-PDSCH scheduling, the number of identified missed DCI formats for multi-cell or single cell multi-PDSCH scheduling, the maximum value between the maximum number of HARQ-ACK bits per DAI value for multi-cell scheduling and the maximum number of HARQ-ACK bits per DAI value for single cell multi-PDSCH scheduling.
  • the UE transmits HARQ-ACK for received PDSCHs on a PUCCH, wherein the gap between end of each received PDSCH and start of the PUCCH is no smaller than PDSCH processing time
  • the UE transmits the PUSCHs, wherein the gap between end of the PDCCH and start of the each PUSCH is no smaller than PUSCH processing time
  • the PDSCH processing time is separately determined for each received PDSCH according to resulting with the largest the PUSCH processing time is separately determined for each PUSCH according to ) resulting with the largest
  • the /JIPDC.C.H corresponds to the subcarrier spacing of the PDCCH scheduling the PDSCH
  • the [IPDSCH corresponds the subcarrier spacing of a scheduled PDSCH
  • the ppuscu corresponds the subcarrier spacing of a scheduled PUSCH
  • /mi corresponds to the subcarrier spacing of the PUCCH.
  • the PDSCH processing time is jointly determined for all received PDSCHs according to resulting with the largest the PUSCH processing time is jointly determined for all PUSCHs according to resulting with the largest where the [IPDCCH corresponds to the subcarrier spacing of the PDCCH scheduling the PDSCH, the [2PDSCH corresponds a set of subcarrier spacings of all co-scheduled PDSCHs, the corresponds a set of subcarrier spacings of all co scheduled PUSCHs, and / corresponds to the subcarrier spacing of the PUCCH.
  • the UE if the UE receives at least two DCIs and at least one DCI is multi-cell scheduling DCI, the UE does not expect any of the scheduled PDSCHs or PUSCHs, the scheduling DCIs and the corresponding PUCCHs to lead to out-of-order scheduling, for each scheduled cell.
  • the UE if the UE receives at least two DCIs and at least one DCI is multi-cell scheduling DCI, the UE does not expect any of the scheduled PDSCHs or PUSCHs, the scheduling DCIs and the corresponding PUCCHs to lead to out-of-order scheduling, across all cells of co-scheduled PDSCHs/PUSCHs by a DCI.
  • the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of FIGs. 6-8, or some other figure herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in FIG. 5.
  • the process may include, at 502, decoding configuration of a search space set related to downlink control information (DCI) formats for multi-cell scheduling.
  • DCI downlink control information
  • the process further includes, at 504, detect a DCI format for multi-cell scheduling .
  • the process further includes, at 506, decoding or encoding one or more Physical Downlink Shared Channels (PDSCHs) or Physical Uplink Shared Channels (PUSCHs) based on the indications in the detected DCI format.
  • PDSCHs Physical Downlink Shared Channels
  • PUSCHs Physical Uplink Shared Channels
  • the process further includes, at 508, transmitting Hybrid Automatic Repeat Request Acknowledgements (HARQ-ACK) for received PDSCHs with a type-2 HARQ-ACK codebook, with power control based on a total number of HARQ-ACK information bits not to exceed a preset limit.
  • HARQ-ACK Hybrid Automatic Repeat Request Acknowledgements
  • the process further includes, a 510, generating power control parameters based on values from the type-2 HARQ-ACK codebook.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • FIGs. 6-8 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • Figure 6 illustrates an example network architecture 600 according to various embodiments.
  • the network 600 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 600 includes a UE 602, which is any mobile or non-mobile computing device designed to communicate with a RAN 604 via an over-the-air connection.
  • the UE 602 is communicatively coupled with the RAN 604 by a Uu interface, which may be applicable to both LTE and NR systems.
  • Examples of the UE 602 include, but are not limited to, a smartphone, tablet computer, wearable computer, desktop computer, laptop computer, in- vehicle infotainment system, in-car entertainment system, instrument cluster, head-up display (HUD) device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electron! c/engine control unit, electron!
  • the network 600 may include a plurality of UEs 602 coupled directly with one another via a D2D, ProSe, PC5, and/or sidelink (SL) interface. These UEs 602 may be M2M/D2D/MTC/IoT devices and/or vehicular systems that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 602 may perform blind decoding attempts of SL channels/links according to the various embodiments herein.
  • the UE 602 may additionally communicate with an AP 606 via an over-the-air (OTA) connection.
  • the AP 606 manages a WLAN connection, which may serve to offload some/all network traffic from the RAN 604.
  • the connection between the UE 602 and the AP 606 may be consistent with any IEEE 802. 11 protocol.
  • the UE 602, RAN 604, and AP 606 may utilize cellular- WLAN aggregation/integration (e.g., LWA/LWIP).
  • Cellular- WLAN aggregation may involve the UE 602 being configured by the RAN 604 to utilize both cellular radio resources and WLAN resources.
  • the RAN 604 includes one or more access network nodes (ANs) 608.
  • the ANs 608 terminate air-interface(s) for the UE 602 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and PHY/L1 protocols. In this manner, the AN 608 enables data/voice connectivity between CN 620 and the UE 602.
  • the ANs 608 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells; or some combination thereof.
  • an AN 608 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, etc.
  • One example implementation is a “CU/DU split” architecture where the ANs 608 are embodied as a gNB-Central Unit (CU) that is communicatively coupled with one or more gNB- Distributed Units (DUs), where each DU may be communicatively coupled with one or more Radio Units (RUs) (also referred to as RRHs, RRUs, or the like) (see e g., 3GPP TS 38.401 v 16.1.0 (2020-03)).
  • RUs Radio Units
  • the one or more RUs may be individual RSUs.
  • the CU/DU split may include an ng-eNB-CU and one or more ng- eNB-DUs instead of, or in addition to, the gNB-CU and gNB-DUs, respectively.
  • the ANs 608 employed as the CU may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network including a virtual Base Band Unit (BBU) or BBU pool, cloud RAN (CRAN), Radio Equipment Controller (REC), Radio Cloud Center (RCC), centralized RAN (C-RAN), virtualized RAN (vRAN), and/or the like (although these terms may refer to different implementation concepts). Any other ty pe of architectures, arrangements, and/or configurations can be used.
  • BBU Virtual Base Band Unit
  • CRAN cloud RAN
  • REC Radio Equipment Controller
  • RRCC Radio Cloud Center
  • C-RAN centralized RAN
  • vRAN virtualized RAN
  • the plurality of ANs may be coupled with one another via an X2 interface (if the RAN 604 is an LTE RAN or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 610) or an Xn interface (if the RAN 604 is a NG-RAN 614).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 604 may each manage one or more cells, cell groups, component earners, etc. to provide the UE 602 with an air interface for network access.
  • the UE 602 may be simultaneously connected with a plurality of cells provided by the same or different ANs 608 of the RAN 604.
  • the UE 602 and RAN 604 may use carrier aggregation to allow the UE 602 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN 608 may be a master node that provides an MCG and a second AN 608 may be secondary node that provides an SCG.
  • the first/second ANs 608 may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 604 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 602 or AN 608 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communications.
  • RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 604 may be an E-UTRAN 610 with one or more eNBs 612.
  • the an E-UTRAN 610 provides an LTE air interface (Uu) with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on C SIRS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 604 may be an next generation (NG)-RAN 614 with one or more gNB 616 and/or on or more ng-eNB 618.
  • the gNB 616 connects with 5G-enabled UEs 602 using a 5G NR interface.
  • the gNB 616 connects with a 5GC 640 through an NG interface, which includes an N2 interface or an N3 interface.
  • the ng-eNB 618 also connects with the 5GC 640 through an NG interface, but may connect with a UE 602 via the Uu interface.
  • the gNB 616 and the ng-eNB 618 may connect with each other over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 614 and a UPF 648 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 614 and an AMF 644 (e.g., N2 interface).
  • NG-U NG user plane
  • N3 interface e.g., N3 interface
  • N-C NG control plane
  • the NG-RAN 614 may provide a 5G-NR air interface (which may also be referred to as a Uu interface) with the following characteristics: variable SCS; CP-OFDM for DL, CP- OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 602 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 602, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 602 with different amount of frequency resources (e g., PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 602 and in some cases at the gNB 616.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 604 is communicatively coupled to CN 620 that includes network elements and/or network functions (NFs) to provide various functions to support data and telecommunications services to customers/subscribers (e.g., UE 602).
  • the components of the CN 620 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 620 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 620 may be referred to as a network slice, and a logical instantiation of a portion of the CN 620 may be referred to as a network sub-slice.
  • the CN 620 may be an LTE CN 622 (also referred to as an Evolved Packet Core (EPC) 622).
  • the EPC 622 may include MME 624, SGW 626, SGSN 628, HSS 630, PGW 632, and PCRF 634 coupled with one another over interfaces (or “reference points”) as shown.
  • the NFs in the EPC 622 are briefly introduced as follows.
  • the MME 624 implements mobility management functions to track a current location of the UE 602 to facilitate paging, bearer activation/ deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 626 terminates an SI interface toward the RAN 610 and routes data packets between the RAN 610 and the EPC 622.
  • the SGW 626 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 628 tracks a location of the UE 602 and performs security functions and access control.
  • the SGSN 628 also performs inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 624; MME 624 selection for handovers; etc.
  • the S3 reference point between the MME 624 and the SGSN 628 enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
  • the HSS 630 includes a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 630 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 630 and the MME 624 may enable transfer of subscription and authentication data for authenticating/ authorizing user access to the EPC 620.
  • the PGW 632 may terminate an SGi interface toward a data network (DN) 636 that may include an application (app)Zcontent server 638.
  • the PGW 632 routes data packets between the EPC 622 and the data network 636.
  • the PGW 632 is communicatively coupled with the SGW 626 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 632 may further include a node for policy enforcement and charging data collection (e.g., PCEF).
  • the SGi reference point may communicatively couple the PGW 632 with the same or different data network 636.
  • the PGW 632 may be communicatively coupled with a PCRF 634 via a Gx reference point.
  • the PCRF 634 is the policy and charging control element of the EPC 622.
  • the PCRF 634 is communicatively coupled to the app/content server 638 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 632 also provisions associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 620 may be a 5GC 640 including an AUSF 642, AMF 644, SMF 646, UPF 648, NSSF 650, NEF 652, NRF 654, PCF 656, UDM 658, and AF 660 coupled with one another over various interfaces as shown.
  • the NFs in the 5GC 640 are briefly introduced as follows.
  • the AUSF 642 stores data for authentication of UE 602 and handle authentication- related functionality.
  • the AUSF 642 may facilitate a common authentication framework for various access types..
  • the AMF 644 allows other functions of the 5GC 640 to communicate with the UE 602 and the RAN 604 and to subscribe to notifications about mobility events with respect to the UE 602.
  • the AMF 644 is also responsible for registration management (e.g., for registering UE 602), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 644 provides transport for SM messages between the UE 602 and the SMF 646, and acts as a transparent proxy for routing SM messages.
  • AMF 644 also provides transport for SMS messages between UE 602 and an SMSF.
  • AMF 644 interacts with the AUSF 642 and the UE 602 to perform various security anchor and context management functions.
  • AMF 644 is a termination point of a RAN-CP interface, which includes the N2 reference point between the RAN 604 and the AMF 644.
  • the AMF 644 is also a termination point of NAS (Nl) signaling, and performs NAS ciphering and integrity protection.
  • AMF 644 also supports NAS signaling with the UE 602 over an N3IWF interface.
  • the N3IWF provides access to untrusted entities.
  • N3IWF may be a termination point for the N2 interface between the (R)AN 604 and the AMF 644 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 614 and the 648 for the user plane.
  • the AMF 644 handles N2 signalling from the SMF 646 and the AMF 644 for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, marks N3 user-plane packets in the uplink, and enforces QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received overN2.
  • N3IWF may also relay UL and DL control-plane NAS signalling between the UE 602 and AMF 644 via an Nl reference point between the UE 602and the AMF 644, and relay uplink and downlink user-plane packets between the UE 602 and UPF 648.
  • the N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 602.
  • the AMF 644 may exhibit an Namf servicebased interface, and may be a termination point for anN14 reference point between two AMFs 644 and an N17 reference point between the AMF 644 and a 5G-EIR (not shown by Figure 6).
  • the SMF 646 is responsible for SM (e g., session establishment, tunnel management between UPF 648 and AN 608); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 648 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 644 over N2 to AN 608; and determining SSC mode of a session.
  • SM refers to management of a PDU session
  • a PDU session or “session” refers to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 602 and the DN 636.
  • the UPF 648 acts as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 636, and a branching point to support multihomed PDU session.
  • the UPF 648 also performs packet routing and forwarding, packet inspection, enforces user plane part of policy rules, lawfully intercept packets (UP collection), performs traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), performs uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and performs downlink packet buffering and downlink data notification triggering.
  • UPF 648 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 650 selects a set of network slice instances serving the UE 602.
  • the NSSF 650 also determines allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 650 also determines an AMF set to be used to serve the UE 602, or a list of candidate AMFs 644 based on a suitable configuration and possibly by querying the NRF 654.
  • the selection of a set of network slice instances for the UE 602 may be triggered by the AMF 644 with which the UE 602 is registered by interacting with the NSSF 650; this may lead to a change of AMF 644.
  • the NSSF 650 interacts with the AMF 644 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown).
  • the NEF 652 securely exposes services and capabilities provided by 3GPP NFs for third party, internal exposure/re-exposure, AFs 660, edge computing or fog computing systems (e.g., edge compute node, etc.
  • the NEF 652 may authenticate, authorize, or throttle the AFs.
  • NEF 652 may also translate information exchanged with the AF 660 and information exchanged with internal network functions. For example, the NEF 652 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 652 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 652 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 652 to other NFs and AFs, or used for other purposes such as analytics.
  • the NRF 654 supports service discovery functions, receives NF discovery requests from NF instances, and provides information of the discovered NF instances to the requesting NF instances. NRF 654 also maintains information of available NF instances and their supported services. The NRF 654 also supports service discovery functions, wherein the NRF 654 receives NF Discovery Request from NF instance or an SCP (not shown), and provides information of the discovered NF instances to the NF instance or SCP.
  • the PCF 656 provides policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 656 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 658.
  • the PCF 656 exhibit an Npcf service-based interface.
  • the UDM 658 handles subscription-related information to support the network entities’ handling of communication sessions, and stores subscription data of UE 602. For example, subscription data may be communicated via an N8 reference point between the UDM 658 and the AMF 644.
  • the UDM 658 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 658 and the PCF 656, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 602) for the NEF 652.
  • the Nudr servicebased interface may be exhibited by the UDR 221 to allow the UDM 658, PCF 656, and NEF 652 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 658 may exhibit the Nudm service-based interface.
  • AF 660 provides application influence on traffic routing, provide access to NEF 652, and interact with the policy framework for policy control.
  • the AF 660 may influence UPF 648 (re)selection and traffic routing. Based on operator deploy ment, when AF 660 is considered to be a trusted entity, the network operator may permit AF 660 to interact directly with relevant NFs. Additionally, the AF 660 may be used for edge computing implementations,
  • the 5GC 640 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 602 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 640 may select a UPF 648 close to the UE 602 and execute traffic steering from the UPF 648 to DN 636 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 660, which allows the AF 660 to influence UPF (re)selection and traffic routing.
  • the data network (DN) 636 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application (app)Zcontent server 638.
  • the DN 636 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the app server 638 can be coupled to an IMS via an S-CSCF or the I-CSCF.
  • the DN 636 may represent one or more local area DNs (LADNs), which are DNs 636 (or DN names (DNNs)) that is/are accessible by a UE 602 in one or more specific areas. Outside of these specific areas, the UE 602 is not able to access the LADN/DN 636.
  • LADNs local area DNs
  • DNNs DN names
  • the DN 636 may be an Edge DN 636, which is a (local) Data Network that supports the architecture for enabling edge applications.
  • the app server 638 may represent the physical hardware systems/devices providing app server functionality and/or the application software resident in the cloud or at an edge compute node that performs server function(s).
  • the app/content server 638 provides an edge hosting environment that provides support required for Edge Application Server's execution.
  • the 5GS can use one or more edge compute nodes to provide an interface and offload processing of wireless communication traffic.
  • the edge compute nodes may be included in, or co-located with one or more RAN610, 614.
  • the edge compute nodes can provide a connection between the RAN 614 and UPF 648 in the 5GC 640.
  • the edge compute nodes can use one or more NFV instances instantiated on virtualization infrastructure within the edge compute nodes to process wireless connections to and from the RAN 614 and UPF 648.
  • the interfaces of the 5GC 640 include reference points and service-based itnterfaces.
  • the reference points include: N 1 (between the UE 602 and the AMF 644), N2 (between RAN 614 and AMF 644), N3 (between RAN 614 and UPF 648), N4 (between the SMF 646 and UPF 648), N5 (between PCF 656 and AF 660), N6 (between UPF 648 and DN 636), N7 (between SMF 646 and PCF 656), N8 (between UDM 658 and AMF 644), N9 (between two UPFs 648), N10 (between the UDM 658 and the SMF 646), Ni l (between the AMF 644 and the SMF 646), N12 (between AUSF 642 and AMF 644), N13 (between AUSF 642 and UDM 658), N14 (betw een two AMFs 644; not shown), N15 (between PCF 656 and AMF 644 in case of
  • the service-based representation of Figure 6 represents NFs within the control plane that enable other authorized NFs to access their services.
  • the service-based interfaces include: Namf (SBI exhibited by AMF 644), Nsmf (SBI exhibited by SMF 646), Nnef (SBI exhibited by NEF 652), Npcf (SBI exhibited by PCF 656), Nudm (SBI exhibited by the UDM 658), Naf (SBI exhibited by AF 660), Nnrf (SBI exhibited by NRF 654), Nnssf (SBI exhibited by NSSF 650), Nausf (SBI exhibited by AUSF 642).
  • NEF 652 can provide an interface to edge compute nodes 636x, which can be used to process wireless connections with the RAN 614.
  • the system 600 may include an SMSF, which is responsible for SMS subscription checking and verification, and relaying SM messages to/fromthe UE 602 to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router.
  • the SMS may also interact with AMF 644 and UDM 658 for a notification procedure that the UE 602 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 658 when UE 602 is available for SMS).
  • the 5GS may also include an SCP (or individual instances of the SCP) that supports indirect communication (see e.g., 3GPP TS 23.501 section 7.1.1); delegated discovery (see e.g., 3GPP TS 23.501 section 7.1.1); message forwarding and routing to destination NF/NF service(s), communication security (e.g., authorization of the NF Service Consumer to access the NF Service Producer API) (see e.g., 3GPP TS 33.501), load balancing, monitoring, overload control, etc.; and discovery and selection functionality for UDM(s), AUSF(s), UDR(s), PCF(s) with access to subscription data stored in the UDR based on UE's SUPI, SUCI or GPSI (see e.g., 3GPP TS 23.501 section 6.3).
  • SCP or individual instances of the SCP
  • indirect communication see e.g., 3GPP TS 23.501 section 7.1.1
  • delegated discovery see e.g.,
  • Load balancing, monitoring, overload control functionality provided by the SCP may be implementation specific.
  • the SCP may be deployed in a distributed manner. More than one SCP can be present in the communication path between various NF Services.
  • the SCP although not an NF instance, can also be deployed distributed, redundant, and scalable.
  • FIG. 7 schematically illustrates a wireless network 700 in accordance with various embodiments.
  • the wireless network 700 may include a UE 702 in wireless communication with an AN 704.
  • the UE 702 and AN 704 may be similar to, and substantially interchangeable with, like-named components described with respect to Figure 6.
  • the UE 702 may be communicatively coupled with the AN 704 via connection 706.
  • the connection 706 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
  • the UE 702 may include ahost platform 708 coupled with a modem platform 710.
  • the host platform 708 may include application processing circuitry 712, which may be coupled with protocol processing circuitry 714 of the modem platform 710.
  • the application processing circuitry 712 may run various applications for the UE 702 that source/sink application data.
  • the application processing circuitry 712 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 714 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 706.
  • the layer operations implemented by the protocol processing circuitry 714 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 710 may further include digital baseband circuitry 716 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 714 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ acknowledgement (ACK) functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decodmg, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ acknowledgement (ACK) functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna
  • the modem platform 710 may further include transmit circuitry 718, receive circuitry 720, RF circuitry 722, and RF front end (RFFE) 724, which may include or connect to one or more antenna panels 726.
  • the transmit circuitry 718 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 720 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 722 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 724 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 714 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE 702 reception may be established by and via the antenna panels 726, RFFE 724, RF circuitry 722, receive circuitry 720, digital baseband circuitry 716, and protocol processing circuitry 714.
  • the antenna panels 726 may receive a transmission from the AN 704 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 726
  • a UE 702 transmission may be established by and via the protocol processing circuitry 714, digital baseband circuitry 716, transmit circuitry 718, RF circuitry 722, RFFE 724, and antenna panels 726.
  • the transmit components of the UE 704 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 726.
  • the AN 704 may include a host platform 728 coupled with a modem platform 730.
  • the host platform 728 may include application processing circuitry 732 coupled with protocol processing circuitry 734 of the modem platform 730.
  • the modem platform may further include digital baseband circuitry 736, transmit circuitry 738, receive circuitry 740, RF circuitry 742, RFFE circuitry 744, and antenna panels 746.
  • the components of the AN 704 may be similar to and substantially interchangeable with like-named components of the UE 702.
  • the components of the AN 708 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • Figure 8 illustrates components of a computing device 800 according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 8 shows a diagrammatic representation of hardware resources 801 including one or more processors (or processor cores) 810, one or more memory /storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840 or other interface circuitry.
  • a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 801.
  • the processors 810 include, for example, processor 812 and processor 814.
  • the processors 810 include circuitry such as, but not limited to one or more processor cores and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface circuit, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as secure digital/multi-media card (SD/MMC) or similar, interfaces, mobile industry processor interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports.
  • LDOs low drop-out voltage regulators
  • interrupt controllers serial interfaces such as SPI, I2C or universal programmable serial interface circuit
  • RTC real time clock
  • timer-counters including interval and watchdog timers
  • general purpose I/O general purpose I/O
  • memory card controllers such as secure digital/multi-media card (SD/MMC) or similar, interfaces, mobile industry processor interface (MIPI) interfaces and Joint Test Access Group
  • the processors 810 may be, for example, a central processing unit (CPU), reduced instruction set computing (RISC) processors, Acom RISC Machine (ARM) processors, complex instruction set computing (CISC) processors, graphics processing units (GPUs), one or more Digital Signal Processors (DSPs) such as a baseband processor, Application-Specific Integrated Circuits (ASICs), an Field-Programmable Gate Array (FPGA), a radio-frequency integrated circuit (RFIC), one or more microprocessors or controllers, another processor (including those discussed herein), or any suitable combination thereof.
  • the processor circuitry 810 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices (e.g., FPGA, complex programmable logic devices (CPLDs), etc.), or the like.
  • the memory /storage devices 820 may include main memory, disk storage, or any suitable combination thereof.
  • the memory /storage devices 820 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as random access memory (RAM), dynamic RAM (DRAM), static RAM (SRAM), synchronous DRAM (SDRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, phase change RAM (PRAM), resistive memory such as magnetoresistive random access memory (MRAM), etc., and may incorporate three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.
  • the memory/storage devices 820 may also comprise persistent storage devices, which may be temporal and/or persistent storage of any type, including, but not limited to, nonvolatile memory, optical, magnetic, and/or solid state mass storage, and so forth.
  • the communication resources 830 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 or other network elements via a network 808.
  • the communication resources 830 may include wired communication components (e.g., for coupling via USB, Ethernet, Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), Ethernet over USB, Controller Area Network (CAN), Local Interconnect Network (LIN), DeviceNet, ControlNet, Data Highway+, PROFIBUS, or PROFINET, among many others), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, WiFi® components, and other communication components.
  • wired communication components e.g., for coupling via USB, Ethernet, Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), Ethernet over USB, Controller Area Network (CAN), Local Interconnect Network (LIN), DeviceNet, ControlNet, Data Highway+, PROFIBUS, or PROFINET, among many others
  • Network connectivity may be provided to/from the computing device 800 via the communication resources 830 using a physical connection, which may be electrical (e.g., a “copper interconnect”’) or optical.
  • the physical connection also includes suitable input connectors (e.g., ports, receptacles, sockets, etc.) and output connectors (e.g., plugs, pins, etc ).
  • the communication resources 830 may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned network interface protocols.
  • Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein.
  • the instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor’s cache memory), the memory/storage devices 820, or any suitable combination thereof.
  • any portion of the instructions 850 may be transferred to the hardware resources 801 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory/storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • the presently described embodiments include the following, non-limiting implementations. Each of the following non-limiting examples may stand on its own or may be combined in any permutation or combination with any one or more of the other examples provided below or throughout the present disclosure.
  • at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • Example 1 may include an apparatus comprising decode configuration of a search space set related to downlink control information (DCI) formats for a multi-cell scheduling; detect a DCI format for multi-cell scheduling; decode or encode one or more Physical Downlink Shared Channels (PDSCHs) or Physical Uplink Shared Channels (PUSCHs) based on the indications in the detected DCI format; encode Hybrid Automatic Repeat Request Acknowledgements (HARQ-ACK) feedback for received PDSCHs with a type-2 HARQ-ACK codebook, with power control based on a total number of HARQ-ACK information bits not to exceed a preset limit; and generate power control parameters based on values from the type-2 HARQ-ACK codebook.
  • DCI downlink control information
  • PDSCHs Physical Downlink Shared Channels
  • PUSCHs Physical Uplink Shared Channels
  • HARQ-ACK Hybrid Automatic Repeat Request Acknowledgements
  • Example 2 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to generate the power control parameters based on values from additional sub-codebooks, if the type-2 HARQ-ACK codebook comprises sub-codebooks for single cell scheduling and multi-cell scheduling for PDSCH.
  • Example 3 may include the apparatus of example 2 and/or some other example herein, wherein the power control parameters depend on the number of received DCI formats, a number of received transport blocks, and mis-detected DCI formats for multi-cell scheduling.
  • Example 4 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to transmit the HARQ-ACK associated with received PDSCHs on a Physical Uplink Control Channel (PUCCH), with a gap no smaller than a minimum gap between an end of each received PDSCH and a start of the PUCCH.
  • PUCCH Physical Uplink Control Channel
  • Example 5 may include the apparatus of example 4 and/or some other example herein, wherein the minimum gap may be at least equal to a PDSCH processing time.
  • Example 6 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to transmit PUSCHs, with a gap no smaller than a minimum gap between an end of a Physical Downlink Control Channel (PDCCH) and a start of each PUS CH.
  • PDCH Physical Downlink Control Channel
  • Example 7 may include the apparatus of example 6 and/or some other example herein, wherein the minimum gap may be at least equal to a PUSCH processing time.
  • Example 8 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to generate the power control parameters when the total number of HARQ-ACK information bits does not exceed 11 bits.
  • Example 9 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to prevent out-of-order scheduling for each scheduled cell, where multiple DCIs are received and at least one of the received multiple DCIs may be a multi-cell scheduling DCI.
  • Example 10 may include a computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: decode configuration of a search space set related to downlink control information (DCI) formats for a multi-cell scheduling; detect a DCI format for multi-cell scheduling; decode or encode one or more Physical Downlink Shared Channels (PDSCHs) or Physical Uplink Shared Channels (PUSCHs) based on the indications in the detected DCI format; encode Hybrid Automatic Repeat Request Acknowledgements (HARQ-ACK) feedback for received PDSCHs with a type-2 HARQ-ACK codebook, with power control based on a total number of HARQ-ACK information bits not to exceed a preset limit; and generate power control parameters based on values from the type-2 HARQ-ACK codebook.
  • DCI downlink control information
  • PDSCHs Physical Downlink Shared Channels
  • PUSCHs Physical Uplink Shared Channels
  • HARQ-ACK Hybrid Automatic Repeat Request Acknowledge
  • Example 11 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise generate the power control parameters based on values from additional sub-codebooks, if the type-2 HARQ-ACK codebook comprises sub-codebooks for single cell scheduling and multi-cell scheduling for PDSCH.
  • Example 12 may include the computer-readable medium of example 11 and/or some other example herein, wherein the power control parameters depend on the number of received DCI formats, a number of received transport blocks, and mis-detected DCI formats for multicell scheduling.
  • Example 13 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise transmit the HARQ-ACK associated with received PDSCHs on a Physical Uplink Control Channel (PUCCH), with a gap no smaller than a minimum gap between an end of each received PDSCH and a start of the PUCCH.
  • PUCCH Physical Uplink Control Channel
  • Example 14 may include the computer-readable medium of example 13 and/or some other example herein, wherein the minimum gap may be at least equal to a PDSCH processing time.
  • Example 15 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise transmit PUSCHs, with a gap no smaller than a minimum gap between an end of a Physical Downlink Control Channel (PDCCH) and a start of each PUS CH.
  • PDCCH Physical Downlink Control Channel
  • Example 16 may include the computer-readable medium of example 15 and/or some other example herein, wherein the minimum gap may be at least equal to a PUSCH processing time.
  • Example 17 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise generate the power control parameters when the total number of HARQ-ACK information bits does not exceed 11 bits.
  • Example 18 may include the computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise prevent out-of-order scheduling for each scheduled cell, where multiple DCIs are received and at least one of the received multiple DCIs may be a multi-cell scheduling DCI.
  • Example 19 may include a method comprising: decode configuration of a search space set related to downlink control information (DCI) formats for a multi-cell scheduling; detect a DCI format for multi-cell scheduling; decode or encode one or more Physical Downlink Shared Channels (PDSCHs) or Physical Uplink Shared Channels (PUSCHs) based on the indications in the detected DCI format; encode Hybrid Automatic Repeat Request Acknowledgements (HARQ-ACK) feedback for received PDSCHs with a type-2 HARQ-ACK codebook, with power control based on a total number of HARQ-ACK information bits not to exceed a preset limit; and generate power control parameters based on values from the type-2 HARQ-ACK codebook.
  • DCI downlink control information
  • PDSCHs Physical Downlink Shared Channels
  • PUSCHs Physical Uplink Shared Channels
  • HARQ-ACK Hybrid Automatic Repeat Request Acknowledgements
  • Example 20 may include the method of example 19 and/or some other example herein, further comprising generate the power control parameters based on values from additional subcodebooks, if the type-2 HARQ-ACK codebook comprises sub-codebooks for single cell scheduling and multi-cell scheduling for PDSCH.
  • Example 21 may include the method of example 20 and/or some other example herein, wherein the power control parameters depend on the number of received DCI formats, a number of received transport blocks, and mis-detected DCI formats for multi-cell scheduling.
  • Example 22 may include the method of example 19 and/or some other example herein, further comprising transmit the HARQ-ACK associated with received PDSCHs on a Physical Uplink Control Channel (PUCCH), with a gap no smaller than a minimum gap between an end of each received PDSCH and a start of the PUCCH.
  • PUCCH Physical Uplink Control Channel
  • Example 23 may include the method of example 22 and/or some other example herein, wherein the minimum gap may be at least equal to a PDSCH processing time.
  • Example 24 may include the method of example 19 and/or some other example herein, further comprising transmit PUSCHs, with a gap no smaller than a minimum gap between an end of a Physical Downlink Control Channel (PDCCH) and a start of each PUSCH.
  • PDCCH Physical Downlink Control Channel
  • Example 25 may include the method of example 24 and/or some other example herein, wherein the minimum gap may be at least equal to a PUSCH processing time.
  • Example 26 may include the method of example 19 and/or some other example herein, further comprising generate the power control parameters when the total number of HARQ- ACK information bits does not exceed 11 bits.
  • Example 27 may include the method of example 19 and/or some other example herein, further comprising prevent out-of-order scheduling for each scheduled cell, where multiple DCIs are received and at least one of the received multiple DCIs may be a multi-cell scheduling DCI
  • Example 28 may include an apparatus comprising means for: decode configuration of a search space set related to downlink control information (DCI) formats for a multi-cell scheduling; detect a DCI format for multi-cell scheduling; decode or encode one or more Physical Downlink Shared Channels (PDSCHs) or Physical Uplink Shared Channels (PUSCHs) based on the indications in the detected DCI format; encode Hybrid Automatic Repeat Request Acknowledgements (HARQ-ACK) feedback for received PDSCHs with a type-2 HARQ-ACK codebook, with power control based on a total number of HARQ-ACK information bits not to exceed a preset limit; and generate power control parameters based on values from the type-2 HARQ-ACK codebook.
  • DCI downlink control information
  • PDSCHs Physical Downlink Shared Channels
  • PUSCHs Physical Uplink Shared Channels
  • HARQ-ACK Hybrid Automatic Repeat Request Acknowledgements
  • Example 29 may include the apparatus of example 28 and/or some other example herein, further comprising generate the power control parameters based on values from additional sub-codebooks, if the type-2 HARQ-ACK codebook comprises sub-codebooks for single cell scheduling and multi-cell scheduling for PDSCH.
  • Example 30 may include the apparatus of example 29 and/or some other example herein, wherein the power control parameters depend on the number of received DCI formats, a number of received transport blocks, and mis-detected DCI formats for multi-cell scheduling.
  • Example 31 may include the apparatus of example 28 and/or some other example herein, further comprising transmit the HARQ-ACK associated with received PDSCHs on a Physical Uplink Control Channel (PUCCH), with a gap no smaller than a minimum gap between an end of each received PDSCH and a start of the PUCCH.
  • PUCCH Physical Uplink Control Channel
  • Example 32 may include the apparatus of example 31 and/or some other example herein, wherein the minimum gap may be at least equal to a PDSCH processing time.
  • Example 33 may include the apparatus of example 28 and/or some other example herein, further comprising transmit PUSCHs, with a gap no smaller than a minimum gap between an end of a Physical Downlink Control Channel (PDCCH) and a start of each PUSCH.
  • PDCCH Physical Downlink Control Channel
  • Example 34 may include the apparatus of example 33 and/or some other example herein, wherein the minimum gap may be at least equal to a PUSCH processing time.
  • Example 35 may include the apparatus of example 28 and/or some other example herein, further comprising generate the power control parameters when the total number of HARQ-ACK information bits does not exceed 11 bits.
  • Example 36 may include the apparatus of example 28 and/or some other example herein, further comprising prevent out-of-order scheduling for each scheduled cell, where multiple DCIs are received and at least one of the received multiple DCIs may be a multi-cell scheduling DCI.
  • Example 37 may include an apparatus comprising means for performing any of the methods of examples 1-36.
  • Example 38 may include a network node comprising a communication interface and processing circuitry connected thereto and configured to perform the methods of examples 1- 36.
  • Example 39 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-36, or any other method or process described herein.
  • Example 40 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-36, or any other method or process described herein.
  • Example 41 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-36, or any other method or process descnbed herein.
  • Example 42 may include a method, technique, or process as described in or related to any of examples 1-36, or portions or parts thereof.
  • Example 43 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-36, or portions thereof.
  • Example 44 may include a signal as described in or related to any of examples 1-36, or portions or parts thereof.
  • Example 45 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-36, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 46 may include a signal encoded with data as described in or related to any of examples 1-36, or portions or parts thereof, or otherwise described in the present disclosure.
  • Example 47 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-36, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 48 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-36, or portions thereof.
  • Example 49 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-36, or portions thereof.
  • Example 50 may include a signal in a wireless network as shown and described herein.
  • Example 51 may include a method of communicating in a wireless network as shown and described herein
  • Example 52 may include a system for providing wireless communication as shown and described herein.
  • Example 53 may include a device for providing wireless communication as shown and described herein.
  • An example implementation is an edge computing system, including respective edge processing devices and nodes to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is a client endpoint node, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an aggregation node, network hub node, gateway node, or core data processing node, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an access point, base station, road-side unit, street-side unit, or on-premise unit, within or coupled to an edge computing system, operable to invoke or perfonn the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an edge provisioning node, service orchestration node, application orchestration node, or multi-tenant management node, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an edge node operating an edge provisioning service, application or service orchestration service, virtual machine deployment, container deployment, function deployment, and compute management, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an edge computing system operable as an edge mesh, as an edge mesh with side car loading, or with mesh-to-mesh communications, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an edge computing system including aspects of network functions, acceleration functions, acceleration hardware, storage hardware, or computation hardware resources, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein.
  • Another example implementation is an edge computing system adapted for supporting client mobility, vehicle-to-vehicle (V2V), vehicle-to-every thing (V2X), or vehicle-to-infrastructure (V2I) scenarios, and optionally operating according to ETSI MEC specifications, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein
  • Another example implementation is an edge computing system adapted for mobile wireless communications, including configurations according to an 3GPP 4G/LTE or 5G network capabilities, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein.
  • Another example implementation is a computing system adapted for network communications, including configurations according to an O-RAN capabilities, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein.
  • the phrase “A and/or B” means (A), (B), or (A and B).
  • the phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).
  • the description may use the phrases “in an embodiment,” or “In some embodiments,” which may each refer to one or more of the same or different embodiments.
  • the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure are synonymous.
  • Coupled may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other.
  • directly coupled may mean that two or more elements are in direct contact with one another.
  • communicatively coupled may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or ink, and/or the like.
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
  • Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information.
  • processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.
  • Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like.
  • the one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators.
  • CV computer vision
  • DL deep learning
  • application circuitry and/or “baseband circuitry'” may be considered synonymous to, and may be referred to as, “processor circuitry.”
  • memory and/or “memory circuitry” as used herein refers to one or more hardware devices for storing data, including RAM, MRAM, PRAM, DRAM, and/or SDRAM, core memory, ROM, magnetic disk storage mediums, optical storage mediums, flash memory devices or other machine readable mediums for storing data.
  • computer-readable medium may include, but is not limited to, memory', portable or fixed storage devices, optical storage devices, and various other mediums capable of storing, containing or carrying instructions or data.
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • interface circuitry may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
  • user equipment refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • the term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
  • the term “user equipment” or “UE” may include any type of wireless/ wired device or any computing device including a wireless communications interface.
  • network element refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services.
  • network element may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
  • computer system refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
  • appliance refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource.
  • a ’’virtual appliance is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
  • element refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary, wherein an element may be any type of entity including, for example, one or more devices, systems, controllers, network elements, modules, etc., or combinations thereof.
  • device refers to a physical entity embedded inside, or attached to, another physical entity in its vicinity, with capabilities to convey digital information from or to that physical entity.
  • entity refers to a distinct component of an architecture or device, or information transferred as a payload.
  • controller refers to an element or entity that has the capability to affect a physical entity, such as by changing its state or causing the physical entity to move.
  • cloud computing refers to a paradigm for enabling network access to a scalable and elastic pool of shareable computing resources with self-service provisioning and administration on-demand and without active management by users.
  • Cloud computing provides cloud computing services (or cloud services), which are one or more capabilities offered via cloud computing that are invoked using a defined interface (e.g., an API or the like).
  • computing resource or simply “resource” refers to any physical or virtual component, or usage of such components, of limited availability within a computer system or network.
  • Examples of computing resources include usage/access to, for a period of time, servers, processor(s), storage equipment, memory devices, memory areas, networks, electrical power, input/output (peripheral) devices, mechanical devices, network connections (e.g., channels/links, ports, network sockets, etc ), operating systems, virtual machines (VMs), software/applications, computer files, and/or the like.
  • a “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s).
  • a “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • the term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network.
  • system resources may refer to any kind of shared entities to provide services, and may include computing and/or network resources.
  • System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
  • cloud service provider or CSP indicates an organization which operates typically large-scale “cloud” resources comprised of centralized, regional, and edge data centers (e.g., as used in the context of the public cloud).
  • a CSP may also be referred to as a Cloud Service Operator (CSO).
  • CSO Cloud Service Operator
  • references to “cloud computing” generally refer to computing resources and services offered by a CSP or a CSO, at remote locations with at least some increased latency, distance, or constraints relative to edge computing.
  • the term “data center” refers to a purpose-designed structure that is intended to house multiple high-performance compute and data storage nodes such that a large amount of compute, data storage and network resources are present at a single location. This often entails specialized rack and enclosure systems, suitable heating, cooling, ventilation, security, fire suppression, and power delivery systems.
  • the term may also refer to a compute and data storage node in some contexts.
  • a data center may vary in scale between a centralized or cloud data center (e.g., largest), regional data center, and edge data center (e.g., smallest).
  • edge computing refers to the implementation, coordination, and use of computing and resources at locations closer to the “edge” or collection of “edges” of a network. Deploying computing resources at the network’s edge may reduce application and network latency, reduce network backhaul traffic and associated energy consumption, improve service capabilities, improve compliance with security or data pnvacy requirements (especially as compared to conventional cloud computing), and improve total cost of ownership).
  • edge compute node refers to a real-world, logical, or virtualized implementation of a compute-capable element in the form of a device, gateway, bridge, system or subsystem, component, whether operating in a server, client, endpoint, or peer mode, and whether located at an “edge” of an network or at a connected location further within the network.
  • references to a “node” used herein are generally interchangeable with a “device”, “component”, and “sub-system”; however, references to an “edge computing system” or “edge computing network” generally refer to a distributed architecture, organization, or collection of multiple nodes and devices, and which is organized to accomplish or offer some aspect of services or resources in an edge computing setting.
  • the term “Edge Computing” refers to a concept, as described in [6], that enables operator and 3rd party services to be hosted close to the UE's access point of attachment, to achieve an efficient service delivery through the reduced end-to- end latency and load on the transport network.
  • the term “Edge Computing Service Provider” refers to a mobile network operator or a 3rd party service provider offering Edge Computing service.
  • the term “Edge Data Network” refers to a local Data Network (DN) that supports the architecture for enabling edge applications.
  • DN local Data Network
  • the term “Edge Elosting Environment” refers to an environment providing support required for Edge Application Server's execution.
  • the term “Application Server” refers to application software resident in the cloud performing the server function.
  • loT Internet of Things
  • loT devices are usually low-power devices without heavy compute or storage capabilities.
  • “Edge loT devices” may be any kind of loT devices deployed at a network’s edge.
  • cluster refers to a set or grouping of entities as part of an edge computing system (or systems), in the form of physical entities (e.g., different computing systems, networks or network groups), logical entities (e g., applications, functions, security constructs, containers), and the like.
  • a “cluster” is also referred to as a “group” or a “domain”.
  • the membership of cluster may be modified or affected based on conditions or functions, including from dynamic or property -based membership, from network or system management scenarios, or from various example techniques discussed below which may add, modify, or remove an entity in a cluster.
  • Clusters may also include or be associated with multiple layers, levels, or properties, including variations in security features and results based on such layers, levels, or properties.
  • the term “application” may refer to a complete and deployable package, environment to achieve a certain function in an operational environment.
  • AI/ML application or the like may be an application that contains some AI/ML models and application-level descriptions.
  • machine learning or “ML” refers to the use of computer systems implementing algorithms and/or statistical models to perform specific task(s) without using explicit instructions, but instead relying on patterns and inferences.
  • ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) in order to make predictions or decisions without being explicitly programmed to perform such tasks.
  • an ML algorithm is a computer program that leams from experience with respect to some task and some performance measure
  • an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets.
  • ML algorithm refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the purposes of the present disclosure.
  • machine learning model may also refer to ML methods and concepts used by an ML-assisted solution.
  • An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation.
  • ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K-means clustering, principle component analysis (PCA), etc.), reinforcement learning (e.g., Q-leaming, multi-armed bandit learning, deep RL, etc.), neural networks, and the like.
  • supervised learning e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.
  • unsupervised learning e.g., K-means clustering, principle component analysis (PCA), etc.
  • reinforcement learning e.g., Q-leaming, multi-armed bandit
  • An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor.
  • the “actor” is an entity that hosts an ML assisted solution using the output of the ML model inference).
  • ML training host refers to an entity, such as a network function, that hosts the training of the model.
  • ML inference host refers to an entity, such as a network function, that hosts model during inference mode (which includes both the model execution as well as any online learning if applicable).
  • the ML-host informs the actor about the output of the ML algorithm, and the actor takes a decision for an action (an “action” is performed by an actor as a result of the output of an ML assisted solution).
  • model inference information refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts.
  • instantiate refers to the creation of an instance.
  • An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element, or a data element that contains content.
  • a “database object”, “data structure”, or the like may refer to any representation of information that is in the form of an object, attribute-value pair (AVP), key -value pair (KVP), tuple, etc., and may include variables, data structures, functions, methods, classes, database records, database fields, database entities, associations between data and/or database entities (also referred to as a “relation”), blocks and links between blocks in block chain implementations, and/or the like.
  • An “information object,” as used herein, refers to a collection of structured data and/or any representation of information, and may include, for example electronic documents (or “documents”), database objects, data structures, files, audio data, video data, raw data, archive files, application packages, and/or any other like representation of information.
  • electronic document or “document,” may refer to a data structure, computer fde, or resource used to record data, and includes various file ty pes and/or data formats such as word processing documents, spreadsheets, slide presentations, multimedia items, webpage and/or source code documents, and/or the like.
  • the information objects may include markup and/or source code documents such as HTML, XML, JSON, Apex®, CSS, JSP, MessagePackTM, Apache® ThriftTM, ASN.l, Google® Protocol Buffers (protobuf), or some other document(s)/format(s) such as those discussed herein.
  • An information object may have both a logical and a physical structure. Physically, an information object comprises one or more units called entities. An entity is a unit of storage that contains content and is identified by a name. An entity may refer to other entities to cause their inclusion in the information object. An information object begins in a document entity, which is also referred to as a root element (or “root”). Logically, an information object comprises one or more declarations, elements, comments, character references, and processing instructions, all of which are indicated in the information object (e.g., using markup).
  • data item refers to an atomic state of a particular object with at least one specific property at a certain point in time.
  • Such an object is usually identified by an object name or object identifier, and properties of such an object are usually defined as database objects (e.g., fields, records, etc.), object instances, or data elements (e.g., mark-up language elements/tags, etc.).
  • database objects e.g., fields, records, etc.
  • object instances e.g., mark-up language elements/tags, etc.
  • data elements e.g., mark-up language elements/tags, etc.
  • data item may refer to data elements and/or content items, although these terms may refer to difference concepts.
  • data element or “element” as used herein refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary.
  • a data element is a logical component of an information object (e.g., electronic document) that may begin with a start tag (e.g., “ ⁇ element>“) and end with amatching end tag (e.g., “ ⁇ /element>“), or only has an empty element tag (e.g., “ ⁇ element />“). Any characters between the start tag and end tag, if any, are the element’s content (referred to herein as “content items” or the like).
  • the content of an entity may include one or more content items, each of which has an associated datatype representation.
  • a content item may include, for example, attribute values, character values, URIs, qualified names (qnames), parameters, and the like.
  • a qname is a fully qualified name of an element, attribute, or identifier in an information object.
  • a qname associates a URI of a namespace with a local name of an element, attribute, or identifier in that namespace. To make this association, the qname assigns a prefix to the local name that corresponds to its namespace.
  • the qname comprises a URI of the namespace, the prefix, and the local name. Namespaces are used to provide uniquely named elements and attributes in information objects.
  • An “attribute” may refer to a markup construct including a name-value pair that exists within a start tag or empty element tag. Atributes contain data related to its element and/or control the element’s behavior.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated.
  • link refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
  • radio technology refers to technology for wireless transmission and/or reception of electromagnetic radiation for information transfer.
  • radio access technology refers to the technology used for the underlying physical connection to a radio based communication network.
  • communication protocol refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like.
  • radio technology refers to technology for wireless transmission and/or reception of electromagnetic radiation for information transfer.
  • radio access technology or “RAT” refers to the technology used for the underlying physical connection to a radio based communication network.
  • communication protocol (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like.
  • Examples of wireless communications protocols may be used in various embodiments include a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3 GPP) radio communication technology including, for example, 3 GPP Fifth Generation (5G) or New Radio (NR), Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), Long Term Evolution (LTE), LTE- Advanced (LTE Advanced), LTE Extra, LTE-A Pro, cdmaOne (2G), Code Division Multiple Access 2000 (CDMA 2000), Cellular Digital Packet Data (CDPD), Mobitex, Circuit Switched Data (CSD), High-Speed CSD (HSCSD), Universal Mobile Telecommunications System (UMTS), Wideband Code Division Multiple Access (W-CDM), High Speed Packet Access (HSPA), HSPA Plus (HSPA+), Time Division-Code Division Multiple Access (TD-CDMA), Time Division-Sy
  • V2X communication technologies including 3GPP C-V2X
  • DSRC Dedicated Short Range Communications
  • ITS Intelligent- Transport-Systems
  • any number of satellite uplink technologies may be used for purposes of the present disclosure including, for example, radios compliant with standards issued by the International Telecommunication Union (ITU), or the European Telecommunications Standards Institute (ETSI), among others.
  • ITU International Telecommunication Union
  • ETSI European Telecommunications Standards Institute
  • access network refers to any network, using any combination of radio technologies, RATs, and/or communication protocols, used to connect user devices and service providers.
  • an “access network” is an IEEE 802 local area network (LAN) or metropolitan area network (MAN) between terminals and access routers connecting to provider services.
  • LAN local area network
  • MAN metropolitan area network
  • access router refers to router that terminates a medium access control (MAC) service from terminals and forwards user traffic to information servers according to Internet Protocol (IP) addresses.
  • MAC medium access control
  • SMTC refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.
  • SSB refers to a synchronization signal/Physical Broadcast Channel (SS/PBCH) block, which includes a Primary Syncrhonization Signal (PSS), a Secondary Syncrhonization Signal (SSS), and a PBCH.
  • PSS Primary Syncrhonization Signal
  • SSS Secondary Syncrhonization Signal
  • PBCH Physical Broadcast Channel
  • a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
  • Primary SCG Cell refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
  • Secondary Cell refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
  • Secondary Cell Group refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
  • Serving Cell refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
  • serving cell refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA.
  • Special Cell refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.
  • Al policy refers to a type of declarative policies expressed using formal statements that enable the non-RT RIC function in the SMO to guide the near-RT RIC function, and hence the RAN, towards better fulfilment of the RAN intent.
  • Al Enrichment information refers to information utilized by near-RT RIC that is collected or derived at SMO/non-RT RIC either from non-network data sources or from network functions themselves.
  • Al -Policy Based Traffic Steering Process Mode refers to an operational mode in which the Near-RT RIC is configured through Al Policy to use Traffic Steering Actions to ensure a more specific notion of network performance (for example, applying to smaller groups of E2 Nodes and UEs in the RAN) than that which it ensures in the Background Traffic Steering.
  • Background Traffic Steering Processing Mode refers to an operational mode in which the Near-RT RIC is configured through 01 to use Traffic Steering Actions to ensure a general background network performance which applies broadly across E2 Nodes and UEs in the RAN.
  • Baseline RAN Behavior refers to the default RAN behavior as configured at the E2 Nodes by SMO
  • E2 refers to an interface connecting the Near-RT RIC and one or more O- CU-CPs, one or more O-CU-UPs, one or more O-DUs, and one or more O-eNBs.
  • E2 Node refers to a logical node terminating E2 interface.
  • ORAN nodes terminating E2 interface are: for NR access: O-CU-CP, O- CU-UP, 0-DU or any combination; and for E-UTRA access: 0-eNB.
  • Intents in the context of 0-RAN systems/implementations, refers to declarative policy to steer or guide the behavior of RAN functions, allowing the RAN function to calculate the optimal result to achieve stated objective.
  • non-RT RIC refers to a logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model training and updates, and policy-based guidance of applications/features in Near-RT RIC.
  • Near-RT RIC or “0-RAN near-real-time RAN Intelligent Controller” refers to a logical function that enables near-real-time control and optimization of RAN elements and resources via fine-grained (e.g., UE basis, Cell basis) data collection and actions over E2 interface.
  • fine-grained e.g., UE basis, Cell basis
  • 0-RAN Central Unit or “O-CU” refers to a logical node hosting RRC, SDAP and PDCP protocols.
  • 0-RAN Central Unit - Control Plane or “O-CU-CP” refers to a logical node hosting the RRC and the control plane part of the PDCP protocol.
  • 0-RAN Central Unit - User Plane or “0-CU-UP” refers to a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol
  • 0-RAN Distributed Unit or “0-DU” refers to a logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split.
  • O-RAN eNB or “O-eNB” refers to an eNB or ng-eNB that supports E2 interface.
  • O-RAN Radio Unit refers to a logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP’s “TRP” or “RRH” but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction).
  • the term “01” refers to an interface between orchestration & management entities (Orchestration/NMS) and O-RAN managed elements, for operation and management, by which FCAPS management, Software management, File management and other similar functions shall be achieved.
  • RAN UE Group refers to an aggregations of UEs whose grouping is set in the E2 nodes through E2 procedures also based on the scope of Al policies. These groups can then be the target of E2 CONTROL or POLICY messages.
  • Traffic Steering Action refers to the use of a mechanism to alter RAN behavior. Such actions include E2 procedures such as CONTROL and POLICY.
  • Traffic Steenng Inner Loop refers to the part of the Traffic Steenng processing, triggered by the arrival of periodic TS related KPM (Key Performance Measurement) from E2 Node, which includes UE grouping, setting additional data collection from the RAN, as well as selection and execution of one or more optimization actions to enforce Traffic Steering policies.
  • KPM Key Performance Measurement
  • Traffic Steering Outer Loop refers to the part of the Traffic Steering processing, triggered by the near-RT RIC setting up or updating Traffic Steering aware resource optimization procedure based on information from Al Policy setup or update, Al Enrichment Information (El) and/or outcome of Near-RT RIC evaluation, which includes the initial configuration (preconditions) and injection of related Al policies, Triggering conditions for TS changes.
  • Al Policy setup or update Al Enrichment Information (El) and/or outcome of Near-RT RIC evaluation, which includes the initial configuration (preconditions) and injection of related Al policies, Triggering conditions for TS changes.
  • El Al Enrichment Information
  • Triggering conditions for TS changes Triggering conditions for TS changes.
  • Traffic Steering Processing Mode refers to an operational mode in which either the RAN or the Near-RT RIC is configured to ensure a particular network performance. This performance includes such aspects as cell load and throughput, and can apply differently to different E2 nodes and UEs. Throughout this process, Traffic Steering Actions are used to fulfill the requirements of this configuration.
  • Traffic Steering Target refers to the intended performance result that is desired from the network, which is configured to Near-RT RIC over 01.
  • any of the disclosed embodiments and example implementations can be embodied in the form of various types of hardware, software, firmware, middleware, or combinations thereof, including in the form of control logic, and using such hardware or software in a modular or integrated manner.
  • any of the software components or functions described herein can be implemented as software, program code, script, instructions, etc., operable to be executed by processor circuitry. These components, functions, programs, etc., can be developed using any suitable computer language such as, for example.
  • the software code can be stored as a computer- or processorexecutable instructions or commands on a physical non-transitory computer-readable medium.
  • suitable media include RAM, ROM, magnetic media such as a hard-drive or a floppy disk, or an optical medium such as a compact disk (CD) or DVD (digital versatile disk), flash memory, and the like, or any combination of such storage or transmission devices.
  • RAM random access memory
  • ROM read-only memory
  • magnetic media such as a hard-drive or a floppy disk
  • optical medium such as a compact disk (CD) or DVD (digital versatile disk), flash memory, and the like, or any combination of such storage or transmission devices.
  • CD compact disk
  • DVD digital versatile disk
  • flash memory and the like, or any combination of such storage or transmission devices.

Landscapes

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

Abstract

La présente invention concerne des systèmes, des procédés et des dispositifs associés à un ordonnancement multi-cellules avancé et à une commande de puissance. Un dispositif peut décoder la configuration d'un ensemble d'espaces de recherche associé à des formats d'information de commande de liaison descendante (DCI) pour un ordonnancement multi-cellules. Le dispositif peut détecter un format d'information DCI pour un ordonnancement multi-cellules. Le dispositif peut décoder ou coder au moins un canal partagé de liaison descendante physique (PDSCH) ou au moins un canal partagé de liaison montante physique (PUSCHs) sur la base des indications dans le format d'information DCI détecté. Le dispositif peut coder une rétroaction d'accusé de réception de demande de répétition automatique hybride (HARQ-ACK) pour des canaux PDSCH reçus avec un livre de codes HARQ-ACK de type 2, avec une commande de puissance sur la base d'un nombre total de bits d'information HARQ-ACK ne dépassant pas une limite prédéfinie. Le dispositif peut générer des paramètres de commande de puissance sur la base de valeurs provenant du livre de codes HARQ-ACK de type 2.
PCT/US2023/069814 2022-07-08 2023-07-07 Commande de puissance et chronologie pour ordonnancement multi-cellules pour des opérations de nouvelle radio WO2024011244A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2022104507 2022-07-08
CNPCT/CN2022/104507 2022-07-08

Publications (1)

Publication Number Publication Date
WO2024011244A1 true WO2024011244A1 (fr) 2024-01-11

Family

ID=89454237

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/069814 WO2024011244A1 (fr) 2022-07-08 2023-07-07 Commande de puissance et chronologie pour ordonnancement multi-cellules pour des opérations de nouvelle radio

Country Status (1)

Country Link
WO (1) WO2024011244A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210250880A1 (en) * 2020-02-12 2021-08-12 Qualcomm Incorporated Feedback power control techniques for wireless communications systems
US20220217651A1 (en) * 2017-04-21 2022-07-07 Samsung Electronics Co., Ltd. Information type multiplexing and power control

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220217651A1 (en) * 2017-04-21 2022-07-07 Samsung Electronics Co., Ltd. Information type multiplexing and power control
US20210250880A1 (en) * 2020-02-12 2021-08-12 Qualcomm Incorporated Feedback power control techniques for wireless communications systems

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "PDSCH/PUSCH enhancements for 52-71GHz band", 3GPP DRAFT; R1-2100201, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. E-meeting; 20210125 - 20210205, 19 January 2021 (2021-01-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051970833 *
MODERATOR (LG ELECTRONICS): "Summary #3 of PDSCH/PUSCH enhancements (Scheduling/HARQ)", 3GPP DRAFT; R1-2205549, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220509 - 20220520, 24 May 2022 (2022-05-24), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052192172 *
SAMSUNG: "Multi-cell PUSCH/PDSCH scheduling with a single DCI", 3GPP DRAFT; R1-2203925, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220509 - 20220520, 29 April 2022 (2022-04-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052143996 *

Similar Documents

Publication Publication Date Title
WO2022087474A1 (fr) Hiérarchisation d'équipements intra-utilisateur pour gérer un chevauchement de canaux de commande montants et de données de liaison montante
EP4233419A1 (fr) Attribution de ressources pour un service de diffusion/multidiffusion en nouvelle radio
WO2022031553A1 (fr) Plan de données pour mégadonnées et données en tant que service dans des réseaux cellulaires de nouvelle génération
WO2022221495A1 (fr) Support d'apprentissage automatique pour services de gestion et services d'analyse de données de gestion
WO2022221260A1 (fr) Support de service de gestion de cycle de vie o-cloud
WO2022087489A1 (fr) Indication de faisceau basée sur des informations de commande de liaison descendante (dci) pour une nouvelle radio (nr)
WO2022125296A1 (fr) Mécanismes pour permettre des services informatiques en réseau
WO2024011244A1 (fr) Commande de puissance et chronologie pour ordonnancement multi-cellules pour des opérations de nouvelle radio
WO2024031028A1 (fr) Activation et désactivation d'une planification semi-persistante à l'aide de techniques multicellulaires
US20240155393A1 (en) Measurement reporting efficiency enhancement
WO2024092132A1 (fr) Chargement d'entité d'intelligence artificielle et d'apprentissage automatique dans des réseaux cellulaires
WO2024097726A1 (fr) Allocation de ressources pour mise en forme du spectre dans le domaine fréquentiel avec extension du spectre
WO2024026211A1 (fr) Régulation de puissance d'émission et de congestion pour positionnement en liaison latérale
WO2023122037A1 (fr) Mesures et données de localisation prenant en charge une analyse de données de gestion (mda) pour analyse de problème de couverture
US20240154761A1 (en) Phase tracking reference signal (pt-rs) pattern determination
WO2024020519A1 (fr) Systèmes et procédés de partage de services d'une fonction de stockage de données non structurées
WO2024026515A1 (fr) Test d'entité d'intelligence artificielle et d'apprentissage machine
WO2024015747A1 (fr) Sélection de fonction de gestion de session dans des réseaux cellulaires prenant en charge une strate de non-accès distribuée entre un dispositif et des fonctions de réseau
WO2024081642A1 (fr) Services de traitement en pipeline dans des réseaux cellulaires de prochaine génération
WO2023069750A1 (fr) Bons critères de qualité cellulaire
WO2024076852A1 (fr) Structure de fonction de coordination de collecte de données et de fonction d'analyse de données de réseau pour détection de services dans des réseaux cellulaires de prochaine génération
WO2023049345A1 (fr) Optimisation d'équilibrage de charge (lbo) pour systèmes 5g
WO2022261028A1 (fr) Fonctions de données et procédures dans un contrôleur intelligent de réseau d'accès radio non temps réel
WO2023122043A1 (fr) Mesures de performance pour une fonction de gestion d'emplacement sur une gestion d'emplacement
US20240187071A1 (en) Time domain restriction for channel state information reference signal configuration

Legal Events

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

Ref document number: 23836318

Country of ref document: EP

Kind code of ref document: A1