Signal sending and receiving method, apparatus, and communication system

Abstract

Embodiments of the present application provide a signal sending and receiving method, an apparatus, and a communication system. The method comprises: a terminal device receives a serving cell configuration of one or more cells, at least one cell of the one or more cells having a first time domain resource and / or a second time domain resource, wherein in the second time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the first time domain resource is outside the second time domain resource; and the terminal device sends an uplink signal in a cell having the first time domain resource and / or the second time domain resource.

Description

Signal transmission and reception methods, devices and communication systems Technical Field

[0001] This application relates to the field of communication technology. Background Technology

[0002] Terminal devices can send uplink signals to network devices, including Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Sounding Reference Signal (SRS), Physical Random Access Channel (PRACH), and so on. PUSCH can be scheduled by Downlink Control Information (DCI), such as DCI format 0_1 / 0_2 / 0_3; or, PUSCH can be scheduled by Configured Grant (CG) information, such as Type 1 CG PUSCH or Type 2 CG PUSCH.

[0003] Carrier aggregation (CA) combines multiple carriers to create a wider bandwidth, thereby achieving higher data transmission rates. It supports the following aggregation methods: Intra-band CA: combining multiple carriers within the same frequency band; Inter-band CA: combining multiple carriers from different frequency bands.

[0004] Dual Connectivity (DC) allows terminal devices (such as mobile phones) to connect to two base stations simultaneously, improving network performance and user experience. In 5G, dual connectivity technology has been further developed to support various scenarios, including dual connectivity between 4G and 5G base stations (EN-DC) and dual connectivity between 5G base stations (NR-DC). In dual connectivity mode, the terminal device connects to a master node (MN) and a secondary node (SN). The master node is responsible for interacting with the core network's control plane, while the secondary node provides additional radio resources. The master node and secondary node manage the master cell group (MCG) and secondary cell group (SCG), respectively, and each cell group can contain one or more cells.

[0005] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application. Summary of the Invention

[0006] In traditional technologies, for Time Division Duplex (TDD) bands, uplink transmission can only occur within the uplink time slot. When limited or few uplink time slots are allocated, problems arise such as small uplink coverage, limited capacity, and high latency. To improve uplink capacity and coverage, and reduce uplink latency, network devices in TDD bands can operate in full-duplex mode at certain time points. For example, at these time points, the network device simultaneously receives and transmits on different frequency domain resources within the corresponding carrier in the TDD band. This operating mode is, for example, called Subband Non-overlapping Full Duplex (SBFD), but is not limited to this. Under this operating mode, there may be differences in the beam, uplink and downlink channel states, power control parameters, and frequency domain resources available for uplink signal transmission corresponding to different time domain resources.

[0007] However, given the existence of the aforementioned different time-domain resources, there are currently no solutions for how to support the transmission and reception of uplink signals, whether / how to support carrier aggregation / dual connectivity with at least some cells or carriers having the aforementioned different time-domain resources, and specifically, for example, how to calculate and report power margins and how to handle link direction conflicts in the above situations.

[0008] To address at least one of the above-mentioned problems, embodiments of this application provide a signal transmission and reception method, apparatus, and communication system.

[0009] According to one aspect of the embodiments of this application, a signal transmission method is provided, including:

[0010] The terminal device receives serving cell configurations for one or more cells, at least one of the one or more cells having first time domain resources and / or second time domain resources, wherein, in the second time domain resources, the first frequency domain resources are used for uplink and the second frequency domain resources are used for downlink, and the first time domain resources are outside the second time domain resources;

[0011] The terminal device transmits uplink signals in a cell that has the first time domain resources and / or the second time domain resources.

[0012] According to another aspect of the embodiments of this application, a signal transmitting device is provided, comprising:

[0013] A receiver receives serving cell configurations for one or more cells, at least one of which has a first time-domain resource and / or a second time-domain resource, wherein, in the second time-domain resource, the first frequency-domain resource is used for uplink and the second frequency-domain resource is used for downlink, and the first time-domain resource is outside the second time-domain resource;

[0014] A transmitter that transmits uplink signals in a cell having the first time domain resource and / or the second time domain resource.

[0015] According to another aspect of the embodiments of this application, a signal receiving method is provided, including:

[0016] The network device sends serving cell configurations for one or more cells, at least one of the one or more cells having first time domain resources and / or second time domain resources, wherein, in the second time domain resources, the first frequency domain resources are used for uplink and the second frequency domain resources are used for downlink, and the first time domain resources are outside the second time domain resources;

[0017] The network device receives uplink signals in a cell that has the first time domain resources and / or the second time domain resources.

[0018] According to another aspect of the embodiments of this application, a signal receiving device is provided, comprising:

[0019] A transmitter that transmits serving cell configurations for one or more cells, at least one of the one or more cells having a first time domain resource and / or a second time domain resource, wherein, in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the first time domain resource is outside the second time domain resource;

[0020] A receiver that receives uplink signals in a cell having the first time domain resources and / or the second time domain resources.

[0021] According to another aspect of the embodiments of this application, a communication system is provided, including:

[0022] A network device that transmits serving cell configurations for one or more cells, at least one of the one or more cells having first time-domain resources and / or second time-domain resources, wherein, in the second time-domain resources, the first frequency-domain resources are used for uplink and the second frequency-domain resources are used for downlink, and the first time-domain resources are outside the second time-domain resources; and receives uplink signals in cells having the first time-domain resources and / or the second time-domain resources;

[0023] A terminal device that receives serving cell configurations for one or more cells; and transmits uplink signals in cells having the first time domain resources and / or the second time domain resources.

[0024] One of the beneficial effects of the embodiments of this application includes: in the presence of different time-domain resources, such as beams, channel states, frequency domain resources for uplink, and power control parameters, which may correspond to different beams, channel states, frequency domain resources for uplink, and power control parameters, the terminal device receives the serving cell configuration and transmits uplink signals in a cell with first time-domain resources and / or second time-domain resources, which can support the transmission and reception of uplink signals in the presence of the above-mentioned different time-domain resources.

[0025] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

[0026] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with or replacing features in other embodiments.

[0027] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0028] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0029] The accompanying drawings, which form part of the specification, are used to provide a further understanding of the embodiments of this application and illustrate the implementation methods of this application, together with the textual description, to explain the principles of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without creative effort. In the drawings:

[0030] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;

[0031] Figure 2 is a schematic diagram of a signal transmission method according to an embodiment of this application;

[0032] Figure 3 is an example diagram of time-domain resources according to an embodiment of this application;

[0033] Figure 4 is an example diagram of uplink available PRB according to an embodiment of this application;

[0034] Figure 5 is an example diagram of downlink available PRB according to an embodiment of this application;

[0035] Figure 6 is a schematic diagram of a signal receiving method according to an embodiment of this application;

[0036] Figure 7 is a schematic diagram of a signal transmitting device according to an embodiment of this application;

[0037] Figure 8 is a schematic diagram of a signal receiving device according to an embodiment of this application;

[0038] Figure 9 is a schematic diagram of a network device according to an embodiment of this application;

[0039] Figure 10 is a schematic diagram of a terminal device according to an embodiment of this application. Detailed Implementation

[0040] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0041] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0042] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly interpreted as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," the term "based on" should be understood as "at least partially based on…," and the term "related to…" should be understood as "at least partially related to…," unless the context explicitly indicates otherwise. In some embodiments, "according to," "based on," and "related to…" can be used interchangeably, but this application is not limited thereto.

[0043] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0044] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), 6G, etc., and / or other currently known or future communication protocols.

[0045] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transceiver node (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0046] Base stations can include, but are not limited to: NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), IAB hosts, etc. They can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" can include some or all of their functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0047] In the embodiments of this application, the term "User Equipment" (UE) refers to a device that accesses a communication network and receives network services through a network device, and can also be called "Terminal Equipment" (TE). Terminal equipment can be fixed or mobile, and can also be called a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, mobile terminal (MT), etc.

[0048] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptops, cordless phones, smartphones, smartwatches, digital cameras, etc.

[0049] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.

[0050] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.

[0051] In the following description, without causing confusion, the terms “uplink control signal” and “uplink control information (UCI)” or “physical uplink control channel (PUCCH)” are used interchangeably, as are the terms “uplink data signal” and “uplink data information” or “physical uplink shared channel (PUSCH)”.

[0052] The terms “downlink control signal” and “downlink control information (DCI)” or “physical downlink control channel (PDCCH)” are interchangeable, as are the terms “downlink data signal” and “downlink data information (PDSCH)” or “physical downlink shared channel (PDSCH)”.

[0053] Additionally, uplink signals can include uplink data signals and / or uplink control signals and / or PRACH and / or SRS, etc., and can also be referred to as uplink transmission (UL transmission), uplink information, or uplink channel. Sending / receiving uplink transmission on uplink resources can be understood as using that uplink resource to send / receive the uplink transmission. Downlink signals can include downlink data signals and / or downlink control signals and / or synchronization signals (SS, such as PSS / SSS) and / or broadcast channel (PBCH) and / or SSB (SS / PBCH block, including PSS, SSS, and PBCH and their DMRS) and / or CSI-RS, etc., and can also be referred to as downlink transmission (DL transmission), downlink information, or downlink channel. Sending / receiving downlink transmission on downlink resources can be understood as using that downlink resource to send / receive the downlink transmission.

[0054] In the embodiments of this application, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling; RRC signaling may include, for example, RRC messages, such as broadcast / public RRC messages / signaling (e.g., Master Information Block (MIB), system information), dedicated RRC messages / signaling; or RRC information elements (RRC IE); or information fields (or information fields included in information fields) included in RRC messages or RRC information elements. Higher-layer signaling may also be, for example, Medium Access Control (MAC) signaling; or referred to as MAC control elements (MAC CE). However, this application is not limited to these. The names of signaling (e.g., RRC messages, information elements IE, information fields, higher-layer parameters, etc.) used in the embodiments of this application are only examples and may be other names, which are not intended to limit the scope of this application. The '-rN' (e.g., -r17, etc.) in the higher-layer parameter names may be omitted (without causing ambiguity).

[0055] In the embodiments of this application, "multiple" refers to at least two, or two or more.

[0056] In the embodiments of this application, "predefined" refers to what is specified by the protocol or determined according to the rules specified by the protocol, and does not require additional configuration. "Configuration / instruction / providement" refers to what the network device directly or indirectly configures / instructs / provides through higher-layer signaling and / or physical layer signaling. Configuration / instruction can be achieved by introducing higher-layer parameters into the higher-layer signaling. Higher-layer parameters refer to information fields and / or information elements / information units / information cells (IE) / control elements (CE) in the higher-layer signaling. Physical layer signaling refers to, for example, control information (DCI) carried by the physical downlink control channel or control information carried by the sequence, but is not limited to these.

[0057] For ease of description, the following description uses a base station as an example of an access network device. In the following descriptions, "if…", "in the case of…", and "when…" are used interchangeably unless there is confusion. For resources in the frequency domain, "carrier" and "resource grid" are interchangeable; "subcarrier spacing configuration (μ)" and "subcarrier spacing (SCS) (Δf)" are interchangeable; "subcarrier spacing" and "numerology" are interchangeable; "resource block," "RB," and "PRB," "physical resource block," and "common resource block (CRB)" are interchangeable; "configuration / indication / providance / given" are interchangeable; "index" and "identifier (ID)" are interchangeable.

[0058] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0059] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, illustrating the case of a terminal device and a network device as examples. As shown in Figure 1, the communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, Figure 1 only illustrates the case of two terminal devices and one network device, but the embodiments of this application are not limited to this.

[0060] In this embodiment of the application, network device 101 and terminal devices 102 and 103 can transmit existing services or services that can be implemented in the future. For example, these services may include, but are not limited to: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0061] Terminal device 102 can send data to network device 101, for example, using authorized or unauthorized transmission methods. Network device 101 can receive data sent by one or more terminal devices 102 and provide feedback to terminal devices 102, such as ACK / NACK confirmation information. Based on the feedback information, terminal device 102 can confirm the end of the transmission process, or can initiate new data transmission, or can retransmit the data.

[0062] Network device 101 can send data to terminal device 102 and / or terminal device 103 using unicast, multicast, or broadcast. Terminal device 102 can receive data sent by one or more network devices (e.g., dual-connection or multi-connection) via a downlink or by terminal device 103 via a sidelink.

[0063] It is worth noting that Figure 1 shows that both terminal devices 102 and 103 are within the coverage area of ​​network device 101, but this application is not limited to this. Both terminal devices 102 and 103 may be outside the coverage area of ​​network device 101, or one terminal device 102 may be within the coverage area of ​​network device 101 while the other terminal device 103 may be outside the coverage area of ​​network device 101.

