Uplink communication processing method, communication device, and storage medium

Abstract

The present disclosure relates to the technical field of communications, and particularly relates to an uplink communication processing method, a communication device, and a storage medium. The uplink communication processing method comprises: if a physical uplink shared channel (PUSCH) conflicts with a broadcast message in a time domain unit configured with a sub-band, determining a processing mode for the PUSCH according to first indication information of a network device, wherein the PUSCH is transmitted on the basis of transport block processing over multiple slots (TBoMS). In the present disclosure, in some SBFD time-domain units, even if a TBoMS PUSCH conflicts with a broadcast message, the TBoMS technology can also be applied, thereby ensuring an uplink coverage gain brought about by the transmission of 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 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 communication device, and a storage medium to solve technical problems in related technologies that exist when a network device performs communication after configuring a sub-band 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: receiving first indication information sent by a network device; determining a processing method for a physical uplink shared channel (PUSCH) based on the first indication information; wherein the physical uplink shared channel is sent based on multi-slot transport block processing TBoMS, and the physical uplink shared channel conflicts with a broadcast message in a time domain unit 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: sending first indication information to a terminal, wherein the first indication information is used to instruct the terminal on a processing method for a physical uplink shared channel PUSCH, the physical uplink shared channel being sent based on multi-slot transport block processing TBoMS, and when the physical uplink shared channel collides with a broadcast message in a time domain unit 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 network device sending first indication information to a terminal; the terminal determining, based on the first indication information, a method for processing a physical uplink shared channel (PUSCH); wherein the physical uplink shared channel is sent based on multi-slot transport block processing (TBoMS), and the physical uplink shared channel conflicts with a broadcast message in a time domain unit configured with a subband.

[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 an embodiment of the present disclosure, in some SBFD (Subband Based Full Duplex) time domain units, even if transport block processing over multi-slot (TBoMS) PUSCH (Physical Uplink Shared Channel) conflicts with a broadcast message, TBoMS technology can be applied, which helps ensure the uplink coverage gain brought by sending 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: receiving first indication information sent by a network device; determining a processing method for the physical uplink shared channel PUSCH based on the first indication information; wherein the physical uplink shared channel is sent based on multi-slot transmission block processing TBoMS, and the physical uplink shared channel conflicts with the broadcast message in a time domain unit 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 the first indication information from the network device. 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 ensure the uplink coverage gain brought about by sending the TBoMS PUSCH in the SBFD time slot.

[0032] In combination with some embodiments of the first aspect. In some embodiments, the first indication information is used to instruct the terminal to transmit the physical uplink shared channel in the time domain unit; wherein the first frequency domain resources of the physical uplink shared channel are all located within the subband; or, not to expect to transmit the physical uplink shared channel in the time domain unit, wherein the first frequency domain resources of the physical uplink shared channel are not all located within the subband.

[0033] In combination with some embodiments of the first aspect, in some embodiments, determining a processing method for the physical uplink shared channel according to the first indication information of the network device includes at least one of the following:

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

[0035] The first frequency domain resources of the physical uplink shared channel are not entirely located within the sub-band, and the physical uplink shared channel is not expected to be transmitted in the time domain unit.

[0036] In combination with some embodiments of the first aspect. In some embodiments, the first indication information is used to instruct the terminal to send the physical uplink shared channel in a second frequency domain resource; wherein the first frequency domain resource of the physical uplink shared channel is not entirely within the subband, and the second frequency domain resource is entirely within the subband.

[0037] In combination with some embodiments of the first aspect, in some embodiments, determining a processing method for the physical uplink shared channel according to first indication information of a network device includes: if the first frequency domain resources of the physical uplink shared channel are not entirely within the subband, determining the second frequency domain resources within the subband; and sending the physical uplink shared channel in the second frequency domain resources.

[0038] In the above embodiment, when the first frequency domain resources of the TBoMS PUSCH are not all located within the 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.

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

[0040] Frequency domain resources of a first frequency domain range starting from a first frequency domain position are determined within the subband as the second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

[0041] In combination with some embodiments of the first aspect, in some embodiments, a frequency domain range of the first frequency domain resource is smaller than or equal to a frequency domain range of the subband.

[0042] In combination with some embodiments of the first aspect. In some embodiments, the first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; wherein the first frequency domain interval between the subband and the broadcast message is greater than or equal to a frequency domain interval threshold; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the subband and the broadcast message is less than the frequency domain interval threshold.

[0043] In combination with some embodiments of the first aspect, in some embodiments, determining a processing method for the physical uplink shared channel according to the first indication information of the network device includes at least one of the following:

[0044] A first frequency domain interval between the 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 time domain unit;

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

[0046] 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 subband in the time domain unit. The frequency domain interference between the subband 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.

[0047] In combination with some embodiments of the first aspect. In some embodiments, the first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; wherein the 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; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold.

[0048] In combination with some embodiments of the first aspect. In some embodiments, the determining of a processing method for the physical uplink shared channel according to the first indication information of the network device includes at least one of the following: sending the physical uplink shared channel in the time domain unit, and the 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; not expecting to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than a frequency domain interval threshold.

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

[0050] In combination with some embodiments of the first aspect. In some embodiments, the first indication information is used to indicate that the terminal expects to send the physical uplink shared channel in the time domain unit, where the physical uplink shared channel conflicts with the broadcast message; or to send the physical uplink shared channel in the time domain unit, where the physical uplink shared channel does not conflict with the broadcast message.

[0051] In combination with some embodiments of the first aspect, in some embodiments, determining a processing method for the physical uplink shared channel according to the first indication information of the network device includes at least one of the following:

[0052] The physical uplink shared channel conflicts with the broadcast message, and it is not desired to send the physical uplink shared channel in the time domain unit;

[0053] The physical uplink shared channel does not conflict with the broadcast message, and the physical uplink shared channel is sent in the time domain unit.

[0054] In conjunction with some embodiments of the first aspect, in some embodiments, the conflict includes at least one of the following:

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

[0056] 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 are completely overlapped;

[0057] The physical uplink shared channel and the broadcast message are in the same time domain unit, and the same time domain unit is configured with a subband.

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

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

[0060] In the second aspect, an embodiment of the present disclosure proposes an uplink communication processing method, the method comprising: sending first indication information to a terminal, wherein the first indication information is used to instruct the terminal on how to process the physical uplink shared channel PUSCH, the physical uplink shared channel is sent based on multi-slot transmission block processing TBoMS, and the physical uplink shared channel conflicts with the broadcast message in a time domain unit configured with a subband.

[0061] In combination with some embodiments of the second aspect. In some embodiments, the first indication information is used to instruct the terminal: to send the physical uplink shared channel in the time domain unit, wherein the first frequency domain resources of the physical uplink shared channel are all located within the subband; or, not to expect to send the physical uplink shared channel in the time domain unit, wherein the first frequency domain resources of the physical uplink shared channel are not all located within the subband.

[0062] In combination with some embodiments of the second aspect. In some embodiments, the first indication information is used to instruct the terminal to send the physical uplink shared channel in a second frequency domain resource, wherein the first frequency domain resource of the physical uplink shared channel is not entirely within the subband, and the second frequency domain resource is entirely within the subband.

[0063] In combination with some embodiments of the second aspect, in some embodiments, a frequency domain range of the first frequency domain resource is smaller than or equal to a frequency domain range of the subband.

[0064] In combination with some embodiments of the second aspect. In some embodiments, the first indication information is used to instruct the terminal: to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the subband and the broadcast message is greater than or equal to a frequency domain interval threshold; or, to not send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the subband and the broadcast message is less than a frequency domain interval threshold.

[0065] In combination with some embodiments of the second aspect. In some embodiments, the first indication information is used to instruct the terminal: to send the physical uplink shared channel in the time domain unit, and the 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; or, not to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than a frequency domain interval threshold.

[0066] In combination with some embodiments of the second aspect. In some embodiments, the first indication information is used to instruct the terminal: not to send the physical uplink shared channel in the time domain unit, where the physical uplink shared channel conflicts with the broadcast message; or to send the physical uplink shared channel in the time domain unit, where the physical uplink shared channel does not conflict with the broadcast message.

[0067] In conjunction with some embodiments of the second aspect, in some embodiments, the conflict includes at least one of the following:

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

[0069] 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 are completely overlapped;

[0070] The physical uplink shared channel and the broadcast message are in the same time domain unit, and the same time domain unit is configured with a subband.

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

[0072] In a third aspect, an embodiment of the present disclosure proposes an uplink communication processing method, the method comprising: a network device sends first indication information to a terminal; the terminal determines, based on the first indication information, a processing method for the physical uplink shared channel PUSCH; wherein, the physical uplink shared channel is sent based on multi-slot transmission block processing TBoMS, and the physical uplink shared channel conflicts with the broadcast message in a time domain unit configured with a subband.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0090] 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 restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

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

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

