Method for retransmitting uplink information, apparatus, and medium

Abstract

A method for retransmitting uplink information, an apparatus, and a medium. The method comprises: a terminal receives DCI sent by a network device, wherein the DCI is used for indicating a first number of retransmissions for retransmitting uplink information; and on the basis of the first number of retransmissions, the terminal retransmits the uplink information to the network device by means of a first PUCCH, wherein the first PUCCH comprises: common PUCCHs other than a PUCCH occupied by a Msg4 HARQ-ACK corresponding to Msg4 in a random access procedure, the common PUCCHs having time domain locations before a location where the terminal receives first configuration information, and the first configuration information comprising a dedicated PUCCH resource corresponding to the terminal. The terminal receives the first number of retransmissions indicated by the network device by means of the DCI, so that before receiving a dedicated PUCCH resource configuration, the terminal can retransmit the first PUCCH on the basis of the first number of retransmissions, so as to enhance, by means of the first number of retransmissions, the coverage of uplink information, other than the Msg4 HARQ-ACK, occupying common PUCCH resources.

Description

Method, device and medium for retransmitting uplink information Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a method, device, and medium for retransmitting uplink information. Background Art

[0002] In non-terrestrial networks (NTN), terminals can obtain wireless resources through satellite base stations to expand 5G network coverage. However, in NTN or terrestrial networks (TN), there is still a lack of uplink enhancement methods for uplink information.

[0003] Summary of the Invention

[0004] There is no uplink enhancement method for other common physical uplink control channel (common PUCCH) resources involved before the terminal dedicated physical uplink control channel (dedicated PUCCH) is configured.

[0005] Embodiments of the present disclosure provide a method, apparatus, and medium for retransmitting uplink information.

[0006] In a first aspect, an embodiment of the present disclosure provides a method for retransmitting uplink information, the method comprising:

[0007] The terminal receives downlink control information (DCI) sent by the network device, where the DCI is used to indicate a first retransmission count for retransmitting uplink information;

[0008] The terminal retransmits the uplink information to the network device through the first physical uplink control channel PUCCH according to the first retransmission number;

[0009] Among them, the first PUCCH includes: in addition to the PUCCH occupied by the hybrid automatic repeat request acknowledgement feedback information (Msg4 hybrid automatic repeat request acknowledgement, Msg4 HARQ-ACK) corresponding to message 4 Msg4 in the random access process, the public PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resources corresponding to the terminal.

[0010] In a second aspect, an embodiment of the present disclosure provides a method for retransmitting uplink information, the method comprising:

[0011] The network device sends a DCI to the terminal, where the DCI is used to indicate a first retransmission count for retransmitting uplink information;

[0012] The network device receives uplink information retransmitted by the terminal through the first PUCCH according to the first retransmission number, wherein the first PUCCH includes: in addition to the PUCCH occupied by the Msg4 HARQ-ACK corresponding to Msg4 in the random access process, the public PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resources corresponding to the terminal.

[0013] In a third aspect, an embodiment of the present disclosure provides a terminal, including:

[0014] A transceiver module, configured to receive downlink control information DCI sent by a network device, where the DCI is used to indicate a first retransmission count for retransmitting uplink information;

[0015] The transceiver module is further configured to retransmit the uplink information to the network device via a first physical uplink control channel PUCCH according to the first retransmission number;

[0016] Among them, the first PUCCH includes: in addition to the PUCCH occupied by the hybrid automatic repeat request confirmation feedback information Msg4 HARQ-ACK corresponding to message 4 Msg4 in the random access process, the public PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resource corresponding to the terminal.

[0017] In a fourth aspect, an embodiment of the present disclosure provides a network device, including:

[0018] A transceiver module, configured to send a DCI to a terminal, where the DCI is used to indicate a first retransmission count for retransmitting uplink information;

[0019] The transceiver module is also used to receive uplink information retransmitted by the receiving terminal through the first PUCCH according to the first retransmission number, wherein the first PUCCH includes: in addition to the PUCCH occupied by the Msg4 HARQ-ACK corresponding to Msg4 in the random access process, the public PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resource corresponding to the terminal.

[0020] In a fifth aspect, an embodiment of the present disclosure provides a communication device, including:

[0021] one or more processors;

[0022] The terminal is used to execute the method for retransmitting uplink information described in the first aspect.

[0023] In a sixth aspect, an embodiment of the present disclosure provides a communication device, including:

[0024] one or more processors;

[0025] Wherein, the communication device is used to execute the method for retransmitting uplink information described in the second aspect.

[0026] In a seventh aspect, an embodiment of the present disclosure provides a communication system, including a terminal and a network device, wherein:

[0027] The terminal is configured to implement the method for retransmitting uplink information according to the first aspect;

[0028] The network device is configured to implement the method for retransmitting uplink information described in the second aspect.

[0029] In an eighth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, wherein:

[0030] When the instruction is executed on a communication device, the communication device is caused to execute the method according to any one of the first aspect or any one of the second aspect.

[0031] In the method disclosed herein, the terminal receives the first number of retransmissions indicated by the network device through the DCI, so that before receiving the dedicated PUCCH resource configuration, the terminal can retransmit the first PUCCH according to the first number of retransmissions, so as to enhance the coverage of the uplink information occupying the common PUCCH resources except Msg4 HARQ-ACK through the first number of retransmissions. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0033] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0034] FIG2 is an exemplary interaction diagram of a method provided according to an embodiment of the present disclosure;

[0035] 3a to 3c are schematic flow diagrams of a method performed by a terminal according to an embodiment of the present disclosure;

[0036] 4a to 4c are flowcharts of methods performed by a network device according to an embodiment of the present disclosure;

[0037] FIG5a is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

[0038] FIG5b is a schematic structural diagram of a network device according to an embodiment of the present disclosure;

[0039] FIG6a is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0040] FIG6 b is a schematic diagram of a communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0041] Embodiments of the present disclosure provide a method, apparatus, and medium for retransmitting uplink information.

[0042] In a first aspect, an embodiment of the present disclosure provides a method for retransmitting uplink information, the method comprising:

[0043] The terminal receives downlink control information DCI sent by the network device, where the DCI is used to indicate a first retransmission count for retransmitting uplink information;

[0044] The terminal retransmits the uplink information to the network device through the first physical uplink control channel PUCCH according to the first retransmission number;