[0064] Furthermore, the content within parentheses is explanatory, exemplary, or optional. For example, in some embodiments, the expressions or limitations within parentheses may be included, while in other embodiments, they may be omitted. " / " indicates "and / or," and this application is not limited thereto. Various embodiments of this application will be described below with reference to the accompanying drawings. These embodiments are merely exemplary and not intended to limit the scope of this application.

[0065] First aspect of the embodiments

[0066] This application provides a method for transmitting uplink signals, which will be described from the perspective of the terminal device.

[0067] Figure 2 is a schematic diagram of an uplink signal transmission method according to an embodiment of this application. As shown in Figure 2, the method includes:

[0068] 201. The terminal device receives a serving cell configuration for one or more (serving) cells, at least one of the one or more (serving) cells having a first time domain resource and / or a second time domain resource, wherein, (in the (serving) cell having the first time domain resource and / or the second time domain resource), in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the first time domain resource is outside the second time domain resource; and

[0069] 202, the terminal device transmits an uplink signal in (serving) cells having the first time domain resources and / or the second time domain resources (in the second time domain resources (indicated as downlink or flexible by (first uplink / downlink configuration)) and / or not in the first time domain resources (indicated as downlink by (first uplink / downlink configuration and / or second uplink / downlink configuration)).

[0070] It is worth noting that Figure 2 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 2 above.

[0071] In some embodiments, the terminal device may be an SBFD-aware device; however, this application is not limited thereto. For example, during the initial access procedure (from RRC_IDLE to RRC_Connected state, including CBRA) and / or the random access procedure (e.g., CBRA) and / or the RRCSetupComplete message and / or in the capability information, the terminal device indicates to the network device that the terminal device is an SBFD-aware device (SBFD-aware UE).

[0072] For example, during random access, the terminal device is indicated to be an SBFD-aware device via the RO / PRACH and / or Msg3 used to send the preamble. For instance, some ROs (first ROs) are not limited to use by SBFD-aware UEs (other UEs can also use them), while some ROs (second ROs) are limited to use by SBFD-aware devices. Therefore, when a UE uses a second RO to send the preamble / PRACH, the base station knows that the UE is an SBFD-aware device (and consequently, the subsequent Msg3 and / or RRCSetupComplete message and / or capability information may include / not include information indicating that the UE is an SBFD-aware device). For example, (when the UE uses a first RO to send the preamble / PRACH), the Msg3 and / or RRCSetupComplete message and / or capability information include information indicating that the UE is an SBFD-aware device.

[0073] For example, an SBFD-aware UE has capabilities related to SBFD operation, including one or more of the following: being able to know the SBFD configuration, such as the configuration of the first time domain resources and / or the second time domain resources and / or the first frequency domain resources and / or the second frequency domain resources described below; being able to configure transmit and receive signals according to the SBFD; and being able to transmit uplink signals on (DL)SBFD symbols.

[0074] In some embodiments, the terminal device is configured with one or more (serving) cells, and / or, the one or more (serving) cells belong to the same cell group or the multiple (serving) cells include (serving) cells belonging to different cell groups, and / or, the one or more (serving) cells include Pcells and / or Scells and / or PScells and / or PUCCH-Scells, and / or, the serving cell configuration is dedicated Radio Resource Control (RRC) signaling (or carried by dedicated RRC signaling or included in dedicated RRC signaling). In the context of this application, the terms "serving cell" and "cell," "primary cell and / or secondary cell," etc., are interchangeable.

[0075] For example, a cell group can be a Master Cell Group (MCG) or a Secondary Cell Group (SCG). MCGs and SCGs can have dual connectivity (DC). A primary cell (Pcell) within an MCG is used for initial access, while a primary secondary cell (PScell) within an SCG is a primary cell used for initial access by the UE within the SCG. Pcells and secondary cells (Scells) within an MCG can perform carrier aggregation (CA), and PScells and Scells within an SCG can also perform carrier aggregation. Pcells and PScells can be collectively referred to as SpCells (Special Cells). A PUCCH-Scell, for example, refers to a secondary cell (SCell) used to transmit uplink control information (UCI) via PUCCH, or a secondary cell configured with PUCCH. For example, the PUCCH-Scell ​​(PUCCH in PUCCH) is used to transmit control information such as HARQ feedback, scheduling requests (SR), or CSI reports. The PUCCH-Scell ​​is one of the Scells in the MCG; the SCG and PUCCH-Scell ​​cannot be configured simultaneously.

[0076] In some embodiments, the terminal device receives serving cell configurations for one or more cells (each). The "serving cell configuration" is used to configure cell-specific parameters and / or UE-specific parameters of the cell, and is sent in dedicated (RRC) signaling, such as a ServingCellConfig IE. This IE is used to configure (add or modify) the serving cell for the terminal device, which can be the SpCell or Scell ​​of an MCG or SCG.

[0077] In some embodiments, a cell is a Pcell / PScell / SpCell / PUCCH-Scell / Scell / primary cell / serving cell. For example, when a UE is configured with one or more serving cells, each serving cell is a Pcell / PScell / SpCell / PUCCH-Scell / Scell / primary cell.

[0078] In some embodiments, when the UE is configured with only one serving cell, the serving cell is a Pcell, which has a first time domain resource and / or a second time domain resource.

[0079] In some embodiments, when a UE is configured with multiple serving cells, at least one of the cells has a first time-domain resource and / or a second time-domain resource:

[0080] For example, when a UE is configured with an SCG, the multiple serving cells include serving cells belonging to different cell groups, that is, at least Pcell and PScell, and may also include Scells of one or more MCGs or SCGs.

[0081] For example, when the UE is not configured with an SCG, the multiple serving cells include serving cells belonging to the same cell group (MCG), i.e., including Pcells and Scells of one or more MCGs. For example, one of the Scells can be configured as a PUCCH-Scell. When the UE is configured with a PUCCH-Scell, PUCCH or uplink control information for serving cells(one or more) in a PUCCH group (e.g., a primary PUCCH group) can be sent in the Pcell (or, uplink control information for serving cells in that PUCCH group can be sent via PUCCH in the Pcell), and PUCCH / uplink control information for serving cells(one or more) in another PUCCH group (e.g., a secondary PUCCH group) can be sent in the PUCCH-Scell ​​(or, uplink control information for serving cells in that other PUCCH group can be sent via PUCCH in the PUCCH-Scell). For power margin calculation, the PUCCH-Scell ​​can also be regarded as the primary cell of the serving cell in the secondary PUCCH group, while the Pcell is only the primary cell of the serving cell in the primary PUCCH group.

[0082] In some embodiments, a cell having (configured) first time-domain resources and / or second time-domain resources may also be referred to as a cell configured with SBFD feature / operation.

[0083] The following describes the first time-domain resources and / or the second time-domain resources.

[0084] In some embodiments, for a cell or carrier, in the second time domain resources, different frequency domain resources are respectively (only) used for (network device receiving) uplink (e.g., corresponding to the first frequency domain resources and / or the third frequency domain resources described below) and (only) used for (network device transmitting) downlink (e.g., corresponding to the second frequency domain resources and / or the fourth frequency domain resources described below). For example, the network device can simultaneously receive (uplink signals) in the frequency domain resources (only) used for uplink and transmit (downlink signals) in the frequency domain resources (only) used for downlink. The first time domain resources are outside the second time domain resources. For example, in the first time domain resources, different frequency domain resources are all used for uplink or all used for downlink. That is, the frequency domain resources are not divided into frequency domain resources (only) used for uplink and (only) used for downlink, and the network device does not receive and transmit at the same time.

[0085] In some embodiments, the time-domain resource type includes a first time-domain resource and a second time-domain resource. The first time-domain resource and the second time-domain resource can also be referred to as a first symbol and a second symbol, respectively; that is, the symbol type includes a first symbol and a second symbol. For example, SBFD symbol (second symbol) and non-SBFD symbol (first symbol). However, this application is not limited to this and can also be applied to other scenarios. For example, the first time-domain resource and the second time-domain resource can respectively refer to different time-domain resources defined in other ways. For convenience, the terms "SBFD symbol" and "non-SBFD symbol" will be used below.

[0086] In some embodiments, SBFD symbols and / or non-SBFD symbols are configured for different cells / carriers.

[0087] In some embodiments, information for configuring SBFD symbols and / or non-SBFD symbols is provided by higher-layer signaling. For example, higher-layer parameters for configuring SBFD symbols may optionally exist in SIB1 and / or the SIB ServingCellConfigCommonSIB IE and / or the ServingCellConfigCommon IE (within the ServingTDD-UL-DL-ConfigCommon IE, which contains the TDD-UL-DL-Pattern IE), and / or, higher-layer parameters for configuring SBFD symbols may optionally exist in the ServingCellConfig.

[0088] In some embodiments, a cell / carrier can be configured with one or more (e.g., two) TDD uplink / downlink patterns. When multiple patterns are configured, different patterns may or may not have corresponding SBFD symbols, and different patterns are independently configured with corresponding SBFD symbols.

[0089] For example, for each pattern with SBFD symbols, the configured SBFD symbols are continuous within the corresponding period of the pattern. The high-level parameters for configuring SBFD symbols mentioned above include, for example, one or more parameters for configuring SBFD symbols in that period, such as: start slot index, start symbol index (in the start slot), end slot index, and end symbol index (in the end slot).

[0090] For example, the start and end slots are the first and last slots containing SBFD symbols, respectively. The start and end symbols are the first and last SBFD symbols in the start slot and the last SBFD symbol in the end slot, respectively. All symbols from the start symbol of the start slot to the end symbol of the end slot are SBFD symbols. The remaining symbols include non-SBFD symbols and / or interval symbols, or, alternatively, non-SBFD symbols. The slot index is the number of the slots included in the period, which increments by 1, for example, starting from 0 or 1. For example, when the start slot index is 0, the start slot is the first slot in the period; when the start slot index is 1, the start slot is the second slot in the period, and so on. Similarly, the symbol index is the number of the symbols within a slot. The aforementioned slots / symbols use the SCS configured in the reference subcarrier spacing field of the Common TDD Uplink / Downlink Configuration (TDD-UL-DL-Config Common) IE.

[0091] For example, each / different pattern is configured with a period independently, for example, by the corresponding ((TDD-UL-DL-Pattern)IE)dl-UL-TransmissionPeriodicity. When only one pattern is configured, the period of the SBFD symbol is the same as the period corresponding to that pattern; when multiple patterns (e.g., two) are configured, the period of the SBFD symbol is the same as the sum of the periods corresponding to all patterns.

[0092] In some embodiments, a downlink symbol is, for example, a symbol indicated as downlink by a first uplink configuration, an uplink symbol is, for example, a symbol indicated as uplink by a first uplink configuration, and a flexible symbol is, for example, a symbol that is neither indicated as downlink nor as uplink by the first uplink configuration, or a symbol indicated as flexible by the configuration.

[0093] For example, the first uplink / downlink configuration is used to provide cell-specific uplink / downlink configurations, such as tdd-UL-DL-ConfigurationCommon, or the common TDD uplink / downlink configuration (TDD-UL-DL-ConfigCommon)IE or (TDD-UL-DL-Pattern)IE, but is not limited thereto. The second uplink / downlink configuration is, for example, tdd-UL-DL-Configuration Dedicated, and the third uplink / downlink configuration is, for example, other configurations; this application is not limited thereto.

[0094] In some embodiments, the UE determines the DL / UL / Flexible symbol corresponding to the BWP based on the DL / UL / Flexible symbol configured according to the aforementioned reference Subcarrier Spacing (and assuming NCP). For example, it determines the DL / UL / Flexible symbol corresponding to the BWP based on the reference Subcarrier Spacing and the SCS and / or CP type (NCP or ECP) ​​of the BWP.

[0095] In some embodiments, the DL / UL / Flexible symbol refers to the DL / UL / Flexible symbol configured based on the reference SubcarrierSpacing or the DL / UL / Flexible symbol corresponding to the BWP.

[0096] In some embodiments, the UE determines the SBFD / non-SBFD symbol corresponding to the BWP based on the SBFD / non-SBFD symbol configured based on the aforementioned reference Subcarrier Spacing (and assuming NCP). For example, it determines the SBFD / non-SBFD symbol corresponding to the BWP based on the reference Subcarrier Spacing and the SCS and / or CP type (NCP or ECP) ​​of the BWP.

[0097] In some embodiments, SBFD / non-SBFD symbols refer to SBFD / non-SBFD symbols configured based on reference SubcarrierSpacing or SBFD / non-SBFD symbols corresponding to BWP.

[0098] In some embodiments, the UE does not expect the CP type of the BWP to be ECP.

[0099] In some embodiments, the UE does not expect the SBFD symbols configured (as described above by the higher-layer parameters) to overlap with the uplink symbols, or if the SBFD symbols configured (as described above by the higher-layer parameters) overlap with the uplink symbols, the UE considers the SBFD symbols overlapping with the uplink symbols to be non-SBFD symbols.

[0100] In some embodiments, the SBFD symbol overlaps with the downlink symbol or the flexible symbol, or in other words, the SBFD symbol is configured within the scope of the downlink symbol and / or the flexible symbol.

[0101] In some embodiments, SBFD symbols include DL SBFD symbols and / or Flexible SBFD symbols, and non-SBFD symbols include Full-DL symbols and / or Full-Flexible symbols and / or Full-UL symbols (or UL symbols). Other representations may also be used for these symbols, and are not limited thereto.

[0102] Figure 3 is an example diagram of time-domain resources according to an embodiment of this application. As shown in Figure 3, a period (e.g., the period corresponding to a pattern) may include multiple different symbols. In this context, the SBFD symbol falls within the scope of downlink symbols and flexible symbols. An SBFD symbol overlapping with a DL symbol, or an SBFD symbol indicated as downlink by the first uplink / downlink configuration, is represented as a DL SBFD symbol. An SBFD symbol overlapping with a flexible symbol, or an SBFD symbol indicated as flexible by the first uplink / downlink configuration (i.e., an SBFD symbol not indicated as downlink (or uplink) by the first uplink / downlink configuration), is represented as a Flexible SBFD symbol. A downlink symbol not overlapping with an SBFD symbol, or a non-SBFD symbol indicated as downlink by the first uplink / downlink configuration, is represented as a Full-DL symbol. A flexible symbol not overlapping with an SBFD symbol, or a non-SBFD symbol indicated as flexible by the first uplink / downlink configuration, is represented as a Full-Flexible symbol. A UL symbol not overlapping with an SBFD symbol, or a (non-SBFD) symbol indicated as uplink by the first uplink / downlink configuration, is represented as a Full-UL symbol (assuming that a UL symbol cannot be used as an SBFD symbol, a Full-UL symbol is equivalent to a UL symbol). Figure 3 exemplarily illustrates the time-domain resources of an embodiment of this application, but is not limited thereto.

[0103] The frequency domain resources involved in the embodiments of this application are illustrated below.

[0104] The first frequency domain resources include the uplink subband (UL subband), and the second frequency domain resources include the downlink subband (DL subband). Other names may also be used, and are not limited to these. For convenience, the following descriptions will use UL subband and DL subband.

[0105] In some embodiments, UL subband and DL subband are configured separately for different cells / carriers.

[0106] In some embodiments, the UE receives information for configuring the UL subband and DL subband. For example, the uplink subband and downlink subband each include an integer number of PRBs, and the information for configuring the UL subband and DL subband includes information indicating the corresponding starting PRB and bandwidth / size (including the number of PRBs).

[0107] In some embodiments, information for configuring the UL subband and DL subband is provided by higher-level signaling.

[0108] For example, higher-layer parameters used to configure the DL subband may optionally exist in SIB1 (the SIB ServingCellConfigCommonSIB IE, the SIB DownlinkConfigCommonSIB IE, the SIB DownlinkFrequencyInfoDL-SIB IE, and the SCS-SpecificCarrier IE), and the inclusion relationship of the above parameters can be expressed as: SIB1 > ServingCellConfigCommonSIB > DownlinkConfigCommonSIB > FrequencyInfoDL-SIB > SCS-SpecificCarrier; and / or,

[0109] The higher-layer parameters used to configure the DL subband may optionally exist in the ServingCellConfigCommon IE (which contains the DownlinkConfigCommon IE, which contains the DownlinkFrequencyInfoDL IE, which contains the SCS-SpecificCarrier IE)). For example, the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > DownlinkConfigCommon > FrequencyInfoDL > SCS-SpecificCarrier, and / or, optionally, in the ServingCellConfig. That is, the higher-layer parameters used to configure the DL subband may optionally exist in one or more of the above parameters.

