Full-power transmission signaling for coherent user equipment

Abstract

The implementation scheme relates to techniques for achieving full-power transmission in a user equipment (UE). The UE implementation scheme includes: an antenna array comprising a plurality of antenna elements; and a processor configured to: cause the UE to establish a communication connection with a network entity; cause the UE to transmit a coherence capability indicator and a power transmission mode capability indicator to the network entity; cause the UE to receive instructions from the network entity for operating in a specified coherence mode and a specified power transmission mode; and configure the UE to operate in the specified coherence mode and the specified power transmission mode.

Description

Technical Field

[0001] Various implementation schemes can typically involve the field of wireless communications, including technologies for implementing full-power transmission signaling for coherent user equipment. Background Technology

[0002] This section is intended to introduce the reader to various aspects of the art that may be related to the aspects of this disclosure, which are described below and / or protected by the claims. This discussion is intended to help provide the reader with background information to better understand the aspects of this disclosure. Therefore, it should be understood that these statements made in this section are not intended to acknowledge prior art.

[0003] Various electronic devices use wireless communication systems to exchange data and / or form communication networks. For example, laptops, mobile phones, and other similar devices may have wireless network adapters that can connect to cellular networks, wireless Ethernet networks, Bluetooth networks, etc. In some devices, the wireless communication system may employ a multiple-input multiple-output (MIMO) antenna setup, which may include discrete antenna arrays, to access radio frequency (RF) channels. Agile management of antennas can facilitate efficient signal transmission and power utilization. Summary of the Invention

[0004] The embodiments described herein provide a user equipment (UE) including: an antenna array including a plurality of antenna elements; and a processor configured to: enable the UE to establish a communication connection with a network entity, enable the UE to transmit a coherence capability indicator and a power transmission mode capability indicator to the network entity, enable the UE to receive instructions from the network entity for operating in a specified coherence mode and a specified power transmission mode, and configure the UE to operate in the specified coherence mode and the specified power transmission mode.

[0005] Other embodiments described herein provide a computer-implemented method comprising: causing a UE to establish a communication connection with a network entity; causing the UE to transmit to the network entity a coherence capability indicator and a power transmission mode capability indicator of the UE; causing the UE to receive from the network entity instructions for operating in a specified coherence mode and a specified power transmission mode; and configuring the UE to operate in the specified coherence mode and the specified power transmission mode.

[0006] Other embodiments described herein provide a non-transitory computer-readable medium including instructions that, when executed by a processor, configure the processor to: cause a UE to establish a communication connection with a network entity; cause the UE to transmit a coherence capability indicator and a power transmission mode capability indicator of the UE to the network entity; cause the UE to receive instructions from the network entity for operating in a specified coherence mode and a specified power transmission mode; and configure the UE to operate in the specified coherence mode and the specified power transmission mode.

[0007] In some examples, the coherence capability indicator indicates that the UE can be configured to operate in at least one of incoherent mode, partially coherent mode, or fully coherent mode. Furthermore, in some examples, the power transmission mode capability indicator includes at least one of the following: a first mode indicating that all Transport Precoding Matrix Indicators (TPMIs) can operate at full power; a second mode indicating one or more coherent TPMIs to be added to a subset of the codebook supported by the UE; or a third mode including a list of TPMIs that can operate at full power, and the power transmission mode capability indicator includes an SRS enhancement indicator.

[0008] In some examples, the instructions for operating in a specified coherence mode include at least one codebook subset identifier. Furthermore, the instructions for operating in the specified coherence mode may identify a specific TPMI. In some examples, the processor is used to select that specific TPMI. Attached Figure Description

[0009] A detailed description is provided with reference to the accompanying drawings.

[0010] Figure 1 These are high-level schematic block diagrams illustrating various components in a 3GPP NR (e.g., 5G) network environment, based on various examples discussed herein, which can be used to implement full-power transmission signaling for coherent user equipment in a communication network.

[0011] Figure 2 This is a schematic diagram of the antenna array according to the implementation plan.

[0012] Figure 3 This is a schematic diagram of an antenna array according to an implementation plan, which can be used in a specific implementation of full-power transmission signaling for coherent user equipment.

[0013] Figure 4 This is a schematic diagram of the operation in the specific implementation method of full-power transmission signaling for coherent user equipment according to the implementation plan.

[0014] Figure 5This is a schematic diagram of a network system according to the implementation plan, which can be used in a specific implementation of full-power transmission signaling for coherent user equipment.

[0015] Figure 6 This is a schematic diagram of the system according to the implementation plan, which can be used in the specific implementation of full-power transmission signaling for coherent user equipment.

[0016] Figure 7 This is a schematic diagram of the system according to the implementation plan, which can be used in the specific implementation of full-power transmission signaling for coherent user equipment.

[0017] Figure 8 This is a schematic diagram of the infrastructure equipment according to the implementation plan, which can be used in the specific implementation of full-power transmission signaling for coherent user equipment.

[0018] Figure 9 This is a schematic diagram of a platform according to the implementation plan, which can be used in the specific implementation of full-power transmission signaling for coherent user equipment.

[0019] Figure 10 This is a schematic diagram of a baseband circuit according to an implementation plan, which can be used in a specific implementation of full-power transmission signaling for coherent user equipment.

[0020] Figure 11 This is a schematic diagram of various protocol functions according to the implementation plan, which can be used in the specific implementation of full-power transmission signaling for coherent user equipment.

[0021] Figure 12 This is a schematic diagram of a component capable of reading instructions from a machine-readable or computer-readable medium according to an implementation scheme, which can be used in a specific implementation of full-power transmission signaling for coherent user equipment. Detailed Implementation

[0022] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0023] Furthermore, various means may be used to implement the aspects of the examples, such as integrated semiconductor circuitry (“hardware”), computer-readable instructions organized into one or more programs (“software”), or some combination of hardware and software. For the purposes of this disclosure, reference to “logic” shall mean hardware, software, or some combination thereof.

[0024] Throughout this specification, the phrase "an embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. Therefore, the phrases "in one embodiment" or "in an embodiment" appearing throughout this specification do not necessarily refer to the same embodiment. Furthermore, a particular feature, structure, or characteristic may be combined in any suitable manner in one or more embodiments. Additionally, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" should not be construed as preferred or superior to other embodiments.

[0025] Various operations can be described as a series of discrete operations in a way that best facilitates understanding of the claimed subject matter. However, the order in which they are described should not be construed as implying that these operations necessarily depend on a specific order. Specifically, these operations do not necessarily need to be performed in the order presented. The operations may be performed in a different order than described in the embodiment. In additional embodiments, various additional operations may be performed and / or the operations described may be omitted.

[0026] Please refer to the following reference. Figures 1 to 10 The network architecture, devices, and methods described are further detailed and technically specific. Figure 1 This is a high-level schematic block diagram of components in a 3GPP NR (e.g., 5G) network environment 100, based on various examples discussed herein, which can be used to implement cooperative IP packet filtering in a communication network.

[0027] refer to Figure 1In some examples, network 100 includes one or more Access and Mobility Management Function / User Plane Function (AMF / UMF) devices 110A, 110B, one or more gNBs 120A, 120B, and one or more ng-eNBs 120C, 120D. AMF / UFP devices 110A, 110B are communicatively coupled to gNBs 120A, 120B and ng-eNBs 120C, 120D via ng interfaces. gNBs 120A, 120B and ng-eNBs 120C, 120D are communicatively coupled to each other via Xn interfaces. One or more User Equipment (UE) devices 130A, 130B are capable of establishing communication connections with one or more gNBs 120A, 120B or ng-eNBs 120C, 120D. A detailed description of the wireless network and UEs is provided below.

[0028] In some examples, a wireless network 100 can be implemented by establishing radio frequency (RF) connections between electronic devices, which may include or be communicatively coupled to one or more cellular networks (e.g., 4G standards such as LTE or Long Term Evolution, 5G standards such as New Radio or 5G NR) and / or connectivity networks (e.g., IEEE 802.3 or WiFi, Bluetooth). To establish the wireless RF connection, UEs 130A and 130B may include an RF communication system that may include transmit and receive circuitry coupled to an antenna array comprising one or more antennas. This circuitry may include a transceiver module capable of performing encoding / decoding and modulation / demodulation tasks, as well as digital-to-analog and analog-to-digital conversion. The transceiver module may be coupled to the antennas via a front-end module (FEM) or an RF header that may provide filtering and / or power amplification capabilities to the RF communication system. The RF header circuitry may be coupled to the antenna array. The transceiver circuitry and / or the RF header circuitry may generate RF signals to drive the antenna array and / or decode signals received by the antenna array. Examples of UEs are discussed in more detail below.

[0029] Figure 2 This is a schematic diagram of the antenna array according to the implementation plan. (Reference) Figure 2 In some examples, antenna array 210 may include incoherent antennas 212 and 214. In this example, the UE including antenna array 210 cannot maintain phase coherence between the first antenna (antenna 212) and the second antenna (antenna 214). Antennas 212 and 214 may have different precoder values, such as Figure 2 As shown. For example, antenna 212 can be associated with a pre-encoder value of 1 / √2, while antenna 214 can be associated with a pre-encoder value of 0.

[0030] Figure 3This is a schematic diagram of antenna array 220 according to an implementation scheme, which can be used in a specific implementation for full-power transmission signaling for coherent user equipment. (Reference) Figure 3 In some examples, antenna array 220 may include a first group of antennas 230, which includes coherent antennas 232 and 234. Therefore, antennas 232 and 234 are able to maintain a relative phase difference with each other over time. Similarly, a second group of antennas 240 may include coherent antennas 242 and 244. Therefore, antennas 242 and 244 are able to maintain a relative phase difference with each other over time. However, the first group of coherent antennas 230 and the second group of coherent antennas 240 are incoherent. Therefore, an electronic device including antenna array 220 cannot maintain phase coherence between the first group of antennas 230 and the second group of antennas 240. For example, phase coherence between antenna 234 and antennas 242 or 244 cannot be maintained. In other words, a wireless communication device including antenna array 220 can maintain phase coherence between the antennas included in each of the two antenna groups (e.g., the first antenna group 230 and the second antenna group 232), but cannot maintain phase coherence between the two antenna groups. Therefore, the wireless communication device can be described as capable of achieving partial coherence between the antenna ports in the antenna array 220, or as having partially coherent antennas. Incoherent antenna groups can be associated with different precoder values, such as... Figure 3 As shown. For example, antennas 232 and 234 in the first coherence group 230 can be associated with a pre-encoder value of 1 / 2, while antennas 242 and 244 in the second coherence group 240 can be associated with a pre-encoder value of 0. Figure 2 and Figure 3 The number of antennas shown is an example. In practice, wireless communication devices can include any number of coherent antenna groups that are incoherent with each other. Furthermore, each coherent group can include any number of coherent antennas.

[0031] The topics described herein relate to power management of User Equipment (UE), and in some examples, to techniques for enabling UEs to operate in a coherent state with full-power uplink (UL) transmission. In some examples of existing New Radio (NR) standards (e.g., Release 15), not all TPMIs using all ports cannot support full-power transmission because the maximum transmission power is scaled by the non-zero / maximum number of ports the UE can support. In other examples (e.g., Release 16), incoherent / partially coherent UEs conditionally support full-power transmission. The Release 16 solution includes two modes. In the first mode (referred to herein as Mode 1), a new TPMI is added to a new CodebookSubset with an existing Sounding Reference Signal (SRS) configuration. In the second mode (referred to herein as Mode 2), the existing CodebookSubset is used, but the SRS resource set is allowed to include SRS resources with different numbers of ports, and the UE is allowed to indicate TPMIs supporting full-power UL Tx. Mode 1 is a simple solution but only supports a limited number of TPMIs and a limited selection of UE antenna virtualization. Mode 2 is a more sophisticated solution that supports more TPMIs and antenna virtualization; however, the instructions for supporting full-power TPMIs are complex. In some examples, the network can decide how to configure SRS resources.

[0032] In the first set of examples, the UE can report its uplink coherence-related capabilities in the UE capability report message (e.g., pusch-TransCoherence = {nonCoherent, partialCoherent, fullCoherent}). When the UE reports that it supports coherent uplink transmission (e.g., pusch-TransCoherence = fullCoherent), the NW can configure the UE to operate in coherent UL in PUSCH-Config (e.g., codebookSubset = fullyAndPartialAndNonCoherent).

[0033] Figure 4 This is a schematic diagram illustrating operation in a specific implementation of a method for full-power transmission signaling for coherent user equipment according to the implementation scheme. In some examples, this operation can be implemented between the UE (e.g., UE 130A, 130B) and network elements (e.g., gNB120A, 120B or ng-eNB 120C, 120D). Figure 4The operation described herein enables the UE to report its uplink (UL) coherence-related capabilities to the network element. The network element can then utilize the UE's coherence-related capabilities to generate instructions for configuring the UE to operate in a specified coherence mode and a specified power transmission mode. The network element can transmit these instructions to the UE, which can then configure its transmitter components to operate according to these instructions.

[0034] refer to Figure 4 At operations 410 and 415, the UE and the network element establish communication connections, respectively. At operation 420, the UE transmits a coherence capability indicator and a power transmission mode indicator to the network element. In some examples, the UE includes an antenna array capable of operating in coherent mode, such as a set of antennas 230 or a set of antennas 240 in antenna array 220, and the UE can transmit a coherence capability indicator indicating that it can support full-power transmission. As a result, the NW can configure the UE for coherent codebook-based PUSCH operation.

[0035] At operation 425, the network element receives a coherence capability indicator and a power transmission mode indicator transmitted by the UE, and at operation 430, the network element transmits instructions to the UE for operating in a specified coherence mode and a specified power transmission mode. At operation 435, the UE receives instructions from the network element for operating in the specified coherence mode and the specified power transmission mode. At operation 440, the UE is configured to operate in the specified coherence mode and the specified power transmission mode based on the instructions received from the network element.

[0036] In some examples, the indicator may include two parts. The first part indicates the maximum number of SRS resources the UE can support in the SRS resource set when the UE is configured to operate in codebook-based PUSCH operation. In some examples, this maximum number can be selected from a set including {1, 2, 4}. The second part indicates whether the UE supports SRS resources with different numbers of ports in the SRS resource set when the UE is configured to operate in codebook-based PUSCH operation. For example, whether the UE can be configured with at least one SRS resource with 4 ports and at least one SRS resource with 2 ports in the same SRS resource set.

[0037] In the first set of examples, one or a subset of the following modes can be indicated as UE capabilities. In mode 0, all TPMIs have a power scaling value of - (1). In mode 2, the UE indicates to the network element a list of TPMIs for which it supports full-power transmission. For TPMIs in the list, the power scaling value is set to - (1). In some examples, the UE may also indicate to the network element that for mode 2, the UE does not support SRS enhancements. In this case, limited by UE capabilities, the UE only supports SRS resources with the same number of ports and a maximum of 1 or 2 SRS resources per SRS resource set.

[0038] In Mode 1, coherent TPMI can be added to a subset of codebooks already supported by the UE. In some examples, when a coherent UE is configured with coherent codebook-based PUSCH operation, the coherent UE does not indicate that it supports UL full-power transmission in Mode 1.

[0039] For a coherent UE, the NW can configure the UE to operate in coherent codebook-based PUSCH operations. In some examples, limited by UE capabilities, the NW can configure the UE to operate in one of three separate modes. In the first mode (mode 0), the power scaling factor (S) is calculated as the ratio of the number of non-zero antenna ports to the maximum number of ports the UE can support. In the second mode, all TPMIs are assigned a power scaling factor (S): - (1). In the third mode (mode 2), the UE instructs the UE to target a list of TPMIs that support full-power transmission, and the TPMIs in the list are assigned a power scaling factor: - (1). In some examples, the network element cannot configure the UE to have more than two SRS resources, and all SRS resources in the same SRS resource set have the same number of ports.