[0045] Among them, the first PUCCH includes: in addition to the PUCCH occupied by the hybrid automatic repeat request confirmation feedback information Msg4 HARQ-ACK corresponding to message 4 Msg4 in the random access process, the public PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resources corresponding to the terminal.

[0046] In the above embodiment, the terminal receives the first number of retransmissions indicated by the network device through the DCI, so that before receiving the dedicated PUCCH resource configuration, the terminal can retransmit the first PUCCH according to the first number of retransmissions to enhance the coverage of uplink information occupying the common PUCCH resources except Msg4 HARQ-ACK through the first number of retransmissions.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the DCI is a DCI for scheduling Msg4, or,

[0048] The DCI is a DCI used for scheduling a physical downlink shared channel (PDSCH) corresponding to the first PUCCH.

[0049] In the above embodiment, the DCI used to indicate the first number of retransmissions may be the DCI of the multiplexing scheduling Msg4, or the DCI of the PDSCH corresponding to the scheduling of the first PUCCH, so that the terminal knows the first number of retransmissions based on the DCI sent by the network device.

[0050] In combination with some embodiments of the first aspect, in some embodiments, the first retransmission number is the same as or different from the second retransmission number, and the second retransmission number is the retransmission number of Msg4 HARQ-ACK.

[0051] In the above embodiment, the first retransmission number corresponding to the first PUCCH and the second retransmission number corresponding to Msg4 HARQ-ACK may be the same or different, that is, the first retransmission number may be untied from the retransmission number of Msg4 HARQ-ACK, and the first PUCCH may be retransmitted using a different retransmission number; or the first PUCCH may be retransmitted using the retransmission number of Msg4 HARQ-ACK, so as to facilitate the flexibility of network device indication or configuration.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the DCI includes a downlink assignment index (DAI) information field, and the DAI information field is used to indicate the first number of retransmissions.

[0053] In the above embodiment, by reusing the reserved DAI field in the DCI to indicate the first number of retransmissions, signaling resources can be effectively utilized and saved.

[0054] In combination with some embodiments of the first aspect, in some embodiments, the first number of retransmissions is one of multiple candidate numbers of retransmissions.

[0055] In the above embodiment, the first number of retransmissions indicated by the DCI may be one of a plurality of known candidate retransmission numbers, so that the network device may indicate a suitable number of retransmissions within a selectable range.

[0056] In combination with some embodiments of the first aspect, in some embodiments, part or all of the multiple candidate retransmission times are defined by the protocol.

[0057] In the above embodiment, part or all of the candidate retransmission times may be defined in a protocol-defined manner, and the network device indicates the first retransmission time through DCI in combination with the candidate retransmission times defined in the protocol.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0059] The terminal receives second configuration information sent by the network device, where the second configuration information includes multiple candidate retransmission times. For example, the second configuration information includes part or all of the aforementioned multiple candidate retransmission times.

[0060] In the above embodiment, the network device can configure some candidate retransmission times and indicate the first retransmission times in the part through DCI; or, the network device configures some candidate retransmission times and indicates the first retransmission times in combination with some candidate retransmission times defined by the protocol; or, the network device indicates the first retransmission times based on all configured candidate retransmission times, with high configuration flexibility.

[0061] In combination with some embodiments of the first aspect, in some embodiments, the second configuration information is sent via a radio resource control (RRC) message.

[0062] In the above embodiment, the terminal may receive the second configuration information sent by the network device through an RRC message to obtain the candidate retransmission times, so as to determine the first retransmission times according to the DCI.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0064] The terminal sends capability information to the network device, where the capability information is used to indicate whether the terminal supports the capability of retransmitting uplink information through the first PUCCH and / or whether the terminal supports the capability of retransmitting Msg4 HARQ-ACK.

[0065] In the above embodiment, the terminal reports capability information to the network device to check whether it supports the first capability and / or the second capability, so that the network device can perform reasonable operations or configurations based on the terminal capabilities.

[0066] In a second aspect, an embodiment of the present disclosure provides a method for retransmitting uplink information, the method comprising:

[0067] The network device sends a DCI to the terminal, where the DCI is used to indicate a first retransmission count for retransmitting uplink information;

[0068] The network device receives the uplink information retransmitted by the terminal through the first PUCCH according to the first retransmission number, wherein the first PUCCH includes: in addition to the PUCCH occupied by the Msg4 HARQ-ACK corresponding to Msg4 in the random access process, the public PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resources corresponding to the terminal.

[0069] In the above embodiment, the network device indicates the first retransmission number to the terminal by sending DCI, so that before receiving the dedicated PUCCH resource configuration, the terminal can retransmit the first PUCCH according to the first retransmission number, so as to enhance the coverage of information occupying common PUCCH resources other than Msg4 HARQ-ACK through the first retransmission number.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the DCI is a DCI for scheduling Msg4, or,

[0071] The DCI is a DCI used to schedule the PDSCH corresponding to the first PUCCH.

[0072] In combination with some embodiments of the second aspect, in some embodiments, the first retransmission number is the same as or different from the second retransmission number, and the second retransmission number is the retransmission number of Msg4 HARQ-ACK.

[0073] In combination with some embodiments of the second aspect, in some embodiments, the DCI includes a DAI information field, and the DAI information field is used to indicate the first number of retransmissions.

[0074] In combination with some embodiments of the second aspect, in some embodiments, the first number of retransmissions is one of multiple candidate numbers of retransmissions.

[0075] In combination with some embodiments of the second aspect, in some embodiments, some or all of the multiple candidate retransmission times are defined by the protocol.

[0076] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0077] The network device sends second configuration information to the terminal, where the second configuration information includes multiple candidate retransmission times. For example, the second configuration information includes part or all of the multiple candidate retransmission times in the aforementioned embodiment.

[0078] In combination with some embodiments of the second aspect, in some embodiments, the second configuration information is sent via a radio resource control RRC message.

[0079] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0080] The network device receives capability information sent by the terminal, where the capability information is used to indicate whether the terminal supports the capability of retransmitting information through the first PUCCH and / or whether the terminal supports the capability of retransmitting Msg4 HARQ-ACK.

[0081] In a third aspect, an embodiment of the present disclosure provides a terminal, including:

