Uplink communication method and apparatus

Abstract

Embodiments of the present disclosure disclose an uplink communication method and apparatus. The method comprises: receiving first information, the first information comprising at least one group of configuration information, and the configuration information being used for configuring a physical uplink shared channel (PUSCH); and determining a PUSCH corresponding to one group of configuration information, and sending a random access message on the PUSCH. The random access message is Msg3, and a terminal does not perform transmission of Msg1 and Msg2 before sending Msg3. The delay of random access can be effectively shortened, uplink capacity can be effectively increased, and the waste of configuration resources can be reduced, thereby improving the communication efficiency of a system and increasing the spectrum and resource utilization rates.

Description

Uplink communication method and device Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to an uplink communication method and apparatus. Background Technology

[0002] To shorten random access latency and increase uplink capacity, enabling the cell to serve more users simultaneously, various random access schemes can be considered, such as multi-user multiplexing based on orthogonal cover codes (OCC), to enhance uplink capacity.

[0003] Summary of the Invention

[0004] To improve uplink capacity and shorten random access latency, this disclosure proposes an uplink communication method and apparatus.

[0005] The first aspect of this disclosure provides an uplink communication method, which is executed by a terminal, and the method includes:

[0006] Receive first information, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH);

[0007] Determine the PUSCH corresponding to one set of configuration information, and send a random access message on the PUSCH;

[0008] The random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

[0009] A second aspect of this disclosure provides an uplink communication method, which is executed by a network device, and the method includes:

[0010] Send first information, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH);

[0011] Receive random access messages sent on the PUSCH, wherein the PUSCH is a PUSCH corresponding to one of the sets of configuration information determined by the terminal;

[0012] The random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

[0013] A third aspect of this disclosure provides a terminal, the terminal comprising:

[0014] The transceiver module is used to receive first information, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH);

[0015] The processing module is used to determine the PUSCH corresponding to one set of configuration information and send a random access message on the PUSCH.

[0016] The random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

[0017] A fourth aspect of this disclosure provides a network device, the network device comprising:

[0018] The transceiver module is used to send first information, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH);

[0019] The transceiver module is also used to receive random access messages sent on the PUSCH, wherein the PUSCH is a PUSCH corresponding to one of the sets of configuration information determined by the terminal;

[0020] The random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

[0021] The solution proposed in this embodiment receives first information, which includes at least one set of configuration information used to configure the Physical Uplink Shared Channel (PUSCH); determines the PUSCH corresponding to one set of configuration information; and sends a random access message on the PUSCH. The random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3. This effectively shortens the random access latency, effectively increases uplink capacity, reduces the waste of configuration resources, effectively improves the communication efficiency of the system, improves spectrum and resource utilization, and improves the robustness of transmission. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0023] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure;

[0024] Figure 2A is an interactive schematic diagram of an uplink communication method provided in an embodiment of this disclosure;

[0025] Figures 3A-3C are schematic flowcharts of an uplink communication method provided in an embodiment of this disclosure;

[0026] Figures 4A-4B are schematic flowcharts of an uplink communication method provided in an embodiment of this disclosure;

[0027] Figure 5 is a flowchart illustrating an uplink communication method provided in an embodiment of this disclosure;

[0028] Figure 6A is a schematic diagram of the structure of a terminal provided in an embodiment of this disclosure;

[0029] Figure 6B is a schematic diagram of the structure of a network device provided in an embodiment of this disclosure;

[0030] Figure 7A is a schematic diagram of the structure of a communication device provided in an embodiment of this disclosure;

[0031] Figure 7B is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0032] This disclosure presents an uplink communication method and apparatus.

[0033] In a first aspect, embodiments of this disclosure provide an uplink communication method, the method comprising:

[0034] The terminal receives first information, which includes at least one set of configuration information for configuring the Physical Uplink Shared Channel (PUSCH); determines the PUSCH corresponding to one set of configuration information, and sends a random access message on the PUSCH; the random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

[0035] In the above embodiments, the latency of random access can be effectively shortened, the uplink capacity can be effectively increased, the waste of configuration resources can be reduced, the communication efficiency of the system can be effectively improved, the spectrum and resource utilization can be improved, and the robustness of transmission can be improved.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, each set of the above configuration information includes at least one of the following:

[0037] One or more demodulation reference signal (DMRS) sequences; one or more DMRS ports; orthogonal coverage code (OCC) sequence related information; periodic time-domain resources, wherein the time-domain resources of one period include one or more PUSCH transmission opportunities; frequency-domain resources, wherein the frequency-domain resources include one or more PUSCH transmission opportunities.

[0038] In the above embodiments, at least one DMRS sequence, DMRS port, etc. can be configured for PUSCH resources, enabling multiple users to reuse the same resources, enhancing uplink capacity, and effectively reducing the waste of configuration resources.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the above configuration information is in multiple groups, and each group of the above configuration information is associated with different random access message groups; wherein, each random access message group corresponds to a different random access message load size.

[0040] In the above embodiments, different random access message load sizes can be associated with different resources, enabling the terminal to select resources based on implementation, effectively reducing the waste of configuration resources and improving random access efficiency.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, each packet of the aforementioned random access message is configured with a corresponding threshold for reference signal reception quality; or,

[0042] Each of the above random access messages is configured with a corresponding number of PUSCH retransmissions.

[0043] In the above embodiments, corresponding reference signal reception quality or number of retransmissions can be configured for different resources, enabling the terminal to select different PUSCH resources based on its actual signal transmission quality. This allows for more targeted resource selection, effectively reducing resource waste, improving resource utilization, increasing the success rate and efficiency of random access, and enhancing transmission robustness.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, determining a set of PUSCHs corresponding to the above configuration information includes:

[0045] Based on the load size of the random access message to be sent by the terminal and / or the reference signal reception quality of the terminal, the corresponding configuration information is determined.

[0046] In the above embodiments, the terminal is able to select different PUSCH resources based on its own implementation, enabling more targeted resource selection, effectively reducing the waste of configuration resources, and improving resource utilization.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the parameters in the configuration information associated with different random access message packets are configured independently; the parameters include at least one of the following:

[0048] Modulation and coding scheme (MCS); number of frequency domain resource units occupied by one PUSCH transmission; number of time domain resource units occupied by one PUSCH transmission.

[0049] In the above embodiments, the parameter configurations between different PUSCH resource configurations are independent, enabling the configuration of PUSCH resources with different parameters, allowing the terminal to select different PUSCH resources and effectively reducing the waste of configuration resources.

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