[0040] In some examples, when a network element generates instructions to enable a coherent UE to operate in coherent codebook-based PUSCH operations, the network element cannot configure the UE to operate in full-power mode 1, in which one or more coherent TPMIs can be added to a subset of codebooks already supported by the UE.

[0041] In the second set of examples, a flexible mode 1 capability report is provided. In some examples, the UE can independently report support for mode 1 for degraded configurations (e.g., maximum number of ports). For example, a UE supporting 4 ports can indicate support for mode 1 for 4-port and 2-port SRS configurations. Furthermore, the UE can independently report support for mode 1 for any degraded configuration related to coherence. For example, a coherent UE can indicate support for mode 1 for partially coherent or incoherent UL operation. Similarly, a partially coherent UE can indicate support for mode 1 for partially coherent and incoherent UL operation.

[0042] Mode 1 capability reports can flexibly utilize bitmap designs, such as {4port-partial-coherent, 4port-non-coherent, 2port-non-coherent}. For example, a 1 in the corresponding bit of the bitmap indicates that the UE supports Mode 1 when the UE is configured with the corresponding UL operation.

[0043] In the third set of examples, a flexible Mode 2 capability report is provided. In Mode 2 operation, the UE can indicate the TPMI list that it supports for full-power transmission. Additionally, network elements can configure up to four SRS resources per SRS resource set, and different SRS resources within the same SRS resource set can be configured with different numbers of ports.

[0044] For Mode 2 operation, in some examples, the UE can independently report its capabilities regarding TPMI and SRS resource configuration to network entities. In some examples, a Mode 2-enabled UE can indicate a list of TPMIs that only support full-power transmission but not any SRS resource enhancements. Similarly, a Mode 2-enabled UE can report to network entities any additional TPMIs that only support SRS enhancements and support full-power transmission.

[0045] Regarding TPMI support, the UE can independently report to network elements the following possible capabilities for coverage: (1) when the UE is configured with a two-port non-coherent / coherent, two-bit TPMI bitmap; (2) when the UE is configured with a four-port non-coherent, two-bit TPMI group index; and (3) when the UE is configured with a four-port partially coherent / coherent, four-bit TPMI group index.

[0046] In addition, for each possible UL configuration, the UE can report to the network element: (1) when the UE is configured as two-port noncoherent / coherent; (2) when the UE is configured as four-port noncoherent; and (3) when the UE is configured as four-port partially coherent / coherent.

[0047] The UE can independently indicate any TPMI it does not support for full-power transmission. In some examples, the UE may not report the corresponding capability. In other examples, for two-port incoherent connections, the UE may report (0,0) as a two-bit map. In some examples, the UE may report special code points (e.g., reserved bits) that are not associated with the TPMI list.

[0048] As described above, the Mode 1 capability report can flexibly utilize bitmap design, for example, {4port-partial-coherent, 4port-non-coherent, 2port-non-coherent}. For example, a 1 in the corresponding bit in the bitmap indicates that the UE supports Mode 1 when the UE is configured with the corresponding UL operation.

[0049] In another example, regarding SRS configuration support, a UE in Mode 2 operation can independently report SRS-related capabilities for the following possible uplink configurations: (1) {4port-coherent, 4port-partial-coherent, 4port-non-coherent, 2port-coherent, 2port-non-coherent}; and 2port-coherent and 4port-coherent. In some examples, UEs may not be allowed to report SRS-related capabilities for configured Mode 2 operation.

[0050] For Mode 2 operation, the UE can independently indicate the following SRS-related capabilities regarding SRS configuration for each UL configuration: (1) the maximum number of SRS resources per SRS resource set, i.e., {1,2,4}; (2) whether the UE prefers to have different numbers of SRS ports configured in the same SRS resource set; and (3) at least in the same SRS resource set, if 4-port SRS resources are configured, whether the UE prefers to be configured with 2-port SRS resources.

[0051] In another example, when the UE is configured to operate in codebook-based PUSCH operation within a subset of coherent codebooks, the UE can indicate its full-power mode capability to the network. This capability indication includes at least one or both of the following modes: a first mode indicating that all TPMIs can operate at full power; and a second mode including a list of TPMIs that can operate at full power.

[0052] In another example, when the network configures the UE to operate in codebook-based PUSCH operation using a subset of coherent codebooks, the NW can configure the UE to operate in at least one of the following full-power transmission modes: a first mode that indicates that all TPMIs can operate at full power; or a second mode that includes a list of TPMIs that can operate at full power.

[0053] System and specific implementation

[0054] Figure 5Exemplary architectures of system 500 for networks according to various implementations are shown. The following description is provided for an exemplary system 500 operating in combination with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary implementations are not limited in this respect, and the implementations can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0055] like Figure 5 As shown, system 500 includes UE 501a and UE 501b (collectively referred to as "multiple UEs 501" or "UE 501"). In this example, UE 501 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics devices, mobile phones, smartphones, feature phones, tablet computers, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminal (MDT), electronic engine management system (EEMS), electronic / engine electronic control unit (ECU), electronic / engine electronic control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), connected or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0056] In some implementations, any of the UEs in UE 501 can be an IoT UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communication, sensor networks, or IoT networks. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network. In some implementations of these implementations, UE 501 may be an NB-IoT UE 501. NB-IoT uses a physical layer optimized for extremely low power consumption (e.g., a full-carrier BW of 180 kHz, with subcarrier spacing of 3.75 kHz or 15 kHz) to provide access to network services. Several E-UTRA functions are not used for NB-IoT and do not require support from RAN node 511 and UE 501, which only use NB-IoT. Examples of such E-UTRA functions may include inter-RAT mobility, handover, measurement reporting, common warning functions, GBR, CSG, HeNB support, relay, carrier aggregation, dual connectivity, NAICS, MBMS, real-time services, interference avoidance for intra-device coexistence, RAN-assisted WLAN interworking, sidelink communication / discovery, MDT, emergency calls, CS fallback, self-configuration / self-optimization, etc. For NB-IoT operation, the UE501 operates in DL using 12 subcarriers with a subcarrier BW of 15kHz, and in UL using a single subcarrier with a subcarrier BW of 3.75kHz or 15kHz, or in DL using 3, 6, or 12 subcarriers with a subcarrier BW of 15kHz.

[0057] In various implementations, UE 501 can be an MF UE 501. An MF UE 501 is (uniquely) an LTE-based UE 501 operating in unlicensed spectrum. This unlicensed spectrum is defined in the MF specification provided by the MulteFire Forum and can include, for example, 1.9 GHz (Japan), 3.5 GHz, and 5 GHz. MulteFire is closely aligned with 3GPP standards and built upon elements of the 3GPP specifications for LAA / eLAA, thereby enhancing standard LTE to operate in globally unlicensed spectrum. In some implementations, LBT can be implemented to coexist with other unlicensed spectrum networks, such as WiFi, other LAA networks, etc. In various implementations, some or all of UE 501 can be NB-IoT UE 501s operating according to MF. In such embodiments, these UEs 501 may be referred to as “MF NB-IoT UE 501”; however, unless otherwise stated, the term “NB-IoT UE 501” may refer to “MF UE 501” or “MF and NB-IoT UE 501”. Therefore, the terms “NB-IoT UE 501”, “MF UE 501”, and “MFNB-IoT UE 501” are used interchangeably throughout this disclosure.

[0058] UE 501 can be configured to be communicatively coupled to, for example, RAN 510. In implementations, RAN 510 can be NGRAN or 5G RAN, E-UTRAN, MF RAN, or a legacy RAN such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., can refer to RAN 510 operating in NR or 5G system 500, while the term "E-UTRAN," etc., can refer to RAN 510 operating in LTE or 4G system 500, and the term "MF RAN," etc., can refer to RAN 510 operating in MF system 100. UE 501 utilizes connections (or channels) 503 and 504, each connection including a physical communication interface or layer (discussed in further detail below). Connections 103 and 104 can include several different physical DL channels and several different physical UL channels. As an example, physical DL channels include PDSCH, PMCH, PDCCH, EPDCCH, MPDCCH, R-PDCCH, SPDCCH, PBCH, PCFICH, PHICH, NPBCH, NPDCCH, NPDSCH, and / or any other physical DL channel mentioned herein. Similarly, physical UL channels include PRACH, PUSCH, PUCCH, SPUCCH, NPRACH, NPUSCH, and / or any other physical UL channel mentioned herein.

[0059] In this example, connections 503 and 504 are shown as air interfaces for communication coupling and can be consistent with cellular communication protocols such as GSM, CDMA, PTT, POC, UMTS, 3GPP LTE, 5G, NR, and / or any other communication protocols discussed herein. In an implementation, UE 501 can directly exchange communication data via ProSe interface 505. ProSe interface 505 may alternatively be referred to as SL interface 505 and may include one or more physical and / or logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0060] UE 501b is shown configured to access AP 506 (also referred to as "WLAN node 506", "WLAN 506", "WLAN terminal 506", "WT 506", etc.) via connection 507. Connection 507 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 506 will include Wireless Fibre. Router. In this example, AP 506 is shown connected to the Internet but not to the core network of the wireless system (described in further detail below). In various implementations, UE 501b, RAN 510, and AP 506 can be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 501b in an RRC_CONNECTED state, configured by RAN nodes 511a-b to utilize the radio resources of LTE and WLAN. LWIP operation may involve UE 501b using WLAN radio resources (e.g., connection 507) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) transmitted through connection 507. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header to protect the original header of the IP packet.

[0061] RAN 510 may include one or more AN nodes or RAN nodes 511a and 511b (collectively referred to as "multiple RAN nodes 511" or "RAN node 511") that enable connectivity between 503 and 504. As used herein, the terms "access node," "access point," etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between the network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, MF-AP, TRxP, or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node," etc., can refer to RAN node 511 (e.g., gNB) operating in NR or 5G system 500, while the terms "E-UT RAN node," etc., can refer to RAN node 511 (e.g., eNB) operating in LTE or 4G system 500. According to various implementation schemes, RAN node 511 may be implemented as one or more of dedicated physical devices such as macro cell base stations and / or low-power (LP) base stations for providing smaller coverage areas, smaller user capacity, or higher BW compared to macro cells.

[0062] In some implementations, all or part of RAN node 511 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as CRAN and / or Virtual Baseband Unit Pool (vBBUP). In these implementations, CRAN or vBBUP may implement RAN function partitioning such as PDCP partitioning, where the RRC and PDCP layers are operated by CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 511; MAC / PHY partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 511; or "lower PHY" partitioning, where the upper portion of the RRC, PDCP, RLC, MAC, and PHY layers is operated by CRAN / vBBUP, and the lower portion of the PHY layer is operated by individual RAN nodes 511. This virtualization framework allows the idle processor cores of multiple RAN nodes 511 to execute other virtualized applications. In some specific implementations, a single RAN node 511 may represent a single F1 interface (… Figure 5 (Not shown) A separate gNB-DU connected to the gNB-CU. In these specific implementations, the gNB-DU may include one or more remote radio head units or RFEMs (see, for example...). Figure 8The gNB-CU can be operated by a server (not shown) located in RAN 510 or by a server pool in a manner similar to CRAN / vBBUP. Alternatively, one or more RAN nodes in RAN 511 can be next-generation eNBs (ng-eNBs) that provide E-UTRA user plane and control plane protocol terminals to UE 501 and are connected to 5GC (e.g., via an ng interface (discussed below)). Figure 7 The RAN node (CN 720). In a specific MF implementation, the MF-AP 511 is the entity that provides MulteFire radio services and can be similar to the eNB 511 in the 3GPP architecture. Each MF-AP 511 includes or provides one or more MF cells.

[0063] In a V2X scenario, one or more RAN nodes in RAN node 511 can be RSUs or act as RSUs. The term "roadside unit" or "RSU" can refer to any traffic infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE can be referred to as a "UE-type RSU," an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU," an RSU implemented in or by a gNB can be referred to as a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside, which provides connectivity support to a passing vehicle UE 501 (vUE 501). An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Near Range Communication (DSRC) band to provide extremely low-latency communication required for high-speed events, such as collision avoidance and traffic warnings. Alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low-latency communication as well as other cellular communication services. Alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communication. Some or all of the computing device and the RSU's radio frequency circuitry may be packaged in a weather-resistant package suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers and / or backhaul networks.

[0064] Any of the RAN nodes 511 can serve as the endpoint of the air interface protocol and can be the first point of contact for multiple UEs 501. In some implementations, any of the multiple RAN nodes 511 can perform various logical functions of the RAN 510, including but not limited to the functions of the Radio Network Controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0065] In the implementation, UE 501 may be configured to communicate with each other or with any AN node in RAN node 511 using OFDM communication signals on a multi-carrier communication channel, according to various communication technologies such as, but not limited to, OFDMA communication technology (e.g., for downlink communication) or SC-FDMA communication technology (e.g., for uplink and ProSe or sidelink communication), but the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0066] Downlink and uplink transmissions can be organized into frames with a duration of 10 ms, each frame comprising ten 1 ms subframes. The slot duration is 14 symbols with normal CP and 12 symbols with extended CP, and is time-scaled as a function of the subcarrier spacing used, ensuring that an integer number of slots always exist within a subframe. In a specific LTE implementation, the DL resource grid can be used for DL ​​transmissions from any node of RAN node 511 to UE 501, while UL transmissions from UE 501 to RAN node 511 can similarly utilize a suitable UL resource grid. These resource grids can refer to time-frequency grids and indicate the physical resources in the DL or UL for each slot. Each column and row of the DL resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively, and each column and row of the UL resource grid corresponds to one SC-FDMA symbol and one SC-FDMA subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a slot in a radio frame. The resource grid includes multiple RBs, which describe the mapping of certain physical channels to REs. In the frequency domain, this can represent the minimum amount of resources currently available for allocation. Each RB comprises a set of REs. An RE is the smallest temporal frequency unit in the resource grid. Each RE is uniquely identified by an index pair (k, l) in a time slot, where and These are the indices in the frequency and time domains, respectively. RE(k, l) at antenna port p corresponds to the complex value... Antenna ports are defined such that the channel through which a symbol is transmitted on an antenna port can be inferred from the channel through which another symbol is transmitted on the same antenna port. Each antenna port has a resource grid. The supported set of antenna ports depends on the reference signal configuration in the cell, and these aspects are discussed in more detail in 3GPP TS 36.211.

[0067] In specific NR / 5G implementations, DL and UL transmissions are organized into frames with a duration of 10ms, each duration comprising ten 1ms subframes. The number of consecutive OFDM symbols in each subframe is... Each frame is divided into two equal-sized half-frames of five subframes. Each subframe has half-frame 0, which includes subframes 0-4, and half-frame 1, which includes subframes 5-9. A set of frames in the UL and a set of frames in the DL exist on the carrier. The uplink frame number i used for transmission from the UE should be in N. TA,offset The TTA (Time To Access) at the UE, starting before the start of the corresponding downlink frame, is given in 3GPP TS 38.213. TA +N TA,offset )T c For the subcarrier spacing configuration μ, the time slots are numbered in ascending order within the subframe. And within the frame, they are numbered in ascending order. Existing in time slots Continuous OFDM symbols, where The cyclic prefix depends on Tables 4.3.2-1 and 4.3.2-2 of 3GPP TS38.211. Time slots in subframes. The start time is the same as the OFDM symbol in the same subframe. The alignment begins. OFDM symbols in a time slot can be classified as “downlink,” “flexible,” or “uplink,” where downlink transmissions occur only in “downlink” or “flexible” symbols, and UE 501 transmits only in “uplink” or “flexible” symbols.