[0093] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

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

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

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

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

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

[0099] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0100] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0101] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

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

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

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

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

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

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

[0108] 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).

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

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

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

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

[0113] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0128] Step S201: The network device sends first indication information to the terminal.

[0129] In some embodiments, the first indication information includes at least one of the following: system information block; radio resource control signaling; downlink control information.

[0130] In some embodiments, the terminal receives first indication information.

[0131] In some embodiments, the first indication information is used to instruct the terminal on how to process the physical uplink shared channel.

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

[0133] In some embodiments, the first indication information 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.

[0134] In some embodiments, taking the timing of occurrence of a conflict as an example, the conflict includes at least one of the following: determining that a conflict is occurring; and predicting that a conflict will occur in a future time domain unit.

[0135] In some embodiments, taking the case where the conflict occurs on time domain resources as an example, the conflict includes at least one of the following:

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

[0137] 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 are completely overlapped;

[0138] The physical uplink shared channel and the broadcast message are in the same time domain unit, and the same time domain unit is configured with a subband.

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

[0140] In some embodiments, the first indication information is used to instruct the terminal: to send the physical uplink shared channel in the time domain unit, wherein the first frequency domain resources of the physical uplink shared channel are all located within the subband; or, not to expect to send the physical uplink shared channel in the time domain unit, wherein the first frequency domain resources of the physical uplink shared channel are not all located within the subband.

[0141] In some embodiments, the first indication information is used to instruct the terminal: to send the physical uplink shared channel in a second frequency domain resource, wherein the first frequency domain resource of the physical uplink shared channel is not entirely within the subband, and the second frequency domain resource is entirely within the subband.

[0142] In some embodiments, the frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the starting point.

[0143] In some embodiments, the first indication information is used to indicate the terminal: when sending the physical uplink shared channel in the time domain unit, the first frequency domain interval between the subband and the broadcast message is greater than or equal to a frequency domain interval threshold; or, when not expecting to send the physical uplink shared channel in the time domain unit, the first frequency domain interval between the subband and the broadcast message is less than a frequency domain interval threshold.

[0144] In some embodiments, the first indication information is used to indicate the terminal: to send the physical uplink shared channel in the time domain unit, and the 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; or, not to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than a frequency domain interval threshold.

[0145] In some embodiments, the first indication information is used to indicate the terminal: not expecting to send the physical uplink shared channel in the time domain unit, wherein the physical uplink shared channel conflicts with the broadcast message; or sending the physical uplink shared channel in the time domain unit, wherein the physical uplink shared channel does not conflict with the broadcast message.

[0146] Step S202: The terminal determines a processing method for the physical uplink shared channel according to the first indication information.

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

[0148] In some embodiments, the terminal determines, according to the first indication information, 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.

