Uplink communication processing method, communication device, and storage medium

Abstract

The present disclosure relates to the technical field of communications, in particular to an uplink communication processing method, a communication device, and a storage medium. The uplink communication processing method comprises: sending a transport block over multi-slot physical uplink shared channel (TBoMS PUSCH) on the basis of a predefined rule, wherein in a first time-domain unit, the TBoMS PUSCH conflicts with a broadcast message, the first time-domain unit being configured with a sub-band. According to the present disclosure, in some SBFD time-domain units, even if the TBoMS PUSCH conflicts with the broadcast message, the TBoMS technology can also be applied, thereby facilitating ensuring the uplink coverage gain brought for sending the TBoMS PUSCH in an SBFD slot.

Description

Uplink communication processing method, communication device and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to an uplink communication processing method, a terminal, a network device, a communication device, and a storage medium. Background Art

[0002] Network devices can communicate with terminals in time-domain units. Within a time slot, network devices can only perform uplink or downlink communications. To improve communication efficiency, network devices can be enabled to perform both uplink and downlink communications within a time slot, thus achieving full-duplex communication. However, full-duplex communication scenarios present some technical challenges.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide an uplink communication processing method, a terminal, a network device, a communication device, and a storage medium to solve technical problems in related technologies that exist when a network device performs communication after configuring a subband for a terminal.

[0005] According to a first aspect of an embodiment of the present disclosure, a method for processing uplink communications is proposed, the method comprising: sending a multi-slot transport block physical uplink shared channel according to a predefined rule, wherein the multi-slot transport block physical uplink shared channel collides with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a subband.

[0006] According to a second aspect of an embodiment of the present disclosure, a method for processing uplink communications is proposed, the method comprising: receiving a multi-slot transport block physical uplink shared channel sent by a terminal according to a predefined rule, wherein the multi-slot transport block physical uplink shared channel collides with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a subband.

[0007] According to a third aspect of an embodiment of the present disclosure, a method for processing uplink communications is proposed, the method comprising: a terminal sending a multi-slot transmission block physical uplink shared channel according to a predefined rule, wherein the multi-slot transmission block physical uplink shared channel collides with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a subband; and a network device receiving the multi-slot transmission block physical uplink shared channel sent by the terminal according to the predefined rule.

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

[0009] According to a fifth aspect of an embodiment of the present disclosure, a network device is proposed, comprising: one or more processors; wherein the network device is used to execute the uplink communication processing method described in the second aspect above.

[0010] According to the sixth aspect of an embodiment of the present disclosure, a communication device is proposed, comprising: one or more processors; wherein the processor is used to call instructions so that the communication device executes the uplink communication processing method described in any one of the first and second aspects above.

[0011] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, comprising 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.

[0012] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the uplink communication processing method as described in any one of the first and second aspects above.

[0013] According to the embodiments of the present disclosure, in some SBFD time domain units, even if the TBoMS PUSCH conflicts with a broadcast message, the TBoMS technology can be applied, which helps to ensure uplink coverage gain brought by sending the TBoMS PUSCH in the SBFD time slot. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0015] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0016] FIG2 is an interactive schematic diagram illustrating an uplink communication processing method according to an embodiment of the present disclosure.

[0017] FIG3 is a schematic flowchart showing a method for processing uplink communications according to an embodiment of the present disclosure.

[0018] FIG4 is a schematic diagram showing a sub-band according to an embodiment of the present disclosure.

[0019] FIG5 is a schematic diagram showing a conflict according to an embodiment of the present disclosure.

[0020] FIG6A is a schematic diagram showing another conflict according to an embodiment of the present disclosure.

[0021] FIG6B is a schematic diagram showing a processing result according to an embodiment of the present disclosure.

[0022] FIG6C is a schematic diagram showing another processing result according to an embodiment of the present disclosure.

[0023] FIG. 7 is a schematic diagram showing a processing result according to an embodiment of the present disclosure.

[0024] FIG8 is a schematic flowchart showing a method for processing uplink communications according to an embodiment of the present disclosure.

[0025] FIG9 is a schematic block diagram of a terminal according to an embodiment of the present disclosure.

[0026] FIG10 is a schematic block diagram showing a network device according to an embodiment of the present disclosure.

[0027] FIG11 is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure.

[0028] FIG12 is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0030] In a first aspect, an embodiment of the present disclosure proposes an uplink communication processing method, the method comprising: sending a multi-slot transmission block physical uplink shared channel according to a predefined rule, wherein the multi-slot transmission 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 subband.

[0031] In the above embodiment, when the terminal determines that the 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 the SBFD time domain unit, but may instead determine how to handle the TBoMS PUSCH based on predefined rules. For example, the TBoMS PUSCH may be sent in the SBFD time domain unit, or the TBoMS PUSCH may not be sent in the SBFD time domain unit. Accordingly, in some SBFD time domain units, even if the TBoMS PUSCH conflicts with a broadcast message, the TBoMS technology can be applied, which helps to ensure the uplink coverage gain brought by sending the TBoMS PUSCH in the SBFD time slot.

[0032] In combination with some embodiments of the first aspect, in some embodiments, sending the multi-slot transport block physical uplink shared channel according to a predefined rule includes at least one of the following:

[0033] 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 sent in the first time domain unit;

[0034] 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 sent in the second time domain unit;

[0035] The second time domain unit and the first time domain unit are different time domain units.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, determining a processing method for a physical uplink shared channel according to a predefined rule includes at least one of the following:

[0037] 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 transmitted in a time domain unit;

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

[0039] In combination with some embodiments of the first aspect. In some embodiments, sending a multi-slot transport block physical uplink shared channel according to a predefined rule includes: if not all first frequency domain resources of the physical uplink shared channel are located within an uplink subband, determining a second frequency domain resource within the uplink subband; and sending the physical uplink shared channel in the second frequency domain resource.

[0040] In the above embodiment, when the first frequency domain resources of the TBoMS PUSCH are not all located within the uplink subband, the TBoMS PUSCH can also be sent in the conflicting SBFD time domain unit by determining the second frequency domain resources, which is beneficial to ensuring the uplink coverage gain brought by sending the TBoMS PUSCH in the SBFD time slot.

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

[0042] Within the uplink subband, frequency domain resources starting from the first frequency domain position and continuing within the first frequency domain range are determined as second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the receiving of a multi-slot transport block physical uplink shared channel sent by a terminal according to a predefined rule includes at least one of the following:

[0044] The frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the uplink subband, and the physical uplink shared channel is sent in the first time domain unit;

[0045] The frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink subband, and the physical uplink shared channel is sent in the second time domain unit;

[0046] The second time domain unit and the first time domain unit are different time domain units.

[0047] In combination with some embodiments of the first aspect, in some embodiments, sending the multi-slot transport block physical uplink shared channel according to a predefined rule includes at least one of the following:

[0048] The frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the uplink subband, and the physical uplink shared channel is sent in the first time domain unit;

[0049] 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 not expected to be sent in the first time domain unit.

[0050] In combination with some embodiments of the first aspect, in some embodiments, sending the multi-slot transport block physical uplink shared channel according to a predefined rule includes at least one of the following:

[0051] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0052] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit;

[0053] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0054] A first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit;

[0055] The second time domain unit and the first time domain unit are different time domain units.

[0056] In combination with some embodiments of the first aspect, in some embodiments, sending the multi-slot transport block physical uplink shared channel according to a predefined rule includes at least one of the following:

[0057] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0058] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit;

[0059] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0060] The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit.

[0061] In the above embodiment, 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 greater impact on the communication quality. Therefore, the terminal does not expect to send TBoMS PUSCH in the conflicting time domain unit, which is conducive to ensuring relatively good communication quality.

[0062] In combination with some embodiments of the first aspect, in some embodiments, the second time domain unit is not configured with a subband.

[0063] In combination with some embodiments of the first aspect, in some embodiments, the physical uplink shared channel and the broadcast message conflict in a time domain unit configured with a subband, including at least one of the following:

[0064] A first time domain resource of the physical uplink shared channel in a time domain unit configured with a subband partially overlaps with a second time domain resource of the broadcast message in the time domain unit;

[0065] The first time domain resource of the physical uplink shared channel in the time domain unit configured with the subband and the second time domain resource of the broadcast message in the time domain unit completely overlap;

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

[0067] In the above embodiment, by considering the conflict situations in various scenarios, it is helpful to ensure that the conflict situations are comprehensively considered, and further determine the processing method of the TBoMS PUSCH in the conflict situation in a more comprehensive manner.

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

[0069] In the second aspect, an embodiment of the present disclosure proposes an uplink communication processing method, the method comprising: receiving a multi-slot transmission block physical uplink shared channel sent by a terminal according to a predefined rule, wherein the multi-slot transmission 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 subband.

[0070] In combination with some embodiments of the second aspect. In some embodiments, the receiving of the multi-slot transport block physical uplink shared channel sent by the terminal according to the predefined rule 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; wherein the second time domain unit and the first time domain unit are different time domain units.

[0071] In combination with some embodiments of the second aspect. In some embodiments, the predefined rule is used to indicate: when the first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, 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 sub-band.

[0072] In combination with some embodiments of the second aspect, in some embodiments, receiving a multi-slot transport block physical uplink shared channel sent by a terminal according to a predefined rule includes:

[0073] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and a second frequency domain resource is determined within the uplink sub-band;

[0074] The physical uplink shared channel is received in the second frequency domain resources.

[0075] In combination with some embodiments of the second aspect. In some embodiments, determining the second frequency domain resource within the uplink sub-band includes: determining, within the uplink sub-band, a frequency domain resource starting from a first frequency domain position and continuing 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.

[0076] In combination with some embodiments of the second aspect. In some embodiments, the receiving of the multi-slot transport block physical uplink shared channel sent by the terminal according to the predefined rule 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 and the first time domain unit are different time domain units.

[0077] In combination with some embodiments of the second aspect. In some embodiments, the receiving of the multi-slot transport block physical uplink shared channel sent by the terminal according to the predefined rule 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.