[0068] For each parameter and carrier, define subcarriers and The resource grid of OFDM symbols begins with the public grid indicated by higher-level signaling. There exists a resource grid for each transmission direction (i.e., uplink or downlink), where the subscript x is set to the DL for downlink and x is set to the UL for uplink. For a given antenna port p, subcarrier spacing configuration μ, and transmission direction (i.e., downlink or uplink), there exists one resource grid.

[0069] RB is defined in the frequency domain There are 12 consecutive subcarriers. In the frequency domain with subcarrier spacing configuration μ, common RBs are numbered from 0 upwards. The center of subcarrier 0 of common resource block 0 with subcarrier spacing configuration μ coincides with "point A". The common resource block numbering in the frequency domain... The relationship between the resource elements (k,l) and the subcarrier spacing configuration μ is determined by Given, where k is defined relative to point A, such that k = 0 corresponds to a subcarrier centered at point A. Point A is used as a common reference point for the resource block grid and is obtained from offsetToPointA of the PCell downlink, where offsetToPointA represents the frequency offset between point A and the lowest subcarrier of the lowest resource block. offsetToPointA has a subcarrier spacing provided by the higher-layer parameter subCarrierSpacingCommon and overlaps with the SS / PBCH block used by the UE for initial cell selection, expressed in resource blocks, assuming a subcarrier spacing of 15 kHz for FR1 and a subcarrier spacing of 60 kHz for FR2; and absoluteFrequencyPointA for all other cases, where absoluteFrequencyPointA represents the frequency position of point A as indicated in ARFCN.

[0070] The PRBs of the subcarrier configuration μ are defined within the BWP and numbered from 0 to 1. Where i represents the number of BWPs. Physical resource blocks in BWPi. With public The relationship between them is Given, among which, It is a common RB, where BWP starts relative to common RB 0. VRB is defined within BWP and numbered from 0 to 0. Where i is the number of BWPs.

[0071] Each element in the resource grid used for antenna port p and subcarrier spacing configuration μ is called an RE, and is defined by (k,l) p,μ Uniquely identified, where k is the index in the frequency domain and l refers to the sign position in the time domain relative to a reference point. Resource element (k, l) p,μ Corresponding to physical resources and complex values Antenna ports are defined such that the channel through which symbols are transmitted on an antenna port can be inferred from the channel through which another symbol is transmitted on the same antenna port. If a wide range of properties of the channel transmitting symbols on another antenna port can be inferred from the channel transmitting symbols on one antenna port, then the two antenna ports are considered quasi-co-located. These wide range of properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and the spatial Rx parameter.

[0072] BWP is a given parameter μ in BWPi on a given carrier. i A subset of contiguous public resource blocks as defined in subclause 4.4.4.3 of 3GPP TS 38.211. Starting position. and resource blocks in BWP The quantities should respectively satisfy and The configuration of BWPs is described in Clause 12 of 3GPP TS 38.213. UE 501 can be configured to have up to four BWPs in the DL, where a single DL BWP is active at a given time. UE 501 is not expected to receive PDSCH, PDCCH, or CSI-RS (except RRM) outside of the active BWP. UE 501 can be configured to have up to four BWPs in the UL, where a single UL BWP is active at a given time. If UE 501 is configured with a supplementary UL, UE 501 can be configured with up to four additional BWPs in the supplementary UL, where a single supplementary UL BWP is active at a given time. UE 501 does not transmit PUSCH or PUCCH outside of the active BWP, and for active cells, UE does not transmit SRS outside of the active BWP.

[0073] An NB is defined as six non-overlapping consecutive PRBs in the frequency domain. The total number of DL NBs in the DL transmission BW configured in the cell is determined by... Given. In narrowband n NB Including PRB index (in In the case of ), NBs are numbered sequentially according to the increasing number of PRBs.

[0074] if The bandwidth is then defined as four non-overlapping narrowbands in the frequency domain. The total uplink bandwidth in the uplink transmission bandwidth configured in the cell is determined by... The bandwidths are given, and the bandwidths are numbered in ascending order of narrowband number. Where, broadband n WB Narrowband index 4n WB It consists of +i, where i = 0, 1, ..., 3. If but and a single broadband by It consists of one or more non-overlapping narrowbands.

[0075] Several different physical channels and physical signals exist, using RBs and / or individual REs for transmission. Physical channels correspond to sets of REs carrying information originating from higher layers. Physical UL channels may include PUSCH, PUCCH, PRACH, and / or any other physical UL channels discussed herein, and physical DL channels may include PDSCH, PBCH, PDCCH, and / or any other physical DL channels discussed herein. Physical signals are transmitted by the physical layer (e.g., Figure 11 The physical UL signal may be used by the PHY 1110, but does not carry information originating from higher layers. Physical UL signals may include DMRS, PTRS, SRS and / or any other physical UL signals discussed herein, and physical DL signals may include DMRS, PTRS, CSI-RS, PSS, SSS and / or any other physical DL signals discussed herein.

[0076] The PDSCH carries user data and higher-layer signaling to multiple UEs 501. Typically, DL scheduling (allocating control and shared channel resource blocks to UEs 501 within the cell) can be performed on any of the RAN nodes 511 based on channel quality information fed back from any of the multiple UEs 501. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., allocated to) each of the multiple UEs 501. The PDCCH uses CCEs to transmit control information (e.g., DCI), and a set of CCEs may be referred to as a "control area". The control channel is formed by the aggregation of one or more CCEs, where different coding rates for the control channel are achieved by aggregating different numbers of CCEs. The CCEs are numbered from 0 to N. CCE,k -1, where N CCE,k-1 represents the number of CCEs in the control area of ​​subframe k. Before being mapped to REs, PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical REs, called REGs. Four QoS symbols can be mapped to each REG. Depending on the DCI size and channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats can exist, defined with different numbers of CCEs (e.g., aggregation levels, L = 1, 2, 4, or 8 in LTE, L = 1, 2, 4, 8, or 16 in NR). UE 501 monitors a set of PDCCH candidates on one or more active serving cells as configured by higher-layer signaling for control information (e.g., DCI), where monitoring means attempting to decode each of the PDCCHs (or PDCCH candidates) in that set according to all monitored DCI formats (e.g., DCI formats 0 to 6-2, as discussed in section 5.3.3 of 3GPP TS 38.212, DCI formats 0_0 to 2_3, as discussed in section 7.3 of 3GPP TS 38.212, etc.). UE 501 monitors (or attempts to decode) the corresponding set of PDCCH candidates at one or more configured monitoring times according to the corresponding search space configuration. DCI transmits DL, UL, or SL scheduling information, requests for aperiodic CQI reports, LAA public information, notifications of MCCH changes, UL power control commands for a cell and / or an RNTI, notifications to a group of UEs regarding time slot formats, notifications to a group of UEs regarding PRB and OFDM symbols (where the UE may assume no transmission intended for the UE), TPC commands for PUCCH and PUSCH, and / or TPC commands for PUCCH and PUSCH. DCI coding procedures are discussed in 3GPP TS 38.212.

[0077] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize EPDCCH, which uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similarly, each ECCE may correspond to a set of nine, each consisting of four physical resource elements, called EREG. In some cases, an ECCE may have a different number of EREGs.

[0078] As previously described, the PDCCH can be used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH. Specifically, the DCI on the PDCCH includes downlink allocation, which at least includes modulation and coding formats, resource allocation, and HARQ information related to the DL-SCH; and / or uplink scheduling permission, which at least includes modulation and coding formats, resource allocation, and HARQ information related to the UL-SCH. In addition to scheduling, the PDCCH can be used to activate and deactivate configured PUSCH transmissions with configured permissions; activate and deactivate PDSCH semi-persistent transmissions; notify one or more UEs 501 of slot formats; notify one or more UEs 501 of PRB and OFDM symbols, where UE 501 may assume no transmission is intended for UE; transmit TPC commands for PUCCH and PUSCH; transmit one or more TPC commands for SRS transmissions by one or more UEs 501; switch the active BWP of UE 501; and initiate random access procedures.

[0079] In the specific implementation of NR, UE 501 monitors (or attempts to decode) the corresponding PDCCH candidate set in one or more configured CORESETs during one or more configured monitoring times, according to the corresponding search space configuration. A CORESET may include a PRB set with a duration of one to three OFDM symbols. A CORESET may additionally or alternatively include frequency domain... RB and time domain Symbols. A CORESET comprises six REGs numbered in ascending order in a time-first manner, where a REG is equal to one RB during one OFDM symbol period. A UE 501 can be configured with multiple CORESETs, where each CORESET is associated with only one CCE-to-REG mapping. Interleaved and non-interleaved CCE-to-REG mappings are supported in a CORESET. Each REG carrying the PDCCH carries its own DMRS.

[0080] According to various implementations, UE 501 and RAN node 511 transmit data (e.g., transmit and receive data) through licensed media (also referred to as “licensed spectrum” and / or “licensed band”) and unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”). Licensed spectrum may include channels operating in the frequency range of approximately 400 MHz to approximately 3.8 GHz, while unlicensed spectrum may include a 5 GHz band.

[0081] To operate in unlicensed spectrum, UE 501 and RAN node 511 may use LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, UE 501 and RAN node 511 may perform one or more known medium sensing and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmission in the unlicensed spectrum. Medium / carrier sensing operations may be performed according to a Listen-After-Speak (LBT) protocol.

[0082] LBT is a mechanism that equipment (e.g., UE 501, RAN node 511, etc.) uses to sense a medium (e.g., a channel or carrier frequency) and transmit when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). Medium sensing operations may include CCA, which utilizes at least ED to determine the presence of other signals on the channel in order to determine whether the channel is occupied or idle. This LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy in the intended transmission band over a period of time and comparing the sensed RF energy with predefined or configured thresholds.

[0083] Typically, existing systems in the 5GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 501, AP 506, etc.) intends to transmit, the WLAN node can first perform CCA before transmitting. Additionally, in cases where more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. This backoff mechanism can be a counter randomly introduced within the CWS, which increases exponentially upon collision and resets to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to WLAN's CSMA / CA. In some specific implementations, the LBT process for DL ​​or UL transmission bursts (including PDSCH or PUSCH transmissions) can have a variable-length LAA contention window between X and Y ECCA time slots, where X and Y are the minimum and maximum values ​​of the LAA's CWS. In one example, the minimum CWS for LAA transmission can be 9 microseconds (μs); however, the size of the CWS and MCOT (e.g., transmission burst) can be based on government regulatory requirements.

[0084] The LAA mechanism is built upon the CA technology of LTE-Advanced systems. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz, or 20MHz, and a maximum of five CCs can be aggregated, thus the maximum aggregated bandwidth is 100MHz. In FDD systems, the number of aggregated carriers can differ for DL ​​and UL, where the number of UL CCs is equal to or less than the number of DL component carriers. In some cases, individual CCs can have different bandwidths than other CCs. In TDD systems, the number of CCs and the bandwidth (BW) of each CC are typically the same for DL ​​and UL.

[0085] The CA also includes individual serving cells to provide individual CCs. The coverage of serving cells can differ, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell, or PCell, provides the PCC for both UL and DL and handles activities related to RRC and NAS. Other serving cells are called SCells, and each SCell provides individual SCCs for both UL and DL. SCCs can be added and removed as needed, and changing the PCC may require UE 501 to undergo handover. In LAA, eLAA, and feLAA, some or all of the SCells can operate in unlicensed spectrum (referred to as "LAA SCells"), and LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured to have more than one LAA SCell, the UE can receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0086] RAN nodes 511 can be configured to communicate with each other via interface 512. In implementations where system 500 is an LTE system (e.g., when CN 520 is...), Figure 6In the case of EPC 620, interface 512 can be an X2 interface 512. The X2 interface can be defined between two or more RAN nodes 511 (e.g., two or more eNBs, etc.) connected to EPC 520, and / or between two eNBs connected to EPC 520. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). X2-U can provide flow control mechanisms for user packets transmitted via the X2 interface and can be used to transmit information about the delivery of user data between eNBs. For example, X2-U can provide specific sequence number information about user data transmitted from MeNB to SeNB; information about the successful in-order delivery of PDCP PDUs from SeNB to UE 501 for user data; information about PDCP PDUs not delivered to UE 501; information about the current minimum expected buffer size at SeNB for transmitting user data to the UE; and so on. X2-C provides intra-LTE access mobility functions, including context transfer from the source eNB to the destination eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions. In embodiments where system 100 is an MF system (e.g., when CN 520 is NHCN 520), interface 512 may be an X2 interface 512. The X2 interface may be defined between two or more RAN nodes 511 (e.g., two or more MF-APs, etc.) connected to NHCN 520, and / or between two MF-APs connected to NHCN 520. In these embodiments, the X2 interface may operate in the same or similar manner as previously discussed.

[0087] In system 500, which is a 5G or NR system (e.g., when CN 520 is as follows), Figure 7In an implementation of 5GC 520, interface 512 may be an Xn interface 512. The Xn interface is defined between two or more RAN nodes 511 (e.g., two or more gNBs, etc.) connected to 5GC 520, between a RAN node 511 (e.g., a gNB) connected to 5GC 520 and an eNB, and / or between two eNBs connected to 5GC 520. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 501 in connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected mode between one or more RAN nodes 511. This mobility support may include context transfer from the old (source) serving RAN node 511 to the new (destination) serving RAN node 511; and control of the user plane tunnel between the old (source) serving RAN node 511 and the new (destination) serving RAN node 511. The Xn-U protocol stack may include a transport network layer built on top of the Internet Protocol (IP) transport layer, and a GTP-U layer on top of the UDP and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on top of SCTP. SCTP may be on top of the IP layer and provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0088] RAN 510 is shown communicatively coupled to the core network—in this embodiment, communicatively coupled to CN 520. CN 520 may include multiple network elements 522 configured to provide various data and telecommunications services to customers / users (e.g., users of UE 501) connected to CN 520 via RAN 510. Components of CN 520 may be implemented in a physical node or separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 520 may be referred to as a network slice, and a logical instance of a portion of CN 520 may be referred to as a network subslice. NFV architectures and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (optionally performed by proprietary hardware). In other words, an NFV system can be used to perform a virtual or reconfigurable concrete implementation of one or more EPC components / functions.

[0089] Generally, application server 530 can be a component that provides IP bearer resources for applications to use with the core network (e.g., UMTS PS domain, LTE PS data service, etc.). Application server 530 can also be configured to support one or more communication services for UE 501 via EPC 520 (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0090] In the implementation, CN 520 may be a 5GC (referred to as "5GC 520", etc.), and RAN 510 may be connected to CN 520 via NG interface 513. In the implementation, NG interface 513 may be divided into two parts: NG User Plane (NG-U) interface 514, which carries traffic data between RAN node 511 and UPF; and S1 Control Plane (NG-C) interface 515, which is the signaling interface between RAN node 511 and AMF. (See reference...) Figure 7 The implementation scheme of CN 520 for 5GC 520 will be discussed in more detail.