[0149] In some embodiments, the first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; wherein the first frequency domain resources of the physical uplink shared channel are all located within the subband; or, the physical uplink shared channel is not expected to be sent in the time domain unit, wherein the first frequency domain resources of the physical uplink shared channel are not all located within the subband.

[0150] In some embodiments, the terminal determines, according to the first indication information of the network device, a processing method for the physical uplink shared channel, including at least one of the following:

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

[0152] The first frequency domain resources of the physical uplink shared channel are not entirely located within the sub-band, and the physical uplink shared channel is not expected to be transmitted in the time domain unit.

[0153] In some embodiments, the first indication information is used to instruct the terminal to send the physical uplink shared channel in a second frequency domain resource; wherein the first frequency domain resource of the physical uplink shared channel is not entirely within the subband, and the second frequency domain resource is entirely within the subband.

[0154] In some embodiments, the terminal determining, according to the first indication information of the network device, a processing method for the physical uplink shared channel, includes:

[0155] If not all of the first frequency domain resources of the physical uplink shared channel are located within the sub-band, determining the second frequency domain resources within the sub-band;

[0156] The physical uplink shared channel is sent in the second frequency domain resources.

[0157] In some embodiments, the terminal determines the second frequency domain resources within the sub-band, including: determining the frequency domain resources of a first frequency domain range with a first frequency domain position as a starting point within the sub-band as the second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

[0158] In some embodiments, a frequency domain range of the first frequency domain resource is smaller than or equal to a frequency domain range of the sub-band.

[0159] In some embodiments, before determining the second frequency domain resource within the 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 subband.

[0160] In some embodiments, when the frequency domain range of the first frequency domain resource is larger than the frequency domain range of the subband, then sufficient frequency domain resources for sending TBoMS PUSCH cannot be determined within the subband, and the terminal does not need to determine the second frequency domain resource within the subband, which helps to avoid wasting the terminal's resources; when the frequency domain range of the first frequency domain resource is less than or equal to the frequency domain range of the subband, then sufficient frequency domain resources for sending TBoMS PUSCH can be determined within the subband, and the terminal determines the second frequency domain resource within the subband.

[0161] In some embodiments, the first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; wherein the first frequency domain interval between the subband and the broadcast message is greater than or equal to a frequency domain interval threshold; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the subband and the broadcast message is less than a frequency domain interval threshold.

[0162] In some embodiments, the terminal determines, according to the first indication information of the network device, a processing method for the physical uplink shared channel, including at least one of the following:

[0163] A first frequency domain interval between the 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 time domain unit;

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

[0165] In some embodiments, the first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; wherein, the 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; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than a frequency domain interval threshold.

[0166] In some embodiments, determining a processing method for the physical uplink shared channel according to the first indication information of the network device includes at least one of the following:

[0167] A first frequency domain interval between a 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 time domain unit;

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

[0169] In some embodiments, the terminal may determine, according to the first indication information, 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.

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

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

[0172] In some embodiments, the terminal may determine, based on the first indication information, a first frequency domain interval between the starting point and the broadcast message in the conflicting time domain unit.

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

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

[0175] In some embodiments, the first indication information is used to indicate that the terminal: does not expect to send the physical uplink shared channel in the time domain unit, wherein the physical uplink shared channel conflicts with the broadcast message; or sends the physical uplink shared channel in the time domain unit, wherein the physical uplink shared channel does not conflict with the broadcast message.

[0176] In some embodiments, the terminal determines, according to the first indication information of the network device, a processing method for the physical uplink shared channel, including at least one of the following:

[0177] The physical uplink shared channel conflicts with the broadcast message, and it is not desired to send the physical uplink shared channel in the time domain unit;

[0178] The physical uplink shared channel does not conflict with the broadcast message, and the physical uplink shared channel is sent in the time domain unit.

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

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

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

[0182] 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:

[0183] In step S301, first indication information sent by a network device is received;

[0184] In step S302, a processing method for the physical uplink shared channel PUSCH is determined according to the first indication information; wherein the physical uplink shared channel is sent based on multi-slot transmission block processing TBoMS, and the physical uplink shared channel and the broadcast message conflict in the time domain unit configured with the subband.

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

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

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

[0188] In some embodiments, the first indication information includes at least one of the following: System Information Block (SIB), such as SIB1; Radio Resource Control (RRC) signaling; Downlink Control Information (DCI).

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

[0190] 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 a TBoMS PUSCH on the SBFD time domain unit, but may determine how to handle the TBoMS PUSCH based on the first indication information of the network device. For example, a TBoMS PUSCH may be sent on an SBFD time domain unit, or a TBoMS PUSCH may not be sent on an SBFD time domain unit. Accordingly, in some SBFD time domain units, even if a TBoMS PUSCH conflicts with a broadcast message, the TBoMS technology can be applied, which is beneficial to ensuring the uplink coverage gain brought about by sending a TBoMS PUSCH in an SBFD time slot.

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

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

[0193] In some embodiments, the conflict includes at least one of the following:

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

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

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

[0197] 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 the first indication information of the network device.

[0198] 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 the first indication information of the network device.

[0199] 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 SSB conflict in the same SBFD time slot, and then determine how to handle the TBoMS PUSCH according to the first indication information of the network device.

[0200] The following uses some embodiments to exemplify how a terminal determines a processing manner for a physical uplink shared channel according to first indication information of a network device.

[0201] In some embodiments, the first indication information is used to instruct the terminal to send a physical uplink shared channel in a time domain unit; wherein the first frequency domain resources of the physical uplink shared channel are all located within the subband; or, it is not expected to send a physical uplink shared channel in a time domain unit, wherein the first frequency domain resources of the physical uplink shared channel are not all located within the subband.

[0202] In some embodiments, determining a processing method for a physical uplink shared channel according to the first indication information of the network device includes at least one of the following:

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

[0204] The first frequency domain resources of the physical uplink shared channel are not all located within the subband, and the physical uplink shared channel is not expected to be transmitted in the time domain unit.

