Default beam operation for uplink transmission

Abstract

Various embodiments herein may relate to default beam operations for uplink transmissions. In particular, some embodiments are directed to default beam operations for Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), or Sounding Reference Signal (SRS) transmissions in multiple transmit receive point (TRP) scenarios. Other embodiments may be disclosed and claimed.

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims priority to U.S. Provisional Patent Application No. 63 / 186,733, filed May 10, 2021.

[0002] Technical Field Various embodiments generally may relate to the field of wireless communication. For example, some embodiments may relate to default beam operation for uplink transmission. In particular, some embodiments are directed to default beam operation for physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), or sounding reference signal (SRS) transmission in a multi - transmission reception point (TRP) scenario.

Background Art

[0003] In New Radio (NR) Rel - 16, default beam operation is defined for SRS, PUCCH, and PUSCH scheduled by DCI 0_0 to reduce overhead. When the default beam is enabled for SRS / PUCCH, SRS / PUCCH can be configured without using spatial relation information, and a media access control (MAC) - control element (CE) for updating the spatial relation information for SRS / PUCCH is not required, and as a result, the MAC - CE overhead is reduced. When the default beam is enabled for PUSCH, PUSCH can be scheduled by DCI format 0_0 even if the PUCCH resource is not set on the CC or the PUCCH resource is set regardless of the spatial relation. However, the existing default beam operation for PUSCH / PUCCH / SRS does not consider PDCCH repetition in a multi - TRP scenario. Embodiments of the present disclosure address these and other problems. [Brief explanation of the drawing]

[0004] Embodiments will be readily apparent from the following detailed description relating to the attached drawings. For the purposes of this description, similar reference numerals indicate similar structural elements. Embodiments are shown in the figures of the attached drawings as examples, not as limitations. [Figure 1] Figure 1 illustrates an example of the problem of determining the uplink default beam when PDCCH iteration is enabled, in relation to various embodiments. [Figure 2] Figure 2 shows examples of default beams for PUSCH iterations when PDCCH iterations are enabled (Alt 1) in various embodiments. [Figure 3] Figure 3 shows examples of default beams for PUCCH iterations when PDCCH iterations are enabled (Alt 1) in various embodiments. [Figure 4] Figure 4 shows examples of default beams for SRS to multiple TRPs when PDCCH repetition is enabled (Alt 1) in various embodiments. [Figure 5] Figure 5 shows an example of the default beam for PUSCH / PUCCH / SRS in various embodiments where PDCCH iterations are enabled and the TCI state is associated with the closed-loop power control index (Alt 1). [Figure 6] Figure 6 schematically shows wireless networks according to various embodiments. [Figure 7] Figure 7 schematically shows the components of a wireless network according to various embodiments. [Figure 8] Figure 8 is a block diagram showing components of some exemplary embodiments that can read instructions from a machine-readable or computer-readable medium (e.g., a non-temporary machine-readable storage medium) and perform any one or more of the methods described herein. [Figure 9]Figure 9 shows an example of the procedure for carrying out the various embodiments described herein. [Figure 10] Figure 10 shows an example of the procedure for carrying out the various embodiments described herein. [Figure 11] Figure 11 shows an example of the procedure for carrying out the various embodiments described herein. [Modes for carrying out the invention] [Examples]

[0005] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify identical or similar elements. In the following description, certain details, such as specific structures, architectures, interfaces, and techniques, are described for illustrative purposes only, not limiting purposes, to provide a complete understanding of the various aspects of the various embodiments. However, it will be apparent to a person skilled in the art who benefits from this disclosure that various aspects of the various embodiments may be implemented in other examples that deviate from these specific details. In some examples, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary details. For the purposes of this specification, the terms "A or B" and "A / B" mean (A), (B), or (A and B).

[0006] As explained above, the existing default beam operation for PUSCH / PUCCH / SRS does not take into account PDCCH iterations in multi-TRP scenarios. For example, when the parameter enableDefaultBeamPlForSRS is set to 'enable', the default spatial relation / path loss reference signal for SRS is as follows:

[0007] • If a CORESET is configured on CC, the TCI state / QCL assumption of the CORESET with the lowest ID is used.

[0008] • If CORESET is not set on CC, the activated TCI state with the lowest ID for PDSCH is selected.

[0009] When the parameter enableDefaultBeamPlForPUCCH is set to 'enable', the default spatial relation / path loss reference signal for PUCCH is as follows:

[0010] • If a CORESET is configured on CC, assume the TCI status / QCL of the CORESET with the lowest ID.

[0011] When the parameter enableDefaultBeamPlForPUSCH0_0 is set to 'enable', the default spatial relation / path loss reference signal for the PUSCH scheduled by DCI 0_0 is as follows:

[0012] If a PUCCH resource is not configured in the active BWP within the CC, the default spatial relationship / path loss reference signal is assumed to be the TCI state / QCL of the CORESET with the lowest ID.

[0013] If PUCCH resources are configured regardless of spatial relationships, the default spatial relationship / path loss reference signal will follow the default spatial relationship / path loss reference signal of those PUCCH resources.

[0014] In NR Rel-17, PDCCH repetitions can be enabled for multi-TRP operation. PUSCH repetitions and PUCCH repetitions can also be enabled for reliability improvement. In this case, the default beam operation for the uplink should be improved. FIG. 1 shows an example of this problem. Therefore, the existing default beam operation for PUSCH / PUCCH / SRS does not consider PDCCH repetitions in a multi-TRP scenario. In particular, the various embodiments disclosed herein address these and other issues regarding the default beam operation for the uplink considering PDCCH repetitions in a multi-TRP scenario.

[0015] Case A: PUSCH 1. When PUSCH iteration is enabled In an embodiment, regarding multi-TRP operation, when PDCCH repetitions and PUSCH repetitions are enabled and the default beam for PUSCH is enabled, the default spatial relation / default path loss reference signal should be applied to PUSCH repetitions. The default spatial relation / default path loss reference signal can be defined by the following alternatives.

[0016] ·Alt 1: The default beam / path loss RS for PUSCH repetitions follows the TCI state of the CORESET / search space that carries the scheduling DCI. In one example, among the multiple CORESETs that transmit PDCCH repetitions, the TCI state of the CORESET with the lower ID is applied to the first PUSCH repetition (or the PUSCH repetition towards the first TRP); the TCI state of the CORESET with the higher ID among the multiple CORESETs that transmit PDCCH repetitions is applied to the second PUSCH repetition (or the PUSCH repetition towards the second TRP). FIG. 2 shows an example of the operation. ​​·Alt 2: When the PDSCH is specified in two TCI states, the TCI state for the PDSCH can be applied to PUSCH repetitions. In one example, among those mapped to the two TCI states, the first TCI state of the PDSCH corresponding to the lowest TCI code point is applied to the first PUSCH repetition (or the PUSCH repetition towards the first TRP); among those mapped to the two TCI states, the second TCI state of the PDSCH corresponding to the lowest TCI code point is applied to the second PUSCH repetition (or the PUSCH repetition towards the second TRP). In another example, the first TCI state among the active PDSCH TCI states is applied to the first PUSCH repetition (or the PUSCH repetition towards the first TRP); the second TCI state among the active PDSCH TCI states is applied to the second PUSCH repetition (or the PUSCH repetition towards the second TRP).

[0018] 2. If PUSCH iteration is not enabled In an embodiment, regarding multi-TRP operation, when PDCCH repetitions are enabled, PUSCH repetitions are not enabled, and the default beam for PUSCH is enabled, the default spatial relation / default path loss reference signal should be applied to the PUSCH. The default spatial relation / default path loss reference signal can be defined by the following alternative examples.

[0019] ·Alt 1: The default beam / path loss RS for the PUSCH follows the TCI state of the CORESET / search space that carries the scheduling DCI. In one example, among the multiple CORESETs that transmit PDCCH repetitions, the TCI state of the CORESET with a lower ID is applied to the PUSCH.

[0020] Alt 2: If a PDSCH is specified with two TCI states, the TCI states of the PDSCH can be applied to the PUSCH. In one example, the first TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to the two TCI states is applied to the PUSCH. In another example, the first TCI state of the active PDSCH TCI state is applied to the PUSCH.

[0021] • Alt 3: The default spatial relation / default path loss reference signal for PUSCH follows the TCI state of a specific CORESET / search space, e.g., the CORESET / search space with the lowest ID.

[0022] Case B: PUCCH 1. When PUCCH iterations are enabled In the embodiment, with respect to multi-TRP operation, if the PDCCH and PUCCH iterations are enabled and the default beam for PUCCH is enabled, the default spatial relation / default path loss reference signal should be applied to the PUCCH iteration. The default spatial relation / default path loss reference signal can be defined by the following alternative examples.

[0023] Alt 1: The default beam / path loss RS for PUCCH iterations follows the TCI state of the CORESET / search space carrying the scheduling DCI. For example, among multiple CORESETs sending PDCCH iterations, the TCI state of the CORESET with the lower ID is applied to the first PUCCH iteration (or PUCCH iteration toward the first TRP); among multiple CORESETs sending PDCCH iterations, the TCI state of the CORESET with the higher ID is applied to the second PUCCH iteration (or PUCCH iteration toward the second TRP). Figure 3 shows an example of operation.

[0024] Alt 2: If PDSCH is specified with two TCI states, the TCI states for PDSCH can be applied to PUCCH iterations. For example, the first TCI state of PDSCH corresponding to the lowest TCI code point among those mapped to two TCI states is applied to the first PUCCH iteration (or PUCCH iteration toward the first TRP); the second TCI state of PDSCH corresponding to the lowest TCI code point among those mapped to two TCI states is applied to the second PUCCH iteration (or PUCCH iteration toward the second TRP). In another example, the first TCI state of the active PDSCH TCI states is applied to the first PUCCH iteration (or PUCCH iteration toward the first TRP); the second TCI state of the active PDSCH TCI states is applied to the second PUCCH iteration (or PUCCH iteration toward the second TRP).

[0025] 2. If PUCCH iterations are not enabled In the embodiment, with respect to multi-TRP operation, if the PDCCH iteration is enabled, the PUCCH iteration is not enabled, and the default beam for PUCCH is enabled, then the default spatial relation / default path loss reference signal should be applied to PUCCH. The default spatial relation / default path loss reference signal can be defined by the following alternative examples.

[0026] Alt 1: The default beam / path loss RS for PUCCH follows the TCI state of the CORESET / search space that carries the scheduling DCI. For example, among multiple CORESETs sending PDCCH iterations, the TCI state of the CORESET with the lower ID is applied to PUCCH.

[0027] Alt 2: If a PDSCH is specified with two TCI states, the TCI states of the PDSCH can be applied to the PUCCH. In one example, the first TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to the two TCI states is applied to the PUCCH. In another example, the first TCI state of the active PDSCH TCI states is applied to the PUCCH.

[0028] • Alt 3: The default spatial relation / default path loss reference signal for PUCCH follows the TCI state of a specific CORESET / search space, e.g., the CORESET / search space with the lowest ID.

[0029] Case C: SRS 1. If an SRS resource set is triggered by a single TRP In the embodiment, with respect to multi-TRP operation, if PDCCH iterations are enabled, an SRS resource set for one TRP is triggered by the same DCI, and a default beam for the SRS is enabled, then a default spatial relationship / default path loss reference signal should be applied to the SRS. The default spatial relationship / default path loss reference signal can be defined by the following alternative examples.

[0030] Alt 1: The default beam / path loss RS for SRS follows the TCI state of the CORESET / search space that carries the triggering DCI. For example, among multiple CORESETs sending PDCCH iterations, the TCI state of the CORESET with the lower ID is applied to the SRS.

[0031] Alt 2: If a PDSCH is specified with two TCI states, the TCI states for the PDSCH can be applied to the SRS. In one example, the first TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to the two TCI states is applied to the SRS. In another example, the first TCI state of the active PDSCH TCI state is applied to the SRS.

[0032] Alt 3: The default spatial relation / default path loss reference signal for SRS follows the TCI state of a specific CORESET / search space, e.g., the CORESET / search space with the lowest ID.

[0033] 2. When the SRS resource set is triggered by multiple TRPs In the embodiment, with respect to multi-TRP operation, if PDCCH iterations are enabled, SRS resource sets for multiple TRPs are triggered by the same DCI, and a default beam for SRS is enabled, then a default spatial relationship / default path loss reference signal should be applied to SRS. The default spatial relationship / default path loss reference signal can be defined by the following alternative examples.

[0034] Alt 1: The default beam / path loss RS for SRS follows the TCI state of the CORESET / search space that carries the scheduling DCI. For example, the TCI state of the CORESET with the lower ID among multiple CORESETs transmitting PDCCH iterations is applied to the SRS resource set using the first closed-loop power control index, e.g., the SRS resource set directed to the first TRP; the TCI state of the CORESET with the higher ID among multiple CORESETs transmitting PDCCH iterations is applied to the SRS resource set using the second closed-loop power control index, e.g., the SRS resource set directed to the second TRP. Figure 4 shows an example of operation.