[0110] For example, the higher-layer parameters used to configure the UL subband may optionally exist in SIB1 (the SIB ServingCellConfigCommonSIB IE, the SIB UplinkConfigCommonSIB IE, the SIB UplinkFrequencyInfoUL-SIB IE, and the SCS-SpecificCarrier IE). For instance, the inclusion relationship of these parameters can be expressed as: SIB1 > ServingCellConfigCommonSIB > UplinkConfigCommonSIB > FrequencyInfoUL-SIB > SCS-SpecificCarrier, and / or...

[0111] The higher-layer parameters used to configure the UL subband may optionally exist in the ServingCellConfigCommon IE (which contains the CommonUplinkConfigCommon IE, which contains the UplinkFrequencyInfoUL IE, which contains the SCS-SpecificCarrier IE)). For example, the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > UplinkConfigCommon > FrequencyInfoUL > SCS-SpecificCarrier, and / or, optionally, in the ServingCellConfig. That is, the higher-layer parameters used to configure the UL subband may optionally exist in one or more of the above parameters.

[0112] In some embodiments, the high-level parameters for configuring the UL subband and the high-level parameters for configuring the DL subband include one or more parameters for providing the RIV (resource indication value) and / or (the SCS corresponding to the UL / DL subband), that is, indicating the starting RB (RB) of the UL subband and the DL subband respectively based on the RIV. start ) and bandwidth (including the number of RBs, L RBs )).

[0113] For example, resource indicator values ​​can be defined as shown in Table 1 below.

[0114] Table 1

[0115] For example, for DL / UL subband: assuming the following in Table 1 In addition, the first PRB (RB) startThe minimum value (0 or 1) corresponding to the PRB can be determined as follows: The first PRB is the PRB determined by the corresponding subcarrierSpacing and offsetToCarrier in ServingCellConfigCommon / ServingCellConfigCommonSIB (configured in the corresponding SCS-Specific Carrier in FrequencyInfoDL (for DL ​​subband) / FrequencyInfoUL (for UL subband) / FrequencyInfoUL-SIB (for UL subband) / FrequencyInfoDL-SIB (for DL ​​subband)).

[0116] In some embodiments, within a cell, the scs-SpecificCarrierList of UL and DL may each include one or more SCS-SpecificCarrier IEs, and each SCS-SpecificCarrier IE corresponds to / includes one SCS configuration (subcarrierSpacing). That is, the scs-SpecificCarrierList of UL and DL may each include one or more SCS configurations.

[0117] For example, each SCS configuration in the UL scs-SpecificCarrierList is configured with a UL subband, or each corresponds to a UL subband, for example, each corresponds to an independent high-level parameter mentioned above for configuring the UL subband. Each SCS configuration in the DL scs-SpecificCarrierList is configured with one or more (e.g., two) DL subbands, or each corresponds to one or more DL subbands, for example, each corresponds to an independent high-level parameter mentioned above for configuring the DL subband. If an SCS configuration is configured with multiple DL subbands, the corresponding high-level parameter for configuring the DL subband includes multiple RIVs mentioned above.