[0091] In one implementation, CN 520 may be a 5G CN (referred to as "5GC 520", etc.), while in other implementations, CN 520 may be an EPC. When CN 520 is an EPC (referred to as "EPC 520", etc.), RAN 510 may be connected to CN 520 via S1 interface 513. In one implementation, S1 interface 513 may be divided into two parts: an S1 user plane (S1-U) interface 514, which carries traffic data between RAN node 511 and S-GW; and an S1-MME interface 515, which is the signaling interface between RAN node 511 and MME.

[0092] In the implementation of CN 520 as MF NHCN 520, one or more network elements 522 may include or operate one or more NH-MMEs, local AAA agents, NH-GWs, and / or other similar MF NHCN elements. The NH-MME provides functionality similar to the MME in EPC 520. The local AAA agent is an AAA agent that is part of an NHN that provides the AAA functionality required for interoperability with PSP AAA and 3GPP AAA. PSP AAA is an AAA server (or server pool) that uses non-USIM credentials associated with the PSP and can be located inside or outside the NHN; 3GPP AAA is discussed in more detail in 3GPP TS 23.402. The NH-GW provides functionality similar to the combined S-GW / P-GW for PDN connections with non-EPC routes. For PDN connections with EPC routes, the NHN-GW provides functionality similar to the S-GW previously discussed in the interaction with the MF-AP via the S1 interface 513, and similar to TWAG in the interaction with the PLMN PDN-GW via the S2a interface. In some implementations, the MF AP 511 may be connected to the previously discussed EPC 520. Additionally, the RAN 510 (referred to as "MF RAN 510", etc.) may be connected to the NHCN 520 via the S1 interface 513. In these implementations, the S1 interface 513 may be divided into two parts: an S1 interface 514, which carries traffic data between the RAN node 511 (e.g., "MF-AP 511") and the NH-GW; and an S1-MME-N interface 515, which is the signaling interface between the RAN node 511 and the NH-MME. The S1-U interface 514 and the S1-MME-N interface 515 have the same or similar functionality as the S1-U interface 514 and S1-MME interface 515 of the EPC 520 discussed herein.

[0093] Figure 6An exemplary architecture of a system 600 including a first CN 620 according to various implementations is shown. In this example, the system 600 can implement the LTE standard, wherein CN 620 is corresponding to... Figure 5 CN 520's EPC 620. Additionally, UE 601 can be used with... Figure 5 The UE 501 is the same as or similar to it, and the E-UTRAN 610 can be the same as... Figure 5 The RAN 510 is the same as or similar to the RAN 511 discussed earlier. CN 620 may include MME 621, S-GW 622, P-GW 623, HSS624 and SGSN 625.

[0094] The MME 621 is functionally similar to the control plane of a traditional SGSN and can implement MM functions to keep track of the current location of UE 601. The MME 621 can perform various MM procedures to manage mobility aspects of access, such as gateway selection and tracking area list management. MM (also known as “EPS MM” or “EMM” in E-UTRAN systems) can refer to all applicable procedures, methods, data storage, etc., used to maintain knowledge about the current location of UE 601, provide user / subscriber confidentiality, and / or perform other similar services. Each UE 601 and MME 621 may include an MM or EMM sublayer, and an MM context can be established in both UE 601 and MME 621 upon successful attachment. The MM context can be a data structure or database object that stores MM-related information for UE 601. MME 621 can be coupled to HSS 624 via reference point S6a, to SGSN 625 via reference point S3, and to S-GW 622 via reference point S11.

[0095] SGSN 625 can be a node that serves UE 601 by tracking the location of the individual UE 601 and performing security functions. Furthermore, SGSN 625 can perform inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; such as PDN and S-GW selection as specified by MME 621; processing of UE 601 time zone functions as specified by MME 621; and MME selection for handover to the E-UTRAN 3GPP access network. The S3 reference point between MME 621 and SGSN 625 can enable user and bearer information exchange for 3GPP indirect access network mobility in idle and / or active states.

[0096] HSS 624 may include a database for network users, containing subscription-related information to support network entities in handling communication sessions. EPC 620 may include one or more HSS 624s, depending on the number of mobile subscribers, equipment capacity, network organization, etc. For example, HSS 624 can provide support for routing / roaming, authentication, authorization, naming / addressing solutions, location dependencies, etc. An S6a reference point between HSS 624 and MME 621 can enable the transfer of subscription and authentication data for authenticated / authorized user access to EPC 620 between HSS 624 and MME 621.

[0097] S-GW 622 can terminate the S1 interface 513 towards RAN 610. Figure 6 The S-GW 622 (referred to as "S1-U") routes data packets between RAN 610 and EPC 620. Additionally, the S-GW 622 can serve as a local mobility anchor for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies. The S11 reference point between the S-GW 622 and MME 621 provides a control plane between MME 621 and S-GW 622. The S-GW 622 can be coupled to the P-GW 623 via the S5 reference point.

[0098] The P-GW 623 can terminate the SGi interface toward the PDN 630. The P-GW 623 can be accessed via IP interface 525 (see, for example, Figure 5 The P-GW 623 routes data packets between the EPC 620 and external networks, such as a network including an application server 530 (optionally referred to as "AF"). In an implementation, the P-GW 623 may be located via an IP communication interface 525 (see, for example, ...). Figure 5 Communication is coupled to the application server. Figure 5 Application server 530 or Figure 6The S5 reference point between P-GW 623 and S-GW 622 can provide user plane tunneling and tunnel management between P-GW 623 and S-GW 622. The S5 reference point can also be used for S-GW 622 relocation due to the mobility of UE 601 and whether S-GW 622 needs to connect to the non-coordinated P-GW 623 for required PDN connectivity. P-GW 623 may also include nodes for policy enforcement and charging data collection (e.g., PCEF (not shown)). Additionally, the SGi reference point between P-GW 623 and Packet Data Network (PDN) 630 can be an external public or private PDN or an internal operator packet data network, for example, for providing IMS services. P-GW 623 can be coupled to PCRF 626 via a Gx reference point.

[0099] PCRF 626 is the policy and charging control element of EPC 620. In non-roaming scenarios, a single PCRF 626 may exist in the domestic public land mobile network (HPLMN) associated with the Internet Protocol Connectivity Access Network (IP-CAN) session of UE 601. In roaming scenarios with local traffic breaches, two PCRFs may exist associated with the IP-CAN session of UE 601: the home PCRF (H-PCRF) in the HPLMN and the visited PCRF (V-PCRF) in the visited public land mobile network (VPLMN). PCRF 626 can be communicatively coupled to application server 630 via P-GW 623. Application server 630 can signal PCRF 626 to indicate new service flows and select appropriate QoS and charging parameters. PCRF 626 can configure this rule to have a PCEF (not shown) with appropriate TFT and QCI, which initiates QoS and charging as specified by application server 630. The Gx reference point between PCRF 626 and P-GW 623 allows QoS policies and charging rules to be transferred from PCRF 626 to PCRF in P-GW 623. The Rx reference point can reside between PDN 630 (or "AF 630") and PCRF 626.

[0100] Figure 7The architecture of a system 700 including a second CN 720 according to various embodiments is shown. System 700 is shown as including a UE 701, which may be the same as or similar to the previously discussed UEs 501 and 601; (R)AN 710, which may be the same as or similar to the previously discussed RANs 510 and 610, and may include the previously discussed RAN node 511; and DN 703, which may be, for example, a carrier service, Internet access, or a third-party service; and 5GC 720. 5GC 720 may include AUSF 722; AMF 721; SMF 724; NEF 723; PCF 726; NRF 725; UDM 727; AF 728; UPF 702; and NSSF 729.

[0101] The UPF 702 can act as an anchor point for mobility within and between RATs, an external PDU session point interconnected with the DN 703, and a branch point supporting multihomed PDU sessions. The UPF 702 can also perform packet routing and forwarding, packet inspection, user plane portion enforcement of policy rules, lawful packet interception (UP collection), traffic usage reporting, QoS processing on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic authentication (e.g., SDF-to-QoS flow mapping), transport level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 702 may include an uplink classifier to support routing traffic flows to the data network. The DN 703 may represent various network operator services, Internet access, or third-party services. The DN 703 may include or be similar to the previously discussed application server 530. The UPF 702 can interact with the SMF 724 via an N4 reference point between the SMF 724 and the UPF 702.

[0102] The AUSF 722 stores data for authentication of the UE 701 and handles authentication-related functions. The AUSF 722 facilitates a common authentication framework for various access types. The AUSF 722 can communicate with the AMF 721 via the N12 reference point between the AMF 721 and the AUSF 722; and with the UDM 727 via the N13 reference point between the UDM 727 and the AUSF 722. Additionally, the AUSF 722 can present an interface based on Nausf services.

[0103] AMF 721 can handle registration management (e.g., registering UE 701, etc.), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. AMF 721 can be the termination point of the N11 reference point between AMF 721 and SMF 724. AMF 721 can provide transport for SM messages between UE 701 and SMF 724 and act as a transparent proxy for routing SM messages. AMF 721 can also provide transport for UE 701 and SMSF ( Figure 7 SMS messages are transmitted between (not shown in the diagram). AMF 721 can act as a SEAF, which may include interaction with AUSF 722 and UE 701, receiving an intermediate key established due to the UE 701 authentication process. In the case of USIM-based authentication, AMF 721 may retrieve security material from AUSF 722. AMF 721 may also include an SCM function that receives a key from the SEA for deriving a network-specific access key. Furthermore, AMF 721 may be the termination point of the RAN CP interface, which may include or be the N2 reference point between (R)AN 710 and AMF 721; and AMF 721 may be the termination point of NAS (N1) signaling, performing NAS encryption and integrity protection.

[0104] The AMF 721 can also support NAS signaling with the UE 701 via the N3 IWF interface. The N3 IWF can be used to provide access to untrusted entities. The N3 IWF can be the termination point of the N2 interface between the (R)AN 710 and AMF 721 in the control plane, and can be the termination point of the N3 reference point between the (R)AN 710 and UPF 702 in the user plane. Therefore, the AMF 721 can process N2 signaling from the SMF 724 and AMF 721 for PDU sessions and QoS, encapsulate / decapsulate packets for IPSec and N3 tunneling, mark N3 user plane packets in the uplink, and perform QoS corresponding to the N3 packet marking, taking into account the QoS requirements associated with such markings received via N2. The N3IWF can also relay uplink and downlink control plane NAS signaling between UE 701 and AMF 721 via the N1 reference point between UE 701 and AMF 721, and relay uplink and downlink user plane packets between UE 701 and UPF 702. The N3IWF also provides a mechanism for establishing IPsec tunnels using UE 701. AMF 721 can present an interface based on Namf services and can be the N14 reference point between two AMF 721s and between AMF 721 and 5G-EIR (…). Figure 7 The endpoint of the N17 reference point (not shown).

[0105] UE 701 may need to register with AMF 721 to receive network services. The RM is used to register or deregister UE 701 with the network (e.g., AMF 721) and to establish a UE context within the network (e.g., AMF 721). UE 701 can operate in either RM-REGISTERED or RM-DEREGISTERED state. In RM-DEREGISTERED state, UE 701 is not registered with the network, and the UE context in AMF 721 does not maintain valid location or routing information for UE 701; therefore, AMF 721 cannot reach UE 701. In RM-REGISTERED state, UE 701 is registered with the network, and the UE context in AMF 721 can maintain valid location or routing information for UE 701; therefore, AMF 721 can reach UE 701. In the RM-REGISTERED state, UE 701 can execute mobility registration update procedures, execute periodic registration update procedures triggered by the expiration of periodic update timers (e.g., to notify the network that UE 701 is still active), and execute registration update procedures to update UE capability information or renegotiate protocol parameters with the network, etc.

[0106] The AMF 721 can store one or more RM contexts for the UE 701, where each RM context is associated with a specific access to the network. The RM context can be a data structure, database object, etc., indicating or storing, in particular, the registration status and periodic update timers for each access type. The AMF 721 can also store 5GC MM contexts that are the same as or similar to the previously discussed (E)MM contexts. In various implementations, the AMF 721 can store the CE Mode B limiting parameters of the UE 701 in the associated MM or RM context. The AMF 721 can also derive values ​​from UE usage setting parameters already stored in the UE context (and / or MM / RM context) when needed.

[0107] The CM can be used to establish and release signaling connections between UE 701 and AMF 721 via the N1 interface. The signaling connection enables NAS signaling exchange between UE 701 and CN 720, and includes signaling connections between the UE and AN (e.g., RRC connections for non-3GPP access or UE-N3IWF connections) and N2 connections between the AN (e.g., RAN 710) and AMF 721 for UE 701. UE 701 can operate in one of two CM states (CM-IDLE mode or CM-CONNECTED mode). When UE 701 operates in CM-IDLE state / mode, UE 701 may not have a NAS signaling connection established with AMF 721 via the N1 interface, and (R)AN 710 signaling connections (e.g., N2 and / or N3 connections) may exist for UE 701. When UE 701 operates in CM-CONNECTED state / mode, UE 701 may have a NAS signaling connection established with AMF 721 via the N1 interface, and may have (R)AN 710 signaling connections (e.g., N2 and / or N3 connections) for UE 701. Establishing an N2 connection between (R)AN 710 and AMF 721 can cause UE 701 to transition from CM-IDLE mode to CM-CONNECTED mode, and UE 701 can transition from CM-CONNECTED mode to CM-IDLE mode when the N2 signaling between (R)AN 710 and AMF 721 is released.

[0108] SMF 724 can be responsible for SM (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic redirection of the UPF to route traffic to the correct destination; terminating the interface toward policy control functions; policy enforcement and QoS control portions; lawful interception (for SM events and interfaces with the LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to the AN via N2 through the AMF; and determining the SSC mode of the session. SM may refer to the management of PDU sessions, and a PDU session or "session" may refer to the PDU connectivity service that provides or enables PDU exchange between UE 701, identified by the Data Network Name (DNN), and Data Network (DN) 703. A PDU session can be established, modified, and released upon request by UE 701, modified, and released upon request by both UE 701 and 5GC 720, using NAS SM signaling exchanged between UE 701 and SMF 724 via the N1 reference point. Upon request from the application server, 5GC 720 can trigger a specific application in UE 701. In response to receiving a trigger message, UE 701 can pass the trigger message (or relevant portions / information of the trigger message) to one or more identified applications in UE 701. The identified application in UE 701 can establish a PDU session to a specific DNN. SMF 724 can check whether the UE 701 request matches the user subscription information associated with UE 701. In this regard, SMF 724 can retrieve and / or request to receive update notifications regarding SMF 724 level subscription data from UDM 727.

[0109] The SMF 724 may include the following roaming functions: handling local execution to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful interception (for SM events and interfaces with the LI system, in the VPLMN); and support for interaction with external DNs to transmit signaling for PDU session authorization / authentication via external DNs. In roaming scenarios, an N16 reference point between two SMF 724s may be included in System 700, which may be located between another SMF 724 in the visited network and an SMF 724 in the home network. Additionally, the SMF 724 may present an interface based on Nsmf services.

[0110] The NEF 723 provides means for securely exposing services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, application functions (e.g., AF 728), edge computing, or fog computing systems. In such implementations, the NEF 723 can authenticate, authorize, and / or restrict AFs. The NEF 723 can also translate information exchanged with AF 728 and information exchanged with internal network functions. For example, the NEF 723 can translate between AF service identifiers and internal 5GC information. The NEF 723 can also receive information from other network functions (NFs) based on their exposure capabilities. This information can be stored as structured data at the NEF 723 or stored at a data storage NF using a standardized interface. The stored information can then be re-exposed by the NEF 723 to other NFs and AFs, and / or used for other purposes such as analysis. Additionally, the NEF 723 can present an interface based on Nnef services.

[0111] The NRF 725 supports service discovery, receiving NF discovery requests from NF instances and providing information about discovered NF instances to them. The NRF 725 also maintains information about available NF instances and the services they support. As used herein, terms such as "instantiation" can refer to the creation of an instance, and "instance" can refer to the concrete occurrence of an object, which may occur, for example, during the execution of program code. Additionally, the NRF 725 can present an interface based on Nnrf services.

[0112] PCF 726 provides control plane functions to enforce their policy rules and also supports a unified policy framework for managing network behavior. PCF 726 also implements FE to access subscription information related to policy decisions in the UDR of UDM 727. PCF 726 can communicate with AMF 721 via the N15 reference point between PCF 726 and AMF 721, which can include PCF 726 in the visited network and AMF 721 in roaming scenarios. PCF 726 can communicate with AF 728 via the N5 reference point between PCF 726 and AF 728; and with SMF 724 via the N7 reference point between PCF 726 and SMF 724. System 700 and / or CN 720 may also include an N24 reference point between PCF 726 (in the home network) and PCF 726 in the visited network. Additionally, PCF 726 can present an interface based on NPCF services.

[0113] The UDM 727 can process subscription-related information to support network entities in handling communication sessions and can store the subscription data of the UE 701. For example, subscription data can be transmitted between the UDM 727 and the AMF 721 via the N8 reference point between the UDM 727 and the AMF 721. The UDM 727 may include two parts: the application FE and the UDR (Application Provider Diagram). Figure 7 (FE and UDR are not shown). The UDR may store subscription data and policy data of UDM 727 and PCF 726, and / or structured data for exposure of NEF 723, as well as application data (including PFD for application detection, application request information of multiple UE 701s). The interface based on the Nudr service may be presented by UDR 221 to allow UDM 727, PCF 726 and NEF 723 to access specific sets of stored data, as well as notifications for reading, updating (e.g., adding, modifying), deleting and subscribing to relevant data changes in the UDR. The UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front-ends may serve the same user in different transactions. UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management and subscription management. The UDR may interact with SMF 724 via the N10 reference point between UDM 727 and SMF 724. The UDM 727 also supports SMS management, with SMS-FE implementing similar application logic as previously discussed. Additionally, the UDM 727 can present an interface based on Nudm services.

[0114] AF 728 can provide application-level influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE can be a mechanism allowing 5GC 720 and AF 728 to provide information to each other via NEF 723, which can be used in edge computing implementations. In such implementations, network operators and third-party services can be hosted near the UE 701 access point to achieve efficient service delivery through reduced end-to-end latency and load on the transport network. For edge computing implementations, 5GC can select UPF 702 near UE 701 and perform traffic redirection from UPF 702 to DN 703 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 728. Thus, AF 728 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 728 is considered a trusted entity, network operators can allow AF 728 to interact directly with the relevant NF. Additionally, AF 728 can present an interface based on Naf services.

[0115] NSSF 729 can select a set of network slice instances to serve UE 701. If needed, NSSF 729 can also determine the allowed NSSAIs and the mapping to subscribed S-NSSAIs. NSSF 729 can also determine the AMF set, or list of candidate AMFs 721, for serving UE 701 based on appropriate configuration and possibly by querying NRF 725. The selection of a set of network slice instances for UE 701 can be triggered by AMF 721, where UE 701 registers by interacting with NSSF 729, which can result in a change to AMF 721. NSSF 729 can interact with AMF 721 via the N22 reference point between AMF 721 and NSSF 729; and via the N31 reference point (…). Figure 7 (Not shown) Communicates with another NSSF 729 in the visited network. Additionally, the NSSF 729 may present an interface based on the Nnssf service.

[0116] As discussed above, CN 720 may include an SMSF responsible for SMS subscription checks and authentication, and for relaying SM messages to / from UE 701 and to / from other entities such as SMS-GMSC / IWMSC / SMS routers. SMS may also interact with AMF 721 and UDM 727 for notification procedures indicating that UE 701 is available for SMS delivery (e.g., setting a UE unreachable flag and notifying UDM 727 when UE 701 is available for SMS).

[0117] CN 520 may also include Figure 7 Other elements not shown include data storage systems / architecture, 5G-EIR, SEPP, etc. Data storage systems may include SDSF, UDSF, etc. Any NF can be transmitted via any NF and UDSF ( Figure 7 The N18 reference points (not shown) between NFs store unstructured data in or retrieve it from the UDSF (e.g., UE context). Individual NFs may share a UDSF for storing their respective unstructured data, or each NF may have its own UDSF located at or near the individual NF. Additionally, the UDSF may present an interface based on the Nudsf service (…). Figure 7 (Not shown). 5G-EIR can be an NF that checks the status of PEI to determine whether to blacklist a specific device / entity from the network; and SEPP can be a non-transparent agent that performs topology hiding, message filtering, and policing on the control plane interface between PLMNs.

[0118] Furthermore, there can be more reference points and / or service-based interfaces between NF services; however, for clarity, Figure 7These interfaces and reference points are omitted. In one example, CN 720 may include an Nx interface, which is an inter-CN interface between the MME (e.g., MME 621) and AMF 721 to enable interoperability between CN 720 and CN 620. Other example interfaces / reference points may include an interface based on N5g-EIR services presented by 5G-EIR, an N27 reference point between an NRF in the visited network and an NRF in the home network; and an N31 reference point between an NSSF in the visited network and an NSSF in the home network.

[0119] Figure 8 Examples of infrastructure equipment 800 according to some embodiments are shown. Infrastructure equipment 800 (or “system 800”) may be implemented as a base station, a radio head unit, a RAN node (such as RAN node 511 and / or AP 506 previously shown and described), an application server 530, and / or any other element / device discussed herein. In other examples, system 800 may be implemented in or by a UE.

[0120] System 800 includes: application circuitry 805, baseband circuitry 810, one or more radio front-end modules (RFEMs) 815, memory circuitry 820, power management integrated circuit (PMIC) 825, power tee circuitry 830, network controller circuitry 835, network interface connector 840, satellite positioning circuitry 845, and user interface 850. In some embodiments, device 800 may include additional components such as, for example, memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the following components may be included in more than one device. For example, the circuitry may be individually included in more than one device for CRAN, vBBU, or other similar implementations.

[0121] Application circuit 805 includes, but is not limited to, the following circuits: one or more processors (processor cores), cache memory, and one or more of the following: low dropout regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I... 2The system may include a C or general-purpose programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, general-purpose input / output (I / O or IO), a memory card controller such as a Secure Digital (SD) Multimedia Card (MMC) or similar, a Universal Serial Bus (USB) interface, a Mobile Industry Processor Interface (MIPI) interface, and a Joint Test Access Group (JTAG) test access port. The processor (or core) of the application circuit 805 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the system 800. In some specific implementations, the memory / storage element may be on-chip memory circuitry that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0122] The processor of application circuit 805 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more Reduced Instruction Set Computing (RISC) processors, one or more Acorn RISC machine (ARM) processors, one or more Complex Instruction Set Computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, application circuit 805 may include or may be a dedicated processor / controller for operation according to the various embodiments described herein. As an example, the processor of application circuit 805 may include one or more Intel processors / controllers. or Processor; Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium™, Inc. MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some implementations, system 800 may not utilize application circuitry 805 and may instead include a dedicated processor / controller to process, for example, IP data received from EPC or 5GC.

[0123] In some implementations, application circuitry 805 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. These hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, programmable processing devices may be one or more field-programmable devices (FPDs), such as field-programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and so on. In such implementations, the circuitry of application circuitry 805 may include logic blocks or logic architectures, and other interconnect resources that can be programmed to perform various functions such as processes, methods, functions, etc., as discussed in the various embodiments herein. In such implementations, the circuitry of application circuit 805 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), fuse, etc.)) for storing logic blocks, logic architectures, data, etc. in lookup tables (LUTs).

[0124] The baseband circuit 810 can be implemented, for example, as a soldered substrate, comprising one or more integrated circuits, a single-package integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. See below for reference. Figure 10 This paper discusses the various hardware electronic components of the 810 baseband circuit.

[0125] User interface circuitry 850 may include one or more user interfaces designed to enable a user to interact with system 800 or peripheral component interfaces, wherein the peripheral component interfaces are designed to enable peripheral components to interact with system 800. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light-emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, headphones, a display screen or display device, etc. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal serial bus (USB) ports, audio jacks, power interfaces, etc.

[0126] The radio front-end module (RFEM) 815 may include a millimeter-wave (mmWave) RFEM and one or more sub-millimeter-wave radio frequency integrated circuits (RFICs). In some specific implementations, the one or more sub-millimeter-wave RFICs may be physically decoupled from the millimeter-wave RFEM. The RFIC may include connectors to one or more antennas or antenna arrays (see, for example, below). Figure 10 The antenna array 10111 is used, and the RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter-wave and sub-millimeter-wave radio functions can be implemented in the same physical RFEM 815 that combines both millimeter-wave and sub-millimeter-wave antennas.

[0127] The memory circuit 820 may include one or more of the following: volatile memory including dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM); non-volatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as "flash memory"); phase-change random access memory (PRAM); magnetoresistive random access memory (MRAM); and may be combined with and A three-dimensional (3D) XPOINT memory. The memory circuit 820 can be implemented as one or more of the following: a solder-in packaged integrated circuit, a socket memory module, and an insertable memory card.