[0078] In combination with some embodiments of the second aspect, the receiving of a multi-slot transport block physical uplink shared channel sent by a terminal according to a predefined rule includes at least one of the following: a first frequency domain interval between the uplink subband 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 subband and the broadcast message is less than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be received in the first time domain unit;

[0079] A first frequency domain interval between the physical uplink shared channel 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;

[0080] A first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be received in the first time domain unit;

[0081] The second time domain unit and the first time domain unit are different time domain units.

[0082] In combination with some embodiments of the second aspect, in some embodiments, the receiving of a multi-slot transport block physical uplink shared channel sent by a terminal according to a predefined rule includes at least one of the following:

[0083] A first frequency domain interval between the uplink subband 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;

[0084] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to receive the physical uplink shared channel in the first time domain unit;

[0085] A first frequency domain interval between the physical uplink shared channel 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;

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

[0087] In combination with some embodiments of the second aspect, in some embodiments, the second time domain unit is not configured with a subband.

[0088] In combination with some embodiments of the second aspect, in some embodiments, the physical uplink shared channel and the broadcast message conflict in a time domain unit configured with a subband, including at least one of the following:

[0089] A first time domain resource of the physical uplink shared channel in the time domain unit configured with the subband partially overlaps with a second time domain resource of the broadcast message in the first time domain unit;

[0090] The first time domain resource of the physical uplink shared channel in the time domain unit configured with the subband and the second time domain resource of the broadcast message in the first time domain unit completely overlap;

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

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

[0093] In the third aspect, an embodiment of the present disclosure proposes an uplink communication processing method, the method comprising: a terminal sends a multi-slot transmission block physical uplink shared channel according to a predefined rule, wherein the multi-slot transmission 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 subband; a network device receives the multi-slot transmission block physical uplink shared channel sent by the terminal according to the predefined rule.

[0094] In a fourth aspect, an embodiment of the present disclosure proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the uplink communication processing method described in the above-mentioned first aspect and the optional embodiment of the first aspect.

[0095] In a fifth aspect, an embodiment of the present disclosure proposes a network device, comprising: one or more processors; wherein the network device is used to execute the uplink communication processing method described in the second aspect and the optional embodiment of the second aspect.

[0096] In a sixth aspect, an embodiment of the present disclosure proposes a communication device, which includes: one or more processors; one or more memories for storing instructions; wherein the processor is used to call the instructions so that the communication device executes the uplink communication processing method described in the first and second aspects, and the optional implementation methods of the first and second aspects.

[0097] In the sixth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and a network device; wherein the terminal is configured to execute the uplink communication processing method described in the first aspect and the second aspect, and the optional implementation of the first aspect and the second aspect, and the network device is configured to execute the uplink communication processing method described in the first aspect and the second aspect, and the optional implementation of the first aspect and the second aspect.

[0098] In the seventh aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the uplink communication processing method described in the first and second aspects, and the optional implementation methods of the first and second aspects.

[0099] In an eighth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the uplink communication processing method described in the first and second aspects, and the optional implementation methods of the first and second aspects.

[0100] In a ninth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the uplink communication processing method described in the first and second aspects, and the optional implementations of the first and second aspects.

[0101] It is understandable that the above-mentioned 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 the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0102] The present disclosure provides an uplink communication processing method, a communication device, and a storage medium. In some embodiments, the terms "uplink communication processing method," "information processing method," and "communication method" are interchangeable; the terms "terminal," "network device," "information processing device," and "communication device" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0103] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain 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 certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0104] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0105] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0106] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "a", "an", "the", "above", "said", "aforementioned", "this", etc., may mean "one and only one", or "one or more", "at least one", etc.

[0107] In the embodiments of the present disclosure, “plurality” refers to two or more.

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

[0109] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0110] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0111] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restrictions on the position, order, priority, quantity or content of the description objects. For the statement of the description objects, please refer to the description in the context of the claims or embodiments, and no unnecessary restrictions should be constituted due to the use of prefixes.

[0112] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0113] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

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

[0115] The recorded names, "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject" and other terms can be used interchangeably.

[0116] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0117] 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", "bandwidth part (BWP)" and the like may be used interchangeably.

[0118] 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 subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

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

[0120] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0121] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0122] As shown in FIG1 , a 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.

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

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

[0125] In some embodiments, the core network device 103 may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element 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).

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

[0127] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0128] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0129] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0130] The embodiments of the present disclosure 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), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (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 utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0131] In some embodiments, the network device may configure sub-bands for the terminal.

[0132] In some embodiments, the sub-band includes at least one of the following: an uplink sub-band and a downlink sub-band.

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

[0134] The frequency domain resources corresponding to the downlink time slot are the downlink frequency domain resources, and the uplink sub-band is configured for the terminal in the downlink time slot. The frequency domain resources corresponding to the uplink sub-band in the frequency domain resources of the downlink time slot can be used for uplink communication, so that the network equipment can perform uplink communication in the uplink sub-band corresponding to the downlink time slot, and perform downlink communication in the frequency domain resources outside the uplink sub-band, thereby realizing full-duplex communication.

[0135] The frequency domain resources corresponding to the flexible time slot can be configured or scheduled as downlink frequency domain resources. Uplink subbands are configured for terminals in the flexible time slots. The frequency domain resources corresponding to the uplink subbands in the flexible time slots can then be used for uplink communication. Network devices can then perform uplink communication in the uplink subbands corresponding to the flexible time slots, and perform downlink communication in frequency domain resources outside the uplink subbands, thereby 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.

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

[0137] The frequency domain resources corresponding to the uplink time slot are the uplink frequency domain resources, and a downlink sub-band is configured for the terminal in the uplink time slot. The frequency domain resources corresponding to the downlink sub-band in the frequency domain resources of the uplink time slot can be used for downlink communication, so that the network equipment can perform downlink communication in the downlink sub-band corresponding to the uplink time slot, and perform uplink communication in the frequency domain resources outside the downlink sub-band, thereby realizing full-duplex communication.

[0138] The frequency domain resources corresponding to the flexible time slot can be configured or scheduled as uplink frequency domain resources, and a downlink sub-band is configured for the terminal in the flexible time slot. The frequency domain resources corresponding to the downlink sub-band in the frequency domain resources of the flexible time slot can be used for downlink communication, so that the network equipment 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.

[0139] In some embodiments, the communication that can be performed between the terminal and the network device in the time domain unit includes at least one of the following: data communication, non-data communication (eg, signaling communication).

[0140] When a terminal performs data communication in a time domain unit (for example, when the terminal sends a transport block (TB) to a network device or receives a transport block sent by a network device), in some scenarios, data communication can be performed in multiple time domain units. For example, when a time domain unit includes a time 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 time slots. In some embodiments, the time domain resources and / or frequency domain resources used to send the TBoMS PUSCH in each time slot can be the same.

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

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

[0143] FIG2 is an interactive schematic diagram illustrating an uplink communication processing method according to an embodiment of the present disclosure.

[0144] As shown in FIG2 , the uplink communication processing method includes:

[0145] Step S201: The terminal sends a multi-slot transport block physical uplink shared channel according to a predefined rule.

[0146] In some embodiments, the predefined rules may be determined by a base protocol agreement.

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

[0148] In some embodiments, the predefined rule is used to indicate how to process the physical uplink shared channel.

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

[0150] In some embodiments, the predefined rule is used to instruct the terminal on how to process the physical uplink shared channel when the physical uplink shared channel collides with a broadcast message in a time domain unit configured with a subband.

[0151] In some embodiments, the collision comprises at least one of: determining that a collision is occurring; and predicting that a collision will occur in a future time domain unit.

[0152] In some embodiments, the physical uplink shared channel and the broadcast message collide in a time domain unit configured with a subband, including at least one of the following:

[0153] A first time domain resource of the physical uplink shared channel in a time domain unit configured with a subband partially overlaps with a second time domain resource of the broadcast message in the time domain unit;

[0154] The first time domain resource of the physical uplink shared channel in the time domain unit configured with the subband and the second time domain resource of the broadcast message in the time domain unit completely overlap;

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

[0156] In some embodiments, the broadcast message collision comprises at least one of: a synchronization signal block; a common search space.

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

[0158] In some embodiments, the terminal sends a multi-slot transport block physical uplink shared channel according to a predefined rule, 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 sent 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 sent in the second time domain unit; wherein the second time domain unit and the first time domain unit are different time domain units.

[0159] In some embodiments, the predefined rules are used to indicate: 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 sent 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 sent in the time domain unit.

[0160] In some embodiments, the terminal sends a multi-slot transport block physical uplink shared channel according to a predefined rule, 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 sent 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 sent in the time domain unit.

[0161] 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 within the uplink subband, the physical uplink shared channel is sent in the second frequency domain resources, wherein the second frequency domain resources are entirely within the uplink subband.

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

[0163] In some embodiments, the terminal determines a second frequency domain resource within the uplink subband, including: determining within the uplink subband a frequency domain resource starting from the first frequency domain position and continuing within the 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.

[0164] In some embodiments, the predefined rules are used to indicate: 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 sent 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 sent in the second time domain unit.

[0165] In some embodiments, the multi-slot transmission block physical uplink shared channel sent by the terminal is received according to predefined rules, and 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.

[0166] In some embodiments, the predefined rules are used to indicate: 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 sent 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 sent in the first time domain unit.

[0167] In some embodiments, the sending of the 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 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 not expected to be sent in the first time domain unit.

[0168] In some embodiments, the predefined rule is used to indicate at least one of the following:

[0169] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0170] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit;

[0171] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0172] The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit.

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

[0174] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0175] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit;

[0176] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0177] A first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit;

[0178] The second time domain unit and the first time domain unit are different time domain units.

[0179] In some embodiments, the predefined rule is used to indicate at least one of the following:

[0180] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0181] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit;

[0182] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0183] The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit.

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

[0185] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0186] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit;

[0187] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit;

[0188] The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit.

[0189] In some embodiments, the terminal may determine, according to a predefined rule, a first frequency domain interval between a first frequency domain resource corresponding to the TBoMS PUSCH and the broadcast message in a conflicting time domain unit.

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

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