[0035] Alt 2: If a PDSCH is specified with two TCI states, the TCI states for the PDSCH can be applied to the SRS. For example, the first TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to two TCI states is applied to the SRS resource set configured using the first closed-loop power control index, for example, the SRS resource set directed to the first TRP; the second TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to two TCI states is applied to the SRS resource set configured using the second closed-loop power control index, for example, the SRS resource set directed to the second TRP. In another example, the first TCI state of the active PDSCH TCI states is applied to the SRS resource set configured using the first closed-loop power control index, for example, the SRS resource set directed to the first TRP; the second TCI state of the active PDSCH TCI states is applied to the SRS resource set configured using the second closed-loop power control index, for example, the SRS resource set directed to the second TRP.

[0036] Case D: Explicit relationship between PDCCH and TRP In the embodiment, the TCI state of PDCCH / PDSCH can be associated with a TRP. In one example, the association is via an uplink closed-loop power control index, for example, a closed-loop power control index for PUSCH. The TCI state for PDCCH / PDSCH from a first TRP is associated with a first closed-loop power control index. The TCI state for PDCCH / PDSCH from a second TRP is associated with a second closed-loop power control index. The association between the TCI state and the uplink closed-loop power control index can be set by RRC and / or updated by MAC-CE.

[0037] When PDCCH iterations are enabled, the default spatial relation / default path loss RS for PUSCH / PUCCH / SRS (regardless of whether PUSCH / PUCCH iterations are enabled or whether an SRS directed to one or more TRPs is triggered) can be determined by the following alternative examples.

[0038] • Alt 1: The default beam / path loss RS for PUSCH / PUCCH / SRS (or PUSCH / PUCCH iterations, SRS, directed toward different TRPs) follows the TCI state of the CORESET / search space that carries the scheduling / triggering DCI, where the CORESET / search space is associated with the same TRP, e.g., the same closed-loop power control index as PUSCH / PUCCH / SRS. Figure 5 shows an example of operation.

[0039] Alt 2: The default beam / path loss RS for PUSCH / PUCCH / SRS (or PUSCH / PUCCH iterations, SRS, directed toward different TRPs) follows the TCI state of one particular CORESET / search space, where that CORESET / search space has the lowest ID associated with the same TRP, e.g., PUSCH / PUCCH / SRS, with the same closed-loop power control index.

[0040] Alt 3: If a PDSCH is specified with two TCI states, the TCI states for the PDSCH can be applied to the PUSCH / PUCCH / SRS. For example, with respect to a PUSCH / PUCCH / SRS (or a PUSCH / PUCCH iteration, SRS) associated with a particular closed-loop power control index, the TCI state of the PDSCH corresponding to the lowest TCI code point among the two mapped TCI states is applied to the PUSCH / PUCCH / SRS (where that TCI state is associated with the same closed-loop index). In another example, with respect to a PUSCH / PUCCH / SRS (or a PUSCH / PUCCH iteration, SRS) associated with a particular closed-loop power control index, the TCI state of the active PDSCH TCI states is applied to the PUSCH / PUCCH / SRS (where that TCI state is associated with the same closed-loop index).

[0041] If PDCCH iterations are not enabled, the default spatial relation / default path loss RS for PUSCH / PUCCH / SRS (regardless of whether PUSCH / PUCCH iterations are enabled or not, and regardless of whether an SRS is triggered toward one or more TRPs) can be determined by the following alternative example.

[0042] Alt 1: If a PUSCH / PUCCH / SRS (or a PUSCH / PUCCH iteration, SRS) directed to a different TRP is configured using the same closed-loop power control index as the CORESET / search space carrying the scheduling / triggering DCI, then the default beam / path loss RS for PUSCH / PUCCH / SRS should follow the TCI state of the CORESET / search space carrying the scheduling / triggering DCI. Otherwise, the default beam / path loss RS for PUSCH / PUCCH / SRS should follow the TCI state of one specific CORESET / search space, where that CORESET / search space has the lowest ID associated with the same TRP, e.g., the same closed-loop power control index as PUSCH / PUCCH / SRS.

[0043] Alt 2: If a PDSCH is specified with two TCI states, the TCI states for the PDSCH can be applied to the PUSCH / PUCCH / SRS. For example, with respect to a PUSCH / PUCCH / SRS (or a PUSCH / PUCCH iteration, SRS) associated with a particular closed-loop power control index, the TCI state of the PDSCH corresponding to the lowest TCI code point among the two mapped TCI states is applied to the PUSCH / PUCCH / SRS (where that TCI state is associated with the same closed-loop index). In another example, with respect to a PUSCH / PUCCH / SRS (or a PUSCH / PUCCH iteration, SRS) associated with a particular closed-loop power control index, the TCI state of the active PDSCH TCI states is applied to the PUSCH / PUCCH / SRS (where that TCI state is associated with the same closed-loop index).

[0044] System and Implementation Figure 6-7 shows various systems, devices, and components that may implement aspects of the disclosed embodiments.

[0045] Figure 6 shows Network 600 in various embodiments. Network 600 can operate in a manner compliant with 3GPP® technical specifications for LTE or 5G / NR systems. However, exemplary embodiments are not limited thereto, and the embodiments described may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems.

[0046] Network 600 may include UE 602, which may include any mobile or non-mobile computing device designed to communicate with RAN 604 via an over-the-air connection. UE 602 can be coupled to RAN 604 in a communicative manner via a Uu interface. UE 602 may be, but is not limited to, smartphones, tablet computers, wearable computer devices, desktop computers, laptop computers, automotive infotainment, automotive entertainment devices, instrument clusters, head-up display devices, automotive diagnostic devices, dash-top mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, network equipment, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0047] In some embodiments, the network 600 may include multiple UEs directly coupled to one another via a sidelink interface. The UEs may be M2M / D2D devices communicating using a physical sidelink channel, which may be, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0048] In some embodiments, UE 602 may further communicate with AP 606 via an over-the-air connection. AP 606 may manage the WLAN connection, which may function to offload all / part of the network traffic from RAN 604. The connection between UE 602 and AP 606 may conform to any IEEE 802.11 protocol, where AP 606 may be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, UE 602, RAN 604, and AP 606 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular WLAN aggregation may include UE 602 configured by RAN 604 to utilize both cellular radio resources and WLAN resources.

[0049] RAN 604 may include one or more access nodes, for example, AN 608. AN 608 can terminate the air interface protocol for UE 602 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 608 can enable data / voice connectivity between CN 620 and UE 602. In some embodiments, AN 608 may be implemented in a separate device, or as one or more software entities running on a server computer as part of a virtual network that may be referred to as CRAN or a virtual baseband unit pool, for example. AN 608 may also be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 608 may be a macrocell base station, or it may be a low-power base station that provides a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0050] In embodiments where RAN 604 includes multiple ANs, they can be coupled to each other via an X2 interface (if RAN 604 is an LTE RAN) or an Xn interface (if RAN 604 is a 5G RAN). In some embodiments, the X2 / Xn interface can be separated into a control / user plane interface, which allows ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0051] Each AN of RAN 604 is capable of managing one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 602. UE 602 may be simultaneously connected to multiple cells provided by the same or different ANs of RAN 604. For example, UE 602 and RAN 604 can use carrier aggregation to enable UE 602 to connect to multiple component carriers, each corresponding to a Pcell or Scell. In a dual-connection scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs can be any combination of eNBs, gNBs, ng-eNBs, etc.

[0052] The RAN 604 can provide an air interface via authorized or unauthorized spectra. To operate in unauthorized spectra, the node can use LAA, eLAA, and / or feLAA mechanisms based on CA technology using PCell / SCell. Before accessing unauthorized spectra, the node can perform medium / carrier sensing operations, for example, based on the Listen Before Talk (LBT) protocol.

[0053] In a V2X scenario, UE 602 or AN 608 may refer to, or act as, an RSU, any transport infrastructure entity used for V2X communication. An RSU may be implemented in, or by, a suitable AN or stationary (or relatively stationary) UE. “RSU implemented in, or by” means: one by a UE may be called a “UE-type RSU”; one by an eNB may be called an “eNB-type RSU”; one by a gNB may be called a “gNB-type RSU,” and so on. In one example, an RSU is a computing device coupled to a roadside radio frequency circuit that provides connectivity support to a passing vehicle UE. An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling oncoming vehicle and pedestrian traffic. An RSU can provide very low-latency communication required for high-speed events such as collision avoidance and traffic warnings. Additionally or alternatively, an RSU can provide other cellular / WLAN communication services. The components of the RSU may be packaged in an all-weather enclosure suitable for outdoor installation and may include a network interface controller for providing wired connectivity (e.g., Ethernet®) to a traffic signal controller or backhaul network.

[0054] In some embodiments, RAN 604 may be an LTE RAN 610 having an eNB, eNB 612, for example. The LTE RAN 610 can provide an LTE air interface having the following characteristics: 15 kHz SCS; CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for US; turbo coding for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; CRS for cell discovery and initial capture; channel quality measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface can operate in the sub-6 GHz band.

[0055] In some embodiments, the RAN 604 may be an NG-RAN 614 having a gNB, e.g., gNB 616, or an ng-eNB, e.g., ng-eNB 618. The gNB 616 can connect to a 5G-enabled UE using a 5G NR interface. The gNB 616 can connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 618 can also connect to the 5G core via an NG interface, but can also connect to the UE via an LTE Air interface. The gNB 616 and ng-eNB 618 can connect to each other via an Xn interface.

[0056] In some embodiments, the NG interface can be divided into two parts: an NG user plane (NG-U) interface (e.g., N3 interface) that carries traffic data between the NG-RAN 614 nodes and the UPF 648, and an NG control plane (NG-C) interface (e.g., N2 interface) that is a signaling interface between the NG-RAN 614 nodes and the AMF 644.

[0057] NG-RAN 614 can provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetitive, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface can rely on CSI-RS and PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G-NR air interface may not use CRS, but can use PBCH DMRS for PBCH demodulation, PTRS for phase tracking for PDSCH, and a tracking reference signal for time tracking. The 5G-NR air interface can operate in the FR1 band, including the sub-6 GHz band, or the FR2 band, including the band from 24.25 GHz to 52.6 GHz. The 5G-NR air interface can include SSB, which is the area of ​​the downlink resource grid including PSS / SSS / PBCH.

[0058] In some embodiments, the 5G-NR air interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For instance, UE 602 can be configured with multiple BWPs, in which case each BWP configuration has a different SCS. When a change in BWP is instructed to UE 602, the transmit SCS is also changed. Another example of a use case for BWPs relates to power saving. In particular, it is possible to configure multiple BWPs for UE 602 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. BWPs with fewer PRBs can be used for data transmission with low traffic loads while enabling power saving in UE 602 and possibly gNB 616. BWPs with more PRBs can be used for scenarios with higher traffic loads.

[0059] RAN 604 is communicatively coupled to CN 620, which includes network elements for providing various functions to customers / subscribers (e.g., users of UE 602) to support data and telecommunications services. The components of CN 620 can be implemented on one physical node or separate physical nodes. In some embodiments, NFV can be used to virtualize some or all of the functions provided by the network elements of CN 620 on physical computing / storage resources such as servers and switches. Logical instantiations of CN 620 may be referred to as network slices, and some logical instantiations of CN 620 may be referred to as network sub-slices.

[0060] In some embodiments, CN 620 may be LTE CN 622, which may also be referred to as EPC. LTE CN 622 may include MME 624, SGW 626, SGSN 628, HSS 630, PGW 632, and PCRF 634 coupled to one another via an interface (or “reference point”) as shown. The functions of the elements of LTE CN 622 are briefly described below.

[0061] The MME 624 can implement mobility management capabilities to track the current location of the UE 602 in order to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, and more.

[0062] SGW 626 can terminate the S1 interface toward the RAN and route data packets between the RAN and LTE CN 622. SGW 626 can be a local mobility anchor point for handovers between RAN nodes and can provide an anchor for movement between 3GPP nodes. Other responsibilities may include lawful interception, billing, and any policy enforcement.

[0063] The SGSN 628 can track the location of the UE 602 and perform security functions and access control. Furthermore, the SGSN 628 can perform EPC node signaling for mobility between different RAT networks; PDN and S-GW selection specified by the MME 624; MME selection for handover, etc. An S3 reference point between the MME 624 and the SGSN 628 can enable the exchange of user and bearer information for mobility between 3GPP access networks in idle / active states.

[0064] The HSS 630 can include a database for network users, containing join-related information to support the processing of network entities in communication sessions. The HSS 630 can provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS 630 and the MME 624 can enable the transfer of join and authentication data for authenticating / authorizing user access to the LTE CN 620.