[0118] In some embodiments, the UE does not expect the DL subband and UL subband (in the frequency domain) to overlap (for the same SCS (configuration), or the UE expects the DL subband and UL subband (in the frequency domain) not to overlap (for the same SCS (configuration)).

[0119] In some embodiments, in the second time domain resource, the first frequency domain resource and / or the third frequency domain resource (UL usable PRBs for the active UL BWP) are used for uplink and the second frequency domain resource and / or the fourth frequency domain resource (DL usable PRBs for the active DL BWP) are used for downlink, and the first time domain resource is outside the second time domain resource. For convenience, UL usable PRBs and DL usable PRBs will be used in the following description.

[0120] In some embodiments, for a UL BWP, its UL usable PRBs include / are determined as (in the SBFD symbol / corresponding to the SBFD symbol,) the intersection of (PRBs in the UL subband) and (PRBs in the uplink BWP) with (the SCS configured for the uplink BWP, or, corresponding to the SCS of the UL BWP), or, the PRBs in the intersection are referred to as UL usable PRBs.

[0121] For example, for a UL BWP, the intersection is determined based on the uplink subband corresponding to the SCS of that UL BWP. For instance, if the SCS of a UL BWP is 15kHz, then its corresponding UL available PRB is the intersection of that UL BWP and the corresponding uplink subband with SCS = 15kHz. If the SCS of a UL BWP is 30kHz, then its corresponding UL available PRB is the intersection of that UL BWP and the corresponding uplink subband with SCS = 15kHz.

[0122] In some embodiments, the UE does not expect the UL usable PRBs of the activated UL BWP and the DL usable PRBs of the activated DL BWP to overlap or their frequency domain spacing to be less than or greater than a specific value; or, the UE expects the UL usable PRBs of the activated UL BWP and the DL usable PRBs of the activated DL BWP to not overlap or their frequency domain spacing to be not less than or greater than a specific value.

[0123] In some embodiments, for a UL / DL BWP, if the PRBs in the UL / DL subband (configured for the SCS of the UL / DL BWP, or corresponding to the SCS of the UL / DL BWP) have no intersection with the PRBs in the UL / DL BWP, or if the intersection of the PRBs in the UL / DL subband (configured for the SCS of the UL / DL BWP, or corresponding to the SCS of the UL / DL BWP) with the PRBs in the UL / DL BWP includes 0 PRBs, then the UL / DL BWP does not have UL / DL usable PRBs; otherwise, if there is an intersection or the intersection includes at least 1 PRB or more than 0 PRBs, the UL / DL BWP has UL / DL usable PRBs.

[0124] Figure 4 is an example diagram of uplink usable PRBs according to an embodiment of this application. As shown in Figure 4, the UL BWP and UL subband overlap, and the UL usable PRBs are the intersection between them. The UL subband, for example, represents the uplink subband corresponding to the SCS of the UL BWP, but this application is not limited to this.

[0125] In some embodiments, for a DL BWP, its DL usable PRBs include / are determined as (in SBFD symbols / corresponding to SBFD symbols,) the intersection of (PRBs in the DL subband) and (PRBs in the downlink BWP) with (the SCS configured for the downlink BWP, or, corresponding to the SCS of the DL BWP), or, the PRBs in the intersection are referred to as DL usable PRBs.

[0126] For example, for a DL BWP, the intersection is determined based on the downlink subband corresponding to the SCS of that DL BWP. For instance, if the SCS of a DL BWP is 15kHz, then its corresponding DL can be represented by the PRB as the intersection of the DL BWP with the corresponding downlink subband of SCS = 15kHz. If the SCS of a DL BWP is 30kHz, then its corresponding DL can be represented by the PRB as the intersection of the DL BWP with the corresponding uplink subband of SCS = 15kHz.

[0127] Figure 5 is an example diagram of downlink usable PRBs according to an embodiment of this application. As shown in Figure 5, DL BWP and DL subband overlap, and DL usable PRBs are the intersection of the two. The DL subband, for example, represents the downlink subband corresponding to the SCS of the DL BWP, but this application is not limited thereto.

[0128] In some embodiments, a UL BWP without UL usable PRBs does not have an SBFD symbol, and a DL BWP without DL usable PRBs does not have an SBFD symbol.

[0129] The above provides an illustrative description of time and frequency resources. The following provides a further illustrative description of the embodiments of this application.

[0130] In some embodiments, a cell with (configured) first time-domain resources and / or second time-domain resources can only be a Pcell, or a cell with (configured) first time-domain resources and / or second time-domain resources can be a Pcell / PScell / SpCell / PUCCH-Scell / Scell / primary cell.

[0131] For example, carrier aggregation (CA) and dual connectivity (DC) between a cell / carrier configured with first and / or second time domain resources and another cell / carrier (with or without the first and / or second time domain resources) are not supported. For example, a cell configured with first and / or second time domain resources can only be used as a Pcell, and when a UE is configured with that cell as a Pcell, other serving cells cannot be configured.

[0132] For example, CA configurations of cells with first and / or second time domain resources and other cells / carriers (with / without the first and / or second time domain resources) are not supported, while DC configurations of cells with first and / or second time domain resources and other cells / carriers (with / without the first and / or second time domain resources) are supported. For example, for a cell group (e.g., MCG or SCG) or within a cell group, if a cell (Pcell / PScell / SpCell) is configured with first and / or second time domain resources, other serving cells cannot be configured. For example, if a cell group includes multiple cells, none of those cells can be configured with first and / or second time domain resources. For example, when an SCG is configured, the MCG and SCG cannot each contain cells configured with first and / or second time domain resources.

[0133] For example, a CA (Cellular Array) that supports a cell configured with first and / or second time-domain resources and another cell / carrier (with / without the first and / or second time-domain resources) does not support a DC (Cellular Array) that supports a cell configured with first and / or second time-domain resources and another cell / carrier (with / without the first and / or second time-domain resources). For example, if at least one cell (Pcell / Scell) in an MCG (Multi-Cell Group) is configured with first and / or second time-domain resources, an SCG (Multi-Cell Group) cannot be configured.

[0134] For example, it is not supported to include a cell configured with first and / or second time domain resources in a PUCCH group with another cell / carrier (with or without the first and / or second time domain resources). For instance, for a PUCCH group (e.g., a primary PUCCH group or a secondary PUCCH group), or within a PUCCH group, if a cell (Pcell / PUCCH-Scell) is configured with first and / or second time domain resources, other serving cells cannot be configured. If a PUCCH group includes multiple cells, none of those cells can be configured with first and / or second time domain resources. For example, if at least one cell in an MCG is configured with first and / or second time domain resources, a PUCCH-Scell ​​cannot be configured.

[0135] For example, it supports CA and DC for a cell configured with a first time domain resource and / or a second time domain resource and another cell / carrier (with / without the first time domain resource and / or the second time domain resource). For example, a cell configured with the first time domain resource and / or the second time domain resource can be used as a Pcell / PScell / SpCell / PUCCH-Scell / Scell / primary cell.

[0136] The above schematically illustrates the cell in the embodiment of this application. The power margin will be explained below.

[0137] In some embodiments, when the terminal device is configured with an SCG, the term "serving cell" refers to the serving cell in the MCG when calculating the power margin of a cell in the MCG; the term "primary cell" refers to the PS cell in the SCG when calculating the power margin of a cell in the SCG. That is, for power margin calculation, the corresponding primary cell for an S cell in the MCG is a P cell, and the corresponding primary cell for an S cell in the SCG is a PS cell.

[0138] When a terminal device is configured with a PUCCH-Scell, the term "serving cell" refers to the serving cell within the primary PUCCH group when calculating power margin for cells in that group; similarly, the term "serving cell" refers to the serving cell within the secondary PUCCH group when calculating power margin for cells in that group, and the term "primary cell" refers to the PUCCH-Scell ​​within the secondary PUCCH group. In other words, for power margin calculations, the primary cell for an Scell ​​in the primary PUCCH group is a Pcell, and the primary cell for an Scell ​​in the secondary PUCCH group is a PUCCH-Scell.

[0139] In some embodiments, the terminal device determines / calculates the (Type 1) power headroom (PH) for the (activated) serving cell based on reference PUSCH transmissions. Table 2 shows an example of power headroom calculation.

[0140] Table 2

[0141] In some embodiments, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 Among them, Δ PREAMBLE_Msg3 is provided by msg3-DeltaPreamble or deltaPreamble,orΔ PREAMBLE,Msg3=0dB if msg3-DeltaPreamble and deltaPreamble are not provided, for carrier f of serving cell c.

[0142] In some embodiments, the terminal device determines / calculates (in one or more serving cells) (serving cell) (based on reference PUSCH) power margin according to the preamble received target power.

[0143] For example, for a cell, if the parameter ul-powerControl is not provided, the UE determines / calculates the power margin of the cell (based on the reference PUSCH) according to the preamble received target power.

[0144] For example, the P mentioned above O_PRE Provided by preambleReceivedTargetPower.

[0145] In some embodiments, the terminal device determines the power margin (based on a reference PUSCH) of the primary cell and / or secondary cell (Scell) (among the one or more serving cells) according to the target received power of the preamble sequence, wherein the primary cell includes a Pcell and / or a PScell ​​and / or a PUCCH-Scell, and the secondary cell includes an Scell.

[0146] For example, for a primary cell, the terminal device determines / calculates the power margin (based on the reference PUSCH) of the primary cell according to the target received power of the preamble sequence of the primary cell.

[0147] For example, for a secondary cell (Scell), the terminal device determines / calculates the power margin (based on the reference PUSCH) of the secondary cell (Scell) based on the preamble target received power of the secondary cell (when the secondary cell is configured with a preamble target received power) or the preamble target received power of the primary cell corresponding to the secondary cell (when the secondary cell is not configured with a preamble target received power).

[0148] In some embodiments, a cell can be configured with one or two sets of preamble target receive powers. For example, a cell without a first time domain resource and / or a second time domain resource can be configured with one set of preamble target receive powers. For example, a cell with a first time domain resource and / or a second time domain resource can be configured with one set of one set of preamble target receive powers. For example, when two sets of preamble target receive powers are configured, one set of preamble target receive powers (e.g., referred to as the first preamble target receive power) is applied to / for the first time domain resource or the first RO, and the other set of preamble target receive powers (e.g., referred to as the second preamble target receive power) is applied to / for the second time domain resource or the second RO. For example, when transmitting a preamble using the first time domain resource or the first RO (e.g., a legacy RO), the transmission power is calculated based on the first preamble target receive power; when transmitting a preamble using the second time domain resource or the second RO (e.g., an additional RO), the transmission power is calculated based on the second preamble target receive power. For example, when a set / one preamble target receive power is configured (e.g., equal to the aforementioned first preamble target receive power or second preamble target receive power, and / or configured by higher-level parameters configuring the aforementioned first preamble target receive power or second preamble target receive power), the preamble target receive power can be applied to / for a first time domain resource or a first RO and a second time domain resource or a second RO. For example, when a preamble is transmitted using a first time domain resource or a first RO (e.g., legacy RO) or a second time domain resource or a second RO (e.g., additional RO), the transmission power is calculated based on the preamble target receive power.

[0149] In some embodiments, the first RO includes a RO in a first time-domain resource that is not indicated as downlink by (first uplink / downlink configuration), and the second RO includes a RO overlapping with a second time-domain resource indicated as downlink by (first uplink / downlink configuration), and / or a RO overlapping with a second time-domain resource. For example, a RO overlapping with a second time-domain resource indicated as downlink by (first uplink / downlink configuration) includes at least one downlink symbol configured by (first uplink / downlink configuration), and / or a RO overlapping with a second time-domain resource configured as downlink includes: a RO in the second time-domain resource configured as downlink, and / or a RO across the second time-domain resource configured as downlink and a second time-domain resource configured as flexible, and / or a RO overlapping with a second time-domain resource includes: a RO in the second time-domain resource, and / or a RO across the second time-domain resource and the first time-domain resource, and / or a RO that starts in the second time-domain resource and ends in the first time-domain resource.

[0150] In some embodiments, the first RO and the second RO are in the initial UL BWP. The first preamble target received power and the second preamble target received power are applied to the (first / second) RO in the initial UL BWP, or configured for the RO in the initial UL BWP.

[0151] In some embodiments, the first preamble sequence target received power is configured by a first (higher-layer) parameter (in the BWP configuration of the initial UL BWP), and the second preamble sequence target received power is configured by a second (higher-layer) parameter (in the BWP configuration of the initial UL BWP). For example, the first (higher-layer) parameter is preambleReceivedTargetPower in the rach-ConfigCommon of the (initial UL BWP) common BWP configuration (BWP-UplinkCommon) (in system information (e.g., SIB1) or ServingCellConfigCommonSIB or ServingCellConfigCommon). For example, the second (higher-layer) parameter is preambleReceivedTargetPower-SBFD in the rach-ConfigCommon of the (initial UL BWP) common BWP configuration (BWP-UplinkCommon) (in system information (e.g., SIB1) or ServingCellConfigCommonSIB or ServingCellConfigCommon) (this parameter is used to configure the target receive power for the preamble sequence for the second RO), or preambleReceivedTargetPower in the rach-ConfigCommon-SBFD of the common BWP configuration (BWP-UplinkCommon) (this parameter is used to configure the random access resources including the second RO).

[0152] In some embodiments, the terminal device determines a power margin based on a first preamble target receive power and / or a second preamble target receive power. For example, the terminal device determines (in one or more serving cells) (based on a reference PUSCH) power margin based on the preamble target receive power applied to / for a first time domain resource / first RO (configuration) and / or the preamble target receive power applied to / for a second time domain resource / second RO (configuration).

[0153] For example, (for a serving cell that has first time domain resources and / or second time domain resources, is not configured with a unified TCI state, and is configured with (two sets / two) preamble sequence target receive power,) the terminal device determines the power margin (based on reference PUSCH) of the serving cell (primary cell or secondary cell) according to the first preamble sequence target receive power and / or the second preamble sequence target receive power.

[0154] For example, (for a secondary cell that has not been configured with a preamble target receive power, and whose corresponding primary cell has a first time domain resource and / or a second time domain resource, and whose corresponding primary cell is configured with (two sets / two) preamble target receive powers,) the terminal device determines the power margin (based on the reference PUSCH) of the secondary cell according to the first preamble target receive power and / or the second preamble target receive power of the primary cell (corresponding to the secondary cell).

[0155] In some embodiments, when a cell (primary cell or secondary cell) has a first time-domain resource and / or a second time-domain resource, the power margin of the cell (based on the reference PUSCH) is determined using the first preamble target received power or the second preamble target received power of the cell or the primary cell corresponding to the cell, according to the time-domain resource type in the reference time slot of the cell.

[0156] For example, when a cell's reference time slot includes only a first time-domain resource, the cell's power margin (based on the reference PUSCH) is determined using the first preamble sequence target received power (of the cell or the corresponding primary cell). For example, when a cell's reference time slot includes only a second time-domain resource, the cell's power margin (based on the reference PUSCH) is determined using the second preamble sequence target received power (of the cell or the corresponding primary cell). For example, when the reference symbol (e.g., the first symbol) in a cell's reference time slot is a first time-domain resource / first symbol, the cell's power margin (based on the reference PUSCH) is determined using the first preamble sequence target received power (of the cell or the corresponding primary cell). For example, when the reference symbol (e.g., the first symbol) in a cell's reference time slot is a second time-domain resource / second symbol, the cell's power margin (based on the reference PUSCH) is determined using the second preamble sequence target received power (of the cell or the corresponding primary cell).

[0157] For example, a cell's power margin is transmitted in the PUSCH of one cell or another. For the cell containing the PUSCH used to transmit the MAC CE including that power margin, the reference timeslot is the timeslot in which the UE transmits / provides the power margin (i.e., the timeslot in which the PUSCH used to transmit the MAC CE including that power margin is located). For other cells, the reference timeslot is the timeslot in that other cell that overlaps with the timeslot in which the UE transmits / provides the power margin (in the cell containing the PUSCH used to transmit the MAC CE including that power margin) or the first overlapping timeslot. The reference timeslot is, for example, referred to as slot n (e.g., for the cell containing the PUSCH used to transmit the MAC CE including that power margin) or the timeslot overlapping with slot n or the first overlapping timeslot (e.g., for the other cells mentioned above), but is not limited to this.

[0158] In some embodiments, a preambleReceivedTargetPower is used / applied, for example, P O_PRE Provided by preambleReceivedTargetPower.

[0159] In some embodiments, if the (activated) serving cell (primary cell or Scell) is configured with preambleReceivedTargetPower, the preambleReceivedTargetPower of that cell is used / applied.

[0160] For example, if the (activated) serving cell is configured with a set / each preambleReceivedTargetPower, use / apply that preambleReceivedTargetPower.

[0161] For example, if the (activated) serving cell is configured with two sets / two preambleReceivedTargetPowers, such as if the serving cell is configured with a preambleReceivedTargetPower for the non-SBFD symbol / first RO and a preambleReceivedTargetPower for the SBFD symbol / second RO, or if the serving cell is configured with a preambleReceivedTargetPower for the SBFD symbol / second RO or is configured with a second RO, use / apply the values ​​associated with the preambleReceivedTargetPower for the non-SBFD symbol / first RO and / or the preambleReceivedTargetPower for the SBFD symbol / second RO of the serving cell. For example, using / applying the preambleReceivedTargetPower of the serving cell for the non-SBFD symbol / first RO, or using / applying the preambleReceivedTargetPower of the serving cell for the SBFD symbol / second RO, or using / applying a value determined based on the preambleReceivedTargetPower of the serving cell for the non-SBFD symbol / first RO and the preambleReceivedTargetPower for the SBFD symbol / second RO (e.g., the average of the two, or the larger / maximum value of the two, or the smaller / minimum value of the two, etc.).

[0162] In some embodiments, the terminal device sends a Power Headroom Report (PHR) (at least one of the one or more serving cells) to the network device, the PHR being carried by the MAC CE.

[0163] In some embodiments, a serving cell having (configured) first time-domain resources and / or second time-domain resources should be configured with a unified TCI state (type).

[0164] For example, a UE expects a cell configured with a first time domain resource and / or a second time domain resource to be configured with a unified TCI state (type) unifiedTCI-StateType-r17 and / or (for the unified TCI state) uplink-PowerControlToAddModList-r17 / ul-powerControl-17.

[0165] For example, for a cell configured with a first time domain resource and / or a second time domain resource: in the ServingCellConfig of that cell, a unified TCI state (type) and / or (for the unified TCI state) uplink-PowerControlToAddModList-r17 / ul-powerControl-17 / ul-powerControl-17 must be configured, or the unified TCI state (type) and / or (for the unified TCI state) uplink-PowerControlToAddModList-r17 / ul-powerControl-17 is mandatory, and / or ul-powerControl-17 must be configured in at least one of the UL BWP configuration and the TCI state configuration and the UL TCI state.

[0166] In some embodiments, if the (activated) serving cell is an S cell and no preambleReceivedTargetPower is configured for that cell, the preambleReceivedTargetPower configured for the primary cell, i.e., P, is used / applied. O_PRE Provided by preambleReceivedTargetPower configured for the primary cell.

[0167] For example, if the primary cell is configured with only one uplink carrier (and is configured with a set / one preambleReceivedTargetPower), use / apply the preamble ReceivedTargetPower configured for the primary cell.

[0168] For example, if the primary cell is configured with two sets / two preambleReceivedTargetPowers (and is configured with only one uplink carrier), use / apply values ​​related to the primary cell's preambleReceivedTargetPower for the non-SBFD symbol / first RO and / or the preambleReceivedTargetPower for the SBFD symbol / second RO. For example, use / apply the primary cell's preambleReceivedTargetPower for the non-SBFD symbol / first RO, or use / apply the primary cell's preambleReceivedTargetPower for the SBFD symbol / second RO, or use / apply values ​​determined based on the primary cell's preambleReceivedTargetPower for the non-SBFD symbol / first RO and the preambleReceivedTargetPower for the SBFD symbol / second RO (e.g., the average of the two, or the larger / maximum value of the two, or the smaller / minimum value of the two, etc.).

[0169] For example, if the primary cell is configured with two uplink carriers (and the non-SUL carrier does not have two sets / two preambleReceivedTargetPowers configured), use / apply the preambleReceivedTargetPower configured for the non-SUL carrier of the primary cell.

[0170] For example, if the primary cell's non-SUL carrier is configured with two sets / two preambleReceivedTarget Powers (and the primary cell is configured with two uplink carriers), use / apply values ​​related to the preambleReceivedTargetPower of the primary cell's non-SUL carrier for the non-SBFD symbol / first RO and / or the preambleReceivedTargetPower for the SBFD symbol / second RO. For example, use / apply the preambleReceivedTargetPower of the primary cell's non-SUL carrier for the non-SBFD symbol / first RO, or use / apply the preambleReceivedTargetPower of the primary cell's non-SUL carrier for the SBFD symbol / second RO, or use / apply values ​​determined based on the preambleReceivedTargetPower of the primary cell's non-SUL carrier for the non-SBFD symbol / first RO and the preambleReceivedTargetPower for the SBFD symbol / second RO (e.g., the average of the two, or the larger / maximum value of the two, or the smaller / minimum value of the two, etc.).

[0171] In some embodiments, two sets / two preambleReceivedTargetPowers are configured, for example: a preambleReceivedTargetPower (second preamble sequence target power) is configured for the SBFD symbol / second RO and a preambleReceivedTargetPower (first preamble sequence target power) is configured for the non-SBFD symbol / first RO, and / or a preambleReceivedTargetPower is configured for the SBFD symbol / second RO and / or the second RO is configured.

[0172] In some embodiments, the UE does not expect a cell to be configured with a first time domain resource and a second time domain resource, as well as two uplink carriers simultaneously; or, the UE does not expect a cell to be configured with a first time domain resource and a second time domain resource, as well as a SUL carrier simultaneously.

[0173] For example, if a cell is configured with both first and second time domain resources simultaneously, then no two uplink carriers are configured; or, if a cell is configured with both uplink carriers simultaneously, then no first and second time domain resources are configured. As another example, if a cell is configured with both first and second time domain resources simultaneously, then no SUL carrier is configured; or, if a cell is configured with an SUL carrier, then no first and second time domain resources are configured simultaneously.

[0174] In some embodiments, the UE receives information indicating whether to use / apply a first preamble target power or a second preamble target power (of the serving cell and / or the primary cell's (non-SUL carrier)) or a larger / maximum / smaller / minimum value of the first preamble target power or the second preamble target power (of the serving cell and / or the primary cell's (non-SUL carrier)).

[0175] In some embodiments, the UE does not expect the primary cell (its non-SUL carrier) to be configured with two sets / two preambleReceivedTargetPowers. For example, if at least one Scell ​​is not configured with a preambleReceivedTargetPower, the primary cell (its non-SUL carrier) corresponding to the Scell ​​that is not configured with a preambleReceivedTargetPower will not be configured with two sets / two preambleReceivedTargetPowers, for example, it will not be configured with a preambleReceivedTargetPower for the SBFD symbol.

[0176] In some embodiments, if the primary cell corresponding to the Scell ​​is configured with two sets / two preambleReceivedTargetPower, the Scell ​​(without a unified TCI state) must be configured with preambleReceivedTargetPower. For example, the UE does not expect the Scell ​​(without a unified TCI state) not to be configured with preambleReceivedTargetPower.

[0177] The above explains the power margin; the following explains directional collision handling.

[0178] In some embodiments, the ServingCellConfig may include a directional CollisionHandling parameter, which instructs the corresponding serving cell to use / adopt a directional collision handling (mechanism) between a reference cell and other cells for half-duplex operation (in a TDD CA with the same SCS). This half-duplex operation applies only within the same frequency range (FR) and the same cell group (e.g., MCG or SCG).

[0179] In some embodiments, the terminal device sends information indicating its capability to support directional collision handling (mechanism) between a reference cell and other cells for half-duplex operation (in a TDD CA with the same SCS).

[0180] For example, the UE sends (capability) information (half-DuplexTDD-CA-SameSCS-r16) to indicate that the UE supports directional collision handling (mechanism) between the reference cell and other cells for half-duplex operation (in a TDD CA with the same SCS).

[0181] For example, the UE may transmit / include this information for band combinations that include only intra-band TDD CA, or (if simultaneousRxTxInterBandCA is not present) for mixed band combinations that include both intra-band TDD CA and inter-band TDD CA. For instance, if the UE does not support / does not transmit simultaneousRxTxInterBandCA, the information is for mixed band combinations that include both intra-band TDD CA and inter-band TDD CA; if the UE supports / transmits simultaneousRxTxInterBandCA, the information is for band combinations that include only intra-band TDD CA.

[0182] In some embodiments, (if the UE is not capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group), when the serving cell with the first time domain resource and / or the second time domain resource is the (active) cell with the smallest cell index in its cell group, none of the serving cells in the cell group containing the serving cell with the first time domain resource and / or the second time domain resource are configured with directional collision handling parameters.

[0183] For example, it is not allowed (not expected / prohibited) for any serving cell in the cell group to which the serving cell with the first time domain resource and / or the second time domain resource is located to be configured with directional collision handling parameters.

[0184] In some embodiments, (if the UE is capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group), when the serving cell with the first time domain resource and / or the second time domain resource is the (active) cell with the smallest cell index in its frequency band (within its cell group), none of the serving cells in the frequency band of the serving cell with the first time domain resource and / or the second time domain resource are configured with directional collision handling parameters.

[0185] In some embodiments, the terminal device ignores the direction collision processing parameters of the serving cell.

[0186] In some embodiments, the SBFD-aware UE does not support directional collision handling (mechanism) between the reference cell and other cells (in a TDD CA with the same SCS) for half-duplex operation, and / or, the SBFD-aware UE does not send (capability) information (half-DuplexTDD-CA-SameSCS-r16) indicating that the UE supports directional collision handling (mechanism) between the reference cell and other cells (in a TDD CA with the same SCS) for half-duplex operation.

[0187] In some embodiments, the UE transmits information (simultaneousRxTxInterBandCA) indicating that the UE supports (in TDD-TDD and TDD-FDD inter-band NR CA) (in different bands) simultaneous transmission and reception.

[0188] In some embodiments, the serving cell having the first time domain resource and / or the second time domain resource is not configured with directional collision handling parameters.

[0189] For example, it is not allowed (not expected / prohibited) for the same serving cell to be configured (simultaneously) with the first time-domain resource and / or the second time-domain resource and the directional collision handling parameter; or

[0190] For example, for a serving cell configured with the first time-domain resource and / or the second time-domain resource, configuring the directional collision handling parameter (directionalCollisionHandling) is not allowed (not desired / prohibited); or

[0191] For example, for a serving cell configured with directional collision handling parameters, it is not allowed (not desired / prohibited) for the serving cell to be configured with the first time domain resource and / or the second time domain resource.

[0192] In some embodiments, (SBFD-aware UE) does not support the same cell being configured with both a first time-domain resource and / or a second time-domain resource and having directional CollisionHandling configured. For example, if a cell is configured with both a first time-domain resource and a second time-domain resource, then directional CollisionHandling is not configured, and vice versa.

[0193] In some embodiments, the (SBFD-aware UE) does not support the (intra-band and inter-band) CA / DC of a cell configured with first and / or second time domain resources and a cell configured with directional CollisionHandling. For example, it is not supported to (for the SBFD-aware UE) simultaneously configure a serving cell configured with first and / or second time domain resources and a serving cell configured with directional CollisionHandling. For example, if the UE (SBFD-aware UE) is configured with multiple serving cells (in the same cell group, MCG, or within an MCG) (in the same and / or different bands), and at least one of these serving cells is configured with first and / or second time domain resources, the UE expects that none of these multiple serving cells (any of these cells) are configured with directional CollisionHandling, or the UE (SBFD-aware UE) does not expect any of these multiple serving cells to be configured with directional CollisionHandling. For example, if a UE is configured with multiple serving cells (in the same cell group, MCG, or within an MCG), and at least one of the serving cells is configured with directional CollisionHandling, the UE expects that none of the multiple serving cells (any of the cells) will be configured with the first time domain resource and / or the second time domain resource, or the UE does not expect any of the multiple serving cells to be configured with the first time domain resource and / or the second time domain resource.

[0194] Thus, for example, it is possible to avoid the simultaneous existence of SBFD cells and directional Collision Handling cells.

[0195] In some embodiments, the (SBFD-aware UE) does not support intra-band CA between a cell configured with first and / or second time domain resources and a cell configured with directional CollisionHandling. For example, it does not support (for the SBFD-aware UE) simultaneously configuring serving cells configured with first and / or second time domain resources and serving cells configured with directional CollisionHandling in the same band. For example, if the UE (SBFD-aware UE) is configured with multiple serving cells (in the same cell group, MCG, or within an MCG) in (the same and / or different bands), and at least one of these serving cells is configured with first and / or second time domain resources, the UE expects that none of the serving cells in the same band with the serving cells configured with first and / or second time domain resources are configured with directional CollisionHandling, or the UE does not expect that directional CollisionHandling be configured with serving cells in the same band with the serving cells configured with first and / or second time domain resources. For example, if a UE is configured with multiple serving cells (in the same cell group, MCG, or within an MCG) (in the same or different bands), and at least one of these serving cells is configured with directional CollisionHandling, the UE expects that none of the serving cells configured with directional CollisionHandling in the same band be configured with the first time domain resource and / or the second time domain resource, or the UE does not expect any of the multiple serving cells to be configured with the first time domain resource and / or the second time domain resource.

[0196] Thus, for example, it is possible to avoid the coexistence of SBFD cells and directional Collision Handling cells in the same band.

[0197] In some embodiments, the (SBFD-aware UE) supports the (intra-band and inter-band) CA of a cell configured with first and / or second time-domain resources and a cell configured with directional CollisionHandling. For example, it supports configuring (for the SBFD-aware UE) simultaneously a serving cell configured with first and / or second time-domain resources and a serving cell configured with directional CollisionHandling. For example, it supports the following configuration: the UE is configured with multiple serving cells (within the same cell group, MCG, or MCG) (in the same and / or different bands), and at least one of these serving cells is configured with first and / or second time-domain resources, and at least one of these serving cells is configured with directional CollisionHandling. The serving cell configured with first and / or second time-domain resources and the cell configured with directional CollisionHandling are in the same or different bands.

[0198] Therefore, for example, it can support the simultaneous existence of SBFD cells and directional Collision Handling cells.

[0199] In some embodiments, the (SBFD-aware UE) supports inter-band CA between a cell configured with first and / or second time domain resources and a cell configured with directional CollisionHandling. For example, it supports (for the SBFD-aware UE) simultaneously configuring serving cells configured with first and / or second time domain resources and serving cells configured with directional CollisionHandling in different bands. For example, the following configuration is supported: the UE (SBFD-aware UE) is configured with multiple serving cells (within the same cell group, MCG, or MCG) (in the same or different bands), wherein at least one serving cell is configured with first and / or second time domain resources, and at least one serving cell in at least one band (different from the band in which the serving cell configured with first and / or second time domain resources is located) is configured with directional CollisionHandling. The serving cell configured with first and / or second time domain resources and the cell configured with directional CollisionHandling are in different bands or not in the same band.

[0200] Thus, for example, it is possible to support the simultaneous existence of SBFD cells and directional Collision Handling cells in the same band.

[0201] In some embodiments, if the UE (SBFD-aware UE) supports (being capable of) (indicated by simultaneousRxTxInterBandCA) (in different bands), the (SBFD-aware UE) does not support CA of the intra-band of the cell configured with the first time domain resources and / or the second time domain resources and the cell configured with directionalCollisionHandling, but supports CA of the inter-band of the cell configured with the first time domain resources and / or the second time domain resources and the cell configured with directionalCollisionHandling.

[0202] If the UE (SBFD-aware UE) does not support (be not capable of) (as indicated by the simultaneousRxTxInterBand CA) (in different bands), the SBFD-aware UE does not support (intra-band and inter-band) CAs of cells configured with first and / or second time domain resources and cells configured with directional Collision Handling.

[0203] In some embodiments, at least one serving cell in the cell group containing the serving cell having (configured) first time-domain resources and / or second time-domain resources (different from the serving cell having the first time-domain resources and / or second time-domain resources) is configured with directional collision handling parameters, and the terminal device determines a reference cell (for the symbol).

[0204] For example, when a (SBFD-aware) UE is configured with multiple serving cells (in a cell group) and (indicates) support for direction collision handling (mechanism) between a reference cell and other cells for half-duplex operation (in a TDD CA with the same SCS) (or, indicates support for half-DuplexTDD-CA-SameSCS-r16 capability), (and is not configured with a monitor PDCCH for detection of DCI format 2_0 on any of the multiple serving cells), the UE determines the reference cell (for a symbol).

[0205] Table 3 shows an example of a reference cell.

[0206] Table 3

[0207] Table 4 shows another example of a reference cell. Table 4 applies, for example, to cases where the UE is not configured with a cell having first time domain resources and / or second time domain resources and / or the UE is configured with a cell having first time domain resources and / or second time domain resources, but is not limited thereto.

[0208] Table 4

[0209] Table 5 shows another example of a reference cell. Table 5 applies, for example, to cases where the UE is configured with a cell having a first time-domain resource and / or a second time-domain resource, but is not limited thereto.

[0210] Table 5

[0211] In some embodiments, the (UE expects) reference cell to not have a first time domain resource and / or a second time domain resource.

[0212] In some embodiments, (if the UE is not capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group), the reference cell (of all serving cells configured with directionalCollisionHandling) of the cell group is the (active) cell with the smallest cell index among the multiple serving cells in the cell group, or, is the (active) cell with the smallest cell index among one or more serving cells in the cell group other than the serving cell with the first time domain resource and / or the second time domain resource, or,

[0213] (if the UE is capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group,) (for each frequency band of the cell group) (all serving cells configured with directionalCollisionHandling) the reference cell is the (active) cell with the smallest cell index among the cells in one / each frequency band (where the serving cell configured with directionalCollisionHandling is located), or, the (active) cell with the smallest cell index among the cells in one / each frequency band (where the serving cell configured with directionalCollisionHandling is located), excluding the serving cell with the first time domain resource and / or the second time domain resource.

[0214] In some embodiments, a cell configured with SBFD operation shall not be determined as a reference cell, or a reference cell shall not be configured with SBFD operation. For example, the UE does not expect a cell configured with SBFD operation to be a reference cell. As another example, the UE does not expect a reference cell to be configured with SBFD operation.

[0215] In some embodiments, the active cell with the smallest cell index among the multiple serving cells shall not be configured with SBFD operation. For example, the UE does not expect the active cell with the smallest cell index among the multiple serving cells to be configured with SBFD operation.

[0216] In some embodiments, the active cell with the smallest cell index among the cells of each band shall not be configured with SBFD operation. For example, the UE does not expect the active cell with the smallest cell index among the cells of each band to be configured with SBFD operation.

[0217] In some embodiments, if the UE cannot simultaneously transmit and receive in multiple serving cells as indicated by `simultaneousRxTxInterBandCA`, the active cell with the smallest cell index among the multiple serving cells should not be configured with SBFD operation. For example, the UE does not expect the active cell with the smallest cell index among the multiple serving cells to be configured with SBFD operation.

[0218] In some embodiments, if the UE is capable of simultaneous transmission and reception by simultaneousRxTxInterBandCA for the configured multiple serving cells, an active cell with the smallest cell index among the cells of each band shall not be configured with SBFD operation. For example, the UE does not expect an active cell with the smallest cell index among the cells of each band to be configured with SBFD operation.

[0219] In some embodiments, the reference cell has the first time-domain resources and / or the second time-domain resources.

[0220] For example, it supports the simultaneous configuration of a first time-domain resource and / or a second time-domain resource for the same cell, along with the configuration of directionalCollisionHandling. For instance, if a cell is configured with both first and second time-domain resources simultaneously, directionalCollisionHandling can also be configured, and vice versa.

[0221] In some embodiments, "configured with first time domain resources and / or second time domain resources" and "configured with SBFD operation" can be interchanged, and "not configured with first time domain resources and / or second time domain resources" and "not configured with SBFD operation" can be interchanged.

[0222] In some embodiments, a first time domain resource indicated as downlink by a first uplink / downlink configuration and / or a second uplink / downlink configuration is configured as downlink, and / or a first time domain resource indicated as uplink by the first uplink / downlink configuration and / or the second uplink / downlink configuration is configured as uplink, and / or the terminal device is configured to transmit uplink signals using a second time domain resource and / or a flexible first time domain resource is configured as uplink, and / or the terminal device is configured to receive downlink signals using a second time domain resource and / or a flexible first time domain resource is configured as downlink.

[0223] Table 6 shows an example when the reference cell is not configured for SBFD operation.

[0224] Table 6

[0225] Table 7 shows an example of when the reference cell is configured for SBFD operation.

[0226] Table 7

[0227] Table 8 shows an example of a UE in an embodiment of this application.

[0228] Table 8

[0229] In some embodiments, the reference cell has the first time-domain resource and / or the second time-domain resource, and the first time-domain resource (overlapping time-domain resource) indicated as downlink by the first uplink configuration and / or the second uplink configuration is determined to be an invalid time-domain resource for PUSCH duplication (Type B) of a cell (with or without the first time-domain resource and / or the second time-domain resource) configured with directional collision handling parameters (directionalCollisionHandling). For example, the UE determines the actual duplication (of the PUSCH) based on the determined invalid time-domain resource and then transmits the PUSCH.

[0230] Table 9 shows an example of a UE in an embodiment of this application.

[0231] Table 9

[0232] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.

[0233] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0234] As can be seen from the above embodiments, in the presence of different time-domain resources, such as beams, channel states, frequency domain resources for uplink, and power control parameters, the terminal device receives the serving cell configuration and transmits uplink signals in a cell with first and / or second time-domain resources, thus enabling the transmission and reception of uplink signals in the presence of the aforementioned different time-domain resources.

