Half duplex frequency division duplex support in non-terrestrial networks

Abstract

Methods, systems, and computer-readable media for performing operations including determining a scheduling conflict between an uplink transmission and a downlink reception, determining a type of the scheduling conflict, and applying a prioritization rule based in part on the type of the scheduling conflict that prioritizes at least a portion of the uplink transmission or the downlink reception in order to mitigate the scheduling conflict are disclosed.

Description

Technical Field

[0001] This disclosure relates in general to half-duplex frequency division duplex support in non-terrestrial networks. Background Technology

[0002] To increase network coverage and support usage scenarios beyond terrestrial (land) infrastructure capabilities, the 3rd Generation Partnership Project (3GPP) has released standards for integrating non-terrestrial networks (NTNs) into the 5G New Radio (NR) framework. Typically, an NTN includes a network or segments thereof that utilize airborne or spaceborne platforms (e.g., non-geostationary satellites) to implement access nodes or base stations. Summary of the Invention

[0003] This disclosure relates to methods, systems, apparatus, computer programs, or combinations thereof for half-duplex frequency division duplex support in non-terrestrial networks (NTN).

[0004] According to one aspect of this disclosure, a method performed by a User Equipment (UE) is disclosed. The method includes: determining a scheduling conflict between uplink transmission and downlink reception; determining the type of scheduling conflict; and applying a priority ordering rule, in part based on the type of scheduling conflict, to prioritize at least a portion of the uplink transmission or downlink reception in order to mitigate the scheduling conflict.

[0005] The previously described embodiments can be implemented using a computer-implemented method; a non-transitory computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system including computer memory operatively coupled to a hardware processor configured to perform the computer-implemented method or the instructions stored on the non-transitory computer-readable medium. These and other embodiments may optionally include one or more of the following features.

[0006] In some specific implementations, the method also includes a priority sorting part for receiving uplink transmissions or downlink receptions.

[0007] In some specific implementations, determining the type of scheduling conflict includes: determining that the type of scheduling conflict is a conflict that does not repeat in uplink transmission and downlink reception.

[0008] In some implementations, the priority ordering rules prioritize uplink transmissions and downlink receptions based on the corresponding priority indices associated with uplink transmissions and downlink receptions.

[0009] In some specific implementations, the application of priority sorting rules includes: comparing the corresponding priority indices; and determining the priority order of communications based on the higher priority index.

[0010] In some specific implementations, applying priority sorting rules includes: comparing corresponding priority indices; determining that the corresponding priority indices are the same; and, in response, executing one of several alternative options, including: (i) prioritizing uplink transmissions; (ii) prioritizing downlink transmissions; (iii) prioritizing uplink or downlink transmissions based on configuration; and (iv) prioritizing based on the corresponding reception times of the authorization associated with uplink transmissions and downlink receptions.

[0011] In some specific implementations, determining the type of scheduling conflict includes: determining that the type of scheduling conflict is a repeated conflict in at least one of uplink transmission or downlink reception.

[0012] In some implementations, the priority ordering rules prioritize uplink transmissions and downlink receptions based on the corresponding priority indices associated with uplink transmissions and downlink receptions.

[0013] In some specific implementations, downlink reception includes duplication, and the application of priority ordering rules includes determining whether the corresponding priority index of the downlink reception is lower than the corresponding priority index of the uplink transmission; if the corresponding priority index of the downlink reception is lower, then: one of a first plurality of alternative options is executed, the first plurality of alternative options including: (i) prioritizing the first portion of the downlink duplication that does not time overlap with the uplink transmission, but not prioritizing the second portion of the downlink duplication that time overlaps with the uplink transmission; (ii) determining not to prioritize the entire downlink transmission; and (ii) i) Prioritize the third portion of the downlink repeat before it overlaps with the uplink transmission, but not prioritize the downlink repeat at or after it overlaps with the uplink transmission; and if the corresponding priority index of the downlink reception is large, then: execute one of the second plurality of alternative options, which includes: (i) prioritizing the first portion of the downlink repeat that does not overlap with the uplink transmission, but not prioritizing the second portion of the downlink repeat that overlaps with the uplink transmission; and (ii) prioritizing the entire downlink repeat.

[0014] In some specific implementations, determining the type of scheduling conflict includes: determining that the type of scheduling conflict involves a time overlap between existing communication configurations and newly scheduled communication.

[0015] In some specific implementations, the existing communication configuration is an uplink transmission, and the newly scheduled communication overlaps with the uplink transmission in time and is received by the downlink under dynamic licensing scheduling, and the application of priority ordering rules includes: determining a threshold time before the last symbol of the control resource set including dynamic licensing is earlier than the first symbol of the uplink transmission; and responsively prioritizing the uplink transmission.

[0016] In some specific implementations, the existing communication configuration is downlink reception, and the newly scheduled communication is uplink transmission that overlaps with downlink reception in time and is dynamically licensed and scheduled, and the applied priority ordering rules include: determining a threshold time before the last symbol of the control resource set containing dynamic licenses is earlier than the first symbol of the downlink transmission; and responsively prioritizing the downlink transmissions.

[0017] Details of one or more embodiments of these systems and methods are set forth in the following figures and description. Other features, objects, and advantages of these systems and methods will be apparent from the specification, figures, and claims. Attached Figure Description

[0018] Figure 1 Exemplary wireless communication systems according to some specific implementations of this disclosure are shown.

[0019] Figure 2 Examples of repeated conflicts in at least one of the uplink and downlink communications are shown in some specific implementations of this disclosure.

[0020] Figure 3 A flowchart of an exemplary method according to some specific implementations of this disclosure is shown.

[0021] Figure 4 This is a block diagram of an exemplary device architecture based on some specific implementations of this disclosure.

[0022] Figure 5 Examples of wireless communication systems according to some specific implementations of this disclosure are shown.

[0023] Figure 6 Examples of infrastructure equipment according to some specific implementations of this disclosure are shown.

[0024] Figure 7 Exemplary components of a baseband circuit and radio front-end module (RFEM) according to some specific embodiments of this disclosure are shown.

[0025] Figure 8This is a block diagram illustrating components according to some specific embodiments of the present disclosure that are capable of reading instructions from a machine-readable medium or a computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any or more of the methods discussed herein.

[0026] Similar reference symbols in the various figures indicate similar elements. Detailed Implementation

[0027] The 3rd Generation Partnership Project (3GPP) has recently developed reduced-capability devices (also known as "RedCap devices") that operate using features and parameters with lower terminal capabilities. These devices can serve applications including industrial wireless sensors, video surveillance, and wearable devices. Some features developed for RedCap devices include support for half-duplex frequency division duplex (HD-FDD) operation, full-duplex FDD (FD-FDD) operation, and time division duplex mode. For FDD operation, two carrier frequencies exist, one for uplink transmission and the other for f. ul And a f for downlink transmission dl In FD-FDD mode, the UE can transmit and receive communications simultaneously. However, HD-FDD UEs do not support simultaneous transmission and reception to reduce costs, for example, by replacing the duplexer with a switch. A fundamental aspect of HD-FDD is the possibility of providing a sufficiently long protection period during which neither downlink nor uplink transmissions occur. This protection period helps avoid interference between uplink and downlink transmissions.

[0028] In addition, 3GPP has released a standard for integrating non-terrestrial networks (NTN) into the 5G New Radio (NR) framework. The timing lead (TA) applied by the NR NTN UE in RRC_IDLE / INACTIVE and RRC_CONNECTED is given by the following formula:

