Uplink communication processing methods, communication equipment and storage media

Abstract

This disclosure relates to the field of communication technology, specifically to an uplink communication processing method, communication device, and storage medium. The uplink communication processing method includes: transmitting a multi-timeslot transport block physical uplink shared channel according to predefined rules, wherein the multi-timeslot transport block physical uplink shared channel conflicts with a broadcast message in a first time domain unit, and the first time domain unit is configured with sub-bands. According to this disclosure, in some SBFD time domain units, even if the TBoMS PUSCH conflicts with a broadcast message, TBoMS technology can still be applied, which helps to ensure the uplink coverage gain brought by transmitting the TBoMS PUSCH in the SBFD time slot.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to uplink communication processing methods, terminals, network devices, communication devices, and storage media. Background Technology

[0002] Network devices can communicate with terminals within a time-domain unit. Within a time-slot unit, a network device can only perform either uplink or downlink communication. To improve communication efficiency, network devices can perform both uplink and downlink communication within a single time-slot unit, thus achieving full-duplex communication. However, some technical challenges arise in full-duplex communication scenarios. Summary of the Invention

[0003] The embodiments of this disclosure provide an uplink communication processing method, a terminal, a network device, a communication device, and a storage medium to solve the technical problems existing in the related art when a network device performs communication after configuring a subband for a terminal.

[0004] According to a first aspect of the present disclosure, an uplink communication processing method is proposed, the method comprising: transmitting a multi-timeslot transport block physical uplink shared channel according to predefined rules, wherein the multi-timeslot transport block physical uplink shared channel conflicts with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a sub-band.

[0005] According to a second aspect of the present disclosure, an uplink communication processing method is proposed, the method comprising: receiving a multi-timeslot transport block physical uplink shared channel sent by a terminal according to a predefined rule, wherein the multi-timeslot transport block physical uplink shared channel conflicts with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a sub-band.

[0006] According to a third aspect of the present disclosure, an uplink communication processing method is proposed, the method comprising: a terminal sending a multi-timeslot transport block physical uplink shared channel according to predefined rules, wherein the multi-timeslot transport block physical uplink shared channel conflicts with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a sub-band; and a network device receiving the multi-timeslot transport block physical uplink shared channel sent by the terminal according to predefined rules.

[0007] According to a fourth aspect of the present disclosure, a terminal is provided, comprising: one or more processors; wherein the terminal is configured to execute the uplink communication processing method described in the first aspect above.

[0008] According to a fifth aspect of the present disclosure, a network device is provided, comprising: one or more processors; wherein the network device is configured to perform the uplink communication processing method described in the second aspect above.

[0009] According to a sixth aspect of the present disclosure, a communication device is provided, comprising: one or more processors; wherein the processors are configured to invoke instructions to cause the communication device to perform the uplink communication processing method described in any one of the first and second aspects above.

[0010] According to a seventh aspect of the present disclosure, a communication system is provided, including a terminal and a network device, wherein the terminal is configured to implement the uplink communication processing method described in the first aspect above, and the network device is configured to implement the uplink communication processing method described in the second aspect above.

[0011] According to an eighth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform an uplink communication processing method as described in any one of the first and second aspects above.

[0012] According to embodiments of this disclosure, in some SBFD time-domain units, TBoMS technology can be applied even if TBoMS PUSCH conflicts with broadcast messages, which helps to ensure the uplink coverage gain brought by transmitting TBoMS PUSCH in the SBFD time slot. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0015] Figure 2 This is an interactive schematic diagram illustrating an uplink communication processing method according to an embodiment of the present disclosure.

[0016] Figure 3 This is a schematic flowchart illustrating an uplink communication processing method according to an embodiment of the present disclosure.

[0017] Figure 4 This is a schematic diagram of a sub-band according to an embodiment of the present disclosure.

[0018] Figure 5 This is a schematic diagram illustrating a conflict according to an embodiment of the present disclosure.

[0019] Figure 6AThis is a schematic diagram illustrating another conflict according to an embodiment of the present disclosure.

[0020] Figure 6B This is a schematic diagram illustrating a processing result according to an embodiment of the present disclosure.

[0021] Figure 6C This is a schematic diagram illustrating another processing result according to an embodiment of the present disclosure.

[0022] Figure 7 This is a schematic diagram illustrating a processing result according to an embodiment of the present disclosure.

[0023] Figure 8 This is a schematic flowchart illustrating an uplink communication processing method according to an embodiment of the present disclosure.

[0024] Figure 9 This is a schematic block diagram of a terminal according to an embodiment of the present disclosure.

[0025] Figure 10 This is a schematic block diagram of a network device apparatus according to embodiments of the present disclosure.

[0026] Figure 11 This is a schematic diagram of the structure of the communication device proposed in the embodiments of this disclosure.

[0027] Figure 12 This is a schematic diagram of the chip structure proposed in the embodiments of this disclosure. Detailed Implementation

[0028] Embodiments of this disclosure provide an uplink communication processing method, a terminal, a network device, a communication device, and a storage medium.

[0029] In a first aspect, embodiments of this disclosure propose an uplink communication processing method, the method comprising: transmitting a multi-timeslot transport block physical uplink shared channel according to predefined rules, wherein the multi-timeslot transport block physical uplink shared channel conflicts with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with sub-bands.

[0030] In the above embodiments, when the terminal determines that a TBoMS PUSCH conflicts with a broadcast message in the SBFD time domain unit, the terminal may not default to not expecting to send the TBoMS PUSCH in that SBFD time domain unit. Instead, it can determine how to handle the TBoMS PUSCH according to predefined rules. For example, it may send the TBoMS PUSCH in the SBFD time domain unit, or it may not send the TBoMS PUSCH in the SBFD time domain unit. Accordingly, in some SBFD time domain units, even if the TBoMS PUSCH conflicts with a broadcast message, TBoMS technology can still be applied, which helps to ensure the uplink coverage gain brought by sending the TBoMS PUSCH in the SBFD time slot.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, the transmission of the multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0032] The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit;

[0033] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the second time domain unit;

[0034] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the processing method for the physical uplink shared channel is determined according to predefined rules, including at least one of the following:

[0036] The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the time domain unit.

[0037] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, so it is not expected to transmit the physical uplink shared channel in the time domain unit.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, transmitting a multi-slot transport block physical uplink shared channel according to predefined rules includes: if a first frequency domain resource of the physical uplink shared channel is not entirely located within an uplink subband, determining a second frequency domain resource within the uplink subband; and transmitting the physical uplink shared channel in the second frequency domain resource.

[0039] In the above embodiments, when the first frequency domain resources of TBoMS PUSCH are not all located within the uplink subband, it is also possible to determine that the second frequency domain resources are used to transmit TBoMS PUSCH in the conflicting SBFD time domain units, which helps to ensure the uplink coverage gain brought by the transmission of TBoMS PUSCH in the SBFD time slot.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, determining a second frequency domain resource within an uplink subband includes:

[0041] Within the uplink subband, the frequency domain resources that extend from the first frequency domain position to the first frequency domain range are defined as the second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the receiving terminal's multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0043] The frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit;

[0044] The frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is transmitted in the second time domain unit;

[0045] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the transmission of the multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0047] The frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit;

[0048] The frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink sub-band, and it is not expected to transmit the physical uplink shared channel in the first time domain unit.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the transmission of the multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0050] When the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0051] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be sent in the first time domain unit.

[0052] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is transmitted in the first time domain unit.

[0053] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0054] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the transmission of the multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0056] When the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0057] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0058] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is transmitted in the first time domain unit.

[0059] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0060] In the above embodiments, when the first frequency domain interval is less than the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit and receives TBoMS PUSCH in the time domain unit. The frequency domain interference between TBoMS PUSCH and the broadcast message is relatively large, which has a significant impact on communication quality. Therefore, the terminal does not want to send TBoMS PUSCH in the conflicting time domain unit, which is beneficial to ensuring relatively good communication quality.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the second time-domain unit is not configured with sub-bands.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, the conflict between the physical uplink shared channel and broadcast messages in a time-domain unit configured with subbands includes at least one of the following:

[0063] The first time-domain resource of the physical uplink shared channel in the time-domain unit configured with sub-bands partially overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0064] The first time-domain resource of the physical uplink shared channel in the time-domain unit configured with sub-bands completely overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0065] The physical uplink shared channel and broadcast messages are in the same time-domain unit with subbands.

[0066] In the above embodiments, by considering conflict scenarios under multiple conditions, it is beneficial to ensure that all conflict scenarios are taken into account, and thus to more comprehensively determine the handling method of TBoMS PUSCH under conflict scenarios.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, broadcast message conflicts include at least one of the following: synchronization signal blocks; common search space.

[0068] Secondly, embodiments of this disclosure propose an uplink communication processing method, the method comprising: receiving a multi-timeslot transport block physical uplink shared channel sent by a terminal according to predefined rules, wherein the multi-timeslot transport block physical uplink shared channel conflicts with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a sub-band.

[0069] In conjunction with some embodiments of the second aspect, in some embodiments, receiving the multi-slot transport block physical uplink shared channel sent by the terminal according to predefined rules includes at least one of the following: the first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit; or the first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the physical uplink shared channel is received in the second time domain unit; wherein the second time domain unit is a different time domain unit from the first time domain unit.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the predefined rule is used to indicate that when the first frequency domain resources of the physical uplink shared channel are not entirely located within the uplink subband, the physical uplink shared channel is received in the second frequency domain resources, wherein the second frequency domain resources are entirely located within the uplink subband.

[0071] In conjunction with some embodiments of the second aspect, in some embodiments, the step of receiving the multi-slot transport block physical uplink shared channel sent by the terminal according to predefined rules includes:

[0072] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the second frequency domain resources are determined within the uplink sub-band.

[0073] The physical uplink shared channel is received in the second frequency domain resource.

[0074] In conjunction with some embodiments of the second aspect, in some embodiments, determining the second frequency domain resource within the uplink sub-band includes: determining a frequency domain resource within the uplink sub-band that extends from a first frequency domain position and lasts for a first frequency domain range as the second frequency domain resource, wherein the first frequency domain range is determined based on the first frequency domain resource.

[0075] In conjunction with some embodiments of the second aspect, in some embodiments, receiving the physical uplink shared channel of a multi-slot transport block sent by the terminal according to predefined rules includes at least one of the following: the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit; the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the second time domain unit; wherein the second time domain unit is a different time domain unit from the first time domain unit.

[0076] In conjunction with some embodiments of the second aspect, in some embodiments, receiving the physical uplink shared channel of a multi-slot transport block sent by the terminal according to predefined rules includes at least one of the following: the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit; the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is not expected to be received in the first time domain unit.

[0077] In conjunction with some embodiments of the second aspect, the receipt of the multi-slot transport block physical uplink shared channel sent by the terminal according to predefined rules includes at least one of the following: the first frequency domain interval between the uplink sub-band and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit; the first frequency domain interval between the uplink sub-band and the broadcast message is less than the frequency domain interval threshold, and the physical uplink shared channel is not expected to be received in the first time domain unit.

[0078] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit.

[0079] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be received in the first time domain unit.

[0080] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0081] In conjunction with some embodiments of the second aspect, in some embodiments, the receiving terminal's multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0082] The first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit.

[0083] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be received in the first time domain unit.

[0084] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit.

[0085] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be received in the first time domain unit.

[0086] In conjunction with some embodiments of the second aspect, in some embodiments, the second time-domain unit is not configured with sub-bands.

[0087] In conjunction with some embodiments of the second aspect, in some embodiments, the conflict between the physical uplink shared channel and broadcast messages in a time-domain unit configured with subbands includes at least one of the following:

[0088] The first time domain resource of the physical uplink shared channel in the time domain unit configured with sub-bands partially overlaps with the second time domain resource of the broadcast message in the first time domain unit;

[0089] The first time domain resources of the physical uplink shared channel in the time domain unit configured with sub-bands completely overlap with the second time domain resources of the broadcast message in the first time domain unit;

[0090] The physical uplink shared channel and the broadcast message reside in the same time-domain unit configured with subbands.

[0091] In conjunction with some embodiments of the second aspect, in some embodiments, the broadcast message conflict includes at least one of the following: a synchronization signal block; a common search space.

[0092] Thirdly, embodiments of this disclosure propose an uplink communication processing method, the method comprising: a terminal sending a multi-timeslot transport block physical uplink shared channel according to predefined rules, wherein the multi-timeslot transport block physical uplink shared channel conflicts with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a sub-band; and a network device receiving the multi-timeslot transport block physical uplink shared channel sent by the terminal according to predefined rules.

[0093] Fourthly, embodiments of this disclosure provide a terminal, including: one or more processors; wherein the terminal is configured to execute the uplink communication processing method described in the first aspect and the optional embodiments of the first aspect.