[0065] PGW 632 can terminate the SGi interface toward the data network (DN) 636, which may contain an application / content server 638. PGW 632 can route data packets between the LTE CN 622 and the data network 636. PGW 632 can be coupled to SGW 626 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 632 may further include nodes (e.g., PCEF) for policy enforcement and billing data collection. Furthermore, the SGi reference point between PGW 632 and the data network 636 may be for an operator-external public, private PDN, or intra-operator packet data network, such as for providing IMS services. PGW 632 can be coupled to PCRF 634 via a Gx reference point.

[0066] PCRF 634 is the policy and billing control element of LTE CN 622. PCRF 634 can be communicatively coupled to application / content server 638 to determine appropriate QoS and billing parameters for service flows. PCRF 632 can prepare associated rules in the PCEF (via Gx reference points) along with appropriate TFT and QCI.

[0067] In some embodiments, CN 620 may be 5GC 640. 5GC 640 can include AUSF 642, AMF 644, SMF 646, UPF 648, NSSF 650, NEF 652, NRF 654, PCF 656, UDM 658, and AF 660, coupled to each other via interfaces (or "reference points") as shown. The functions of the elements of 5GC 640 are briefly described below.

[0068] The AUSF 642 is capable of storing data for authentication of the UE 602 and processing authentication-related functions. The AUSF 642 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 640 via reference points as illustrated, the AUSF 642 can present a Nausf service-based interface.

[0069] The AMF 644 can enable other functions of the 5GC 640 to communicate with the UE 602 and RAN 604, and to schedule notifications about mobility events related to the UE 602. The AMF 644 may have responsibilities for registration management (e.g., for registering the UE 602), connectivity management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 644 can forward SM messages between the UE 602 and the SMF 646 and act as a transparent proxy for routing SM messages. The AMF 644 can also forward SMS messages between the UE 602 and the SMF 646. The AMF 644 can interact with the AUSF 642 and UE 602 to perform various security anchor and context management functions. Furthermore, the AMF 644 may also be the termination point of the RAN CP interface, which may be the N2 reference point between the RAN 604 and the AMF 644, or include it; the AMF 644 may also be the termination point of NAS(N1) signaling, enabling NAS encryption and integrity protection. The AMF 644 may also support NAS signaling with the UE 602 via the N3 IWF interface.

[0070] SMF 646 may be responsible for SM (e.g., session establishment, tunnel management between UPF 648 and AN 608); UE IP address assignment and management (including optional authorization); selection and control of UP functions; setting traffic steering in UPF 648 for routing traffic to appropriate destinations; termination of the interface to policy control functions; control of policy enforcement, billing, and QoS parts; lawful interception (of SM events and interfaces to L1 systems); termination of the SM part of NAS messages; downlink data notification; initiation of AN-specific SM information transmitted to AN 608 via N2 through AMF 644; and determination of the session's SSC mode. SM may refer to the management of PDU sessions, and PDU sessions or "session" may refer to PDU connectivity services that provide or enable the exchange of PDUs between UE 602 and data network 636.

[0071] The UPF 648 can function as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to data network 636, and a branching point to support multi-homed PDU sessions. The UPF 648 can also perform packet routing and forwarding, perform packet inspection, enforce the user-plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform user-plane QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), perform transport-level packet marking on uplinks and downlinks, and perform downlink packet buffering and downlink data notification triggering. The UPF 648 can include an uplink classifier to support routing of traffic flows to the data network.

[0072] The NSSF 650 can select a set of network slice instances to correspond to the UE 602. The NSSF 650 can also determine, if necessary, authorized NSSAIs and their mappings to subscribed S-NSSAIs. Based on a preferred configuration, the NSSF 650 can also determine a set of AMFs, or a list of candidate AMFs, to be used to correspond to the UE 602, possibly by querying the NRF 654. The selection of a set of network slice instances for the UE 602 can be triggered by an AMF 644, which the UE 602 registers with the NSSF 650 upon interaction, and which may result in a change in the AMF. The NSSF 650 can interact with the AMF 644 via the N22 reference point; and can communicate with another NSSF in the visited network via the N31 reference point (not shown). Furthermore, the NSSF 650 can provide an Nnssf service-based interface.

[0073] NEF 652 can reliably expose services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, AFs (e.g., AF 660), edge computing, or fog computing systems. In such embodiments, NEF 652 can authenticate, authorize, or restrict AFs. NEF 652 can also convert information exchanged with AF 660 and information exchanged with internal network functions. For example, NEF 652 can convert between AF service identifiers and internal 5 GC information. NEF 652 can also receive information from other NFs based on the exposed capabilities of those NFs. This information may be stored in NEF 652 as structured data or in a data storage NF using a standardized interface. The stored information can then be re-exposed by NEF 652 to other NFs and AFs, or used for other purposes such as analysis. Furthermore, the NEF 652 can represent an Nnef service-based interface.

[0074] NRF 654 supports service discovery functionality, receiving NF discovery requests from NF instances and providing information about discovered NF instances to those instances. NRF 654 also maintains information about available NF instances and their supported services. As used herein, terms such as "instantiate" and "instantiation" may refer to the creation of an instance, and "instance" may refer to the specific occurrence of an object, for example, during the execution of program code. Furthermore, NRF 654 may represent an Nnrf service-based interface.

[0075] The PCF 656 can provide policy rules to control plane functions and enforce them, and can also manage network behavior by supporting an integrated policy framework. The PCF 656 can also implement a front-end for accessing subscription information related to policy decisions in the UDR of the UDM 658. In addition to communicating with functional units via reference points as illustrated, the PCF 656 exhibits an Npcf service-based interface.

[0076] The UDM 658 is capable of processing subscriber-related information to support the processing of network entities in a communication session and can store subscriber data for UE 602. For example, subscriber data may be communicated via an N8 reference point between the UDM 658 and the AMF 644. The UDM 658 can include two parts: an application front-end and a UDR. The UDR can store subscriber and policy data for the UDM 658 and PCF 656, and / or structured data for publication and application data for the NEF 652 (including PFD for application discovery and application request information for multiple UE 602). A Nudr service-based interface, indicated by the UDR 221, can enable the UDM 658, PCF 656, and NEF 652 to access specific sets of stored data, as well as read, update (e.g., add, modify), delete, and reserve notifications of relevant data changes within the UDR. The UDM can include a UDM-FE responsible for processing credentials, location management, and enrollment management. Several different front-ends can serve the same user in different transactions. The UDM-FE accesses enrollment information stored in the UDR and performs credential processing, user identification, access control, enrollment / mobility management, and enrollment management. In addition to communicating with other NFs via reference points as illustrated, the UDM 658 can represent a Nudm service-based interface.

[0077] The AF 660 provides application influence over traffic routing, offers access to the NEF, and can interact with the policy framework for policy control.

[0078] In some embodiments, the 5GC 640 is positioned so that the UE 602 is geographically close to the point where it is attached to the network.rd By selecting a party service, edge computing can be enabled. This can reduce latency and load on the network. To provide an implementation of edge computing, the 5GC 640 can select UPF 648, which is close to UE 602, and perform traffic steering from UPF 648 to data network 636 via the N6 interface. This can be based on UE subscriber data, UE location, and information provided by AF 660. In this way, AF 660 can influence UPF (re)selection and traffic routing. If AF 660 is considered a trusted entity based on the operator's deployment, the network operator can allow AF 660 to interact directly with the relevant NF. Furthermore, AF 660 can represent a NAF service-based interface.

[0079] The data network 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, an application / content server 638.

[0080] Figure 7 schematically illustrates the wireless network 700 in various embodiments. The wireless network 700 may include a UE 702 that wirelessly communicates with AN 704. UE 702 and AN 704 are similar in name to components described elsewhere in this specification and may be substantially interchangeable.

[0081] UE 702 can be communicatively coupled to AN 704 via connection 706. Connection 706 is shown as an air interface to enable communication coupling and can comply with cellular communication protocols such as LTE or 5G NR protocols operating on mm wave or sub-6GHz frequencies.

[0082] The UE 702 may include a host platform 708 coupled to a modem platform 710. The host platform 708 may include an application processing circuit 712 that can be coupled to a protocol processing circuit 714 of the modem platform 710. The application processing circuit 712 is capable of running various applications for the UE 702 to source / sink application data. The application processing circuit 712 is further capable of performing one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

[0083] The protocol processing circuit 714 can perform one or more layer operations to facilitate the transmission or reception of data over connection 706. Layer operations performed by the protocol processing circuit 714 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0084] The modem platform 710 may further include a digital baseband circuit 716, which is capable of performing one or more layer operations that are “lower” layer operations performed by the protocol processing circuit 714 in the network protocol stack. These operations may include, for example, PHY operations that include HARQ-ACK functionality, scrambling / descrambling, coding / decoding, layer mapping / de-mapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding which may include one or more of space-time, space-frequency, or space coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronous sequence generation / detection, control channel signal blind decoding, and one or more other related functions.

[0085] The modem platform 710 may further include a transmitting circuit 718, a receiving circuit 720, an RF circuit 722, and an RF front end (RFFE) 724, which may include or be connectable to one or more antenna panels 726. The transmitting circuit 718 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) element, etc.; the receiving circuit 720 may include an analog-to-digital converter, a mixer, an IF element, etc.; the RF circuit 722 may include a low-noise amplifier, a power amplifier, a power tracking element, etc.; the RFFE 724 may include a filter (e.g., a surface / bulk acoustic wave filter), a switch, an antenna tuner, a beamforming element (e.g., a phased array antenna element), etc. The selection and arrangement of components of the transmitting circuit 718, receiving circuit 720, RF circuit 722, RFFE 724, and antenna panel 726 (collectively referred to as “transmitting / receiving elements”) may be specific to particular implementation details, such as whether the communication is in millimeter wave or sub-6 GHz frequency, or whether it is TDM or FDM. In some embodiments, the transmitting / receiving elements may be arranged in multiple parallel transmit / receive chains, or may be located on the same or different chips / modules, etc.

[0086] In some embodiments, the protocol processing circuit 714 may include one or more instances of a control circuit (not shown) that provides control functions for the transmitting / receiving elements.

[0087] UE reception can be established by and through the antenna panel 726, RFFE 724, RF circuit 722, receiving circuit 720, digital baseband circuit 716, and protocol processing circuit 714. In some embodiments, the antenna panel 726 can receive transmissions from AN 704 by receiving beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 726.

[0088] UE transmission can be established by and through the protocol processing circuit 714, the digital baseband circuit 716, the transmitting circuit 718, the RF circuit 722, the RFFE 724, and the antenna panel 726. In some embodiments, the transmitting element of UE 704 can apply a spatial filter to the data to be transmitted in order to form a transmit beam emitted by the antenna elements of the antenna panel 726.

[0089] Similar to UE 702, AN 704 may include a host platform 728 coupled to a modem platform 730. The host platform 728 may include an application processing circuit 732 coupled to the protocol processing circuit 734 of the modem platform 730. The modem platform may further include a digital baseband circuit 736, a transmit circuit 738, a receive circuit 740, an RF circuit 742, an RFFE circuit 744, and an antenna panel 746. The components of AN 704 may be similar to and substantially interchangeable with similarly named components of UE 702. In addition to performing data transmission / reception as described above, the components of AN 708 may perform various logical functions, including, for example, radio bearer management, dynamic uplink and downlink radio resource management, and RNC functions such as data packet scheduling.

[0090] Figure 8 is a block diagram showing components of some exemplary embodiment capable of reading instructions from a machine-readable medium or a computer-readable medium (e.g., a non-temporary machine-readable storage medium) and executing any one or more of the methods described herein. Specifically, Figure 8 shows a schematic representation of hardware resources 800 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 can be communicatively coupled via a bus 840 or other interface circuitry. In embodiments utilizing node virtualization (e.g., NFV), the hypervisor 802 may be implemented to provide execution environments for one or more network slices / sub-slices for utilizing the hardware resources 800.

[0091] Processor 810 may include, for example, processors 812 and 814. Processor 810 may be, for example, a central processing unit (CPU), a reduced instruction set arithmetic (RISC) processor, a composite instruction set arithmetic (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those described herein), or any suitable combination thereof.

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

[0093] The communication resource 830 includes an interconnector or network interface controller, components, or other suitable devices, and is capable of communicating with one or more peripheral devices 804 or one or more databases 806 or other network elements via the network 808. For example, the communication resource 830 may include wired communication elements (e.g., those connected via USB, Ethernet®, etc.), cellular communication elements, NFC elements, Bluetooth® (or Bluetooth® Low Energy) elements, Wi-Fi® elements, and other communication elements.