[0029] [IIT TA =(N TA +N TA，UE-专用 +N TA，通用 +N TA，偏移 )×T C

[0030] In formula [1], N TA For PRACH, it is defined as 0 and updated based on the TA command field in the Msg2 / MsgB and Media Access Control (MAC) Control Element (CE) TA command. TA，UE-专用 It is the TA (Target Aspect) self-estimated by the UE to pre-compensate for service link delay. TA，通用 It is the common TA for network control and can include any timing offsets that the network deems necessary. N with a value of 0 is supported.TA，通用 N TA，偏移 This is the fixed offset used to calculate the TA. It should be noted that the UE cannot assume that the round-trip time (RTT) between the UE and the base station is equal to the TA calculated for Msg1 / MsgA.

[0031] Once RedCap devices are implemented, they are expected to be served by NTN. One potential issue in such systems is the continuous change in the UE's TA caused by moving satellites. Due to this continuous change, the base station serving the UE, such as the gNB (whether satellite or NTN cell gNB), is unaware of the UE's TA (whether the TA is cell-wide or UE-specific). Consequently, simultaneous uplink transmission and downlink reception may occur at the UE side, potentially leading to scheduling conflicts for HD-FDD UEs (e.g., RedCap devices).

[0032] This document discloses methods and systems that enable resource-efficient HD-FDD operation by minimizing signaling overhead for HD-FDD support and avoiding or mitigating scheduling conflicts (such as those caused in NTN). In some implementations, the methods and systems implement priority ordering rules that enable the UE to resolve scheduling conflicts between uplink and downlink communications.

[0033] Figure 1 An exemplary wireless communication system 100 according to some specific implementations is shown. As described below, the wireless communication system 100 may include and / or communicate with non-terrestrial networks. For convenience and not limitation, the exemplary system 100 is described in the context of Long Term Evolution (LTE) and 5th Generation (5G) New Radio (NR) communication standards as defined by the 3GPP technical specifications. More specifically, the wireless communication system 100 is described in the context of a non-standalone (NSA) network combining both LTE and NR, such as an E-UTRA (Evolved Universal Terrestrial Radio Access)-NR Dual Connectivity (EN-DC) network and a NE-DC network. However, the wireless communication system 100 may also be a standalone (SA) network combining only NR. Furthermore, other types of communication standards are also possible, including future 3GPP systems (e.g., 6th Generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0034] like Figure 1As shown, system 100 includes UE 102. UE 102 can be a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), or any mobile or non-mobile computing device, such as consumer electronics, cellular phones, smartphones, feature phones, tablet computers, wearable computing devices, networked or “smart” appliances, MTC devices, M2M, IoT devices, etc. In some examples, UE 102 can be configured to operate according to a specific standard, such as the RedCap standard defined by 3GPP technical specifications. For example, UE 102 can be configured to operate in HD-FDD mode.

[0035] UE 102 can be configured to connect to RAN 110, for example, communicatively coupled. In implementations, RAN 110 can be an NG RAN or 5G RAN, E-UTRAN, or a legacy RAN such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., can refer to RAN 110 operating in NR or 5G system 100, while the term "E-UTRAN," etc., can refer to RAN 110 operating in LTE or 4G system 100. UE 102 utilizes connections (or channels) 103 and 104, each connection including a physical communication interface or layer.

[0036] RAN 110 includes one or more AN nodes or RAN nodes 111a and 111b (collectively referred to as "RAN node 111") that enable connections between 103 and 104. 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 can be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, etc., and can 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 111 (e.g., gNB) operating in NR or 5G system 100, while the terms "E-UT RAN node," etc., can refer to RAN node 111 (e.g., eNB) operating in LTE or 4G system 100. According to various implementation schemes, RAN node 111 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 bandwidth compared to macro cells.

[0037] In some implementations, UE 102 may be configured to implement one or more priority ordering rules 106 that enable the UE to resolve scheduling conflicts between uplink and downlink communications. In some examples, priority ordering rules 106 are associated with scheduling conflict types. Therefore, UE 102 may select the priority ordering rule to apply based on the type of scheduling conflict. In some examples, scheduling conflict types include: (i) conflicts between uplink and downlink communications without duplication; (ii) conflicts between uplink and downlink communications with duplication in at least one of the uplink and downlink communications; and (iii) conflicts involving time overlap between existing transport configurations and newly scheduled transports. It should be noted that priority ordering rules 106 can be applied to any type of uplink transport (e.g., PUSCH / PUCCH / SRS / PRACH) and any type of downlink transport (e.g., PDCCH / PDSCH / CSI-RS / DL PRS).

[0038] In some implementations, UE 102 is configured to apply a first priority ordering rule to a first conflict type involving conflicts between uplink and downlink communications that do not overlap. UE 102 can be configured to apply different implementations of the first priority ordering rule in different scenarios of the first conflict type. A first scenario of the first conflict type occurs when UE 102 has received dynamic downlink grants and dynamic uplink grants. In a first implementation of the first scenario, priority ordering is performed based on the corresponding priority indices associated with the uplink and downlink grants. The corresponding priority index can be, for example, a one-bit index (e.g., for communication in control signals such as DCI). According to the first implementation, UE 102 prioritizes communications with a priority index of "1". For example, if the priority index of PDSCH is "1" and the priority index of PUSCH / PUCCH is "0", the UE prioritizes PDSCH communications. Note that if PUCCH / PUSCH is multiplexed (e.g., using control information), priority ordering is performed by taking the higher priority index value of the multiplexed PUCCH / PUSCH. For example, uplink control information (UCI) with a priority index of "1" is multiplexed on PUCCH / PUSCH, and then PUCCH / PUSCH is considered to also have a priority index of "1".

[0039] However, uplink and downlink communications can have the same priority index. Different alternatives to the first specific implementation of the first priority ordering rule are possible here. UE 102 can be configured to implement any of these alternatives. In the first alternative, the priority ordering between uplink and downlink communications is configured by RAN 110, possibly using RRC configuration or any other signaling method. RAN 110 can prioritize by cell or by UE configuration. In the second alternative, uplink communications take precedence over downlink communications. In this alternative, only PUCCH may take precedence over PDSCH, or both PUCCH and PUSCH may take precedence over PDSCH. This applies to PUCCHs with HARQ-ACK feedback and / or scheduling requests (SR). In the third alternative, downlink communications take precedence over uplink communications. In this alternative, PDSCH may take precedence over PUSCH only, or both PUSCH and PUCCH may take precedence. In the fourth alternative, prioritization is performed according to the specific implementation of the UE (i.e., UE 102 determines the communications to be prioritized). In the fifth alternative, prioritization is based on the time of receipt of the grant (e.g., via downlink control information [DCI]). For example, later received uplink and downlink grants are prioritized.

[0040] In the second implementation of the first scenario, the prioritization of communications is independent of the associated priority index. Different alternatives are possible in this second implementation. UE 102 can be configured to implement any of these alternatives. In the first alternative, the prioritization between uplink and downlink communications is configured by RAN 110, possibly using RRC configuration or any other signaling method. RAN 110 can prioritize by cell or by UE configuration. In the second alternative, uplink communications take precedence over downlink communications. In this alternative, only PUCCH may take precedence over PDSCH, or both PUCCH and PUSCH may take precedence over PDSCH. This applies to PUCCHs with HARQ-ACK feedback and / or SR. In the third alternative, downlink communications take precedence over uplink communications. In this alternative, PDSCH may take precedence over PUSCH only, or both PUSCH and PUCCH may take precedence. In the fourth alternative, prioritization is performed on a UE-specific basis (i.e., UE 102 determines the communications to be prioritized). In the fifth alternative, prioritization is based on the reception time of the licensed DCI. For example, later received uplink and downlink licenses are prioritized.

[0041] When UE 102 has received both a dynamic downlink grant and a configured uplink grant, a second scenario of the first conflict type occurs. In a first implementation of the second scenario, uplink and downlink communications are prioritized based on their respective priority indices associated with the uplink and downlink communications. However, uplink and downlink communications may have the same priority index. Here, different alternatives to the first implementation of the first priority prioritization rule are possible. UE 102 can be configured to implement any of these alternatives. In the first alternative, the priority prioritization between uplink and downlink communications is configured by RAN 110, possibly using RRC configuration or any other signaling method. RAN 110 can prioritize by cell or by UE configuration. In the second alternative, the dynamic downlink grant takes precedence over the configured uplink grant. In the third alternative, priority prioritization is performed for the UE specific implementation (i.e., UE 102 determines which communications to prioritize).