[0094] Fifthly, embodiments of this disclosure provide a network device comprising: one or more processors; wherein the network device is configured to perform the uplink communication processing method described in the second aspect and optional embodiments thereof.

[0095] In a sixth aspect, embodiments of this disclosure provide a communication device comprising: one or more processors; one or more memories for storing instructions; wherein the processors are configured to invoke the instructions to cause the communication device to perform an uplink communication processing method as described in the first and second aspects, and optional implementations of the first and second aspects.

[0096] In a sixth aspect, embodiments of this disclosure provide a communication system comprising: a terminal and a network device; wherein the terminal is configured to perform an uplink communication processing method as described in the first and second aspects and optional implementations of the first and second aspects, and the network device is configured to perform an uplink communication processing method as described in the first and second aspects and optional implementations of the first and second aspects.

[0097] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the uplink communication processing method as described in the first and second aspects, and optional implementations of the first and second aspects.

[0098] Eighthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the uplink communication processing method as described in the first and second aspects, and optional implementations of the first and second aspects.

[0099] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the uplink communication processing method as described in the first and second aspects, and alternative implementations of the first and second aspects.

[0100] It is understood that the aforementioned terminals, network devices, communication devices, communication systems, storage media, program products, and computer programs are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0101] This disclosure provides an uplink communication processing method, a communication device, and a storage medium. In some embodiments, the terms "uplink communication processing method" and "information processing method," "communication method," etc., can be used interchangeably; the terms "terminal," "network device," "information processing apparatus," "communication apparatus," etc., can be used interchangeably; and the terms "information processing system," "communication system," etc., can be used interchangeably.

[0102] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0103] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0104] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0105] In the embodiments of this disclosure, unless otherwise stated, elements expressed in the singular, such as “a,” “an,” “the,” “the,” “the,” “the,” “the,” “the,” “this,” etc., may mean “one and only one,” or “one or more,” “at least one,” etc.

[0106] In the embodiments disclosed herein, "multiple" refers to two or more.

[0107] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0108] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0109] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0110] The prefixes such as "first" and "second" in the embodiments of this disclosure are only for distinguishing different descriptive objects and do not constitute restrictions on the position, order, priority, number or content of the descriptive objects. For the description of the descriptive objects, please refer to the description in the claims or the context of the embodiments. The use of prefixes should not constitute unnecessary restrictions.

[0111] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0112] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0113] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to those used in the embodiments.

[0114] The terms “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0115] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0116] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0117] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriberstation, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, and client can be used interchangeably.

[0118] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0119] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0120] Figure 1 This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0121] like Figure 1 As shown, the communication system 100 includes a terminal 101 and a network device 102, wherein the network device includes at least one of the following: an access network device and a core network device.

[0122] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0123] In some embodiments, the access network device 102 may be a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0124] In some embodiments, the core network device 103 may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0125] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0126] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0127] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0128] The following embodiments of this disclosure can be applied to Figure 1 The communication system 100 shown, or a part thereof, but not limited to it. Figure 1 The entities shown are illustrative; a communication system may include... Figure 1 All or part of the main body, or may include Figure 1 Other entities besides the main body, the number and form of each entity are arbitrary, each entity can be physical or virtual, the connection relationship between the entities is illustrative, the entities can be unconnected or connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0129] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Futuregeneration radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0130] In some embodiments, the network device can configure subbands for terminals.

[0131] In some embodiments, the subband includes at least one of the following: an uplink subband and a downlink subband.

[0132] In some embodiments, the network device may configure an uplink subband for a terminal in a first type of time slot, wherein the first type of time slot includes at least one of the following: a downlink time slot and a flexible time slot.

[0133] The frequency domain resources corresponding to the downlink time slot are downlink frequency domain resources. In the downlink time slot, an uplink sub-band is configured for the terminal. The frequency domain resources of the downlink time slot corresponding to the uplink sub-band can then be used for uplink communication. Thus, network devices can perform uplink communication in the uplink sub-band corresponding to the downlink time slot, and downlink communication in the frequency domain resources outside the uplink sub-band, thereby achieving full-duplex communication.

[0134] The frequency domain resources corresponding to flexible time slots can be configured or scheduled as downlink frequency domain resources. Uplink subbands are configured for terminals within the flexible time slots, and the frequency domain resources corresponding to these uplink subbands can then be used for uplink communication. This allows network devices to perform uplink communication within the uplink subband corresponding to the flexible time slot, and downlink communication within frequency domain resources outside the uplink subband, thus achieving full-duplex communication. For example, a time domain unit configured with subbands can be called a Subband Based Full Duplex (SBFD) time domain unit.

[0135] In some embodiments, the network device may configure downlink subbands for terminals in a second type of time slot, wherein the second type of time slot includes at least one of the following: uplink time slot, flexible time slot.

[0136] The frequency domain resources corresponding to the uplink time slot are uplink frequency domain resources. Downlink sub-bands are configured for terminals in the uplink time slots. The frequency domain resources of the uplink time slots corresponding to the downlink sub-bands can then be used for downlink communication. Thus, network devices can perform downlink communication in the downlink sub-bands corresponding to the uplink time slots, and perform uplink communication in the frequency domain resources outside the downlink sub-bands, thereby achieving full-duplex communication.

[0137] The frequency domain resources corresponding to the flexible time slot can be configured or scheduled as uplink frequency domain resources. Downlink sub-bands are configured for terminals in the flexible time slot, and the frequency domain resources of the corresponding downlink sub-band in the frequency domain resources of the flexible time slot can be used for downlink communication. Thus, network devices can perform downlink communication in the downlink sub-band corresponding to the flexible time slot, and perform uplink communication in the frequency domain resources outside the downlink sub-band, thereby realizing full-duplex communication.

[0138] In some embodiments, the communication that the terminal and the network device can perform in the time domain unit includes at least one of the following: data communication and non-data communication (e.g., signaling communication).

[0139] When a terminal performs data communication within a time-domain unit (e.g., the terminal sends a Transport Block (TB) to a network device or receives a TB sent by a network device), in some scenarios, data communication can occur within multiple time-domain units. For example, when a time-domain unit includes a slot, the terminal can send a Physical Uplink Shared Channel (PUSCH) based on TB processing over Multiple Slots (TBoMS) to the network device in multiple slots. In some embodiments, the time-domain resources and / or frequency-domain resources used to send the TBoMS PUSCH in each slot can be the same.

[0140] In some embodiments, TBoMS PUSCH can be combined with PDSCH repetition. For example, TBoMS PUSCH occupies n time slots, and the content of a TB can be transmitted in these n time slots. The TB can be retransmitted k times, that is, the number of PDSCH repetitions is k. Then, the terminal can transmit the TB based on TBoMS PUSCH and PDSCH repetition, and can transmit PUSCH on n×k time slots.

[0141] In some embodiments, when the multiple time-domain units used to send TBoMS PUSCH include SBFD time-domain units, since both uplink and downlink communication can be performed on the SBFD time-domain unit, there may be a situation where the broadcast message sent by the network device conflicts with the TBoMS PUSCH on the SBFD time-domain unit.

[0142] Figure 2 This is an interactive schematic diagram illustrating an uplink communication processing method according to an embodiment of the present disclosure.

[0143] like Figure 2 As shown, the uplink communication processing method includes:

[0144] In step S201, the terminal sends the multi-slot transport block physical uplink shared channel according to predefined rules.

[0145] In some embodiments, the predefined rules may be determined by the root protocol agreement.

[0146] In some embodiments, the physical uplink shared channel is sent from the terminal to the network device.

[0147] In some embodiments, predefined rules are used to indicate how the physical uplink shared channel is handled.

[0148] In some embodiments, the physical uplink shared channel is transmitted based on multi-slot transport block processing.

[0149] In some embodiments, predefined rules are used to instruct the terminal how to handle the physical uplink shared channel when the physical uplink shared channel and broadcast messages conflict in a time-domain unit configured with subbands.

[0150] In some embodiments, a conflict includes at least one of the following: determining that a conflict is occurring; predicting that a conflict will occur in a future time-domain unit.

[0151] In some embodiments, the conflict between the physical uplink shared channel and broadcast messages in a time-domain unit configured with subbands includes at least one of the following:

[0152] The first time-domain resource of the physical uplink shared channel in the time-domain unit configured with sub-bands partially overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0153] The first time-domain resource of the physical uplink shared channel in the time-domain unit configured with sub-bands completely overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0154] The physical uplink shared channel and broadcast messages are in the same time-domain unit with subbands.

[0155] In some embodiments, broadcast message conflicts include at least one of the following: synchronization signal blocks; common search space.

[0156] In some embodiments, predefined rules are used to indicate that: if all the first frequency domain resources of the physical uplink shared channel are located within the uplink sub-band, the physical uplink shared channel is transmitted in the first time domain unit; if not all the first frequency domain resources of the physical uplink shared channel are located within the uplink sub-band, the physical uplink shared channel is transmitted in the second time domain unit.

[0157] In some embodiments, the terminal transmits a multi-slot transport block physical uplink shared channel according to predefined rules, including at least one of the following: the first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit; or the first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the second time domain unit; wherein the second time domain unit is a different time domain unit from the first time domain unit.

[0158] In some embodiments, predefined rules are used to indicate that: if all the first frequency domain resources of the physical uplink shared channel are within the uplink subband, the physical uplink shared channel is transmitted in the time domain unit; if not all the first frequency domain resources of the physical uplink shared channel are within the uplink subband, the physical uplink shared channel is not expected to be transmitted in the time domain unit.

[0159] In some embodiments, the terminal transmits a multi-slot transport block physical uplink shared channel according to predefined rules, including at least one of the following: the first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the time domain unit; the first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the physical uplink shared channel is not expected to be transmitted in the time domain unit.

[0160] In some embodiments, a predefined rule is used to indicate that when the first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, the physical uplink shared channel is transmitted in the second frequency domain resources, wherein the second frequency domain resources are all located within the uplink subband.

[0161] In some embodiments, the terminal transmits a multi-slot transport block physical uplink shared channel according to predefined rules, including: the first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, and a second frequency domain resource is determined within the uplink subband; the physical uplink shared channel is transmitted in the second frequency domain resources.

[0162] In some embodiments, the terminal determines a second frequency domain resource within an uplink subband, including: determining a frequency domain resource within the uplink subband that extends from a first frequency domain position and continues within a first frequency domain range as the second frequency domain resource, wherein the first frequency domain range is determined based on the first frequency domain resource.

[0163] In some embodiments, predefined rules are used to indicate that: if the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, the physical uplink shared channel is transmitted in the first time domain unit; if the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, the physical uplink shared channel is transmitted in the second time domain unit.

[0164] In some embodiments, the physical uplink shared channel of the multi-slot transport block sent by the receiving terminal according to predefined rules further includes at least one of the following: the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is sent in the first time domain unit; the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is sent in the second time domain unit; wherein the second time domain unit is a different time domain unit from the first time domain unit.

[0165] In some embodiments, predefined rules are used to indicate that: if the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, the physical uplink shared channel is transmitted in the first time domain unit; if the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, the physical uplink shared channel is not expected to be transmitted in the first time domain unit.

[0166] In some embodiments, transmitting the physical uplink shared channel of a multi-slot transport block according to predefined rules includes at least one of the following: the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit; the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is not expected to be transmitted in the first time domain unit.

[0167] In some embodiments, predefined rules are used to indicate at least one of the following:

[0168] When the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0169] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be sent in the first time domain unit.

[0170] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is transmitted in the first time domain unit.

[0171] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0172] In some embodiments, transmitting the multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0173] When the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0174] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be sent in the first time domain unit.

[0175] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is transmitted in the first time domain unit.

[0176] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0177] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0178] In some embodiments, predefined rules are used to indicate at least one of the following:

[0179] When the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0180] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0181] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is transmitted in the first time domain unit.

[0182] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0183] In some embodiments, transmitting the physical uplink shared channel of multi-slot transport blocks according to predefined rules includes at least one of the following:

[0184] When the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0185] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0186] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is transmitted in the first time domain unit.

[0187] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0188] In some embodiments, the terminal can determine, according to predefined rules, the first frequency domain interval between the first frequency domain resource corresponding to TBoMSPUSCH and the broadcast message in the conflicting time domain unit.

[0189] For example, when the first frequency domain interval is less than the frequency domain interval threshold, the terminal does not expect to send TBoMS PUSCH in conflicting time domain units.

[0190] For example, when the first frequency domain interval is greater than or equal to the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit, and the terminal can send TBoMS PUSCH in the conflicting time domain unit.