[0051] The terminal receives second information, which is used to indicate the index information of the configuration information; the index information is also used by the terminal to determine the physical downlink shared channel (PDSCH) corresponding to the configuration information.

[0052] In the above embodiments, the PDSCH corresponding to different resource configurations can be indicated by the index information, enabling the terminal to avoid unnecessary blind detection and / or reception of downlink channels, effectively reducing terminal power consumption and improving information transmission and system communication efficiency.

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

[0054] Determine the initial scrambling sequence of Msg3 based on at least one of the following:

[0055] The DMRS sequence corresponding to Msg3 above; the DMRS port corresponding to Msg3 above; the DMRS pattern corresponding to Msg3 above; the orthogonal overlay code (OCC) sequence of the above terminal.

[0056] In the above embodiments, interference between different terminals can be randomized, effectively reducing interference between terminals, improving transmission robustness, improving message transmission efficiency, and effectively increasing uplink capacity.

[0057] Secondly, embodiments of this disclosure provide an uplink communication method, the method comprising:

[0058] Send first information, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH); receive a random access message sent on the PUSCH, the PUSCH being one of the PUSCHs corresponding to the configuration information determined by the terminal; the random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

[0059] In the above embodiments, the latency of random access can be effectively shortened, the uplink capacity can be effectively increased, the waste of configuration resources can be reduced, the communication efficiency of the system can be effectively improved, the spectrum and resource utilization can be improved, and the robustness of transmission can be improved.

[0060] In conjunction with some embodiments of the second aspect, in some embodiments, each set of the above configuration information includes at least one of the following:

[0061] One or more demodulation reference signal (DMRS) sequences; one or more DMRS ports; orthogonal coverage code (OCC) sequence related information; periodic time-domain resources, wherein the time-domain resources of one period include one or more PUSCH transmission opportunities; frequency-domain resources, wherein the frequency-domain resources include one or more PUSCH transmission opportunities.

[0062] In conjunction with some embodiments of the second aspect, in some embodiments, the above configuration information is in multiple groups, and each group of the above configuration information is associated with different random access message groups; wherein, each random access message group corresponds to a different random access message load size.

[0063] In conjunction with some embodiments of the second aspect, in some embodiments, each packet of the aforementioned random access message is configured with a corresponding threshold for reference signal reception quality; or,

[0064] Each of the above random access messages is configured with a corresponding number of PUSCH retransmissions.

[0065] In conjunction with some embodiments of the second aspect, in some embodiments, one of the above-mentioned sets of configuration information is determined by the terminal based on the load size of the random access message to be sent and / or the reference signal reception quality of the terminal.

[0066] In conjunction with some embodiments of the second aspect, in some embodiments, the parameters in the configuration information associated with different random access message packets are configured independently; the parameters include at least one of the following:

[0067] Modulation and coding scheme (MCS); number of frequency domain resource units occupied by one PUSCH transmission; number of time domain resource units occupied by one PUSCH transmission.

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

[0069] Send a second message, which is used to indicate the index information of the configuration information; the index information is also used by the terminal to determine the physical downlink shared channel (PDSCH) corresponding to the configuration information.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the initial scrambling code sequence of Msg3 described above is determined based on at least one of the following:

[0071] The DMRS sequence corresponding to Msg3 above; the DMRS port corresponding to Msg3 above; the DMRS pattern corresponding to Msg3 above; the orthogonal overlay code (OCC) sequence of the above terminal.

[0072] Thirdly, embodiments of this disclosure provide an uplink communication method, the method comprising:

[0073] The network device sends first information to the terminal, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH); the terminal determines the PUSCH corresponding to one set of the configuration information and sends a random access message on the PUSCH.

[0074] In the above embodiments, the latency of random access can be effectively shortened, the uplink capacity can be effectively increased, the waste of configuration resources can be reduced, the communication efficiency of the system can be effectively improved, and the spectrum and resource utilization can be improved.

[0075] Fourthly, embodiments of this disclosure provide a terminal, which includes a transceiver module and a processing module; wherein the terminal is used to execute the first aspect and optional implementations of the first aspect.

[0076] Fifthly, embodiments of this disclosure provide a network device, which includes a transceiver module and a processing module; wherein the network device is used to execute the second aspect and optional implementations of the second aspect.

[0077] In a sixth aspect, embodiments of this disclosure provide a communication device comprising: one or more processors; wherein the communication device is configured to execute the first aspect and optional implementations thereof.

[0078] In a seventh aspect, embodiments of this disclosure provide a communication device comprising: one or more processors; wherein the communication device is configured to execute the second aspect and optional implementations thereof.

[0079] Eighthly, embodiments of this disclosure provide a communication system comprising: a terminal and a network device; wherein the terminal is configured to perform the method described in the first aspect and optional implementations thereof, and the network device is configured to perform the method described in the second aspect and optional implementations thereof.

[0080] Ninthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect and its optional implementation, as well as the second aspect and its optional implementation.

[0081] In a tenth aspect, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in the first aspect and its optional implementation, the second aspect and its optional implementation.

[0082] In one aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect and its alternative implementations, the second aspect and its alternative implementations.

[0083] In a twelfth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to the first aspect and its optional implementations, the second aspect, and its optional implementations.

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

[0085] This disclosure provides an uplink communication method and apparatus. In some embodiments, the terms "uplink communication method" and "information processing method" and "communication method" can be used interchangeably; the terms "uplink communication apparatus" and "information processing apparatus" and "communication apparatus" can be used interchangeably; and the terms "uplink communication system" and "information processing system" and "communication system" can be used interchangeably.

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

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

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

[0089] In this disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the aforementioned," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular or a plural expression.

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

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

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

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

[0094] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

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

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

[0097] In some embodiments, the terms “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 lower than,” and “above” can be used interchangeably, as can the terms “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”.

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

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

[0100] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)," "base station (BS)," "radio base station," or "fixed station." In some embodiments, it may also be understood as "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," or "bandwidth part (BWP)."

[0101] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)," "user terminal," "Narrow Band-Internet of Things (NB-IoT) device," "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.

[0102] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0103] 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, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0104] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

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

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

[0108] As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.

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

[0110] In some embodiments, network device 102 may be a node or device that connects a terminal to a wireless network. The network device may include, but is not limited to, nodes such as satellites or drones in an uplink communication network, evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), next-generation RAN node (NG-RAN node), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

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

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

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