[0042] In the second implementation of the second scenario, dynamic downlink grant takes precedence over configured uplink grant. In the third implementation of the second scenario, priority ordering depends on the UE implementation. In the third implementation of the second scenario, priority ordering is configured by RAN 110 (e.g., by UE or by cell).

[0043] A third scenario of the first conflict type occurs when UE 102 has received downlink semi-persistent scheduling (SPS) and dynamic uplink grant. In a first implementation of the third scenario, uplink and downlink communications are prioritized based on their respective priority indices associated with the uplink and downlink grants. However, uplink and downlink communications may have the same priority index. Here, different alternative schemes are possible. UE 102 can be configured to implement any of these alternative schemes. In the first alternative scheme, the priority ordering between uplink and downlink communications is configured by RAN 110, possibly using RRC configuration or any other signaling method. RAN 110 can prioritize by cell or by UE configuration. In the second alternative scheme, dynamic uplink grant takes precedence over downlink SPS. In the third alternative scheme, priority ordering is performed for the specific UE implementation (i.e., UE 102 determines which communications to prioritize).

[0044] In the second implementation of the third scenario, dynamic uplink grants are prioritized. In the third implementation of the third scenario, priority ranking depends on the UE implementation. In the fourth implementation of the third scenario, priority ranking is configured by RAN 110 (e.g., by UE or by cell).

[0045] When UE 102 has received a downlink SPS and a configured uplink grant, a fourth scenario of the first conflict type occurs. In a first implementation of the third scenario, priority ordering is performed based on the corresponding priority indices associated with the uplink and downlink grants. However, if the associated priority indices are the same, different alternative schemes exist to determine the communications to be prioritized. In the first alternative scheme, priority ordering is based on the UE implementation. In the second alternative scheme, the configured uplink grant is prioritized. In the third alternative scheme, the downlink SPS is prioritized. In the fourth alternative scheme, priority ordering is configured by RAN 110 (e.g., by UE or by cell).

[0046] In the second implementation of the fourth scenario, the configured uplink grants are always prioritized. In the third implementation of the fourth scenario, the downlink SPS is always prioritized. In the fourth implementation of the fourth scenario, the priority ranking depends on the UE implementation. In the fifth implementation of the fourth scenario, the priority ranking is configured by RAN 110 (e.g., by UE or by cell).

[0047] In some implementations, UE 102 is configured to apply a second priority ordering rule to a second conflict type involving duplicate conflicts in at least one of uplink and downlink communications. UE 102 can be configured to apply different implementations of the second priority ordering rule in different scenarios of the second conflict type. A first scenario of the second conflict type occurs when there is a conflict between duplicate downlink and uplink communications. In a first implementation of the first scenario, priority ordering is based on the corresponding priority indices associated with the uplink and downlink communications. If the downlink has a lower priority index than the uplink, UE 102 can be configured using one of several alternative rule schemes. In a first alternative scheme, UE 102 receives downlink duplicates when there is no time overlap with the uplink communications, and does not receive downlink duplicates when there is a time overlap with the uplink communications. In a second alternative scheme, UE 102 determines not to receive the entire downlink duplicate. In the third alternative, UE 102 receives downlink duplicates during time slots before the time slots overlap with uplink communication, and does not receive downlink duplicates during or after time slots that overlap with uplink communication.

[0048] In some implementations, the applied alternative scheme rule depends on whether the downlink communication is SPS downlink or dynamic granting downlink. In dynamic granting downlink, the TDRA (Time Domain Resource Allocation) entry can indicate the number of repetitions. In SPS downlink, the configuration itself can indicate the number of repetitions. For example, the UE can determine to apply a second alternative scheme rule to the SPS downlink and a third alternative scheme rule to the dynamic granting downlink. The selection in different alternative schemes can be configured on a UE or cell basis. Additionally and / or alternatively, the selection in different alternative schemes can depend on UE capabilities.

[0049] Figure 2 Examples of repeated collisions 200 in at least one of uplink and downlink communications, according to some specific implementations, are shown. Figure 2 As shown, there is a conflict between uplink communication 202 (e.g., PUSCH / PUCCH with a guard period) and downlink communication 204 (e.g., PDSCH) with overlap. According to the first alternative scheme rule (Alt 1), UE 102 determines to receive both uplink and downlink communication during non-overlapping time slots. As shown in downlink communication 206, UE 102 does not receive time slots overlapping with the uplink communication. According to the second alternative scheme rule (Alt 2), UE 102 determines not to receive any downlink communication. As shown in downlink communication 208, UE 102 does not receive any downlink time slots. According to the third alternative scheme rule (Alt 3), UE 102 determines not to receive overlapping time slots and any subsequent time slots after the overlapping time slots. As shown in downlink communication 210, UE 102 receives two time slots before the overlapping time slots, but does not receive overlapping downlink time slots or any subsequent downlink time slots in the communication.

[0050] In a first specific implementation of the first scenario (i.e., priority ordering is based on the associated priority index), if the downlink priority index is higher than the uplink priority index, UE 102 can be configured using one of several alternative scheme rules. In the first alternative scheme, downlink duplicates are received when there is no time overlap with uplink communication, but downlink duplicates are not received when there is time overlap with uplink communication. In the second alternative scheme, the entire downlink duplicate is received. The selection in different alternative schemes can be configured per UE or per cell. In addition and / or alternatively, the selection in different alternative schemes may depend on UE capabilities.

[0051] The second scenario involves prioritizing uplink and downlink communications with overlapping times. In this scenario, it is first determined whether the uplink communication has a lower priority index than the downlink communication. If so, UE 102 is configured to use one of several alternative scheme rules. In the first alternative scheme, uplink overlaps at timeslots that do not overlap with downlink communication are transmitted, but overlaps at timeslots that overlap with downlink communication are not transmitted. In the second alternative scheme, the entire uplink communication is not transmitted. In the third alternative scheme, uplink overlaps at timeslots before and after overlapping with downlink communication are transmitted, but uplink overlaps at or after timeslots that overlap with downlink communication are not transmitted.

[0052] However, if uplink communication has a higher priority index than downlink communication, UE 102 is configured to use one of several alternative scheme rules. In the first alternative scheme, uplink duplicates are transmitted when there is no time overlap with downlink communication, but uplink duplicates are not transmitted when there is a time overlap with downlink communication. In the second alternative scheme, the entire uplink duplicate is transmitted.

[0053] In some implementations, different alternatives can be applied to the configured authorized PUSCH and the dynamic authorized PUSCH. In the dynamic authorized PUSCH, the TDRA (Time Domain Resource Allocation) entry can indicate the number of repetitions. In the configured authorized PUSCH, the configuration itself or the activated DCI can indicate the number of repetitions. For example, a second alternative is applied to the configured authorized PUSCH, and a third option is applied to the dynamic authorized PUSCH. Note that the selection in different alternatives can be configured on a UE or cell basis. Furthermore and / or alternatively, the selection in different alternatives can depend on UE capabilities.

[0054] The third scenario involves prioritizing uplink communications with duplicates versus downlink communications with duplicates. This scenario can be handled similarly to the first and second scenarios of the second rule.