[0082] a transceiver module, configured to receive downlink control information DCI sent by a network device, wherein the DCI is used to indicate a first retransmission count for retransmitting uplink information;

[0083] The transceiver module is further configured to retransmit uplink information to the network device via a first physical uplink control channel PUCCH according to the first retransmission number;

[0084] Among them, the first PUCCH includes: in addition to the PUCCH occupied by the hybrid automatic repeat request confirmation feedback information Msg4 HARQ-ACK corresponding to message 4 Msg4 in the random access process, the common PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resource corresponding to the terminal.

[0085] In a fourth aspect, an embodiment of the present disclosure provides a network device, including:

[0086] a transceiver module, configured to send a DCI to a terminal, where the DCI is used to indicate a first retransmission count for retransmitting uplink information;

[0087] The transceiver module is also used to receive uplink information retransmitted by the terminal through the first PUCCH according to the first retransmission number, wherein the first PUCCH includes: in addition to the PUCCH occupied by the Msg4 HARQ-ACK corresponding to Msg4 in the random access process, the public PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resource corresponding to the terminal.

[0088] In a fifth aspect, an embodiment of the present disclosure provides a communication device, including:

[0089] one or more processors;

[0090] Wherein, the communication device is used to execute the method for retransmitting uplink information described in the first aspect.

[0091] In a sixth aspect, an embodiment of the present disclosure provides a communication device, including:

[0092] one or more processors;

[0093] Wherein, the communication device is used to execute the method for retransmitting uplink information described in the second aspect.

[0094] In a seventh aspect, an embodiment of the present disclosure provides a communication system, including a terminal and a network device, wherein:

[0095] The terminal is configured to implement the method for retransmitting uplink information according to the first aspect;

[0096] The network device is configured to implement the method for retransmitting uplink information described in the second aspect.

[0097] In an eighth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, wherein:

[0098] When the instruction is executed on a communication device, the communication device is caused to execute the method according to any one of the first aspect or any one of the second aspect.

[0099] In a ninth 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 method described in the optional implementation of the first and second aspects.

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

[0101] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0102] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform 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.

[0103] Embodiments of the present disclosure provide a method, apparatus, and medium for retransmitting uplink information.

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

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

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

[0107] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

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

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

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

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

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

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

[0114] In some embodiments, terms such as "time / frequency" and "time / frequency domain" refer to the time domain and / or the frequency domain.

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

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

[0117] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0118] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

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

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

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

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

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

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

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

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

[0127] As shown in FIG. 1 , a communication system 100 includes a terminal 101 and a network device 102 .

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

[0129] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

[0130] In some embodiments, the access network device 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 wireless fidelity (WiFi) system, but is not limited thereto.

[0131] Optionally, in a communication system applicable to NTN, network device 102 may include non-terrestrial base stations such as satellite base stations (or satellites) or drones, as well as terrestrial base stations such as ground stations or gateways. Optionally, terrestrial base stations may be used to connect satellite base stations with core network equipment. Optionally, terminal 101 may receive wireless resources from satellite base stations in different orbits.

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

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

[0134] In some embodiments, a core network device may be a single device comprising one or more network elements, or may be a plurality of devices or a group of devices, each comprising all or part of one or more network elements. A 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).

[0135] 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 provided by 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 provided by the embodiment of the present disclosure is also applicable to similar technical problems.

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

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

[0138] In the NTN, uplink enhancement can be performed on the HARQ-ACK for message 4 Msg4 reported using the public PUCCH, such as using repetition to enhance coverage.

[0139] FIG2 is an interactive diagram of a method for retransmitting uplink information according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to a method for retransmitting uplink information, the method comprising:

[0140] Step S2101 : Terminal 101 sends capability information to network device 102 .

[0141] In some embodiments, the capability information is used to indicate whether the terminal 101 supports the capability of retransmitting uplink information through the first PUCCH, and / or whether the terminal supports the capability of retransmitting Msg4 HARQ-ACK.

[0142] Optionally, when the terminal 101 supports the capability of retransmitting uplink information through the first PUCCH (referred to as supporting the first capability), it may support retransmitting uplink information through the first PUCCH, or simply referred to as retransmitting the first PUCCH as described in some embodiments.

[0143] Optionally, when the terminal 101 supports the capability of retransmitting Msg4 HARQ-ACK (referred to as supporting the second capability), it can support retransmitting Msg4 HARQ-ACK.

[0144] Optionally, the first capability and the second capability may be indicated by the same capability information, or may be indicated by different capability information respectively.

[0145] For example, when the same capability information is used to indicate whether a first capability and a second capability are supported, two bits of the capability information may be occupied, with each bit indicating whether the corresponding capability is supported. For example, when the value of the two bits is 01, it indicates that the terminal 101 does not support the first capability but supports the second capability; when the value of the two bits is 10, it indicates that the terminal 101 supports the first capability but not the second capability; when the value of the two bits is 11, it indicates that the terminal 101 supports both the first capability and the second capability; and when the value of the two bits is 00, it indicates that the terminal 101 does not support either the first capability or the second capability.

[0146] In some embodiments, the first PUCCH includes: in addition to the PUCCH occupied by Msg4 HARQ-ACK corresponding to Msg4 during the random access process, the public PUCCH whose time domain position is before the terminal 101 receives the first configuration information, and the first configuration information includes the dedicated PUCCH resource corresponding to the terminal 101.

[0147] Optionally, during the random access process, the terminal 101 may send Msg1 and Msg3 to the network device 102 , and receive Msg2 and Msg4 sent by the network device 102 accordingly.

[0148] Optionally, when the terminal 101 receives the Msg4 sent by the network device 102 via the PDSCH, the corresponding Msg4 HARQ-ACK is sent to the network device 102, so that the network device 102 performs the dedicated PUCCH configuration of the terminal 101 after receiving the Msg4 HARQ-ACK.

[0149] Optionally, the uplink information transmitted by the first PUCCH may include: information other than Msg4 HARQ-ACK transmitted using the public PUCCH after the terminal 101 sends Msg4 HARQ-ACK and before receiving the first configuration information, such as HARQ-ACK corresponding to other information.

[0150] In some embodiments, the network device 102 receives the capability information described above.

[0151] Optionally, the network device 102 may be a base station in a terrestrial network (TN), or a satellite base station or a ground base station in an NTN.