[0094] Instruction 850 may include software, programs, applications, applets, apps, or other executable code that causes at least one of the processors 810 to execute any one or more of the methods described herein. Instruction 850 may reside entirely or partially in at least one of the processors 810 (e.g., in the processor's cache memory), the memory / storage device 820, or any preferred combination thereof. Furthermore, any part of instruction 850 may be transferred from any combination of peripheral devices 804 or database 806 to the hardware resource 800. Thus, the memory of the processor 810, the memory / storage device 820, the peripheral device 804, and the database 806 are examples of computer-readable and machine-readable media.

[0095] Example procedure In some embodiments, an electronic device, network, system, chip, or component, or part thereof or implementation, in Figures 6-8 or any other drawings herein, can be configured to perform one or more processes, techniques, or methods, or parts thereof, described herein. One such process is shown in Figure 9. In this example, process 900 includes, in 905, retrieving configuration information from memory for uplink transmission by a user device (UE), wherein the configuration information includes instructions that default beam operation be enabled for uplink transmission and that physical downlink control channel (PDCCH) iterations be enabled for the operation of a multitransmit / receive point (TRP). The process further includes, in 910, encoding a message for transmission to the UE, including the configuration information.

[0096] Another such process is shown in Figure 10. In this example, process 1000 includes determining configuration information for uplink transmission by the user equipment (UE) at 1005, where the configuration information includes instructions that default beam operation be enabled for uplink transmission and that iteration of the physical downlink control channel (PDCCH) be enabled for the operation of the multi-transmit / receive point (TRP). The process further includes encoding a message to be sent to the UE at 1010, where the configuration information in the message is contained in downlink control information (DCI).

[0097] Another such process is shown in Figure 11. In this example, process 1100 includes, in 1105, the user equipment (UE) receiving a configuration message from the next-generation NodeB (gNB) containing configuration information for uplink transmission by the UE, where the configuration information includes instructions that default beam operation is enabled for uplink transmission and that physical downlink control channel (PDCCH) iteration is enabled for the operation of the multi-transmit / receive point (TRP). The process further includes, in 1110, encoding the uplink message to be transmitted based on the configuration information.

[0098] In one or more embodiments, at least one of the components described in one or more of the aforementioned drawings may be configured to perform one or more operations, techniques, processes, and / or methods as described in the following exemplary section. For example, a baseband circuit described in relation to one or more of the aforementioned drawings may be configured to operate according to one or more of the examples described below. In another example, a circuit related to a UE, base station, network element, etc., described in relation to one or more of the aforementioned drawings may be configured to operate according to one or more of the examples described in the following exemplary section.

[0099] Case study In Example 1, the gNB may include a method for configuring the UE by uplink transmission including PUSCH / PUCCH / SRS. Example 2 may include the methods of Example 1 or any other example in this case, in which case the gNB may enable PDCCH repeats carrying the same DCI, and the PDCCH repeats may be transmitted from different TRPs. Example 3 may include the methods of Example 1 or any other example in this case, in which case the gNB may enable PUSCH iterations or PUCCH iterations. Iterations may be sent by the UE to different TRPs. The gNB may also trigger SRS transmissions to different TRPs via a single DCI. Example 3 may include the methods of Examples 2 and 3 or any other examples in this case, in which case the default spatial relation / default path loss reference signal should be applied to the PUSCH repeat if the PDCCH repeat and PUSCH repeat are enabled and the default beam for PUSCH is enabled. The default spatial relation / default path loss reference signal can be defined by the following alternative example. Alt 1: The default beam / path loss RS for PUSCH iterations follows the TCI state of the CORESET / search space carrying the scheduling DCI. For example, among multiple CORESETs sending PDCCH iterations, the TCI state of the CORESET with the lower ID is applied to the first PUSCH iteration (or PUSCH iteration toward the first TRP); among multiple CORESETs sending PDCCH iterations, the TCI state of the CORESET with the higher ID is applied to the second PUSCH iteration (or PUSCH iteration toward the second TRP). Alt 2: If a PDSCH is specified with two TCI states, the TCI states for the PDSCH can be applied to the PUSCH iteration. For example, the first TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to the two TCI states is applied to the first PUSCH iteration (or the PUSCH iteration toward the first TRP); the second TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to the two TCI states is applied to the second PUSCH iteration (or the PUSCH iteration toward the second TRP). In another example, the first TCI state of the active PDSCH TCI states is applied to the first PUSCH iteration (or the PUSCH iteration toward the first TRP); the second TCI state of the active PDSCH TCI states is applied to the second PUSCH iteration (or the PUSCH iteration toward the second TRP). Example 5 may include the methods of Examples 2 and 3 or any other examples in this case, in which case the default spatial relation / default path loss reference signal should be applied to PUSCH, provided that the PDCCH repeat is enabled, the PUSCH repeat is not enabled, and the default beam for PUSCH is enabled. The default spatial relation / default path loss reference signal can be defined by the following alternative examples. • Alt 1: The default beam / path loss RS for PUSCH follows the TCI state of the CORESET / search space that carries the scheduling DCI. For example, among multiple CORESETs sending PDCCH iterations, the TCI state of the CORESET with the lower ID is applied to PUSCH. Alt 2: If a PDSCH is specified with two TCI states, the TCI states of the PDSCH can be applied to the PUSCH. In one example, the first TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to the two TCI states is applied to the PUSCH. In another example, the first TCI state of the active PDSCH TCI state is applied to the PUSCH. • Alt 3: The default spatial relation / default path loss reference signal for PUSCH follows the TCI state of a specific CORESET / search space, e.g., the CORESET / search space with the lowest ID. Example 6 may include the methods of Examples 2 and 3 or any other examples in this case, in which case the default spatial relation / default path loss reference signal should be applied to the PUCCH repeat if the PDCCH repeat and PUCCH repeat are enabled and the default beam for PUCCH is enabled. The default spatial relation / default path loss reference signal can be defined by the following alternative example. Alt 1: The default beam / path loss RS for PUCCH iterations follows the TCI state of the CORESET / search space carrying the scheduling DCI. For example, among multiple CORESETs sending PDCCH iterations, the TCI state of the CORESET with the lower ID is applied to the first PUCCH iteration (or PUCCH iteration toward the first TRP); among multiple CORESETs sending PDCCH iterations, the TCI state of the CORESET with the higher ID is applied to the second PUCCH iteration (or PUCCH iteration toward the second TRP). Alt 2: If PDSCH is specified with two TCI states, the TCI states for PDSCH can be applied to PUCCH iterations. For example, the first TCI state of PDSCH corresponding to the lowest TCI code point among those mapped to two TCI states is applied to the first PUCCH iteration (or PUCCH iteration toward the first TRP); the second TCI state of PDSCH corresponding to the lowest TCI code point among those mapped to two TCI states is applied to the second PUCCH iteration (or PUCCH iteration toward the second TRP). In another example, the first TCI state of the active PDSCH TCI states is applied to the first PUCCH iteration (or PUCCH iteration toward the first TRP); the second TCI state of the active PDSCH TCI states is applied to the second PUCCH iteration (or PUCCH iteration toward the second TRP). Example 7 may include the methods of Examples 2 and 3 or any other examples in this case, in which case the default spatial relation / default path loss reference signal should be applied to PUCCH, where the PDCCH repeat is enabled, the PUCCH repeat is not enabled, and the default beam for PUCCH is enabled. The default spatial relation / default path loss reference signal can be defined by the following alternative examples. Alt 1: The default beam / path loss RS for PUCCH follows the TCI state of the CORESET / search space that carries the scheduling DCI. For example, among multiple CORESETs sending PDCCH iterations, the TCI state of the CORESET with the lower ID is applied to PUCCH. Alt 2: If a PDSCH is specified with two TCI states, the TCI states of the PDSCH can be applied to the PUCCH. In one example, the first TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to the two TCI states is applied to the PUCCH. In another example, the first TCI state of the active PDSCH TCI states is applied to the PUCCH. • Alt 3: The default spatial relation / default path loss reference signal for PUCCH follows the TCI state of a specific CORESET / search space, e.g., the CORESET / search space with the lowest ID. Example 8 may include the methods of Examples 2 and 3 or any other examples present, in which case the default spatial relation / default path loss reference signal should be applied to the SRS if the PDCCH iteration is enabled, the SRS resource set for one TRP is triggered by the same DCI, and the default beam for the SRS is enabled. The default spatial relation / default path loss reference signal can be defined by the following alternative examples. Alt 1: The default beam / path loss RS for SRS follows the TCI state of the CORESET / search space that carries the triggering DCI. For example, among multiple CORESETs sending PDCCH iterations, the TCI state of the CORESET with the lower ID is applied to the SRS. Alt 2: If a PDSCH is specified with two TCI states, the TCI states for the PDSCH can be applied to the SRS. In one example, the first TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to the two TCI states is applied to the SRS. In another example, the first TCI state of the active PDSCH TCI state is applied to the SRS. Alt 3: The default spatial relation / default path loss reference signal for SRS follows the TCI state of a specific CORESET / search space, e.g., the CORESET / search space with the lowest ID. Example 9 may include the methods of Examples 2 and 3 or any other examples present, in which case a default spatial relation / default path loss reference signal should be applied to the SRS if PDCCH iterations are enabled, SRS resource sets for multiple TRPs are triggered by the same DCI, and a default beam for the SRS is enabled. The default spatial relation / default path loss reference signal can be defined by the following alternative examples. Alt 1: The default beam / path loss RS for SRS follows the TCI state of the CORESET / search space that carries the scheduling DCI. For example, the TCI state of the CORESET with the lower ID among multiple CORESETs transmitting PDCCH iterations is applied to the SRS resource set using the first closed-loop power control index, e.g., the SRS resource set directed to the first TRP; the TCI state of the CORESET with the higher ID among multiple CORESETs transmitting PDCCH iterations is applied to the SRS resource set using the second closed-loop power control index, e.g., the SRS resource set directed to the second TRP. Alt 2: If a PDSCH is specified with two TCI states, the TCI states for the PDSCH can be applied to the SRS. For example, the first TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to two TCI states is applied to the SRS resource set configured using the first closed-loop power control index, for example, the SRS resource set directed to the first TRP; the second TCI state of the PDSCH corresponding to the lowest TCI code point among those mapped to two TCI states is applied to the SRS resource set configured using the second closed-loop power control index, for example, the SRS resource set directed to the second TRP. In another example, the first TCI state of the active PDSCH TCI states is applied to the SRS resource set configured using the first closed-loop power control index, for example, the SRS resource set directed to the first TRP; the second TCI state of the active PDSCH TCI states is applied to the SRS resource set configured using the second closed-loop power control index, for example, the SRS resource set directed to the second TRP. Example 10 may include the methods of Examples 2 and 3 or any other examples present herein, in which case the TCI state of PDCCH / PDSCH may be associated with a TRP. In one example, the association is via an uplink closed-loop power control index, e.g., a closed-loop power control index for PUSCH. The TCI state for PDCCH / PDSCH from a first TRP is associated with a first closed-loop power control index. The TCI state for PDCCH / PDSCH from a second TRP is associated with a second closed-loop power control index. The association between the TCI state and the uplink closed-loop power control index can be set by RRC and / or updated by MAC-CE. Example 11 may include the methods of Examples 2, 3, and 10 or any other examples in this case, in which case, if PDCCH iterations are enabled, the default spatial relation / default path loss RS for PUSCH / PUCCH / SRS (whether PUSCH / PUCCH iterations are enabled or not, and whether an SRS directed to one or more TRPs is triggered or not) may be determined by the following alternative examples. Alt 1: The default beam / path loss RS for PUSCH / PUCCH / SRS (or PUSCH / PUCCH iterations, SRS, directed toward different TRPs) follows the TCI state of the CORESET / search space that carries the scheduling / triggering DCI, where the CORESET / search space is associated with the same TRP, e.g., the same closed-loop power control index as PUSCH / PUCCH / SRS. Alt 2: The default beam / path loss RS for PUSCH / PUCCH / SRS (or PUSCH / PUCCH iterations, SRS, directed toward different TRPs) follows the TCI state of one particular CORESET / search space, where that CORESET / search space has the lowest ID associated with the same TRP, e.g., PUSCH / PUCCH / SRS, with the same closed-loop power control index. Alt 3: If a PDSCH is specified with two TCI states, the TCI states for the PDSCH can be applied to the PUSCH / PUCCH / SRS. For example, with respect to a PUSCH / PUCCH / SRS (or a PUSCH / PUCCH iteration, SRS) associated with a particular closed-loop power control index, the TCI state of the PDSCH corresponding to the lowest TCI code point among the two mapped TCI states is applied to the PUSCH / PUCCH / SRS (where that TCI state is associated with the same closed-loop index). In another example, with respect to a PUSCH / PUCCH / SRS (or a PUSCH / PUCCH iteration, SRS) associated with a particular closed-loop power control index, the TCI state of the active PDSCH TCI states is applied to the PUSCH / PUCCH / SRS (where that TCI state is associated with the same closed-loop index). Example 12 may include the methods of Examples 2, 3 and 10 or any other examples in this case, in which case, if PDCCH iterations are not enabled, the default spatial relation / default path loss RS for PUSCH / PUCCH / SRS (whether PUSCH / PUCCH iterations are enabled or not, and whether an SRS directed to one or more TRPs is triggered or not) may be determined by the following alternative example. Alt 1: If a PUSCH / PUCCH / SRS (or a PUSCH / PUCCH iteration, SRS) directed to a different TRP is configured using the same closed-loop power control index as the CORESET / search space carrying the scheduling / triggering DCI, then the default beam / path loss RS for PUSCH / PUCCH / SRS should follow the TCI state of the CORESET / search space carrying the scheduling / triggering DCI. Otherwise, the default beam / path loss RS for PUSCH / PUCCH / SRS should follow the TCI state of one specific CORESET / search space, where that CORESET / search space has the lowest ID associated with the same TRP, e.g., the same closed-loop power control index as PUSCH / PUCCH / SRS. Alt 2: If a PDSCH is specified with two TCI states, the TCI states for the PDSCH can be applied to the PUSCH / PUCCH / SRS. For example, with respect to a PUSCH / PUCCH / SRS (or a PUSCH / PUCCH iteration, SRS) associated with a particular closed-loop power control index, the TCI state of the PDSCH corresponding to the lowest TCI code point among the two mapped TCI states is applied to the PUSCH / PUCCH / SRS (where that TCI state is associated with the same closed-loop index). In another example, with respect to a PUSCH / PUCCH / SRS (or a PUSCH / PUCCH iteration, SRS) associated with a particular closed-loop power control index, the TCI state of the active PDSCH TCI states is applied to the PUSCH / PUCCH / SRS (where that TCI state is associated with the same closed-loop index). Example 13 may include a method of UE, which is: A step of receiving PDCCH repetitions from different TRPs, wherein the PDCCH repetitions contain the same DCI, and scheduling uplink transmissions along with repetitions to different TRPs; and Includes the step of encoding an uplink transmission with repetitions based on DCI; Example 14 may include the methods of Example 13 or any other example in this case, in which case the uplink transmission includes one or more of PUSCH, PUCCH, and / or SRS. Example 15 may include the methods of Examples 13-14 or any other examples present herein, and further include the step of determining a default spatial relationship and / or default path loss reference signal for uplink transmission. Example 16 may include the methods of Example 15 or any other example present herein, in which the default spatial relation and / or default path loss reference signal is based on the TCI state of the control resource set carrying the DCI. Example 17 may include the methods of Example 15 or any other example in this case, in which case the default spatial relation and / or default path loss reference signal is based on the TCI state of the PDSCH. Example X1. The device is: A memory for storing configuration information for uplink transmission by user equipment (UE); and Processing circuitry coupled to memory; The processing circuit includes: The configuration information is retrieved from memory, and a message containing the configuration information is encoded for transmission to the UE, the configuration information including an instruction that default beam operation is enabled for uplink transmission and an instruction that physical downlink control channel (PDCCH) iterations are enabled for the operation of multiple transmit / receive points (TRP). Example X2 includes the device of Example X1 or any other example in this case, in which case the configuration information in the message is included in the downlink control information (DCI). Example X3 includes the apparatus of Example X1 or any other example in this case, in which case the uplink transmission is a physical uplink shared channel (PUSCH) transmission, a physical uplink controlled channel (PUCCH) transmission, or a sounding reference signal (SRS) transmission. Example X4 includes the apparatus of Example X3 or any other example in this case, in which case the uplink transmit is a PUSCH transmit or PUCCH transmit with repetition enabled or disabled, and the default spatial relation or path loss reference signal for the uplink transmit is: The state of the transmit configuration indicator (TCI) of the control resource set (CORESET) or search space that carries downlink control information (DCI); or Multiple TCI states associated with physical downlink shared channel (PDSCH) transmission; It is associated with this. Example X5 includes the apparatus of Example X3 or any other example in this case, in which case the uplink transmission is a PUSCH transmission or PUCCH transmission with repetition disabled, and the default spatial relation or path loss reference signal for the uplink transmission is associated with the TCI state of the CORESET or search space having the lowest identifier among a plurality of CORESETs or search spaces. Example X6 includes the apparatus of Example X3 or any other example in this case, in which case the uplink transmission is an SRS transmission, one or more SRS resource sets for one TRP are triggered by a common DCI, the default beam for SRS is enabled, and the default spatial relation or path loss reference signal for SRS transmission is: The TCI state of the CORESET or search space that carries the triggering DCI; A TCI state among multiple TCI states associated with PDSCH; or The TCI state of the CORESET or search space with the lowest identifier among multiple CORESETs or search spaces; It is associated with this. Example X7 includes a device from any one of Examples X1-X6 or any other example in this case, in which case the device includes a next-generation NodeB (gNB) or a portion thereof. Example X8 includes one or more computer-readable storage media that store instructions, and when the instructions are executed by one or more processors, they are sent to the next-generation NodeB (gNB): The system determines the configuration information for uplink transmission by the user equipment (UE) and encodes a message containing the configuration information for transmission to the UE; The configuration information includes an instruction that default beam operation is enabled for uplink transmission, and an instruction that physical downlink control channel (PDCCH) iteration is enabled for multi-transmit / receive point (TRP) operation; The configuration information within the message is included in the Downlink Control Information (DCI). Example X9 includes one or more computer-readable media of Example X8 or any other example herein, in which case the uplink transmission is a physical uplink shared channel (PUSCH) transmission, a physical uplink controlled channel (PUCCH) transmission, or a sounding reference signal (SRS) transmission. Example X10 includes one or more computer-readable media of Example X9 or any other example herein, in which case the uplink transmission is a PUSCH transmission or PUCCH transmission with repetition enabled or disabled, and the default spatial relation or path loss reference signal for the uplink transmission is: The state of the transmit configuration indicator (TCI) of the control resource set (CORESET) or search space that carries downlink control information (DCI); or Multiple TCI states associated with physical downlink shared channel (PDSCH) transmission; It is associated with this. Example X11 includes one or more computer-readable media of Example X9 or any other example in this case, in which case the uplink transmission is a PUSCH transmission or PUCCH transmission with repetition disabled, and the default spatial relation or path loss reference signal for the uplink transmission is associated with the TCI state of the CORESET or search space having the lowest identifier among a plurality of CORESETs or search spaces. Example X12 includes one or more computer-readable media of Example X9 or any other example herein, in which case the uplink transmission is an SRS transmission, one or more SRS resource sets for one TRP are triggered by a common DCI, the default beam for SRS is enabled, and the default spatial relation or path loss reference signal for SRS transmission is: The TCI state of the CORESET or search space that carries the triggering DCI; A TCI state among multiple TCI states associated with PDSCH; or The TCI state of the CORESET or search space with the lowest identifier among multiple CORESETs or search spaces; It is associated with this. Example X13 is one or more computer-readable media for storing instructions, where the instructions, when executed by one or more processors, are sent to the user device (UE): The UE receives a configuration message from the next-generation NodeB (gNB) containing configuration information for uplink transmission, and then encodes the uplink message to be transmitted based on that configuration information; The configuration information includes an instruction that default beam operation is enabled for uplink transmission, and an instruction that physical downlink control channel (PDCCH) iteration is enabled for multi-transmit / receive point (TRP) operation. Example X14 includes one or more computer-readable media of Example X13 or any other example herein, in which case the uplink transmission is a physical uplink shared channel (PUSCH) transmission, a physical uplink controlled channel (PUCCH) transmission, or a sounding reference signal (SRS) transmission. Example X15 includes one or more computer-readable media of Example X14 or any other example herein, in which case the uplink transmission is a PUSCH transmission or PUCCH transmission with repetition enabled or disabled, and the default spatial relation or path loss reference signal for the uplink transmission is: The state of the transmit configuration indicator (TCI) of the control resource set (CORESET) or search space that carries downlink control information (DCI); or Multiple TCI states associated with physical downlink shared channel (PDSCH) transmission; It is associated with this. Example X16 includes one or more computer-readable media of Example X14 or any other example in this case, in which case the uplink transmission is a PUSCH transmission or PUCCH transmission with repetition disabled, and the default spatial relation or path loss reference signal for the uplink transmission is associated with the TCI state of the CORESET or search space having the lowest identifier among a plurality of CORESETs or search spaces. Example X17 includes one or more computer-readable media of Example X14 or any other example herein, in which case the uplink transmission is an SRS transmission, one or more SRS resource sets for one TRP are triggered by a common DCI, the default beam for SRS is enabled, and the default spatial relation or path loss reference signal for SRS transmission is: The TCI state of the CORESET or search space that carries the triggering DCI; A TCI state among multiple TCI states associated with PDSCH; or The TCI state of the CORESET or search space with the lowest identifier among multiple CORESETs or search spaces; It is associated with this. Example X18 includes a computer-readable medium from any one of Examples X13-X17 or one or more of any other examples in this document, in which case the configuration information in the configuration message is included in the downlink control information (DCI). Example Z01 may include an apparatus having means for performing one or more elements of the methods described in or related to any one of Examples 1-X18, or any other methods or processes described herein. Example Z02 may include one or more non-temporary computer-readable media containing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the methods described or related to any one of Examples 1-X18, or any other methods or processes described herein. Example Z03 may include a device comprising logic, modules, or circuits that perform one or more elements of the methods described in or related to any one of Examples 1-X18, or any other methods or processes described herein. Example Z04 may include methods, techniques, or processes described or related to any of Examples 1-X18 or any part or portion thereof. Example Z05 may include a device comprising one or more processors and one or more computer-readable media containing instructions, which, when executed by one or more processors, cause one or more processors to execute a method, technique, or process, or part thereof, described or related to any of Examples 1-X18. Example Z06 may include signals described or related to any of Examples 1-X18 or any part or portion thereof. Example Z07 may include data, packets, frames, segments, protocol data units (PDUs), or messages described or related to any of Examples 1-X18 or any part or portion thereof, or otherwise described in this disclosure. Example Z08 may include a signal that is encoded together with data described or related to any of Examples 1-X18 or any part or portion thereof, or otherwise described in this disclosure. Example Z09 may include signals encoded with data, packets, frames, segments, protocol data units (PDUs), or messages described or related to any of Examples 1-X18 or any part or portion thereof, or otherwise described in this disclosure. Example Z10 may include an electromagnetic signal carrying a computer-readable instruction, and the execution of the computer-readable instruction by one or more processors causes one or more processors to perform a method, technique, or process described or related to any or part of Examples 1-X18. Example Z11 may include a computer program containing instructions, and the execution of the program by the processing element causes the processing element to perform a method, technique, or process described or related to any or part of Examples 1-X18. Example Z12 may include signals in a wireless network as illustrated or described herein. Example Z13 may include a method of communication in a wireless network as illustrated or described herein. Example Z14 may include a system that provides wireless communication as illustrated or described herein. Example Z15 may include a device that provides wireless communication as illustrated or described herein. Any of the above examples can be combined with any other example (or combination of examples) unless explicitly stated otherwise. The above descriptions of one or more implementations are illustrative and explanatory, but are not intended to be exhaustive or to limit the scope of embodiments to the exact forms disclosed. Modifications and variations are possible in light of the above teachings or may be made from the conventions of various embodiments.

[0100] Abbreviation Unless otherwise used herein, terms, definitions, and abbreviations may correspond to those defined in 3GPP TR21.905 v16.0.0 (2019-06). For the purposes of this specification, the following abbreviations may apply to the examples and embodiments described herein. 3GPP: Third Generation Partnership Project 4G: Fourth Generation 5G: Fifth Generation 5GC: 5G Core network; 5G Core Network AC:Application Client:Application Client ACR: Application Context Relocation: Application Context Relocation ACK: Acknowledgement; Delivery Confirmation ACID: Application Client Identification AF: Application Function AM: Acknowledged Mode; Confirmation Mode AMBR: Aggregate Maximum Bit Rate AMF: Access and Mobility Management Function AN: Access Network ANR: Automatic Neighbor Relation AOA:Angle of Arrival;Angle of Arrival AP: Application Protocol, Antenna Port, Access Point API: Application Programming Interface APN: Access Point Name ARP: Allocation and Retention Priority ARQ:Automatic Repeat Request AS: Access Stratum ASP: Application Service Provider ASN.1: Abstract Syntax Notation One AUSF: Authentication Server Function AWGN: Additive White Gaussian Noise BAP: Backhaul Adaptation Protocol BCH: Broadcast Channel BER: Bit Error Ratio BFD: Beam Failure Detection BLER: Block Error Rate BPSK: Binary Phase Shift Keying BRAS: Broadband Remote Access Server BSS: Business Support System BS:Base Station BSR: Buffer Status Report BW: Bandwidth BWP: Bandwidth Part; Bandwidth portion C-RNTI: Cell Radio Network Temporary Identity CA: Carrier Aggregation, Certification Authority CAPEX:CAPital Expenditure;Capital Expenditure CBRA: Contention-Based Random Access CC:Component Carrier, Country Code, Cryptographic Checksum CCA: Clear Channel Assessment CCE: Control Channel Element CCCH: Common Control Channel CE: Coverage Enhancement CDM: Content Delivery Network CDMA:Code-Division Multiple Access;Code-Division Multiple Access CDR: Charging Data Request; billing data request CDR: Charging Data Response CFRA: Contention-Free Random Access CG: Cell Group CGF: Charging Gateway Function CHF: Charging Function; billing function CI: Cell Identity; Cell Identifier CID: Cell-ID (e.g., positioning method) CIM: Common Information Model CIR: Carrier-to-Interference Ratio CK: Cipher Key; encryption key CM:Connection Management, Conditional Mandatory;Connection Management, Conditional Mandatory CMAS: Commercial Mobile Alert Service CMD: Command; Command CMS: Cloud Management System CO: Conditional Optional CoMP: Coordinated Multi-Point CORESET: Control Resource Set COTS: Commercial Off-The-Shelf CP: Control Plane, Cyclic Prefix, Connection Point CPD: Connection Point Descriptor CPE: Customer Premise equipment; customer terminals CPICH: Common Pilot Channel CQI: Channel Quality Indicator CPU: CSI processing unit, Central Processing Unit; CSI processing unit, central processing unit C / R: Command / Response field bit CRAN: Cloud Radio Access Network, Cloud RAN; Cloud Wireless Access Network, Cloud RAN CRB: Common Resource Block CRC:Cyclic Redundancy Check CRI: Channel-State Information Resource Indicator, CSI-RS Resource Indicator; Channel State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI: Cell RNTI CS: Circuit Switched CSCF: Call Session Control Function CSAR: Cloud Service Archive CSI: Channel-State Information; Channel State Information CSI-IM:CSI Interference Measurement CSI-RS: CSI Reference Signal CSI-RSRP: CSI reference signal received power; CSI reference signal received power CSI-RSRQ: CSI reference signal received quality CSI-SINR: CSI signal-to-noise and interference ratio; CSI signal-to-noise plus interference ratio CSMA: Carrier Sense Multiple Access CSMA / CA:CSMA with collision avoidance ;Collision avoidance type CSMA CSS:Common Search Space, Cell-specific Search Space;Common Search Space, Cell-specific Search Space CTF: Charging Trigger Function; billing trigger function CTS: Clear-to-Send CW: Codeword; Codeword CWS: Contention Window Size; Conflict Window Size D2D: Device-to-Device DC: Dual Connectivity, Direct Current; Dual connection, DC DCI: Downlink Control Information DF: Deployment Flavor DL:Downlink; Downlink DMTF: Distributed Management Task Force DPDK: Data Plane Development Kit DM-RS, DMRS: Demodulation Reference Signal DN: Data network; Data Network DNN: Data Network Name DNAI: Data Network Access Identifier DRB: Data Radio Bearer DRS: Discovery Reference Signal DRX: Discontinuous Reception DSL: Domain Specific Language. Digital Subscriber Line. DSLAM: DSL Access Multiplexer DwPTS: Downlink Pilot Time Slot E-LAN: Ethernet Local Area Network E2E: End-to-End EAS: Edge Application Server ECCA: Extended Clear Channel Assessment, Extended CCA ECCE: Enhanced Control Channel Element, Enhanced CCE; Enhanced Control Channel Evaluation, Enhanced CCE ED: Energy Detection EDGE: Enhanced Datarates for GSM Evolution (GSM Evolution); Enhanced database for GSM Evolution (GSM Evolution) EAS: Edge Application Server EASID: Edge Application Server Identification ECS: Edge Configuration Server ECSP: Edge Computing Service Provider EDN: Edge Data Network EEC: Edge Enabler Client EECID: Edge Enabler Client Identification EES: Edge Enabler Server EESID: Edge Enabler Server Identification EHE: Edge Hosting Environment EGMF: Exposure Governance Management Function EGPRS: Enhanced GPRS EIR: Equipment Identity Register eLAA: Enhanced Licensed Assisted Access; Enhanced LAA EM: Element Manager eMBB: Enhanced Mobile Broadband EMS: Element Management System eNB:evolved NodeB, E-UTRAN Node B;Evolved NodeB EN-DC: E-UTRA-NR Dual Connectivity; E-UTRA-NR Dual Connection EPC: Evolved Packet Core EPDCCH: enhanced PDCCH, enhanced Physical Downlink Control Channel EPRE: Energy per resource element EPS: Evolved Packet System EREG: enhanced REG, enhanced resource element groups; enhanced REG, enhanced resource element groups ETSI: European Telecommunications Standards Institute ETWS: Earthquake and Tsunami Warning System eUICC: embedded UICC, embedded Universal Integrated Circuit Card; built-in UICC, built-in universal integrated circuit card E-UTRA: Evolved UTRA; Evolved UTRA E-UTRAN: Evolved UTRAN; Evolved UTRAN EV2X: Enhanced V2X; Enhanced V2X F1AP: F1 Application Protocol; F1 Application Protocol F1-C: F1 Control Plane Interface F1-U: F1 User Plane Interface; F1 User Plane Interface FACCH: Fast Associated Control Channel FACCH / F: Fast Associated Control Channel / Full rate FACCH / H: Fast Associated Control Channel / Half rate FACH: Forward Access Channel FAUSCH: Fast Uplink Signaling Channel FB: Functional Block FBI: Feedback Information FCC: Federal Communications Commission FCCH: Frequency Correction Channel FDD: Frequency Division Duplex FDM: Frequency Division Multiplexing FDMA: Frequency Division Multiple Access FE: Front End; Front End FEC: Forward Error Correction FFS: For Further Study; Further research subject FFT: Fast Fourier Transformation feLAA: further enhanced Licensed Assisted Access, further enhanced LAA; Farther Enhanced Licensed Assisted Access, Farther Enhanced LAA FN: Frame Number; Frame Name FPGA: Field-Programmable Gate Array FR: Frequency Range FQDN: Fully Qualified Domain Name G-RNTI: GERAN Radio Network Temporary Identity; GERAN Radio Network Temporary Identifier GERAN: GSM EDGE RAN, GSM EDGE Radio Access Network; GSM Edge RAN, GSM Edge Radio Access Network GGSN: Gateway GPRS Support Node GLONASS: GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System); Global Navigation Satellite System gNB:Next Generation NodeB;Next Generation NodeB gNB-CU: gNB-centralized unit, Next Generation NodeB Centralized unit; gNB central unit, next generation NodeB central unit gNB-DU: gNB-distributed unit, Next Generation NodeB distributed unit; gNB distributed unit, Next Generation NodeB distributed unit GNSS: Global Navigation Satellite System GPRS: General Packet Radio Service GPSI: Generic Public Subscription Identifier GSM: Global System for Mobile Communications, Groupe Special Mobile; Mobile Communications Global System, Groupe Special Mobile GTP: GPRS Tunneling Protocol GTP-U: GPRS Tunneling Protocol for User Plane GTS: Go To Sleep Signal (related to WUS) GUMMEI: Globally Unique MME Identifier GUTI: Globally Unique Temporary UE Identity; a globally unique temporary UE identifier. HARQ: Hybrid ARQ, Hybrid Automatic Repeat Request HANDO: Handover; Handover HFN: HyperFrame Number HHO: Hard Handover HLR: Home Location Register HN: Home Network HO: Handover; Handover HPLMN: Home Public Land Mobile Network HSDPA: High Speed ​​Downlink Packet Access HSN: Hopping Sequence Number HSPA: High Speed ​​Packet Access HSS: Home Subscriber Server HSUPA: High Speed ​​Uplink Packet Access HTTP: Hyper Text Transfer Protocol HTTPS:Hyper Text Transfer Protocol Secure (https is http / 1.1 over SSL, ie port 443) I-Block Information Block; Hypertext Transfer Protocol Secure ICCID: Integrated Circuit Card Identification IAB: Integrated Access and Backhaul ICIC: Inter-Cell Interference Coordination ID: Identity, identifier; identity, identifier IDFT: Inverse Discrete Fourier Transform IE: Information element; information element IBE: In-Band Emission IEEE: Institute of Electrical and Electronics Engineers; Japan Electrical and Electronics Engineers Association IEI: Information Element Identifier IEIDL: Information Element Identifier Data Length; IETF: Internet Engineering Task Force IF: Infrastructure IIOT: Industrial Internet of Things IM: Interference Measurement, Intermodulation, IP Multimedia IMC: IMS Credentials; IMS Certification Information IMEI: International Mobile Equipment Identity IMGI: International mobile group identity; International Mobile Group Identifier IMPI: IP Multimedia Private Identity IMPU: IP Multimedia Public Identity IMS: IP Multimedia Subsystem IMSI: International Mobile Subscriber Identity IoT: Internet of Things IP: Internet Protocol IPsec: IP Security, Internet Protocol Security; IP Security, Internet Protocol Security IP-CAN: IP-Connectivity Access Network IP-M: IP Multicast; IP Multicast IPv4: Internet Protocol Version 4 IPv6: Internet Protocol Version 6 IR: Infrared; infrared IS: In Sync; Synchronization IRP: Integration Reference Point ISDN: Integrated Services Digital Network ISIM: IM Services Identity Module ISO: International Organization for Standardization ISP: Internet Service Provider IWF: Interworking Function I-WLAN: Interworking WLAN Convolutional code, USIM individual key length limit kB: Kilobyte (1000 bytes); kilobyte kbps: kilobits per second Kc: Ciphering key; encryption key Ki: Individual subscriber authentication key KPI: Key Performance Indicator KQI: Key Quality Indicator KSI: Key Set Identifier ksps:kilo-symbols per second; kilo-symbols per second KVM: Kernel Virtual Machine L1: Layer 1 (physical layer) L1-RSRP: Layer 1 reference signal received power; L2: Layer 2 (data link layer) L3: Layer 3 (Network Layer) LAA: Licensed Assisted Access LAN: Local Area Network LADN: Local Area Data Network LBT: Listen Before Talk LCM: Life Cycle Management LCR: Low Chip Rate LCS: Location Services; positioning services LCID: Logical Channel ID LI: Layer Indicator LLC: Logical Link Control, Low Layer Compatibility LMF: Location Management Function LOS: Line of Sight LPLMN: Local PLMN; Local PLMN LPP: LTE Positioning Protocol LSB: Least Significant Bit LTE: Long Term Evolution LWA: LTE-WLAN aggregation; LTE-WLAN aggregation LWIP: LTE / WLAN Radio Level Integration with IPsec Tunnel LTE: Long Term Evolution M2M: Machine-to-Machine MAC: Medium Access Control (protocol layering context) MAC: Message authentication code (security / encryption context); MAC-A: MAC used for authentication and key agreement (TSG T WG3 context); MAC used for authentication and key assignment (TSG T WG3 context) MAC-IMAC used for data integrity of signaling messages (TSG T WG3 context); MAC used for data integrity of signaling messages (TSG T WG3 context) MANO: Management and Orchestration MBMS: Multimedia Broadcast and Multicast Service MBSFN: Multimedia Broadcast Multicast Service Single Frequency Network MCC: Mobile Country Code MCG: Master Cell Group MCOT: Maximum Channel Occupancy Time MCS: Modulation and coding scheme MDAF: Management Data Analytics Function MDAS: Management Data Analytics Service MDT: Minimization of Drive Tests ME: Mobile Equipment; Mobile Devices MeNB:master eNB;Master eNB MER: Message Error Ratio MGL: Measurement Gap Length MGRP: Measurement Gap Repetition Period MIB: Master Information Block, Management Information Base MIMO: Multiple Input Multiple Output MLC: Mobile Location Centre MM: Mobility Management MME: Mobility Management Entity MN: Master Node MNO: Mobile Network Operator MO: Measurement Object, Mobile Originated; Measurement target, mobile origin MPBCH: MTC Physical Broadcast Channel MPDCCH: MTC Physical Downlink Control Channel MPDSCH: MTC Physical Downlink Shared Channel MPRACH: MTC Physical Random Access Channel MPUSCH: MTC Physical Uplink Shared Channel MPLS: MultiProtocol Label Switching MS:Mobile Station MSB: Most Significant Bit; Most Significant Bit MSC: Mobile Switching Centre MSI: Minimum System Information, MCH Scheduling Information MSID: Mobile Station Identifier MSIN: Mobile Station Identification Number MSISDN: Mobile Subscriber ISDN Number MT: Mobile Terminated, Mobile Termination; Mobile Terminal MTC: Machine-Type Communications mMTC: massive MTC, massive Machine-Type Communications; massive MTC, massive machine-type communications MU-MIMO: Multi-User MIMO MWUS: MTC wake-up signal, MTC WUS: MTC wake-up signal NACK: Negative Acknowledgement; Negative Response NAI: Network Access Identifier NAS: Non-Access Stratum, Non-Access Stratum layer; Non-access layer NCT: Network Connectivity Topology NC-JT: Non-Coherent Joint Transmission NEC: Network Capability Exposure NE-DC: NR-E-UTRA Dual Connectivity; NR-E-UTRA Dual Connection NEF: Network Exposure Function NF: Network Function; Network Function NFP: Network Forwarding Path NFPD: Network Forwarding Path Descriptor NFV: Network Functions Virtualization NFVI: NFV Infrastructure NFVO: NFV Orchestrator; NFV Orchestrator NG: Next Generation, Next Gen; next generation NGEN-DC: NG-RAN E-UTRA-NR Dual Connectivity; NG-RAN E-UTRA-NR Dual Connection NM: Network Manager NMS: Network Management System N-PoP: Network Point of Presence NMIB, N-MIB Narrowband MIB; N-MIB narrowband MIB NPBCH: Narrowband Physical Broadcast Channel NPDCCH: Narrowband Physical Downlink Control Channel NPDSCH: Narrowband Physical Downlink Shared Channel NPRACH: Narrowband Physical Random Access Channel NPUSCH: Narrowband Physical Uplink Shared Channel NPSS: Narrowband Primary Synchronization Signal NSSS: Narrowband Secondary Synchronization Signal NR: New Radio, Neighbour Relation; New Radio, Neighbour Relation NRF: NF Repository Function NRS: Narrowband Reference Signal NS: Network Service NSA: Non-Standalone operation mode NSD: Network Service Descriptor NSR: Network Service Record NSSAI: Network Slice Selection Assistance Information S-NNSAI: Single-NSSAI; Single NSSAI NSSF: Network Slice Selection Function NW: Network; Network NWUS: Narrowband wake-up signal, Narrowband WUS; Narrowband wake-up signal, Narrowband WUS NZP: Non-Zero Power O&M: Operation and Maintenance ODU2: Optical channel Data Unit - type 2 OFDM: Orthogonal Frequency Division Multiplexing OFDMA: Orthogonal Frequency Division Multiple Access OOB: Out-of-band; outside the band. OOS: Out of Sync; synchronization failed OPEX:OPErating Expense;Operating Expense OSI: Other System Information OSS: Operations Support System OTA: over-the-air PAPR: Peak-to-Average Power Ratio PAR: Peak to Average Ratio PBCH: Physical Broadcast Channel PC: Power Control, Personal Computer; Power Control, Personal Computer PCC: Primary Component Carrier, Primary CC P-CSCF: Proxy CSCF; Proxy CSCF PCell: Primary Cell PCI: Physical Cell ID, Physical Cell Identity; Physical Cell ID, Physical Cell Identifier PCEF: Policy and Charging Enforcement Function PCF: Policy Control Function PCRF: Policy Control and Charging Rules Function PDCP: Packet Data Convergence Protocol, Packet Data Convergence Protocol layer PDCCH: Physical Downlink Control Channel PDCP: Packet Data Convergence Protocol PDN: Packet Data Network, Public Data Network; Packet Data Network, Public Data Network PDSCH: Physical Downlink Shared Channel PDU: Protocol Data Unit PEI: Permanent Equipment Identifiers PFD: Packet Flow Description P-GW: PDN Gateway; PDN Gateway PHICH: Physical hybrid-ARQ indicator channel; Physical hybrid ARQ indicator channel PHY: Physical layer PLMN: Public Land Mobile Network PIN: Personal Identification Number PM: Performance Measurement; Performance Scale PMI: Precoding Matrix Indicator PNF: Physical Network Function PNFD: Physical Network Function Descriptor PNFR: Physical Network Function Record POC: PTT over Cellular; PTT over Cellular PP, PTP: Point-to-Point PPP: Point-to-Point Protocol PRACH:Physical RACH;Physical RACH PRB: Physical resource block; PRG: Physical Resource block group; Physical Resource Block Group ProSe: Proximity Services, Proximity-Based Service; Proxy Service, Proxy-Based Service PRS: Positioning Reference Signal PRR: Packet Reception Radio PS: Packet Services PSBCH: Physical Sidelink Broadcast Channel PSDCH: Physical Sidelink Downlink Channel PSCCH: Physical Sidelink Control Channel PSSCH: Physical Sidelink Shared Channel PSCell: Primary SCell; Primary SCell PSS: Primary Synchronization Signal PSTN: Public Switched Telephone Network PT-RS: Phase-tracking reference signal; movement tracking reference signal PTT: Push-to-Talk PUCCH: Physical Uplink Control Channel PUSCH: Physical Uplink Shared Channel QAM: Quadrature Amplitude Modulation QCI: QoS class of identifier; QoS class of indicator QCL: Quasi co-location; pseudo-co-location QFI: QoS Flow ID, QoS Flow Identifier; QoS Flow ID, QoS Flow Identifier QoS: Quality of Service; Service quality QPSK: Quadrature (Quaternary) Phase Shift Keying; Quadrature phase shift keying QZSS: Quasi-Zenith Satellite System; Quasi-zenith satellite system RA-RNTI: Random Access RNTI; Random access RNTI RAB: Radio Access Bearer, Random Access Burst; Radio access bearer, random access burst RACH: Random Access Channel; Random access channel RADIUS: Remote Authentication Dial In User Service; Remote authentication dial in user service RAN: Radio Access Network; Radio access network RAND: RANDom number (used for authentication); (Used for authentication) random number RAR: Random Access Response; Random access response RAT: Radio Access Technology; Radio access technology RAU: Routing Area Update; Routing area update RB: Resource block, Radio Bearer; Resource block, radio bearer RBG: Resource block group; Resource block group REG: Resource Element Group; Resource element group Rel: Release; Release REQ: REQuest; Request RF: Radio Frequency; Radio frequency RI: Rank Indicator RIV: Resource indicator Value RL: Radio Link; Wireless Link RLC: Radio Link Control, Radio Link Control layer; Wireless link control, Wireless link control layer RLC AM: RLC Acknowledged Mode; RLC Confirmation Mode RLC UM: RLC Unacknowledged Mode; RLC Unconfirmed Mode RLF: Radio Link Failure; Wireless Link Failure RLM: Radio Link Monitoring RLM-RS: Reference Signal for RLM; Reference signal for RLM RM: Registration Management RMC: Reference Measurement Channel RMSI: Remaining MSI, Remaining Minimum System Information RN: Relay Node; relay node RNC: Radio Network Controller; Wireless Network Controller RNL: Radio Network Layer RNTI: Radio Network Temporary Identifier ROHC: Robust Header Compression RRC: Radio Resource Control, Radio Resource Control Layer; Radio Resource Control, Radio Resource Control Layer RRM: Radio Resource Management RS: Reference Signal RSRP: Reference Signal Received Power RSRQ: Reference Signal Received Quality RSSI: Received Signal Strength Indicator RSU: Road Side Unit RSTD: Reference Signal Time Difference RTP: Real Time Protocol RTS: Ready-To-Send RTT: Round Trip Time Rx: Reception, Receiving, Receiver; reception, receiver S1AP: S1 Application Protocol; S1 Application Protocol S1-MME: S1 for the control plane; S1 for the control plane S1-U: S1 for the user plane; S1 for the user plane S-CSCF: Serving CSCF; Serving CSCF S-GW: Serving Gateway S-RNTI: SRNC Radio Network Temporary Identity; SYNC Radio Network Temporary Identifier S-TMSI: SAE Temporary Mobile Station Identifier SA: Standalone operation mode SAE: System Architecture Evolution SAP: Service Access Point SAPD: Service Access Point Descriptor SAPI: Service Access Point Identifier SCC: Secondary Component Carrier, Secondary CC; Secondary Component Carrier, Secondary CC SCell: Secondary Cell; Secondary Cell SCEF: Service Capability Exposure Function SC-FDMA: Single Carrier Frequency Division Multiple Access SCG: Secondary Cell Group SCM: Security Context Management; Secondary Context Management SCS: Subcarrier Spacing SCTP: Stream Control Transmission Protocol SDAP: Service Data Adaptation Protocol, Service Data Adaptation Protocol layer; SDL: Supplementary Downlink SDNF: Structured Data Storage Network Function; Structured Data Storage Network Function SDP: Session Description Protocol; Session Description Protocol SDSF: Structured Data Storage Function; Structured Data Storage Function SDT: Small Data Transmission; Small Data Transmission SDU: Service Data Unit; Service Data Unit SEAF: Security Anchor Function; Security Anchor Function SeNB: secondary eNB; secondary eNB SEPP: Security Edge Protection Proxy; Security Edge Protection Proxy SFI: Slot format indication; Slot format indication SFTD: Space-Frequency Time Diversity, SFN and frame timing difference; Space-Frequency Time Diversity, SFN and frame timing difference SFN: System Frame Number; System Frame Number SgNB: Secondary gNB; Secondary gNB SGSN: Serving GPRS Support Node; Serving GPRS Support Node S-GW: Serving Gateway ; Serving Gateway SI: System Information; System Information SI-RNTI: System Information RNTI; System Information RNTI SIB: System Information Block; System Information Block SIM: Subscriber Identity Module SIP: Session Initiated Protocol SiP: System in Package SL: Sidelink; Sidelink SLA: Service Level Agreement SM: Session Management SMF: Session Management Function SMS: Short Message Service SMSF: SMS Function; SMS function SMTC: SSB-based Measurement Timing Configuration SN: Secondary Node, Sequence Number SoC: System on Chip SON: Self-Organizing Network SpCell: Special Cell SP-CSI-RNTI: Semi-Persistent CSI RNTI SPS: Semi-Persistent Scheduling SQN: Sequence number SR: Scheduling Request SRB: Signaling Radio Bearer SRS: Sounding Reference Signal SS:Synchronization Signal SSB: Synchronization Signal Block SSID: Service Set Identifier SS / PBCH Block; SS / PBCH Block SSBRI: SS / PBCH Block Resource Indicator, Synchronization Signal Block Resource Indicator SSC: Session and Service Continuity SS-RSRP: Synchronization Signal based Reference Signal Received Power SS-RSRQ: Synchronization Signal based Reference Signal Received Quality SS-SINR: Synchronization Signal based Signal to Noise and Interference Ratio SSS: Secondary Synchronization Signal SSSG: Search Space Set Group SSSIF: Search Space Set Indicator SST: Slice / Service Types SU-MIMO: Single User MIMO SUL: Supplementary Uplink TA: Timing Advance, Tracking Area TAC: Tracking Area Code TAG: Timing Advance Group TAI: Tracking Area Identity TAU: Tracking Area Update TB: Transport Block TBS: Transport Block Size TBD: To Be Unified; Under Review TCI: Transmission Configuration Indicator TCP: Transmission Communication Protocol TDD: Time Division Duplex TDM:Time Division Multiplexing TDMA: Time Division Multiple Access TE: Terminal Equipment; terminal device TEID: Tunnel End Point Identifier TFT: Traffic Flow Template TMSI: Temporary Mobile Subscriber Identity TNL: Transport Network Layer TPC: Transmit Power Control TPMI: Transmitted Precoding Matrix Indicator TR: Technical Report; Technical Report TRP, TRxP: Transmission Reception Point TRS: Tracking Reference Signal TRx: Transceiver; Walkie-talkie TS: Technical Specifications, Technical Standard; Technical specifications, technical standards TTI: Transmission Time Interval Tx: Transmission, Transmitting, Transmitter; transmission, transmitter U-RNTI: UTRAN Radio Network Temporary Identity; UTRAN Radio Network Temporary Identifier UART: Universal Asynchronous Receiver and Transmitter UCI: Uplink Control Information UE: User Equipment; User Devices UDM: Unified Data Management UDP: User Datagram Protocol UDSF: Unstructured Data Storage Network Function UICC: Universal Integrated Circuit Card UL:Uplink; Uplink UM: Unacknowledged Mode; Unconfirmed Mode UML: Unified Modeling Language UMTS: Universal Mobile Telecommunications System UP: User Plane; User Plane UPF: User Plane Function URI: Uniform Resource Identifier URL:Uniform Resource Locator URLLC: Ultra-Reliable and Low Latency USB: Universal Serial Bus USIM: Universal Subscriber Identity Module USS:UE-specific search space;UE-specific search space UTRA: UMTS Terrestrial Radio Access; UMTS Terrestrial Radio Access UTRAN: Universal Terrestrial Radio Access Network UwPTS: Uplink Pilot Time Slot: Uplink Pilot Time Slot V2I: Vehicle-to-Infrastruction V2P: Vehicle-to-Pedestrian V2V: Vehicle-to-Vehicle; vehicle-to-vehicle V2X: Vehicle-to-everything; Vehicle-to-everything VIM: Virtualized Infrastructure Manager VL: Virtual Link VLAN: Virtual LAN, Virtual Local Area Network; virtual LAN, virtual local area network VM: Virtual Machine VNF: Virtualized Network Function VNFFG: VNF Forwarding Graph; VNF Transfer Graph VNFFGD: VNF Forwarding Graph Descriptor; VNF forwarding graph descriptor VNFM: VNF Manager; VNF Manager VoIP: Voice-over-IP, Voice-over-Internet Protocol VPLMN: Visited Public Land Mobile Network VPN: Virtual Private Network VRB: Virtual Resource Block WiMAX: Worldwide Interoperability for Microwave Access WLAN: Wireless Local Area Network WMAN: Wireless Metropolitan Area Network WPAN: Wireless Personal Area Network X2-C: X2-Control plane; X2 control plane X2-U: X2-User plane; X2 User Plane XML: eXtensible Markup Language XRES: Expected User Response; Extensible User Response XOR:eXclusive OR;exclusive OR ZC: Zadoff-Chu; Zadoffchu ZP: Zero Power