[0114] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0115] The embodiments disclosed herein can be applied to Non-terrestrial Networks (NTN), IoT-NTN, 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), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Narrow Band-IoT (NB-IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0116] In some embodiments, to shorten random access latency and improve uplink capacity, a random access scheme without Msg1 / 2 (also known as Msg1 / 2-less) can be considered. The terminal can directly send Msg3 without transmitting through the Physical Random Access Channel (PRACH).

[0117] In some embodiments, for the terminal, directly sending Msg3 without receiving Msg2 can avoid insufficient uplink coverage due to limited downlink transmission capacity. Furthermore, to enhance the capacity of Msg3 while avoiding waste of configured semi-static resources, multi-user multiplexing schemes can be considered, such as using different Demodulation Reference Signal (DMRS) ports / sequences and different Orthogonal Cover Code (OCC) sequences.

[0118] In some embodiments, to reduce interference from neighboring cells and randomize the interference signal, a pseudo-random sequence is typically used to scramble the codeword before modulation. The initial scrambling sequence for Msg3 Narrow-band Physical Uplink Shared Channel (NPUSCH) format 1 can be generated using the following formula:

[0119] Where, n s This is the first slot for the current codeword transmission. In the case of repetition, under a single-tone subcarrier, C... init Regeneration; In multi-tone mode, a redundancy version (RV) repetition (containing M_identical_NPUSCH symbol-based slot-level repetitions) ends, C init Regenerate. RNTIFor traditional Msg3 transmission, it is the Temporary Cell-Radio Network Temporary Identity (TC-RNTI) assigned by the eNB through the Random Access Response (RAR). Used to ensure randomization of interference between adjacent cells.

[0120] In some embodiments, for transmissions excluding Msg1 / 2, a possible method for generating the Radio Network Temporary Identity (RNTI) is similar to the method for generating the RA (Random Access)-RNTI in a legacy Random Access Channel (RACH) procedure (e.g., the same as the RA-RNTI generation method for LTE terminals), and the RNTI can be directly determined by the time-frequency domain location sent by Msg3.

[0121] Furthermore, the base station will schedule Msg4 based on the RNTI, while the terminal will scramble Msg3 PUSCH through the RNTI.

[0122] In some embodiments, the RA-RNTI associated with the PRACH that transmits the random access preamble is calculated as follows:

[0123] RA-RNTI = 1 + t_id + 10 * f_id.

[0124] Where t_id is the index of the first subframe of a specific PRACH (0≤t_id<10), and f_id is the index of the specific PRACH in ascending frequency domain order within the subframe (0≤f_id<6), except for NB-IoT UE, BL UE, or UE in enhanced coverage.

[0125] In some embodiments, for an NB-IoT UE, the RA-RNTI associated with the PRACH that transmits the random access preamble is calculated as follows: RA-RNTI = 1 + floor(SFN_id / 4) + 256 * carrier_id.

[0126] In some embodiments, the initial sequence of the NR PUSCH codeword scrambling sequence is generated as follows:

[0127] For MsgA PUSCH, in order to reduce interference between different UEs and achieve randomization of interference between UEs, a Preamble ID is introduced to generate the initial sequence of MsgA PUSCH.

[0128] In some embodiments, for contention-based Msg3 transmission without Msg1 / 2, even with OCC multiplexing, due to interference between UEs, a maximum of 2 UEs can be multiplexed to ensure access performance. However, in NTN / IoT-NTN networks, there are many users simultaneously initiating random access.

[0129] In summary, one issue that needs to be considered is how to achieve interference randomization when different UEs are transmitting Msg3 on the same resources, so as to maximize the probability of successful Msg3 transmission of Msg1 / 2-less.

[0130] The uplink communication method and apparatus provided in this disclosure will now be described in detail with reference to the accompanying drawings.

[0131] Figure 2A is an interactive schematic diagram of an uplink communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the present disclosure relates to an uplink communication method, which includes:

[0132] In step S2101, network device 102 sends the first information.

[0133] In some embodiments, terminal 101 receives the first information sent by network device 102.

[0134] In some embodiments, the first information mentioned above includes at least one set of configuration information.

[0135] In some embodiments, the above configuration information is used to configure the Physical Uplink Shared Channel (PUSCH).

[0136] In some embodiments, each of the above-mentioned at least one set of configuration information can configure a PUSCH resource.

[0137] In some embodiments, each of the above-mentioned at least one set of configuration information can configure a semi-static PUSCH resource.

[0138] In some embodiments, each of the above-mentioned at least one set of configuration information can configure a Configuration Grant (CG) PUSCH resource.

[0139] In some embodiments, the terminal 101 receives the first information and can determine at least one corresponding PUSCH resource based on at least one set of configuration information included in the first information.

[0140] In some embodiments, terminal 101 can select a PUSCH resource to send a random access message based on its own implementation, etc.

[0141] In some embodiments, different terminals 101 may randomly select the same PUSCH resource to send random access messages.

[0142] In some embodiments, each set of configuration information in the above-mentioned at least one set of configuration information is independent, and the parameter configurations in different configuration information can be the same or different.

[0143] In some embodiments, each set of configuration information may include at least one of the following:

[0144] One or more DMRS sequences;

[0145] One or more DMRS ports;

[0146] Information related to orthogonal covering code (OCC) sequences;

[0147] Periodic time-domain resources, wherein a periodic time-domain resource includes one or more PUSCH transmission occasions (PO);

[0148] Frequency domain resources, wherein the frequency domain resources include one or more PUSCH transmission opportunities.

[0149] Optionally, the aforementioned OCC sequence-related information may include at least one of the following: OCC sequence; OCC length; enable information; de-enable information, etc.

[0150] Optionally, the multiple PUSCH transmission opportunities included in the time domain resources of one cycle can be used for PUSCH repetition.

[0151] Optionally, the aforementioned frequency domain resources may include a single PUSCH transmission opportunity or multiple PUSCH transmission opportunities, wherein the multiple PUSCH transmission opportunities are frequency division multiplexing (FDM), that is, multiple frequency division multiplexing (FDMed) PUSCH transmission opportunities.

[0152] In some embodiments, the above configuration information is in multiple groups, and each group of configuration information is associated with a different packet of random access messages; wherein, each packet of random access messages corresponds to a different payload size of random access messages.

[0153] As an example, the configuration information CG PUSCH configuration#0 and CG PUSCH configuration#1 are associated with the random access message packet Group A, and another group of configuration information CG PUSCH configuration#2 is associated with the random access message packet Group B. Among them, each packet of random access messages corresponds to a different payload size of random access messages. That is, Group A and Group B correspond to different payload sizes of random access messages.