[0152] Step S2102 , the network device 102 sends second configuration information to the terminal 101 .

[0153] In some embodiments, the second configuration information includes a plurality of candidate repetition factors.

[0154] Optionally, the second configuration information may include part or all of a plurality of candidate retransmission times.

[0155] For example, the multiple candidate retransmission times are {1, 2, 4, 8}, and the second configuration information may configure all of the above candidate retransmission times, or only configure part of the candidate retransmission times such as {2, 8}.

[0156] In some embodiments, some or all of the multiple candidate retransmission times may also be protocol defined.

[0157] Optionally, when all multiple candidate retransmission times are defined by a protocol, step S2102 can be omitted.

[0158] Optionally, the protocol definition method can be used in combination with the configuration method, such as the protocol defines some candidate retransmission times, and the network device 102 configures the remaining candidate retransmission times through the second configuration information.

[0159] In some embodiments, the second configuration information is sent via an RRC message.

[0160] Optionally, the network device 102 sends the second configuration information by sending a system information block (SIB) to the terminal 101.

[0161] Step S2103 , the network device 102 sends DCI to the terminal 101 .

[0162] In some embodiments, the DCI is used to indicate a first retransmission count for retransmitting uplink information.

[0163] Optionally, the uplink information refers to information transmitted through the first PUCCH.

[0164] In some embodiments, the plurality of candidate retransmission times include a first retransmission time.

[0165] Optionally, in combination with the optional implementation of step S2102, after configuring some or all candidate retransmission times, the network device 102 may indicate the first retransmission time therein through DCI based on the configuration and / or protocol definition.

[0166] For example, the candidate retransmission times are {1, 2, 4, 8}, and the first retransmission time is 8.

[0167] Optionally, when all multiple candidate retransmission times are configured through the second configuration information, the network device 102 may perform DCI indication according to the configuration.

[0168] Optionally, when the second configuration information configures some candidate retransmission times, the network device 102 may make a DCI indication according to the configuration, or make a DCI indication according to the configuration and the candidate retransmission times defined by the protocol.

[0169] In some embodiments, the DCI is a DCI for scheduling Msg4.

[0170] In this embodiment, the DCI includes a DAI information field, and the DAI information field is used to indicate the first number of retransmissions.

[0171] Optionally, the DAI information field may occupy 2 reserved bits in the DCI.

[0172] In one example, the protocol defines four candidate retransmission counts {1, 2, 4, 8}. Different values ​​of the two bits in the DAI field correspond to different candidate retransmission counts. For example, when the two bits are 00, the candidate retransmission count is 1; when the two bits are 01, the candidate retransmission count is 2; when the two bits are 10, the candidate retransmission count is 4; and when the two bits are 11, the candidate retransmission count is 8.

[0173] In another example, two candidate retransmission counts {1, 8} are configured through protocol definition and network device 102. Different values ​​of the two bits in the DAI field correspond to different candidate retransmission counts. For example, when the two bits are 00, it corresponds to a candidate retransmission count of 1; when the two bits are 01, it corresponds to a candidate retransmission count of 8. Alternatively, a single bit in the DAI field indicates a different candidate retransmission count. For example, the MSB (Most significant bit) or LSB (Least significant bit) bit is selected for indication. When the single bit is 0, it corresponds to a candidate retransmission count of 1; when the single bit is 1, it corresponds to a candidate retransmission count of 8.

[0174] Optionally, in the DCI used to schedule Msg4, the DAI information field may indicate the second retransmission number, i.e., the retransmission number of Msg4 HARQ-ACK, and / or indicate the first retransmission number.

[0175] In this embodiment, the first retransmission number is the same as or different from the second retransmission number, and the second retransmission number is the retransmission number of Msg4 HARQ-ACK.

[0176] In one example, network device 102 configures a retransmission count that applies to Msg4 HARQ-ACK, i.e., the second retransmission count is the configured retransmission count. Network device 102 uses the DAI of the DCI that schedules Msg4 as the first retransmission count. In this example, the first retransmission count and the second retransmission count can be different, or the retransmission count corresponding to the first PUCCH can be indicated independently, without being bound to the retransmission count or retransmission count of Msg4 HARQ-ACK.

[0177] In another example, the network device 102 configures multiple retransmission times, such as two retransmission times, and indicates one retransmission time through the DAI of the DCI. The retransmission time indicated by the DAI applies to both Msg4 HARQ-ACK and the first PUCCH, i.e., the first retransmission time and the second retransmission time are both the retransmission times indicated by the DAI. In this example, the first retransmission time is the same as the second retransmission time, or the retransmission time of Msg4 HARQ-ACK is multiplexed as the retransmission time corresponding to the first PUCCH.

[0178] In some embodiments, the DCI is a DCI used to schedule the PDSCH corresponding to the first PUCCH.

[0179] In this embodiment, the DCI includes a DAI information field, and the DAI information field is used to indicate the first number of retransmissions.

[0180] Optionally, the DAI information field may occupy 2 reserved bits in the DCI. The number of retransmissions indicated by the 2 bits can be found in the description of the above embodiment and will not be repeated here.

[0181] In this embodiment, the DAI of the DCI that schedules the PDSCH is used to indicate the first retransmission number. The first retransmission number may be the same as or different from the second retransmission number.

[0182] Optionally, the second retransmission number may be determined based on the configuration of the network device 102, as described in the aforementioned example. Alternatively, the second retransmission number may be indicated by the DAI of the DCI that schedules Msg4. In this embodiment, the first retransmission number and the second retransmission number may be indicated by different DCIs, i.e., the first retransmission number is indicated separately, so that the retransmission corresponding to the first PUCCH is further decoupled from the retransmission of Msg4 HARQ-ACK.

[0183] In some embodiments, terminal 101 receives the above-mentioned DCI.

[0184] In step S2104 , the terminal 101 retransmits the uplink information to the network device 102 through the first PUCCH according to the first retransmission number.

[0185] In some embodiments, the number of times that the terminal 101 retransmits the uplink information through the first PUCCH (or simply described as retransmitting the first PUCCH) is the first retransmission number. When the retransmission number reaches the first retransmission number, the terminal 101 does not retransmit any more.

[0186] 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", and "field" can be used interchangeably.

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

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