[0128] The PMIC 825 may include a voltage regulator, surge protector, power alarm detection circuitry, and one or more backup power sources, such as batteries or capacitors. The power alarm detection circuitry can detect one or more of a power outage (undervoltage) and a power surge (overvoltage) condition. The power tee circuit 830 can provide power drawn from the network cable to provide both power and data connectivity to the infrastructure equipment 800 using a single cable.

[0129] Network controller circuitry 835 can provide connectivity to a network using standard network interface protocols such as Ethernet, GRE-tunneled Ethernet, Multiprotocol Label Switching (MPLS)-based Ethernet, or some other suitable protocol. Network connectivity can be provided to / from infrastructure equipment 800 via a physical connection via network interface connector 840, which can be an electrical connection (typically referred to as a "copper interconnect"), an optical connection, or a wireless connection. Network controller circuitry 835 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, network controller circuitry 835 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0130] Positioning circuit 845 includes circuitry for receiving and decoding signals transmitted / broadcast by a positioning network of a Global Navigation Satellite System (GNSS). Examples of navigation satellite constellations (or GNSS) include the U.S. Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler orbit chart and satellite integrated radio positioning (DORIS), etc.). Positioning circuit 845 may include various hardware components (e.g., hardware devices such as switches, filters, amplifiers, antenna elements, etc.) for facilitating OTA communication to communicate with components of the positioning network, such as navigation satellite constellation nodes. In some embodiments, positioning circuit 845 may include a micro-technology (micro PNT) IC for positioning, navigation, and timing, which performs position tracking / estimation using a master timing clock in the absence of GNSS assistance. The positioning circuit 845 may also be part of or interact with the baseband circuit 810 and / or RFEM 815 to communicate with nodes and components of the positioning network. The positioning circuit 845 may also provide location data and / or time data to the application circuit 805, which may use the data to synchronize operations with various infrastructures, such as RAN node 511.

[0131] Figure 8 The components shown can communicate with each other using interface circuitry, which may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI Express (PCIe), or any number of other technologies. The bus / IX may be a proprietary bus, for example, used in a SoC-based system. Other bus / IX systems, such as I... 2 Interfaces include C-type interface, SPI interface, point-to-point interface, and power bus, etc.

[0132] Figure 9 Examples of platform 900 (or “device 900”) according to various embodiments are shown. In embodiments, computer platform 900 may be adapted to function as UE 501, 601, 701, application server 530 and / or any other element / device discussed herein. Platform 900 may include any combination of the components shown in the examples. Components of platform 900 may be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices or other modules, logic, hardware, software, firmware or combinations thereof adapted in computer platform 900, or implemented as components otherwise integrated within the chassis of a larger system. Figure 9The block diagram is intended to show a high-level view of the components of the computer platform 900. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific embodiments.

[0133] Application circuit 905 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and LDOs, interrupt controllers, serial interfaces (such as SPI), and I / O pins. 2 The system may include one or more of the following: a C or general-purpose programmable serial interface module, an RTC, timers (including interval timers and watchdog timers), general-purpose I / O, a memory card controller (such as an SD MMC or similar controller), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of the application circuitry 905 may be coupled to or may include a memory / storage element, and may be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the system 900. In some specific implementations, the memory / storage element may be on-chip memory circuitry that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0134] The processor 805 of the application circuit may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, the application circuit 805 may include or may be a dedicated processor / controller for operation according to the various embodiments herein.

[0135] As an example, the processor of application circuit 905 may include a processor based on... Architecture Core TM processors, such as Quark TM Atom TM i3, i5, i7 or MCU-level processors, or available from Santa Clara, California. Another processor of this type from the company. The processor for the Application Circuit 905 can also be one or more of the following: Advanced Micro Devices (AMD). Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, from Snapdragon by Technologies, Inc. TM Processor, Texas Instruments Open Multimedia Applications Platform(OMAP) TM Processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some specific implementations, the application circuitry 905 may be part of a system-on-a-chip (SoC), where the application circuitry 905 and other components are formed as a single integrated circuit or a single package, such as... company( Edison Corporation TM Or Galileo TM SoC board.

[0136] Additionally or alternatively, application circuitry 905 may include circuitry such as, but not limited to, one or more field-programmable devices (FPDs) such as FPGAs; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs such as structured ASICs; programmable SoCs (PSoCs); and so on. In such embodiments, the circuitry of application circuitry 905 may include logic blocks or logic architectures, and other interconnect resources that can be programmed to perform various functions such as processes, methods, functions, etc., as discussed in the various embodiments herein. In such embodiments, the circuitry of application circuitry 905 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), fuses, etc.)) for storing logic blocks, logic architectures, data, etc., in lookup tables (LUTs), etc.

[0137] The baseband circuit 910 can be implemented, for example, as a soldered substrate, comprising one or more integrated circuits, a single-package integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. See below for reference. Figure 10 This paper discusses the various hardware electronic components of the 910 baseband circuit.

[0138] The RFEM 915 may include a millimeter-wave (mmWave) RFEM and one or more sub-millimeter-wave radio frequency integrated circuits (RFICs). In some specific implementations, the one or more sub-millimeter-wave RFICs may be physically decoupled from the millimeter-wave RFEM. The RFIC may include connectors to one or more antennas or antenna arrays (see, for example, below). Figure 10 The antenna array 1011 is used, and the RFEM can be connected to multiple antennas. In an alternative embodiment, the radio functions of both millimeter wave and sub-millimeter wave can be implemented in the same physical RFEM 915 that combines both millimeter wave antennas and sub-millimeter wave antennas.

[0139] The memory circuitry 920 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuitry 920 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM), and / or synchronous dynamic RAM (SDRAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as flash memory), phase-change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuitry 920 may be developed according to the Joint Electronic Equipment Committee (JEDEC) designs based on Low Power Double Data Rate (LPDDR), such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuitry 920 can be implemented as one or more of the following: solder-in packaged integrated circuits, single-die packages (SDP), dual-die packages (DDP), or quad-die packages (Q17P), socket memory modules, dual in-line memory modules (DIMMs) including micro DIMMs or mini DIMMs, and / or soldered to a motherboard via a ball grid array (BGA). In low-power implementations, the memory circuitry 920 may be an on-chip memory or register associated with application circuitry 905. To provide persistent storage for information such as data, applications, operating systems, etc., the memory circuitry 920 may include one or more mass storage devices, which may include, in particular, solid-state drives (SSDDs), hard disk drives (HDDs), miniature HDDs, resistance-changing memories, phase-change memories, holographic memories, or chemical memories. For example, the computer platform 900 may be integrated with... and 3D XPOINT memory.