[0055] In some implementations, UE 102 is configured to apply a third priority ordering rule to a third conflict type involving time overlap between existing communication configurations and newly scheduled communication. Time overlap may include a protection period. UE 102 can be configured to apply different specific implementations of the third rule in different scenarios of the third conflict type. A first scenario involves a conflict between configured uplink communication and newly received dynamic downlink grants. In this scenario, UE 102 is configured with PUSCH / PUCCH transmissions, and UE 102 receives dynamically granted PDCCHs whose scheduled PDSCHs overlap with PUSCH / PUCCH transmissions. In one implementation, the configured PUSCH / PUCCH is transmitted if the last symbol of the control resource set including the PDCCH is no earlier than a threshold time before the first symbol of the configured PUSCH / PUCCH, regardless of the priority index of the PDCCH and PUSCH / PUCCH.

[0056] The second scenario involves a conflict between the SPS downlink and the newly received dynamic uplink grant PUSCH / PUCCH. In this scenario, UE 102 is configured to receive PDSCH, and then UE 102 receives uplink grants whose scheduled PUSCH and PDSCH reception overlap in time. In one implementation, the configured PDSCH is received if the last symbol of the control resource set containing the uplink grant is not earlier than a threshold time before the first symbol of the configured PDSCH, regardless of the priority indexes of the PDSCH / PDCCH and PUSCH / PUCCH.

[0057] The third scenario involves a conflict between dynamic downlink grants and dynamic uplink grants. In this scenario, if an uplink grant is received first, UE 102 is scheduled to transmit the PUSCH under the uplink grant. Then, UE 102 can receive a downlink grant to receive a PDSCH that overlaps with the PUSCH transmission time. In one specific implementation, if the reception time of the last symbol of the control resource set containing the downlink grant DCI is no earlier than a threshold time before the first symbol of the scheduled PUSCH, the scheduled PUSCH is transmitted and the PDSCH is not received, regardless of the PDSCH priority index.

[0058] However, if a downlink grant is received first, UE 102 is scheduled to receive the PDSCH by the downlink grant. UE 102 can then receive an uplink grant that schedules the UE to transmit the PUSCH at a time overlapping with the PDSCH reception. In one implementation, if the reception time of the last symbol of the control resource set containing the uplink grant DCI is no earlier than a threshold time before the first symbol of the scheduled PDSCH, the scheduled PDSCH is received and the PUSCH is not transmitted, regardless of the PUSCH priority index.

[0059] In some implementations, the threshold time can be a network-configured threshold (e.g., a predetermined threshold), or it can be a threshold time calculated by the UE based on one or more variables. In one example, the threshold time is T as defined in 3GPP TS38.214. proc,2 In some examples, N_2 depends on the SCS or UE capabilities (see Tables 6.4-1 and 6.4-2 in TS38.214).

[0060] It depends on the BWP switching time d_{2,2}

[0061] It is d_{2} reported by the UE.

[0062] Figure 3 A flowchart of an exemplary method 300 according to some specific implementation is shown. For clarity, the following description generally describes method 300 in the context of other figures in this specification. For example, method 300 may be... Figure 1 The method is executed by UE 102. As described above, UE 102 can operate in a wireless communication system 100 that includes a non-terrestrial network (NTN) serving UE 102. Additionally, UE 102 supports half-duplex frequency division duplex (HD-FDD) mode. It should be understood that method 300 can be executed, for example, by any suitable system, environment, software, hardware, or a combination of system, environment, software, and hardware. In some specific implementations, the various steps of method 300 can be run in parallel, in combination, cyclically, or in any order.

[0063] At 302, method 300 includes determining a scheduling conflict between uplink transmission and downlink reception.

[0064] At 304, method 300 includes determining the type of scheduling conflict.

[0065] At step 306, method 300 includes applying a priority ordering rule, in part based on the type of scheduling conflict, to prioritize at least a portion of uplink transmissions or downlink receptions in order to mitigate scheduling conflicts.

[0066] In some implementations, method 300 also includes receiving at least a priority-ordered portion of uplink or downlink transmissions.

[0067] In some specific implementations, determining the type of scheduling conflict includes: determining that the type of scheduling conflict is a conflict that does not repeat in uplink transmission and downlink reception.

[0068] In some implementations, the priority ordering rules prioritize uplink transmissions and downlink receptions based on the corresponding priority indices associated with uplink transmissions and downlink receptions.

[0069] In some specific implementations, the application of priority sorting rules includes: comparing the corresponding priority indices; and determining the priority order of communications based on the higher priority index.

[0070] In some specific implementations, applying priority sorting rules includes: comparing corresponding priority indices; determining that the corresponding priority indices are the same; and, in response, executing one of several alternative options, including: (i) prioritizing uplink transmissions; (ii) prioritizing downlink transmissions; (iii) prioritizing uplink or downlink transmissions based on configuration; and (iv) prioritizing based on the corresponding reception times of the authorization associated with uplink transmissions and downlink receptions.

[0071] In some specific implementations, determining the type of scheduling conflict includes: determining that the type of scheduling conflict is a repeated conflict in at least one of uplink transmission or downlink reception.

[0072] In some implementations, the priority ordering rules prioritize uplink transmissions and downlink receptions based on the corresponding priority indices associated with uplink transmissions and downlink receptions.

[0073] In some specific implementations, downlink reception includes duplication, and the application of priority ordering rules includes determining whether the corresponding priority index of the downlink reception is lower than the corresponding priority index of the uplink transmission; if the corresponding priority index of the downlink reception is lower, then: one of a first plurality of alternative options is executed, the first plurality of alternative options including: (i) prioritizing the first portion of the downlink duplication that does not time overlap with the uplink transmission, but not prioritizing the second portion of the downlink duplication that time overlaps with the uplink transmission; (ii) determining not to prioritize the entire downlink transmission; and (ii) i) Prioritize the third portion of the downlink repeat before it overlaps with the uplink transmission, but not prioritize the downlink repeat at or after it overlaps with the uplink transmission; and if the corresponding priority index of the downlink reception is large, then: execute one of the second plurality of alternative options, which includes: (i) prioritizing the first portion of the downlink repeat that does not overlap with the uplink transmission, but not prioritizing the second portion of the downlink repeat that overlaps with the uplink transmission; and (ii) prioritizing the entire downlink repeat.

[0074] In some specific implementations, determining the type of scheduling conflict includes: determining that the type of scheduling conflict involves a time overlap between existing communication configurations and newly scheduled communication.

[0075] In some specific implementations, the existing communication configuration is an uplink transmission, and the newly scheduled communication overlaps with the uplink transmission in time and is received by the downlink under dynamic licensing scheduling, and the application of priority ordering rules includes: determining a threshold time before the last symbol of the control resource set including dynamic licensing is earlier than the first symbol of the uplink transmission; and responsively prioritizing the uplink transmission.

[0076] In some specific implementations, the existing communication configuration is downlink reception, and the newly scheduled communication is uplink transmission that overlaps with downlink reception in time and is dynamically licensed and scheduled, and the applied priority ordering rules include: determining a threshold time before the last symbol of the control resource set containing dynamic licenses is earlier than the first symbol of the downlink transmission; and responsively prioritizing the downlink transmissions.

[0077] Also disclosed are one or more systems of one or more computers configured to perform the actions of method 300 by means of software, firmware, hardware, or combinations thereof installed on the system that cause the system to perform specific operations or actions during operation. One or more computer programs may be configured to perform the actions of method 300 by means of instructions including instructions that cause a data processing device to perform specific operations or actions when executed by the data processing device.

[0078] Other implementations of this aspect include corresponding computer systems, devices, and computer programs recorded on one or more computer storage devices, all configured to perform the actions of method 300.

[0079] Figure 4 It is used to implement the reference Figures 1 to 3 The block diagram of an example device architecture 400 describing the features and processes is shown. For example, architecture 400 can be used to implement a user equipment (UE), such as UE 102. Architecture 400 can be used to generate reference... Figures 1 to 3 The described features are implemented in any device, including but not limited to desktop computers, server computers, portable computers, smartphones, tablet computers, game consoles, wearable computers, set-top boxes, media players, smart TVs, etc.