[0205] In some embodiments, the network device may send a first indication message to the terminal, instructing the terminal through the first indication message that when the first frequency domain resources of the physical uplink shared channel are all located within the sub-band, the physical uplink shared channel is sent in the time domain unit; when the first frequency domain resources of the physical uplink shared channel are not all located within the sub-band, the physical uplink shared channel is not expected to be sent in the time domain unit.

[0206] Based on the first indication information, 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.

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

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

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

[0210] 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).

[0211] 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)).

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

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

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

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

[0216] In some embodiments, the first indication information is used to indicate that when all first frequency domain resources of the physical uplink shared channel are located within a sub-band, the physical uplink shared channel is sent in a time domain unit.

[0217] 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 first indication information 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.

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

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

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

[0221] In some embodiments, the first indication information is used to indicate that when all first frequency domain resources of the physical uplink shared channel are located within a sub-band, the physical uplink shared channel is sent in a time domain unit.

[0222] In the embodiment shown in FIG6A , since 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 the first indication information 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.

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

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

[0225] In some embodiments, the first indication information is used to indicate that when all first frequency domain resources of the physical uplink shared channel are located within a sub-band, the physical uplink shared channel is sent in a time domain unit.

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

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

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

[0229] In some embodiments, the first indication information is used to instruct the terminal to send a physical uplink shared channel in a second frequency domain resource; wherein the first frequency domain resource of the physical uplink shared channel is not entirely within the subband, and the second frequency domain resource is entirely within the subband.

[0230] In some embodiments, determining a processing method for the physical uplink shared channel based on first indication information of the network device includes: if the first frequency domain resources of the physical uplink shared channel are not all located within the subband, determining a second frequency domain resource within the subband; and sending the physical uplink shared channel in the second frequency domain resource.

[0231] In some embodiments, the network device may send first indication information to the terminal, instructing the terminal through the first indication information to send the physical uplink shared channel in the second frequency domain resources when the first frequency domain resources of the physical uplink shared channel are not all located within the subband, wherein the second frequency domain resources are all located within the subband.

[0232] Based on the first indication information, 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 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. Accordingly, 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 beneficial to reducing the delay of TBoMS PUSCH transmission.

[0233] In some embodiments, the frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the subband.

[0234] 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 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 for sending TBoMS PUSCH cannot be determined within the uplink subband, and the terminal does not need to determine the second frequency domain resource within the uplink subband, which helps to avoid wasting terminal resources; 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 for sending TBoMS PUSCH can be determined within the uplink subband, and the terminal will then determine the second frequency domain resource within the uplink subband.

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

[0236] Frequency domain resources of a first frequency domain range starting from a first frequency domain position are determined within the subband as second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

[0237] The terminal determines the second frequency domain resource within the uplink subband and can determine the starting point and frequency domain range 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 frequency domain range of the second frequency domain resource can be the 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.

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

[0239] In some embodiments, the first indication information is used to indicate that when the first frequency domain resources of the physical uplink shared channel are not entirely within the subband, the physical uplink shared channel is sent in the second frequency domain resources, wherein the second frequency domain resources are entirely within the subband.

[0240] 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 the second frequency domain resources within the conflicting time domain unit, such as the uplink subband of slot#1 to slot#3, based on the first indication information sent by the network device. 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. The terminal can then transmit the TBoMS PUSCH in the second frequency domain resources.

[0241] 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, with RB #20 as the starting point and a frequency domain range of 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.

[0242] In some embodiments, the first indication information is used to indicate that the terminal does not expect to send a physical uplink shared channel in a time domain unit; wherein the physical uplink shared channel conflicts with a broadcast message; or, to send a physical uplink shared channel in a time domain unit, wherein the physical uplink shared channel does not conflict with a broadcast message.

[0243] In some embodiments, determining a processing method for a physical uplink shared channel according to the first indication information of the network device includes at least one of the following:

[0244] The physical uplink shared channel conflicts with the broadcast message and it is not desired to send the physical uplink shared channel in the time domain unit;

[0245] The physical uplink shared channel does not conflict with the broadcast message, and the physical uplink shared channel is sent in a time domain unit.

[0246] In some embodiments, the network device may send first indication information to the terminal, instructing the terminal through the first indication information to send the physical uplink shared channel in the time domain unit when the physical uplink shared channel conflicts with the broadcast message, or not to send the physical uplink shared channel in the time domain unit.

[0247] According to the first indication information, the terminal may determine that it does not expect to send the TBoMS PUSCH in the conflicting time domain unit, or the terminal may determine to send the TBoMS PUSCH in the conflicting time domain unit.

[0248] For example, the network device sends the first indication information to the terminal through SIB1, and the first indication information may occupy at least 1 bit.

[0249] Taking the first indication information occupying 1 bit as an example, this bit is 1, which is used to indicate that when the physical uplink shared channel conflicts with the broadcast message, the terminal can send the physical uplink shared channel in the conflicting time domain unit; this bit is 0, which is used to indicate that when the physical uplink shared channel conflicts with the broadcast message, the terminal cannot send the physical uplink shared channel in the conflicting time domain unit.

[0250] Taking the first indication information occupying multiple bits as an example, the number of bits in the multiple bits can be the same as the number of conflicting time domain units. There is an association between the bits and the conflicting time domain units, and the bits are used to indicate whether the physical uplink shared channel is sent or not sent in the corresponding time domain unit.

[0251] For example, in the embodiment shown in FIG5 , the number of conflicting time domain units is 3, and the first indication information may occupy 3 bits. The first bit is used to indicate whether TBoMS PUSCH is sent or not in the first conflicting time domain unit slot#1. The first bit is used to indicate whether TBoMS PUSCH is sent or not in the second conflicting time domain unit slot#2. The third bit is used to indicate whether TBoMS PUSCH is sent or not in the third conflicting time domain unit slot#3.