[0101] Technical terms For the purposes of this specification, the following terms and definitions are applicable to the examples and embodiments described herein.

[0102] As used herein, the term “circuit” refers to, is part of, or includes hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) and / or memory (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), composite PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), and digital signal processors (DSPs), configured to provide the functions described. In some embodiments, a circuit may run one or more software or firmware programs to provide at least some of the functions described. The term “circuit” may also refer to a combination of one or more hardware elements having the program code (or a combination of circuits used in an electrical or electronic system) that is used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0103] As used herein, the term “processor circuit” refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. A processing circuit may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term “processor circuit” may also refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single-core processors, dual-core processors, triple-core processors, quad-core processors, and / or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, and / or functional processes. A processing circuit may include more hardware accelerators, such as microprocessors and programmable processing devices. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuit” and / or “baseband circuit” may be considered synonymous with “processor circuit,” and may also be referred to as “processor circuit.”

[0104] As used herein, the term "interface circuit" refers to, a part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can also refer to one or more hardware interfaces, such as a bus, I / O interface, peripheral interface, network interface card, and / or similar.

[0105] As used herein, the terms “User Equipment” or “UE” refer to a device with wireless communication capabilities and may refer to a remote user of network resources within a communication network. The terms “User Equipment” or “UE” may be considered synonymous with, and may be referred to as, a 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. Furthermore, the terms “User Equipment” or “UE” may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0106] As used herein, the term “Network Element” refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless network services. The term “Network Element” may be considered synonymous with, and / or referred to as, networked computers, networking hardware, network equipment, network nodes, routers, switches, hubs, bridges, wireless network controllers, RAN devices, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, and / or similar entities.