[0191] In some embodiments, the terminal can determine, according to predefined rules, the first frequency domain interval between the uplink subband and the broadcast message in the conflicting time domain unit.

[0192] For example, when the first frequency domain interval is less than the frequency domain interval threshold, the terminal does not expect to send TBoMS PUSCH in conflicting time domain units.

[0193] For example, when the first frequency domain interval is greater than or equal to the frequency domain interval threshold, the terminal can send TBoMS PUSCH in conflicting time domain units.

[0194] In step S202, the network device receives the multi-timeslot transport block physical uplink shared channel sent by the terminal according to predefined rules.

[0195] In some embodiments, the physical uplink shared channel is sent by the terminal.

[0196] In some embodiments, predefined rules are used to indicate how the physical uplink shared channel is handled.

[0197] In some embodiments, the physical uplink shared channel is transmitted by the terminal in a manner based on multi-timeslot transport block processing.

[0198] In some embodiments, the network device determines, according to predefined rules, how to handle the physical uplink shared channel when the physical uplink shared channel and broadcast messages conflict in a time-domain unit configured with subbands.

[0199] In some embodiments, the network device receives the multi-timeslot transport block physical uplink shared channel sent by the terminal according to predefined rules, including at least one of the following:

[0200] The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit;

[0201] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the physical uplink shared channel is received in the second time domain unit;

[0202] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0203] In some embodiments, the network device receives the multi-timeslot transport block physical uplink shared channel sent by the terminal according to predefined rules, including at least one of the following:

[0204] The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is received in the time domain unit.

[0205] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, so it is not expected to receive the physical uplink shared channel in the time domain unit.

[0206] In some embodiments, a predefined rule is used to indicate that when the first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, the physical uplink shared channel is transmitted in the second frequency domain resources, wherein the second frequency domain resources are all located within the uplink subband.

[0207] In some embodiments, the network device receives the multi-timeslot transport block physical uplink shared channel sent by the terminal according to predefined rules, including:

[0208] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband; the second frequency domain resources are determined within the uplink subband.

[0209] Receive the physical uplink shared channel in the second frequency domain resources.

[0210] In some embodiments, the network device determines a second frequency domain resource within an uplink subband, including: determining a frequency domain resource within the uplink subband that extends from a first frequency domain position and continues within a first frequency domain range as the second frequency domain resource, wherein the first frequency domain range is determined based on the first frequency domain resource.

[0211] In some embodiments, the network device receiving the multi-timeslot transport block physical uplink shared channel sent by the terminal according to predefined rules further includes at least one of the following:

[0212] The frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit;

[0213] The frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the second time domain unit;

[0214] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0215] In some embodiments, the network device receives the multi-timeslot transport block physical uplink shared channel sent by the terminal according to predefined rules, including at least one of the following:

[0216] The frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit;

[0217] The frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink sub-band, and it is not expected to receive the physical uplink shared channel in the first time domain unit.

[0218] In some embodiments, before determining the second frequency domain resource within the uplink subband, the network device may first determine the relationship between the frequency domain range of the first frequency domain resource and the frequency domain range of the uplink subband.

[0219] In some embodiments, when the frequency range of the first frequency domain resource is greater than the frequency range of the uplink subband, then sufficient frequency domain resources for transmitting TBoMS PUSCH cannot be determined within the uplink subband. In this case, the network device does not need to determine the second frequency domain resource within the uplink subband, which helps to avoid wasting the network device's resources. When the frequency range of the first frequency domain resource is less than or equal to the frequency range of the uplink subband, then sufficient frequency domain resources for receiving TBoMS PUSCH cannot be determined within the uplink subband. Only then will the network device determine the second frequency domain resource within the uplink subband.

[0220] In some embodiments, a predefined rule is used to indicate that when the first frequency domain interval between the uplink subband and / or the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the time domain unit.

[0221] In some embodiments, the network device receives the multi-timeslot transport block physical uplink shared channel sent by the terminal according to predefined rules, including at least one of the following:

[0222] The first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit.

[0223] The first frequency domain interval between the uplink sub-band and the broadcast message is less than the frequency domain interval threshold, and it is not expected to receive the physical uplink shared channel in the first time domain unit.

[0224] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit.

[0225] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be received in the first time domain unit.

[0226] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0227] In some embodiments, the network device receives the multi-timeslot transport block physical uplink shared channel sent by the terminal according to predefined rules, including at least one of the following:

[0228] The first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit.

[0229] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be received in the first time domain unit.

[0230] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit.

[0231] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be received in the first time domain unit.

[0232] In some embodiments, the second time-domain unit is not configured with sub-bands.

[0233] In some embodiments, the network device may determine, according to predefined rules, the first frequency domain interval between the first frequency domain resource corresponding to TBoMS PUSCH and the broadcast message in the conflicting time domain unit.

[0234] For example, when the first frequency domain interval is less than the frequency domain interval threshold, the network device does not expect to receive TBoMS PUSCH in conflicting time domain units.

[0235] For example, when the first frequency domain interval is greater than or equal to the frequency domain interval threshold, the network device can receive TBoMS PUSCH in conflicting time domain units.

[0236] In some embodiments, the network device may determine, according to predefined rules, a first frequency domain spacing between the uplink subband and the broadcast message in a conflicting time domain unit.

[0237] For example, when the first frequency domain interval is less than the frequency domain interval threshold, the network device does not expect to receive TBoMS PUSCH in conflicting time domain units.

[0238] For example, when the first frequency domain interval is greater than or equal to the frequency domain interval threshold, the network device can receive TBoMS PUSCH in conflicting time domain units.

[0239] The uplink communication processing method involved in the embodiments of this disclosure may include at least one of steps S201 to S202. For example, step S201 may be implemented as a standalone embodiment, step S202 may be implemented as a standalone embodiment, and step S201+S202 may be implemented as a standalone embodiment, but is not limited thereto.

[0240] In some embodiments, steps S201 and S202 may be performed in an alternate order or simultaneously.

[0241] In some embodiments, see Figure 2 Other optional implementation methods described before or after the corresponding instruction manual.

[0242] In a first aspect, embodiments of this disclosure propose an uplink communication processing method. Figure 3 This is a schematic flowchart illustrating an uplink communication processing method according to an embodiment of the present disclosure. For example, the uplink communication processing method shown in this embodiment can be executed by a terminal. Figure 3 As shown, the uplink communication processing method may include the following steps:

[0243] In step S301, a multi-timeslot transport block physical uplink shared channel is transmitted according to predefined rules. This multi-timeslot transport block physical uplink shared channel conflicts with broadcast messages in a first time domain unit (e.g., an SBFD time domain unit), where the first time domain unit is configured with sub-bands. For example, the predefined rules can be determined according to protocol agreements.

[0244] It should be noted that, Figure 3 The embodiments shown can be implemented independently or in combination with at least one other embodiment of this disclosure. The specific choice can be made as needed, and this disclosure does not limit the scope of the embodiments.

[0245] In some embodiments, when a TBoMS PUSCH conflicts with a broadcast message from a network device in a certain time domain unit, the terminal may not expect the TBoMS PUSCH to be sent in that time domain unit.

[0246] However, when TBoMS PUSCH conflicts with broadcast messages in a time-domain unit configured with subbands (hereinafter referred to as SBFD time-domain unit), since the SBFD time-domain unit is configured with subbands, the terminal can perform both uplink and downlink communication in the SBFD time-domain unit. If the above implementation method is still used and TBoMSPUSCH is not expected to be sent in this time-domain unit, it will be difficult to apply TBoMS technology in the SBFD time-domain unit, thus limiting the uplink coverage gain brought by SBFD technology.

[0247] In some embodiments, a conflict includes at least one of the following: determining that a conflict is occurring; predicting that a conflict will occur in a future time-domain unit.

[0248] According to embodiments of this disclosure, when a terminal determines that a TBoMS PUSCH conflicts with a broadcast message in an SBFD time-domain unit, the terminal may not default to not expecting to send the TBoMS PUSCH in that SBFD time-domain unit. Instead, it can determine how to handle the TBoMS PUSCH according to predefined rules. For example, it may send the TBoMS PUSCH in the SBFD time-domain unit, or it may not send the TBoMS PUSCH in the SBFD time-domain unit. Accordingly, in some SBFD time-domain units, even if the TBoMS PUSCH conflicts with a broadcast message, TBoMS technology can still be applied, which helps to ensure the uplink coverage gain brought by sending the TBoMS PUSCH in the SBFD time slot.

[0249] In some embodiments, the broadcast message includes at least one of the following: a Synchronization Signal Block (SSB); and a Common Search Space (CSS). For example, the Synchronization Signal Block may also be referred to as a Synchronization Broadcast Signal Block, and PBCH stands for Physical Broadcast Channel. For example, the Common Search Space includes, but is not limited to, Type-0 PDCCH CSS, where PDCCH stands for Physical Downlink Control Channel.

[0250] The following embodiments mainly use broadcast messages including SSB as an example to illustrate the technical solutions of this disclosure.

[0251] In some embodiments, the conflict between the physical uplink shared channel and broadcast messages in a time-domain unit configured with subbands includes at least one of the following:

[0252] The first time-domain resource of the physical uplink shared channel in the time-domain unit partially overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0253] The first time-domain resource of the physical uplink shared channel in the time-domain unit completely overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0254] The physical uplink shared channel and broadcast messages reside in the same time domain unit.

[0255] For example, when the first time domain resource of TBoMS PUSCH in the SBFD time slot partially overlaps with the second time domain resource of SSB in the SBFD time slot, the terminal can determine that TBoMS PUSCH and SSB are in conflict in the SBFD time slot, and then determine the processing method for TBoMS PUSCH according to predefined rules.

[0256] For example, when the first time domain resource of TBoMS PUSCH in the SBFD time slot completely overlaps with the second time domain resource of SSB in the SBFD time slot, the terminal can determine that TBoMS PUSCH and SSB are in conflict in the SBFD time slot, and then determine the processing method for TBoMS PUSCH according to the predefined rules.

[0257] For example, when the SBFD time slot where TBoMS PUSCH is located is the same as the SBFD time slot where SSB is located, the terminal can determine that TBoMS PUSCH and SSB are in conflict in the same SBFD time slot, and then determine the processing method for TBoMS PUSCH according to predefined rules.

[0258] The following examples illustrate how a terminal transmits a multi-slot transport block physical uplink shared channel according to predefined rules.

[0259] In some embodiments, predefined rules are used to indicate that: if all the first frequency domain resources of the physical uplink shared channel are within the uplink subband, the physical uplink shared channel is transmitted in the time domain unit; if not all the first frequency domain resources of the physical uplink shared channel are within the uplink subband, the physical uplink shared channel is not expected to be transmitted in the time domain unit.

[0260] In some embodiments, transmitting the multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0261] The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the time domain unit.

[0262] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, so it is not expected to transmit the physical uplink shared channel in the time domain unit.

[0263] In some embodiments, the terminal can determine, according to predefined rules, that when all the first frequency domain resources of the physical uplink shared channel are within the uplink subband, the physical uplink shared channel is transmitted in the time domain unit.

[0264] According to predefined rules, the terminal can determine whether all the first frequency domain resources of the TBoMS PUSCH are within the uplink subband in the conflicting time domain unit. If all the first frequency domain resources of the TBoMS PUSCH are within the uplink subband, the terminal can transmit the TBoMS PUSCH in the conflicting time domain unit; if not all the first frequency domain resources of the TBoMS PUSCH are within the uplink subband, the terminal does not expect to transmit the TBoMS PUSCH in the conflicting time domain unit, and correspondingly, the network device does not expect to receive the TBoMS PUSCH in the conflicting time domain unit.

[0265] Figure 4 This is a schematic diagram of a sub-band according to an embodiment of the present disclosure.

[0266] Taking the example of a subband including an uplink subband and a time domain unit including a time slot, where the network device configures the uplink subband for the terminal in the downlink time slot.

[0267] like Figure 4 As shown, the network device configures the time slot structure for the terminal using Slot Format Indication (SFI) and / or Time Division Duplexing (TDD) Uplink-Downlink configuration as DDFFU, where D represents downlink time slot, U represents uplink time slot, and F represents flexible time slot. That is, in the 5 time slots, slots #0 to #1 are downlink time slots, slots #2 and #3 are flexible time slots, and slot #4 is an uplink time slot.

[0268] In some embodiments, the TDD UL-DL configuration may include a common time-division duplex uplink / downlink configuration (tdd-UL-DL-ConfigurationCommon), or may include a common time-division duplex uplink / downlink configuration (tdd-UL-DL-ConfigurationCommon) and a dedicated time-division duplex uplink / downlink configuration (tdd-UL-DL-ConfigurationDedicated).