[0154] Optionally, the size of the payload corresponding to each packet of random access messages may include at least one threshold, for example, it may be a range of payload size values.

[0155] For example, the payload size of the random access messages corresponding to Group A is a1 < x < a2, that is, the random access messages with a payload greater than a1 and less than a2 correspond to Group A; it can also be that the payload size of the random access messages corresponding to Group A is x > a3, that is, the random access messages with a payload greater than a3 correspond to Group A; it can also be that the payload size of the random access messages corresponding to Group A is x < a4, that is, the random access messages with a payload less than a4 correspond to Group A, and so on.

[0156] Optionally, the payload size corresponding to each packet of random access messages can be configured by the network device 102.

[0157] Optionally, the threshold of the payload size corresponding to each packet of random access messages can be configured by the network device 102.

[0158] Optionally, the network device 102 can configure a corresponding reference signal reception quality threshold for each packet of random access messages. For example, the network device 102 can configure corresponding reference signal reception quality thresholds for Group A and Group B. Among them, the reference signal reception quality thresholds corresponding to each packet of random access messages are independent, and the reference signal reception quality thresholds corresponding to different packets can be the same or different.

[0159] Optionally, the reference signal reception quality can be, for example, reference signal received power (RSRP), reference signal received quality (RSRQ), reference signal received signal-to-noise ratio (RSSNR), signal to interference plus noise ratio (SNR), etc.

[0160] Optionally, network device 102 can configure a corresponding number of repetitions for each random access message packet. The number of repetitions for each random access message packet is independent; different packets may have the same or different number of repetitions.

[0161] In some embodiments, the first information mentioned above may be a System Information Block (SIB).

[0162] In some embodiments, the name of the first information is not limited, and may be, for example, "system information", "system information block", "system configuration", "semi-static configuration", "PUSCH configuration", "configuration authorization information", etc.

[0163] In step S2102, terminal 101 determines PUSCH.

[0164] In some embodiments, the terminal 101 can determine one set of configuration information based on at least one set of configuration information included in the first information, and then determine the PUSCH corresponding to the configuration information.

[0165] In some embodiments, terminal 101 may determine at least one set of configuration information associated with a packet of a corresponding random access message based on the size of the load of the random access message to be sent.

[0166] In some embodiments, terminal 101 may determine at least one set of configuration information associated with a packet of a corresponding random access message based on the reference signal reception quality.

[0167] In some embodiments, terminal 101 may determine at least one set of configuration information associated with a packet of a corresponding random access message based on the size of the payload of the random access message to be sent and the quality of the reference signal reception.

[0168] In some embodiments, terminal 101 may select a PUSCH resource corresponding to one set of configuration information from at least one set of configuration information associated with a determined random access message packet to send the random access message.

[0169] In some embodiments, terminal 101 selects a time-frequency domain resource from a set of configuration information to send a random access message.

[0170] Optionally, terminal 101 may also select one of the multiple DMRS ports included in the configuration information for sending random access messages. Similarly, terminal 101 may also select one of the multiple DMRS sequences included in the configuration information for sending random access messages.

[0171] Optionally, terminal 101 may also select one of the multiple OCC sequences included in the configuration information for sending random access messages.

[0172] In some embodiments, terminal 101 may also select the PUSCH based on its own implementation. For example, terminal 101 may select the PUSCH corresponding to the configuration information of the most recently available PUSCH transmission opportunity to send a random access message.

[0173] In some embodiments, the parameters in the configuration information associated with packets of different random access messages are configured independently by the network device 102. These parameters may include at least one of the following:

[0174] Modulation and Coding Scheme (MCS);

[0175] The number of frequency domain resource units occupied by one PUSCH transmission;

[0176] The number of time-domain resource units occupied by one PUSCH transmission.

[0177] Optionally, the aforementioned frequency domain resource unit can be a resource block (RB).

[0178] Optionally, the aforementioned time-domain resource unit can be a symbol.

[0179] As an example, network device 102 can configure Group A with fewer RBs or fewer symbols, while configuring Group B with more RBs or more symbols, etc.

[0180] In step S2103, terminal 101 determines the initial sequence of scrambling codes for the random access message.

[0181] In various embodiments of this application, the aforementioned random access message may be Msg3, and Msg1 and Msg2 are not transmitted before the terminal 101 sends Msg3.

[0182] In some embodiments, terminal 101 may generate the initial scrambling code sequence for the above-mentioned random access message based on at least one of the following information:

[0183] The DMRS sequence corresponding to the above random access message;

[0184] The DMRS port corresponding to the above random access message;

[0185] The DMRS pattern corresponding to the above random access message;

[0186] Terminal 101 uses the orthogonal overlay code (OCC) sequence.

[0187] In step S2104, terminal 101 sends the aforementioned random access message on the PUSCH.

[0188] In some embodiments, terminal 101 sends a random access message to network device 102 on a determined PUSCH resource.

[0189] In some embodiments, network device 102 receives a random access message sent by terminal 101.

[0190] In some embodiments, the time-domain resources of one period of configuration information determined by terminal 101 may include multiple PUSCH transmission opportunities. These multiple PUSCH transmission opportunities are time-division multiplexing (TDM), that is, the time-domain resources of one period may include multiple TDMed PUSCH transmission opportunities. Each PUSCH transmission opportunity can be used as the initial time-domain position for terminal 101 to send the random access message.

[0191] Optionally, terminal 101 can select a PUSCH transmission timing as the initial time-domain position for sending the aforementioned random access message. For example, terminal 101 can select the nearest time-domain transmission position (i.e., the nearest PUSCH transmission timing) to transmit the CG PUSCH and send the aforementioned random access message.

[0192] In step S2105, network device 102 sends the second information.

[0193] In some embodiments, network device 102 can send second information to terminal 101.

[0194] In some embodiments, terminal 101 receives second information sent by network device 102.

[0195] In some embodiments, the second information is used to indicate the index information of the configuration information of the terminal 101.

[0196] The aforementioned index information is also used by terminal 101 to determine the physical downlink shared channel (PDSCH) corresponding to the configuration information.

[0197] In some embodiments, the above index information can be used by terminal 101 to determine the PDSCH of the corresponding Msg4.

[0198] In some embodiments, the second information may include the scrambled Radio Network Temporary Identity (RNTI) in the Downlink Control Information (DCI) of the scheduling Msg4.