[0252] For example, a bit of 1 indicates sending a TBoMS PUSCH, and a bit of 0 indicates sending a TBoMS PUSCH. When the first indication information is 101, the terminal may determine to send a TBoMS PUSCH in slot#1 and slot#3, and not to send a TBoMS PUSCH in slot#2.

[0253] In some embodiments, the first indication information is used to indicate: when sending a physical uplink shared channel in a time domain unit, the first frequency domain interval between the subband and the broadcast message is greater than or equal to a frequency domain interval threshold; or, when sending a physical uplink shared channel in a time domain unit, the first frequency domain interval between the subband and the broadcast message is less than a frequency domain interval threshold.

[0254] In some embodiments, determining a processing method for a physical uplink shared channel according to the first indication information of the network device includes at least one of the following:

[0255] A first frequency domain interval between the 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 time domain unit;

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

[0257] It should be noted that the first frequency domain interval can be a positive number, zero, or a negative number. For example, the broadcast message can be within the first frequency domain resource corresponding to the subband.

[0258] In some embodiments, the network device may send a first indication message to the terminal, instructing the terminal through the first indication message that when the first frequency domain interval between the subband and the broadcast message is greater than or equal to the frequency domain interval threshold, the physical uplink shared channel is sent in the time domain unit; when the first frequency domain interval between the subband and the broadcast message is less than the frequency domain interval threshold, it is not expected to send the physical uplink shared channel in the time domain unit.

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

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

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

[0262] In some embodiments, the first indication information is used to instruct the terminal to send a physical uplink shared channel in a time domain unit; wherein the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold; or, the first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; wherein the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold.

[0263] In some embodiments, determining a processing method for a physical uplink shared channel according to the first indication information of the network device includes at least one of the following:

[0264] Sending a physical uplink shared channel in a time domain unit, where 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;

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

[0266] It should be noted that the first frequency domain interval may be a positive number, zero, or a negative number. For example, the broadcast message may be within the first frequency domain resource corresponding to the physical uplink shared channel.

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

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

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

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

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

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

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

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

[0275] 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:

[0276] In step S801, first indication information is sent to the terminal, wherein the first indication information is used to instruct the terminal on a processing method for a physical uplink shared channel PUSCH, the physical uplink shared channel is sent based on multi-slot transport block processing TBoMS, and when the physical uplink shared channel collides with a broadcast message in a time domain unit configured with a subband.

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

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

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

[0280] In some embodiments, the first indication information includes at least one of the following: system information block (SSIB), such as SIB1; radio resource control (RRC) signaling; downlink control information (DCI).

[0281] In some embodiments, taking the timing of occurrence of a conflict as an example, the conflict includes at least one of the following: determining that a conflict is occurring; and predicting that a conflict will occur in a future time domain unit.

[0282] According to an embodiment of the present disclosure, the network device may indicate to the terminal through the first indication information how to handle the TBoMS PUSCH when the TBoMS PUSCH conflicts with the broadcast message in the SBFD time domain unit. Accordingly, the terminal may not default to not expecting to send the TBoMS PUSCH on the SBFD time domain unit, but may determine how to handle the TBoMS PUSCH based on the first indication information of the network device. For example, the TBoMS PUSCH may be sent on the SBFD time domain unit, or the TBoMS PUSCH may not be sent on the SBFD time domain unit. Accordingly, in some SBFD time domain units, even if the TBoMS PUSCH conflicts with the broadcast message, the TBoMS technology can be applied, which is beneficial to ensure the uplink coverage gain brought about by sending the TBoMS PUSCH in the SBFD time slot.

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

[0284] In some embodiments, taking the case where the conflict occurs on time domain resources as an example, the conflict includes at least one of the following:

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

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

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

[0288] 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 the first indication information of the network device.

[0289] 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 the first indication information of the network device.

[0290] 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 SSB conflict in the same SBFD time slot, and then determine how to handle the TBoMS PUSCH according to the first indication information of the network device.

[0291] In some embodiments, the first indication information is used to instruct the terminal to send a physical uplink shared channel in a time domain unit; wherein the first frequency domain resources of the physical uplink shared channel are all located within the subband; or, it is not expected to send a physical uplink shared channel in a time domain unit, wherein the first frequency domain resources of the physical uplink shared channel are not all located within the subband.

[0292] In some embodiments, the network device may send first indication information to the terminal, instructing the terminal through the first indication information to send 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 subband.

[0293] Based on the first indication information, 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.

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

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

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

[0297] In some embodiments, the first indication information is used to indicate that when all first frequency domain resources of the physical uplink shared channel are located within a sub-band, the physical uplink shared channel is sent in a time domain unit.

[0298] 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 terminal can still send the TBoMS PUSCH within the uplink subband according to the configuration and / or scheduling of the network device. Based on the first indication information sent by the network device, the terminal can determine to send the TBoMS PUSCH in the conflicting time domain unit, that is, slot #1 to slot #3. Of course, the TBoMS PUSCH can also be sent in the non-conflicting time domain unit, that is, slot #4. Correspondingly, the network device can receive the TBoMS PUSCH sent by the terminal in slots #1 to slot #4.

[0299] 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 the first indication information 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. Correspondingly, the network device may not expect to receive the TBoMS PUSCH transmitted by the terminal in slots #1 to #3, but may instead receive the TBoMS PUSCH transmitted by the terminal in slot #4.

[0300] In some embodiments, since TBoMS PUSCH is sent in at least three slots, to ensure that the number of TBoMS PUSCH slots is 4, it is necessary to determine three available slots after slot #4 to send TBoMS PUSCH. Correspondingly, the network device can also receive TBoMS PUSCH sent by the terminal in the three available slots after slot #4.

[0301] 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. Correspondingly, the network device may not expect to receive the TBoMS PUSCH sent by the terminal in slot #1, but may receive the TBoMS PUSCH sent by the terminal in slot #2 to slot #4.