[0192] In some embodiments, the terminal may determine, according to a predefined rule, a first frequency domain interval between the uplink subband and the broadcast message in the conflicting time domain unit.

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

[0194] For example, when the first frequency domain interval is greater than or equal to a frequency domain interval threshold, the terminal may send the TBoMS PUSCH in the conflicting time domain unit.

[0195] Step S202: The network device receives a multi-slot transport block physical uplink shared channel sent by a terminal according to a predefined rule.

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

[0197] In some embodiments, the predefined rule is used to indicate how to process the physical uplink shared channel.

[0198] In some embodiments, the physical uplink shared channel is sent by the terminal in a multi-slot transmission block processing manner.

[0199] In some embodiments, the network device determines, according to a predefined rule, how to process the physical uplink shared channel when the physical uplink shared channel collides with a broadcast message in a time domain unit configured with a subband.

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

[0201] 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;

[0202] 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;

[0203] The second time domain unit and the first time domain unit are different time domain units.

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

[0205] 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 the time domain unit;

[0206] 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 received in the time domain unit.

[0207] 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 within the uplink subband, the physical uplink shared channel is sent in the second frequency domain resources, wherein the second frequency domain resources are entirely within the uplink subband.

[0208] In some embodiments, the network device receives a multi-slot transport block physical uplink shared channel sent by a terminal according to a predefined rule, including:

[0209] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and a second frequency domain resource is determined within the uplink sub-band;

[0210] A physical uplink shared channel is received in the second frequency domain resources.

[0211] In some embodiments, the network device determines a second frequency domain resource within the uplink sub-band, including: determining within the uplink sub-band a frequency domain resource starting from the first frequency domain position and continuing within the 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.

[0212] In some embodiments, the network device receives a multi-slot transport block physical uplink shared channel sent by a terminal according to a predefined rule, further comprising at least one of the following:

[0213] The frequency domain range of the first frequency domain resource is smaller 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;

[0214] 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;

[0215] The second time domain unit and the first time domain unit are different time domain units.

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

[0217] The frequency domain range of the first frequency domain resource is smaller 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;

[0218] 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 not expected to be received in the first time domain unit.

[0219] In some embodiments, before determining the second frequency domain resource within the uplink sub-band, 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 sub-band.

[0220] In some embodiments, when the frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink sub-band, then sufficient frequency domain resources for sending TBoMS PUSCH cannot be determined within the uplink sub-band, and the network device does not need to determine the second frequency domain resource within the uplink sub-band, which helps to avoid wasting the resources of the network device; when 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, then sufficient frequency domain resources for receiving TBoMS PUSCH can be determined within the uplink sub-band, and the network device determines the second frequency domain resource within the uplink sub-band.

[0221] In some embodiments, the predefined rule is used to indicate that when a 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 a frequency domain interval threshold, the physical uplink shared channel is sent in a time domain unit.

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

[0223] A first frequency domain interval between the uplink subband 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;

[0224] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be received in the first time domain unit;

[0225] A first frequency domain interval between the physical uplink shared channel 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;

[0226] A first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be received in the first time domain unit;

[0227] The second time domain unit and the first time domain unit are different time domain units.

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

[0229] A first frequency domain interval between the uplink subband 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;

[0230] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to receive the physical uplink shared channel in the first time domain unit;

[0231] A first frequency domain interval between the physical uplink shared channel 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;

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

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

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

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

[0236] For example, when the first frequency domain interval is greater than or equal to a frequency domain interval threshold, the network device may receive the TBoMS PUSCH in the conflicting time domain unit.

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

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

[0239] For example, when the first frequency domain interval is greater than or equal to a frequency domain interval threshold, the network device may receive the TBoMS PUSCH in the conflicting time domain unit.

[0240] The uplink communication processing method involved in the embodiment of the present disclosure may include at least one of steps S201 to S202. For example, step S201 may be implemented as an independent embodiment, step S202 may be implemented as an independent embodiment, and steps S201+S202 may be implemented as independent embodiments, but are not limited thereto.

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

[0242] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0243] In a first aspect, an embodiment of the present disclosure provides an uplink communication processing method. FIG3 is a schematic flow chart of 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. As shown in FIG3, the uplink communication processing method may include the following steps:

[0244] In step S301, a multi-slot transport block physical uplink shared channel is transmitted according to a predefined rule, wherein the multi-slot transport block physical uplink shared channel collides with a broadcast message in a first time domain unit (e.g., an SBFD time domain unit), wherein the first time domain unit is configured with a subband. For example, the predefined rule may be determined according to a protocol agreement.

[0245] It should be noted that the embodiment shown in FIG. 3 can be implemented independently or in combination with at least one other embodiment in the present disclosure. The specific selection can be made as needed and the present disclosure does not limit it.

[0246] In some embodiments, when a TBoMS PUSCH collides with a broadcast message of a network device in a certain time domain unit, the terminal may not expect to send a TBoMS PUSCH in the time domain unit.

[0247] However, when the TBoMS PUSCH conflicts with the broadcast message in a time domain unit configured with a subband (hereinafter referred to as the SBFD time domain unit), since the subband is configured in the SBFD time domain unit, the terminal can perform both uplink and downlink communications in the SBFD time domain unit. If the above implementation method is still used and TBoMS PUSCH is not expected to be sent on the time domain unit, it will make it difficult to apply the TBoMS technology in the SBFD time domain unit, limiting the uplink coverage gain brought by the SBFD technology.

[0248] In some embodiments, the collision comprises at least one of: determining that a collision is occurring; and predicting that a collision will occur in a future time domain unit.

[0249] According to an embodiment of the present 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 the SBFD time domain unit, but may determine how to handle the TBoMS PUSCH according to predefined rules. For example, the TBoMS PUSCH may be sent in the SBFD time domain unit, or the TBoMS PUSCH may not be sent in the SBFD time domain unit. Accordingly, in some SBFD time domain units, even if the TBoMS PUSCH conflicts with a broadcast message, the TBoMS technology can be applied, which is beneficial to ensuring the uplink coverage gain brought by sending the TBoMS PUSCH in the SBFD time slot.

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

[0251] The following embodiments mainly take the broadcast message including SSB as an example to exemplify the technical solution of the present disclosure.

[0252] In some embodiments, the physical uplink shared channel and the broadcast message collide in a time domain unit configured with a subband, including at least one of the following:

[0253] 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;

[0254] The first time domain resource of the physical uplink shared channel in the time domain unit and the second time domain resource of the broadcast message in the time domain unit completely overlap;

[0255] The physical uplink shared channel and the broadcast message are in the same time domain unit.

[0256] 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 conflicts with SSB in the SBFD time slot, and then determine how to handle TBoMS PUSCH according to predefined rules.

[0257] 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 conflicts with SSB in the SBFD time slot, and then determine how to handle TBoMS PUSCH according to predefined rules.

[0258] For example, when the SBFD time slot where the TBoMS PUSCH is located is the same as the SBFD time slot where the SSB is located, the terminal can determine that the TBoMS PUSCH and the SSB conflict in the same SBFD time slot, and then determine how to handle the TBoMS PUSCH according to predefined rules.

[0259] The following uses some embodiments to exemplify how a terminal sends a multi-slot transport block physical uplink shared channel according to a predefined rule.

[0260] In some embodiments, the predefined rules are used to indicate: 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 sent 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 sent in the time domain unit.

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

[0262] 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 transmitted in a time domain unit;

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

[0264] In some embodiments, the terminal may determine, according to a predefined rule, that when all first frequency domain resources of the physical uplink shared channel are located within the uplink sub-band, to send the physical uplink shared channel in a time domain unit.

[0265] According to predefined rules, the terminal can determine whether the first frequency domain resources of the TBoMS PUSCH are all located within the uplink subband in the conflicting time domain unit. When the first frequency domain resources of the TBoMS PUSCH are all located within the uplink subband, the terminal can send the TBoMS PUSCH in the conflicting time domain unit; when the first frequency domain resources of the TBoMS PUSCH are not all located within the uplink subband, the terminal does not expect to send 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.

[0266] FIG4 is a schematic diagram showing a sub-band according to an embodiment of the present disclosure.

[0267] For example, a subband includes an uplink subband, a time domain unit includes a time slot, and a network device configures an uplink subband for a terminal in a downlink time slot.

[0268] As shown in Figure 4, the time slot structure configured for the terminal by the network device through the time slot format indication (SFI) and / or time division duplexing uplink and downlink configuration (TDD (Time Division Duplexing) UL-DL configuration) is DDFFU, where D represents the downlink time slot, U represents the uplink time slot, and F represents the flexible time slot, that is, in the 5 time slots, slot#0 to slot#1 are downlink time slots, slot#2 and slot#3 are flexible time slots, and slot#4 is the uplink time slot.

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

[0270] As shown in Figure 4, the network device configures uplink subbands (UL subbands) in slot #1, slot #2, and slot #3. In some embodiments, all uplink subbands are located in the active uplink bandwidth part (active UL BWP (BandWdith Part)).

[0271] FIG5 is a schematic diagram showing a conflict according to an embodiment of the present disclosure.

[0272] As shown in Figure 5, for example, an SSB burst includes eight SSB candidates, and the network device sends an SSB on each SSB candidate. The eight SSB candidates are distributed across slots 0 to 3, with two SSB candidates in each time slot.

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

[0274] Since the network device transmits SSB in slots #1 to #3 and the terminal also needs to transmit TBoMS PUSCH in the uplink subbands in slots #1 to #3, the terminal may determine that TBoMS PUSCH conflicts with SSB in slots #1 to #3.

[0275] In some embodiments, the predefined rule is used to indicate that when all 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 a time domain unit.

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

[0277] FIG6A is a schematic diagram showing another conflict according to an embodiment of the present disclosure.

[0278] As shown in FIG6A , the first frequency domain resources of TBoMS PUSCH in slot#1 to slot#3 are not all located within the uplink subband. In this case, the terminal cannot smoothly send TBoMS PUSCH within the uplink subband according to the configuration and / or scheduling of the network device.