[0189] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0190] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0191] In some embodiments, the terms "component carrier (CC)", "cell", "frequency carrier", "carrier frequency" and the like can be used interchangeably.

[0192] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0193] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

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

[0195] The method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2104. For example, steps S2103 to S2104 may be implemented as independent embodiments, steps S2102 to S2104 may be implemented as independent embodiments, and steps S2101 and S2103 to S2104 may be implemented as independent embodiments, but are not limited thereto.

[0196] In some embodiments, at least one of steps S2101 and S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the candidate retransmission times are configured through a protocol, step S2102 may be omitted.

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

[0198] FIG3a is a flow chart of a method for retransmitting uplink information according to an embodiment of the present disclosure. As shown in FIG3a , the embodiment of the present disclosure relates to a method for retransmitting uplink information, which is executed by terminal 101 and includes:

[0199] Step S3101: Send capability information.

[0200] Optionally, optional implementations of step S3101 can refer to step S2101 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0201] In some embodiments, the terminal 101 may send capability information to the network device 102, but is not limited thereto and may also send capability information to other entities.

[0202] Step S3102: Obtain second configuration information.

[0203] Optionally, optional implementations of step S3102 can refer to step S2102 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0204] In some embodiments, the terminal 101 may obtain the second configuration information from the network device 102, but is not limited thereto and may also obtain the second configuration information from other entities.

[0205] Step S3103, obtain DCI.

[0206] Optionally, optional implementations of step S3103 may refer to step S2103 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0207] In some embodiments, the terminal 101 may obtain the DCI from the network device 102, but is not limited thereto and may also obtain the DCI from other entities.

[0208] Step S3104: retransmit the uplink information through the first PUCCH according to the first retransmission number.

[0209] Optionally, optional implementations of step S3104 can refer to step S2104 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0210] In some embodiments, the terminal 101 may retransmit the uplink information to the network device 102, but is not limited thereto and may also retransmit the uplink information to other entities.

[0211] The method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3104. For example, steps S3103 to S3104 may be implemented as independent embodiments, steps S3102 to S3104 may be implemented as independent embodiments, and steps S3101 and S3103 to S3104 may be implemented as independent embodiments, but are not limited thereto.

[0212] In some embodiments, at least one of steps S3101 and S3102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0214] FIG3b is a flow chart of a method for retransmitting uplink information according to an embodiment of the present disclosure. As shown in FIG3b , an embodiment of the present disclosure relates to a method for retransmitting uplink information, which is executed by terminal 101 and includes:

[0215] Step S3201: Send capability information.

[0216] Optionally, optional implementations of step S3201 can refer to step S2101 in FIG. 2 , step S3101 in FIG. 3 a and other related parts in the embodiments involved in FIG. 2 and FIG. 3 a , which will not be described in detail here.

[0217] Step S3202, obtain DCI.

[0218] Optionally, optional implementations of step S3202 may refer to step S2103 in FIG. 2 , step S3103 in FIG. 3 a and other related parts in the embodiments involved in FIG. 2 and FIG. 3 a , which will not be described in detail here.

[0219] Step S3203: retransmit the uplink information through the first PUCCH according to the first retransmission number.

[0220] Optionally, optional implementations of step S3203 may refer to step S2104 in FIG. 2 , step S3104 in FIG. 3 a and other related parts in the embodiments involved in FIG. 2 and FIG. 3 a , which will not be described in detail here.

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

[0222] FIG3c is a flow chart of a method for retransmitting uplink information according to an embodiment of the present disclosure. As shown in FIG3c, an embodiment of the present disclosure relates to a method for retransmitting uplink information, which is executed by terminal 101 and includes:

[0223] Step S3301: Receive DCI sent by network device 102.

[0224] Optionally, optional implementations of step S3301 can refer to step S2103 in FIG. 2 , step S3103 in FIG. 3 a and other related parts in the embodiments involved in FIG. 2 and FIG. 3 a , which will not be described in detail here.

[0225] In some embodiments, the DCI is used to indicate a first retransmission count for retransmitting uplink information.

[0226] In some embodiments, the DCI is a DCI used to schedule Msg4, or the DCI is a DCI used to schedule a physical downlink shared channel PDSCH corresponding to the first PUCCH.

[0227] Optionally, the first retransmission number is the same as or different from the second retransmission number, and the second retransmission number is the retransmission number of Msg4 HARQ-ACK.

[0228] In some embodiments, the DCI includes a downlink allocation index DAI information field, and the DAI information field is used to indicate the first number of retransmissions.

[0229] In some embodiments, the first retransmission number is one of a plurality of candidate retransmission numbers.

[0230] Optionally, some or all of the multiple candidate retransmission times are protocol defined.

[0231] Optionally, the method may further include: the terminal receiving second configuration information sent by the network device, where the second configuration information includes a plurality of candidate retransmission times.

[0232] Optionally, the second configuration information is sent via a radio resource control RRC message.

[0233] Optionally, before step S3301, the method may further include: the terminal sending capability information to the network device, the capability information being used to indicate whether the terminal supports the capability of retransmitting information through the first PUCCH, and / or whether the terminal supports the capability of retransmitting Msg4 HARQ-ACK.

[0234] In step S3302 , the terminal 101 retransmits uplink information to the network device 102 through the first PUCCH according to the first retransmission number.

[0235] Optionally, optional implementations of step S3302 can refer to step S2104 in FIG. 2 , step S3104 in FIG. 3 a and other related parts in the embodiments involved in FIG. 2 and FIG. 3 a , which will not be described in detail here.

[0236] In some embodiments, the first PUCCH includes: in addition to the PUCCH occupied by Msg4 HARQ-ACK corresponding to Msg4 during the random access process, the public PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resources corresponding to the terminal.

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

[0238] FIG4a is a flow chart of a method for retransmitting uplink information according to an embodiment of the present disclosure. As shown in FIG4a , an embodiment of the present disclosure relates to a method for retransmitting uplink information, which is executed by a network device 102 and includes:

[0239] Step S4101, obtaining capability information.

[0240] Optionally, optional implementations of step S4101 can refer to step S2101 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0241] In some embodiments, the network device 102 may obtain capability information from the terminal 101, but is not limited thereto and may also obtain capability information from other entities.

[0242] Step S4102: Send second configuration information.