[0107] As used herein, the term “computer system” refers to any type of interconnected electronic devices, computer devices, or components thereof. Furthermore, the terms “computer system” and / or “system” may refer to various components of a computer that are interconnected in a communicative manner. Furthermore, the terms “computer system” and / or “system” may refer to multiple computer devices and / or multiple computing systems that are interconnected in a communicative manner and configured to share computing and / or networking resources.

[0108] As used herein, terms such as "appliance" and "computer appliance" refer to a computer device or computer system that has program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image implemented by a hypervisor-based device that virtualizes or emulates a computer appliance, or otherwise is dedicated to providing specific computing resources.

[0109] As used herein, the term “resource” refers to physical or virtual devices, physical or virtual components within a computing environment, and / or physical or virtual components within a particular device, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operation, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, workload units and / or similar entities. “Hardware resources” may refer to computing, storage, and / or network resources provided by physical hardware elements. “Virtualized resources” may refer to computing, storage, and / or network resources provided to applications, devices, systems, etc., by a virtual infrastructure. The terms “network resources” or “communication resources” may refer to resources accessible by computer devices / systems via a communication network. The term “system resources” may refer to any kind of shared entity providing services, and may include computing and / or network resources. System resources may be thought of as a set of coherent functions, network data objects, or services accessible via a server, in which case such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0110] As used herein, the term “channel” refers to any tangible or intangible transmission medium used to communicate data or data streams. The term “channel” may be synonymous and / or equivalent to “communication channel,” “data communication channel,” “transmit channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radio frequency carrier,” and / or any other similar term that indicates the path or medium through which data is communicated. Furthermore, as used herein, the term “link” refers to the connection between two devices via the RAT for the purpose of sending and receiving information.