[0199] In some embodiments, the second information described above may be the DMRS of DCI or the DMRS of PDSCH.

[0200] In some embodiments, the second information described above may be included in a new field of the DCI or in an existing field of the DCI.

[0201] In the above embodiments, the terminal 101 can determine the PDSCH of Msg4 corresponding to the configuration information based on the second information, thereby avoiding unnecessary blind detection of the Physical Downlink Control Channel (PDCCH) and / or reception of the PDSCH, and effectively reducing the power consumption of the terminal.

[0202] In some embodiments, the terms “eNB”, “gNB”, “base station”, and “NG-RAN node” can be used interchangeably.

[0203] In some embodiments, the terms "carrier," "band," and "frequency" can be used interchangeably.

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

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

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

[0207] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

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

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

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

[0211] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0212] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

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

[0214] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2105. For example, step 2101 may be implemented as an independent embodiment, step 2102 may be implemented as an independent embodiment, step 2103 may be implemented as an independent embodiment, step 2104 may be implemented as an independent embodiment, steps 2101+2102 may be implemented as an independent embodiment, steps 2101+2102+2103 may be implemented as an independent embodiment, steps 2101+2102+2103+2104+2105 may be implemented as an independent embodiment, and so on, but are not limited thereto.

[0215] In some embodiments, steps S2103 and S2105 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0216] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2A.

[0217] Figure 3A is a flowchart illustrating an uplink communication method according to an embodiment of the present disclosure. As shown in Figure 3A, this embodiment of the present disclosure relates to an uplink communication method, which is executed by terminal 101, and includes:

[0218] Step S3101: Receive the first information sent by network device 102.

[0219] The optional implementation of step S3101 can be found in the optional implementation of step S2101 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0220] Step S3102, determine PUSCH.

[0221] The optional implementation of step S3102 can be found in the optional implementation of step S2102 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0222] Step S3103: Determine the initial sequence of scrambling codes for the random access message.

[0223] The optional implementation of step S3103 can be found in the optional implementation of step S2103 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0224] Step S3104: Send the random access message to network device 102 on the PUSCH.

[0225] The optional implementation of step S3104 can be found in the optional implementation of step S2104 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0226] Step S3105: Receive the second information sent by network device 102.

[0227] The optional implementation of step S3105 can be found in the optional implementation of step S2105 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0228] The communication method involved in the embodiments of this disclosure may include at least one of steps S3101 to S3105. For example, step 3101 may be implemented as an independent embodiment, step 3102 may be implemented as an independent embodiment, step 3103 may be implemented as an independent embodiment, step 3104 may be implemented as an independent embodiment, steps 3101+3102 may be implemented as an independent embodiment, steps 3101+3102+3103 may be implemented as an independent embodiment, steps 3101+3102+3103+3104+3105 may be implemented as an independent embodiment, and so on, but not limited thereto.

[0229] In some embodiments, steps S3103 and S3105 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0230] Figure 3B is a flowchart illustrating an uplink communication method according to an embodiment of the present disclosure. As shown in Figure 3B, this embodiment of the present disclosure relates to an uplink communication method, which is executed by terminal 101, and includes:

[0231] Step S3201: Receive the first information sent by network device 102.

[0232] The optional implementation of step S3201 can be found in step S2101 of Figure 2A, the optional implementation of step S3101 of Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0233] Step S3202: Determine PUSCH.

[0234] The optional implementation of step S3202 can be found in step S2102 of Figure 2A, the optional implementation of step S3102 of Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0235] Step S3203: Determine the initial sequence of scrambling codes for the random access message.

[0236] The optional implementation of step S3203 can be found in step S2103 of Figure 2A, the optional implementation of step S3103 of Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0237] Step S3204: Send the random access message to network device 102 on the PUSCH.

[0238] The optional implementation of step S3204 can be found in step S2104 of Figure 2A, the optional implementation of step S3104 of Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0239] The communication method involved in the embodiments of this disclosure may include at least one of steps S3201 to S3204. For example, step 3201 may be implemented as an independent embodiment, step 3202 may be implemented as an independent embodiment, step 3203 may be implemented as an independent embodiment, step 3204 may be implemented as an independent embodiment, steps 3201+3202 may be implemented as an independent embodiment, steps 3201+3202+3203 may be implemented as an independent embodiment, steps 3201+3202+3203+3204 may be implemented as an independent embodiment, etc., but not limited thereto.

[0240] In some embodiments, step S3203 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0241] Figure 3C is a flowchart illustrating an uplink communication method according to an embodiment of the present disclosure. As shown in Figure 3C, this embodiment of the present disclosure relates to an uplink communication method, which is executed by terminal 101, and includes:

[0242] Step S3301: Receive the first information sent by network device 102.

[0243] The optional implementation of step S3301 can be found in the optional implementation of step S2101 in Figure 2A, step S3101 in Figure 3A, step S3201 in Figure 3B, and other related parts in the embodiments involved in Figures 2A, 3A, and 3B, which will not be repeated here.

[0244] Step S3302, determine PUSCH.

[0245] The optional implementation of step S3302 can be found in the optional implementation of step S2102 in Figure 2A, step S3102 in Figure 3A, step S3202 in Figure 3B, and other related parts in the embodiments involved in Figures 2A, 3A, and 3B, which will not be repeated here.

[0246] Step S3303: Send the random access message to network device 102 on the PUSCH.

[0247] The optional implementation of step S3303 can be found in the optional implementations of step S2104 in Figure 2A, step S3104 in Figure 3A, and step S3204 in Figure 3B, as well as other related parts in the embodiments involved in Figures 2A, 3A, and 3B, which will not be repeated here.

[0248] The communication method involved in the embodiments of this disclosure may include at least one of steps S3301 to S3304. For example, step 3301 may be implemented as an independent embodiment, step 3302 may be implemented as an independent embodiment, step 3303 may be implemented as an independent embodiment, step 3304 may be implemented as an independent embodiment, steps 3301+3302 may be implemented as an independent embodiment, steps 3301+3302+3303 may be implemented as an independent embodiment, steps 3301+3302+3303+3304 may be implemented as an independent embodiment, etc., but not limited thereto.

[0249] Figure 4A is a flowchart illustrating an uplink communication method according to an embodiment of the present disclosure. As shown in Figure 4A, this embodiment of the present disclosure relates to an uplink communication method, which is executed by network device 102, and includes:

[0250] Step S4101: Send the first information to terminal 101.