[0243] Optionally, optional implementations of step S4102 can refer to step S2102 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0244] In some embodiments, the network device 102 may send the second configuration information to the terminal 101 , but is not limited thereto and may also send the second configuration information to other entities.

[0245] Step S4103, send DCI.

[0246] Optionally, optional implementations of step S4103 may refer to step S2103 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0247] In some embodiments, the network device 102 may send DCI to the terminal 101, but is not limited thereto and may also send DCI to other entities.

[0248] In step S4104, the network device 102 obtains uplink information retransmitted via the first PUCCH.

[0249] Optionally, optional implementations of step S4104 can refer to step S2104 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0250] In some embodiments, the network device 102 may receive retransmitted uplink information from the terminal 101, but is not limited thereto and may also receive retransmitted uplink information from other entities.

[0251] The method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4104. For example, steps S4103 to S4104 may be implemented as independent embodiments, steps S4102 to S4104 may be implemented as independent embodiments, and steps S4101 and S4103 to S4104 may be implemented as independent embodiments, but are not limited thereto.

[0252] In some embodiments, at least one of steps S4101 and S4102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0254] FIG4 b is a flow chart of a method for retransmitting uplink information according to an embodiment of the present disclosure. As shown in FIG4 b , an embodiment of the present disclosure relates to a method for retransmitting uplink information, which is executed by a network device 102 and includes:

[0255] Step S4201, obtain capability information.

[0256] Optionally, optional implementations of step S4101 can refer to step S2101 in FIG. 2 , step S4101 in FIG. 4 a and other related parts in the embodiments involved in FIG. 2 and FIG. 4 a , which will not be described in detail here.

[0257] Step S4202, send DCI.

[0258] Optionally, optional implementations of step S4202 can refer to step S2103 in FIG. 2 , step S4103 in FIG. 4 a and other related parts in the embodiments involved in FIG. 2 and FIG. 4 a , which will not be described in detail here.

[0259] In step S4203 , the network device 102 obtains uplink information retransmitted via the first PUCCH.

[0260] Optionally, optional implementations of step S4203 may refer to step S2104 in FIG. 2 , step S4104 in FIG. 4 a and other related parts in the embodiments involved in FIG. 2 and FIG. 4 a , which will not be described in detail here.

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

[0262] FIG4c is a flow chart of a method for retransmitting uplink information according to an embodiment of the present disclosure. As shown in FIG4c, an embodiment of the present disclosure relates to a method for retransmitting uplink information, which is executed by the network device 102 and includes:

[0263] Step S4301, sending DCI to terminal 101.

[0264] Optionally, optional implementations of step S4301 can refer to step S2103 in FIG. 2 , step S4103 in FIG. 4 a and other related parts in the embodiments involved in FIG. 2 and FIG. 4 a , which will not be described in detail here.

[0265] In some embodiments, the DCI is used to indicate a first retransmission count for retransmitting uplink information.

[0266] In some embodiments, the DCI is a DCI used to schedule Msg4, or the DCI is a DCI used to schedule a physical downlink shared channel PDSCH corresponding to the first PUCCH.

[0267] Optionally, the first retransmission number is the same as or different from the second retransmission number, and the second retransmission number is the retransmission number of Msg4 HARQ-ACK.

[0268] In some embodiments, the DCI includes a downlink allocation index DAI information field, and the DAI information field is used to indicate the first number of retransmissions.

[0269] In some embodiments, the first retransmission number is one of a plurality of candidate retransmission numbers.

[0270] Optionally, some or all of the multiple candidate retransmission times are protocol defined.

[0271] Optionally, the method may further include: the network device sends second configuration information to the terminal, where the second configuration information includes a plurality of candidate retransmission times.

[0272] Optionally, the second configuration information is sent via a radio resource control RRC message.

[0273] Optionally, before step S3301, the method may further include: the network device receives capability information sent by the terminal, where the capability information is used to indicate whether the terminal supports the capability of retransmitting information through the first PUCCH and / or whether the terminal supports the capability of retransmitting Msg4 HARQ-ACK.

[0274] In step S4302, the network device 102 receives uplink information retransmitted by the terminal 101 through the first PUCCH according to the first retransmission number.

[0275] Optionally, optional implementations of step S4302 may refer to step S2104 in FIG. 2 , step S4104 in FIG. 4 a and other related parts in the embodiments involved in FIG. 2 and FIG. 4 a , which will not be described in detail here.

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

[0277] The method for retransmitting uplink information provided in the embodiments of the present disclosure illustrates whether the number of retransmissions of Msg4 HARQ-ACK can be applied to the first PUCCH and how to configure the number of retransmissions of the first PUCCH. This involves whether the retransmission of the first PUCCH and Msg4 HARQ-ACK can be unbound, or the relationship between the number of retransmissions of the first PUCCH and the DAI indication and RRC configuration. Some examples are listed below:

[0278] Example 1:

[0279] The UE reports the retransmission capability for PUCCH x and Msg 4 HARQ-ACK respectively.

[0280] Optionally, PUCCH x corresponds to the first PUCCH in the aforementioned embodiment.

[0281] Optionally, the retransmission capability corresponds to the first capability and / or the second capability of the aforementioned embodiment.

[0282] Example 2:

[0283] PUCCH x and msg4 HARQ-ACK may have the same or different retransmission times.

[0284] Example 3:

[0285] The indication of DAI may be based on the RRC configuration, or not based on the RRC configuration, or partially based on the RRC configuration.

[0286] In this example, the following specific implementations are listed:

[0287] Method 1: The base station configures a repetition factor of {8} through the SIB (RRC). For UEs with PUCCH x and msg4 HARQ-ACK retransmission capabilities, the UE behavior is as follows:

[0288] For msg4 HARQ-ACK, the number of retransmissions is 8; that is, the number of retransmissions configured by the base station, without considering the value indicated by the DAI in the DCI scheduling msg 4;

[0289] For PUCCH X, one optional example is: the number of retransmissions is the value indicated by the DAI in the DCI that schedules msg 4; another optional example is: the number of retransmissions is the value indicated by the DAI in the DCI that schedules the PDSCH.

[0290] When DAI indicates the number of retransmissions, one optional example is: the value indicated by DAI is a predefined value, and 2 bits correspond to {1, 2, 4, 8} respectively; another optional example is: the value indicated by DAI is a predefined value + the value configured by RRC, as in this example, 1 bit indicates 1 or 8, or 2 bits correspond to {1, 8} respectively.