[0140] The removable memory circuitry 923 may include devices, circuitry, enclosures / housings, ports, or sockets for coupling portable data storage devices to the platform 900. These portable data storage devices may be used for mass storage and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, Micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical discs, external HDDs, etc.

[0141] Platform 900 may also include interface circuitry (not shown) for connecting external devices to platform 900. External devices connected to platform 900 via this interface circuitry include sensor circuitry 921 and electromechanical components (EMC) 922, as well as a removable memory device coupled to removable memory circuitry 923.

[0142] Sensor circuit 921 includes devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units (IMUs) including accelerometers, gyroscopes, and / or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, and / or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture devices); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0143] EMC 922 includes devices, modules, or subsystems intended to enable platform 900 to change its state, position, and / or orientation, or to move or control mechanisms or (sub)systems. Additionally, EMC 922 can be configured to generate messages / signaling and send messages / signaling to other components of platform 900 to indicate the current state of EMC 922. Examples of EMC 922 include one or more power switches, relays (including electromechanical relays (EMRs) and / or solid-state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, propellers, pawls, clamps, hooks, and / or other similar electromechanical components. In embodiments, platform 900 is configured to operate one or more EMC 922s based on one or more captured events and / or commands or control signals received from service providers and / or various clients.

[0144] In some implementations, the interface circuitry can connect platform 900 to positioning circuitry 945. Positioning circuitry 945 includes circuitry for receiving and decoding signals transmitted / broadcast by a GNSS positioning network. Examples of navigation satellite constellations (or GNSS) may include the US GPS, Russia's GLONASS, the EU's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.). Positioning circuitry 945 includes various hardware components (e.g., hardware devices such as switches, filters, amplifiers, antenna elements, etc.) for facilitating OTA communication to communicate with components of the positioning network, such as navigation satellite constellation nodes. In some implementations, positioning circuitry 945 may include a miniature PNT IC that performs position tracking / estimation using a master timing clock without GNSS assistance. Positioning circuitry 945 may also be part of or interact with baseband circuitry 810 and / or RFEM 915 to communicate with nodes and components of the positioning network. The positioning circuit 945 can also provide location data and / or time data to the application circuit 905, which can use the data to synchronize operations with various infrastructures (e.g., radio base stations) for use in turn-by-turn navigation applications, etc.

[0145] In some implementations, the interface circuitry can connect platform 900 to near-field communication (NFC) circuitry 940. NFC circuitry 940 is configured to provide contactless short-range communication based on radio frequency identification (RFID) standards, where magnetic field sensing is used to enable communication between NFC circuitry 940 and NFC-enabled devices (e.g., “NFC contacts”) external to platform 900. NFC circuitry 940 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller can be a chip / IC that provides NFC functionality to NFC circuitry 940 by executing NFC controller firmware and an NFC stack. The NFC stack can be executed by the processor to control the NFC controller, and the NFC controller firmware can be executed by the NFC controller to control the antenna element to transmit short-range RF signals. The RF signals can power passive NFC tags (e.g., microchips embedded in stickers or wristbands) to transmit stored data to NFC circuitry 940, or initiate data transfer between NFC circuitry 940 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) located near platform 900.

[0146] The driving circuitry 946 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 900. The driving circuitry 946 may include various drivers that allow other components of the platform 900 to interact with or control various input / output (I / O) devices that may exist within or be connected to the platform. For example, the driving circuitry 946 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface of the platform 900; a sensor driver for acquiring sensor readings of sensor circuitry 921 and controlling and allowing access to sensor circuitry 921; an EMC driver for acquiring actuator position of EMC 922 and / or controlling and allowing access to EMC 922; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0147] The power management integrated circuit (PMIC) 925 (also referred to as the "power management circuit 925") manages the power supplied to various components of the platform 900. Specifically, relative to the baseband circuit 910, the PMIC 925 controls power selection, voltage scaling, battery charging, or DC-DC conversion. The PMIC 925 is typically included when the platform 900 can be powered by the battery 930, for example, when the device is included in UE 501, 601, 701.

[0148] In some implementations, the PMIC 925 can be controlled or otherwise integrated into various power-saving mechanisms of the platform 900. For example, if the platform 900 is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, it can enter a state known as Discontinuous Receive (DRX) after a period of inactivity. During this state, the platform 900 can power down for short intervals to conserve power. If there is no data traffic activity for an extended period, the platform 900 can transition to the RRC_Idle state, where the device disconnects from the network and does not perform operations such as channel quality feedback or handover. The platform 900 enters a very low-power state and performs paging, where the device periodically wakes up again to listen to the network before powering down again. The platform 900 may not receive data in this state; to receive data, the platform must transition back to the RRC_Connected state. Additional power-saving modes can allow the device to be inaccessible from the network for longer than the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will result in significant latency, which is assumed to be acceptable.

[0149] Battery 930 can power platform 900, but in some examples, platform 900 may be mounted in a fixed location and may have a power source coupled to the grid. Battery 930 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in V2X applications, battery 930 may be a typical lead-acid automotive battery.

[0150] In some implementations, battery 930 may be a "smart battery," which includes or is coupled to a battery management system (BMS) or battery monitoring integrated circuit. The BMS may be included in platform 900 to track the state of charge (SoCh) of battery 930. The BMS can be used to monitor other parameters of battery 930, such as state of health (SoH) and state of function (SoF) to provide fault prediction. The BMS can transmit information about battery 930 to application circuitry 905 or other components of platform 900. The BMS may also include an analog-to-digital converter (ADC) that allows application circuitry 905 to directly monitor the voltage of battery 930 or the current from battery 930. Battery parameters can be used to determine actions that platform 900 can perform, such as transmission frequency, network operation, sensing frequency, etc.

[0151] A power block coupled to the mains or other power source can be coupled to the BMS to charge the battery 930. In some examples, a wireless power receiver can replace the power block XS30 to wirelessly obtain power, for example, via a loop antenna in the computer platform 900. In these examples, wireless battery charging circuitry can be included in the BMS. The specific charging circuitry chosen may depend on the size of the battery 930 and therefore on the required current. Charging can be performed using the aviation fuel standards published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Radio Power Alliance, or the Rezence charging standard published by the Radio Power Alliance.

[0152] User interface circuitry 950 includes various input / output (I / O) devices present within or connected to platform 900, and includes one or more user interfaces designed to enable user interaction with platform 900 and / or peripheral component interfaces designed to enable interaction with peripheral components of platform 900. User interface circuitry 950 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual device for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number and / or combination of audio or visual displays, particularly one or more simple visual outputs / indicators (e.g., binary status indicators (e.g., light-emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of platform 900. Output device circuitry may also include speakers or other audio transmitting devices, printers, etc. In some embodiments, sensor circuitry 921 may be used as input device circuitry (e.g., image capture devices, motion capture devices, etc.) and one or more EMCs may be used as output device circuitry (e.g., actuators for providing haptic feedback, etc.). In another example, NFC circuitry may be included for reading electronic tags and / or connecting to another NFC-enabled device, the NFC circuitry including an NFC controller and processing device coupled to an antenna element. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, USB ports, audio jacks, power interfaces, etc.

[0153] Although not shown, components of platform 900 may communicate with each other using suitable bus or interconnect (IX) technologies, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, Time Triggered Protocol (TTP) systems, FlexRay systems, or any number of other technologies. The bus / IX may be a proprietary bus / IX, for example, used in a SoC-based system. Other bus / IX systems, such as I... 2 Interfaces include C-type interface, SPI interface, point-to-point interface, and power bus, etc.

[0154] Figure 10 Exemplary components of a baseband circuit 100 and a radio front-end module (RFEM) 1015 according to various embodiments are shown. The baseband circuit 1010 corresponds to... Figure 8 The baseband circuit 810 and Figure 9 The baseband circuit 910. RFEM 1015 corresponds to respectively Figure 8 RFEM 815 and Figure 9 The RFEM 915. As shown in the figure, the RFEM 1015 may include a radio frequency (RF) circuit 1006, a front-end module (FEM) circuit 1008, and an antenna array 1011 coupled together as shown in the figure.

[0155] Baseband circuit 1010 includes circuitry and / or control logic components configured to perform various radio / network protocols and radio control functions that enable communication with one or more radio networks via RF circuit 1006. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, RF shifting, etc. In some embodiments, the modulation / demodulation circuitry of baseband circuit 1010 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuit 1010 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Implementations of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments. Baseband circuit 1010 is configured to process baseband signals received from the receive signal path of RF circuit 1006 and to generate baseband signals for the transmit signal path of RF circuit 1006. Baseband circuit 1010 is configured to interact with application circuits 805 / 905 (see...). Figure 8 and Figure 9 The baseband circuit 1010 is connected to generate and process baseband signals and control the operation of the RF circuit 1006. The baseband circuit 1010 can handle various radio control functions.

[0156] The aforementioned circuitry and / or control logic components of the baseband circuitry 1010 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 1004A, a 4G / LTE baseband processor 1004B, a 5G / NR baseband processor 1004C, or other baseband processors 1004D for other existing, developing, or future generations (e.g., sixth generation (6G)). In other embodiments, some or all of the functions of the baseband processors 1004A-1004D may be included in modules stored in memory 1004G and executed via a central processing unit (CPU) 1004E. In other embodiments, some or all of the functions of the baseband processors 1004A-1004D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with appropriate bitstreams or logic blocks stored in the respective memory cells. In various implementations, memory 1004G may store program code for a real-time operating system (RTOS), which, when executed by CPU 1004E (or other baseband processor), will enable CPU 1004E (or other baseband processor) to manage resources of baseband circuitry 1010, schedule tasks, etc. Examples of RTOS may include those developed by... The provided Operating System Embedded (OSE) TM By Mentor Nucleus RTOS provided TM By Mentor Versatile Real-Time Executive (VRTX) is provided by Express. ThreadX provided TM ,Depend on The provided FreeRTOS and REX OS are based on the Open Kernel (OK). The provided OKL4, or any other suitable RTOS, such as those discussed herein. Furthermore, the baseband circuitry 1010 includes one or more audio digital signal processors (DSPs) 1004F. The audio DSP 1004F includes elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements.

[0157] In some implementations, each processor in processors 1004A-1004E includes a corresponding memory interface for sending data to / receiving data from memory 1004G. Baseband circuitry 1010 may also include one or more interfaces for communicatively coupling to other circuitry / devices, such as interfaces for sending data to / receiving data from memory external to baseband circuitry 1010; and interfaces for sending data to / receiving data from memory external to baseband circuitry 1010. Figures 8 to 10 Application circuit interface for sending data to / receiving data from the application circuit 805 / 905; used for sending data to / receiving data from the application circuit. Figure 10 RF circuit 1006 is an RF circuit interface for transmitting / receiving data from / from one or more wireless hardware components (e.g., near field communication (NFC) components). Low power components A wireless hardware connection interface for transmitting data from / receiving data from these wireless hardware components; and a power management interface for sending power or control signals to / receiving power or control signals from the PMIC 925.

[0158] In an alternative embodiment (which may be combined with the embodiments described above), the baseband circuit 1010 includes one or more digital baseband systems coupled to each other and to a CPU subsystem, an audio subsystem, and an interface subsystem via interconnect subsystems. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, a network-on-chip (NOC) architecture, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include DSP circuitry, buffer memory, program memory, voice processing accelerator circuitry, data converter circuitry such as analog-to-digital converter circuitry and digital-to-analog converter circuitry, analog circuitry including one or more amplifiers and filters, and / or other similar components. In one aspect of this disclosure, the baseband circuit 1010 may include protocol processing circuitry having one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and / or radio frequency circuitry (e.g., radio front-end module 1015).

[0159] although Figure 10Not shown, but in some embodiments, baseband circuitry 1010 includes various processing devices (e.g., a "multi-protocol baseband processor" or "protocol processing circuit") for operating one or more wireless communication protocols and various processing devices for implementing PHY layer functions. In these embodiments, PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuit operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when baseband circuitry 1010 and / or RF circuitry 1006 are part of millimeter-wave communication circuitry or some other suitable cellular communication circuitry, the protocol processing circuit can operate LTE protocol entities and / or 5G / NR protocol entities. In the first example, the protocol processing circuit will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when baseband circuitry 1010 and / or RF circuitry 1006 are part of a Wi-Fi communication system, the protocol processing circuit can operate one or more IEEE-based protocols. In the second example, the protocol processing circuit will operate Wi-Fi MAC and Logical Link Control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 1004G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using the data. The baseband circuitry 1010 may also support radio communication using more than one wireless protocol.

[0160] The various hardware components of the baseband circuit 1010 discussed herein can be implemented, for example, as a soldered substrate comprising one or more integrated circuits (ICs), a single-packaged IC soldered to a main board, or a multi-chip module containing two or more ICs. In one example, components of the baseband circuit 1010 may be suitably combined in a single chip or a single chipset, or disposed on the same board. In another example, some or all of the components of the baseband circuit 1010 and the RF circuit 1006 may be implemented together, such as, for example, a system-on-a-chip (SOC) or a system-in-package (SiP). In yet another example, some or all of the components of the baseband circuit 1010 may be implemented as a separate SoC communicatively coupled to the RF circuit 1006 (or multiple instances of the RF circuit 1006). In yet another example, some or all of the components of the baseband circuit 1010 and the application circuits 805 / 905 may be implemented together as a separate SoC mounted to the same board (e.g., a “multi-chip package”).

[0161] In some implementations, baseband circuit 1010 can provide communication compatible with one or more radio technologies. For example, in some implementations, baseband circuit 1010 can support communication with E-UTRAN or other WMAN, WLAN, WPAN. Implementations in which baseband circuit 1010 is configured to support radio communication with more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0162] RF circuit 1006 enables communication with a wireless network via a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 1006 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 1006 may include a receive signal path, which may include circuitry for down-converting the RF signal received from FEM circuit 1008 and providing a baseband signal to baseband circuit 1010. RF circuit 1006 may also include a transmit signal path, which may include circuitry for up-converting the baseband signal provided by baseband circuit 1010 and providing an RF output signal for transmission to FEM circuit 1008.

[0163] In some embodiments, the receive signal path of RF circuit 1006 may include mixer circuit 1006a, amplifier circuit 1006b, and filter circuit 1006c. In some embodiments, the transmit signal path of RF circuit 1006 may include filter circuit 1006c and mixer circuit 1006a. RF circuit 1006 may also include synthesizer circuit 1006d for synthesizing frequencies used by mixer circuit 1006a for both the receive and transmit signal paths. In some embodiments, mixer circuit 1006a for the receive signal path may be configured to down-convert the RF signal received from FEM circuit 1008 based on the synthesized frequency provided by synthesizer circuit 1006d. Amplifier circuit 1006b may be configured to amplify the down-converted signal, and filter circuit 1006c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal can be provided to the baseband circuit 1010 for further processing. In some embodiments, although not required, the output baseband signal may be a zero-frequency baseband signal. In some embodiments, the mixer circuit 1006a receiving the signal path may include a passive mixer, but the scope of the embodiments is not limited in this respect.

[0164] In some implementations, the mixer circuit 1006a of the transmit signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1006d to generate an RF output signal for the FEM circuit 1008. The baseband signal can be provided by the baseband circuit 1010 and can be filtered by the filter circuit 1006c.

[0165] In some embodiments, the mixer circuit 1006a for the receive signal path and the mixer circuit 1006a for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and quadrature upconversion, respectively. In some embodiments, the mixer circuit 1006a for the receive signal path and the mixer circuit 1006a for the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 1006a for the receive signal path and the mixer circuit 1006a for the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 1006a for the receive signal path and the mixer circuit 1006a for the transmit signal path may be configured for superheterodyne operation.

[0166] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 1006 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuit 1010 may include a digital baseband interface for communicating with the RF circuit 1006.

[0167] In some dual-mode implementations, separate radio IC circuits can be provided to process signals for each spectrum, but the scope of the implementation is not limited in this respect.

[0168] In some implementations, synthesizer circuit 1006d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of implementations is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 1006d may be a Δ-∑ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0169] The synthesizer circuit 1006d can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 1006a of the RF circuit 1006. In some embodiments, the synthesizer circuit 1006d can be a fractional N / N+1 synthesizer.