[0279] FIG6B is a schematic diagram showing a processing result according to an embodiment of the present disclosure.

[0280] In some embodiments, the predefined rule is used to indicate that when all 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 a time domain unit.

[0281] In the embodiment shown in FIG6A , because the first frequency domain resources of the TBoMS PUSCH are not entirely within the uplink subband, the terminal cannot successfully transmit the TBoMS PUSCH in the conflicting time slot according to the configuration and / or scheduling of the network device. Then, as shown in FIG6B , the terminal can determine, based on a predefined rule sent by the network device, not to transmit the TBoMS PUSCH in the conflicting time domain units, such as slots #1 to #3, and to transmit the TBoMS PUSCH only in slot #4.

[0282] In some embodiments, since there are at least three slots in which the TBoMS PUSCH is sent, in order to ensure that the number of slots for the TBoMS PUSCH is four, it is necessary to determine three available slots after slot #4 to send the TBoMS PUSCH.

[0283] FIG6C is a schematic diagram showing another processing result according to an embodiment of the present disclosure.

[0284] In some embodiments, the predefined rule is used to indicate that when all 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 a time domain unit.

[0285] In the embodiment shown in FIG6A , since the first frequency domain resources of the TBoMS PUSCH are not entirely located within the uplink subband, the terminal cannot smoothly transmit the TBoMS PUSCH in the downlink time slot configured with the subband (e.g., slot#1) according to the configuration and / or scheduling of the network device. However, in the flexible time slot configured with the subband (e.g., slot#2), the terminal may still be able to smoothly transmit the TBoMS PUSCH according to the configuration and / or scheduling of the network device (e.g., the frequency domain resources corresponding to the flexible time slot are scheduled as uplink frequency domain resources). Then, as shown in FIG6C , the terminal may determine that the TBoMS PUSCH is not transmitted in the downlink time domain unit configured with the subband in the conflicting time domain unit, such as slot#1, but may transmit the TBoMS PUSCH in the flexible time domain unit configured with the subband in the conflicting time domain unit, such as slot#2 and slot#3. Of course, the TBoMS PUSCH may also be transmitted in slot#4.

[0286] In some embodiments, since there is at least one slot in which the TBoMS PUSCH is sent, in order to ensure that the number of slots for the TBoMS PUSCH is 4, it is necessary to determine one available slot after slot #4 to send the TBoMS PUSCH.

[0287] In some embodiments, when the first frequency domain resources of the TBoMS PUSCH are not all located within the uplink subband, whether to send the TBoMS PUSCH in the flexible time domain unit configured with the subband in the conflicting time domain unit, for example, in the case of Figure 6A, according to the example processing of Figure 6B or according to the example processing of Figure 6C, can be indicated by the network device or determined according to the protocol agreement.

[0288] In some embodiments, the predefined rules are used to indicate: 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 sent 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 sent in the second time domain unit.

[0289] In some embodiments, the terminal sends a multi-slot transport block physical uplink shared channel according to a predefined rule, 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 sent 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 sent in the second time domain unit; wherein the second time domain unit and the first time domain unit are different time domain units.

[0290] For example, the second time domain includes the nearest available time domain unit (eg, a time domain unit that does not conflict with the broadcast message and has uplink frequency domain resources), and may also include a time domain unit that does not conflict among the time domain units used to send the TBoMS PUSCH.

[0291] For example, TBoMS PUSCH is sent in the manner of the embodiment shown in Figure 6B. In one cycle, only the 5th time slot can be used to send TBoMS PUSCH. Since TBoMS PUSCH is sent in at least 3 time slots, the three nearest available time slots after the cycle are the 5th time slot of each of the 3 cycles after the cycle. Then, the 5th time slot of each of the 3 cycles after the cycle can be used as the second time domain unit for sending TBoMS PUSCH, thereby satisfying the requirement of sending TBoMS PUSCH in 4 time slots.

[0292] For example, if the TBoMS PUSCH is sent in the manner of the embodiment shown in FIG6C , the 3rd to 5th time slots in a cycle can be used to send the TBoMS PUSCH. Since the TBoMS PUSCH is sent in one less time slot, it can be determined that the nearest available time slot after the cycle is the 3rd time slot in the next cycle. Then, the 3rd time slot in the next cycle can be used as the second time domain unit for sending the TBoMS PUSCH, thereby satisfying the requirement of sending the TBoMS PUSCH in 4 time slots. Correspondingly, the network device receives the TBoMS PUSCH sent by the terminal in the 3rd time slot in the next cycle.

[0293] 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 within the uplink subband, the physical uplink shared channel is sent in the second frequency domain resources, wherein the second frequency domain resources are entirely within the uplink subband.

[0294] In some embodiments, sending a multi-slot transport block physical uplink shared channel according to a predefined rule includes:

[0295] The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and a second frequency domain resource is determined within the uplink sub-band;

[0296] A physical uplink shared channel is sent in the second frequency domain resources.

[0297] In some embodiments, the predefined rule may instruct the terminal to send 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 within the uplink subband, wherein the second frequency domain resource is entirely within the uplink subband.

[0298] According to predefined rules, the terminal can first determine whether the first frequency domain resources of the TBoMS PUSCH are all located within the uplink subband in the conflicting time domain unit. When it is determined that the first frequency domain resources of the TBoMS PUSCH are all located within the uplink subband, the terminal can determine the second frequency domain resources within the uplink subband and then send the TBoMS PUSCH in the second frequency domain resources. Correspondingly, the network device can receive the TBoMS PUSCH on the second frequency domain resources in the conflicting time domain unit. Based on this, it can be ensured that the terminal can smoothly send the TBoMS PUSCH in the uplink subband in the conflicting time domain unit, which is conducive to reducing the delay of TBoMS PUSCH transmission.

[0299] In some embodiments, the predefined rules are used to indicate: 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 sent 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 sent in the second time domain unit.

[0300] In some embodiments, receiving a multi-slot transmission block physical uplink shared channel sent by a terminal 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 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.

[0301] Before determining the second frequency domain resource within the uplink subband, the terminal 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. When it is determined that the frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink subband, then it is not possible to determine frequency domain resources sufficient for sending TBoMS PUSCH within the uplink subband, then the terminal does not need to determine the second frequency domain resource within the uplink subband, nor does it need to send TBoMS PUSCH in the first time domain unit, but instead determines the second time domain unit to be used for sending TBoMS PUSCH; when it is determined that 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 it is possible to determine frequency domain resources sufficient for sending TBoMS PUSCH within the uplink subband, and then the terminal determines the second frequency domain resource within the uplink subband.

[0302] Regarding the method for determining the second time domain unit, reference may be made to the above embodiments, which will not be described in detail in this embodiment.

[0303] In some embodiments, the predefined rules are used to indicate: 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 sent 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 sent in the first time domain unit.

[0304] In some embodiments, a multi-slot transport block physical uplink shared channel is sent according to predefined rules, including 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 subband, 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 subband, and the physical uplink shared channel is not expected to be sent in the first time domain unit.

[0305] Before determining the second frequency domain resource within the uplink subband, the terminal 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. When it is determined that the frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink subband, then it is not possible to determine frequency domain resources sufficient for sending TBoMS PUSCH within the uplink subband, then the terminal does not need to determine the second frequency domain resource within the uplink subband, nor does it need to send TBoMS PUSCH in the first time domain unit, but instead determines the second time domain unit to be used for sending TBoMS PUSCH; when it is determined that 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 it is possible to determine frequency domain resources sufficient for sending TBoMS PUSCH within the uplink subband, and then the terminal determines the second frequency domain resource within the uplink subband.

[0306] In some embodiments, determining the second frequency domain resource within the uplink subband includes:

[0307] Within the uplink subband, frequency domain resources starting from the first frequency domain position and continuing within the first frequency domain range are determined as second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

[0308] The terminal determines the second frequency domain resource within the uplink subband and can determine the starting point and duration of the second frequency domain resource. The starting point can be the first frequency domain position within the uplink subband. For example, the first frequency domain position can be configured or indicated by the network device, or can be determined based on a protocol agreement. For example, the first frequency domain position can be the starting point or end point of the frequency domain resource corresponding to the uplink subband. The duration of the second frequency domain resource can be a first frequency domain range, which can be determined based on the first frequency domain resource of the TBoMS PUSCH in the SFBD time domain unit. For example, the first frequency domain range can be the same as the frequency domain range corresponding to the first frequency domain resource.

[0309] FIG. 7 is a schematic diagram showing a processing result according to an embodiment of the present disclosure.

[0310] 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 within the uplink subband, the physical uplink shared channel is sent in the second frequency domain resources, wherein the second frequency domain resources are entirely within the uplink subband.

[0311] In the embodiment shown in FIG6A , because the first frequency domain resources of the TBoMS PUSCH are not entirely within the uplink subband, the terminal cannot successfully transmit the TBoMS PUSCH in the conflicting time slot according to the configuration and / or scheduling of the network device. Then, as shown in FIG7 , the terminal can determine a second frequency domain resource within the conflicting time domain unit, such as the uplink subband from slot #1 to slot #3, according to predefined rules sent by the network device. The starting point of the second frequency domain resource is the starting point of the frequency domain resource corresponding to the uplink subband, 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 transmit the TBoMS PUSCH in the second frequency domain resource.

[0312] For example, if the frequency domain range corresponding to the uplink subband is RB (Resource Block, RB) #20 to RB #40, and the first frequency domain resources corresponding to the TBoMS PUSCH are RB #35 to RB #45, the terminal can determine that the first frequency domain resources are not entirely within the uplink subband and are smaller than the frequency domain range corresponding to the uplink subband. Therefore, the terminal can determine, within RB #20 to RB #40, a second frequency domain resource, RB #20 to RB #30, starting with RB #20 and lasting for 10 RBs. Furthermore, the terminal can transmit the TBoMS PUSCH within RB #20 to RB #30 within slots #1 to #3. Correspondingly, the network device can receive the TBoMS PUSCH sent by the terminal within RB #20 to RB #30 within slots #1 to #3, and still receive the TBoMS PUSCH sent by the terminal within RB #20 to RB #30 in slots #4.

[0313] In some embodiments, the predefined rule is used to indicate at least one of the following:

[0314] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and a physical uplink shared channel is sent in a first time domain unit;

[0315] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and a physical uplink shared channel is not expected to be sent in the first time domain unit;

[0316] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in a first time domain unit;

[0317] The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than the frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit.

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

[0319] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and a physical uplink shared channel is sent in a first time domain unit;

[0320] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and a physical uplink shared channel is not expected to be sent in the first time domain unit;

[0321] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in a first time domain unit;

[0322] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit;

[0323] The second time domain unit and the first time domain unit are different time domain units.

[0324] For example, the terminal may determine, according to a predefined rule, a first frequency domain interval between a first frequency domain resource corresponding to the TBoMS PUSCH and the broadcast message in the conflicting time domain unit.

[0325] 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 the 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 greater 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 conducive to ensuring relatively good communication quality.

[0326] 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 the impact on communication quality is small. Therefore, the terminal can send TBoMS PUSCH in the conflicting time domain unit.

[0327] For example, the terminal may determine, according to a predefined rule, a first frequency domain interval between the uplink subband and the broadcast message in the conflicting time domain unit.

[0328] 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, receives the TBoMS PUSCH in the uplink subband of the time domain unit, and sends a broadcast message. The frequency domain interference between the TBoMS PUSCH and the broadcast message is relatively large, which has a greater 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 conducive to ensuring relatively good communication quality.

[0329] 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 the impact on communication quality is small. Therefore, the terminal can send TBoMS PUSCH in the conflicting time domain unit.

[0330] Regarding the method for determining the second time domain unit, reference may be made to the above embodiments, which will not be described in detail in this embodiment.

[0331] In some embodiments, the predefined rule is used to indicate at least one of the following:

[0332] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and a physical uplink shared channel is sent in a first time domain unit;

[0333] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not desired to send a physical uplink shared channel in the first time domain unit;

[0334] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in a first time domain unit;

[0335] The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit.

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

[0337] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and a physical uplink shared channel is sent in a first time domain unit;

[0338] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not desired to send a physical uplink shared channel in the first time domain unit;

[0339] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in a first time domain unit;

[0340] The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit.

[0341] For example, the terminal may determine, according to a predefined rule, a first frequency domain interval between a first frequency domain resource corresponding to the TBoMS PUSCH and the broadcast message in the conflicting time domain unit.

[0342] 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 the 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 greater impact on the communication quality. Therefore, the terminal does not expect to send the TBoMS PUSCH in the conflicting time domain unit, which is conducive to ensuring relatively good communication quality.

[0343] 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 the impact on communication quality is small. Therefore, the terminal can send TBoMS PUSCH in the conflicting time domain unit.

[0344] For example, the terminal may determine, according to a predefined rule, a first frequency domain interval between the uplink subband and the broadcast message in the conflicting time domain unit.

[0345] 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, receives the TBoMS PUSCH in the uplink subband of the time domain unit, and sends a broadcast message. The frequency domain interference between the TBoMS PUSCH and the broadcast message is relatively large, which has a greater impact on the communication quality. Therefore, the terminal does not expect to send the TBoMS PUSCH in the conflicting time domain unit, which is conducive to ensuring relatively good communication quality.

[0346] 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 the impact on communication quality is small. Therefore, the terminal can send TBoMS PUSCH in the conflicting time domain unit.

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

[0348] For example, the number of time domain units occupied by the TBoMS PUSCH is n. When, in the current TDD cycle, the terminal does not expect to send the TBoMS PUSCH in m (for example, m is an integer less than or equal to n) conflicting time domain units, the terminal needs to determine the m nearest available time domain units after the current TDD cycle to send the TBoMS PUSCH to ensure that the number of time domain units occupied by the TBoMS PUSCH is n. Correspondingly, the network device does not expect to receive the 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 the TBoMS PUSCH sent by the terminal.

[0349] For example, in the embodiment shown in FIG6A , one TDD cycle includes 5 time slots.

[0350] When TBoMS PUSCH is sent in the manner of the embodiment shown in FIG6B , only the 5th time slot in a cycle can be used to send TBoMS PUSCH. Since TBoMS PUSCH is sent in at least 3 time slots, the three nearest available time slots after the cycle are the 5th time slots of each of the 3 cycles after the cycle. Therefore, TBoMS PUSCH can be sent in the 5th time slot of each of the 3 cycles after the cycle, thereby satisfying the requirement of sending TBoMS PUSCH in 4 time slots. Correspondingly, the network device receives TBoMS PUSCH sent by the terminal in the 5th time slot of each of the 3 cycles after the current cycle.

[0351] When TBoMS PUSCH is sent in the manner of the embodiment shown in FIG6C , the 3rd to 5th time slots in a cycle can be used to send TBoMS PUSCH. Since TBoMS PUSCH is sent in one less time slot, it can be determined that the nearest available time slot after the cycle is the 3rd time slot in the next cycle. Then, TBoMS PUSCH can be sent in the 3rd time slot in the next cycle, thereby satisfying the requirement of sending TBoMS PUSCH in 4 time slots. Correspondingly, the network device receives the TBoMS PUSCH sent by the terminal in the 3rd time slot in the next cycle.

[0352] In a second aspect, an embodiment of the present disclosure proposes an uplink communication processing method. FIG8 is a schematic flow chart of 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. As shown in FIG8, the uplink communication processing method may include the following steps:

[0353] In step S801, a multi-slot transport block physical uplink shared channel (PUSCH) transmitted by a terminal is received according to a predefined rule, wherein the multi-slot transport block PUSCH collides with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a subband. For example, the predefined rule may be determined by a base protocol agreement.

[0354] It should be noted that the embodiment shown in FIG8 can be implemented independently or in combination with at least one other embodiment in the present disclosure. The specific selection can be made as needed and the present disclosure does not limit it.

[0355] In some embodiments, when a TBoMS PUSCH collides with a broadcast message of a network device in a certain time domain unit, the terminal may not expect to send a TBoMS PUSCH in the time domain unit.

[0356] However, when the TBoMS PUSCH conflicts with the broadcast message in a time domain unit configured with a subband (hereinafter referred to as the SBFD time domain unit), since the subband is configured in the SBFD time domain unit, the terminal can perform both uplink and downlink communications in the SBFD time domain unit. If the above implementation method is still used and TBoMS PUSCH is not expected to be sent on the time domain unit, it will make it difficult to apply the TBoMS technology in the SBFD time domain unit, limiting the uplink coverage gain brought by the SBFD technology.

[0357] In some embodiments, the collision comprises at least one of: determining that a collision is occurring; and predicting that a collision will occur in a future time domain unit.

[0358] According to an embodiment of the present disclosure, the network device can determine, based on predefined rules, how to handle the TBoMS PUSCH when the TBoMS PUSCH conflicts with a broadcast message in a SBFD time domain unit. Accordingly, the network device may not default to not expecting to receive the TBoMS PUSCH sent by the terminal on the SBFD time domain unit, but may determine how to handle the TBoMS PUSCH based on predefined rules. For example, the TBoMS PUSCH sent by the terminal may be received on the SBFD time domain unit, or the TBoMS PUSCH sent by the terminal may not be expected to be received on the SBFD time domain unit. Accordingly, in some SBFD time domain units, even if the TBoMS PUSCH conflicts with a broadcast message, the TBoMS technology can be applied, which is beneficial to ensure the uplink coverage gain brought about by receiving the TBoMS PUSCH in the SBFD time slot.

[0359] In some embodiments, the broadcast message includes at least one of: 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, the common search space includes, but is not limited to, a Type-0 PDCCH CSS.

[0360] In some embodiments, the physical uplink shared channel and the broadcast message collide in a time domain unit configured with a subband, including at least one of the following:

[0361] 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;

[0362] The first time domain resource of the physical uplink shared channel in the time domain unit and the second time domain resource of the broadcast message in the time domain unit completely overlap;

[0363] The physical uplink shared channel and the broadcast message are in the same time domain unit.

[0364] 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 conflicts with SSB in the SBFD time slot, and then determine how to handle TBoMS PUSCH according to predefined rules.

[0365] 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 conflicts with SSB in the SBFD time slot, and then determine how to handle TBoMS PUSCH according to predefined rules.

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

[0367] In some embodiments, the predefined rules are used to indicate that: 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; 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 received in the time domain unit.

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

[0369] 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 the time domain unit;

[0370] 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 received in the time domain unit.

[0371] In some embodiments, the network device may determine, according to a predefined rule, to receive the physical uplink shared channel in a time domain unit when all first frequency domain resources of the physical uplink shared channel are located within the uplink sub-band.

[0372] Based on predefined rules, the network device can determine whether the first frequency domain resources of the TBoMS PUSCH are all located within the uplink sub-band in the conflicting time domain unit. When the first frequency domain resources of the TBoMS PUSCH are all located within the uplink sub-band, 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 the TBoMS PUSCH are not all located within the uplink sub-band, 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 the TBoMS PUSCH in the conflicting time domain unit.

[0373] As shown in Figure 5, for example, an SSB burst includes eight SSB candidates, and the network device sends an SSB on each SSB candidate. The eight SSB candidates are distributed across slots 0 to 3, with two SSB candidates in each time slot.

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

[0375] Since the network device transmits SSB in slots #1 to #3 and also needs to receive TBoMS PUSCH in the uplink subbands in slots #1 to #3, the network device may determine that TBoMS PUSCH and SSB collide in slots #1 to #3.

[0376] In some embodiments, the predefined rule is used to indicate that when all first frequency domain resources of the physical uplink shared channel are located within the uplink sub-band, the physical uplink shared channel is received in the time domain unit.

[0377] In the embodiment shown in Figure 5, 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 based on the configuration and / or scheduling of the terminal. The network device can determine, based on predefined rules, to receive the TBoMS PUSCH sent by the terminal in the conflicting time domain units, i.e., slots #1 to #3. Of course, the TBoMS PUSCH sent by the terminal can also be received in the non-conflicting time domain unit, i.e., slot #4. Correspondingly, the terminal can send the TBoMS PUSCH in slots #1 to #4.

[0378] In the embodiment shown in FIG6A , because the first frequency domain resources of the TBoMS PUSCH are not entirely within the uplink subband, the network device cannot successfully receive the TBoMS PUSCH sent by the terminal in the conflicting time slot according to the configuration and / or scheduling of the terminal. As shown in FIG6B , the network device can determine, based on predefined rules, not to receive the TBoMS PUSCH sent by the terminal in the conflicting time domain units, such as slots #1 to #3, and only receive the TBoMS PUSCH sent by the terminal in slot #4. Correspondingly, the terminal may not expect to send the TBoMS PUSCH in slots #1 to #3, but may instead send the TBoMS PUSCH in slot #4.

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

[0380] In the case of the embodiment shown in FIG6A , 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 the downlink time slot configured with the subband (e.g., slot#1) according to the terminal configuration and / or scheduling. However, in the flexible time slot configured with the subband (e.g., slot#2), the network device may still be able to successfully receive the TBoMS PUSCH sent by the terminal according to 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). Then, as shown in FIG6C , the network device may determine that the downlink time domain unit configured with the subband in the conflicting time domain unit, such as slot#1, does not receive the TBoMS PUSCH sent by the terminal, but in the flexible time domain unit configured with the subband in the conflicting time domain unit, such as slot#2 and slot#3, the TBoMS PUSCH sent by the terminal may be received. Of course, the TBoMS PUSCH sent by the terminal may also be received in slot#4. Correspondingly, the terminal may not expect to send the TBoMS PUSCH in slot #1, but may send the TBoMS PUSCH in slot #2 to slot #4.

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

[0382] In some embodiments, when the first frequency domain resources of the TBoMS PUSCH are not all located within the uplink subband, whether to send the TBoMS PUSCH in the flexible time domain unit configured with the subband in the conflicting time domain unit, for example, in the case of Figure 6A, according to the example processing of Figure 6B or according to the example processing of Figure 6C, can be determined by the network device and indicated to the terminal, or can be determined according to the protocol agreement.

[0383] In some embodiments, the predefined rules are used to indicate that: 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.

[0384] In some embodiments, the network device receives a multi-slot transmission block physical uplink shared channel according to a predefined rule, 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 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; wherein the second time domain unit and the first time domain unit are different time domain units.

[0385] For example, the second time domain includes the nearest available time domain unit (eg, a time domain unit that does not conflict with the broadcast message and has uplink frequency domain resources), and may also include a time domain unit that does not conflict among the time domain units used to send the TBoMS PUSCH.

[0386] For example, TBoMS PUSCH is sent in the manner of the embodiment shown in Figure 6B. In one cycle, only the 5th time slot can be used to send TBoMS PUSCH. Since TBoMS PUSCH is sent in at least 3 time slots, the three nearest available time slots after the cycle are the 5th time slot of each of the 3 cycles after the cycle. Then, the 5th time slot of each of the 3 cycles after the cycle can be used as the second time domain unit for sending TBoMS PUSCH, thereby satisfying the requirement of sending TBoMS PUSCH in 4 time slots.

[0387] For example, if TBoMS PUSCH is sent in the manner of the embodiment shown in FIG6C , the 3rd to 5th time slots in a cycle can be used to send TBoMS PUSCH. Since TBoMS PUSCH is sent in one less time slot, it can be determined that the nearest available time slot after the cycle is the 3rd time slot in the next cycle. Then, the 3rd time slot in the next cycle can be used as the second time domain unit for sending TBoMS PUSCH, thereby satisfying the requirement of sending TBoMS PUSCH in 4 time slots. Correspondingly, the terminal sends TBoMS PUSCH in the 3rd time slot in the next cycle.

[0388] 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 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 within the uplink subband.

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

[0390] In some embodiments, the network device receives the physical uplink shared channel in a second frequency domain resource according to a predefined rule when the first frequency domain resource of the physical uplink shared channel is not entirely within the uplink subband, wherein the second frequency domain resource is entirely within the uplink subband.

[0391] Based on predefined rules, the network device can determine whether the first frequency domain resources of the TBoMS PUSCH are all located within the uplink subband in the conflicting time domain unit. When the first frequency domain resources of the TBoMS PUSCH are all located 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 the TBoMS PUSCH on the second frequency domain resources in the conflicting time domain unit. Based on this, it can be ensured that the network device can smoothly receive the TBoMS PUSCH sent by the terminal in the uplink subband in the conflicting time domain unit, which is conducive to reducing the latency of TBoMS PUSCH reception.

[0392] In some embodiments, the predefined rules are used to indicate: 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 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, the physical uplink shared channel is received in the second time domain unit.

[0393] In some embodiments, receiving a multi-slot transmission block physical uplink shared channel sent by a terminal 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 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 and the first time domain unit are different time domain units.

[0394] Before determining the second frequency domain resource within the uplink sub-band, 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 sub-band. When it is determined that the frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink sub-band, then it is not possible to determine frequency domain resources sufficient for receiving the TBoMS PUSCH within the uplink sub-band. In this case, the network device does not need to determine the second frequency domain resource within the uplink sub-band, nor does it need to receive the TBoMS PUSCH in the first time domain unit. Instead, it determines that the second time domain unit is used to send the TBoMS PUSCH. When it is determined that 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, then it is possible to determine frequency domain resources sufficient for receiving the TBoMS PUSCH within the uplink sub-band. Only then will the network device determine the second frequency domain resource within the uplink sub-band.

[0395] Regarding the method for determining the second time domain unit, reference may be made to the above embodiments, which will not be described in detail in this embodiment.

[0396] In some embodiments, the predefined rules are used to indicate: 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 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, the physical uplink shared channel is not expected to be received in the first time domain unit.

[0397] In some embodiments, a multi-slot transport block physical uplink shared channel is sent according to predefined rules, including 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 subband, 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 subband, and the physical uplink shared channel is not expected to be received in the first time domain unit.

[0398] 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. When the frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink subband, then sufficient frequency domain resources cannot be determined within the uplink subband for receiving the TBoMS PUSCH sent by the terminal, and the network device does not need to determine the second frequency domain resource within the uplink subband, which helps to avoid wasting the resources of the network device; when 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 can be determined within the uplink subband for receiving the TBoMS PUSCH sent by the terminal, and the network device will then determine the second frequency domain resource within the uplink subband.

[0399] In some embodiments, determining the second frequency domain resource within the uplink subband includes: determining the frequency domain resource within the uplink subband starting from the first frequency domain position and continuing the 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.

[0400] In the embodiment shown in FIG6A , since the first frequency domain resources of the TBoMS PUSCH are not entirely within the uplink subband, the network device cannot successfully receive the TBoMS PUSCH sent by the terminal in the conflicting time slot according to the terminal configuration and / or scheduling. Then, as shown in FIG7 , the network device can predefine rules to determine the second frequency domain resources within the conflicting time domain unit, such as the uplink subband of slot#1 to slot#3, wherein the starting point of the second frequency domain resources is the starting point of the frequency domain resources corresponding to the uplink subband, and the first frequency domain range is the same as the frequency domain range corresponding to the first frequency domain resources. Thus, the network device can receive the TBoMS PUSCH sent by the terminal in the second frequency domain resources.

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

[0402] In some embodiments, the predefined rule is used to indicate at least one of the following:

[0403] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and a physical uplink shared channel is sent in a first time domain unit;

[0404] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and a physical uplink shared channel is not expected to be sent in the first time domain unit;

[0405] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in a first time domain unit;

[0406] The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than the frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit.

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

[0408] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and a physical uplink shared channel is sent in a first time domain unit;

[0409] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and a physical uplink shared channel is not expected to be sent in the first time domain unit;

[0410] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in a first time domain unit;

[0411] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit;

[0412] The second time domain unit and the first time domain unit are different time domain units.

[0413] For example, the network device may determine, according to a predefined rule, a first frequency domain interval between a first frequency domain resource corresponding to the TBoMS PUSCH and the broadcast message in the conflicting time domain unit.

[0414] When the first frequency domain interval is less than the frequency domain interval threshold, the network device sends the broadcast message in the conflicting time domain unit and receives the 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 greater 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 conducive to ensuring relatively good communication quality.

[0415] 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 the impact on communication quality is small. Therefore, the network device can receive TBoMS PUSCH in the conflicting time domain unit.

[0416] For example, the network device may determine, according to a predefined rule, a first frequency domain interval between the uplink subband and the broadcast message in the conflicting time domain unit.

[0417] 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, receives the TBoMS PUSCH in the uplink subband of the time domain unit, and sends a broadcast message. The frequency domain interference between the TBoMS PUSCH and the broadcast message is relatively large, which has a greater impact on the communication quality. Therefore, the network device can determine a second time domain unit and receive the TBoMS PUSCH in the second time domain unit, which is conducive to ensuring relatively good communication quality.

[0418] 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 the impact on communication quality is small. Therefore, the network device can receive TBoMS PUSCH in the conflicting time domain unit.

[0419] Regarding the method for determining the second time domain unit, reference may be made to the above embodiments, which will not be described in detail in this embodiment.

[0420] In some embodiments, the predefined rule is used to indicate at least one of the following:

[0421] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and a physical uplink shared channel is sent in a first time domain unit;

[0422] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not desired to send a physical uplink shared channel in the first time domain unit;

[0423] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in a first time domain unit;

[0424] The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit.

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

[0426] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and a physical uplink shared channel is sent in a first time domain unit;

[0427] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not desired to send a physical uplink shared channel in the first time domain unit;

[0428] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in a first time domain unit;

[0429] The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit.

[0430] For example, the network device may first determine, according to a predefined rule, a first frequency domain interval between a first frequency domain resource corresponding to the TBoMS PUSCH and a broadcast message in a conflicting time domain unit.

[0431] When the first frequency domain interval is less than the frequency domain interval threshold, since the network device sends a broadcast message in the conflicting time domain unit and receives the 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 greater impact on the communication quality. Therefore, the network device does not expect to receive the 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 send the TBoMS PUSCH in the conflicting time domain unit;

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

[0433] For example, the network device may first determine a first frequency domain interval between the uplink subband and the broadcast message in the conflicting time domain unit according to a predefined rule.

[0434] When the first frequency domain interval is less than the frequency domain interval threshold, since the network device sends a broadcast message in the conflicting time domain unit, and receives the TBoMS PUSCH and sends the broadcast message in the uplink subband of the time domain unit, the frequency domain interference between the TBoMS PUSCH and the broadcast message is relatively large, which has a greater impact on the communication quality. Therefore, the network device does not expect to receive the 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 the TBoMS PUSCH in the conflicting time domain unit;

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

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

[0437] For example, the number of time domain units occupied by TBoMS PUSCH is n. When, in the current TDD cycle, the network device does not expect to receive TBoMS PUSCH in m (for example, m is an integer less than or equal to n) conflicting time domain units, the network device needs to determine the m nearest available time domain units after the current TDD cycle to receive TBoMS PUSCH to ensure 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 sends TBoMS PUSCH in the m nearest available time domain units after the current TDD cycle.

[0438] For example, in the embodiment shown in FIG6A , one TDD cycle includes 5 time slots.

[0439] When TBoMS PUSCH is sent in the manner of the embodiment shown in FIG6B , only the 5th time slot in a cycle can be used to receive TBoMS PUSCH. Since TBoMS PUSCH is received in at least 3 time slots, the three nearest available time slots after the cycle are the 5th time slots of each of the 3 cycles after the cycle. Therefore, the network device can receive TBoMS PUSCH in the 5th time slot of each of the 3 cycles after the cycle, thereby satisfying the requirement of receiving TBoMS PUSCH in 4 time slots. Correspondingly, the terminal sends TBoMS PUSCH in the 5th time slot of each of the 3 cycles after the current cycle.

[0440] When TBoMS PUSCH is sent in the manner of the embodiment shown in FIG6C , the 3rd to 5th time slots in a cycle can be used to receive TBoMS PUSCH. Since TBoMS PUSCH is received in at least one time slot, it can be determined that the nearest available time slot after the cycle is the 3rd time slot in the next cycle. Then, the network device can receive TBoMS PUSCH in the 3rd time slot in the next cycle, thereby meeting the requirement of receiving TBoMS PUSCH in 4 time slots. Correspondingly, the terminal sends TBoMS PUSCH in the 3rd time slot in the next cycle.

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

[0442] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0443] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

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

[0445] In some embodiments, the terms "search space", "search space set", "search space configuration", "search space set configuration", "control resource set (CORESET)", "CORESET configuration" and the like may be used interchangeably.

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

[0447] In some embodiments, terms such as "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.

[0448] In some embodiments, terms such as "frame", "radio frame", "subframe", "slot", "sub-slot", "mini-slot", "symbol", "symbol", and "transmission time interval (TTI)" can be used interchangeably.

[0449] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0450] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0451] 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 recipient to respond to the content sent.