[0269] like Figure 4As shown, the network device is configured with uplink subbands in slots #1, #2, and #3. In some embodiments, the entire uplink subband is located in the active UL BWP (BandWidth Part).

[0270] Figure 5 This is a schematic diagram illustrating a conflict according to an embodiment of the present disclosure.

[0271] like Figure 5 As shown, for example, an SSB burst (synchronization signal block cluster) includes 8 SSB candidates, and the network device transmits an SSB on each SSB candidate. The 8 SSB candidates are distributed in slots #0 to #3, with two SSB candidates existing in each time slot.

[0272] The terminal sends TBoMS PUSCH based on the configuration and / or scheduling of the network device. The number of time slots used for sending TBoMS PUSCH is n=4, that is, one TB corresponding to TBoMS PUSCH is sent on 4 time slots, which are slot#1 to slot#4.

[0273] Since the network devices transmitted SSB in slots #1 to #3, and the terminal also needs to transmit TBoMS PUSCH in the uplink subbands of slots #1 to #3, the terminal can determine that there is a conflict between TBoMS PUSCH and SSB in slots #1 to #3.

[0274] In some embodiments, predefined rules are used to indicate that when all the first frequency domain resources of the physical uplink shared channel are within the uplink subband, the physical uplink shared channel is transmitted in the time domain unit.

[0275] exist Figure 5 In the illustrated embodiment, since the first frequency domain resources of TBoMS PUSCH are all located within the uplink subband, the terminal can still transmit TBoMS PUSCH within the uplink subband according to the network device's configuration and / or scheduling. Based on the predefined rules transmitted by the network device, the terminal can determine which time domain units to transmit TBoMS PUSCH in, i.e., slots #1 to #3, are conflicting. Of course, TBoMS PUSCH can also be transmitted in the non-conflicting time domain unit, i.e., slot #4.

[0276] Figure 6A This is a schematic diagram illustrating another conflict according to an embodiment of the present disclosure.

[0277] like Figure 6A As shown, the first frequency domain resources of TBoMS PUSCH in slots #1 to #3 are not all located within the uplink subband. In this case, the terminal cannot successfully send TBoMS PUSCH within the uplink subband according to the network device configuration and / or scheduling.

[0278] Figure 6B This is a schematic diagram illustrating a processing result according to an embodiment of the present disclosure.

[0279] In some embodiments, predefined rules are used to indicate that when all the first frequency domain resources of the physical uplink shared channel are within the uplink subband, the physical uplink shared channel is transmitted in the time domain unit.

[0280] exist Figure 6A In the illustrated embodiment, because the first frequency domain resources of TBoMS PUSCH are not entirely located within the uplink subband, the terminal cannot successfully transmit TBoMSPUSCH in conflicting time slots according to the network device configuration and / or scheduling. Therefore, it can be done as follows: Figure 6B As shown, based on the predefined rules sent by the network device, the terminal can determine that it will not send TBoMS PUSCH in conflicting time domain units, such as slots #1 to #3, but will only send TBoMS PUSCH in slot #4.

[0281] In some embodiments, since TBoMS PUSCH is sent in less than 3 slots, in order to ensure that the number of slots for TBoMS PUSCH is 4, 3 available slots need to be determined after slot #4 to send TBoMS PUSCH.

[0282] Figure 6C This is a schematic diagram illustrating another processing result according to an embodiment of the present disclosure.

[0283] In some embodiments, predefined rules are used to indicate that when all the first frequency domain resources of the physical uplink shared channel are within the uplink subband, the physical uplink shared channel is transmitted in the time domain unit.

[0284] exist Figure 6AIn the illustrated embodiment, because the first frequency domain resources of the TBoMS PUSCH are not entirely located within the uplink subband, the terminal cannot successfully transmit the TBoMS PUSCH according to the network device's configuration and / or scheduling in a downlink time slot configured with a subband (e.g., slot #1). However, in a flexible time slot configured with a subband (e.g., slot #2), the terminal may still successfully transmit the TBoMS PUSCH according to the network device's configuration and / or scheduling (e.g., the frequency domain resources corresponding to the flexible time slot are scheduled as uplink frequency domain resources). Therefore, it can be done as follows... Figure 6C As shown, the terminal can determine that in a conflicting time-domain unit configured with a subband, such as slot #1, TBoMS PUSCH will not be sent. However, in a conflicting time-domain unit configured with a subband, such as slots #2 and #3, TBoMS PUSCH can be sent. Of course, TBoMS PUSCH can also be sent in slot #4.

[0285] In some embodiments, since TBoMS PUSCH is sent in less than one slot, in order to ensure that the number of slots for TBoMS PUSCH is 4, one available slot needs to be determined after slot #4 to send TBoMS PUSCH.

[0286] In some embodiments, when the first frequency domain resources of TBoMS PUSCH are not entirely located within the uplink subband, whether to transmit TBoMS PUSCH in the flexible time domain unit configured with subbands in the conflicting time domain unit, for example, in Figure 6A In this case, according to Figure 6B The example processing still follows Figure 6C Example processing can be instructed by network devices or determined according to protocol agreements.

[0287] In some embodiments, predefined rules are used to indicate that: if all the first frequency domain resources of the physical uplink shared channel are located within the uplink subband, the physical uplink shared channel is transmitted in the first time domain unit; if not all the first frequency domain resources of the physical uplink shared channel are located within the uplink subband, the physical uplink shared channel is transmitted in the second time domain unit.

[0288] In some embodiments, the terminal transmits a multi-slot transport block physical uplink shared channel according to predefined rules, including at least one of the following: the first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit; or the first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the second time domain unit; wherein the second time domain unit and the first time domain unit are different time domain units.

[0289] For example, the second time domain includes the most recently available time domain unit (e.g., a time domain unit that does not conflict with a broadcast message and has uplink frequency domain resources). It may also include time domain units that have not conflicted from the time domain units used to send TBoMS PUSCH.

[0290] For example, according to Figure 6B The embodiment shown transmits TBoMS PUSCH in such a way that only the 5th time slot in a cycle can be used to transmit TBoMS PUSCH. Since TBoMS PUSCH is transmitted in less than 3 time slots, the 3 most recent available time slots after this cycle are the 5th time slots in each of the 3 cycles after this cycle. Therefore, the 5th time slot in each of the 3 cycles after this cycle can be used as the second time domain unit to transmit TBoMS PUSCH, thereby satisfying the requirement of transmitting TBoMS PUSCH in 4 time slots.

[0291] For example, according to Figure 6C The illustrated embodiment transmits TBoMS PUSCH in a manner where time slots 3 through 5 of a cycle can be used for transmission. Since TBoMS PUSCH is transmitted in less than one time slot, the nearest available time slot after this cycle can be determined to be the 3rd time slot in the next cycle. Therefore, the 3rd time slot in the next cycle can be designated as the second time domain unit for transmitting TBoMS PUSCH, thus satisfying the requirement of transmitting TBoMS PUSCH in four time slots. Correspondingly, the network device receives the TBoMS PUSCH transmitted by the terminal in the 3rd time slot of the next cycle.

[0292] In some embodiments, a predefined rule is used to indicate that when the first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, the physical uplink shared channel is transmitted in the second frequency domain resources, wherein the second frequency domain resources are all located within the uplink subband.

[0293] In some embodiments, transmitting the multi-slot transport block physical uplink shared channel according to predefined rules includes:

[0294] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband; the second frequency domain resources are determined within the uplink subband.

[0295] Transmit the physical uplink shared channel in the second frequency domain resources.

[0296] In some embodiments, a predefined rule may instruct the terminal to transmit the physical uplink shared channel in a second frequency domain resource when the first frequency domain resource of the physical uplink shared channel is not entirely located within the uplink subband, wherein the second frequency domain resource is entirely located within the uplink subband.

[0297] According to predefined rules, the terminal can first determine whether all the first frequency domain resources of TBoMS PUSCH are located within the uplink subband in the conflicting time domain unit. If it is determined that all the first frequency domain resources of TBoMS PUSCH are located within the uplink subband, the terminal can determine the second frequency domain resources within the uplink subband and then transmit TBoMS PUSCH in the second frequency domain resources. Correspondingly, the network device can receive TBoMS PUSCH on the second frequency domain resources within the conflicting time domain unit. Therefore, it can be guaranteed that the terminal can successfully transmit TBoMS PUSCH within the uplink subband in the conflicting time domain unit, which helps reduce the transmission latency of TBoMS PUSCH.

[0298] In some embodiments, predefined rules are used to indicate that: if the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, a physical uplink shared channel is transmitted in the first time domain unit; if the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, a physical uplink shared channel is transmitted in the second time domain unit.

[0299] In some embodiments, receiving the physical uplink shared channel of the multi-slot transport block sent by the receiving terminal according to predefined rules further includes at least one of the following: the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is sent in the first time domain unit; the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is sent in the second time domain unit; wherein the second time domain unit and the first time domain unit are different time domain units.

[0300] Before determining the second frequency domain resource within the uplink subband, the terminal can first determine the relationship between the frequency domain range of the first frequency domain resource and the frequency domain range of the uplink subband. If the frequency domain range of the first frequency domain resource is determined to be greater than the frequency domain range of the uplink subband, then sufficient frequency domain resources for transmitting TBoMS PUSCH cannot be determined within the uplink subband. In this case, the terminal does not need to determine the second frequency domain resource within the uplink subband, nor does it need to transmit TBoMS PUSCH in the first time domain unit. Instead, it determines the second time domain unit for transmitting TBoMS PUSCH. If the frequency domain range of the first frequency domain resource is determined to be less than or equal to the frequency domain range of the uplink subband, then sufficient frequency domain resources for transmitting TBoMS PUSCH cannot be determined within the uplink subband. Only then will the terminal determine the second frequency domain resource within the uplink subband.

[0301] The method for determining the second time-domain unit can be referred to in the previous embodiment, and will not be repeated in this embodiment.

[0302] In some embodiments, predefined rules are used to indicate that: if the frequency range of the first frequency domain resource is less than or equal to the frequency range of the uplink sub-band, a physical uplink shared channel is transmitted in the first time domain unit; if the frequency range of the first frequency domain resource is greater than the frequency range of the uplink sub-band, a physical uplink shared channel is not expected to be transmitted in the first time domain unit.

[0303] In some embodiments, transmitting a physical uplink shared channel for a multi-slot transport block according to predefined rules includes at least one of the following: the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and a physical uplink shared channel is transmitted in the first time domain unit; the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, and a physical uplink shared channel is not expected to be transmitted in the first time domain unit.

[0304] Before determining the second frequency domain resource within the uplink subband, the terminal can first determine the relationship between the frequency domain range of the first frequency domain resource and the frequency domain range of the uplink subband. If the frequency domain range of the first frequency domain resource is determined to be greater than the frequency domain range of the uplink subband, then sufficient frequency domain resources for transmitting TBoMS PUSCH cannot be determined within the uplink subband. In this case, the terminal does not need to determine the second frequency domain resource within the uplink subband, nor does it need to transmit TBoMS PUSCH in the first time domain unit. Instead, it determines the second time domain unit for transmitting TBoMS PUSCH. If the frequency domain range of the first frequency domain resource is determined to be less than or equal to the frequency domain range of the uplink subband, then sufficient frequency domain resources for transmitting TBoMS PUSCH cannot be determined within the uplink subband. Only then will the terminal determine the second frequency domain resource within the uplink subband.

[0305] In some embodiments, determining a second frequency domain resource within an uplink subband includes:

[0306] Within the uplink subband, the frequency domain resources that extend from the first frequency domain position to the first frequency domain range are defined as the second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

[0307] The terminal determines the second frequency domain resource within the uplink subband, including its start point and duration. The start point can be a first frequency domain location within the uplink subband. This first frequency domain location can be configured or indicated by the network device, or it can be determined based on protocol agreements. For example, the first frequency domain location can be the start or end point of the corresponding frequency domain resource in the uplink subband. The duration of the second frequency domain resource can be a range within the first frequency domain. This range can be determined based on the first frequency domain resource in the SFBD time domain unit of the TBoMS PUSCH. For example, the first frequency domain range can be the same as the frequency domain range corresponding to the first frequency domain resource.

[0308] Figure 7This is a schematic diagram illustrating a processing result according to an embodiment of the present disclosure.

[0309] In some embodiments, a predefined rule is used to indicate that when the first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, the physical uplink shared channel is transmitted in the second frequency domain resources, wherein the second frequency domain resources are all located within the uplink subband.