[0302] 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 an available slot after slot #4 to send the TBoMS PUSCH. Correspondingly, the network device can also receive the TBoMS PUSCH sent by the terminal in an available slot after slot #4.

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

[0304] In some embodiments, the first indication information is used to instruct the terminal to send a physical uplink shared channel in a second frequency domain resource; wherein the first frequency domain resource of the physical uplink shared channel is not entirely within the subband, and the second frequency domain resource is entirely within the subband.

[0305] In some embodiments, the network device may send first indication information to the terminal, instructing the terminal through the first indication information to send the physical uplink shared channel in the second frequency domain resources when the first frequency domain resources of the physical uplink shared channel are not all located within the subband, wherein the second frequency domain resources are all located within the subband.

[0306] Based on the first indication information, 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 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. Accordingly, 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 beneficial to reducing the delay of TBoMS PUSCH transmission.

[0307] In some embodiments, the frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the subband.

[0308] The network device can instruct the terminal to send the physical uplink shared channel in the second frequency domain resources only when the frequency domain range of the first frequency domain resources is less than or equal to the frequency domain range of the subband and the first frequency domain resources of the physical uplink shared channel are not all located within the subband, wherein the second frequency domain resources are all located within the subband.

[0309] 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 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 for sending TBoMS PUSCH cannot be determined within the uplink subband, and the terminal does not need to determine the second frequency domain resource within the uplink subband, which helps to avoid wasting terminal resources; 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 for sending TBoMS PUSCH can be determined within the uplink subband, and the terminal will then determine the second frequency domain resource within the uplink subband.

[0310] 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 the second frequency domain resources within the conflicting time domain unit, such as the uplink subband of slot#1 to slot#3, based on the first indication information sent by the network device. 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. The terminal can then transmit the TBoMS PUSCH in the second frequency domain resources.

[0311] For example, 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 a second frequency domain resource, RB #20 to RB #30, with a length of 10 RBs starting at RB #20, from RB #20 to RB #40. Furthermore, the terminal can transmit the TBoMS PUSCH from RB #20 to RB #30 in slots #1 to #3. Correspondingly, the network device can receive the TBoMS PUSCH sent by the terminal from RB #20 to RB #30 in slots #1 to #3, and still receive the TBoMS PUSCH from RB #20 to RB #30 in slots #4.

[0312] In some embodiments, the network device may send first indication information to the terminal, instructing the terminal through the first indication information to send the physical uplink shared channel in the time domain unit when the physical uplink shared channel conflicts with the broadcast message, or not to send the physical uplink shared channel in the time domain unit.

[0313] According to the first indication information, the terminal may determine that it does not expect to send the TBoMS PUSCH in the conflicting time domain unit, or the terminal may determine to send the TBoMS PUSCH in the conflicting time domain unit.

[0314] For example, the network device sends the first indication information to the terminal through SIB1, and the first indication information may occupy at least 1 bit.

[0315] Taking the first indication information occupying 1 bit as an example, this bit is 1, which is used to indicate that when the physical uplink shared channel conflicts with the broadcast message, the terminal can send the physical uplink shared channel in the conflicting time domain unit; this bit is 0, which is used to indicate that when the physical uplink shared channel conflicts with the broadcast message, the terminal cannot send the physical uplink shared channel in the conflicting time domain unit.

[0316] Taking the first indication information occupying multiple bits as an example, the number of bits in the multiple bits can be the same as the number of conflicting time domain units. There is an association between the bits and the conflicting time domain units, and the bits are used to indicate whether the physical uplink shared channel is sent or not sent in the corresponding time domain unit.

[0317] For example, in the embodiment shown in FIG5 , the number of conflicting time domain units is 3, and the first indication information may occupy 3 bits. The first bit is used to indicate whether TBoMS PUSCH is sent or not in the first conflicting time domain unit slot#1. The first bit is used to indicate whether TBoMS PUSCH is sent or not in the second conflicting time domain unit slot#2. The third bit is used to indicate whether TBoMS PUSCH is sent or not in the third conflicting time domain unit slot#3.

[0318] For example, a bit of 1 indicates the transmission of a TBoMS PUSCH, and a bit of 0 indicates the transmission of a TBoMS PUSCH. When the first indication information is 101, the terminal may determine to transmit a TBoMS PUSCH in slots #1 and #3, and not to transmit a TBoMS PUSCH in slot #2. Correspondingly, the network device transmits a TBoMS PUSCH in slots #1 and #3, and does not expect to receive a TBoMS PUSCH transmitted by the terminal in slot #2.

[0319] In some embodiments, the first indication information is used to indicate the terminal: to send a physical uplink shared channel in a time domain unit, and the first frequency domain interval between the subband and the broadcast message is greater than or equal to a frequency domain interval threshold; or, not to expect to send a physical uplink shared channel in a time domain unit, and the first frequency domain interval between the subband and the broadcast message is less than a frequency domain interval threshold; or, the first indication information is used to indicate that the terminal does not expect to send the physical uplink shared channel in the time domain unit, wherein the physical uplink shared channel conflicts with the broadcast message; or, to send the physical uplink shared channel in the time domain unit, wherein the physical uplink shared channel does not conflict with the broadcast message.

[0320] In some embodiments, the network device may send first indication information to the terminal, instructing the terminal through the first indication information to send a physical uplink shared channel in a time domain unit when the first frequency domain interval between the subband and the broadcast message is greater than or equal to a frequency domain interval threshold.

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

[0322] 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 the 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. The network device does not expect to receive the TBoMS PUSCH sent by the terminal in the conflicting time domain unit;

[0323] 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, and the network device can also receive TBoMS PUSCH sent by the terminal in the conflicting time domain unit.

[0324] In some embodiments, the network device may send first indication information to the terminal, instructing the terminal through the first indication information to send the physical uplink shared channel in the time domain unit when the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold.

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