[0452] Corresponding to the aforementioned embodiment of the uplink communication processing method, the present disclosure also provides embodiments of a terminal and a network device.

[0453] An embodiment of the present disclosure further proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the uplink communication processing method described in the above-mentioned first aspect and the optional embodiment of the first aspect.

[0454] FIG9 is a schematic block diagram of a terminal according to an embodiment of the present disclosure. As shown in FIG9 , the terminal includes: a processing module 901 .

[0455] In some embodiments, the processing module is configured to send a multi-slot transport block physical uplink shared channel according to a predefined rule, wherein the multi-slot transport block physical uplink shared channel collides with the broadcast message in a first time domain unit, wherein the first time domain unit is configured with a subband.

[0456] In some embodiments, the processing module is configured to at least one of:

[0457] 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 sent in the first time domain unit;

[0458] 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 sent in the second time domain unit;

[0459] The second time domain unit and the first time domain unit are different time domain units.

[0460] In some embodiments, the processing module is configured to at least one of:

[0461] 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 sent in the first time domain unit;

[0462] 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 send the physical uplink shared channel in the first time domain unit.

[0463] In some embodiments, the processing module is configured to determine a second frequency domain resource within the uplink subband if all of the first frequency domain resources of the physical uplink shared channel are not located within the uplink subband;