[0310] exist Figure 6A In the illustrated embodiment, because the first frequency domain resources of TBoMS PUSCH are not entirely located within the uplink subband, the terminal cannot successfully transmit TBoMSPUSCH in conflicting time slots according to the network device configuration and / or scheduling. Therefore, it can be done as follows: Figure 7 As shown, based on predefined rules sent by the network device, the terminal can determine a second frequency domain resource within conflicting time domain units, such as the uplink sub-bands from slot #1 to slot #3. The starting point of the second frequency domain resource is the starting point of the corresponding frequency domain resource in the uplink sub-band, and the first frequency domain range is the same as the frequency domain range corresponding to the first frequency domain resource. The terminal can then send TBoMS PUSCH within the second frequency domain resource.

[0311] For example, if the uplink subband corresponds to a frequency range of RB (Resource Block, RB)#20 to RB#40, and the first frequency resource corresponding to TBoMSPUSCH is RB#35 to RB#45, the terminal can determine that the first frequency resource is not entirely within the uplink subband and is smaller than the frequency range corresponding to the uplink subband. Therefore, the terminal can determine a second frequency resource RB#20 to RB#30 within RB#20 to RB#40, starting from RB#20 and lasting for 10 RBs. Then, in slots #1 to #3, the terminal can send TBoMS PUSCH from RB#20 to RB#30. Correspondingly, the network device can receive the TBoMS PUSCH sent by the terminal from RB#20 to RB#30 in slots #1 to #3, and in slot #4, it will still receive the TBoMS PUSCH sent by the terminal from RB#20 to RB#30.

[0312] In some embodiments, predefined rules are used to indicate at least one of the following:

[0313] If the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0314] If the first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, it is not expected to send the physical uplink shared channel in the first time domain unit.

[0315] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0316] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0317] In some embodiments, transmitting the multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0318] If the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0319] If the first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, it is not expected to send the physical uplink shared channel in the first time domain unit.

[0320] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0321] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0322] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0323] For example, based on predefined rules, the terminal can determine the first frequency domain interval between the first frequency domain resource corresponding to TBoMS PUSCH and the broadcast message in the conflicting time domain unit.

[0324] When the first frequency domain interval is less than the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit and receives a TBoMS PUSCH in the time domain unit. The frequency domain interference between the TBoMS PUSCH and the broadcast message is relatively large, which has a significant impact on the communication quality. Therefore, the terminal can determine the second time domain unit and send the TBoMS PUSCH in the second time domain unit, which is beneficial to ensuring relatively good communication quality.

[0325] When the first frequency domain interval is greater than or equal to the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit and receives a TBoMS PUSCH in the same time domain unit. The frequency domain interference between the TBoMS PUSCH and the broadcast message is relatively small and has little impact on communication quality. Therefore, the terminal can send a TBoMS PUSCH in the conflicting time domain unit.

[0326] For example, based on predefined rules, the terminal can determine the first frequency domain interval between the uplink subband and the broadcast message in the conflicting time domain unit.

[0327] When the first frequency domain interval is less than the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit, and receives TBoMS PUSCH and sends a broadcast message in the uplink subband of the time domain unit. The frequency domain interference between TBoMS PUSCH and broadcast message is relatively large, which has a significant impact on communication quality. Therefore, the terminal can determine the second time domain unit and send TBoMS PUSCH in the second time domain unit, which is beneficial to ensuring relatively good communication quality.

[0328] When the first frequency domain interval is greater than or equal to the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit and receives TBoMS PUSCH in the uplink subband of the time domain unit. The frequency domain interference between TBoMS PUSCH and broadcast message is relatively small and has little impact on communication quality. Therefore, the terminal can send TBoMS PUSCH in the conflicting time domain unit.

[0329] The method for determining the second time-domain unit can be referred to in the previous embodiment, and will not be repeated in this embodiment.

[0330] In some embodiments, predefined rules are used to indicate at least one of the following:

[0331] If the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0332] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit;

[0333] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0334] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0335] In some embodiments, transmitting the multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0336] If the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0337] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit;

[0338] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0339] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0340] For example, based on predefined rules, the terminal can determine the first frequency domain interval between the first frequency domain resource corresponding to TBoMS PUSCH and the broadcast message in the conflicting time domain unit.

[0341] When the first frequency domain interval is less than the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit and receives TBoMS PUSCH in the time domain unit. The frequency domain interference between TBoMS PUSCH and broadcast message is relatively large, which has a significant impact on communication quality. Therefore, the terminal does not want to send TBoMS PUSCH in the conflicting time domain unit, which is conducive to ensuring relatively good communication quality.

[0342] When the first frequency domain interval is greater than or equal to the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit and receives a TBoMS PUSCH in the same time domain unit. The frequency domain interference between the TBoMS PUSCH and the broadcast message is relatively small and has little impact on communication quality. Therefore, the terminal can send a TBoMS PUSCH in the conflicting time domain unit.

[0343] For example, based on predefined rules, the terminal can determine the first frequency domain interval between the uplink subband and the broadcast message in the conflicting time domain unit.

[0344] When the first frequency domain interval is less than the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit, and receives TBoMS PUSCH and sends a broadcast message in the uplink subband of the time domain unit. The frequency domain interference between TBoMS PUSCH and broadcast message is relatively large, which has a significant impact on communication quality. Therefore, the terminal does not want to send TBoMS PUSCH in the conflicting time domain unit, which is conducive to ensuring relatively good communication quality.

[0345] When the first frequency domain interval is greater than or equal to the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit and receives TBoMS PUSCH in the uplink subband of the time domain unit. The frequency domain interference between TBoMS PUSCH and broadcast message is relatively small and has little impact on communication quality. Therefore, the terminal can send TBoMS PUSCH in the conflicting time domain unit.

[0346] In some embodiments, since the number of time domain units occupied by TBoMS PUSCH is fixed, if the terminal does not expect to send TBoMS PUSCH when it is in a conflicting time domain unit, then the nearest available time domain unit (e.g., a time domain unit that does not conflict with the broadcast message and has uplink frequency domain resources) can be determined to send TBoMS PUSCH to make up for the number of time domain units occupied by TBoMSPUSCH.

[0347] For example, if the number of time domain units occupied by TBoMS PUSCH is n, and the terminal does not expect to send TBoMS PUSCH in m (e.g., m is an integer less than or equal to n) conflicting time domain units during the current TDD cycle, the terminal needs to determine the m nearest available time domain units after the current TDD cycle to send TBoMS PUSCH, ensuring that the number of time domain units occupied by TBoMS PUSCH is n. Correspondingly, the network device does not expect to receive TBoMS PUSCH sent by the terminal in m conflicting time domain units, but instead determines the m nearest available time domain units after the current TDD cycle to receive TBoMS PUSCH sent by the terminal.

[0348] For example in Figure 6A In the embodiment shown, one TDD cycle includes 5 time slots.

[0349] When according to Figure 6B In the illustrated embodiment, when transmitting TBoMS PUSCH, only the 5th time slot in a cycle is available for transmission. Since TBoMS PUSCH is transmitted in fewer than 3 time slots, the three most recent available time slots after this cycle are the 5th time slots in each of the next 3 cycles. Therefore, TBoMS PUSCH can be transmitted in the 5th time slot of each of the next 3 cycles, thus satisfying the requirement of transmitting TBoMS PUSCH in 4 time slots. Correspondingly, the network device receives the TBoMS PUSCH transmitted by the terminal in the 5th time slot of each of the next 3 cycles.

[0350] When according to Figure 6CWhen transmitting TBoMS PUSCH in the illustrated embodiment, slots 3 through 5 of a cycle can be used to transmit TBoMS PUSCH. Since TBoMS PUSCH is transmitted in less than one slot, the nearest available slot after this cycle can be determined to be the 3rd slot of the next cycle. Therefore, TBoMS PUSCH can be transmitted in the 3rd slot of the next cycle, thus satisfying the requirement of transmitting TBoMS PUSCH in 4 slots. Correspondingly, the network device receives the TBoMS PUSCH transmitted by the terminal in the 3rd slot of the next cycle.

[0351] Secondly, embodiments of this disclosure propose an uplink communication processing method. Figure 8 This is a schematic flowchart illustrating an uplink communication processing method according to an embodiment of the present disclosure. For example, the uplink communication processing method shown in this embodiment can be executed by a network device. Figure 8 As shown, the uplink communication processing method may include the following steps:

[0352] In step S801, the multi-timeslot transport block physical uplink shared channel sent by the receiving terminal is received according to predefined rules. The multi-timeslot transport block physical uplink shared channel conflicts with broadcast messages in the first time domain unit, which is configured with sub-bands. For example, the predefined rules can be determined by the root protocol.

[0353] It should be noted that, Figure 8 The embodiments shown can be implemented independently or in combination with at least one other embodiment of this disclosure. The specific choice can be made as needed, and this disclosure does not limit the scope of the embodiments.

[0354] In some embodiments, when a TBoMS PUSCH conflicts with a broadcast message from a network device in a certain time domain unit, the terminal may not expect the TBoMS PUSCH to be sent in that time domain unit.

[0355] However, when TBoMS PUSCH conflicts with broadcast messages in a time-domain unit configured with subbands (hereinafter referred to as SBFD time-domain unit), since the SBFD time-domain unit is configured with subbands, the terminal can perform both uplink and downlink communication in the SBFD time-domain unit. If the above implementation method is still used and TBoMSPUSCH is not expected to be sent in this time-domain unit, it will be difficult to apply TBoMS technology in the SBFD time-domain unit, thus limiting the uplink coverage gain brought by SBFD technology.

[0356] In some embodiments, a conflict includes at least one of the following: determining that a conflict is occurring; predicting that a conflict will occur in a future time-domain unit.

[0357] According to embodiments of this disclosure, a network device can determine, based on predefined rules, how to handle a TBoMS PUSCH when it conflicts with a broadcast message in an SBFD time-domain unit. Accordingly, the network device may not default to not expecting to receive TBoMS PUSCH sent by a terminal in that SBFD time-domain unit, but can determine the handling method based on predefined rules. For example, it may receive a TBoMS PUSCH sent by a terminal in the SBFD time-domain unit, or it may not expect to receive a TBoMS PUSCH sent by a terminal in the SBFD time-domain unit. Therefore, in some SBFD time-domain units, even if a TBoMS PUSCH conflicts with a broadcast message, TBoMS technology can still be applied, which helps ensure the uplink coverage gain brought by receiving TBoMS PUSCH in the SBFD time slot.

[0358] In some embodiments, a broadcast message includes at least one of the following: a synchronization signal block (SSB); and a common search space (CSS). For example, a synchronization signal block may also be referred to as a synchronization broadcast signal block. For example, a common search space includes, but is not limited to, a Type-0 PDCCH CSS.

[0359] In some embodiments, the conflict between the physical uplink shared channel and broadcast messages in a time-domain unit configured with subbands includes at least one of the following:

[0360] The first time-domain resource of the physical uplink shared channel in the time-domain unit partially overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0361] The first time-domain resource of the physical uplink shared channel in the time-domain unit completely overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0362] The physical uplink shared channel and broadcast messages reside in the same time domain unit.

[0363] For example, when the first time domain resource of TBoMS PUSCH in the SBFD time slot partially overlaps with the second time domain resource of SSB in the SBFD time slot, the network device can determine that TBoMS PUSCH and SSB are in conflict in the SBFD time slot, and then determine the processing method for TBoMS PUSCH according to predefined rules.

[0364] For example, when the first time domain resource of TBoMS PUSCH in the SBFD time slot completely overlaps with the second time domain resource of SSB in the SBFD time slot, the network device can determine that TBoMS PUSCH and SSB are in conflict in the SBFD time slot, and then determine the processing method for TBoMS PUSCH according to predefined rules.

[0365] For example, when the SBFD time slot where TBoMS PUSCH is located is the same as the SBFD time slot where SSB is located, the network device can determine that TBoMS PUSCH and SSB are in conflict in the same SBFD time slot, and then determine the processing method for TBoMS PUSCH according to predefined rules.

[0366] In some embodiments, predefined rules are used to indicate that: if all the first frequency domain resources of the physical uplink shared channel are located within the uplink subband, the physical uplink shared channel is received in the time domain unit; if not all the first frequency domain resources of the physical uplink shared channel are located within the uplink subband, the physical uplink shared channel is not expected to be received in the time domain unit.

[0367] In some embodiments, receiving a multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0368] The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is received in the time domain unit.

[0369] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, so it is not expected to receive the physical uplink shared channel in the time domain unit.

[0370] In some embodiments, the network device may determine, according to predefined rules, that when all the first frequency domain resources of the physical uplink shared channel are within the uplink subband, the physical uplink shared channel will be received in the time domain unit.