[0251] The optional implementation of step S4101 can be found in the optional implementation of step S2101 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0252] Optionally, the first information mentioned above is used by terminal 101 to determine PUSCH. The optional implementation of this information can be found in the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0253] Step S4102: Receive the random access message sent by terminal 101 on PUSCH.

[0254] The optional implementation of step S4102 can be found in the optional implementation of step S2104 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0255] Optionally, the initial scrambling sequence of the random access message is generated by terminal 101. The optional implementation of this can be found in the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0256] Step S4103: Send the second information to terminal 101.

[0257] The optional implementation of step S4103 can be found in the optional implementation of step S2105 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0258] The communication method involved in the embodiments of this disclosure may include at least one of steps S4101 to S4103. For example, step 4101 may be implemented as an independent embodiment, step 4102 may be implemented as an independent embodiment, step 4103 may be implemented as an independent embodiment, step 4101+4102 may be implemented as an independent embodiment, step 4101+4102+4103 may be implemented as an independent embodiment, etc., but is not limited thereto.

[0259] In some embodiments, step S4103 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0260] Figure 4B is a flowchart illustrating an uplink communication method according to an embodiment of the present disclosure. As shown in Figure 4B, this embodiment of the present disclosure relates to an uplink communication method, which is executed by network device 102, and includes:

[0261] Step S4201: Send the first information to terminal 101.

[0262] The optional implementation of step S4201 can be found in step S2101 of Figure 2A, the optional implementation of step S4101 of Figure 4A, and other related parts in the embodiments involved in Figures 2A and 4A, which will not be repeated here.

[0263] Step S4202: Receive the random access message sent by terminal 101 on PUSCH.

[0264] Optional implementations of step S4202 can be found in step S2104 of Figure 2A, optional implementations of step S4102 of Figure 4A, and other related parts in the embodiments involved in Figures 2A and 4A, which will not be repeated here.

[0265] The communication method involved in the embodiments of this disclosure may include at least one of steps S4201 to S4202. For example, step 4201 may be implemented as a standalone embodiment, step 4202 may be implemented as a standalone embodiment, step 4201+4202 may be implemented as a standalone embodiment, etc., but is not limited thereto.

[0266] Figure 5 is a flowchart illustrating an uplink communication method according to an embodiment of the present disclosure. As shown in Figure 5, the method involved in this embodiment of the present disclosure is used in a communication system 100, and the method includes:

[0267] In step S5101, network device 102 sends first information to terminal 101, the first information including at least one set of configuration information.

[0268] In step S5102, terminal 101 determines the PUSCH corresponding to one set of configuration information and sends a random access message on the PUSCH.

[0269] The optional implementations of steps S5101-S5102 can be found in any or more embodiments of the above-mentioned embodiments in Figures 2A, 3A-3C, and 4A-4B, as well as other related parts of the embodiments involved in Figures 2A, 3A-3C, and 4A-4B.

[0270] In some embodiments, the above methods may include the methods described in the embodiments of the communication system side, terminal side, network device side, etc., which will not be repeated here.

[0271] In this implementation or embodiment, unless there is contradiction, each step can be independent, arbitrarily combined or exchanged in order, optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementations or other embodiments.

[0272] The following is an exemplary description of the methods described in the above embodiments.

[0273] In this embodiment of the application, terminal 101 can send Msg3 based on the semi-static PUSCH resources of SIB message configuration grant (CG).

[0274] In this embodiment, terminal 101 does not need to send Msg1 and Msg2, and can directly send Msg3 through CG PUSCH resources.

[0275] In some embodiments, different terminals may randomly select the same CG PUSCH resource.

[0276] In some embodiments, the above SIB message can configure one or more sets of semi-static PUSCH resources.

[0277] Each set of semi-static PUSCH resources is configured independently, and each configuration includes at least one of the following: one or more DMRS sequences; one or more DMRS ports; OCC sequence; periodic time-domain resources; frequency-domain resources.

[0278] Optionally, the aforementioned OCC sequence may include information such as OCC length and enable / de-enable.

[0279] Optionally, a time-domain period may contain one or more time-domain PUSCH transmission occasions, and multiple time-domain PUSCH transmission occasions can be used to transmit PUSCH repetitions.

[0280] Optionally, the aforementioned frequency domain resources can be frequency-division multiplexed PUSCH transmission opportunities or single PUSCH occasions in the frequency domain.

[0281] In some embodiments, the above SIB message can configure multiple sets of semi-static PUSCH resources, and different CG PUSCHs can be associated with different Msg3 payload sizes.

[0282] As an example, CG PUSCH configuration#0,1 is associated with the Msg3 size of Group A, and CG configuration#2 is associated with the Msg3 size of Group B; optionally, the threshold value of the payload size of Group A / B can be configured by network device 102 (e.g., gNB).

[0283] Optionally, network device 102 can configure corresponding reference signal reception quality thresholds for Group A / B.

[0284] One possible approach is that Group A and Group B can correspond to independent repetition counts.

[0285] In some embodiments, the above SIB message can configure multiple sets of semi-static PUSCH resources. The terminal 101 can select one time-frequency domain resource under one of the configurations, and / or one DMRS port / sequence, and / or one OCC sequence, to send Msg3PUSCH.

[0286] In some embodiments, terminal 101 can select between Msg3 Group A and Group B based on its own Msg3 payload size and / or reference signal reception quality. Further, it selects appropriate PUSCH resources from one or more CG PUSCH sets associated with the selected Msg3 group for Msg3 transmission.

[0287] As an example, one possible implementation is that terminal 101 can select the resource configured in the CG configuration corresponding to the most recently sendable PUSCH occasion to send Msg3.

[0288] In some embodiments, the parameters such as MCS, the number of RBs and / or the number of symbols in a single PSUCH transmission are independent of each other in the configuration of CG PUSCH associated with different Msg3 groups.

[0289] As an example, network device 102 can configure Msg3 Group A with fewer RBs or fewer symbols, while configuring Msg3 Group B with more RBs or more symbols, etc.

[0290] In some embodiments, the CG PUSCH resource configured in the SIB message above can be configured with multiple time-division multiplexed (TDMed) PUSCH transmission occasions (POs) per cycle. The multiple TDMed POs are different time-domain positions for initiating the initial transmission of Msg3.

[0291] Optionally, terminal 101 may select the nearest time-domain transmission location for CG PUSCH transmission.