[0080] Architecture 400 may include a memory interface 402, one or more data processors 404, one or more data coprocessors 474, and a peripheral interface 406. The memory interface 402, processors 404, coprocessors 474, and / or peripheral interface 406 may be standalone components or integrated into one or more integrated circuits. One or more communication buses or signal lines may couple the various components.

[0081] Processor 404 and / or coprocessor 474 may operate in cooperation to perform the operations described herein. For example, processor 404 may include one or more central processing units (CPUs) configured to act as the main computer processor of architecture 400. For example, processor 404 may be configured to perform generalized data processing tasks of architecture 400. Additionally, at least some of the data processing tasks may be offloaded to coprocessor 474. For example, specialized data processing tasks (such as processing motion data, processing image data, encrypting data, and / or performing certain types of arithmetic operations) may be offloaded to one or more dedicated coprocessors 474 for processing these tasks. In some cases, processor 404 may be relatively more powerful and / or consume more power than coprocessor 474. For example, this may be useful because it allows processor 404 to process generalized tasks quickly while offloading certain other tasks to coprocessor 474, which can perform those tasks more efficiently and / or more effectively. In some cases, the coprocessor may include one or more sensors or other components (e.g., as described herein) and may be configured to process data acquired using those sensors or components and provide the processed data to the processor 404 for further analysis.

[0082] Sensors, devices, and subsystems can be coupled to peripheral interface 406 to facilitate multiple functions. For example, motion sensor 410, light sensor 412, and proximity sensor 414 can be coupled to peripheral interface 406 to facilitate orientation, illumination, and proximity functions of architecture 400. For example, in some embodiments, light sensor 412 can be used to help adjust the brightness of touch surface 446. In some embodiments, motion sensor 410 can be used to detect movement and orientation of the device. For example, motion sensor 410 may include one or more accelerometers (e.g., for measuring acceleration experienced by motion sensor 410 and / or architecture 400 over a time period) and / or one or more compasses or gyroscopes (e.g., for measuring orientation of motion sensor 410 and / or mobile device). In some cases, the measurement information acquired by motion sensor 410 may be in the form of one or more time-varying signals (e.g., time-varying graphs of acceleration and / or orientation over a time period). Additionally, the displayed object or media can be presented according to the detected orientation (e.g., according to "vertical" orientation or "lateral" orientation). In some cases, motion sensor 410 may be directly integrated into coprocessor 474, which is configured to process measurements acquired by motion sensor 410. For example, coprocessor 474 may include one or more accelerometers, compasses, and / or gyroscopes, and may be configured to acquire sensor data from each of these sensors, process the sensor data, and transmit the processed data to one or more processors 404 for further analysis.

[0083] Other sensors can also be connected to the peripheral interface 406, such as temperature sensors, biometric sensors, or other sensing devices to facilitate related functions. For example, Figure 4 As shown, architecture 400 may include a heart rate sensor 432 that measures a user's heartbeat. Similarly, these other sensors may also be directly integrated into one or more coprocessors 474 configured to process measurements acquired from those sensors.

[0084] A location processor 415 (e.g., a GNSS receiver chip) can be connected to a peripheral interface 406 to provide georeferencing. An electronic magnetometer 416 (e.g., an integrated circuit chip) can also be connected to the peripheral interface 406 to provide data that can be used to determine magnetic north. Thus, the electronic magnetometer 416 can be used as an electronic compass.

[0085] The camera subsystem 420 and optical sensor 422 (such as a charge-coupled device [CCD] or complementary metal-oxide-semiconductor [CMOS] optical sensor) can be used to enable camera functions such as taking photos and editing videos.

[0086] Communication functionality can be facilitated by one or more communication subsystems 424. Communication subsystem 424 may include one or more wireless and / or wired communication subsystems. For example, a wireless communication subsystem may include a radio frequency receiver and transmitter and / or an optical (e.g., infrared) receiver and transmitter. As another example, a wired communication system may include port devices (e.g., a Universal Serial Bus (USB) port) or other wired port connections that can be used to establish wired connections to other computing devices such as other communication devices, network access devices, personal computers, printers, displays, or other processing devices capable of receiving or transmitting data.

[0087] The specific design and implementation of the communication subsystem 424 may depend on one or more communication networks or one or more media through which the architecture 400 is intended to operate. For example, the architecture 400 may include networks designed to operate via GSM networks, GPRS networks, enhanced data GSM environment (EDGE) networks, 802.x communication networks (e.g., Wi-Fi, Wi-Max), code division multiple access (CDMA) networks, NFC, and Bluetooth. TM A network-operated wireless communication subsystem. The wireless communication subsystem may also include a host protocol, enabling architecture 400 to be configured as a base station for other wireless devices. For example, communication subsystem 424 may use one or more protocols, such as TCP / IP, HTTP, UDP, and any other known protocols, to allow architecture 400 to synchronize with host devices.

[0088] The audio subsystem 426 can be coupled to the speaker 428 and one or more microphones 430 to facilitate support for voice functions such as speech recognition, speech copying, digital recording, and telephone functions.

[0089] I / O subsystem 440 may include touch controller 442 and / or other input controller 444. Touch controller 442 may be coupled to touch surface 446. Touch surface 446 and touch controller 442 may detect contact and movement or interruption thereof using, for example, any of a variety of touch-sensitive technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch surface 446. In one embodiment, touch surface 446 may display virtual buttons or soft buttons and a virtual keyboard, which a user can use as input / output devices.

[0090] Other input controllers 444 can be coupled to other input / control devices 448, such as one or more buttons, rocker switches, thumbwheels, infrared ports, USB ports, and / or pointing devices (e.g., styluses). One or more buttons (not shown) may include volume up / down buttons for speaker 428 and / or microphone 430.

[0091] In some implementations, architecture 400 may display recorded audio and / or video files, such as MP3, AAC, and MPEG video files. In some implementations, architecture 400 may include MP3 player functionality and may include pin connectors for connection to other devices. Other input / output devices and control devices may be used.

[0092] Memory interface 402 may be coupled to memory 450. Memory 450 may include high-speed random access memory or non-volatile memory, such as one or more disk storage devices, one or more optical storage devices, or flash memory (e.g., NAND, NOR). Memory 450 may store operating system 452, such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, ANDROID, or embedded operating system (such as VxWorks). Operating system 452 may include instructions for handling basic system services and for performing hardware-related tasks. In some implementations, operating system 452 may include a kernel (e.g., a UNIX kernel).

[0093] The memory 450 may also store communication instructions 454 to facilitate communication with one or more additional devices, one or more computers, or servers, including peer-to-peer communication. The communication instructions 454 may also be used to select an operating mode or communication medium for the device based on its geographic location (obtained by GPS / navigation instructions 468). The memory 450 may include graphical user interface instructions 456 facilitating graphical user interface processing, including touch models for interpreting touch inputs and gestures; sensor processing instructions 458 facilitating sensor-related processing and functions; telephone instructions 460 facilitating telephone-related processes and functions; electronic message processing instructions 462 facilitating electronic message processing and functions; web browsing instructions 464 facilitating web browsing-related processes and functions; media processing instructions 466 facilitating media processing-related processes and functions; GPS / navigation instructions 468 facilitating GPS and navigation-related processes; camera instructions 470 facilitating camera-related processes and functions; and other instructions 472 for performing some or all of the processes described herein.

[0094] Each of the instructions identified above and in the application corresponds to an instruction set used to perform one or more of the functions described herein. These instructions do not need to be implemented as a separate software program, process, or module. Memory 450 may include additional instructions or fewer. Furthermore, various functions of the device may be performed in hardware and / or software, including in one or more signal processing and / or application-specific integrated circuits (ASICs).

[0095] The features may be implemented in digital electronic circuits, or in computer hardware, firmware, software, or a combination thereof. The features may be implemented in a computer program product tangibly embodied in an information carrier (e.g., in a machine-readable storage device) for execution by a programmable processor; and the method steps may be executed by a programmable processor that executes an instruction program to perform the functions of the specific implementation by manipulating input data and generating output.