[0371] According to predefined rules, network devices can determine whether the first frequency domain resources of TBoMS PUSCH are all within the uplink subband in a conflicting time domain unit. When the first frequency domain resources of TBoMS PUSCH are all within the uplink subband, the network device can receive the TBoMS PUSCH sent by the terminal in the conflicting time domain unit; when the first frequency domain resources of TBoMS PUSCH are not all within the uplink subband, the network device does not expect to receive the TBoMS PUSCH sent by the terminal in the conflicting time domain unit, and correspondingly, the terminal does not expect to send TBoMS PUSCH in the conflicting time domain unit.

[0372] like Figure 5 As shown, for example, an SSB burst (synchronization signal block cluster) includes 8 SSB candidates, and the network device transmits an SSB on each SSB candidate. The 8 SSB candidates are distributed in slots #0 to #3, with two SSB candidates existing in each time slot.

[0373] The terminal sends TBoMS PUSCH based on the configuration and / or scheduling of the network device. The number of time slots used for sending TBoMS PUSCH is n=4, that is, one TB corresponding to TBoMS PUSCH is sent on 4 time slots, which are slot#1 to slot#4.

[0374] Since the network device transmitted SSB in slots #1 to #3, and the network device also needs to receive TBoMS PUSCH in the uplink subbands of slots #1 to #3, the network device can determine that there is a conflict between TBoMS PUSCH and SSB in slots #1 to #3.

[0375] In some embodiments, predefined rules are used to indicate that when all the first frequency domain resources of the physical uplink shared channel are within the uplink subband, the physical uplink shared channel is received in the time domain unit.

[0376] exist Figure 5 In the illustrated embodiment, since the first frequency domain resources of the TBoMS PUSCH are all located within the uplink subband, the network device can still receive the TBoMS PUSCH sent by the terminal within the uplink subband according to the terminal configuration and / or scheduling. The network device can determine, according to predefined rules, to receive the TBoMS PUSCH sent by the terminal in conflicting time domain units, i.e., slots #1 to #3. Of course, it can also receive the TBoMS PUSCH sent by the terminal in non-conflicting time domain units, i.e., slot #4. Correspondingly, the terminal can send the TBoMS PUSCH in slots #1 to #4.

[0377] exist Figure 6A In the illustrated embodiment, because the first frequency domain resources of the TBoMS PUSCH are not entirely located within the uplink subband, the network device cannot successfully receive the TBoMS PUSCH sent by the terminal in conflicting time slots based on the terminal configuration and / or scheduling. Therefore, it can be done as follows... Figure 6B As shown, network devices can determine, based on predefined rules, that in conflicting time domain units, such as slots #1 to #3, they will not receive TBoMS PUSCH sent by the terminal, but will only receive TBoMS PUSCH sent by the terminal in slot #4. Correspondingly, the terminal may also choose not to expect TBoMS PUSCH to be sent in slots #1 to #3, but will instead send TBoMS PUSCH in slot #4.

[0378] In some embodiments, since TBoMS PUSCH is received in at least 3 slots, in order to ensure that the number of slots for TBoMS PUSCH is 4, the network device needs to determine 3 available slots after slot #4 to receive TBoMS PUSCH. Correspondingly, the terminal can also send TBoMS PUSCH in the 3 available slots after slot #4.

[0379] exist Figure 6A In the illustrated embodiment, since the first frequency domain resources of the TBoMS PUSCH are not entirely located within the uplink subband, the network device cannot successfully receive the TBoMS PUSCH sent by the terminal in a downlink time slot (e.g., slot #1) configured with a subband, based on the terminal configuration and / or scheduling. However, in a flexible time slot (e.g., slot #2) configured with a subband, the network device may still successfully receive the TBoMS PUSCH sent by the terminal based on the terminal configuration and / or scheduling (e.g., the frequency domain resources corresponding to the flexible time slot are scheduled as uplink frequency domain resources). Therefore, it is possible to... Figure 6C As shown, the network device can determine that in a conflicting time-domain unit configured with subbands, such as slot #1, it will not receive TBoMS PUSCH sent by the terminal. However, in a conflicting time-domain unit configured with subbands, such as slots #2 and #3, it can receive TBoMS PUSCH sent by the terminal. Of course, it can also receive TBoMS PUSCH sent by the terminal in slot #4. Correspondingly, the terminal in slot #1 may not expect TBoMS PUSCH to be sent, but may instead expect it to be sent in slots #2 through #4.

[0380] In some embodiments, since TBoMS PUSCH is received in at least one slot, to ensure that the number of slots for TBoMS PUSCH is 4, the network device needs to determine one available slot after slot #4 to receive TBoMS PUSCH. Correspondingly, the terminal can also send TBoMS PUSCH in one available slot after slot #4.

[0381] In some embodiments, when the first frequency domain resources of TBoMS PUSCH are not entirely located within the uplink subband, whether to transmit TBoMS PUSCH in the flexible time domain unit configured with subbands in the conflicting time domain unit, for example, in Figure 6A In this case, according to Figure 6B The example processing still follows Figure 6C The example processing can be determined by the network device and instructed to the terminal, or it can be determined according to the protocol.

[0382] In some embodiments, predefined rules are used to indicate that: if all the first frequency domain resources of the physical uplink shared channel are located within the uplink subband, the physical uplink shared channel is received in the first time domain unit; if not all the first frequency domain resources of the physical uplink shared channel are located within the uplink subband, the physical uplink shared channel is received in the second time domain unit.

[0383] In some embodiments, the network device receives a multi-slot transport block physical uplink shared channel according to predefined rules, including at least one of the following: the first frequency domain resources of the physical uplink shared channel are all located within the uplink subband, and the physical uplink shared channel is received in a first time domain unit; or the first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, and the physical uplink shared channel is received in a second time domain unit; wherein the second time domain unit and the first time domain unit are different time domain units.

[0384] For example, the second time domain includes the most recently available time domain unit (e.g., a time domain unit that does not conflict with a broadcast message and has uplink frequency domain resources). It may also include time domain units that have not conflicted from the time domain units used to send TBoMS PUSCH.

[0385] For example, according to Figure 6B The embodiment shown transmits TBoMS PUSCH in such a way that only the 5th time slot in a cycle can be used to transmit TBoMS PUSCH. Since TBoMS PUSCH is transmitted in less than 3 time slots, the 3 most recent available time slots after this cycle are the 5th time slots in each of the 3 cycles after this cycle. Therefore, the 5th time slot in each of the 3 cycles after this cycle can be used as the second time domain unit to transmit TBoMS PUSCH, thereby satisfying the requirement of transmitting TBoMS PUSCH in 4 time slots.

[0386] For example, according to Figure 6C The illustrated embodiment transmits TBoMS PUSCH in a manner where time slots 3 through 5 of a cycle can be used to transmit TBoMS PUSCH. Since TBoMS PUSCH is transmitted in less than one time slot, the nearest available time slot after this cycle can be determined to be the 3rd time slot in the next cycle. Therefore, the 3rd time slot in the next cycle can be designated as the second time domain unit for transmitting TBoMS PUSCH, thus satisfying the requirement of transmitting TBoMS PUSCH in 4 time slots. Correspondingly, the terminal transmits TBoMS PUSCH in the 3rd time slot of the next cycle.

[0387] In some embodiments, a predefined rule is used to indicate that when the first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, the physical uplink shared channel is received in the second frequency domain resources, wherein the second frequency domain resources are all located within the uplink subband.

[0388] In some embodiments, receiving a multi-slot transport block physical uplink shared channel according to predefined rules includes: the first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, and a second frequency domain resource is determined within the uplink subband; the physical uplink shared channel is received in the second frequency domain resources.

[0389] In some embodiments, the network device receives the physical uplink shared channel in the second frequency domain resources according to predefined rules when the first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, wherein the second frequency domain resources are all located within the uplink subband.

[0390] According to predefined rules, network devices can determine whether the first frequency domain resources of TBoMS PUSCH are entirely within the uplink subband in a conflicting time domain unit. If the first frequency domain resources of TBoMS PUSCH are entirely within the uplink subband, the network device can determine the second frequency domain resources within the uplink subband, and then receive the TBoMS PUSCH sent by the terminal in the second frequency domain resources. Correspondingly, the terminal can send TBoMS PUSCH on the second frequency domain resources in a conflicting time domain unit. Therefore, it can be ensured that the network device can successfully receive the TBoMS PUSCH sent by the terminal within the uplink subband in a conflicting time domain unit, which helps reduce the latency of TBoMS PUSCH reception.

[0391] In some embodiments, predefined rules are used to indicate that: if the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, a physical uplink shared channel is received in the first time domain unit; if the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, a physical uplink shared channel is received in the second time domain unit.

[0392] In some embodiments, receiving a physical uplink shared channel for a multi-slot transport block sent by a terminal according to predefined rules further includes at least one of the following: the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in a first time domain unit; the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in a second time domain unit; wherein the second time domain unit and the first time domain unit are different time domain units.

[0393] Before determining the second frequency domain resource within the uplink subband, the network device can first determine the relationship between the frequency domain range of the first frequency domain resource and the frequency domain range of the uplink subband. If the frequency domain range of the first frequency domain resource is determined to be greater than the frequency domain range of the uplink subband, then sufficient frequency domain resources for receiving TBoMS PUSCH cannot be determined within the uplink subband. In this case, the network device does not need to determine the second frequency domain resource within the uplink subband, nor does it need to receive TBoMS PUSCH in the first time domain unit. Instead, it determines the second time domain unit for transmitting TBoMS PUSCH. Conversely, if the frequency domain range of the first frequency domain resource is determined to be less than or equal to the frequency domain range of the uplink subband, then sufficient frequency domain resources for receiving TBoMS PUSCH cannot be determined within the uplink subband, and only then will the network device determine the second frequency domain resource within the uplink subband.

[0394] The method for determining the second time-domain unit can be referred to in the previous embodiment, and will not be repeated in this embodiment.

[0395] In some embodiments, predefined rules are used to indicate that: if the frequency range of the first frequency domain resource is less than or equal to the frequency range of the uplink sub-band, a physical uplink shared channel is received in the first time domain unit; if the frequency range of the first frequency domain resource is greater than the frequency range of the uplink sub-band, a physical uplink shared channel is not expected to be received in the first time domain unit.

[0396] In some embodiments, transmitting a multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following: the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit; the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is not expected to be received in the first time domain unit.

[0397] Before determining the second frequency domain resource within the uplink subband, the network device can first determine the relationship between the frequency domain range of the first frequency domain resource and the frequency domain range of the uplink subband. If the frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink subband, then sufficient frequency domain resources for the TBoMS PUSCH transmitted by the receiving terminal cannot be determined within the uplink subband. In this case, the network device does not need to determine the second frequency domain resource within the uplink subband, thus avoiding wasting network device resources. Conversely, if the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink subband, then sufficient frequency domain resources for the TBoMS PUSCH transmitted by the receiving terminal cannot be determined within the uplink subband. Only then will the network device determine the second frequency domain resource within the uplink subband.

[0398] In some embodiments, determining a second frequency domain resource within an uplink subband includes: determining a frequency domain resource within an uplink subband that extends from a first frequency domain position and continues within a first frequency domain range as a second frequency domain resource, wherein the first frequency domain range is determined based on the first frequency domain resource.

[0399] exist Figure 6A In the illustrated embodiment, because the first frequency domain resources of the TBoMS PUSCH are not entirely located within the uplink subband, the network device cannot successfully receive the TBoMS PUSCH sent by the terminal in conflicting time slots according to the terminal configuration and / or scheduling. Therefore, it can be done as follows... Figure 7 As shown, the network device can predefine rules to determine a second frequency domain resource within conflicting time domain units, such as the uplink sub-bands from slot #1 to slot #3. The starting point of the second frequency domain resource is the starting point of the corresponding frequency domain resource in the uplink sub-band, and the first frequency domain range is the same as the frequency domain range corresponding to the first frequency domain resource. Furthermore, the network device can receive TBoMS PUSCH sent by the terminal within the second frequency domain resource.

[0400] For example, if the uplink subband corresponds to a frequency range of RB (Resource Block, RB)#20 to RB#40, and the first frequency domain resource corresponding to TBoMSPUSCH is RB#35 to RB#45, the network device can determine that the first frequency domain resource is not entirely within the uplink subband and is smaller than the frequency range corresponding to the uplink subband. Therefore, the network device can determine a second frequency domain resource RB#20 to RB#30 within RB#20 to RB#40, starting from RB#20 and lasting for 10 RBs. Then, in slots #1 to #3, the network device receives the TBoMS PUSCH sent by the terminal from RB#20 to RB#30. Correspondingly, the terminal can send TBoMS PUSCH from RB#20 to RB#30 in slots #1 to #3, and still send TBoMS PUSCH from RB#20 to RB#30 in slot #4.

[0401] In some embodiments, predefined rules are used to indicate at least one of the following:

[0402] If the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0403] If the first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, it is not expected to send the physical uplink shared channel in the first time domain unit.