[0464] A physical uplink shared channel is sent in the second frequency domain resources.

[0465] In some embodiments, the processing module is used to determine, within the uplink subband, frequency domain resources starting from the first frequency domain position and continuing the first frequency domain range as second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

[0466] In some embodiments, the processing module is further configured to:

[0467] The frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the uplink subband, and the physical uplink shared channel is sent in the first time domain unit;

[0468] The frequency domain range of the first frequency domain resource is larger than the frequency domain range of the uplink subband, and the physical uplink shared channel is sent in the second time domain unit;

[0469] The second time domain unit and the first time domain unit are different time domain units.

[0470] In some embodiments, the processing module is configured to at least one of:

[0471] The frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the uplink subband, and the physical uplink shared channel is sent in the first time domain unit;

[0472] 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 send a physical uplink shared channel in the first time domain unit.

[0473] In some embodiments, the processing module is configured to at least one of:

[0474] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and a physical uplink shared channel is sent in a first time domain unit;

[0475] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and a physical uplink shared channel is not expected to be sent in the first time domain unit;

[0476] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in a first time domain unit;

[0477] The first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit;

[0478] The second time domain unit and the first time domain unit are different time domain units.

[0479] In some embodiments, the processing module is configured to at least one of:

[0480] A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and a physical uplink shared channel is sent in a first time domain unit;