[0111] The terms "instantiate" and "instantiate" used in this context refer to the creation of an instance. "Instance" may also refer to the specific occurrence of an object that may occur, for example, during the execution of program code.

[0112] The terms “coupled” and “communicatively coupled” are used in this context, along with their derivatives. The term “coupled” may mean that two or more elements are in direct physical or electrical contact with each other, that two or more elements are indirectly in contact with each other but still cooperate or interact with each other, and / or that one or more other elements are coupled or connected between the elements referred to as coupled. The term “directly coupled” may mean that two or more elements are in direct contact with each other. The term “communicatively coupled” may mean that two or more elements are able to come into contact with each other by means of communication, including via wires or other interconnections, via wireless communication channels or links, and / or similar.

[0113] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains such contents.

[0114] The term "SMTC" refers to the SSB-based measurement timing setting configured by SSB-MeasurementTimingConfiguration.

[0115] The term "SSB" refers to the SS / PBCH block.

[0116] The term "primary cell" refers to the MCG cell operating at the primary frequency from which the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

[0117] The term "primary SCG cell" refers to the SCG cell that the UE performs random access to when a reconfiguration is performed by a synchronous procedure regarding DC operation.

[0118] The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell in relation to a UE configured using CA.

[0119] The term "secondary cell group" refers to a subset of serving cells that includes a PSCell and zero or more secondary cells for UEs configured using a DC.