[0326] 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. The network device does not expect to receive the TBoMS PUSCH sent by the terminal in the conflicting time domain unit.

[0327] 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 time domain unit, and the network device can also receive TBoMS PUSCH sent by the terminal in the conflicting time domain unit.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0346] FIG9 is a schematic block diagram of a terminal according to an embodiment of the present disclosure. As shown in FIG9 , the terminal includes at least one of the following: a receiving module 901 and a processing module 902 .

[0347] In some embodiments, the receiving module is configured to receive first indication information sent by a network device;

[0348] In some embodiments, the processing module is used to determine a processing method for the physical uplink shared channel PUSCH based on the first indication information; wherein the physical uplink shared channel is sent based on multi-slot transmission block processing TBoMS, and the physical uplink shared channel conflicts with the broadcast message in the time domain unit configured with the subband.

[0349] In some embodiments, the first indication information is used by the terminal to send a physical uplink shared channel in a time domain unit; wherein the first frequency domain resources of the physical uplink shared channel are all located within the subband; or, it is not expected to send a physical uplink shared channel in a time domain unit, wherein the first frequency domain resources of the physical uplink shared channel are not all located within the subband.

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

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

[0352] The first frequency domain resources of the physical uplink shared channel are not all located within the subband, and the physical uplink shared channel is not expected to be transmitted in the time domain unit.

[0353] In some embodiments, the first indication information is used to instruct the terminal to send a physical uplink shared channel in a second frequency domain resource; wherein the first frequency domain resource of the physical uplink shared channel is not entirely within the subband, and the second frequency domain resource is entirely within the subband.

[0354] In some embodiments, the processing module is configured to, when not all first frequency domain resources of the physical uplink shared channel are located within the subband, determine second frequency domain resources within the subband; and send the physical uplink shared channel in the second frequency domain resources.

[0355] In some embodiments, the processing module is configured to determine, within the subband, frequency domain resources of a first frequency domain range starting from a first frequency domain position as the second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

[0356] In some embodiments, the frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the subband.

[0357] In some embodiments, the first indication information is used to instruct the terminal to send a physical uplink shared channel in a time domain unit; wherein the first frequency domain interval between the subband and the broadcast message is greater than or equal to the frequency domain interval threshold; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the subband and the broadcast message is less than the frequency domain interval threshold; or, the physical uplink shared channel is sent in the time domain unit; wherein the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold.

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

[0359] A first frequency domain interval between the 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 time domain unit;

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

[0361] In some embodiments, determining a processing method for a physical uplink shared channel according to the first indication information of the network device includes at least one of the following:

[0362] Sending a physical uplink shared channel in a time domain unit, where 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;

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

[0364] In some embodiments, the first indication information is used to indicate: it is not expected to send a physical uplink shared channel in a time domain unit, where the physical uplink shared channel conflicts with a broadcast message; or, to send a physical uplink shared channel in a time domain unit, where the physical uplink shared channel does not conflict with a broadcast message.

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

[0366] The physical uplink shared channel conflicts with the broadcast message and it is not desired to send the physical uplink shared channel in the time domain unit;

[0367] The physical uplink shared channel does not conflict with the broadcast message, and the physical uplink shared channel is sent in a time domain unit.

[0368] In some embodiments, the conflict includes at least one of the following:

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

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

[0371] The physical uplink shared channel and the broadcast message are in the same time domain unit, and the same time domain unit is configured with a subband.

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

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

[0374] 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 sending module 1001 .

[0375] In some embodiments, the sending module is used to send first indication information to the terminal, wherein the first indication information is used to instruct the terminal on how to process the physical uplink shared channel PUSCH, the physical uplink shared channel is sent based on multi-slot transmission block processing TBoMS, and when the physical uplink shared channel conflicts with the broadcast message in a time domain unit configured with a subband.

[0376] In some embodiments, the first indication information is used by the terminal to send a physical uplink shared channel in a time domain unit; wherein the first frequency domain resources of the physical uplink shared channel are all located within the subband; or, it is not expected to send a physical uplink shared channel in a time domain unit, wherein the first frequency domain resources of the physical uplink shared channel are not all located within the subband.

[0377] In some embodiments, the first indication information is used to instruct the terminal to send a physical uplink shared channel in a second frequency domain resource; wherein the first frequency domain resource of the physical uplink shared channel is not entirely within the subband, and the second frequency domain resource is entirely within the subband.

[0378] In some embodiments, the frequency domain range of the first frequency domain resource is smaller than or equal to the frequency domain range of the subband.

[0379] In some embodiments, the first indication information is used for the terminal to send a physical uplink shared channel in a time domain unit; the first frequency domain interval between the subband and the broadcast message is greater than or equal to the frequency domain interval threshold; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the subband and the broadcast message is less than the frequency domain interval threshold; or, the physical uplink shared channel is sent in the time domain unit; wherein the first frequency domain interval between the physical uplink shared channel and the broadcast message is greater than or equal to the frequency domain interval threshold; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than the frequency domain interval threshold.

[0380] In some embodiments, the first indication information is used to indicate that the terminal does not expect to send a physical uplink shared channel in a time domain unit, where the physical uplink shared channel conflicts with a broadcast message; or to send a physical uplink shared channel in a time domain unit, where the physical uplink shared channel does not conflict with a broadcast message.

[0381] In some embodiments, the conflict includes at least one of the following:

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

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

[0384] The physical uplink shared channel and the broadcast message are in the same time domain unit, and the same time domain unit is configured with a subband.

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

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

[0387] An embodiment of the present disclosure further proposes an uplink communication processing method, the method comprising: a network device sending first indication information to a terminal; the terminal determining, based on the first indication information, a processing method for the physical uplink shared channel PUSCH; wherein the physical uplink shared channel is sent based on multi-slot transport block processing TBoMS, and the physical uplink shared channel conflicts with a broadcast message in a time domain unit configured with a subband.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0410] 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: Receiving first indication information sent by the network device; Determine a processing method for a physical uplink shared channel PUSCH according to the first indication information; The physical uplink shared channel is sent based on multi-slot transmission block processing TBoMS, and the physical uplink shared channel conflicts with the broadcast message in a time domain unit configured with a subband.