[0292] In some embodiments, when multiple CG PUSCH resources are configured, different CG PUSCH resources may overlap in the time domain. Therefore, at least one of the following methods can be considered to distinguish the Msg4 PDSCH corresponding to different CG configurations (this allows the terminal to avoid unnecessary blind detection of PDCCH and / or reception of PDSCH, reducing terminal power consumption):

[0293] Optionally, relevant index information for different CG configurations can be added to the scrambled RNTI of the DCI for scheduling Msg4.

[0294] Alternatively, the DMRS of DCI / PDSCH can be used to indicate different CG configurations.

[0295] Alternatively, existing indicator fields and / or newly added indicator fields in the DCI can be used to indicate different CG configurations.

[0296] In some embodiments, the initial sequence corresponding to the Msg3 PUSCH scrambling sequence may be generated based on at least one of the following factors: DMRS sequence; DMRS port; DMRS pattern; OCC sequence.

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

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

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

[0300] Figure 6A is a schematic diagram of the network device proposed in an embodiment of this disclosure. As shown in Figure 6A, the terminal 6100 may include at least one of a transceiver module 6101, a processing module 6102, etc. In some embodiments, the transceiver module 6101 is used to receive first information, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH); the processing module 6102 is used to determine the PUSCH corresponding to one set of the configuration information, and send a random access message on the PUSCH; the random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

[0301] Optionally, each set of the above configuration information includes at least one of the following: one or more demodulation reference signal (DMRS) sequences; one or more DMRS ports; orthogonal coverage code (OCC) sequence related information; periodic time-domain resources, wherein the time-domain resources of one period include one or more PUSCH transmission opportunities; and frequency-domain resources, wherein the frequency-domain resources include one or more PUSCH transmission opportunities.

[0302] Optionally, the above configuration information is in multiple groups, and each group of the above configuration information is associated with different random access message groups; wherein, each random access message group corresponds to a different random access message load size.

[0303] Optionally, each packet of the aforementioned random access message is configured with a corresponding threshold for reference signal reception quality; or,

[0304] Each of the above random access messages is configured with a corresponding number of PUSCH retransmissions.

[0305] Optionally, the processing module 6102 is specifically used to: determine the corresponding configuration information based on the load size of the random access message to be sent by the terminal and / or the reference signal reception quality of the terminal.

[0306] Optionally, the parameters in the configuration information associated with different random access messages are configured independently; the parameters include at least one of the following: modulation and coding scheme (MCS); number of frequency domain resource units occupied by one PUSCH transmission; and number of time domain resource units occupied by one PUSCH transmission.

[0307] Optionally, the transceiver module 6101 is further configured to: receive second information, the second information being used to indicate index information of the configuration information; the index information is further used by the terminal to determine the physical downlink shared channel (PDSCH) corresponding to the configuration information.

[0308] Optionally, the processing module 6102 is further configured to: determine the initial scrambling code sequence of the Msg3 based on at least one of the following information: the DMRS sequence corresponding to the Msg3; the DMRS port corresponding to the Msg3; the DMRS pattern corresponding to the Msg3; and the orthogonal overlay code (OCC) sequence of the terminal.

[0309] Optionally, the transceiver module is used to perform at least one of the communication steps (such as steps S2101, S2104, S2105, but not limited thereto) performed by the terminal in any of the above methods, which will not be elaborated here.

[0310] Optionally, the above processing module is used to execute at least one of the other steps executed by the terminal in any of the above methods (such as steps S2102, S2103, but not limited thereto), which will not be described in detail here.

[0311] Figure 6B is a schematic diagram of another network device according to an embodiment of this disclosure. As shown in Figure 6B, the network device 6200 may include at least one of a transceiver module 6201, a processing module 6202, etc. In some embodiments, the transceiver module 6201 is used to send first information, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH); the transceiver module 6201 is also used to receive a random access message sent on the PUSCH, the PUSCH being a PUSCH corresponding to one of the sets of configuration information determined by the terminal; the random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

[0312] Optionally, each set of the above configuration information includes at least one of the following: one or more demodulation reference signal (DMRS) sequences; one or more DMRS ports; orthogonal coverage code (OCC) sequence related information; periodic time-domain resources, wherein the time-domain resources of one period include one or more PUSCH transmission opportunities; and frequency-domain resources, wherein the frequency-domain resources include one or more PUSCH transmission opportunities.

[0313] Optionally, the above configuration information is in multiple groups, and each group of the above configuration information is associated with different random access message groups; wherein, each random access message group corresponds to a different random access message load size.

[0314] Optionally, each packet of the aforementioned random access message is configured with a corresponding threshold for reference signal reception quality; or,

[0315] Each of the above random access messages is configured with a corresponding number of PUSCH retransmissions.

[0316] Optionally, one of the above-mentioned sets of configuration information is determined by the terminal based on the load size of the random access message to be sent and / or the reference signal reception quality of the terminal.

[0317] Optionally, the parameters in the configuration information associated with different random access messages are configured independently; the parameters include at least one of the following: modulation and coding scheme (MCS); number of frequency domain resource units occupied by one PUSCH transmission; and number of time domain resource units occupied by one PUSCH transmission.

[0318] Optionally, the transceiver module 6201 is further configured to: send second information, the second information being used to indicate the index information of the configuration information; the index information is further used by the terminal to determine the physical downlink shared channel (PDSCH) corresponding to the configuration information.

[0319] Optionally, the initial scrambling code sequence of Msg3 is determined based on at least one of the following: the DMRS sequence corresponding to Msg3; the DMRS port corresponding to Msg3; the DMRS pattern corresponding to Msg3; and the orthogonal overlay code (OCC) sequence of the terminal.

[0320] Optionally, the transceiver module is used to perform at least one of the communication steps (such as steps S2101, S2104, S2105, but not limited thereto) performed by the network device in any of the above methods, which will not be described in detail here.

[0321] Optionally, the above processing module is used to perform at least one of the other steps performed by the network device in any of the above methods, which will not be elaborated here.

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

[0323] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

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

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

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

[0327] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the transceivers 7103 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2104, S2105, but not limited thereto), and the processor 7101 performs at least one of other steps (e.g., steps S2102, S2103, but not limited thereto).

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

[0329] In some embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuit 7104 is connected to the memory 7102, and the interface circuit 7104 can be used to receive signals from the memory 7102 or other devices, and can be used to send signals to the memory 7102 or other devices. For example, the interface circuit 7104 can read instructions stored in the memory 7102 and send the instructions to the processor 7101.

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