[0120] The term "serving cell" refers to the primary cell for a UE that is in the RRC_CONNECTED state and is not configured in the CA / DC. There is only one serving cell that has a primary cell.

[0121] The term "serving cell" or "multiple serving cells" refers to a set of cells that includes a special cell for a UE in the RRC_CONNECTED state, configured using CA / , and all secondary cells.

[0122] The term "special cell" refers to a PCell in an MCG or a PSCell in an SCG for DC operation; otherwise, the term "special cell" refers to a Pcell.

Claims

1. A memory for storing configuration information for uplink transmission by user equipment (UE); and A processing circuit coupled to the memory; An apparatus including the processing circuit: A device that retrieves the configuration information from the memory, encodes a message containing the configuration information for transmission to the UE, wherein the configuration information includes an instruction that default beam operation is enabled for the uplink transmission, and an instruction that iteration of the physical downlink control channel (PDCCH) is enabled with respect to the operation of the multi-transmit / receive point (TRP).

2. The apparatus according to claim 1, wherein the configuration information in the message is included in the downlink control information (DCI).

3. The apparatus according to claim 1, wherein the uplink transmission is a physical uplink shared channel (PUSCH) transmission, a physical uplink control channel (PUCCH) transmission, or a sounding reference signal (SRS) transmission.

4. In the apparatus according to claim 3, the uplink transmission is a PUSCH transmission or PUCCH transmission with repetition enabled or disabled, and the default spatial relation or path loss reference signal for the uplink transmission is: The state of the control resource set (CORESET) or the transmit configuration indicator (TCI) of the search space that carries downlink control information (DCI); or Multiple TCI states associated with physical downlink shared channel (PDSCH) transmission; A device associated with something.

5. The apparatus according to claim 3, wherein the uplink transmission is a PUSCH transmission or PUCCH transmission with repetition disabled, and the default spatial relation or path loss reference signal for the uplink transmission is associated with the TCI state of the CORESET or search space having the lowest identifier among a plurality of CORESETs or search spaces.

6. In the apparatus according to claim 3, the uplink transmission is an SRS transmission, one or more SRS resource sets for a single TRP are triggered by a common DCI, a default beam for the SRS is enabled, and the default spatial relation or path loss reference signal for the SRS transmission is: The TCI state of the CORESET or search space that carries the triggering DCI; A TCI state among multiple TCI states associated with PDSCH; or The TCI state of the CORESET or search space with the lowest identifier among multiple CORESETs or search spaces; A device associated with something.

7. An apparatus according to any one of claims 1 to 6, wherein the apparatus includes a next-generation NodeB (gNB) or a portion thereof.

8. One or more computer-readable storage media for storing instructions, wherein, when the instructions are executed by one or more processors, they are sent to a next-generation NodeB (gNB): The system determines the configuration information for uplink transmission by the user equipment (UE) and encodes a message containing the said configuration information for transmission to the UE; The configuration information includes an instruction that default beam operation is enabled for the uplink transmission, and an instruction that physical downlink control channel (PDCCH) iterations are enabled with respect to the operation of the multiple transmit / receive point (TRP); The configuration information in the aforementioned message is a storage medium included in the downlink control information (DCI).

9. A storage medium according to claim 8, wherein the uplink transmission is a physical uplink shared channel (PUSCH) transmission, a physical uplink controlled channel (PUCCH) transmission, or a sounding reference signal (SRS) transmission.

10. In one or more computer-readable storage media according to claim 9, The uplink transmission is a PUSCH transmission or PUCCH transmission with repetition enabled or disabled, and the default spatial relationship or path loss reference signal for the uplink transmission is: The state of the control resource set (CORESET) or the transmit configuration indicator (TCI) of the search space that carries downlink control information (DCI); or Multiple TCI states associated with physical downlink shared channel (PDSCH) transmission; A storage medium associated with something.

11. A storage medium according to one or more computer-readable storage mediums according to claim 9, wherein the uplink transmission is a PUSCH transmission or PUCCH transmission with repetition disabled, and the default spatial relation or path loss reference signal for the uplink transmission is associated with the TCI state of the CORESET or search space having the lowest identifier among a plurality of CORESETs or search spaces.

12. In one or more computer-readable storage media according to claim 9, The uplink transmission is an SRS transmission, one or more SRS resource sets for a single TRP are triggered by a common DCI, the default beam for the SRS is enabled, and the default spatial relation or path loss reference signal for the SRS transmission is: The TCI state of the CORESET or search space that carries the triggering DCI; A TCI state among multiple TCI states associated with PDSCH; or The TCI state of the CORESET or search space with the lowest identifier among multiple CORESETs or search spaces; A storage medium associated with something.

13. One or more computer-readable storage media for storing instructions, wherein, when the instructions are executed by one or more processors, they are sent to the user device (UE): The UE receives a configuration message from the next-generation NodeB (gNB) containing configuration information for uplink transmission, and performs the encoding of the uplink message to be transmitted based on the configuration information; A storage medium in which the configuration information includes an instruction that default beam operation is enabled for the uplink transmission, and an instruction that physical downlink control channel (PDCCH) iterations are enabled with respect to the operation of a multiple transmit / receive point (TRP).

14. A storage medium according to claim 13, wherein the uplink transmission is a physical uplink shared channel (PUSCH) transmission, a physical uplink controlled channel (PUCCH) transmission, or a sounding reference signal (SRS) transmission.

15. In one or more computer-readable storage media according to claim 14, The uplink transmission is a PUSCH transmission or PUCCH transmission with repetition enabled or disabled, and the default spatial relationship or path loss reference signal for the uplink transmission is: The state of the control resource set (CORESET) or the transmit configuration indicator (TCI) of the search space that carries downlink control information (DCI); or Multiple TCI states associated with physical downlink shared channel (PDSCH) transmission; A storage medium associated with something.

16. A storage medium according to one or more computer-readable storage mediums according to claim 14, wherein the uplink transmission is a PUSCH transmission or PUCCH transmission with repetition disabled, and the default spatial relation or path loss reference signal for the uplink transmission is associated with the TCI state of the CORESET or search space having the lowest identifier among a plurality of CORESETs or search spaces.

17. In one or more computer-readable storage media according to claim 14, The uplink transmission is an SRS transmission, one or more SRS resource sets for a single TRP are triggered by a common DCI, the default beam for the SRS is enabled, and the default spatial relation or path loss reference signal for the SRS transmission is: The TCI state of the CORESET or search space that carries the triggering DCI; A TCI state among multiple TCI states associated with PDSCH; or The TCI state of the CORESET or search space with the lowest identifier among multiple CORESETs or search spaces; A storage medium associated with something.

18. A storage medium according to one or more computer-readable storage mediums according to any one of claims 13-17, wherein the configuration information in the configuration message is contained in downlink control information (DCI).

Images