[0096] The described features can be advantageously implemented in one or more computer programs that can be executed on a programmable system, the programmable system including at least one input device, at least one output device, and at least one programmable processor coupled to receive data and instructions from and transfer data and instructions to the data storage system. A computer program is a set of instructions that can be used directly or indirectly in a computer to perform an activity or produce a result. Computer programs can be written in any form of programming language (e.g., Objective-C, Java), including compiled and interpreted languages, and can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0097] For example, suitable processors for executing programs include both general-purpose microprocessors and special-purpose microprocessors, as well as one or a single processor among multiple processors or cores in any type of computer. Generally, the processor receives instructions and data from read-only memory or random access memory, or both. The basic components of a computer are the processor for executing instructions and one or more memories for storing instructions and data. Generally, a computer can communicate with mass storage devices to store data files. These mass storage devices can include disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Storage devices suitable for tangibly embodying computer program instructions and data include: all forms of non-volatile memory, including semiconductor memory devices such as EPROM, EEPROM, and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM discs. The processor and memory can be supplemented by ASICs (Application-Specific Integrated Circuits) or incorporated into ASICs.

[0098] To provide interaction with the user, these features can be implemented on a computer having a display device for displaying information to the author and a keyboard and pointing device that the author can use to provide input to the computer, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, and a pointing device such as a mouse or trackball.

[0099] These features can be implemented in a computer system that includes back-end components such as data servers, or middleware components such as application servers or internet servers, or front-end components such as client computers with graphical user interfaces or internet browsers, or any combination thereof. The components of the system can be connected via any form of digital data communication (such as a communication network) or the medium of such digital data communication. Examples of communication networks include LANs, WANs, and computers and networks that form the Internet.

[0100] Computer systems may include clients and servers. Clients and servers are generally geographically separated and typically interact over a network. The client-server relationship is established by computer programs running on the respective computers and having a client-server relationship with each other.

[0101] An application programming interface (API) can be used to implement one or more features or steps of the disclosed implementation. An API can define one or more parameters passed between the calling application and other software code (e.g., operating system, stock program, function) that provides services, provides data, or performs operations or calculations.

[0102] An API can be implemented as one or more calls in program code that send or receive one or more parameters through parameter lists or other structures based on the calling conventions defined in the API specification document. Parameters can be constants, keys, data structures, targets, target classes, variables, data types, pointers, arrays, lists, or other calls. API calls and parameters can be implemented in any programming language. Programming languages ​​define the vocabulary and calling conventions that programmers will use to access the functionality that supports the API.

[0103] In some implementations, API calls can report to applications the device's capabilities for running applications, such as input capabilities, output capabilities, processing capabilities, power capabilities, and communication capabilities.

[0104] As stated above, some aspects of the subject matter of this specification include the collection and use of data from various sources to improve services that mobile devices can provide to users. This disclosure contemplates that, in some cases, the collected data may be used to identify specific locations or addresses based on device usage. Such personal information data may include location-based data, addresses, subscriber account identifiers, or other identifying information.

[0105] This disclosure also envisions that entities responsible for the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. For example, personal information from users should be collected for legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate purposes. Furthermore, such collection should only be conducted with the user's informed consent. Additionally, such entities should take any necessary steps to safeguard and protect access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and procedures. Furthermore, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices.

[0106] With regard to advertising delivery services, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, with regard to advertising delivery services, the technology of the present invention can be configured to allow users to choose to "join" or "opt out" of the collection of personal information data during service registration.

[0107] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not be rendered inoperable due to the absence of all or part of such personal information data. For example, preferences can be inferred based on non-personal information data or a minimal amount of personal information, such as content requested by a device associated with a user, other non-personal information available to the content delivery service, or publicly available information, thereby selecting content and delivering it to the user.

[0108] Several specific embodiments have been described. However, it should be understood that various modifications can be made. Elements in one or more embodiments may be combined, deleted, modified, or supplemented to form other embodiments. As another example, the logical flow shown in the figures does not require a specific order or sequence to achieve the desired result. Furthermore, additional steps may be provided or steps may be eliminated from the process, and other components may be added to or removed from the system. Therefore, other embodiments are within the scope of the following claims.

[0109] Figure 5 An example of a wireless communication system 500 is shown. Wireless system 500 may include and / or communicate with a non-terrestrial network 100. For convenience and not limitation, exemplary system 100 is described in the context of Long Term Evolution (LTE) and 5th Generation (5G) New Radio (NR) communication standards, as defined by the 3rd Generation Partnership Project (3GPP) technical specifications. More specifically, wireless communication system 500 is described in the context of a non-standalone (NSA) network combining both LTE and NR (e.g., E-UTRA (Evolved Universal Terrestrial Radio Access) - NR Dual Connectivity (EN-DC) network and NE-DC network). However, wireless communication system 500 may also be a standalone (SA) network combining only NR. Furthermore, other types of communication standards are also possible, including future 3GPP systems (e.g., 6th Generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0110] like Figure 5As 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.

[0111] In some implementations, any of the UEs in UE 501 can be IoT UEs, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. IoT UEs may use technologies such as M2M or MTC to exchange data with MTC servers or devices 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. IoT UEs may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0112] UE 501 can be configured to connect to RAN 510, for example, communicatively coupled. In implementations, RAN 510 can be an NG RAN or 5G RAN, E-UTRAN, non-terrestrial cell, or a traditional RAN such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., can refer to RAN 510 operating in an NR or 5G system 500, while the term "E-UTRAN," etc., can refer to RAN 510 operating in an LTE or 4G system 500. UE 501 utilizes connections (or channels) 503 and 504, each connection including a physical communication interface or layer (discussed in further detail below).

[0113] 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, LTE-A (LTE-Advanced Long Term Evolution), LTE-U (LTE-U), 5G, NR, NR-U (NR-U), 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 also be referred to as SL interface 505 and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0114] 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.

[0115] 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, 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 "NGRAN node," etc., can refer to RAN node 511 (e.g., gNB) operating in NR or 5G system 500, while the terms "E-UTRAN 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 bandwidth compared to macro cells.

[0116] In some implementations, all or part of the multiple RAN nodes 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 splitting, such as PDCP splitting, where the RRC and PDCP layers are operated by CRAN / vBBUP and other L2 protocol entities are operated by individual RAN nodes 511; MAC / PHY splitting, 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” splitting, where the upper part of the RRC, PDCP, RLC, MAC, and PHY layers is operated by CRAN / vBBUP and the lower part 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 6Furthermore, the 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), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminals to multiple UEs 501 and are connected to the 5GC via the ng interface (discussed below).

[0117] 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.

[0118] Any one of the multiple 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 one of the multiple RAN nodes 511 can perform various logical functions of 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.

[0119] 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.

[0120] In some implementations, the downlink resource grid can be used for downlink transmissions from any node in RAN 511 to UE 501, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0121] 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. NR in the unlicensed spectrum may be referred to as NR-U, and LTE in the unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0122] 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.

[0123] 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.

[0124] 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.

[0125] 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 the other CCs. In TDD systems, the number of CCs and the bandwidth of each CC are usually the same for DL ​​and UL.

[0126] 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.

[0127] The PDSCH carries user data and higher-layer signaling to multiple UEs 501. Among other information, the PDCCH carries information about the transmission format and resource allocation related to the PDSCH channel. It can also inform UEs 501 about the transmission format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UEs 501b within the cell) can be performed on any RAN node in RAN node 511 based on channel quality information fed back from any of the UEs 501. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., allocated to) each of the multiple UEs 501.

