Apparatus, method, and computer readable medium for communication
Patent Information
- Application Number
- CN202380101174.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-07
- Publication Date
- 2026-03-17
Smart Images

Figure CN121694002A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to the field of communications, and more particularly to devices, methods, and computer readable media for sending cancellation. BACKGROUND
[0002] With the development of communication technology, a time unit (e.g., a symbol, a time slot, a frame, a subframe, etc.) can be divided into multiple frequency subbands in the frequency domain. The multiple frequency subbands can be respectively used for different link directions, e.g., uplink (UL) or downlink (DL). The time unit can also be referred to as a subband non-overlapping full duplex (SBFD) time unit. Accordingly, a device (e.g., a network device or a terminal device) for communication can perform simultaneous transmission and reception of channels in different link directions on these time units in order to improve communication efficiency.
[0003] In addition to this, in order to implement uplink channel sounding, a device can be configured for transmitting a sounding reference signal (SRS). Specifically, the device can be configured with one or several SRS resource sets, where each resource set includes one or several configured SRSs. Furthermore, the SRSs can be configured for periodic, semi-persistent, or aperiodic transmission. As mentioned before, the time unit can be configured as an SBFD time unit to enhance uplink coverage. Accordingly, coordination between the SRS configuration and the SBFD time unit becomes a key aspect. SUMMARY
[0004] Generally, example embodiments of the present disclosure relate to devices, methods, and computer readable media for sending cancellation.
[0005] In a first aspect, a terminal device is provided. The terminal device includes a processor. The processor is configured to cause the terminal device to receive, from a network device, a resource indicator associated with an uplink channel. Further cause the terminal device to transmit, based on a time unit of the uplink channel being an SBFD time unit, the uplink channel using a first resource indicated by the resource indicator in a first resource set. The SBFD time unit is configured with frequency subbands for different link directions. Further cause the terminal device to transmit, based on the time unit being a non-SBFD time unit, the uplink channel using a second resource indicated by the resource indicator in a second resource set.
[0006] In a second aspect, a network device is provided. The network device includes a processor. The processor is configured to cause the network device to transmit, to a terminal device, a resource indicator associated with an uplink channel. The network device is further caused to receive, based on a time unit of the uplink channel being a SBFD time unit, the uplink channel using first resources indicated by the resource indicator in a first resource set. The SBFD time unit is configured with frequency subbands for different link directions. The network device is further caused to receive, based on the time unit being a non-SBFD time unit, the uplink channel using second resources indicated by the resource indicator in a second resource set.
[0007] In a third aspect, a method implemented at a terminal device is provided. In the method, the terminal device receives, from a network device, a resource indicator associated with an uplink channel. Then, based on a time unit of the uplink channel being a SBFD time unit, the terminal device transmits the uplink channel using first resources indicated by the resource indicator in a first resource set. The SBFD time unit is configured with frequency subbands for different link directions. Based on the time unit being a non-SBFD time unit, the terminal device transmits the uplink channel using second resources indicated by the resource indicator in a second resource set.
[0008] In a fourth aspect, a method implemented at a network device is provided. In the method, the network device transmits, to a terminal device, a resource indicator associated with an uplink channel. Then, based on a time unit of the uplink channel being a SBFD time unit, the network device receives the uplink channel using first resources indicated by the resource indicator in a first resource set. The SBFD time unit is configured with frequency subbands for different link directions. Based on the time unit being a non-SBFD time unit, the network device receives the uplink channel using second resources indicated by the resource indicator in a second resource set.
[0009] In a fifth aspect, a computer readable medium is provided, having stored thereon instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of the fifth to eighth aspects.
[0010] It is to be understood that the Summary is not intended to identify key or essential features of example embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features, details, and advantages of the disclosure will become BRIEF DESCRIPTION OF DRAWINGS
[0011] Some example embodiments will now be described with reference to the accompanying drawings, in which: Figure 1An example environment in which some embodiments of the present disclosure can be implemented is illustrated; Figure 2 A signaling procedure for SRS configuration and associated PUSCH transmission according to some embodiments of the present disclosure is illustrated; Figure 3 Examples of association between PUSCH transmission on SBFD or non-SBFD time units and SRS resource configuration for the SBFD or non-SBFD time units according to some embodiments of the present disclosure are illustrated; Figure 4 Examples of multiple SRS repetition transmissions related to SBFD time units according to some embodiments of the present disclosure are illustrated; Figure 5 Examples of SRS resource set configuration according to some embodiments of the present disclosure are illustrated; Figure 6 Examples of SRS transmission spanning SBFD symbols and non-SBFD symbols according to some embodiments of the present disclosure are illustrated; Figure 7 Examples of avoidance and postponement of SRS transmission related to SBFD slots according to some embodiments of the present disclosure are illustrated; Figure 8 Examples of association between SRS resource set and reference signals for beams according to some embodiments of the present disclosure are illustrated; Figure 9 Examples of hopping pattern for SRS transmission in SBFD time units according to some embodiments of the present disclosure are illustrated; Figure 10 A flowchart of an example method implemented at a terminal device according to some embodiments of the present disclosure is illustrated; Figure 11 A flowchart of an example method implemented at a network device according to some embodiments of the present disclosure is illustrated; and Figure 12 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is illustrated.
[0012] Throughout the drawings, identical or similar reference numerals can designate identical or similar elements throughout the several views. DETAILED DESCRIPTION
[0013] The principles of the present disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and are not meant to limit the scope of the present disclosure in any way. The disclosure described herein can be implemented in various ways other than those described below.
[0014] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.
[0015] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to: user equipment (UE); personal computers; desktop computers; mobile phones; cellular phones; smartphones; personal digital assistants (PDAs); portable computers; tablets; wearable devices; Internet of Things (IoT) devices; Ultra-reliable and Low-Latency Communication (URLLC) devices; Internet of Everything (IoE) devices; machine-type communication (MTC) devices; devices on vehicles for V2X communication, where X refers to pedestrians, vehicles, or infrastructure / networks; devices for Integrated Access and Backhaul (IAB); devices for Small Data Transmission (SDT); mobility devices; devices for Multicast and Broadcast Service (MBS); devices for location services; devices for dynamic / flexible duplexing in commercial networks; RedCap (red-cap) devices; and non-terrestrial networks (NTNs). In the context of a non-terrestrial network, spacecraft or aircraft vehicles are included. These non-terrestrial networks include satellites and high-altitude platforms (HAPs) encompassing unmanned aircraft systems (UAS); extended reality (XR) devices that include different types of reality (such as augmented reality (AR), mixed reality (MR), and virtual reality (VR)); unmanned aerial vehicles (UAVs), often referred to as drones (aircraft without any human pilots); equipment on high-speed trains (HSTs); or image capture devices such as digital cameras and sensors; gaming devices; music storage and playback devices; or internet devices that enable wireless or wired internet access and browsing.The "terminal device" may also have "multicast / broadcast" capabilities to support public safety and mission-critical applications, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, radio services, wireless software delivery, group communications, and IoT applications. The "terminal device" may also incorporate one or more Subscriber Identity Modules (SIMs), a latter case referred to as multi-SIM. The term "terminal device" is used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, wireless device, or a terminal device with reduced capabilities.
[0016] As used herein, the term "network device" refers to a device capable of providing or hosting communication for terminal devices within a cell or coverage area. Examples of network devices include, but are not limited to, NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), next-generation NodeBs (gNBs), transmission reception points (TRPs), remote radio units (RRUs), radio heads (RHs), remote radio heads (RRHs), IAB nodes, low-power nodes (such as femtonodes and piconodes), reconfigurable intelligent surfaces (RISs), network-controlled repeaters, etc.
[0017] Terminal or network devices may possess artificial intelligence (AI) or machine learning capabilities. They typically include models trained on specific functions based on extensive data collection and capable of predicting information. Terminal or network devices can operate within several frequency ranges, such as FR1 (410MHz to 7125MHz), FR2 (24.25GHz to 71GHz), 71GHz to 114GHz, and frequency bands above 100GHz and terahertz (THz). They can also operate on licensed / unlicensed / shared spectrum. In Multi-Radio Dual Connectivity (MR-DC) applications, terminal devices may connect to more than one network device. Terminal or network devices can operate in full-duplex, flexible-duplex, and cross-division duplex modes.
[0018] Network devices may feature network energy saving and self-organizing network (SON) / minimization of drive test (MDT) capabilities. Terminals may feature power saving capabilities.
[0019] The embodiments disclosed herein can be implemented in test equipment (e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal equipment, test network equipment, channel simulator).
[0020] The embodiments of this disclosure can be implemented according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, 5G-Advanced Networks, or sixth-generation (6G) networks.
[0021] In one embodiment, the terminal device may be connected to a first network device and a second network device. One of the first and second network devices may be a master node, and the other may be a slave node. The first and second network devices may use different Radio Access Technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information related to different RATs may be sent to the terminal device from at least one of the first and second network devices. In one embodiment, first information may be sent from the first network device to the terminal device, and second information may be sent from the second network device directly or via the first network device to the terminal device. In one embodiment, configuration-related information configured by the second network device for the terminal device may be sent from the second network device via the first network device. Reconfiguration-related information configured by the second network device for the terminal device may be sent from the second network device directly or via the first network device to the terminal device.
[0022] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term “comprising” and its variations should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one implementation” and “implementation” should be understood as “at least one implementation.” The term “another implementation” should be understood as “at least one other implementation.” The terms “first,” “second,” etc., may refer to different or the same objects. Other explicit and implicit definitions are given below.
[0023] In some examples, values, programs, or devices are described as “best,” “lowest,” “highest,” “smallest,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a choice can be made among many alternative functionalities used, and that such a choice is not necessarily better, smaller, higher, or otherwise preferred than other choices.
[0024] As used herein, the term "circuit" can refer to hardware circuitry and / or a combination of hardware and software circuitry. For example, a circuit can be a combination of analog and / or digital hardware circuitry with software / firmware. As another example, a circuit can be any part of a hardware processor with software, including digital signal processors, software, and memory, which work together to enable a device (such as a terminal device or network device) to perform various functions. In yet another example, a circuit can be hardware circuitry and / or a processor (such as a microprocessor or a portion thereof) that requires software / firmware to operate, but which may be absent when no software is required to operate. As used herein, the term "circuit" also encompasses a specific implementation of hardware circuitry or a processor, or a portion thereof, and its accompanying software and / or firmware. In this disclosure, subbands and frequency subbands are used interchangeably without any limitation. The group size of an RBG can also be referred to as the RBG size without any limitation. In this disclosure, a control channel can be used interchangeably with a physical downlink control channel (PDCCH) without any limitation.
[0025] A time unit configured with SBFD communication or configured with SBFD can also be referred to as an SBFD time unit, and a time unit not configured with SBFD communication can also be referred to as a non-SBFD time unit. Non-SBFD time units may include UL time units and / or DL time units.
[0026] In this disclosure, the time unit can be any duration, such as a symbol, time slot, subframe, and frame. Without any limitation, and for illustrative purposes only, these time scales can be used interchangeably.
[0027] The terms “resource”, “physical resource block (PRB)” or “resource block” used in this article refer to the basic unit of resources in the frequency domain.
[0028] As used in this document, the term "SBFD-aware UE" can refer to a terminal device that obtains the SBFD configuration of time units (e.g., subband division or the location of these time units) and supports SBFD operations with network devices.
[0029] In this disclosure, the terms "frequency subband" and "subband" are used interchangeably without any limitation. Furthermore, a frequency subband configured for uplink communication in the SBFD time unit may also be referred to as an "uplink (UL) subband." Correspondingly, a frequency subband configured for downlink communication in the SBFD time unit may also be referred to as a "downlink (DL) subband."
[0030] In this disclosure, a time unit can be any measure in the time domain. For example, a time unit can be a frame, subframe, time slot, or symbol. Without any limitation, a time unit can be any other duration.
[0031] In this disclosure, the term "a set of SRS resources" may be used interchangeably with "SRS resource set".
[0032] As mentioned earlier, to enhance UL coverage, network devices can indicate to terminal devices that certain time units are configured as SBFD time units, for example, configuring some DL time units as SBFD time units. Simultaneously, the terminal device may need to transmit SRS in the uplink direction based on the SRS resource set configuration to estimate channel conditions. Accordingly, the terminal device can utilize the configured SBFD time units for SRS transmission, for example, transmitting the SRS on the uplink subband of that SBFD time unit to increase the chance of SRS transmission. However, the SRS resource set configuration may be incompatible with the subband division of the SBFD time unit. For example, resources for SRS may be configured in the DL subband or guard band of the SBFD time unit. In this case, the terminal device cannot transmit SRS within that SBFD time unit. Furthermore, SRS transmission is associated with subsequent uplink data channels. For example, the network device can feed back an SRS resource indicator (SRI) to the terminal device to indicate which resource (e.g., which beam) is available for the uplink data channel. In this scenario, previous SRS transmitted in either an SBFD or non-SBFD time unit may result in different SRIs. In one implementation, SRS resource sets can be configured separately for SBFD and non-SBFD time units. However, separate configuration does not address issues related to resource indications for subsequent uplinks.
[0033] In view of this, an example embodiment of this disclosure proposes a mechanism for configuring an SRS resource set relative to an SBFD time unit. In this mechanism, a terminal device receives a resource indicator associated with an uplink channel from a network device. Then, if the time unit of the uplink channel is an SBFD time unit, the terminal device transmits the uplink channel using a first resource indicated by the resource indicator in a first resource set. If the time unit is a non-SBFD time unit, the terminal device transmits the uplink channel using a second resource indicated by the resource indicator in a second resource set.
[0034] In this way, for uplink channels transmitted in SBFD or non-SBFD time units, the resource indicator can indicate resources in different resource sets. Thus, even when the channel state differs between SBFD and non-SBFD time units, the resource indicator can correctly indicate the resources of subsequent uplink channels within either the SBFD or non-SBFD time unit. Furthermore, the first resource set can be a first SRS resource set for SBFD time units, and the second resource set can be a second SRS resource set for non-SBFD time units. This approach enables coordination between SRS resource configuration and subband partitioning within SBFD time units.
[0035] Figure 1 Example environment 100 is illustrated in which example implementations of this disclosure may be carried out.
[0036] Environment 100 may be part of a communication network and includes terminal device 110 and network device 120. In some embodiments, the communication network may include NTN, NB-IoT, and / or eMTC. In other embodiments, the communication network may include any other possible communication network. It should be understood that the number of network devices and terminal devices is given for illustrative purposes only and does not imply any limitation. The communication network may include any suitable number of network devices and / or terminal devices suitable for implementing embodiments of this disclosure. Although not shown, it should be understood that one or more terminal devices may be located in environment 100. Without any limitation, network device 120 supports SBFD communication. For example, network device 120 may simultaneously transmit a downlink (DL) channel to terminal device 110 and receive a UL channel from another terminal device 130 in an SBFD time unit. In this disclosure, a non-SBFD time unit may be a UL-only time unit or a DL-only time unit.
[0037] It should be understood that Figure 1 The number of units and other objects described herein is provided for illustrative purposes only and does not imply any limitation on device environment 100. Device environment 100 may include any suitable number of functional units configured to implement the example embodiments disclosed herein. Although not shown, it should be understood that one or more terminal devices may be located in device environment 100.
[0038] In this disclosure, as previously described, coordination between SRS resource allocation and subband partitioning within SBFD time units can be achieved, and associated uplink channel transmission can be improved.
[0039] Figure 2 Signaling procedures 200 for SRS configuration and associated PUSCH transmission according to some embodiments of this disclosure are illustrated. For illustrative purposes, reference will be made to... Figure 1 Describe the process 200.
[0040] In signaling procedure 200, network device 120 sends (210) a resource indicator 215 associated with the uplink channel to terminal device 110. Resource indicator 215 may identify communication resources used for the uplink channel. In some embodiments, the resource indicator may be a Sounding Reference Signal (SRS) Resource Indicator (SRI) identifying SRS resources used for SRS transmissions from terminal device 110. Alternatively, resource indicator 215 may identify certain resources within the uplink frequency of an SBFD time unit. Alternatively, resource indicator 215 may identify certain resources in non-SBFD time units. Without limitation, resource indicator 215 may also identify other communication resources.
[0041] In the example where a signal indicator identifies SRS resources, network device 120 may send (201) configuration information 202 to terminal device 110. Configuration information 202 indicates a first SRS resource set configured for an SBFD time unit and a second SRS resource set configured for a non-SBFD time unit. Furthermore, the first SRS resource set is located within one or more uplink frequency subbands of the SBFD time unit. After receiving (203) configuration information 202, terminal device 110 may use the first SRS resource set to send (204) SRS 205 during the SBFD time unit. Correspondingly, during a non-SBFD time unit, terminal device 110 may use the second SRS resource set to send (204) SRS 205. In this case, after receiving (206) SRS 205, network device 120 may estimate the channel state on either the SBFD or non-SBFD time unit separately. Then, network device 120 may feed back a resource indicator, such as an SRI, to terminal device 110. The SRI can indicate a first resource from a first SRS resource set relative to an SBFD time unit. The SRI can indicate a second resource from a second SRS resource set relative to a non-SBFD time unit, which may be the same as or different from the first resource. In one example, the SRI can indicate a resource within an uplink subband of an SBFD time unit in the time domain. Alternatively, the SRI can indicate other resources in a non-SBFD time unit in the time domain. In some implementations, network device 120 can send a first resource indicator (or first SRI) specific to an SBFD time unit and a second resource indicator (or second SRI) specific to a non-SBFD time unit. Alternatively, the first SRI indicates the first resource, and the second SRI indicates the second resource. Alternatively, there may be one SRI, which can be associated with a resource in either the first or second SRS resource set in a predefined rule. Furthermore, the first resource can also be a first beam (e.g., a first antenna port), and the second resource can be a second beam (e.g., a second antenna port). For clarity, refer to [reference needed]. Figure 4 to Figure 9 The configuration of the first SRS resource set and the second SRS resource set will be discussed further, but will not be elaborated here.
[0042] Still refer to Figure 2If terminal device 110 needs to transmit an uplink channel, such as a physical uplink shared channel (PUSCH) and / or a physical uplink control channel (PUCCH), terminal device 110 can determine whether the time unit of the uplink channel is an SBFD time unit or a non-SBFD time unit. Based on the assumption that the uplink channel time unit is an SBFD time unit, terminal device 110 uses the first resource indicated by resource indicator 215 in the first resource set to transmit (230) the uplink channel 235. Alternatively, based on the assumption that the time unit is a non-SBFD time unit, terminal device 110 uses the second resource indicated by resource indicator 215 in the second resource set to transmit (230) the uplink channel 235. In this case, since the network device can estimate the uplink channel for either the SBFD time unit or the non-SBFD time unit separately, the performance of uplink channel transmission can be improved. In addition, uplink channels transmitted within SBFD time units are based on a first resource set configured for the SBFD time unit, such as a first SRS resource set. Correspondingly, uplink channels transmitted outside SBFD time units are based on a second resource set configured for the non-SBFD time unit, such as a second SRS resource set. For discussion purposes only, refer to... Figure 3 Further discussion on uplink channel transmission.
[0043] Figure 3 Examples illustrating the association between PUSCH transmission on an SBFD or non-SBFD time unit and SRS resource configuration for that SBFD or non-SBFD time unit according to some embodiments of this disclosure are given.
[0044] like Figure 3 As shown, SBFD symbols may be affected by CLI, therefore the link quality of SBFD time units may differ from that of non-SBFD symbols. As previously stated, for PUSCH 310 scheduled in an SBFD time unit (e.g., a slot or symbol), the SRS resources indicated by the SRI in the DCI scheduling the PUSCH may belong to the first SRS resource set 340. Correspondingly, for PUSCH 320 scheduled in a non-SBFD time unit, the SRS resources indicated by the SRI in the DCI scheduling the PUSCH may belong to the second SRS resource set. In this way, the probability of successful PUSCH transmission can be improved. Alternatively, the above implementation can also be described as follows.
[0045] Return to reference Figure 2To ensure SRS reception, terminal device 110 may send (206) multiple SRS retransmissions 205 to network device 120. In some cases, these multiple SRS retransmissions may span more than one time slot, and one of the multiple SRS retransmissions may be sent within one time slot. Generally, SRS can be targeted at... repetitionFactor The parameters are configured to transmit 1, 2, or 4 repetitions. In addition, in some cases, a time slot may not have sufficient UL resources to accommodate a single SRS repetition. Accordingly, a time slot capable of transmitting an SRS repetition can be counted as an available time slot, for example, a time slot including a sufficient number of UL symbols. However, available time slots including SBFD symbols may not be counted. In the example embodiments of this disclosure, the concept of an available time slot is introduced for SRS repetition. If a time slot can be used for an SRS repetition, that time slot can be considered an "available time slot." In some embodiments, terminal device 110 or network device 120 can determine whether a time slot is available by determining whether one or more resources configured for SRS repetition in the time slot are greater than or equal to the resources required for SRS repetition. Then, if the one or more resources are greater than or equal to the resources required for SRS repetition, terminal device 110 or second device 120 can determine that the time slot is available. For clarity of discussion, refer to... Figure 4 Further discussion on "available time slots".
[0046] Figure 4 Examples of multiple SRS retransmissions associated with SBFD time units are illustrated according to some embodiments of this disclosure.
[0047] like Figure 4As shown, a time slot may include SBFD symbols and non-SBFD symbols, such as time slot 0. Alternatively, a time slot may include only SBFD symbols (e.g., time slot 1). Alternatively, a time slot may include only non-SBFD symbols (e.g., time slots 2 and 3). As previously described, SBFD symbols may be configured with a first SRS resource set within the UL subband, and non-SBFD symbols (i.e., UL symbols) may be configured with a second SRS resource set. For a time slot including both SBFD and non-SBFD symbols, if the first SRS resource set in the SBFD symbols and the second SRS resource set in the non-SBFD symbols can accommodate one SRS repeat transmission, then the time slot may be considered an available time slot, and the SRS repeat count is incremented by one. Otherwise, the time slot may be considered unavailable, such as time slot 0. For a time slot including only SBFD symbols, if the first SRS resource set in the SBFD symbols of the time slot can accommodate one SRS repeat transmission, then the time slot may be considered an available time slot, such as time slot 1. Alternatively, for time slots that consist only of non-SBFD symbols, a time slot can be considered a usable time slot if the second SRS resource set in the non-SBFD symbols of that time slot can accommodate an SRS repeat transmission, such as time slots 2 and 3. In view of this, SRS repeat transmissions 420, 430, and 440 can be transmitted, and SRS repeat transmission 410 cannot be transmitted. In this case, time slots 1 through 3 can be counted as a single usable time slot. In the above embodiments of this disclosure, if the UL subband on the configured / indicated SBFD symbol is used for SRS transmission, the counting method needs to be changed. Alternatively, the above embodiments can also be described as follows.
[0048] Return to reference Figure 2 As previously described, configuration information 202 may indicate a first SRS resource set for SBFD time units and a second SRS resource set for non-SBFD time units. In some embodiments, configuration information 202 may include one or more parameters indicating the second SRS resource set. Furthermore, configuration information 202 may include at least one offset value, and the first SRS resource set is indicated by the one or more parameters and the at least one offset value. References are provided only for clarity of discussion. Figure 5 Further discussion on configuration information.
[0049] Figure 5 Examples of SRS resource set configurations according to some embodiments of this disclosure are illustrated.
[0050] like Figure 5As shown, SRS resource set 510 represents a first SRS resource set, and SRS resource set 520 represents a second SRS resource set. As previously described, configuration information may include one or more parameters that directly indicate SRS resource set 520 and at least one offset value 530. Furthermore, SRS resource set 510 may be indicated by the one or more parameters and the at least one offset value 530. In one example, terminal device 110 transmits multiple SRS repetitions across SBFD symbols and non-SBFD symbols, such as... Figure 5 As shown. In this case, the RB offset may be included in the configuration information (or in the downlink control information DCI) to indicate to the first device 110 the start frequency offset of the SRS resource set in the SBFD symbol relative to the start frequency position of the SRS resource set in the non-SBFD symbol. Furthermore, in some embodiments, the offset value is set to zero if the second SRS resource set is within the uplink subband of the SBFD time unit. That is, the offset value 530 is applied only if the frequency resources allocated for the SRS are outside the UL subband of the SBFD time unit. Otherwise, the parameter is not applied, and the frequency position of the SRS resource set is the same for both SBFD and non-SBFD symbols.
[0051] In such Figure 5 In the example shown, when the frequency domain start position of the SRS resource set configuration is not within the UL subband of the SBFD symbol, the configured repetition factor is 2, and the RB offset is configured as "-8RB" for the SBFD symbol. Alternatively, for example, since the starting UL RB in the SBFD slot does not coincide with the starting RB in the BWP, a new factor can be added to calculate the frequency domain position of the SRS resource set. This new factor can indicate the starting RB of the SRS resource set in the SBFD slot. For example, the new factor V can be the difference between the starting PRB of the UL subband of the SBFD time unit and the starting RB of the SRS resource set configured on the UL-only slot. The above implementation can be considered as "a frequency domain resource allocation (FDRA) plus additional parameters". In this way, SRS transmission on the SBFD symbol can be guaranteed.
[0052] In addition to the aforementioned offset values, or alternatively, the configuration information 202 may include first configuration information and second configuration information, respectively. The first configuration information separately indicates the first SRS resource set (i.e., SRS resource set 510), and the second configuration information separately indicates the second SRS resource set (i.e., SRS resource set 520). In this case, if the terminal device 110 transmits multiple SRS repetitions as described above, different FDRAs can be determined for SBFD or non-SBFD time units. For example, if the SRS resources configured for the UL time slot overlap with the DL subband of the SBFD time unit in the frequency domain, two FDRAs may exist for the SBFD and non-SBFD time units. Otherwise, if the SRS resources configured for the UL time slot are within the UL subband of the SBFD time unit, the same FDRA can be assigned to the SBFD and non-SBFD symbols. In addition, or alternatively, new parameters may be defined. k4 This is used to indicate the frequency domain starting position of the SRS resource set on the SBFD symbol relative to the starting RB in point A or BWP. This implementation can be considered as "two FDRAs". In this way, SRS transmission on the SBFD symbol is guaranteed.
[0053] In addition, time-domain resources can be adjusted for SBFD time units. For example, time-domain resources can be defined. startPosition -SBFD is used to indicate the starting symbol position of an SBFD symbol and / or the last SBFD symbol that is after or equal to the starting symbol position. In addition, other symbols can be defined. nrofSymbols -SBFD is used to indicate the number of SRS symbols used for SRS transmission on SBFD symbols, and this number should not exceed the number of adjacent SBFD symbols.
[0054] Return to reference Figure 2When terminal device 110 needs to send (204) SRS or SRS repetition, there may be other downlink transmissions scheduled using at least a portion of the same resources. That is, the terminal device's SRS transmission may conflict with downlink transmissions. In some implementations, terminal device 110 or network device 120 may compare a first priority level of SRS transmission with a second priority level of downlink transmission. Then, based on this priority level comparison, terminal device 110 may send an SRS transmission to the network device or receive a DL transmission from the network device 120. Accordingly, network device 120 may receive an SRS transmission from terminal device 110 or send a DL transmission to terminal device 110. In other words, a standard for priority levels related to conflicts is defined. For conflicts between periodic or semi-persistent SRS transmissions and configured DL receptions (such as periodic CSI-RS / CORESET or SPS PDSCH), a mechanism for skipping / disabling the timing of periodic or semi-static SRS transmissions on SBFD slots / symbols may be introduced. In some implementations, priority criteria may be defined as follows: the priority level of an aperiodic reference signal is higher than the priority level of a periodic or semi-persistent reference signal; the priority level of an aperiodic uplink reference signal is higher than the priority level of a pre-configured downlink reference signal; the priority level of a pre-configured downlink control channel is higher than the priority level of a periodic or semi-persistent uplink reference signal; or the priority level of an aperiodic uplink reference signal is higher than the priority level of a pre-configured downlink control channel.
[0055] In certain examples, dynamic granting (aperiodic SRS / CSI-RS / PRS) may have a higher priority than periodic or semi-persistent SRS / CSI-RS / PRS. Periodic or semi-persistent signals will be discarded. Alternatively, predefined downlink reference signals (such as SSB, CSI-RS, PRS, and TRS) have a higher priority than uplink reference signals (such as semi-persistent / periodic SRS). If a conflict occurs, the UE will discard or delay SRS transmission and receive SSB, CSI-RS, PRS, and TRS. Alternatively, predefined downlink reference signals (such as CSI-RS, PRS, and TRS) have a lower priority than uplink reference signals (such as aperiodic SRS). If a conflict occurs, the UE will transmit SRS and discard CSI-RS, PRS, and TRS reception. Alternatively, if CORESET conflicts with periodic / semi-persistent SRS, the SRS is discarded or delayed. If the CORESET conflicts with an aperiodic SRS, the UE does not need to monitor the PDCCH and transmits an aperiodic SRS. Alternatively, if the SPS PDSCH conflicts with an aperiodic SRS, the UE transmits the SRS and does not receive the PDSCH. Alternatively, if the transmission of a PDSCH with priority index 1 overlaps in time with the transmission of an SRS on the UL subband in the SBFD symbol, the UE does not transmit the SRS in the overlapping symbol.
[0056] In this way, conflicts between reference signal transmission and downlink transmission can be avoided.
[0057] Furthermore, in some cases, the SRS to be transmitted may span adjacent SBFD time units and non-SBFD time units. In some implementations, whether an SRS can be transmitted or received depends on the frequency resources in the SRS resource set. In some implementations, terminal device 110 and network device 120 may determine whether the SRS resource set is within the uplink subband of the SBFD time unit in the frequency domain. If the SRS resource set is within the uplink subband of the SBFD time unit, then terminal device 110 may transmit the SRS spanning the SBFD time unit and adjacent non-SBFD time units. Accordingly, network device 120 may receive the SRS spanning the SBFD time unit and adjacent non-SBFD time units. For clarity of discussion, refer to Figure 6 Further discussion of the above implementation plan.
[0058] Figure 6 Examples of SRS transmission across SBFD symbols and non-SBFD symbols according to some embodiments of this disclosure are illustrated.
[0059] like Figure 6As shown, if the configured SRS frequency resource is within the UL subband (e.g., SRS resource set 610), SRS transmission can span both SBFD and non-SBFD symbols. Furthermore, if the configured SRS frequency resource is not within the UL subband of an SBFD symbol (e.g., SRS resource set 620), the terminal device 110 can discard the configured periodic / semi-persistent SRS transmission.
[0060] exist Figure 6 In the example, the configured SRS symbol count is 6, and the starting symbol count is 3. When the MAC-CE or DCI-based indication indicates that the starting symbol is symbol 0 and the SBFD symbol duration is 7 symbols, the SRS can only be transmitted if the SRS frequency resource is within the UL subband. Otherwise, the SRS can be discarded. Alternatively, the above implementation can also be described as follows.
[0061] In this way, SRS transmission can span SBFD symbols and non-SBFD symbols in a single time slot.
[0062] In addition, in some implementations, the configured SRS transmission can be circumvented and postponed. For example, the SRS is scheduled to be transmitted on the SBFD time unit. In some cases, the configured SRS may overlap with frequency subbands other than the uplink subband of that SBFD time unit. For example, the configured SRS may partially overlap with the guard band and / or DL subband. In this case, terminal device 110 can circumvent the transmission of SRS on that SBFD time unit and postpone the transmission of SRS. For clarity, refer to... Figure 7 Further discussion of the above implementation plan.
[0063] Figure 7 Examples of circumvention and delay of SRS transmission associated with SBFD slots according to some embodiments of this disclosure are provided.
[0064] like Figure 7As shown, if SRS 710 overlaps with an RB outside the UL subband in the SBFD time slot / symbol, SRS transmission 710 can be delayed or postponed to the nearest available UL time slot or flexible time slot. Furthermore, the SRS resources used for transmitting the SRS in the nearest available UL time slot or flexible time slot are the same as those in the SBFD time slot / symbol. Additionally, network device 120 can reserve these resources for delayed SRS transmission. In other words, if the configured periodic or semi-static SRS resources overlap with an RB outside the UL subband in the SBFD time slot, the SRS is delayed to the next UL time slot, and the time and frequency resources are the same as those in the SBFD symbol. Alternatively, the above embodiment can also be described as follows. In this way, SRS transmission can be processed finely relative to the SBFD time unit.
[0065] In some implementations, the first resource set may be associated with a first plurality of beams, and the first resource set may also be associated with a second plurality of beams. For example, the channel states between SBFD time units and non-SBFD time units may differ. Therefore, the beam set configured in the first resource set may differ from another beam set configured in the second resource set. Furthermore, the first resource set may be associated with a first reference signal or a first identifier (ID) associated with the first reference signal. Correspondingly, the second resource set may be associated with a second reference signal or a second ID associated with the second reference signal. For clarity, reference... Figure 8 Further discussion of the above implementation plan.
[0066] Figure 8 Examples illustrating the association between an SRS resource set and a reference signal used for beamforming are given according to some embodiments of this disclosure.
[0067] like Figure 8 As shown, separate beam / spatial relationships can be configured for SBFD and non-SBFD time units (e.g., UL symbols) relative to the SRS resource set. This allows interference or SINR to be considered separately. Furthermore, the reference signal and / or reference signal SSB / NZP-CSI-RS-Resource ID can also be different for SBFD and non-SBFD time units.
[0068] In one example, for SRS resource Id#1 within an SBFD time unit, the reference signal can be SSB Index#3. Conversely, for SRS resource Id#2 outside of an SBFD time unit, the reference signal can be NZP-CSI-RS-Resource Id#6. Alternatively, the beam directions for SBFD and non-SBFD time units can be as follows:Figure 8 exemplified.
[0069] Return to reference Figure 2 The frequency hopping pattern used for SRS transmission in an SBFD time unit can be adjusted. In some embodiments, terminal device 110 can receive a frequency hopping indication for SRS transmission from network device 120. In some embodiments, in an SBFD time unit, terminal device 110 can use a first frequency hopping pattern to transmit (205) SRS to network device 120. In addition, in non-SBFD time units (e.g., UL time units), terminal device 110 can use a second frequency hopping pattern to transmit (205) SRS to the network device. Furthermore, at least one of the start position and frequency hopping step size of the second frequency hopping pattern is different from the first frequency hopping pattern. For clarity, refer to Figure 9 The frequency hopping pattern of the SBFD time unit is further discussed.
[0070] Figure 9 Examples of transition patterns for SRS transmission in SBFD time units according to some embodiments of this disclosure are illustrated.
[0071] like Figure 9 As shown, if frequency hopping for SRS is enabled in the SBFD unit, the start frequency position and hopping bandwidth can be within the UL subband of the SBFD time unit. For example, separate frequency hopping parameters can be configured for the SBFD time unit, such as... and ,in Indicates frequency hopping pattern index and Indicates the number of frequency hopping RBs. In addition, the hopping step size configured from network device 120 can be scaled for SBFD time slots, and the scaling factor can be equal to (UL subband bandwidth) / (UL time slot bandwidth). In some implementations, the hopping step size configured from network device 120 can be the hopping step size used in a second frequency mode for non-SBFD time units.
[0072] Alternatively, terminal device 110 may send SRS to network devices within an SBFD time unit without using frequency hopping. In one example, if the resources used for frequency hopping are outside the uplink subband of the SBFD time unit, terminal device 110 may assume that inter-slot / intra-slot frequency hopping is not enabled on the SBFD symbol, even if such frequency hopping is configured. In this case, wideband SRS can be configured for the SBFD symbol. Alternatively, the above embodiments may also be described as follows.
[0073] In addition, since cross-link interference (CLI) may occur within the SBFD time unit, the transmit power of the SRS within the SBFD time unit can also be adjusted. In some implementations, the terminal device 110 can receive a power control configuration indicating a first power control parameter for the SBFD time unit and a second power control parameter for the non-SBFD time unit. Specifically, a first maximum value of the first output power parameter (also known as the first power control parameter) is less than a second maximum value of the second output power parameter (also known as the second power control parameter). In a specific example, different power control parameters can be configured for SBFD symbols and non-SBFD symbols. The maximum UE output power for SBFD symbols or non-SBFD symbols can be configured separately. Furthermore, the maximum UE output power for SBFD symbols can be less than the maximum UE output power for non-SBFD symbols to reduce potential CLI.
[0074] Alternatively, a set of power control parameters can be configured, and additional offset values can be configured for the SBFD time units. For example, if SBFD time units and non-SBFD time units share an SRS resource set, then... SRS- ResourceSet The configuration includes two alpha and P0 pins. srs-PowerControlAdjustmentStates and pathlossReferenceRS If SBFD time units and non-SBFD time units share different SRS resource sets, then each SRS-Resourceset This may include a set of transmit power control parameters. Alternatively, if the SRS spans both SBFD and non-SBFD symbols, the terminal device 110 may apply different transmit powers to the same SRS on both SBFD and non-SBFD symbols. In this way, CLI within the SBFD time unit can be reduced.
[0075] In view of this, through the example implementation of this disclosure, SRS resource configuration, SRS transmission and associated channel transmission can be coordinated with the introduced SBFD time unit.
[0076] Figure 10 A flowchart illustrating a method 1000 for communication implemented at a terminal device according to some embodiments of the present disclosure is provided. Method 900 may be... Figure 1 The terminal device 110 shown is implemented here. For discussion purposes, reference will be made to... Figure 1 Method 1000 is described. It should be understood that method 1000 may include additional actions not shown and / or some actions shown may be omitted, and the scope of this disclosure is not limited in this respect.
[0077] At 1010, terminal device 110 receives a resource indicator associated with the uplink channel from the network device. At 1020, based on the uplink channel's time unit being an SBFD time unit, terminal device 110 uses a first resource indicated by the resource indicator in a first resource set to transmit the uplink channel. The SBFD time unit is configured with frequency subbands for different link directions. At 1030, based on the time unit being a non-SBFD time unit, terminal device 110 uses a second resource indicated by the resource indicator in a second resource set to transmit the uplink channel.
[0078] In some implementations, at least one of the following is present: the resource indicator is a sounding reference signal (SRS) resource indicator (SRI); the first resource set is a first sounding reference signal (SRS) resource set configured for the SBFD time unit, and the first resource set is in the uplink subband of the SBFD time unit in the frequency domain; the second resource set is a second SRS resource set configured for a non-SBFD time unit; or the uplink channel is a physical uplink shared channel (PUSCH).
[0079] In some implementations, terminal device 110 may also receive configuration information from network device indicating a first SRS resource set and a second SRS resource set.
[0080] In some implementations, the configuration information includes one or more parameters indicating a second SRS resource set, and the configuration information also includes at least one offset value, and the first SRS resource set is indicated by the one or more parameters and the at least one offset value.
[0081] In some implementations, the offset value is set to zero when the second SRS resource set is within the uplink subband of the SBFD time unit.
[0082] In some implementations, the configuration information includes first configuration information indicating a first SRS resource set and second configuration information indicating a second SRS resource set.
[0083] In some implementations, terminal device 110 may also use a first SRS resource set and a second SRS resource set to send multiple SRS retransmissions.
[0084] In some implementations, terminal device 110 may also send SRS retransmissions on available time slots.
[0085] In some implementations, an available time slot is determined by the following conditions: for a time slot, whether one or more resources configured for SRS retransmission in the time slot are greater than or equal to the resources required for the SRS retransmission; and based on the determination that the one or more resources are greater than or equal to the resources required for the SRS retransmission, the time slot is determined to be an available time slot, wherein an SRS retransmission in the available time slot is counted as one SRS retransmission.
[0086] In some implementations, the time slot includes SBFD symbols and non-SBFD symbols, and the resources configured for SRS retransmission include a first SRS resource set within the uplink subband of the SBFD symbols and a second SRS resource set within the non-SBFD symbols.
[0087] In some implementations, the SRS transmission of the terminal device conflicts with the downlink transmission, and the terminal device 110 may also compare a first priority level of the SRS transmission with a second priority level of the downlink transmission; based on the comparison, i) the SRS transmission is sent to the network device, or ii) the DL transmission is received from the network device.
[0088] In some implementations, at least one of the following exists: the priority level of the aperiodic reference signal is higher than the priority level of the periodic or semi-persistent reference signal; the priority level of the pre-configured downlink reference signal is higher than the priority level of the periodic or semi-persistent uplink reference signal; the priority level of the aperiodic uplink reference signal is higher than the priority level of the pre-configured downlink reference signal; the priority level of the pre-configured downlink control channel is higher than the priority level of the periodic or semi-persistent uplink reference signal; or the priority level of the aperiodic uplink reference signal is higher than the priority level of the pre-configured downlink control channel.
[0089] In some implementations, terminal device 110 may further determine that the SRS to be transmitted spans SBFD time units and adjacent non-SBFD time units; determine whether the SRS resource set is within the uplink subband of the SBFD time unit in the frequency domain; and based on the determination that the SRS resource set is within the uplink subband of the SBFD time unit, transmit the SRS spanning the SBFD time unit and adjacent non-SBFD time units.
[0090] In some implementations, an SRS is configured to be transmitted on an SBFD time unit, and the terminal device 110 may also determine whether the SRS resource set at least partially overlaps with a frequency subband other than the uplink subband of the SBFD time unit; and based on the determination that the SRS resource set at least partially overlaps with the frequency subband other than the uplink subband, avoid transmitting the SRS on the SBFD time unit and postpone the transmission of the SRS.
[0091] In some implementations, a first resource set is associated with a first plurality of beams, and a second resource set is associated with a second plurality of beams.
[0092] In some implementations, the first resource set is associated with a first reference signal or a first identifier (ID) of the first reference signal, and the second resource set is associated with a second reference signal or a second ID of the second reference signal.
[0093] In some implementations, terminal device 110 may also receive frequency hopping indications for SRS transmission.
[0094] In some implementations, terminal device 110 may also send SRS to network device using a first frequency hopping pattern within an SBFD time unit; and send SRS to network device using a second frequency hopping pattern outside of an SBFD time unit, wherein at least one of the start position and frequency hopping step size of the second frequency hopping pattern is different from the first frequency hopping pattern.
[0095] In some implementations, the first frequency hopping step size of the first frequency hopping pattern is determined based on a scaling factor and the second frequency hopping step size of the second frequency hopping pattern.
[0096] In some implementations, terminal device 110 may also send SRS to network devices within the SBFD time unit without using frequency hopping.
[0097] In some implementations, terminal device 110 may also receive a power control configuration indicating a first power control parameter for SBFD time units and a second power control parameter for non-SBFD time units, wherein a first maximum value of the first power control parameter is less than a second maximum value of the second power control parameter.
[0098] In some implementations, the first resource includes a first beam, and the second resource includes a second beam.
[0099] Figure 11 A flowchart illustrating a method 1100 for communication implemented at a network device according to some embodiments of the present disclosure is provided. Method 1100 may be implemented at... Figure 1 The network devices shown are implemented in 120 locations. For discussion purposes, references will be made to... Figure 1 Method 1100 is described. It should be understood that method 1100 may include additional actions not shown and / or some actions shown may be omitted, and the scope of this disclosure is not limited in this respect.
[0100] At 1110, network device 120 sends a resource indicator associated with the uplink channel to the terminal device. At 1120, based on the uplink channel's time unit being an SBFD time unit, the network device uses a first resource indicated by the resource indicator in a first resource set to receive the uplink channel. The SBFD time unit is configured with frequency subbands for different link directions. At 1130, based on the time unit being a non-SBFD time unit, the network device uses a second resource indicated by the resource indicator in a second resource set to receive the uplink channel.
[0101] In some implementations, at least one of the following is present: the resource indicator is a sounding reference signal (SRS) resource indicator (SRI); the first resource set is a first sounding reference signal (SRS) resource set configured for the SBFD time unit, and the first resource set is in the uplink subband of the SBFD time unit in the frequency domain; the second resource set is a second SRS resource set configured for a non-SBFD time unit; or the uplink channel is a physical uplink shared channel (PUSCH).
[0102] In some implementations, network device 120 may also send configuration information indicating the first SRS resource set and the second SRS resource set to the terminal device.
[0103] In some implementations, the configuration information includes one or more parameters indicating a second SRS resource set, and the configuration information also includes at least one offset value, and the first SRS resource set is indicated by the one or more parameters and the at least one offset value.
[0104] In some implementations, the offset value is set to zero when the second SRS resource set is within the uplink subband of the SBFD time unit.
[0105] In some implementations, the configuration information includes first configuration information indicating a first SRS resource set and second configuration information indicating a second SRS resource set.
[0106] In some implementations, network device 120 may also use a first SRS resource set and a second SRS resource set to receive multiple SRS duplicate transmissions.
[0107] In some implementations, network device 120 may also send SRS retransmissions on available time slots.
[0108] In some implementations, an available time slot is determined by the following conditions: for a time slot, whether one or more resources configured for SRS retransmission in the time slot are greater than or equal to the resources required for the SRS retransmission; and based on the determination that the one or more resources are greater than or equal to the resources required for the SRS retransmission, the time slot is determined to be an available time slot, wherein an SRS retransmission in the available time slot is counted as one SRS retransmission.
[0109] In some implementations, the time slot includes SBFD symbols and non-SBFD symbols, and the resources configured for SRS retransmission include a first SRS resource set within the uplink subband of the SBFD symbols and a second SRS resource set within the non-SBFD symbols.
[0110] In some implementations, the SRS transmission of the terminal device conflicts with the downlink transmission, and the network device 120 may also compare the first priority level of the SRS transmission with the second priority level of the downlink transmission; based on the comparison, i) receive the SRS transmission from the terminal device, or ii) send a DL transmission to the terminal device.
[0111] In some implementations, at least one of the following exists: the priority level of the aperiodic reference signal is higher than the priority level of the periodic or semi-persistent reference signal; the priority level of the pre-configured downlink reference signal is higher than the priority level of the periodic or semi-persistent uplink reference signal; the priority level of the aperiodic uplink reference signal is higher than the priority level of the pre-configured downlink reference signal; the priority level of the pre-configured downlink control channel is higher than the priority level of the periodic or semi-persistent uplink reference signal; or the priority level of the aperiodic uplink reference signal is higher than the priority level of the pre-configured downlink control channel.
[0112] In some implementations, network device 120 may further determine that the SRS to be transmitted spans SBFD time units and adjacent non-SBFD time units; determine whether the SRS resource set is within the uplink subband of the SBFD time unit in the frequency domain; and, based on the determination that the SRS resource set is within the uplink subband of the SBFD time unit, receive the SRS spanning SBFD time units and adjacent non-SBFD time units.
[0113] In some implementations, an SRS is configured to be transmitted on an SBFD time unit, and network device 120 may also determine whether the SRS resource set at least partially overlaps with a frequency subband other than the uplink subband of the SBFD time unit; and based on the determination that the SRS resource set at least partially overlaps with the frequency subband other than the uplink subband, avoid receiving the SRS on the SBFD time unit and postpone the reception of the SRS.
[0114] In some implementations, a first resource set is associated with a first plurality of beams, and a second resource set is associated with a second plurality of beams.
[0115] In some implementations, the first resource set is associated with a first reference signal or a first identifier (ID) of the first reference signal, and the second resource set is associated with a second reference signal or a second ID of the second reference signal.
[0116] In some implementations, network device 120 may also send frequency hopping indications for SRS transmission.
[0117] In some implementations, network device 120 may also receive SRS using a first frequency hopping pattern within an SBFD time unit; and receive SRS using a second frequency hopping pattern outside of an SBFD time unit, wherein at least one of the start position and frequency hopping step size of the second frequency hopping pattern is different from the first frequency hopping pattern.
[0118] In some implementations, the first frequency hopping step size of the first frequency hopping pattern is determined based on a scaling factor and the second frequency hopping step size of the second frequency hopping pattern.
[0119] In some implementations, network device 120 can also receive SRS from terminal devices within SBFD time units without using frequency hopping.
[0120] In some implementations, network device 120 may also receive a power control configuration indicating a first power control parameter for SBFD time units and a second power control parameter for non-SBFD time units, wherein a first maximum value of the first power control parameter is less than a second maximum value of the second power control parameter.
[0121] In some implementations, the first resource includes a first beam, and the second resource includes a second beam.
[0122] Figure 12 This is a simplified block diagram of device 1200 suitable for implementing some embodiments of the present disclosure. Device 1200 can be considered as follows: Figure 1 Another example embodiment of the terminal device 110 or network device 120 shown. Therefore, device 1200 may be implemented in or be implemented as at least a part of the aforementioned network device or terminal device.
[0123] As shown in the figure, device 1200 includes a processor 1210, a memory 1220 coupled to the processor 1210, a suitable transceiver 1240 coupled to the processor 1210, and a communication interface coupled to the transceiver 1240. The memory 1210 stores at least a portion of a program 1230. Depending on requirements, the transceiver 1240 can be used for bidirectional or unidirectional communication. The transceiver 1240 may include at least one of a transmitter 1242 and a receiver 1244. The transmitter 1242 and receiver 1244 may be functional modules or physical entities. The transceiver 1240 has at least one antenna to facilitate communication; however, in practice, the access node mentioned in this application may have several antennas. The communication interface can represent any interface necessary for communication with other network elements, such as the X2 / Xn interface for bidirectional communication between eNBs / gNBs, the S1 / NG interface for communication between the Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and eNBs / gNBs, the Un interface for communication between eNBs / gNBs and relay nodes (RNs), or the Uu interface for communication between eNBs / gNBs and terminal equipment.
[0124] Assume that program 1230 includes program instructions that, when executed by the associated processor 1210, enable device 1200 to operate according to embodiments of this disclosure, as referenced herein. Figure 1 to Figure 11 The embodiments described herein may be implemented by computer software executable by processor 1210 of device 1200, or by hardware, or by a combination of software and hardware. Processor 1210 may be configured to implement various embodiments of this disclosure. Furthermore, a combination of processor 1210 and memory 1220 may form a processing unit 1250 suitable for implementing various embodiments of this disclosure.
[0125] Memory 1220 can be of any type suitable for a local technology network and can be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 1220 is shown in device 1200, several physically different memory modules may exist in device 1200. Processor 1210 can be of any type suitable for a local technology network and may include one or more of the following: as non-limiting examples, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Device 1200 may have multiple processors, such as application-specific integrated circuit chips, which are time-dependent on a clock that synchronizes the main processor.
[0126] In some implementations, the terminal device includes circuitry configured to perform method 1000 or 1100.
[0127] The components included in the apparatus and / or device disclosed herein can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In one embodiment, one or more units may be implemented using software and / or firmware (e.g., machine-executable instructions stored on a storage medium). As a supplement to or alternative to the machine-executable instructions, some or all of the units in the apparatus and / or device may be implemented at least partially by one or more hardware logic components. For example, but not limited to, exemplary types of hardware logic components that may be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), complex programmable logic devices (CPLDs), etc.
[0128] Generally, various embodiments of this disclosure can be implemented in hardware or special-purpose circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software executable by a controller, microprocessor, or other computing device. Although various aspects of embodiments of this disclosure are illustrated and described using block diagrams, flowcharts, or other illustrations, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, terminal devices, or methods described herein can be implemented in hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.
[0129] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions (such as those included in program modules) that execute on a target real or virtual processor in a device to perform the functions described above. Figure 2 to Figure 7 The process or method described in any of the above. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. The functionality of a program module can be combined in various implementation schemes or split among program modules as needed. The machine-executable instructions used for a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.
[0130] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0131] The aforementioned program code may be embodied on a machine-readable medium, which may be any tangible medium containing or storing a program used by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of machine-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0132] Furthermore, although the operations are described in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all the illustrated operations to achieve the desired result. In some environments, multitasking and parallel processing can be advantageous. While several specific implementation details are included in the discussion above, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular implementations. Certain features described in the context of individual implementations may also be implemented in a single implementation in combination. Conversely, various features described in the context of a single implementation may also be implemented individually or in any suitable sub-combination in multiple implementations.
[0133] Although this disclosure has been described using language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims.
[0134] In summary, the implementation schemes disclosed herein can provide the following solutions.
[0135] A terminal device includes a processor configured to: receive a resource indicator associated with an uplink channel from a network device; transmit the uplink channel using a first resource indicated by the resource indicator in a first resource set, based on the uplink channel's time unit being a subband non-overlapping full-duplex (SBFD) time unit, wherein the SBFD time unit is configured with frequency subbands for different link directions; and transmit the uplink channel using a second resource indicated by the resource indicator in a second resource set, based on the time unit being a non-SBFD time unit.
[0136] In one implementation, at least one of the following is present: the resource indicator is a sounding reference signal (SRS) resource indicator (SRI); the first resource set is a first sounding reference signal (SRS) resource set configured for the SBFD time unit, and the first resource set is in the uplink subband of the SBFD time unit in the frequency domain; the second resource set is a second SRS resource set configured for a non-SBFD time unit; or the uplink channel is a physical uplink shared channel (PUSCH).
[0137] In one implementation, the terminal device is further configured to receive configuration information from the network device indicating a first SRS resource set and a second SRS resource set.
[0138] In one embodiment, the configuration information includes one or more parameters indicating a second SRS resource set, and the configuration information also includes at least one offset value, and the first SRS resource set is indicated by the one or more parameters and the at least one offset value.
[0139] In one implementation, the offset value is set to zero if the second SRS resource set is within the uplink subband of the SBFD time unit.
[0140] In one implementation, the configuration information includes first configuration information indicating a first SRS resource set and second configuration information indicating a second SRS resource set.
[0141] In one implementation, the terminal device is further configured to use a first SRS resource set and a second SRS resource set to send multiple SRS retransmissions.
[0142] In one implementation, the terminal device is further configured to send repeated SRS transmissions on available time slots.
[0143] In one implementation, an available time slot is determined by the following conditions: for a time slot, whether one or more resources configured for SRS retransmission in the time slot are greater than or equal to the resources required for the SRS retransmission; and based on the determination that the one or more resources are greater than or equal to the resources required for the SRS retransmission, the time slot is determined to be an available time slot, wherein an SRS retransmission in the available time slot is counted as one SRS retransmission.
[0144] In one implementation, the time slot includes SBFD symbols and non-SBFD symbols, and the resources configured for SRS retransmission include a first SRS resource set within the uplink subband of the SBFD symbols and a second SRS resource set within the non-SBFD symbols.
[0145] In one implementation, the SRS transmission of the terminal device conflicts with the downlink transmission, and the terminal device further causes to: compare a first priority level of the SRS transmission with a second priority level of the downlink transmission; and based on the comparison, i) transmit the SRS transmission to the network device, or ii) receive the DL transmission from the network device.
[0146] In one implementation, at least one of the following is present: the priority level of the aperiodic reference signal is higher than the priority level of the periodic or semi-persistent reference signal; the priority level of the pre-configured downlink reference signal is higher than the priority level of the periodic or semi-persistent uplink reference signal; the priority level of the aperiodic uplink reference signal is higher than the priority level of the pre-configured downlink reference signal; the priority level of the pre-configured downlink control channel is higher than the priority level of the periodic or semi-persistent uplink reference signal; or the priority level of the aperiodic uplink reference signal is higher than the priority level of the pre-configured downlink control channel.
[0147] In one embodiment, the terminal device is further configured to: determine that the SRS to be transmitted spans an SBFD time unit and an adjacent non-SBFD time unit; determine whether the SRS resource set is within the uplink subband of the SBFD time unit in the frequency domain; and based on the determination that the SRS resource set is within the uplink subband of the SBFD time unit, transmit the SRS spanning the SBFD time unit and the adjacent non-SBFD time unit.
[0148] In one implementation, one of the SRS is configured to be transmitted on the SBFD time unit, and wherein the terminal device further causes the terminal device to: determine whether the SRS resource set at least partially overlaps with a frequency subband other than the uplink subband of the SBFD time unit; and based on the determination that the SRS resource set at least partially overlaps with the frequency subband other than the uplink subband, avoid transmitting the SRS on the SBFD time unit and postpone the transmission of the SRS.
[0149] In one implementation, the first resource set is associated with a first plurality of beams, and the second resource set is associated with a second plurality of beams.
[0150] In one embodiment, the first resource set is associated with a first reference signal or a first identifier (ID) of the first reference signal, and the second resource set is associated with a second reference signal or a second ID of the second reference signal.
[0151] In one embodiment, the terminal device is further configured to receive a frequency hopping indication for SRS transmission.
[0152] In one embodiment, the terminal device is further configured to: transmit SRS to the network device using a first frequency hopping pattern within an SBFD time unit; and transmit SRS to the network device using a second frequency hopping pattern outside of an SBFD time unit, wherein at least one of the start position and frequency hopping step size of the second frequency hopping pattern is different from that of the first frequency hopping pattern.
[0153] In one implementation, the first frequency hopping step size of the first frequency hopping pattern is determined based on a scaling factor and the second frequency hopping step size of the second frequency hopping pattern.
[0154] In one implementation, the terminal device is further configured to send SRS to the network device within the SBFD time unit without using frequency hopping.
[0155] In one embodiment, the terminal device is further configured to receive a power control configuration indicating a first power control parameter for an SBFD time unit and a second power control parameter for a non-SBFD time unit, wherein a first maximum value of the first power control parameter is less than a second maximum value of the second power control parameter.
[0156] In one embodiment, the first resource includes a first beam, and the second resource includes a second beam.
[0157] A network device includes a processor configured to: send a resource indicator associated with an uplink channel to an end device; receive the uplink channel using a first resource indicated by the resource indicator in a first resource set, based on the uplink channel's time unit being a subband non-overlapping full-duplex (SBFD) time unit, wherein the SBFD time unit is configured with frequency subbands for different link directions; and receive the uplink channel using a second resource indicated by the resource indicator in a second resource set, based on the time unit being a non-SBFD time unit.
[0158] In one implementation, at least one of the following is present: the resource indicator is a sounding reference signal (SRS) resource indicator (SRI); the first resource set is a first sounding reference signal (SRS) resource set configured for the SBFD time unit, and the first resource set is in the uplink subband of the SBFD time unit in the frequency domain; the second resource set is a second SRS resource set configured for a non-SBFD time unit; or the uplink channel is a physical uplink shared channel (PUSCH).
[0159] In one implementation, the network device is further configured to send configuration information indicating the first SRS resource set and the second SRS resource set to the terminal device.
[0160] In one embodiment, the configuration information includes one or more parameters indicating a second SRS resource set, and the configuration information also includes at least one offset value, and the first SRS resource set is indicated by the one or more parameters and the at least one offset value.
[0161] In one implementation, the offset value is set to zero if the second SRS resource set is within the uplink subband of the SBFD time unit.
[0162] In one implementation, the configuration information includes first configuration information indicating a first SRS resource set and second configuration information indicating a second SRS resource set.
[0163] In one implementation, the network device is further configured to use a first SRS resource set and a second SRS resource set to receive multiple SRS duplicate transmissions.
[0164] In one implementation, the network device is further configured to send repeated SRS transmissions on available time slots.
[0165] In one implementation, an available time slot is determined by the following conditions: for a time slot, whether one or more resources configured for SRS retransmission in the time slot are greater than or equal to the resources required for the SRS retransmission; and based on the determination that the one or more resources are greater than or equal to the resources required for the SRS retransmission, the time slot is determined to be an available time slot, wherein an SRS retransmission in the available time slot is counted as one SRS retransmission.
[0166] In one implementation, the time slot includes SBFD symbols and non-SBFD symbols, and the resources configured for SRS retransmission include a first SRS resource set within the uplink subband of the SBFD symbols and a second SRS resource set within the non-SBFD symbols.
[0167] In one implementation, the SRS transmission of the terminal device conflicts with the downlink transmission, and the network device further causes the network device to: compare a first priority level of the SRS transmission with a second priority level of the downlink transmission; and based on the comparison, i) receive the SRS transmission from the terminal device, or ii) send a DL transmission to the terminal device.
[0168] In one implementation, at least one of the following is present: the priority level of the aperiodic reference signal is higher than the priority level of the periodic or semi-persistent reference signal; the priority level of the pre-configured downlink reference signal is higher than the priority level of the periodic or semi-persistent uplink reference signal; the priority level of the aperiodic uplink reference signal is higher than the priority level of the pre-configured downlink reference signal; the priority level of the pre-configured downlink control channel is higher than the priority level of the periodic or semi-persistent uplink reference signal; or the priority level of the aperiodic uplink reference signal is higher than the priority level of the pre-configured downlink control channel.
[0169] In one embodiment, the network device is further configured to: determine that the SRS to be transmitted spans an SBFD time unit and an adjacent non-SBFD time unit; determine whether the SRS resource set is within the uplink subband of the SBFD time unit in the frequency domain; and, based on the determination that the SRS resource set is within the uplink subband of the SBFD time unit, receive the SRS spanning the SBFD time unit and the adjacent non-SBFD time unit.
[0170] In one implementation, one of the SRS is configured to be transmitted on the SBFD time unit, and wherein the network device further causes the network device to: determine whether the SRS resource set at least partially overlaps with a frequency subband other than the uplink subband of the SBFD time unit; and based on the determination that the SRS resource set at least partially overlaps with the frequency subband other than the uplink subband, avoid receiving the SRS on the SBFD time unit and postpone the reception of the SRS.
[0171] In one implementation, the first resource set is associated with a first plurality of beams, and the second resource set is associated with a second plurality of beams.
[0172] In one embodiment, the first resource set is associated with a first reference signal or a first identifier (ID) of the first reference signal, and the second resource set is associated with a second reference signal or a second ID of the second reference signal.
[0173] In one implementation, the network device is further configured to send a frequency hopping indication for SRS transmission.
[0174] In one embodiment, the network device is further configured to: receive SRS using a first frequency hopping pattern within an SBFD time unit; and receive SRS using a second frequency hopping pattern outside an SBFD time unit, wherein at least one of the start position and frequency hopping step size of the second frequency hopping pattern is different from the first frequency hopping pattern.
[0175] In one implementation, the first frequency hopping step size of the first frequency hopping pattern is determined based on a scaling factor and the second frequency hopping step size of the second frequency hopping pattern.
[0176] In one implementation, the network device is further configured to receive SRS from the terminal device within an SBFD time unit without using frequency hopping.
[0177] In one embodiment, the network device is further configured to receive a power control configuration indicating a first power control parameter for an SBFD time unit and a second power control parameter for a non-SBFD time unit, wherein a first maximum value of the first power control parameter is less than a second maximum value of the second power control parameter.
[0178] In one embodiment, the first resource includes a first beam, and the second resource includes a second beam.
[0179] A communication method includes: receiving, at a terminal device, a resource indicator associated with an uplink channel from a network device; transmitting the uplink channel using a first resource indicated by the resource indicator in a first resource set, based on the uplink channel's time unit being a subband non-overlapping full-duplex (SBFD) time unit, wherein the SBFD time unit is configured with frequency subbands for different link directions; and transmitting the uplink channel using a second resource indicated by the resource indicator in a second resource set, based on the time unit being a non-SBFD time unit.
[0180] A communication method includes: transmitting a resource indicator associated with an uplink channel to a terminal device at a network device; receiving the uplink channel using a first resource indicated by the resource indicator in a first resource set, based on the uplink channel's time unit being a subband non-overlapping full-duplex (SBFD) time unit, wherein the SBFD time unit is configured with frequency subbands for different link directions; and receiving the uplink channel using a second resource indicated by the resource indicator in a second resource set, based on the time unit being a non-SBFD time unit.
[0181] A computer-readable medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform the methods described above.
Claims
1. A terminal device, the terminal device comprising: a processor configured to cause the terminal device to: receive, from a network device, a resource indicator associated with an uplink channel; based on a time unit of the uplink channel being a sub-band non-overlapping full duplex (SBFD) time unit, transmit the uplink channel using first resources indicated in a first resource set by the resource indicator, wherein the SBFD time unit is configured with frequency sub-bands for different link directions; and based on the time unit being a non-SBFD time unit, transmit the uplink channel using second resources indicated in a second resource set by the resource indicator. 2.The terminal device of claim 1, wherein there is at least one of: the resource indicator is a sounding reference signal (SRS) resource indicator (SRI); the first resource set is a first sounding reference signal (SRS) resource set configured for the SBFD time unit, and the first resource set is within an uplink sub-band of the SBFD time unit in a frequency domain; the second resource set is a second SRS resource set configured for the non-SBFD time unit; or the uplink channel is a physical uplink shared channel (PUSCH). 3.The terminal device of claim 1 or 2, wherein the terminal device is further caused to: receive, from the network device, configuration information indicating the first SRS resource set and the second SRS resource set. 4.The terminal device of claim 3, wherein: the configuration information comprises one or more parameters indicating the second SRS resource set, and the configuration information further comprises at least one offset value, and the first SRS resource set is indicated by the one or more parameters and the at least one offset value. 5.The terminal device of claim 4, wherein the offset value is set to zero in a case that the second SRS resource set is within an uplink sub-band of the SBFD time unit. 6.The terminal device of claim 3, wherein the configuration information comprises first configuration information indicating the first SRS resource set and second configuration information indicating the second SRS resource set. 7.The terminal device of any one of claims 2 to 6, wherein the terminal device is further caused to: transmit a plurality of SRS repetitions using the first SRS resource set and the second SRS resource set. 8.The terminal device of any one of claims 1 to 7, wherein the terminal device is further caused to transmit SRS repetitions on available slots. 9.The terminal device of claim 8, wherein the available slots are determined by: for a slot, determining whether one or more resources configured for the SRS repetition in the slot is greater than or equal to resources required for the SRS repetition; and based on determining that the one or more resources is greater than or equal to the resources required for the SRS repetition, determining the slot as the available slot. wherein the SRS repetition transmissions in the available slots are counted as one SRS repetition.
10. The terminal device of claim 9, wherein: the slots comprise SBFD symbols and non-SBFD symbols, and the resources configured for the SRS repetition transmissions comprise a first set of SRS resources within an uplink sub-band of the SBFD symbols and a second set of SRS resources in the non-SBFD symbols.
11. The terminal device of any one of claims 1-10, wherein an SRS transmission of the terminal device collides with a downlink transmission, and wherein the terminal device is further caused to: compare a first priority level of the SRS transmission with a second priority level of the downlink transmission; and based on the comparison, i) transmit the SRS transmission to the network device, or ii) receive the DL transmission from the network device.
12. The terminal device of claim 11, wherein there is at least one of: a priority level of an aperiodic reference signal is higher than a priority level of a periodic or semi-persistent reference signal; a priority level of a pre-configured downlink reference signal is higher than a priority level of a periodic or semi-persistent uplink reference signal; a priority level of an aperiodic uplink reference signal is higher than a priority level of a pre-configured downlink reference signal; a priority level of a pre-configured downlink control channel is higher than a priority level of a periodic or semi-persistent uplink reference signal; or, a priority level of an aperiodic uplink reference signal is higher than a priority level of a pre-configured downlink control channel.
13. The terminal device of any one of claims 1-12, wherein the terminal device is further caused to: determine that a SRS to be transmitted spans an SBFD time unit and an adjacent non-SBFD time unit; determine whether a set of SRS resources is within an uplink sub-band of the SBFD time unit in the frequency domain; and based on determining that the set of SRS resources is within the uplink sub-band of the SBFD time unit, transmit the SRS spanning the SBFD time unit and the adjacent non-SBFD time unit.
14. The terminal device of any one of claims 1-13, wherein SRS is configured to be transmitted on the SBFD time unit, and wherein the terminal device is further caused to: determine whether a set of SRS resources at least partially overlaps a frequency sub-band other than the uplink sub-band of the SBFD time unit; and based on determining that the set of SRS resources at least partially overlaps the frequency sub-band other than the uplink sub-band, circumvent transmitting the SRS on the SBFD time unit and postpone transmission of the SRS.
15. The terminal device of any one of claims 1-14, wherein the first set of resources is associated with a first plurality of beams and the second set of resources is associated with a second plurality of beams.
16. The terminal device of claim 15, wherein the first set of resources is associated with a first reference signal or with a first identifier (ID) of the first reference signal, and the second set of resources is associated with a second reference signal or with a second ID of the second reference signal.
17. The terminal device of any one of claims 1-16, wherein the terminal device is further caused to: receive a frequency hopping indication for SRS transmission.
18. The terminal device of claim 17, wherein the terminal device is further caused to: transmit the SRS to the network device using a first frequency hopping pattern within the SBFD time unit; and transmit the SRS to the network device using a second frequency hopping pattern within the non-SBFD time unit, wherein at least one of a starting position and a frequency hopping step size of the second frequency hopping pattern is different from the first frequency hopping pattern.
19. The terminal device of claim 17, wherein a first frequency hopping step size of the first frequency hopping pattern is determined according to a scaling factor and a second frequency hopping step size of the second frequency hopping pattern.
20. The terminal device of claim 17, wherein the terminal device is further caused to: transmit the SRS to the network device without frequency hopping within the SBFD time unit.
Citation Information
Cited By
Reference signal transmission in subband full-duplex and non-subband full-duplex slots
US20250112744A1