[0170] In some implementations, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not mandatory. The divider control input may be provided by the baseband circuit 1010 or the application circuit 805 / 905 according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 805 / 905.

[0171] The synthesizer circuit 1006d of the RF circuit 1006 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay elements may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. Thus, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0172] In some embodiments, synthesizer circuit 1006d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and may be used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at that carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, RF circuit 1006 may include an IQ / polarity converter.

[0173] FEM circuit 1008 may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array 1011, amplify the received signals, and provide an amplified version of the received signals to RF circuit 1006 for further processing. FEM circuit 1008 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by RF circuit 1006 for transmission by one or more antenna elements in antenna array 1011. In various embodiments, amplification via the transmit or receive signal path may be performed only in RF circuit 1006, only in FEM circuit 1008, or in both RF circuit 1006 and FEM circuit 1008.

[0174] In some embodiments, FEM circuit 1008 may include a TX / RX switch to switch between transmit and receive mode operation. FEM circuit 1008 may include a receive signal path and a transmit signal path. The receive signal path of FEM circuit 1008 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to RF circuit 1006). The transmit signal path of FEM circuit 1008 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by RF circuit 1006), and one or more filters for generating the RF signal for subsequent transmission by one or more antenna elements of antenna array 1011.

[0175] Antenna array 1011 includes one or more antenna elements, each configured to convert electrical signals into radio waves to travel through the air and to convert received radio waves back into electrical signals. For example, a digital baseband signal provided by baseband circuit 1010 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of antenna array 1011, which includes one or more antenna elements (not shown). Antenna elements can be omnidirectional, directional, or a combination thereof. Antenna elements can be arranged in various configurations as known and / or discussed herein. Antenna array 1011 may include microstrip antennas or printed antennas fabricated on the surface of one or more printed circuit boards. Antenna array 1011 may be formed as a patch of metal foil of various shapes (e.g., a patch antenna) and may be coupled to RF circuit 1006 and / or FEM circuit 1008 using metal transmission lines, etc.

[0176] The processors of application circuitry 805 / 905 and baseband circuitry 1010 are elements that can be used to execute one or more instances of the protocol stack. For example, the processor of baseband circuitry 1010 can be used alone or in combination to execute layer 3, layer 2, or layer 1 functions, while the processor of application circuitry 805 / 905 can utilize data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include the RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include the MAC layer, RLC layer, and PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 may include the PHY layer of the UE / RAN node, which will be described in further detail below.

[0177] Figure 11 Various protocol functions that can be implemented in wireless communication devices according to various implementation schemes are illustrated. Specifically, Figure 11This includes an arrangement 1100 illustrating the interconnections between various protocol layers / entities. It provides various protocol layers / entities operating in conjunction with 5G / NR system standards and LTE system standards. Figure 11 The following description, but Figure 11 Some or all of these aspects may also be applicable to other wireless communication network systems.

[0178] In addition to other higher-layer functions not shown, the protocol layers of arrangement 1100 may also include one or more of PHY 1110, MAC 1120, RLC 1130, PDCP 1140, SDAP 1147, RRC 1155, and NAS layer 1157. These protocol layers may include one or more service access points (e.g., capable of providing communication between two or more protocol layers) that can provide communication between two or more protocol layers. Figure 11 Items 1159, 1156, 1150, 1149, 1145, 1135, 1125, and 1115.

[0179] PHY 1110 can transmit and receive physical layer signals 1105, which can be received from or transmitted to one or more other communication devices. Physical layer signals 1105 may include one or more physical channels, such as those discussed herein. PHY 1110 can also perform link adaptive or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers (e.g., RRC1155). PHY 1110 can further perform error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and MIMO antenna processing. In some embodiments, instances of PHY 1110 may process requests from instances of MAC 1120 and provide indications to them via one or more PHY-SAP 1115. According to some embodiments, requests and indications transmitted via PHY-SAP 1115 may include one or more transport channels.

[0180] An instance of MAC 1120 can process requests from instances of RLC 1130 and provide instructions to them via one or more MAC-SAP 1125s. These requests and instructions transmitted via MAC-SAP 1125s may include one or more logical channels. MAC 1120 can perform mapping between logical channels and transport channels, multiplexing MAC SDUs from one or more logical channels onto a TB to be delivered to PHY 1110 via a transport channel, demultiplexing MAC SDUs from a TB delivered from PHY 1110 via a transport channel onto one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via HARQ, and logical channel prioritization.

[0181] An instance of RLC 1130 can process requests from instances of PDCP 1140 and provide them with instructions via one or more Radio Link Control Service Access Points (RLC-SAP) 1135. These requests and instructions transmitted via RLC-SAP 1135 may include one or more RLC channels. RLC 1130 can operate in several modes, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). RLC 1130 can perform transmission of Upper Layer Protocol Data Units (PDUs), error correction via Automatic Repeat Request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLCSDUs for UM and AM data transmission. RLC 1130 can also resegment RLC data PDUs for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.

[0182] An instance of PDCP 1140 can process and provide instructions to instances of RRC 1155 and / or SDAP 1147 via one or more Packet Data Convergence Protocol Service Points (PDCP-SAP) 1145. These requests and instructions transmitted via PDCP-SAP 1145 may include one or more radio bearers. PDCP 1140 can perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform sequential delivery of upper-layer PDUs during lower-layer re-establishment, eliminate duplication of lower-layer SDUs during lower-layer re-establishment for radio bearers mapped on RLCAM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discarding, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0183] An instance of SDAP 1147 can process requests from one or more higher-layer protocol entities and provide them with indications via one or more SDAP-SAP 1149s. These requests and indications transmitted via SDAP-SAP 1149s may include one or more QoS flows. SDAP 1147 can map QoS flows to DRBs and vice versa, and can also tag QFIs in DL and UL packets. A single SDAP entity 1147 can be configured for a single PDU session. In the UL direction, NG-RAN 510 can control the mapping of QoS flows to DRBs in two different ways (reflective mapping or explicit mapping). For reflective mapping, UE 501's SDAP 1147 can monitor the QFI of DL packets for each DRB and can apply the same mapping for packets flowing in the UL direction. For DRBs, UE 501's SDAP 1147 can map UL packets belonging to a QoS flow that corresponds to the QoS flow ID and PDU session observed in the DL packets of that DRB. To implement reflection mapping, the NG-RAN 710 can tag DL packets with QoS flow IDs via the Uu interface. Explicit mapping may involve the RRC 1155 configuring the SDAP 1147 with explicit mapping rules from QoS flows to the DRB; these rules can be stored and followed by the SDAP 1147. In implementations, the SDAP 1147 may be used only in NR-specific implementations and may not be used in LTE-specific implementations.

[0184] RRC 1155 can be configured with aspects of one or more protocol layers via one or more Management Service Access Points (M-SAPs), which may include one or more instances of PHY 1110, MAC 1120, RLC 1130, PDCP 1140, and SDAP 1147. In an implementation, an instance of RRC 1155 may handle requests from one or more NAS entities 1157 and provide them with instructions via one or more RRC-SAPs 1156. The main services and functions of RRC 1155 may include broadcasting system information (e.g., included in NAS-related MIBs or SIBs), broadcasting system information related to the Access Layer (AS), paging, establishment, maintenance, and release of RRC connections between UE 501 and RAN 510 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. These MIBs and SIBs may include one or more IEs, each of which may include a separate data field or data structure.

[0185] The NAS 1157 forms the highest layer of the control plane between UE 501 and AMF 721. The NAS 1157 supports the mobility and session management procedures of UE 501 to establish and maintain IP connections between UE 501 and P-GW in LTE systems.

[0186] According to various implementation schemes, one or more protocol entities deployed in 1100 may be implemented in UE 501, RAN node 511, AMF 721 in NR implementation or MME 621 in LTE implementation, UPF 702 in NR implementation or S-GW 622 and P-GW 623 in LTE implementation, etc., for use in the control plane or user plane communication protocol stack between the aforementioned devices. In such implementation schemes, one or more protocol entities that may be implemented in one or more of UE 501, gNB 511, AMF 721, etc., may communicate with corresponding peer protocol entities that may be implemented in another device or on another device (using the services of the corresponding lower-level protocol entity to perform such communication). In some implementations, the gNB-CU of gNB 511 may host the RRC 1155, SDAP 1147, and PDCP 1140 of gNB controlling one or more gNB-DU operations, and the gNB-DU of gNB 511 may each host the RLC 1130, MAC 1120, and PHY 1110 of gNB 511.

[0187] In the first example, the control plane protocol stack may include NAS 1157, RRC 1155, PDCP 1140, RLC 1130, MAC 1120, and PHY 1110 in order from the highest to the lowest layer. In this example, the upper layer 1160 may be built on top of NAS 1157, which includes IP layer 1161, SCTP 1162, and application layer signaling protocol (AP) 1163.

[0188] In a specific NR implementation, AP 1163 may be an NG application protocol layer (NGAP or NG-AP) 1163 for an NG interface 513 that is limited between NG-RAN nodes 511 and AMF 721, or AP 1163 may be an Xn application protocol layer (XnAP or Xn-AP) 1163 for an Xn interface 512 that is limited between two or more RAN nodes 511.

[0189] NG-AP 1163 can support the functionality of NG interface 513 and may include an initial procedure (EP). The NG-AP EP can be the interaction unit between NG-RAN node 511 and AMF 721. NG-AP 1163 services may include two groups: UE-related services (e.g., services related to UE 501) and non-UE-related services (e.g., services related to the entire NG interface instance between NG-RAN node 511 and AMF 721). These services may include functions, including but not limited to: paging functions for sending paging requests to the NG-RAN node 511 involved in a specific paging area; UE context management functions for allowing AMF 721 to establish, modify, and / or release UE contexts in AMF 721 and NG-RAN node 511; mobility functions for UE 501 in ECM-CONNECTED mode, for intra-system HO support of mobility within the NG-RAN, and for inter-system HO support of mobility from / to EPS systems; NAS signaling transmission functions for transmitting or rerouting NAS messages between UE 501 and AMF 721; NAS node selection functions for determining the association between AMF 721 and UE 501; NG interface management functions for setting up the NG interface and monitoring for errors via the NG interface; warning message transmission functions for providing means of transmitting warning messages or canceling ongoing warning message broadcasts via the NG interface; and functions for transmitting warning messages via CN. 520 is a configuration transfer function that requests and transfers RAN configuration information (e.g., SON information, performance measurement (PM) data, etc.) between two RAN nodes 511; and / or other similar functions.

[0190] XnAP 1163 supports the functions of Xn interface 512 and may include XnAP basic mobility procedures and XnAP global procedures. XnAP basic mobility procedures may include processes for handling UE mobility within NG RAN 511 (or E-UTRAN 610), such as handover preparation and cancellation procedures, SN state transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, and procedures related to dual connectivity. XnAP global procedures may include procedures independent of a specific UE 501, such as Xn interface setup and reset procedures, NG-RAN update procedures, and cell activation procedures.

[0191] In a specific LTE implementation, AP 1163 may be an S1 application protocol layer (S1-AP) 1163 for an S1 interface 513 defined between E-UTRAN node 511 and MME, or AP 1163 may be an X2 application protocol layer (X2AP or X2-AP) 1163 for an X2 interface 512 defined between two or more E-UTRAN nodes 511.

[0192] The S1 Application Protocol Layer (S1-AP) 1163 supports the functions of the S1 interface and, similar to the previously discussed NG-AP, may include an S1-AP EP. The S1-AP EP can be the interaction unit between the E-UTRAN node 511 and the MME 621 within the LTE CN 520. The S1-AP 1163 services may include two sets: UE-associated services and non-UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM), and configuration transmission.

[0193] X2AP 1163 supports the functions of X2 interface 512 and may include X2AP basic mobility procedures and X2AP global procedures. X2AP basic mobility procedures may include procedures for handling UE mobility within E-UTRAN 520, such as handover preparation and cancellation procedures, SN state transmission procedures, UE context retrieval and UE context release procedures, RAN paging procedures, and procedures related to dual connectivity. X2AP global procedures may include procedures independent of a specific UE 501, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, and cell activation procedures.

[0194] The SCTP layer (optionally referred to as the SCTP / IP layer) 1162 provides guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in an NR implementation, or S1-AP or X2AP messages in an LTE implementation). SCTP 1162 may, in part, rely on the IP protocol supported by IP 1161 to ensure reliable delivery of signaling messages between RAN node 511 and AMF 721 / MME 621. The Internet Protocol layer (IP) 1161 can be used to perform packet addressing and routing functions. In some implementations, IP layer 1161 may use point-to-point transmission to deliver and transmit PDUs. In this regard, RAN node 511 may include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.

[0195] In the second example, the user plane protocol stack may include SDAP 1147, PDCP 1140, RLC 1130, MAC 1120, and PHY 1110 in order from the highest to the lowest layer. The user plane protocol stack can be used for communication between UE501, RAN node 511, and UPF 702 in an NR implementation, or between S-GW 622 and P-GW 623 in an LTE implementation. In this example, the upper layer 1151 may be built on top of SDAP 1147 and may include User Datagram Protocol (UDP) and IP Security Layer (UDP / IP) 1152, General Packet Radio Service (GPRS) Tunneling Protocol for User Plane Layer (GTP-U) 1153, and User Plane PDU Layer (UPPDU) 1163.

[0196] The transport network layer 1154 (also known as the "transport layer") can be built on top of IP transport, and GTP-U 1153 can be used on top of the UDP / IP layer 1152 (which includes the UDP layer and the IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also known as the "Internet layer") can be used to perform packet addressing and routing functions. The IP layer can assign IP addresses to user data packets in any of the formats, such as IPv4, IPv6, or PPP.

[0197] The GTP-U 1153 can be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data can be packets in any of the IPv4, IPv6, or PPP formats. The UDP / IP 1152 provides checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication for selected data streams. RAN node 511 and S-GW 622 can exchange user plane data via the S1-U interface through a protocol stack including L1 layer (e.g., PHY 1110), L2 layer (e.g., MAC 1120, RLC 1130, PDCP 1140, and / or SDAP 1147), UDP / IP layer 1152, and GTP-U 1153. The S-GW 622 and P-GW 623 can exchange user plane data via an S5 / S8a interface through a protocol stack including L1, L2, UDP / IP layer 1152, and GTP-U 1153. As previously discussed, the NAS protocol supports the mobility and session management procedures of UE 501 to establish and maintain the IP connection between UE 501 and P-GW 623.