[0128] PDCCH uses CCEs to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH 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, called REGs, each with four physical resource elements. Four Quadrature Phase Shift Keying (QPSK) 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 defined in LTE with different numbers of CCEs (e.g., aggregation level, L = 1, 2, 4, or 8) can exist.

[0129] 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.

[0130] RAN nodes 511 can be configured to communicate with each other via interface 512. In an implementation where system 500 is an LTE system, interface 512 can be an X2 interface 512. The X2 interface can be defined between two or more RAN nodes 511 connected to EPC 520 (e.g., two or more eNBs, etc.), and / or between two eNBs connected to EPC 520. In some specific 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 through 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 UE; and so on. The X2-C provides LTE intra-eNB access mobility functions, including context transmission from the source eNB to the destination eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.

[0131] In implementations where system 500 is a 5G or NR system, 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 modes (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected modes between one or more RAN nodes 511. 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.

[0132] RAN 510 is shown communicatively coupled to the core network—in this embodiment, communicatively coupled to the core network (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.

[0133] Generally, an application server 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.).

[0134] 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.

[0135] 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.

[0136] Figure 6 Examples of infrastructure equipment 600 according to various embodiments are shown. Infrastructure equipment 600 (or “system 600”) may be implemented as a base station, radio headquarters, non-terrestrial base station, RAN node (such as RAN node 511 and / or AP 506 previously shown and described), application server 530 and / or any other element / device discussed herein. In other examples, system 600 may be implemented in or by a UE.

[0137] System 600 includes application circuitry 605, baseband circuitry 610, one or more radio front-end modules (RFEMs) 615, memory circuitry 620, power management integrated circuit (PMIC) 625, power tee circuitry 630, network controller circuitry 635, network interface connector 640, satellite positioning circuitry 645, and user interface 650. In some embodiments, device 600 may include additional components such as, for example, memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, these 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.

[0138] Application circuitry 605 may include circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: a low-dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C, or a universal programmable serial interface module, a real-time clock (RTC), timers (including interval timers and watchdog timers), 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 application circuitry 605 may be coupled to or may include memory / storage elements, and may be configured to execute instructions stored in the memory / storage elements to enable various applications or operating systems to run on system 600. In some specific implementations, the memory / storage element may be an on-chip memory circuit, which 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.

[0139] The processor of application circuit 605 may include, for example, one or more processor cores (CPU), 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 605 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 605 may include one or more Apple A-series processors, Intel... 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 supplied by Cavium™, Inc. MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some implementations, system 600 may not utilize application circuitry 605 and may instead include a dedicated processor / controller to process, for example, IP data received from an EPC or 5GC.

[0140] In some implementations, application circuitry 605 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 605 may include logic blocks or logic architectures, and other interconnect resources that can be programmed to perform various functions such as procedures, methods, functions, etc., of the various implementations discussed herein. In such implementations, the circuitry of application circuit 605 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).

[0141] The baseband circuit 610 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. References are made below. Figure 7 This paper discusses the various hardware electronic components of the baseband circuit 610.

[0142] User interface circuitry 650 may include one or more user interfaces designed to enable a user to interact with system 600 or peripheral component interfaces, which are designed to enable peripheral components to interact with system 600. 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 transmitter, 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.

[0143] The radio front-end module (RFEM) 615 may include a millimeter-wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some specific implementations, the one or more sub-mmWave 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 7 The antenna array 711 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 615 that combines both millimeter wave antennas and sub-millimeter wave antennas.

[0144] The memory circuitry 620 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 electrically erasable memory (often 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 620 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.

[0145] The PMIC 625 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 630 can provide power drawn from the network cable to provide both power and data connectivity to the infrastructure equipment 600 using a single cable.

[0146] Network controller circuitry 635 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 600 via a physical connection via network interface connector 640; this physical connection can be an electrical connection (typically referred to as a "copper interconnect"), an optical connection, or a wireless connection. Network controller circuitry 635 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 635 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0147] Positioning circuit 645 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 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 645 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 embodiments, positioning circuit 645 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 645 may also be part of or interact with the baseband circuit 610 and / or RFEM 615 to communicate with nodes and components of the positioning network. The positioning circuit 645 may also provide location data and / or time data to the application circuit 605, which may use the data to synchronize operations with various infrastructures, such as RAN node 511.

[0148] Figure 6 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 may be included, such as I2C interfaces, SPI interfaces, point-to-point interfaces, and power buses, etc.

[0149] Figure 7 Exemplary components of a baseband circuit 710 and a radio front-end module (RFEM) 715 according to various embodiments are shown. The baseband circuit 710 corresponds to... Figure 6 The baseband circuit 610. RFEM 715 corresponds to... Figure 6 The RFEM 615. As shown in the figure, the RFEM 715 may include radio frequency (RF) circuitry 706, front-end module (FEM) circuitry 708, and at least an antenna array 711 coupled together as shown in the figure.

[0150] Baseband circuit 710 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 706. 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 710 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuit 710 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 710 is configured to process baseband signals received from the receive signal path of RF circuit 706 and to generate baseband signals for the transmit signal path of RF circuit 706. Baseband circuit 710 is configured to interact with application circuit 605 (see application circuit 605). Figure 6 The baseband circuit 710 is used to generate and process baseband signals and control the operation of the RF circuit 706. The baseband circuit 710 can handle various radio control functions.

[0151] The aforementioned circuitry and / or control logic components of the baseband circuitry 710 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 704A, a 4G / LTE baseband processor 704B, a 5G / NR baseband processor 704C, or other baseband processors 704D 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 704A-704D may be included in modules stored in memory 704G and executed via a central processing unit (CPU) 704E. In other embodiments, some or all of the functions of the baseband processors 704A-D 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 704G may store program code for a real-time operating system (RTOS), which, when executed by CPU 704E (or other baseband processor), enables CPU 704E (or other baseband processor) to manage resources of baseband circuitry 710, 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 from OpenKernel (OK). The provided OKL4, or any other suitable RTOS, such as those discussed herein. Furthermore, the baseband circuitry 710 includes one or more audio digital signal processors (DSPs) 704F. The audio DSP 704F includes elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements.

[0152] In some implementations, each processor in processors 704A-704E includes a corresponding memory interface for sending data to / receiving data from memory 704G. Baseband circuitry 710 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 710, and interfaces for sending data to / receiving data from memory external to baseband circuitry 710. Figure 6 Application circuit interface for sending data to / receiving data from application circuit 605; used for sending data to / receiving data from application circuit. Figure 7 The RF circuit 706 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 Wireless hardware connection interfaces for transmitting data from and receiving data from components, etc.; and power management interfaces for sending power or control signals to and from the PMIC.

[0153] In an alternative embodiment (which may be combined with the embodiments described above), baseband circuitry 710 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, baseband circuitry 710 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 715).

[0154] although Figure 7 Not shown, but in some embodiments, baseband circuitry 710 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 710 and / or RF circuitry 706 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 710 and / or RF circuitry 706 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., 704G) 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 710 may also support radio communication using more than one wireless protocol.

[0155] The various hardware components of the baseband circuit 710 discussed herein can be implemented, for example, as a solderable 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 710 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 710 and the RF circuit 706 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 710 may be implemented as a separate SoC communicatively coupled to the RF circuit 706 (or multiple instances of the RF circuit 706). In yet another example, some or all of the components of the baseband circuit 710 and the application circuit 605 may be implemented together as a separate SoC mounted to the same board (e.g., a “multi-chip package”).

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

[0157] RF circuit 706 can communicate with a wireless network using modulated electromagnetic radiation over a non-solid medium. In various embodiments, RF circuit 706 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 706 may include a receive signal path that includes circuitry for down-converting an RF signal received from FEM circuit 708 and providing a baseband signal to baseband circuit 710. RF circuit 706 may also include a transmit signal path that includes circuitry for up-converting the baseband signal provided by baseband circuit 710 and providing an RF output signal for transmission to FEM circuit 708.