[0235] Second aspect of the embodiments

[0236] This application provides a signal receiving method, which will be described from the perspective of a network device. The content that is the same as that in the first aspect of the embodiment will not be repeated.

[0237] Figure 6 is a schematic diagram of a signal receiving method according to an embodiment of this application. As shown in Figure 6, the method includes:

[0238] 601, The network device sends a serving cell configuration for one or more (serving) cells, at least one of the one or more (serving) cells having a first time domain resource (non-SBFD) and / or a second time domain resource (SBFD), wherein, in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the first time domain resource is outside the second time domain resource;

[0239] 602, the network device receives uplink signals in a (serving) cell having the first time domain resources and / or the second time domain resources.

[0240] It is worth noting that Figure 6 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 6 above.

[0241] In some embodiments, a cell having the first time-domain resource and / or the second time-domain resource can only be a Pcell, or a cell having the first time-domain resource and / or the second time-domain resource can be a Pcell / PScell / SpCell / PUCCH-Scell / Scell / primary cell.

[0242] In some embodiments, carrier aggregation (CA) and dual connectivity (DC) between a cell / carrier having the first time domain resource and / or the second time domain resource and another cell / carrier (having / not having the first time domain resource and / or the second time domain resource) are not supported; or

[0243] Carrier aggregation (CA) between a cell / carrier having the first time domain resource and / or the second time domain resource and another cell / carrier (having / not having the first time domain resource and / or the second time domain resource) is not supported; dual connectivity (DC) between a cell / carrier having the first time domain resource and / or the second time domain resource and another cell / carrier (having / not having the first time domain resource and / or the second time domain resource) is supported; or