[0404] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0405] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0406] In some embodiments, receiving a multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0407] If the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0408] If the first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, it is not expected to send the physical uplink shared channel in the first time domain unit.

[0409] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0410] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0411] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0412] For example, network devices can determine the first frequency domain interval between the first frequency domain resource corresponding to TBoMS PUSCH and the broadcast message in a conflicting time domain unit based on predefined rules.

[0413] When the first frequency domain interval is less than the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit and receives a TBoMS PUSCH in the time domain unit. The frequency domain interference between the TBoMS PUSCH and the broadcast message is relatively large, which has a significant impact on the communication quality. Therefore, the network device can determine the second time domain unit and receive the TBoMS PUSCH in the second time domain unit, which is beneficial to ensuring relatively good communication quality.

[0414] When the first frequency domain interval is greater than or equal to the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit and receives TBoMS PUSCH in the time domain unit. The frequency domain interference between TBoMS PUSCH and the broadcast message is relatively small and has little impact on communication quality. Therefore, the network device can receive TBoMSPUSCH in the conflicting time domain unit.

[0415] For example, network devices can determine the first frequency domain interval between the uplink subband and the broadcast message in a conflicting time domain unit based on predefined rules.

[0416] When the first frequency domain interval is less than the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit, and receives TBoMS PUSCH and sends a broadcast message in the uplink subband of the time domain unit. The frequency domain interference between TBoMS PUSCH and broadcast message is relatively large, which has a significant impact on communication quality. Therefore, the network device can determine the second time domain unit and receive TBoMS PUSCH in the second time domain unit, which is beneficial to ensuring relatively good communication quality.

[0417] When the first frequency domain interval is greater than or equal to the frequency domain interval threshold, the network device sends a broadcast message in the conflicting time domain unit and receives TBoMS PUSCH in the uplink subband of the time domain unit. The frequency domain interference between TBoMS PUSCH and the broadcast message is relatively small and has little impact on communication quality. Therefore, the network device can receive TBoMS PUSCH in the conflicting time domain unit.

[0418] The method for determining the second time-domain unit can be referred to in the previous embodiment, and will not be repeated in this embodiment.

[0419] In some embodiments, predefined rules are used to indicate at least one of the following:

[0420] If the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0421] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit;

[0422] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0423] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0424] In some embodiments, transmitting the multi-slot transport block physical uplink shared channel according to predefined rules includes at least one of the following:

[0425] If the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0426] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit;

[0427] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0428] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0429] For example, based on predefined rules, network devices can first determine the first frequency domain interval between the first frequency domain resource corresponding to TBoMS PUSCH and the broadcast message in the conflicting time domain unit.

[0430] When the first frequency domain interval is less than the frequency domain interval threshold, since the network device sends broadcast messages in the conflicting time domain unit and receives TBoMS PUSCH in the conflicting time domain unit, the frequency domain interference between TBoMS PUSCH and broadcast messages is relatively large, which has a significant impact on communication quality. Therefore, the network device does not want to receive TBoMS PUSCH sent by the terminal in the conflicting time domain unit, which is beneficial to ensuring relatively good communication quality. The terminal does not send TBoMSPUSCH in the conflicting time domain unit.

[0431] When the first frequency domain interval is greater than or equal to the frequency domain interval threshold, since the network device sends broadcast messages in the conflicting time domain unit and receives TBoMS PUSCH in the conflicting time domain unit, the frequency domain interference between TBoMS PUSCH and broadcast messages is relatively small, and the impact on communication quality is small. Therefore, the network device can receive TBoMS PUSCH sent by the terminal in the time domain unit, and the terminal can also send TBoMS PUSCH in the conflicting time domain unit.

[0432] For example, network devices can determine the first frequency domain interval between the uplink subband and the broadcast message in the conflicting time domain unit based on predefined rules.

[0433] When the first frequency domain interval is less than the frequency domain interval threshold, since the network device sends broadcast messages in the conflicting time domain unit, and receives TBoMS PUSCH and sends broadcast messages in the uplink subband of the time domain unit, the frequency domain interference between TBoMS PUSCH and broadcast messages is relatively large, which has a significant impact on communication quality. Therefore, the network device does not want to receive TBoMS PUSCH sent by the terminal in the conflicting time domain unit, which is conducive to ensuring relatively good communication quality. The terminal does not expect to send TBoMS PUSCH in the conflicting time domain unit.

[0434] When the first frequency domain interval is greater than or equal to the frequency domain interval threshold, since the network device sends broadcast messages in the conflicting time domain unit and receives TBoMS PUSCH in the uplink subband of the time domain unit, the frequency domain interference between TBoMS PUSCH and broadcast messages is relatively small and has little impact on communication quality. Therefore, the network device can receive TBoMS PUSCH sent by the terminal in the conflicting time domain unit, and the terminal can also send TBoMS PUSCH in the conflicting time domain unit.

[0435] In some embodiments, since the number of time domain units occupied by TBoMS PUSCH is fixed, and the network device does not expect to receive TBoMS PUSCH when it is in a conflicting time domain unit, the nearest available time domain unit (e.g., a time domain unit that does not conflict with the broadcast message and has uplink frequency domain resources) can be determined to receive TBoMS PUSCH to make up for the number of time domain units occupied by TBoMS PUSCH.

[0436] For example, if the number of time domain units occupied by TBoMS PUSCH is n, and the network device does not expect to receive TBoMS PUSCH in m (e.g., m is an integer less than or equal to n) conflicting time domain units during the current TDD cycle, the network device needs to determine the m nearest available time domain units after the current TDD cycle to receive TBoMS PUSCH, ensuring that the number of time domain units occupied by TBoMS PUSCH is n. Correspondingly, the terminal does not expect to send TBoMS PUSCH in m conflicting time domain units, but instead determines the m nearest available time domain units after the current TDD cycle to send TBoMS PUSCH.

[0437] For example in Figure 6A In the embodiment shown, one TDD cycle includes 5 time slots.

[0438] When according to Figure 6B When transmitting TBoMS PUSCH in the illustrated embodiment, only the 5th time slot in a cycle is available for receiving TBoMS PUSCH. Since TBoMS PUSCH is received in at least 3 time slots, the 3 most recent available time slots after this cycle are the 5th time slots in each of the next 3 cycles. Therefore, the network device can receive TBoMS PUSCH in the 5th time slot of each of the next 3 cycles, thus satisfying the requirement of receiving TBoMSPUSCH in 4 time slots. Correspondingly, the terminal transmits TBoMSPUSCH in the 5th time slot of each of the next 3 cycles.

[0439] When according to Figure 6CWhen transmitting TBoMS PUSCH in the illustrated embodiment, time slots 3 through 5 within a cycle can all be used to receive TBoMS PUSCH. Since TBoMS PUSCH is received in less than one time slot, the nearest available time slot after this cycle can be determined to be the 3rd time slot in the next cycle. Therefore, the network device can receive TBoMS PUSCH in the 3rd time slot of the next cycle, thus satisfying the requirement of receiving TBoMS PUSCH in 4 time slots. Correspondingly, the terminal transmits TBoMS PUSCH in the 3rd time slot of the next cycle.

[0440] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0441] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0442] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0443] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0444] In some embodiments, the terms "search space", "search spaceset", "search space configuration", "search spaceset configuration", "control resource set (CORESET)", and "CORESET configuration" can be used interchangeably.

[0445] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

[0446] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0447] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0448] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0449] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0450] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0451] Corresponding to the aforementioned embodiments of the uplink communication processing method, this disclosure also provides embodiments of terminals and network devices.

[0452] Embodiments of this disclosure also provide a terminal, comprising: one or more processors; wherein the terminal is configured to execute the uplink communication processing method described in the first aspect and the optional embodiments of the first aspect.

[0453] Figure 9 This is a schematic block diagram of a terminal according to an embodiment of the present disclosure. Figure 9 As shown, the terminal includes: a processing module 901.

[0454] In some embodiments, the processing module is configured to send a multi-timeslot transport block physical uplink shared channel according to predefined rules, wherein the multi-timeslot transport block physical uplink shared channel conflicts with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a sub-band.

[0455] In some embodiments, the processing module is used for at least one of the following:

[0456] The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit.

[0457] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the second time domain unit.

[0458] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0459] In some embodiments, the processing module is used for at least one of the following:

[0460] The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit.

[0461] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, so it is not expected to transmit the physical uplink shared channel in the first time domain unit.

[0462] In some embodiments, the processing module is used to determine the second frequency domain resources within the uplink subband when the first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband.

[0463] Transmit the physical uplink shared channel in the second frequency domain resources.

[0464] In some embodiments, the processing module is configured to determine, within the uplink subband, a frequency domain resource that extends from a first frequency domain position to a first frequency domain range as a second frequency domain resource, wherein the first frequency domain range is determined based on the first frequency domain resource.

[0465] In some embodiments, the processing module is also used for at least one of the following:

[0466] The frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit.

[0467] The frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is transmitted in the second time domain unit.

[0468] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0469] In some embodiments, the processing module is used for at least one of the following:

[0470] The frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit.

[0471] The frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink subband, so it is not expected to transmit the physical uplink shared channel in the first time domain unit.

[0472] In some embodiments, the processing module is used for at least one of the following:

[0473] If the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0474] If the first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, it is not expected to send the physical uplink shared channel in the first time domain unit.

[0475] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0476] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0477] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0478] In some embodiments, the processing module is used for at least one of the following:

[0479] If the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0480] The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit;

[0481] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit.

[0482] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

[0483] In some embodiments, the second time-domain unit is not configured with a sub-band.

[0484] In some embodiments, the conflict between the physical uplink shared channel and broadcast messages in a time-domain unit configured with subbands includes at least one of the following:

[0485] The first time-domain resource of the physical uplink shared channel in the time-domain unit configured with sub-bands partially overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0486] The first time-domain resource of the physical uplink shared channel in the time-domain unit configured with sub-bands completely overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0487] The physical uplink shared channel and broadcast messages are in the same time-domain unit with subbands.

[0488] In some embodiments, broadcast message conflicts include at least one of the following: synchronization signal blocks; common search space.

[0489] It should be noted that, Figure 9The network device shown may include, in addition to the modules described in the above embodiments, other modules such as communication modules and storage modules. The embodiments disclosed herein do not limit this.

[0490] Embodiments of this disclosure also provide a network device comprising: one or more processors; wherein the network device is configured to perform the uplink communication processing method described in the second aspect and optional embodiments thereof.

[0491] Figure 10 This is a schematic block diagram of a network device according to embodiments of the present disclosure. Figure 10 As shown, the network device includes: processing module 1001.

[0492] In some embodiments, the processing module is configured to receive a multi-timeslot transport block physical uplink shared channel sent by a terminal according to predefined rules, wherein the multi-timeslot transport block physical uplink shared channel conflicts with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a sub-band.

[0493] In some embodiments, the processing module is used for at least one of the following:

[0494] The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit.

[0495] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the physical uplink shared channel is received in the second time domain unit.

[0496] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0497] In some embodiments, the processing module is used for at least one of the following:

[0498] The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit.

[0499] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband, so it is not expected to receive the physical uplink shared channel in the first time domain unit.

[0500] In some embodiments, the processing module is used to determine the second frequency domain resources within the uplink subband when the first frequency domain resources of the physical uplink shared channel are not all located within the uplink subband.

[0501] Receive the physical uplink shared channel in the second frequency domain resources.

[0502] In some embodiments, the processing module is configured to determine, within the uplink subband, a frequency domain resource that extends from a first frequency domain position to a first frequency domain range as a second frequency domain resource, wherein the first frequency domain range is determined based on the first frequency domain resource.

[0503] In some embodiments, the processing module is also used for at least one of the following:

[0504] The frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit.

[0505] The frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the second time domain unit.

[0506] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0507] In some embodiments, the processing module is used for at least one of the following:

[0508] The frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit.

[0509] The frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink subband, so it is not expected to receive the physical uplink shared channel in the first time domain unit.

[0510] In some embodiments, the processing module is used for at least one of the following:

[0511] The first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit.

[0512] If the first frequency domain spacing between the uplink subband and the broadcast message is less than the frequency domain spacing threshold, it is not expected to receive the physical uplink shared channel in the first time domain unit.

[0513] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit.

[0514] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected to receive the physical uplink shared channel in the first time domain unit.

[0515] The second time-domain unit is a different time-domain unit from the first time-domain unit.

[0516] In some embodiments, the processing module is used for at least one of the following:

[0517] The first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit.

[0518] If the first frequency domain spacing between the uplink subband and the broadcast message is less than the frequency domain spacing threshold, it is not expected that the physical uplink shared channel will be received in the first time domain unit.

[0519] The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit.