[0291] The implementation of Method 1 can be found in the following more specific examples:

[0292] Example 1: The base station configures a retransmission count of {8} through SIB (RRC). For a UE with PUCCH x and msg4 HARQ-ACK retransmission capabilities, the UE behavior is as follows:

[0293] For msg4 HARQ-ACK, the number of msg4 HARQ-ACK retransmissions is 8;

[0294] For PUCCH x, the number of retransmissions is the value indicated by the DAI in the DCI scheduling Msg 4. The candidate value indicated by the DAI is a predefined value, with 2 bits corresponding to {1, 2, 3, 4}. Assuming the DAI in the PDCCH scheduling Msg 4 indicates 01 (binary), the number of retransmissions for PUCCH x is 2. Optionally, the candidate value corresponds to the candidate retransmission number in the aforementioned embodiment. Optionally, the predefined value corresponds to the protocol definition in the aforementioned embodiment.

[0295] Example 2: The base station configures a retransmission count of {8} through SIB (RRC). For a UE with PUCCH x and msg4 HARQ-ACK retransmission capabilities, the UE behavior is as follows:

[0296] For msg4 HARQ-ACK, the number of msg4 HARQ-ACK retransmissions is 8;

[0297] For PUCCH x, the number of retransmissions is the value indicated by the DAI in the DCI that schedules the PDSCH corresponding to PUCCH x. The candidate value indicated by the DAI is a predefined value combined with the value configured by the RRC. The predefined value is 1, so the candidate value is {1, 8}. Assuming that the DAI in the DCI that schedules the PDSCH corresponding to PUCCH x indicates 01 (binary), the number of retransmissions of PUCCH x is 8. Optionally, the RRC configuration corresponds to the network device configuration of the aforementioned embodiment, such as configured through the second configuration information.

[0298] Mode 2: The base station configures two retransmission times {2, 8} through SIB (RRC). For UEs with PUCCH x and msg4 HARQ-ACK retransmission capabilities, the UE behavior is as follows:

[0299] For msg4 HARQ-ACK, the DAI in the PDCCH that schedules Msg4 indicates 01 (LSB, binary), so the number of msg4 HARQ-ACK retransmissions is 8;

[0300] For PUCCH X, one optional example is: the number of retransmissions is the value indicated by the DAI in the DCI that schedules msg 4; another optional example is: the number of retransmissions is the value indicated by the DAI in the DCI that schedules the PDSCH.

[0301] When DAI indicates the number of retransmissions, one optional example is: the value indicated by DAI is a predefined value, and 2 bits correspond to {1, 2, 4, 8} respectively; another optional example is: the value indicated by DAI is a predefined value combined with the value configured by RRC.

[0302] The implementation of Method 2 can be found in the following more specific examples:

[0303] Example 1: The base station configures two retransmission times {2, 8} through SIB (RRC). For a UE with PUCCH x and msg4 HARQ-ACK retransmission capabilities, the UE behavior is as follows:

[0304] For msg4 HARQ-ACK, the DAI in the PDCCH that schedules Msg4 indicates 01 (LSB, binary), so the number of msg4 HARQ-ACK retransmissions is 8;

[0305] For PUCCH x, the number of retransmissions is the value indicated by the DAI in the DCI that schedules Msg 4. The candidate value indicated by the DAI is a predefined value, and the 2 bits correspond to {1, 2, 4, 8} respectively. Since the DAI in the PDCCH that schedules Msg 4 indicates 01 (binary), the number of retransmissions of PUCCH x is 2.

[0306] Example 2: The base station configures two retransmission times {2, 8} through SIB (RRC). For a UE with PUCCH x and msg4 HARQ-ACK retransmission capabilities, the UE behavior is as follows:

[0307] For msg4 HARQ-ACK, the DAI in the PDCCH that schedules Msg4 indicates 01 (LSB, binary), so the number of msg4 HARQ-ACK retransmissions is 8;

[0308] For PUCCH x, the number of retransmissions is the value indicated by the DAI in the DCI of the PDSCH corresponding to PUCCH x. The candidate value indicated by the DAI is a predefined value combined with the value configured by RRC. The predefined value is 1, then the candidate value is {1, 2, 8}. Assuming that the DAI in the DCI of the PDSCH corresponding to PUCCH x indicates 01 (binary), then the number of retransmissions of PUCCH x is 2.

[0309] Example 4:

[0310] PUCCH x refers to the PUCCH before the dedicated PUCCH configuration, excluding Msg4 HARQ-ACK.

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

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

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

[0314] Figure 5a is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in Figure 5a, the terminal 5100 may include: at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module 5101 is used to receive downlink control information DCI sent by a network device, and the DCI is used to indicate a first retransmission number of uplink information; the transceiver module 5101 is also used to retransmit the uplink information to the network device through a first physical uplink control channel PUCCH according to the first retransmission number; wherein the first PUCCH includes: in addition to the PUCCH occupied by the hybrid automatic repeat request confirmation feedback information Msg4 HARQ-ACK corresponding to message 4 Msg4 in the random access process, the common PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resource corresponding to the terminal.

[0315] Optionally, the transceiver module 5101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods, which will not be described in detail here. Optionally, the processing module is used to perform at least one of the other steps performed by the terminal 101 in any of the above methods, which will not be described in detail here.

[0316] Figure 5b is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure. As shown in Figure 5b, the network device 5200 may include: at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is used to send a DCI to the terminal, where the DCI is used to indicate a first retransmission count of retransmitted uplink information; the transceiver module 5201 is also used to receive uplink information retransmitted by the terminal through a first PUCCH according to the first retransmission count, wherein the first PUCCH includes: in addition to the PUCCH occupied by the Msg4 HARQ-ACK corresponding to Msg4 in the random access process, a common PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes a dedicated PUCCH resource corresponding to the terminal.

[0317] Optionally, the transceiver module 5201 is configured to execute at least one of the communication steps of sending and / or receiving performed by the network device 102 in any of the above methods, which are not described in detail here. Optionally, the processing module is configured to execute at least one of the other steps performed by the network device 102 in any of the above methods, which are not described in detail here.