[0244] Supports carrier aggregation (CA) between a cell / carrier with the first time domain resource and / or the second time domain resource and another cell / carrier (with / without the first time domain resource and / or the second time domain resource), but does not support dual connectivity (DC) between a cell / carrier with the first time domain resource and / or the second time domain resource and another cell / carrier (with / without the first time domain resource and / or the second time domain resource); or

[0245] PUCCH groups that include a cell / carrier having the first time domain resource and / or the second time domain resource and another cell / carrier (having / not having the first time domain resource and / or the second time domain resource) are not supported.

[0246] In some embodiments, the terminal device is configured with one or more (serving) cells, and / or, the one or more (serving) cells belong to the same cell group or the multiple (serving) cells include (serving) cells belonging to different cell groups, and / or, the one or more (serving) cells include Pcell and / or Scell ​​and / or PScell ​​and / or PUCCH-Scell, and / or, the serving cell configuration is dedicated radio resource control (RRC) signaling.

[0247] In some embodiments, the power margin (based on a reference PUSCH) of (one or more serving cells) is determined based on the preamble received target power.

[0248] In some embodiments, the power margin (based on a reference PUSCH) of the primary cell and / or secondary cell (Scell) (among the one or more serving cells) is determined according to the preamble received target power, wherein the primary cell includes a Pcell and / or a PScell ​​and / or a PUCCH-Scell.

[0249] In some embodiments, the power margin (based on reference PUSCH) of (one or more serving cells) is determined based on the first preamble received target power and / or the second preamble received target power.

[0250] In some embodiments, (for a serving cell that has first time domain resources and / or second time domain resources, is not configured with a unified TCI state, and is configured with (two sets / two) preamble target received power,) the power margin (based on reference PUSCH) of the (serving) cell (primary or secondary cell) is determined according to the first preamble target received power and / or the second preamble target received power of the (serving) cell (primary or secondary cell) having first time domain resources and / or second time domain resources.

[0251] In some embodiments, (for a secondary cell that has not been configured with preamble target received power, and the corresponding primary cell has a first time domain resource and / or a second time domain resource, and the corresponding primary cell is configured with (two sets / two) preamble target received powers,) the power margin (based on reference PUSCH) of the secondary cell is determined according to the first preamble target received power (preambleReceivedTargetPower) and / or the second preamble target received power (preambleReceivedTargetPower) of the primary cell (corresponding to the secondary cell).

[0252] In some embodiments, when the secondary cell has a first time-domain resource and / or a second time-domain resource, the power margin of the secondary cell (based on the reference PUSCH) is determined according to the time-domain resource type in the reference time slot using the first preamble received target power (preambleReceivedTargetPower) or the second preamble received target power (preambleReceivedTargetPower) of the primary cell (corresponding to the secondary cell).

[0253] In some embodiments, the network device receives a Power Headroom Report (PHR) (at least one of the one or more serving cells), which is carried by a MAC CE.

[0254] In some embodiments, the serving cell having the first time domain resources and / or the second time domain resources (should) be configured with a unified TCI state (type).