[0520] If the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, it is not expected that the physical uplink shared channel will be received in the first time domain unit.

[0521] In some embodiments, the second time-domain unit is not configured with a sub-band.

[0522] In some embodiments, the conflict between the physical uplink shared channel and broadcast messages in a time-domain unit configured with subbands includes at least one of the following:

[0523] The first time-domain resource of the physical uplink shared channel in the time-domain unit configured with sub-bands partially overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0524] The first time-domain resource of the physical uplink shared channel in the time-domain unit configured with sub-bands completely overlaps with the second time-domain resource of the broadcast message in the time-domain unit;

[0525] The physical uplink shared channel and broadcast messages are in the same time-domain unit with subbands.

[0526] In some embodiments, broadcast message conflicts include at least one of the following: synchronization signal blocks; common search space.

[0527] It should be noted that, Figure 10 The network device shown may include, in addition to the modules described in the above embodiments, other modules such as communication modules and storage modules. The embodiments disclosed herein do not limit this.

[0528] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0529] The embodiments of this disclosure also propose an uplink communication processing method, the method comprising: a terminal sending a multi-timeslot transport block physical uplink shared channel according to predefined rules, wherein the multi-timeslot transport block physical uplink shared channel conflicts with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a sub-band; and a network device receiving the multi-timeslot transport block physical uplink shared channel sent by the terminal according to predefined rules.

[0530] Embodiments of this disclosure also provide a terminal, comprising: one or more processors; wherein the terminal is configured to execute the uplink communication processing method described in the first aspect and the optional embodiments of the first aspect.

[0531] Embodiments of this disclosure also provide a network device comprising: one or more processors; wherein the network device is configured to perform the uplink communication processing method described in the second aspect and optional embodiments thereof.

[0532] Embodiments of this disclosure also provide a communication device, comprising: one or more processors; wherein the processors are configured to invoke instructions to cause the communication device to perform the uplink communication processing method described in the first aspect, the second aspect, an optional embodiment of the first aspect, and an optional embodiment of the second aspect.

[0533] Embodiments of this disclosure also propose a communication system including a terminal and a network device, wherein the terminal is configured to implement the uplink communication processing method described in the first aspect and optional embodiments of the first aspect, and the network device is configured to implement the uplink communication processing method described in the second aspect and optional embodiments of the second aspect.

[0534] Embodiments of this disclosure also provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the uplink communication processing method described in the first aspect, the second aspect, an optional embodiment of the first aspect, and an optional embodiment of the second aspect.

[0535] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0536] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0537] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0538] Figure 11 This is a schematic diagram of the structure of the communication device 11100 proposed in this embodiment. The communication device 11100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 11100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0539] like Figure 11As shown, the communication device 11100 includes one or more processors 11101. The processor 11101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. The processor 11101 is used to invoke instructions to cause the communication device 11100 to execute any of the above methods.

[0540] In some embodiments, the communication device 11100 further includes one or more memories 11102 for storing instructions. Optionally, all or part of the memories 11102 may also be located outside the communication device 11100.

[0541] In some embodiments, the communication device 11100 further includes one or more transceivers 11103. When the communication device 11100 includes one or more transceivers 11103, the communication steps such as sending and receiving in the above method are performed by the transceivers 11103, and other steps are performed by the processor 11101.

[0542] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.

[0543] Optionally, the communication device 11100 further includes one or more interface circuits 11104, which are connected to the memory 11102. The interface circuits 11104 can be used to receive signals from the memory 11102 or other devices, and can be used to send signals to the memory 11102 or other devices. For example, the interface circuits 11104 can read instructions stored in the memory 11102 and send the instructions to the processor 11101.

[0544] The communication device 11100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 11100 described in this disclosure is not limited thereto, and the structure of the communication device 11100 may vary. Figure 11The limitations. The communication device can be a standalone device or part of a larger device. For example, the communication device can be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0545] Figure 12 This is a schematic diagram of the structure of chip 12200 according to an embodiment of this disclosure. For cases where the communication device 11100 can be a chip or a chip system, please refer to... Figure 12 The diagram shown is a schematic representation of the structure of chip 12200, but it is not limited to this.

[0546] Chip 12200 includes one or more processors 12201, which are used to invoke instructions to cause chip 12200 to perform any of the above methods.

[0547] In some embodiments, the chip 12200 further includes one or more interface circuits 12202, which are connected to the memory 12203. The interface circuits 12202 can be used to receive signals from the memory 12203 or other devices, and can also be used to send signals to the memory.

[0548] 12203 or other devices transmit signals. For example, interface circuit 12202 can read instructions stored in memory 12203 and send those instructions to processor 12201. Optionally, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0549] In some embodiments, chip 12200 further includes one or more memories 12203 for storing instructions. Optionally, all or part of the memories 12203 may be located outside of chip 12200.

[0550] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 11100, cause the communication device 11100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0551] This disclosure also provides a program product that, when executed by the communication device 11100, causes the communication device 11100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0552] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. An uplink communication processing method, characterized in that, The method includes: The multi-timeslot transport block physical uplink shared channel is transmitted according to predefined rules. The multi-timeslot transport block physical uplink shared channel conflicts with the broadcast message in the first time domain unit, which is configured with an uplink sub-band. The step of transmitting the physical uplink shared channel of the multi-slot transport block according to predefined rules includes: The frequency domain range of the first frequency domain resource of the physical uplink shared channel is larger than the frequency domain range of the uplink sub-band, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

2. The method according to claim 1, characterized in that, The method of transmitting the physical uplink shared channel of multi-slot transport blocks according to predefined rules also includes at least one of the following: The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit; The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the second time domain unit; The second time-domain unit is a different time-domain unit from the first time-domain unit.

3. The method according to claim 1, characterized in that, The method of transmitting the physical uplink shared channel of multi-slot transport blocks according to predefined rules also includes at least one of the following: The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit; The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

4. The method according to claim 1, characterized in that, The step of transmitting the physical uplink shared channel of multi-slot transport blocks according to predefined rules also includes: The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the second frequency domain resources are determined within the uplink sub-band. The physical uplink shared channel is transmitted in the second frequency domain resource.

5. The method according to claim 4, characterized in that, Determining the second frequency domain resource within the uplink sub-band includes: Within the uplink sub-band, a frequency domain resource is defined as the second frequency domain resource, starting from a first frequency domain position and extending continuously within a first frequency domain range. The first frequency domain range is determined based on the first frequency domain resource.

6. The method according to any one of claims 4 to 5, characterized in that, The method of transmitting the physical uplink shared channel of multi-slot transport blocks according to predefined rules also includes at least one of the following: The frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is transmitted in the first time domain unit; The frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is transmitted in the second time domain unit; The second time-domain unit is a different time-domain unit from the first time-domain unit.

7. The method according to claim 1, characterized in that, The method of transmitting the physical uplink shared channel of multi-slot transport blocks according to predefined rules also includes at least one of the following: When the first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is transmitted in the first time domain unit. The first frequency domain interval between the uplink subband and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be sent in the first time domain unit. The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is transmitted in the first time domain unit. The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be transmitted in the first time domain unit.

8. The method according to claim 2 or 6, characterized in that, The second time-domain unit is not configured with a sub-band.

9. The method according to any one of claims 1 to 8, characterized in that, The conflict between the physical uplink shared channel and the broadcast message in the first time-domain unit configured with uplink subbands includes at least one of the following: The first time domain resource of the physical uplink shared channel in the first time domain unit configured with uplink sub-bands partially overlaps with the second time domain resource of the broadcast message in the first time domain unit; The first time domain resources of the physical uplink shared channel in the first time domain unit configured with uplink sub-bands completely overlap with the second time domain resources of the broadcast message in the first time domain unit; The physical uplink shared channel and the broadcast message reside in the same first time domain unit configured with uplink subbands.

10. The method according to any one of claims 1 to 9, characterized in that, The broadcast message conflict includes at least one of the following: Synchronization signal block; Public search space.

11. An uplink communication processing method, characterized in that, The method includes: According to predefined rules, the multi-timeslot transmission block physical uplink shared channel sent by the receiving terminal is received. The multi-timeslot transmission block physical uplink shared channel conflicts with the broadcast message in the first time domain unit, wherein the first time domain unit is configured with an uplink sub-band. The physical uplink shared channel for receiving multi-slot transport blocks sent by the terminal according to predefined rules includes: The frequency domain range of the first frequency domain resource of the physical uplink shared channel is larger than the frequency domain range of the uplink sub-band, and it is not expected to receive the physical uplink shared channel in the first time domain unit.

12. The method according to claim 11, characterized in that, The physical uplink shared channel for receiving multi-timeslot transport blocks sent by the terminal according to predefined rules also includes at least one of the following: The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit; The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the physical uplink shared channel is received in the second time domain unit; The second time-domain unit is a different time-domain unit from the first time-domain unit.

13. The method according to claim 11, characterized in that, The physical uplink shared channel for receiving multi-timeslot transport blocks sent by the terminal according to predefined rules also includes at least one of the following: The first frequency domain resources of the physical uplink shared channel are all located within the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit; The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and it is not expected to receive the physical uplink shared channel in the first time domain unit.

14. The method according to claim 11, characterized in that, The multi-timeslot transport block physical uplink shared channel received by the terminal according to predefined rules also includes: The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and the second frequency domain resources are determined within the uplink sub-band. The physical uplink shared channel is received in the second frequency domain resource.

15. The method according to claim 14, characterized in that, Determining the second frequency domain resource within the uplink sub-band includes: Within the uplink sub-band, a frequency domain resource extending from a first frequency domain position to a first frequency domain range is defined as the second frequency domain resource, wherein the first frequency domain range is determined based on the first frequency domain resource.

16. The method according to any one of claims 14 to 15, characterized in that, The multi-timeslot transport block physical uplink shared channel received by the terminal according to predefined rules also includes: The frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the first time domain unit; The frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is received in the second time domain unit; The second time-domain unit is a different time-domain unit from the first time-domain unit.

17. The method according to claim 11, characterized in that, The physical uplink shared channel for receiving multi-timeslot transport blocks sent by the terminal according to predefined rules also includes at least one of the following: The first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit. The first frequency domain interval between the uplink sub-band and the broadcast message is less than the frequency domain interval threshold, and it is not expected to receive the physical uplink shared channel in the first time domain unit. The first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold, and the physical uplink shared channel is received in the first time domain unit. The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and it is not expected that the physical uplink shared channel will be received in the first time domain unit.

18. The method according to claim 12 or 16, characterized in that, The second time-domain unit is not configured with a sub-band.

19. The method according to any one of claims 11 to 18, characterized in that, The conflict between the physical uplink shared channel and the broadcast message in the first time-domain unit configured with uplink subbands includes at least one of the following: The first time domain resource of the physical uplink shared channel in the first time domain unit configured with uplink sub-bands partially overlaps with the second time domain resource of the broadcast message in the first time domain unit; The first time domain resources of the physical uplink shared channel in the first time domain unit configured with uplink sub-bands completely overlap with the second time domain resources of the broadcast message in the first time domain unit; The physical uplink shared channel and the broadcast message reside in the same first time domain unit configured with uplink subbands.

20. The method according to any one of claims 11 to 19, characterized in that, The broadcast message conflict includes at least one of the following: Synchronization signal block; Public search space.

21. An uplink communication processing method, characterized in that, The method includes: The terminal sends a multi-timeslot transport block physical uplink shared channel according to predefined rules. The multi-timeslot transport block physical uplink shared channel conflicts with the broadcast message in the first time domain unit, wherein the first time domain unit is configured with an uplink sub-band. Network devices receive multi-slot transport blocks sent by terminals via the physical uplink shared channel according to predefined rules. The predefined rules include: The frequency domain range of the first frequency domain resource of the physical uplink shared channel is greater than the frequency domain range of the uplink sub-band. The terminal does not expect to transmit the physical uplink shared channel in the first time domain unit, and the network device does not expect to receive the physical uplink shared channel in the first time domain unit.

22. A terminal, characterized in that, include: One or more processors; The terminal is used to execute the uplink communication processing method according to any one of claims 1-10.

23. A network device, characterized in that, include: One or more processors; The network device is used to execute the uplink communication processing method according to any one of claims 11-20.

24. A communication device, characterized in that, include: One or more processors; The processor is used to invoke instructions to cause the communication device to execute the uplink communication processing method according to any one of claims 1-10 and 11-20.

25. A communication system, characterized in that, The device includes a terminal and a network device, wherein the terminal is configured to implement the uplink communication processing method according to any one of claims 1-10, and the network device is configured to implement the uplink communication processing method according to any one of claims 11-20.

26. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the uplink communication processing method as described in any one of claims 1-10 and 11-20.

Images