[0318] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0319] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0320] Figure 6a is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 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 implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal implementing any of the above methods. Communication device 6100 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.

[0321] As shown in Figure 6a, the communication device 6100 includes one or more processors 6101. The processor 6101 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 the communication protocol 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. Optionally, the communication device 6100 is used to perform any of the above methods. Optionally, one or more processors 6101 are used to call instructions to enable the communication device 6100 to perform any of the above methods.

[0322] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method, and the processor 6101 performs at least one of the other steps. In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface 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.

[0323] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Alternatively, all or part of the memories 6103 may be located outside the communication device 6100. In alternative embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memory 6102 and may be configured to receive data from the memory 6102 or other devices, or to send data to the memory 6102 or other devices. For example, the interface circuits 6104 may read data stored in the memory 6102 and send the data to the processor 6101.

[0324] The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6a. 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.

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

[0326] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.

[0327] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Alternatively, all or part of memory 6203 may be located external to chip 6200. Optionally, interface circuit 6202 is connected to memory 6203 and may be used to receive data from memory 6203 or other devices, or may be used to send data to memory 6203 or other devices. For example, interface circuit 6202 may read data stored in memory 6203 and send the data to processor 6201.

[0328] In some embodiments, the interface circuit 6202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 6202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 6202 performs data exchange between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps.

[0329] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0330] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 executes 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.

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

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

[0333] In the method disclosed herein, the terminal receives the first number of retransmissions indicated by the network device through the DCI, so that before receiving the dedicated PUCCH resource configuration, the terminal can retransmit the first PUCCH according to the first number of retransmissions, so as to enhance the coverage of the uplink information occupying the common PUCCH resources except Msg4 HARQ-ACK through the first number of retransmissions.

Claims

1. A method for retransmitting uplink information, the method comprising: The terminal receives downlink control information DCI sent by the network device, where the DCI is used to indicate a first retransmission number of retransmissions of uplink information; The terminal retransmits the uplink information to the network device through a first physical uplink control channel PUCCH according to the first retransmission number; Among them, the first PUCCH includes: in addition to the PUCCH occupied by the hybrid automatic repeat request confirmation feedback information Msg4 HARQ-ACK corresponding to message 4 Msg4 in the random access process, the common PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resources corresponding to the terminal.

2. The method of claim 1, wherein: The DCI is a DCI for scheduling the Msg4, or, The DCI is a DCI used to schedule a physical downlink shared channel PDSCH corresponding to the first PUCCH.

3. The method according to claim 1 or 2, wherein: The DCI includes a downlink allocation index DAI information field, and the DAI information field is used to indicate the first retransmission number.

4. The method according to any one of claims 1 to 3, wherein: The method further comprises: The terminal receives second configuration information sent by the network device, where the second configuration information includes a plurality of candidate retransmission times.

5. The method of claim 4, wherein: The second configuration information is sent via a radio resource control RRC message.

6. The method according to any one of claims 1 to 5, wherein: The method further comprises: The terminal sends capability information to the network device, where the capability information is used to indicate whether the terminal supports a capability of retransmitting uplink information through the first PUCCH and / or whether the terminal supports a capability of retransmitting the Msg4 HARQ-ACK.

7. A method for retransmitting uplink information, the method comprising: The network device sends a DCI to the terminal, where the DCI is used to indicate a first retransmission number of retransmission uplink information; The network device receives the uplink information retransmitted by the terminal through the first PUCCH according to the first retransmission number, wherein the first PUCCH includes: except for the PUCCH occupied by Msg4 HARQ-ACK corresponding to Msg4 in the random access process, the common PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resources corresponding to the terminal.

8. The method of claim 7, wherein: The DCI is a DCI for scheduling the Msg4, or, The DCI is a DCI used to schedule the PDSCH corresponding to the first PUCCH.

9. The method according to claim 7 or 8, wherein: The DCI includes a DAI information field, and the DAI information field is used to indicate the first retransmission number.

10. The method according to any one of claims 7 to 9, wherein: The method further comprises: The network device sends second configuration information to the terminal, where the second configuration information includes a plurality of candidate retransmission times.

11. The method of claim 10, wherein: The second configuration information is sent via a radio resource control RRC message.

12. The method according to any one of claims 7 to 11, wherein: The method further comprises: The network device receives capability information sent by the terminal, where the capability information is used to indicate whether the terminal supports a capability of retransmitting uplink information through the first PUCCH and / or whether the terminal supports a capability of retransmitting the Msg4 HARQ-ACK.

13. A terminal, comprising: A transceiver module, used for receiving downlink control information DCI sent by a network device, wherein the DCI is used for indicating a first retransmission number of retransmission uplink information; The transceiver module is further configured to retransmit the uplink information to the network device through a first physical uplink control channel PUCCH according to the first retransmission number; Among them, the first PUCCH includes: in addition to the PUCCH occupied by the hybrid automatic repeat request confirmation feedback information Msg4 HARQ-ACK corresponding to message 4 Msg4 in the random access process, the common PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes the dedicated PUCCH resources corresponding to the terminal.

14. A network device comprising: A transceiver module, used for sending a DCI to a terminal, where the DCI is used for indicating a first retransmission number of retransmission uplink information; The transceiver module is also used to receive the uplink information retransmitted by the terminal through the first PUCCH according to the first retransmission number, wherein the first PUCCH includes: in addition to the PUCCH occupied by the Msg4 HARQ-ACK corresponding to Msg4 in the random access process, the common PUCCH whose time domain position is before the terminal receives the first configuration information, and the first configuration information includes The dedicated PUCCH resources corresponding to the terminal are included.

15. A communication device, comprising: one or more processors; The communication device is used to execute the method for retransmitting uplink information according to any one of claims 1 to 6.

16. A communication device, comprising: one or more processors; The communication device is used to execute the method for retransmitting uplink information according to any one of claims 7 to 12.

17. A communication system, comprising a terminal and a network device, wherein: The terminal is configured to implement the method for retransmitting uplink information according to any one of claims 1 to 6; The network device is configured to implement the method for retransmitting uplink information according to any one of claims 7 to 12.

18. A storage medium storing instructions, wherein: When the instruction is executed on a communication device, the communication device is caused to execute the method according to any one of claims 1 to 6 or any one of claims 7 to 12.

Images