[0255] In some embodiments, the network device receives (capability) information indicating that the terminal device supports directional collision handling (mechanism) between a reference cell and other cells (in a TDD CA with the same SCS) for half-duplex operation, or the network device does not support directional collision handling (mechanism) between a reference cell and other cells (in a TDD CA with the same SCS) for half-duplex operation.

[0256] In some embodiments, (if the UE is not capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group), when the serving cell with the first time domain resource and / or the second time domain resource is the (active) cell with the smallest cell index in its cell group, none of the serving cells in the cell group containing the serving cell with the first time domain resource and / or the second time domain resource are configured with directional collision handling parameters (e.g., it is not allowed (not desired / prohibited) for any serving cell in the cell group containing the serving cell with the first time domain resource and / or the second time domain resource to be configured with directional collision handling parameters ()), and / or,

[0257] (If the UE is capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group,) when the serving cell with the first time domain resource and / or the second time domain resource is the (active) cell with the smallest cell index in its frequency band (within its cell group),) no serving cell in the frequency band of the serving cell with the first time domain resource and / or the second time domain resource is configured with directional collision handling parameters.

[0258] In some embodiments, the network device ignores the orientation collision handling parameters of the serving cell.

[0259] In some embodiments, the serving cell having the first time domain resource and / or the second time domain resource is not configured with directional collision handling parameters.

[0260] (For example, it is not allowed (not expected / prohibited) for the same serving cell to be configured (simultaneously) with the first time domain resource and / or the second time domain resource and the directional collision handling parameter; or

[0261] For a serving cell configured with the first time-domain resource and / or the second time-domain resource, configuring the directional collision handling parameter (directionalCollisionHandling) is not allowed (not desired / prohibited); or

[0262] For a serving cell configured with directional collision handling parameters, it is not allowed (not desired / prohibited) for the serving cell to be configured with the first time domain resource and / or the second time domain resource.

[0263] In some embodiments, at least one serving cell in the cell group to which the serving cell with the first time domain resource and / or the second time domain resource is located (different from the serving cell with the first time domain resource and / or the second time domain resource) is configured with directional collision handling parameters.

[0264] In some embodiments, the network device determines a reference cell (for symbols).

[0265] In some embodiments, (UE expects) the reference cell to not have the first time domain resource and / or the second time domain resource.

[0266] In some embodiments, (if the UE is not capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group,) the reference cell of (all serving cells of the cell group configured with directionalCollisionHandling) is the (active) cell with the smallest cell index among the multiple serving cells in the cell group, or, is the (active) cell with the smallest cell index among one or more serving cells in the cell group other than the serving cell with the first time domain resource and / or the second time domain resource, or...

[0267] (if the UE is capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group,) (for each frequency band of the cell group,) the reference cell is the (active) cell with the smallest cell index among the cells in one / each frequency band where the serving cell with directionalCollisionHandling is located, or, the (active) cell with the smallest cell index among the cells in one / each frequency band where the serving cell with directionalCollisionHandling is located, excluding the serving cell with the first time domain resource and / or the second time domain resource.

[0268] In some embodiments, the reference cell has the first time-domain resources and / or the second time-domain resources.

[0269] A first time-domain resource indicated as downlink by (first uplink / downlink configuration and / or second uplink / downlink configuration) is configured as downlink, and / or a first time-domain resource indicated as uplink by (first uplink / downlink configuration and / or second uplink / downlink configuration) is configured as uplink, and / or the terminal device is configured to transmit uplink signals using a second time-domain resource and / or a flexible first time-domain resource is configured as uplink, and / or the terminal device is configured to receive downlink signals using a second time-domain resource and / or a flexible first time-domain resource is configured as downlink, and / or a second time-domain resource indicated as downlink by (second uplink / downlink configuration and / or third uplink / downlink configuration) is configured as downlink, and / or a second time-domain resource indicated as uplink by (second uplink / downlink configuration and / or the third uplink / downlink configuration) is configured as uplink.

[0270] In some embodiments, the reference cell has the first time-domain resources and / or the second time-domain resources.

[0271] The first time-domain resource (with or without the first and / or second time-domain resources) indicated as downlink by (first uplink and / or second uplink and / or third ...

[0272] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.

[0273] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0274] As can be seen from the above embodiments, in the presence of different time-domain resources, such as beams, channel states, frequency domain resources for uplink, and power control parameters, the network device can transmit the serving cell configuration and receive uplink signals in cells with first and / or second time-domain resources, thus supporting the transmission and reception of uplink signals in the presence of the aforementioned different time-domain resources.

[0275] Third aspect of the embodiments

[0276] This application provides a signal transmitting device. This device may be, for example, a terminal device, or one or more components or parts configured within a terminal device; details identical to those in the first aspect of the embodiment will not be repeated.

[0277] Figure 7 is a schematic diagram of a signal transmitting device according to an embodiment of this application. Since the principle of this device in solving the problem is the same as the method of the embodiment of the first aspect, its specific implementation can refer to the embodiment of the first aspect, and the contents that are the same will not be described again. As shown in Figure 7, the signal transmitting device 700 includes: a receiver 701 and a transmitter 702; it may also include a processor 703.

[0278] Receiver 701 receives serving cell configurations for one or more (serving) cells (each), at least one of the one or more (serving) cells having (or being configured with) a first time domain resource (non-SBFD) and / or a second time domain resource (SBFD), wherein, in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the first time domain resource is outside the second time domain resource;

[0279] Transmitter 702 transmits uplink signals in the (serving) cell having the first time domain resource and / or the second time domain resource.

[0280] In some embodiments, the terminal device is configured with one or more (serving) cells, and / or, the one or more (serving) cells belong to the same cell group or the multiple (serving) cells include (serving) cells belonging to different cell groups, and / or, the one or more (serving) cells include Pcell and / or Scell ​​and / or PScell ​​and / or PUCCH-Scell, and / or, the serving cell configuration is dedicated radio resource control (RRC) signaling.

[0281] In some embodiments, the processor 703 determines the power margin (based on a reference PUSCH) of (one or more) serving cells based on the preamble received target power.

[0282] In some embodiments, the processor 703 determines the power margin (based on a reference PUSCH) of the primary cell and / or secondary cell (Scell) (among the one or more serving cells) according to the preamble received target power, wherein the primary cell includes a Pcell and / or a PScell ​​and / or a PUCCH-Scell.

[0283] In some embodiments, the processor 703 determines the power margin (based on reference PUSCH) of (one or more serving cells) based on the first preamble received target power and / or the second preamble received target power.

[0284] In some embodiments, (for a serving cell having first time domain resources and / or second time domain resources, not configured with a unified TCI state, and configured with (two sets / two) preamble target received powers), processor 703 determines the (serving) cell's ...

[0285] In some embodiments, (for a secondary cell that has not been configured with preamble target received power, and the corresponding primary cell has a first time domain resource and / or a second time domain resource, and the corresponding primary cell is configured with (two sets / two) preamble target received power,) the processor 703 determines the power margin (based on reference PUSCH) of the secondary cell according to the first preamble received power (preambleReceivedTargetPower) and / or the second preamble received power (preambleReceivedTargetPower) of the primary cell (corresponding to the secondary cell).

[0286] In some embodiments, when the secondary cell has a first time-domain resource and / or a second time-domain resource, the power margin of the secondary cell (based on the reference PUSCH) is determined according to the time-domain resource type in the reference time slot using the first preamble received target power (preambleReceivedTargetPower) or the second preamble received target power (preambleReceivedTargetPower) of the primary cell (corresponding to the secondary cell).

[0287] In some embodiments, transmitter 702 sends a Power Headroom Report (PHR) (at least one of the one or more serving cells) to the network device, the Power Headroom Report being carried by a MAC CE.

[0288] In some embodiments, the serving cell having the first time domain resources and / or the second time domain resources (should) be configured with a unified TCI state (type).

[0289] In some embodiments, transmitter 702 transmits (capability) information indicating that the terminal device supports directional collision handling (mechanism) between a reference cell and other cells (in a TDD CA with the same SCS) for half-duplex operation, or that the (SBFD-aware) terminal device does not support directional collision handling (mechanism) between a reference cell and other cells (in a TDD CA with the same SCS) for half-duplex operation.

[0290] In some embodiments, (if the UE is not capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group), when the serving cell with the first time domain resource and / or the second time domain resource is the (active) cell with the smallest cell index in its cell group, none of the serving cells in the cell group containing the serving cell with the first time domain resource and / or the second time domain resource are configured with directional collision handling parameters (e.g., it is not allowed (not desired / prohibited) for any serving cell in the cell group containing the serving cell with the first time domain resource and / or the second time domain resource to be configured with directional collision handling parameters ()), and / or,

[0291] (If the UE is capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group,) when the serving cell with the first time domain resource and / or the second time domain resource is the (active) cell with the smallest cell index in its frequency band (within its cell group),) no serving cell in the frequency band of the serving cell with the first time domain resource and / or the second time domain resource is configured with directional collision handling parameters.

[0292] In some embodiments, the terminal device ignores the direction collision processing parameters of the serving cell.

[0293] In some embodiments, the serving cell having the first time domain resource and / or the second time domain resource is not configured with directional collision handling parameters.

[0294] (For example, it is not allowed (not expected / prohibited) for the same serving cell to be configured (simultaneously) with the first time domain resource and / or the second time domain resource and the directional collision handling parameter; or

[0295] For a serving cell configured with the first time-domain resource and / or the second time-domain resource, configuring the directional collision handling parameter (directionalCollisionHandling) is not allowed (not desired / prohibited); or

[0296] For a serving cell configured with directional collision handling parameters, it is not allowed (not desired / prohibited) for the serving cell to be configured with the first time domain resource and / or the second time domain resource.

[0297] In some embodiments, at least one serving cell in the cell group to which the serving cell with the first time domain resource and / or the second time domain resource is located (different from the serving cell with the first time domain resource and / or the second time domain resource) is configured with directional collision handling parameters.

[0298] In some embodiments, processor 703 determines a reference cell (for symbols).

[0299] In some embodiments, (UE expects) the reference cell to not have the first time domain resource and / or the second time domain resource.

[0300] In some embodiments, (if the UE is not capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group,) the reference cell of (all serving cells of the cell group configured with directionalCollisionHandling) is the (active) cell with the smallest cell index among the multiple serving cells in the cell group, or, is the (active) cell with the smallest cell index among one or more serving cells in the cell group other than the serving cell with the first time domain resource and / or the second time domain resource, or...

[0301] (if the UE is capable of simultaneous transmission and reception as indicated by simultaneousRxTxInterBandCA among the multiple serving cells of the cell group,) (for each frequency band of the cell group,) the reference cell is the (active) cell with the smallest cell index among the cells in one / each frequency band where the serving cell with directionalCollisionHandling is located, or, the (active) cell with the smallest cell index among the cells in one / each frequency band where the serving cell with directionalCollisionHandling is located, excluding the serving cell with the first time domain resource and / or the second time domain resource.

[0302] In some embodiments, the reference cell has the first time-domain resources and / or the second time-domain resources.

[0303] A first time-domain resource indicated as downlink by (first uplink / downlink configuration and / or second uplink / downlink configuration) is configured as downlink, and / or a first time-domain resource indicated as uplink by (first uplink / downlink configuration and / or second uplink / downlink configuration) is configured as uplink, and / or the terminal device is configured to transmit uplink signals using a second time-domain resource and / or a flexible first time-domain resource is configured as uplink, and / or the terminal device is configured to receive downlink signals using a second time-domain resource and / or a flexible first time-domain resource is configured as downlink, and / or a second time-domain resource indicated as downlink by (second uplink / downlink configuration and / or third uplink / downlink configuration) is configured as downlink, and / or a second time-domain resource indicated as uplink by (second uplink / downlink configuration and / or the third uplink / downlink configuration) is configured as uplink.

[0304] In some embodiments, the reference cell has the first time-domain resources and / or the second time-domain resources.

[0305] The first time-domain resource (with or without the first and / or second time-domain resources) indicated as downlink by (first uplink and / or second uplink and / or third ...

[0306] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The signal transmitting device 700 of this application embodiment may also include other components or modules, and for details of these components or modules, please refer to related technologies.

[0307] Furthermore, for simplicity, Figure 7 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0308] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0309] As can be seen from the above embodiments, in the presence of different time-domain resources, such as beams, channel states, frequency domain resources for uplink, and power control parameters, the terminal device receives the serving cell configuration and transmits uplink signals in a cell with first and / or second time-domain resources, thus enabling the transmission and reception of uplink signals in the presence of the aforementioned different time-domain resources.

[0310] Fourth aspect of the embodiment