[0481] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not desired to send a physical uplink shared channel in the first time domain unit;

[0482] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in a first time domain unit;

[0483] The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit.

[0484] In some embodiments, the second time domain unit is not configured with a subband.

[0485] In some embodiments, the physical uplink shared channel and the broadcast message collide in a time domain unit configured with a subband, including at least one of the following:

[0486] A first time domain resource of the physical uplink shared channel in a time domain unit configured with a subband partially overlaps with a second time domain resource of the broadcast message in the time domain unit;

[0487] The first time domain resource of the physical uplink shared channel in the time domain unit configured with the subband and the second time domain resource of the broadcast message in the time domain unit completely overlap;

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

[0489] In some embodiments, the broadcast message collision comprises at least one of: a synchronization signal block; a common search space.

[0490] It should be noted that, in addition to the modules of the above embodiments, the network device shown in FIG. 9 may also include other modules, such as a communication module and a storage module, and the embodiments of the present disclosure are not limited to this.

[0491] An embodiment of the present disclosure further proposes a network device, comprising: one or more processors; wherein the network device is used to execute the uplink communication processing method described in the above-mentioned second aspect and the optional embodiment of the second aspect.

[0492] FIG10 is a schematic block diagram of a network device according to an embodiment of the present disclosure. As shown in FIG10 , the network device includes: a processing module 1001 .

[0493] In some embodiments, the processing module is used to receive a multi-slot transport block physical uplink shared channel sent by a terminal according to a predefined rule, wherein the multi-slot transport block physical uplink shared channel collides with the broadcast message in a first time domain unit, wherein the first time domain unit is configured with a subband.

[0494] In some embodiments, the processing module is configured to at least one of:

[0495] 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;

[0496] 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 the second time domain unit;

[0497] The second time domain unit and the first time domain unit are different time domain units.

[0498] In some embodiments, the processing module is configured to at least one of:

[0499] 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;

[0500] 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 received in the first time domain unit.

[0501] In some embodiments, the processing module is configured to determine a second frequency domain resource within the uplink subband if all of the first frequency domain resources of the physical uplink shared channel are not located within the uplink subband;

[0502] A physical uplink shared channel is received in the second frequency domain resources.

[0503] In some embodiments, the processing module is used to determine, within the uplink subband, frequency domain resources starting from the first frequency domain position and continuing the first frequency domain range as second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

[0504] In some embodiments, the processing module is further configured to:

[0505] The frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the uplink subband, and the physical uplink shared channel is received in the first time domain unit;

[0506] The frequency domain range of the first frequency domain resource is greater than the frequency domain range of the uplink subband, and the physical uplink shared channel is received in the second time domain unit;

[0507] The second time domain unit and the first time domain unit are different time domain units.

[0508] In some embodiments, the processing module is configured to at least one of:

[0509] The frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the uplink subband, and the physical uplink shared channel is received in the first time domain unit;

[0510] 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 not expected to be received in the first time domain unit.

[0511] In some embodiments, the processing module is configured to:

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

[0513] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and reception of a physical uplink shared channel is not expected in the first time domain unit;

[0514] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is received in a first time domain unit;

[0515] The first frequency domain interval between the physical uplink shared channel 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;

[0516] The second time domain unit and the first time domain unit are different time domain units.

[0517] In some embodiments, the processing module is configured to at least one of:

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

[0519] A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not desired to receive the physical uplink shared channel in the first time domain unit;

[0520] A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is received in a first time domain unit;

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

[0522] In some embodiments, the second time domain unit is not configured with a subband.

[0523] In some embodiments, the physical uplink shared channel and the broadcast message collide in a time domain unit configured with a subband, including at least one of the following:

[0524] A first time domain resource of the physical uplink shared channel in a time domain unit configured with a subband partially overlaps with a second time domain resource of the broadcast message in the time domain unit;

[0525] The first time domain resource of the physical uplink shared channel in the time domain unit configured with the subband and the second time domain resource of the broadcast message in the time domain unit completely overlap;

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

[0527] In some embodiments, the broadcast message collision comprises at least one of: a synchronization signal block; a common search space.

[0528] It should be noted that, in addition to the modules of the above embodiments, the network device shown in FIG10 may also include other modules, such as a communication module and a storage module, and the embodiments of the present disclosure are not limited to this.

[0529] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can be referred to the partial description of the method embodiment. The device embodiment described above is merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art can understand and implement it without paying any creative work.