[0198] Furthermore, despite Figure 11Not shown, but the application layer may exist above AP 1163 and / or transport network layer 1154. The application layer may be a layer where users of UE 501, RAN node 511, or other network elements interact with software applications, such as those executed by application circuitry 805 or application circuitry 905, respectively. The application layer may also provide one or more interfaces for software applications to interact with the communication systems of UE 501 or RAN node 511, such as baseband circuitry 1010. In some implementations, the IP layer and / or application layer may provide the same or similar functionality as layers 5 through 7 of the Open Systems Interconnection (OSI) model, or portions thereof (e.g., OSI layer 7—application layer, OSI layer 6—presentation layer, and OSI layer 5—session layer).

[0199] Figure 12 This is a block diagram illustrating components, according to some exemplary embodiments, capable of reading instructions from a machine-readable medium or a computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing any one or more of the methods discussed herein. Specifically, Figure 12 A schematic diagram of hardware resources 1200 is shown, including one or more processors (or processor cores) 1210, one or more memory / storage devices 1220, and one or more communication resources 1230, each of which can be communicatively coupled via bus 1240. For implementations utilizing node virtualization (e.g., NFV), an executable hypervisor 1202 provides an execution environment for one or more network slices / subslices to utilize hardware resources 1200.

[0200] Processor 1210 may include, for example, processor 1212 and processor 1214. Processor 1210 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (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 discussed herein), or any suitable combination thereof.

[0201] The memory / storage device 1220 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1220 may include, but is not limited to, any type of volatile or non-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, solid-state storage devices, etc.

[0202] Communication resource 1230 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 1204 or one or more databases 1206 via network 1208. For example, communication resource 1230 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, etc. (or Low-power components Components and other communication components.

[0203] Instructions 1250 may include software, programs, applications, applets, or other executable code for causing at least any one of processors 1210 to perform any or more of the methods discussed herein. Instructions 1250 may reside wholly or partially within processor 1210 (e.g., within the processor's cache memory), memory / storage device 1220, or any suitable combination thereof. Furthermore, any portion of instructions 1250 may be transferred to hardware resource 1200 from any combination of peripheral device 1204 or database 1206. Therefore, the memory of processor 1210, memory / storage device 1220, peripheral device 1204, and database 1206 are examples of computer-readable and machine-readable media.

[0204] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0205] the term

[0206] For the purposes of this document, the following terms and definitions apply to the examples and implementations discussed herein.

[0207] The term "circuit" refers to a circuit or a system of multiple circuits configured to perform a specific function in an electronic device. A circuit or circuit system can be part of or include one or more hardware components configured to provide said function, such as logic circuits, processors (shared, dedicated, or grouped) and / or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), system-on-a-chip (SoCs), system-in-package (SiPs), multi-chip packages (MCPs), digital signal processors (DSPs), etc. Furthermore, the term "circuit" can also refer to a combination of one or more hardware elements and program code for executing program code. Some types of circuits can execute one or more software or firmware programs to provide at least some of said functions. Such combinations of hardware elements and program code can be referred to as a particular type of circuit.

[0208] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and / or transmitting digital data. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures). The terms "application circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may be referred to as "processor circuit".

[0209] As used herein, the terms “memory” and / or “memory circuitry” refer to one or more hardware devices used for storing data, including random access memory (RAM), magnetoresistive RAM (MRAM), phase-change random access memory (PRAM), dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM), core memory, read-only memory (ROM), disk storage media, optical storage media, flash memory devices, or other machine-readable media used for storing data. The term “computer-readable media” may include, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and a variety of other media capable of storing, containing, or carrying instructions or data.

[0210] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.

[0211] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, 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. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0212] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as networked computers, network hardware, network equipment, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN equipment, RAN nodes, gateways, servers, virtualized virtual networks (VNFs), NFVIs, etc.

[0213] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the terms "computer system" and / or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or networking resources.

[0214] As used herein, the terms “appliance,” “computer appliance,” etc., refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide particular computing resources. A “virtual appliance” is a virtual machine image implemented by a device equipped with a hypervisor that virtualizes or emulates a computer appliance, or otherwise dedicates itself to providing particular computing resources.

[0215] The term "element" refers to an indivisible unit with well-defined boundaries at a given level of abstraction, wherein an element can be any type of entity, including, for example, one or more devices, systems, controllers, network elements, modules, etc., or combinations thereof.

[0216] The term "device" refers to a physical entity that is embedded in or attached to another physical entity in its vicinity, and that has the ability to transmit digital information from or to that physical entity.

[0217] The term "entity" refers to different components of an architecture or device, or information transmitted as a payload.

[0218] The term "controller" refers to a component or entity that has the ability to influence a physical entity, such as by changing its state or causing the physical entity to move.

[0219] 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 specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time and / or processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resources" can refer to computing, storage, and / or networking resources provided by physical hardware components. "Virtualized resources" can refer to computing, storage, and / or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resources" or "communication resources" can refer to resources accessible to computer devices / systems via a communication network. The term "system resources" can refer to any kind of shared entity providing services and can include computing resources and / or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0220] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous and / or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar term denoteing a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices via a RAT for transmitting and receiving information.

[0221] As used herein, the term "communication protocol" (wired or wireless) refers to a set of standardized rules or instructions implemented by communication devices and / or systems to communicate with other devices and / or systems, including instructions for packing / unpacking data, modulating / demodulating signals, implementing protocol stacks, etc.

[0222] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0223] This document uses the terms “coupled,” “communicably coupled,” and their derivatives. The term “coupled” can mean two or more elements in direct physical or electrical contact with each other, or two or more elements in indirect contact but still interacting or cooperating with each other, and / or one or more other elements coupled or connected between elements that are said to be coupled to each other. The term “directly coupled” can mean two or more elements in direct contact with each other. The term “communicably coupled” can mean two or more elements that can be in contact with each other by means of communication, including via wires or other interconnections, via wireless communication channels or links, etc.

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

[0225] The term "admission control" refers to the authentication process in a communication system, in which checks are performed before a connection is established to see if the available resources are sufficient for the proposed connection.

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

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

[0228] The term "primary cell" refers to an MCG cell operating on the primary frequency, where the UE either performs an initial connection establishment procedure or initiates a connection reconstruction procedure.

[0229] The term "primary SCG cell" refers to the SCG cell in which the UE performs random access when reconfiguration is performed using the synchronization process used for DC operation.

[0230] The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell of a UE configured with a CA.

[0231] The term "secondary cell group" refers to a subset of serving cells that includes the PSCell of the UE configured with DC and zero or more secondary cells.

[0232] The term "serving cell" refers to the primary cell for a UE that is not configured with CA / DC in RRC_CONNECTED, where there is only one serving cell including the primary cell.

[0233] The term "serving cell" refers to a group of cells that includes the special cell used by a UE configured with CA and in RRC_CONNECTED, and all secondary cells.

[0234] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG used for DC operation; otherwise, the term "special cell" refers to the PCell.

[0235] The invention has been described above in conjunction with specific embodiments thereof. However, it will be apparent that various modifications and alterations can be made thereto without departing from the broader spirit and scope of the invention. Accordingly, the description and drawings should be considered illustrative rather than restrictive. Specific details provided in the description and examples can be used anywhere in one or more embodiments. Various features of different embodiments or examples can be combined differently with some included features and others excluded features to suit a variety of different applications. Examples may include subjects such as methods, means for performing the actions of the method, at least one machine-readable medium including instructions that, when executed by a machine, cause the machine to perform the actions of the method, or actions of a means or system according to the embodiments and examples described herein. Additionally, the various components described herein may be means for performing the operations or functions described according to the embodiments.

[0236] The embodiments described herein provide a user equipment (UE) including a processor configured to: configure the UE to receive one or more repetitions of a transport block (TB) using a first physical downlink shared channel (PDSCH) beam; acquire downlink control information (DCI) including one or more transport configuration indicator (TCI) states; and configure the UE to switch from the first PDSCH beam to a second PDSCH beam, different from the first PDSCH beam, at least in part based on one or more TCI states.

[0237] Other embodiments described herein provide a computer-implemented method comprising: configuring a UE to receive one or more repetitions of a transport block (TB) using a first physical downlink shared channel (PDSCH) beam, acquiring downlink control information (DCI) including one or more transport configuration indicator (TCI) states, and configuring the UE to switch from the first PDSCH beam to a second PDSCH beam different from the first PDSCH beam, at least in part based on one or more TCI states.

[0238] Other embodiments described herein provide a non-transitory computer-readable medium including instructions that, when executed by a processor, configure the processor to: configure the UE to receive one or more repetitions of a transport block (TB) using a first physical downlink shared channel (PDSCH) beam, acquire downlink control information (DCI) including one or more transport configuration indicator (TCI) states, and configure the UE to switch from the first PDSCH beam to a second PDSCH beam different from the first PDSCH beam, at least in part based on one or more TCI states.

[0239] In some examples, the UE may be configured to receive one or more repetitions of a transport block (TB) using a second physical downlink shared channel (PDSCH) beam. In some examples, the processor may determine a first PDSCH target coding rate and a first PDSCH duration for a first set of repetitions of the transport block (TB), and a second PDSCH target coding rate and a second PDSCH duration for a second set of repetitions of the transport block (TB). In some examples, the method may determine a Transmission Configuration Indicator (TCI) state sequence representing downlink (DL) beam repetitions based on received downlink control information (DCI), wherein one or more individual TCI states in the TCI state sequence represent corresponding downlink (DL) beams, and configure the UE to receive one or more DL transmissions (Tx) via one or more DL channels according to the TCI state sequence.

[0240] In some examples, the processor can configure the UE to receive a first set of downlink transmissions (DL Tx) based on a default repetition, and the UE can configure the UE to receive a second set of DL Tx based on one or more repetitions of a TCI state sequence. In some examples, the processor can configure the UE to receive the first set of downlink transmissions (DL Tx) with a first modulation order, a first target coding rate, a first transport block (TB) size, and a first DL channel duration, and the UE can configure the UE to receive the second set of downlink transmissions (DL Tx) with a second modulation order, a second target coding rate, a second transport block (TB) size, and a second DL channel duration DL. Tx has a modulation order, n times the target coding rate, a TB size, and a DL channel duration of 1 / n. In some examples, the second target coding rate is a multiple of the first target coding rate, and the second DL channel duration is a fraction of the first DL channel duration.

[0241] Other features of this embodiment will become apparent from the accompanying drawings and the detailed description described above. Therefore, the true scope of these embodiments will be apparent to a skilled practitioner upon studying the drawings, description, and appended claims.

Claims

1. A method for wireless communication, comprising: generating, for a user equipment (UE), a coherence capability indicator and a power transmission mode capability indicator for transmission to a network entity, wherein: the coherence capability indicator indicates that the UE can be configured to operate in a full-coherent mode, and the power transmission mode capability indicator includes: a first transmission precoding matrix indicator (TPMI) bitmap indicating TPMIs that support full power transmission when the UE is configured for two-port transmission; a first TPMI group index indicating TPMIs that support full power transmission when the UE is configured for four-port non-coherent transmission; and a second TPMI group index indicating TPMIs that support full power transmission when the UE is configured for four-port partial-coherent operation; processing a physical uplink shared channel (PUSCH) configuration received from the network entity; and generating a PUSCH transmission based on the PUSCH configuration and with full transmission power.

2. The method of claim 1, further comprising: generating a first capability indication or a second capability indication for transmission to the network entity, the first capability indication indicating a maximum number of sounding reference signal (SRS) resources per SRS resource set, wherein the maximum number is one, two, or four, and the second capability indication indicating a UE preference regarding having different numbers of SRS ports configured in a same SRS resource set.

3. One or more computer-readable media having instructions that, when executed, cause processing circuitry to: generating a coherency capability indicator and a power transfer mode capability indicator for transmission to a network entity, wherein the coherency capability indicator indicates that a user equipment (UE) is capable of being configured to operate in a full-coherent mode, and the power transfer mode capability indicator includes: a first transmission precoding matrix indicator (TPMI) bitmap indicating TPMIs that support full power transmission when the UE is configured for two-port transmission; a first TPMI group index indicating TPMIs that support full power transmission when the UE is configured for four-port non-coherent transmission; and a second TPMI group index indicating TPMIs that support full power transmission when the UE is configured for four-port partial-coherent operation; process a physical uplink shared channel (PUSCH) configuration received from the network entity; and generate a PUSCH transmission based on the PUSCH configuration and with full transmission power.

4. The one or more computer-readable media of claim 3, wherein the instructions, when executed, further cause the processing circuitry to: transmit, to the network entity, an indication that the UE supports sounding reference signal (SRS) resources with a same number of ports and a maximum amount of one or two SRS resources per SRS resource set.

5. The one or more computer-readable media of claim 3, wherein the PUSCH configuration is to configure the UE to operate in a first mode in which all TPMIs are able to operate with full power settings or a second mode in which a list of TPMIs provided by the UE are able to operate with full power settings.

6. The one or more computer-readable media of claim 3, wherein the power transfer mode capability indicator is to indicate a list of one or more TPMIs that the UE supports for full power transfer.

7. The one or more computer-readable media of claim 3, wherein the instructions, when executed, are further to cause the processing circuitry to: generate a capability indication for transmission to the network entity to indicate whether the UE supports SRS resource sets with SRS resources with different numbers of ports.

8. The one or more computer-readable media of claim 3, wherein the instructions, when executed, are further to cause the UE to: generate a first capability indication or a second capability indication for transmission to the network entity, the first capability indication to indicate a maximum number of SRS resources per SRS resource set, wherein the maximum number is one, two, or four, the second capability indication to indicate a UE preference regarding different numbers of SRS ports configured in a same SRS resource set.

9. A method for wireless communication, the method comprising: processing capability information received from a user equipment (UE), the capability information including coherence capability information and power transfer mode capability information, the coherence capability information to indicate that the UE is capable of being configured to operate in a full-coherent mode, the power transfer mode capability information including: a first transmission precoding matrix indicator (TPMI) bitmap to indicate TPMIs that support full power transfer when the UE is configured for two-port transmission; a first TPMI group index to indicate TPMIs that support full power transfer when the UE is configured for four-port non-coherent transmission; and a second TPMI group index to indicate TPMIs that support full power transfer when the UE is configured for four-port partial-coherent operation; generating a physical uplink shared channel (PUSCH) configuration based on the capability information to configure the UE for PUSCH operation; and outputting the PUSCH configuration for transmission to the UE.

10. The method of claim 9, comprising: processing an indication received from the UE, the indication to indicate that the UE supports SRS resources with a same number of ports and a maximum amount of one or two SRS resources per SRS resource set.

11. The method of claim 9, wherein the power transfer mode capability information includes a capability indication to indicate a capability associated with sounding reference signal (SRS) resource configuration.

12. The method of claim 11, wherein the capability indication is to indicate whether the UE supports SRS resource sets with SRS resources with different numbers of ports.

13. An apparatus for wireless communication, the apparatus comprising: processing circuitry, the processing circuitry to: generating a first capability indication and a second capability indication for transmission to a network entity, the first capability indication indicating one or more TPMIs that a user equipment (UE) supports for full power transmission, the second capability indication indicating a capability associated with sounding reference signal (SRS) resource configuration, wherein the second capability indication indicates that the UE supports SRS resources with different numbers of ports; processing a physical uplink shared channel (PUSCH) configuration received from the network entity; and generating a PUSCH transmission based on the PUSCH configuration and with full transmission power; and an interface circuit coupled to the processing circuit for enabling communication.

14. The apparatus of claim 13, wherein the processing circuit is further configured to generate a third capability indication indicating a maximum number of SRS resources in a set of SRS resources that the UE supports. ​

Images