[0311] This application provides a signal receiving device. This device may be, for example, a network device, or one or more components or parts configured within a network device; details identical to those in the second aspect of the embodiment will not be repeated.

[0312] Figure 8 is a schematic diagram of a signal receiving device according to an embodiment of this application. Since the principle of this device in solving the problem is the same as the method of the embodiment of the second aspect, its specific implementation can refer to the embodiment of the second aspect, and the contents that are the same will not be repeated. As shown in Figure 8, the signal receiving device 800 includes: a transmitter 801 and a receiver 802; it may also include a processor 803.

[0313] Transmitter 801 transmits serving cell configurations for one or more (serving) cells (each), at least one of the one or more (serving) cells having (or being configured with) a first time domain resource (non-SBFD) and / or a second time domain resource (SBFD), wherein, in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the first time domain resource is outside the second time domain resource;

[0314] Receiver 802 receives uplink signals in a (serving) cell having the first time domain resources and / or the second time domain resources.

[0315] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The signal receiving device 800 of this application embodiment may also include other components or modules, and for details of these components or modules, please refer to related technologies.

[0316] Furthermore, for simplicity, Figure 8 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0317] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0318] As can be seen from the above embodiments, in the presence of different time-domain resources, such as beams, channel states, frequency domain resources for uplink, and power control parameters, the network device can transmit the serving cell configuration and receive uplink signals in cells with first and / or second time-domain resources, thus supporting the transmission and reception of uplink signals in the presence of the aforementioned different time-domain resources.

[0319] Fifth aspect of the embodiment

[0320] This application also provides a communication system, which can be referred to FIG1. ​​The contents that are the same as those in the embodiments of the first to fourth aspects will not be repeated.

[0321] In some embodiments, the communication system 100 may include at least:

[0322] A network device that transmits serving cell configurations for one or more (serving) cells, at least one of the one or more (serving) cells having (or being configured with) a first time domain resource (non-SBFD) and / or a second time domain resource (SBFD), wherein, in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the first time domain resource is outside the second time domain resource; and receives uplink signals in the (serving) cell having the first time domain resource and / or the second time domain resource;

[0323] A terminal device that receives serving cell configurations for one or more (serving) cells (each); and transmits uplink signals in the (serving) cell having the first time domain resources and / or the second time domain resources.

[0324] This application also provides a network device, such as a base station, but this application is not limited to this and may also include other network devices.

[0325] Figure 9 is a schematic diagram of the network device according to an embodiment of this application. As shown in Figure 9, the network device 900 may include: a processor 910 (e.g., a central processing unit CPU) and a memory 920; the memory 920 is coupled to the processor 910. The memory 920 can store various data; in addition, it also stores an information processing program 930, and executes the program 930 under the control of the processor 910.

[0326] For example, processor 910 can be configured to execute a program to implement the method as described in the embodiments of the second aspect.

[0327] In addition, as shown in Figure 9, the network device 900 may also include a transceiver 940 and an antenna 950, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that the network device 900 does not necessarily have to include all the components shown in Figure 9; in addition, the network device 900 may also include components not shown in Figure 9, which can be referred to in the prior art.

[0328] This application also provides a terminal device, but the application is not limited thereto and may also include other devices.

[0329] Figure 10 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 10, the terminal device 1000 may include a processor 1010 and a memory 1020; the memory 1020 stores data and programs and is coupled to the processor 1010. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0330] For example, processor 1010 can be configured to execute a program to implement the method as described in the embodiment of the first aspect.

[0331] As shown in Figure 10, the terminal device 1000 may further include: a communication module 1030, an input device 1040, a display 1050, and a power supply 1060. The functions of these components are similar to those in the prior art and will not be described in detail here. It is worth noting that the terminal device 1000 does not necessarily include all the components shown in Figure 10; these components are not essential. Furthermore, the terminal device 1000 may also include components not shown in Figure 10, which can be referred to in the prior art.

[0332] This application also provides a computer-readable program, wherein when the program is executed in a network device, the program causes the computer to perform the method described in the second aspect of the embodiment in the network device.

[0333] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer in a network device to perform the methods described in the second aspect of the embodiments.

[0334] This application also provides a computer-readable program, wherein when the program is executed in a terminal device, the program causes the computer to perform the method described in the first aspect of the embodiment in the terminal device.

[0335] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer in a terminal device to perform the method described in the first aspect of the embodiments.

[0336] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. Logic components include, for example, field-programmable logic devices (FPGAs), microprocessors, and processors used in computers. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, and flash memory.

[0337] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

[0338] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

[0339] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0340] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0341] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0342] 1. A signal transmission method, comprising:

[0343] The terminal device receives serving cell configurations for one or more (serving) cells (each), at least one of the one or more (serving) cells having (or being configured with) a first time domain resource (non-SBFD) and / or a second time domain resource (SBFD), wherein, in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the first time domain resource is outside the second time domain resource;

[0344] The terminal device transmits an uplink signal in the (serving) cell that has the first time domain resources and / or the second time domain resources.

[0345] 2. A signal receiving method, comprising:

[0346] The network device sends a serving cell configuration for one or more (serving) cells, at least one of the one or more (serving) cells having a first time domain resource (non-SBFD) and / or a second time domain resource (SBFD), wherein, in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the first time domain resource is outside the second time domain resource;

[0347] The network device receives uplink signals in a (serving) cell that has the first time domain resources and / or the second time domain resources.

[0348] 3. According to the method described in Appendix 2, a cell having the first time domain resource and / or the second time domain resource can only be used as a Pcell, or a cell having the first time domain resource and / or the second time domain resource can be used as a Pcell / PScell / SpCell / PUCCH-Scell / Scell / primary cell.

[0349] 4. The method according to Appendix 2 or 3, wherein,

[0350] Carrier aggregation (CA) and dual connectivity (DC) between a cell / carrier having the first time domain resource and / or the second time domain resource and another cell / carrier (having / not having the first time domain resource and / or the second time domain resource) are not supported; or

[0351] Carrier aggregation (CA) between a cell / carrier having the first time domain resource and / or the second time domain resource and another cell / carrier (having / not having the first time domain resource and / or the second time domain resource) is not supported; dual connectivity (DC) between a cell / carrier having the first time domain resource and / or the second time domain resource and another cell / carrier (having / not having the first time domain resource and / or the second time domain resource) is supported; or

[0352] Supports carrier aggregation (CA) between a cell / carrier with the first time domain resource and / or the second time domain resource and another cell / carrier (with / without the first time domain resource and / or the second time domain resource), but does not support dual connectivity (DC) between a cell / carrier with the first time domain resource and / or the second time domain resource and another cell / carrier (with / without the first time domain resource and / or the second time domain resource); or

[0353] PUCCH groups that include a cell / carrier having the first time domain resource and / or the second time domain resource and another cell / carrier (having / not having the first time domain resource and / or the second time domain resource) are not supported.

[0354] 5. The method according to Appendix 2, wherein the method further comprises:

[0355] The network device receives a Power Headroom Report (PHR) from at least one of the one or more serving cells, the PHR being carried by a MAC CE.

[0356] 6. The method according to Appendix 2, wherein the method further comprises:

[0357] The network device receives (capability) information indicating that the terminal device supports orientation collision handling (mechanism) between a reference cell and other cells for half-duplex operation (in a TDD CA with the same SCS).

[0358] 7. A terminal device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the signal transmission method as described in Appendix 1.

[0359] 8. A network device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the signal receiving method as described in any one of Appendices 2 to 6.

[0360] 9. A computer program product comprising at least a computer program that, when executed by a processor, causes a terminal device to perform the signal transmission method as described in Appendix 1.

[0361] 10. A computer program product comprising at least a computer program that, when executed by a processor, causes a network device to perform a signal receiving method as described in any one of Appendices 2 to 6.

Claims

1. A signal transmitting device, comprising: A receiver receives serving cell configurations for one or more cells, at least one of which has a first time-domain resource and / or a second time-domain resource, wherein, in the second time-domain resource, the first frequency-domain resource is used for uplink and the second frequency-domain resource is used for downlink, and the first time-domain resource is outside the second time-domain resource; A transmitter that transmits uplink signals in a cell having the first time domain resource and / or the second time domain resource.

2. The apparatus according to claim 1, wherein, The terminal device is configured with one or more cells, and / or, the one or more cells belong to the same cell group or the multiple cells include cells belonging to different cell groups, and / or, the one or more cells include Pcell and / or Scell ​​and / or PScell ​​and / or PUCCH-Scell, and / or, the serving cell configuration is dedicated radio resource control signaling.

3. The apparatus according to claim 1, wherein, The device further includes: The processor determines the power margin based on the target received power of the preamble sequence.

4. The apparatus according to claim 3, wherein, The power margin of the primary cell and / or secondary cell is determined based on the target received power of the preamble sequence, wherein the primary cell includes Pcell and / or PScell ​​and / or PUCCH-Scell.

5. The apparatus according to claim 3, wherein, The power margin is determined based on the target received power of the first preamble sequence and / or the target received power of the second preamble sequence.

6. The apparatus according to claim 3, wherein, The power margin of the cell is determined based on the target received power of the first preamble sequence and / or the target received power of the second preamble sequence.

7. The apparatus according to claim 3, wherein, The power margin of the secondary cell is determined based on the target received power of the first preamble sequence and / or the target received power of the second preamble sequence of the primary cell.

8. The apparatus according to claim 3, wherein, The transmitter sends a power headroom report to the network device, and the power headroom report is carried by the MAC CE.

9. The apparatus according to claim 1, wherein, Cells with the first time domain resources and / or the second time domain resources are configured with a unified TCI status.

10. The apparatus according to claim 1, wherein, The transmitter sends information indicating that the terminal device supports directional collision processing between the reference cell and other cells for half-duplex operation, or does not support directional collision processing between the reference cell and other cells for half-duplex operation.

11. The apparatus according to claim 1, wherein, No cell in the cell group containing the cell with the first time domain resource and / or the second time domain resource is configured with directional collision processing parameters.

12. The apparatus according to claim 1, wherein, Cells with the first time-domain resources and / or the second time-domain resources are not configured with directional collision handling parameters.

13. The apparatus according to claim 1, wherein, At least one cell in the cell group containing the cell with the first time-domain resource and / or the second time-domain resource is configured with orientation collision handling parameters.

14. The apparatus according to claim 13, wherein, The device further includes: The processor determines the reference cell.

15. The apparatus according to claim 14, wherein, The reference cell does not have the first time domain resources and / or the second time domain resources.

16. The apparatus according to claim 14, wherein, The reference cell is the cell with the smallest cell index among multiple cells in the cell group, or, it is the cell with the smallest cell index among one or more cells in the cell group other than the cells with the first time-domain resources and / or the second time-domain resources. The reference cell is the cell with the smallest cell index in one / each frequency band, or the cell with the smallest cell index in one / each frequency band other than the cell with the first time domain resource and / or the second time domain resource.

17. The apparatus according to claim 14, wherein, The reference cell has the first time-domain resources and / or the second time-domain resources. A first time domain resource indicated as downlink is configured as downlink, and / or a first time domain resource indicated as uplink is configured as uplink, and / or a terminal device is configured to transmit an uplink signal via a second time domain resource and / or a flexible first time domain resource is configured as uplink, and / or the terminal device is configured to receive a downlink signal via a second time domain resource and / or a flexible first time domain resource is configured as downlink, and / or a second time domain resource indicated as downlink is configured as downlink, and / or a second time domain resource indicated as uplink is configured as uplink.

18. The apparatus according to claim 14, wherein, The reference cell has the first time-domain resources and / or the second time-domain resources. The first time-domain resource indicated as downlink and / or the second time-domain resource indicated as downlink are determined to be invalid time-domain resources for PUSCH duplication in a cell configured with direction conflict handling parameters.

19. A signal receiving device, comprising: A transmitter that transmits serving cell configurations for one or more cells, at least one of the one or more cells having a first time domain resource and / or a second time domain resource, wherein, in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the first time domain resource is outside the second time domain resource; A receiver that receives uplink signals in a cell having the first time domain resources and / or the second time domain resources.

20. A communication system, comprising: A network device that transmits serving cell configurations for one or more cells, at least one of the one or more cells having first time-domain resources and / or second time-domain resources, wherein, in the second time-domain resources, the first frequency-domain resources are used for uplink and the second frequency-domain resources are used for downlink, and the first time-domain resources are outside the second time-domain resources; and receives uplink signals in cells having the first time-domain resources and / or the second time-domain resources; A terminal device that receives serving cell configurations for one or more cells; and transmits uplink signals in cells having the first time domain resources and / or the second time domain resources.

Images