[0331] Figure 7B is a schematic diagram of the structure of the chip 7200 according to an embodiment of this disclosure. For cases where the communication device 7100 can be a chip or a chip system, the schematic diagram of the chip 7200 shown in Figure 7B can be referenced, but is not limited thereto.

[0332] Chip 7200 includes one or more processors 7201, which are used to perform any of the above methods.

[0333] In some embodiments, chip 7200 further includes one or more interface circuits 7202. Optionally, the interface circuit 7202 is connected to memory 7203, and the interface circuit 7202 can be used to receive signals from memory 7203 or other devices, and the interface circuit 7202 can be used to send signals to memory 7203 or other devices. For example, the interface circuit 7202 can read instructions stored in memory 7203 and send the instructions to processor 7201.

[0334] In some embodiments, the interface circuit 7202 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 7201 performs at least one of the other steps.

[0335] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

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

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

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

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

[0340] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The aforementioned computer program product includes one or more computer programs. When the aforementioned computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The aforementioned computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The aforementioned computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the aforementioned computer program can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The aforementioned computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The aforementioned available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0341] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0342] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0343] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the above claims.

Claims

1. An uplink communication method, characterized in that, The method is executed by a terminal, and the method includes: Receive first information, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH); Determine the PUSCH corresponding to one set of configuration information, and send a random access message on the PUSCH; The random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

2. The method according to claim 1, characterized in that, Each set of configuration information includes at least one of the following: One or more demodulation reference signal (DMRS) sequences; One or more DMRS ports; Information related to orthogonal covering code (OCC) sequences; Periodic time-domain resources, wherein a periodic time-domain resource includes one or more PUSCH transmission opportunities; Frequency domain resources, wherein the frequency domain resources include one or more PUSCH transmission opportunities.

3. The method according to claim 1 or 2, characterized in that, The configuration information is in multiple groups, and each group of configuration information is associated with different groups of random access messages; Each random access message packet corresponds to a different random access message load size.

4. The method according to claim 3, characterized in that, Each packet of the random access message is configured with a corresponding threshold for reference signal reception quality; or, Each random access message packet is configured with a corresponding number of PUSCH retransmissions.

5. The method according to claim 3 or 4, characterized in that, Determining the PUSCH corresponding to a set of configuration information includes: Based on the payload size of the random access message to be sent by the terminal, and / or the reference signal reception quality of the terminal, the corresponding configuration information is determined.

6. The method according to claim 5, characterized in that, The parameters in the configuration information associated with different random access message packets are configured independently; The parameter includes at least one of the following: Modulation and coding scheme (MCS); The number of frequency domain resource units occupied by one PUSCH transmission; The number of time-domain resource units occupied by one PUSCH transmission.

7. The method according to claim 3, characterized in that, The method further includes: Receive second information, which is used to indicate the index information of the configuration information; The index information is also used by the terminal to determine the Physical Downlink Shared Channel (PDSCH) corresponding to the configuration information.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: The initial scrambling sequence of Msg3 is determined based on at least one of the following: The DMRS sequence corresponding to Msg3; The DMRS port corresponding to Msg3; The DMRS pattern corresponding to Msg3; The orthogonal overlay code (OCC) sequence of the terminal.

9. An uplink communication method, characterized in that, The method is performed by a network device, and the method includes: Send first information, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH); Receive random access messages sent on the PUSCH, wherein the PUSCH is a PUSCH corresponding to one of the sets of configuration information determined by the terminal; The random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

10. The method according to claim 9, characterized in that, Each set of configuration information includes at least one of the following: One or more demodulation reference signal (DMRS) sequences; One or more DMRS ports; Information related to orthogonal covering code (OCC) sequences; Periodic time-domain resources, wherein a periodic time-domain resource includes one or more PUSCH transmission opportunities; Frequency domain resources, wherein the frequency domain resources include one or more PUSCH transmission opportunities.

11. The method according to claim 10 or 11, characterized in that, The configuration information is in multiple groups, and each group of configuration information is associated with different groups of random access messages; Each random access message packet corresponds to a different random access message load size.

12. The method according to claim 12, characterized in that, Each packet of the random access message is configured with a corresponding threshold for reference signal reception quality; or, Each random access message packet is configured with a corresponding number of PUSCH retransmissions.

13. The method according to claim 12 or 13, characterized in that, One of the sets of configuration information is determined by the terminal based on the load size of the random access message to be sent, and / or the reference signal reception quality of the terminal.

14. The method according to claim 14, characterized in that, The parameters in the configuration information associated with different random access message packets are configured independently; The parameter includes at least one of the following: Modulation and coding scheme (MCS); The number of frequency domain resource units occupied by one PUSCH transmission; The number of time-domain resource units occupied by one PUSCH transmission.

15. The method according to claim 12, characterized in that, The method further includes: Send a second message, which is used to indicate the index information of the configuration information; The index information is also used by the terminal to determine the Physical Downlink Shared Channel (PDSCH) corresponding to the configuration information.

16. The method according to any one of claims 9-15, characterized in that, The initial scrambling sequence of Msg3 is determined based on at least one of the following: The DMRS sequence corresponding to Msg3; The DMRS port corresponding to Msg3; The DMRS pattern corresponding to Msg3; The orthogonal overlay code (OCC) sequence of the terminal.

17. A terminal, characterized in that, The terminal includes: The transceiver module is used to receive first information, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH); The processing module is used to determine the PUSCH corresponding to one set of configuration information and send a random access message on the PUSCH. The random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

18. A network device, characterized in that, The network device includes: The transceiver module is used to send first information, the first information including at least one set of configuration information, the configuration information being used to configure the Physical Uplink Shared Channel (PUSCH); The transceiver module is also used to receive random access messages sent on the PUSCH, wherein the PUSCH is a PUSCH corresponding to one of the sets of configuration information determined by the terminal; The random access message is Msg3, and the terminal does not transmit Msg1 and Msg2 before sending Msg3.

19. A communication device, characterized in that, The terminal includes: One or more processors; The terminal is used to execute the uplink communication method according to any one of claims 1-8.

20. A communication device, characterized in that, The network device includes: One or more processors; The network device is used to perform the uplink communication method according to any one of claims 9-16.

21. A communication system, characterized in that, The device includes a terminal and a network device, wherein the terminal is configured to implement the uplink communication method according to any one of claims 1-8, and the network device is configured to implement the uplink communication method according to any one of claims 9-16.

22. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, it causes the communication device to perform the uplink communication method as described in any one of claims 1-8 or 9-16.

Images