2. The method according to claim 1, characterized in that The first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; Wherein, the first frequency domain resources of the physical uplink shared channel are all located within the sub-band; or, It is not expected to transmit the physical uplink shared channel in the time domain unit, and the first frequency domain resources of the physical uplink shared channel are not all located within the subband.

3. The method according to claim 2, characterized in that The determining, according to the first indication information of the network device, a processing method for the physical uplink shared channel includes at least one of the following: The first frequency domain resources of the physical uplink shared channel are all located within the 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 sub-band, and it is not expected to send the physical uplink shared channel in the time domain unit.

4. The method according to claim 1, characterized in that: The first indication information is used to instruct the terminal to send the physical uplink shared channel in a second frequency domain resource, wherein the first frequency domain resource of the physical uplink shared channel is not entirely located within the subband, and the second frequency domain resource is entirely located within the subband.

5. The method according to claim 4, characterized in that The determining, according to the first indication information of the network device, a processing method for the physical uplink shared channel includes: If not all of the first frequency domain resources of the physical uplink shared channel are located within the sub-band, the second frequency domain resources are determined within the sub-band; The physical uplink shared channel is sent in the second frequency domain resources.

6. The method according to claim 5, characterized in that The determining the second frequency domain resource within the sub-band includes: Frequency domain resources of a first frequency domain range starting from a first frequency domain position are determined within the subband as the second frequency domain resources, wherein the first frequency domain range is determined based on the first frequency domain resources.

7. The method according to any one of claims 4 to 6, characterized in that A frequency domain range of the first frequency domain resource is smaller than or equal to a frequency domain range of the subband.

8. The method according to claim 1, characterized in that The first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; the first frequency domain interval between the subband and the broadcast message is greater than or equal to a frequency domain interval threshold; or, It is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the subband and the broadcast message is less than a frequency domain interval threshold; or, The first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; The 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; or, It is not expected to send the physical uplink shared channel in the time domain unit, and a first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold.

9. The method according to claim 8, characterized in that The determining, according to the first indication information of the network device, a processing method for the physical uplink shared channel includes at least one of the following: A first frequency domain interval between the 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 time domain unit; A first frequency domain interval between the 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 time domain unit; Sending the physical uplink shared channel in the time domain unit, wherein 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; It is not expected to send the physical uplink shared channel in the time domain unit, and a first frequency domain interval between the physical uplink shared channel and the broadcast message is smaller than a frequency domain interval threshold.

10. The method according to claim 1, characterized in that The first indication information is used to indicate the terminal: not expecting to send the physical uplink shared channel in the time domain unit, wherein the physical uplink shared channel conflicts with the broadcast message; or sending the physical uplink shared channel in the time domain unit, wherein the physical uplink shared channel does not conflict with the broadcast message.

11. The method according to claim 10, characterized in that The determining, according to the first indication information of the network device, a processing method for the physical uplink shared channel includes at least one of the following: The physical uplink shared channel conflicts with the broadcast message, and it is not desired to send the physical uplink shared channel in the time domain unit; The physical uplink shared channel does not conflict with the broadcast message, and the physical uplink shared channel is sent in the time domain unit.

12. The method according to any one of claims 1 to 11, characterized in that The conflict includes 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 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 time domain unit are completely overlapped; The physical uplink shared channel and the broadcast message are in the same time domain unit, and the same time domain unit is configured with a subband.

13. A method for processing uplink communication, characterized in that: The method comprises: Send first indication information to the terminal, wherein the first indication information is used to instruct the terminal on how to process a physical uplink shared channel PUSCH, the physical uplink shared channel is sent based on multi-slot transmission block processing TBoMS, and the physical uplink shared channel conflicts with a broadcast message in a time domain unit configured with a subband.

14. The method according to claim 13, characterized in that The first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; wherein the first frequency domain resources of the physical uplink shared channel are all located within the subband; or, the physical uplink shared channel is not expected to be sent in the time domain unit, and the first frequency domain resources of the physical uplink shared channel are not all located within the subband.

15. The method according to claim 13, characterized in that The first indication information is used to instruct the terminal to send the physical uplink shared channel in a second frequency domain resource; wherein the first frequency domain resource of the physical uplink shared channel is not entirely within the subband, and the second frequency domain resource is entirely within the subband.

16. The method according to claim 15, characterized in that A frequency domain range of the first frequency domain resource is smaller than or equal to a frequency domain range of the subband.

17. The method according to claim 13, characterized in that The first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; wherein, the first frequency domain interval between the subband and the broadcast message is greater than or equal to a frequency domain interval threshold; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the subband and the broadcast message is less than a frequency domain interval threshold.

18. The method according to claim 13, characterized in that The first indication information is used to instruct the terminal to send the physical uplink shared channel in the time domain unit; wherein, the 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; or, it is not expected to send the physical uplink shared channel in the time domain unit, and the first frequency domain interval between the physical uplink shared channel and the broadcast message is less than a frequency domain interval threshold; or, the first indication information is used to indicate that the terminal does not expect to send the physical uplink shared channel in the time domain unit, wherein the physical uplink shared channel conflicts with the broadcast message; or, the physical uplink shared channel is sent in the time domain unit, wherein the physical uplink shared channel does not conflict with the broadcast message.

19. The method according to any one of claims 13 to 18, characterized in that The conflict includes 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 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 time domain unit are completely overlapped; The physical uplink shared channel and the broadcast message are in the same time domain unit, and the same time domain unit is configured with a subband.

20. 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.

21. 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-19.

22. 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-19.

23. 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-19.

24. 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 as described in any one of claims 1-12 and 13-19.

Images