[0530] An embodiment of the present disclosure also proposes an uplink communication processing method, which includes: a terminal sends a multi-slot transmission block physical uplink shared channel according to a predefined rule, wherein the multi-slot transmission 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 subband; and a network device receives the multi-slot transmission block physical uplink shared channel sent by the terminal according to the predefined rule.

[0531] An embodiment of the present disclosure further proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the uplink communication processing method described in the above-mentioned first aspect and the optional embodiment of the first aspect.

[0532] An embodiment of the present disclosure further proposes a network device, comprising: one or more processors; wherein the network device is used to execute the uplink communication processing method described in the second aspect and the optional embodiment of the second aspect.

[0533] An embodiment of the present disclosure also proposes a communication device, comprising: one or more processors; wherein the processor is used to call instructions to enable the communication device to execute the uplink communication processing method described in the first aspect, the second aspect, the optional embodiment of the first aspect, and the optional embodiment of the second aspect.

[0534] An embodiment of the present disclosure also proposes 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 the optional embodiment of the first aspect, and the network device is configured to implement the uplink communication processing method described in the second aspect and the optional embodiment of the second aspect.

[0535] An embodiment of the present disclosure also proposes a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes the uplink communication processing method described in the first aspect, the second aspect, the optional embodiment of the first aspect, and the optional embodiment of the second aspect.

[0536] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0537] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0538] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution 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 relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by 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 implementing the hardware circuit configuration 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. In addition, 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), a deep learning processing unit (DPU), etc.

[0539] Figure 11 is a schematic diagram of the structure of a communication device 11100 proposed in an embodiment of the present disclosure. Communication device 11100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 11100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0540] As shown in Figure 11, the communication device 11100 includes one or more processors 11101. The processor 11101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The processor 11101 is used to call instructions to enable the communication device 11100 to perform any of the above methods.

[0541] 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 be located outside the communication device 11100.

[0542] 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 transceiver 11103, and the other steps are performed by the processor 11101.

[0543] 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, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

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

[0545] 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 the present disclosure is not limited thereto, and the structure of the communication device 11100 may not be limited by FIG. 11 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0546] FIG12 is a schematic diagram of the structure of a chip 12200 according to an embodiment of the present disclosure. If the communication device 11100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 12200 shown in FIG12 , but the present disclosure is not limited thereto.

[0547] The chip 12200 includes one or more processors 12201 , and the processor 12201 is used to call instructions so that the chip 12200 executes any of the above methods.

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

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

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

[0551] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the communication device 11100, the communication device 11100 is caused to execute 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 is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0552] The present disclosure also provides a program product, which, when executed by the communication device 11100, enables the communication device 11100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0553] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A method for processing uplink communication, characterized in that: The method comprises: A multi-slot transport block physical uplink shared channel is sent according to a predefined rule, wherein the multi-slot transport block physical uplink shared channel collides with a broadcast message in a first time domain unit, and the first time domain unit is configured with an uplink subband.

2. The method according to claim 1, characterized in that The sending of the multi-slot transport block physical uplink shared channel according to a predefined rule comprises 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 sent in the first time domain unit; 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 sent in the second time domain unit; The second time domain unit and the first time domain unit are different time domain units.

3. The method according to claim 1, characterized in that The sending of the multi-slot transport block physical uplink shared channel according to a predefined rule comprises 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 sent 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 send the physical uplink shared channel in the first time domain unit.

4. The method according to claim 1, characterized in that: The sending of a multi-slot transport block physical uplink shared channel according to a predefined rule comprises: The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and a second frequency domain resource is determined within the uplink sub-band; The physical uplink shared channel is sent in the second frequency domain resources.

5. The method according to claim 4, characterized in that The determining of the second frequency domain resource within the uplink subband includes: A frequency domain resource of a continuous first frequency domain range with a first frequency domain position as a starting point is determined within the uplink subband as the second frequency domain resource, wherein 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 receiving, according to a predefined rule, a multi-slot transport block physical uplink shared channel sent by a terminal, further comprises at least one of the following: The frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the uplink subband, 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 subband, and the physical uplink shared channel is sent in the second time domain unit; The second time domain unit and the first time domain unit are different time domain units.

7. The method according to any one of claims 4 to 5, characterized in that The sending of the multi-slot transport block physical uplink shared channel according to a predefined rule comprises at least one of the following: The frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the uplink subband, 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 larger than the frequency domain range of the uplink sub-band, and the physical uplink shared channel is not expected to be sent in the first time domain unit.

8. The method according to claim 1, characterized in that The sending of the multi-slot transport block physical uplink shared channel according to a predefined rule comprises at least one of the following: A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit; A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit; A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit; The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be sent in the first time domain unit; The second time domain unit and the first time domain unit are different time domain units.

9. The method according to claim 1, characterized in that: The sending of the multi-slot transport block physical uplink shared channel according to a predefined rule comprises at least one of the following: A first frequency domain interval between the uplink subband and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit; A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit; A first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to a frequency domain interval threshold, and the physical uplink shared channel is sent in the first time domain unit; The first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to send the physical uplink shared channel in the first time domain unit.

10. The method according to any one of claims 2, 6 and 8, characterized in that: The second time domain unit is not configured with a subband.

11. The method according to any one of claims 1 to 10, characterized in that The physical uplink shared channel and the broadcast message conflict in a time domain unit configured with a subband, including at least one of the following: A first time domain resource of the physical uplink shared channel in the time domain unit configured with the subband partially overlaps with a second time domain resource of the broadcast message in the first time domain unit; The first time domain resource of the physical uplink shared channel in the time domain unit configured with the subband and the second time domain resource of the broadcast message in the first time domain unit completely overlap; The physical uplink shared channel and the broadcast message are in the same time domain unit configured with subbands.

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

13. A method for processing uplink communication, characterized in that: The method comprises: A multi-slot transport block physical uplink shared channel sent by a terminal is received according to a predefined rule, wherein the multi-slot transport block physical uplink shared channel collides with a broadcast message in a first time domain unit, wherein the first time domain unit is configured with a subband.

14. The method according to claim 13, characterized in that The receiving, according to a predefined rule, a multi-slot transport block physical uplink shared channel sent by a terminal comprises 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 and the first time domain unit are different time domain units.

15. The method according to claim 13, characterized in that The receiving, according to a predefined rule, a multi-slot transport block physical uplink shared channel sent by a terminal comprises 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 not expected to be received in the first time domain unit.

16. The method according to claim 13, characterized in that The receiving, according to a predefined rule, a multi-slot transmission block physical uplink shared channel sent by a terminal comprises: The first frequency domain resources of the physical uplink shared channel are not all located within the uplink sub-band, and a second frequency domain resource is determined within the uplink sub-band; The physical uplink shared channel is received in the second frequency domain resources.

17. The method according to claim 16, characterized in that The determining of the second frequency domain resource within the uplink subband includes: The frequency domain resources starting from the first frequency domain position and continuing in the first frequency domain range are determined within the uplink subband as the second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

18. The method according to any one of claims 16 to 17, characterized in that The receiving, according to a predefined rule, a multi-slot transport block physical uplink shared channel sent by a terminal, further comprises at least one of the following: The frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the uplink subband, 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 subband, and the physical uplink shared channel is received in the second time domain unit; The second time domain unit and the first time domain unit are different time domain units.

19. The method according to any one of claims 16 to 17, characterized in that The receiving, according to a predefined rule, a multi-slot transport block physical uplink shared channel sent by a terminal comprises at least one of the following: The frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the uplink subband, 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 not expected to be received in the first time domain unit.

20. The method according to claim 13, characterized in that The receiving, according to a predefined rule, a multi-slot transport block physical uplink shared channel sent by a terminal comprises at least one of the following: A first frequency domain interval between the uplink subband 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; A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be received in the first time domain unit; A first frequency domain interval between the physical uplink shared channel 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 physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and the physical uplink shared channel is not expected to be received in the first time domain unit; The second time domain unit and the first time domain unit are different time domain units.

21. The method according to claim 13, characterized in that The receiving, according to a predefined rule, a multi-slot transport block physical uplink shared channel sent by a terminal comprises at least one of the following: A first frequency domain interval between the uplink subband 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; A first frequency domain interval between the uplink subband and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to receive the physical uplink shared channel in the first time domain unit; A first frequency domain interval between the physical uplink shared channel 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 physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold, and it is not expected to receive the physical uplink shared channel in the first time domain unit.

22. The method according to any one of claims 14, 18 and 20, characterized in that: The second time domain unit is not configured with a subband.

23. The method according to any one of claims 13 to 22, characterized in that The physical uplink shared channel and the broadcast message conflict in a time domain unit configured with a subband, including at least one of the following: A first time domain resource of the physical uplink shared channel in the time domain unit configured with the subband partially overlaps with a second time domain resource of the broadcast message in the first time domain unit; The first time domain resource of the physical uplink shared channel in the time domain unit configured with the subband and the second time domain resource of the broadcast message in the first time domain unit completely overlap; The physical uplink shared channel and the broadcast message are in the same time domain unit configured with subbands.

24. The method according to any one of claims 13 to 23, characterized in that The broadcast message conflict includes at least one of the following: Synchronous signal block; Public search space.

25. A method for processing uplink communication, characterized in that: The method comprises: The terminal sends a multi-slot transport block physical uplink shared channel according to a predefined rule, wherein the multi-slot 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 subband; The network device receives the multi-slot transmission block physical uplink shared channel sent by the terminal according to a predefined rule.

26. 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 to 12.

27. A network device, characterized in that: include: one or more processors; Wherein, the network device is used to execute the uplink communication processing method described in any one of claims 13 to 24.

28. A communication device, characterized in that: include: one or more processors; The processor is used to call instructions so that the communication device executes the uplink communication processing method described in any one of claims 1-12 and 13 to 24.

29. A communication system, characterized in that: It comprises a terminal and a network device, wherein the terminal is configured to implement the uplink communication processing method described in any one of claims 1-12, and the network device is configured to implement the uplink communication processing method described in any one of claims 13 to 24.

30. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device executes the uplink communication processing method according to any one of claims 1 to 12 and 13 to 24.

Images