[0158] In some embodiments, the receive signal path of RF circuit 706 may include mixer circuit 706a, amplifier circuit 706b, and filter circuit 706c. In some embodiments, the transmit signal path of RF circuit 706 may include filter circuit 706c and mixer circuit 706a. RF circuit 706 may also include synthesizer circuit 706d for synthesizing the frequency used by mixer circuit 706a in both the receive and transmit signal paths. In some embodiments, mixer circuit 706a in the receive signal path may be configured to down-convert the RF signal received from FEM circuit 708 based on the synthesized frequency provided by synthesizer circuit 706d. Amplifier circuit 706b may be configured to amplify the down-converted signal, and filter circuit 706c 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 may be provided to baseband circuit 710 for further processing. In some implementations, although not required, the output baseband signal may be a zero-frequency baseband signal. In some implementations, the mixer circuit 706a of the receiving signal path may include a passive mixer, but the scope of the implementations is not limited in this respect.

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

[0160] In some embodiments, the mixer circuit 706a for the receive signal path and the mixer circuit 706a 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 706a for the receive signal path and the mixer circuit 706a 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 706a for the receive signal path and the mixer circuit 706a for the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 706a for the receive signal path and the mixer circuit 706a for the transmit signal path may be configured for superheterodyne operation.

[0161] 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, RF circuit 706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuit 710 may include a digital baseband interface for communicating with RF circuit 706.

[0162] 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.

[0163] In some implementations, synthesizer circuit 706d 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 706d may be a Δ-Σ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

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

[0165] 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 circuitry 710 or the application circuitry 605 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 circuitry 605.

[0166] The synthesizer circuit 706d of the RF circuit 706 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.

[0167] In some embodiments, synthesizer circuitry 706d 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 circuitry 706 may include an IQ / polarity converter.

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

[0169] In some embodiments, FEM circuit 708 may include a TX / RX switch to switch between transmit and receive mode operation. FEM circuit 708 may include a receive signal path and a transmit signal path. The receive signal path of FEM circuit 708 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 706). The transmit signal path of FEM circuit 708 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by RF circuit 706), and one or more filters for generating the RF signal for subsequent transmission by one or more antenna elements of antenna array 711.

[0170] Antenna array 711 includes one or more antenna elements, each configured to convert electrical signals into radio waves for propagation through the air and to convert received radio waves back into electrical signals. For example, a digital baseband signal provided by baseband circuit 710 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of antenna array 711, 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 711 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. Antenna array 711 may be formed as a patch of metal foil of various shapes (e.g., a patch antenna) and may be coupled to RF circuit 706 and / or FEM circuit 708 using metal transmission lines, etc.

[0171] The processors of application circuitry 605 and baseband circuitry 710 are elements that can be used to execute one or more instances of the protocol stack. For example, the processor of baseband circuitry 710 can be used alone or in combination to execute layer 3, layer 2, or layer 1 functions, while the processor of application circuitry 605 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.

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

[0173] Processor 810 may include, for example, processor 812 and processor 814. Processor 810 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.

[0174] The memory / storage device 820 may include main memory, disk storage devices, or any suitable combination thereof. The memory / storage device 820 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.

[0175] Communication resource 830 may include interconnection devices or network interface components or other suitable devices for communicating with one or more peripheral devices 804 or one or more databases 806 via network 808. For example, communication resource 830 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.

[0176] Instructions 850 may include software, programs, applications, applets, or other executable code for causing at least one processor in processor 810 to perform any or more of the methods discussed herein. Instructions 850 may reside wholly or partially within at least one of processors 810 (e.g., within the processor's cache memory), memory / storage device 820, or any suitable combination thereof. Furthermore, any portion of instructions 850 may be transferred from peripheral device 804 or database 806 to hardware resource 800 from any combination thereof. Thus, the memory of processor 810, memory / storage device 820, peripheral device 804, and database 806 are examples of computer-readable and machine-readable media.

[0177] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

Claims

1. A method to be performed by a user equipment (UE) in a wireless communication system including a non-terrestrial network (NTN) serving the UE supporting a half duplex frequency division duplex (HD-FDD) mode, the method comprising: determining, based on a scheduling conflict between an uplink transmission and a downlink reception, that a priority ordering between the uplink transmission and the downlink reception is not configured; and based on the priority ordering not being configured, applying a priority ordering rule that prioritizes the uplink transmission or the downlink reception, wherein applying the priority ordering rule comprises: prioritizing the downlink reception over the uplink transmission based on a last symbol of a control resource set including a downlink control information (DCI) scheduling the downlink reception being received earlier than a threshold time before a first symbol of the uplink transmission in a time domain; and prioritizing the uplink transmission over the downlink reception based on the last symbol not being received earlier than the threshold time.

2. The method of claim 1, wherein the uplink transmission is a dynamic grant uplink transmission and the downlink reception is a dynamic grant downlink reception.

3. The method of claim 1, wherein prioritizing the downlink reception comprises: canceling the uplink transmission; and identifying the downlink reception.

4. The method of claim 1, wherein prioritizing the uplink transmission comprises: determining not to receive the downlink reception; and causing the uplink transmission.

5. The method of claim 1, wherein the downlink reception includes a reception of at least one of a physical downlink shared channel (PDSCH) or a channel state information reference signal (CSI-RS).

6. The method of claim 1, wherein the uplink transmission includes a transmission of at least one of a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), or a sounding reference signal (SRS).

7. The method of claim 1, wherein the threshold time is configured by the NTN or computed by the UE.

8. A user equipment (UE) in a wireless communication system including a non-terrestrial network (NTN), the UE served by the NTN and supporting a half duplex frequency division duplex (HD-FDD) mode, the UE comprising: one or more processors configured to perform operations comprising: determining, based on a scheduling conflict between an uplink transmission and a downlink reception, that a priority ordering between the uplink transmission and the downlink reception is not configured; and based on the priority ordering not being configured, applying a priority ordering rule that prioritizes the uplink transmission or the downlink reception, wherein applying the priority ordering rule comprises: ​ ​ ​ based on a last symbol of a control resource set including downlink control information (DCI) scheduling the downlink reception being received earlier than a threshold time before a first symbol of the uplink transmission in a time domain, prioritizing the downlink reception over the uplink transmission; and based on the last symbol not being received earlier than the threshold time, prioritizing the uplink transmission over the downlink reception.

9. The UE of claim 8, wherein prioritizing the downlink reception comprises: canceling the uplink transmission; and identifying the downlink reception.

10. The UE of claim 8, wherein prioritizing the uplink transmission comprises: determining not to receive the downlink reception; and causing the uplink transmission.

11. A non-transitory computer-readable storage device in a wireless communication system comprising a non-terrestrial network (NTN) serving a user equipment (UE) supporting a half duplex frequency division duplex (HD-FDD) mode, the non-transitory computer-readable storage device having instructions stored thereon that, when executed by a data processing apparatus, cause the data processing apparatus to perform operations comprising: based on a scheduling conflict between an uplink transmission and a downlink reception, determining that a prioritization between the uplink transmission and the downlink reception is not configured; and based on the prioritization not being configured, applying a prioritization rule that prioritizes the uplink transmission or the downlink reception, wherein applying the prioritization rule comprises: based on a last symbol of a control resource set including downlink control information (DCI) scheduling the downlink reception being received earlier than a threshold time before a first symbol of the uplink transmission in a time domain, prioritizing the downlink reception over the uplink transmission; and based on the last symbol not being received earlier than the threshold time, prioritizing the uplink transmission over the downlink reception.

12. The non-transitory computer-readable storage device of claim 11, wherein prioritizing the downlink reception comprises: canceling the uplink transmission; and identifying the downlink reception.

13. The non-transitory computer-readable storage device of claim 11, wherein prioritizing the uplink transmission comprises: determining not to receive the downlink reception; and causing the uplink transmission.

Images