Communication method and apparatus

Abstract

The application provides a communication method and device, which can improve the flexibility of resource configuration in the random access process. The method can be applied to a terminal, and the method comprises the following steps: acquiring configuration information; the configuration information is used for indicating a resource set, the resource set comprises a first resource set and / or a second resource set; the resources in the first resource set can be used for a terminal of a first capability type to send a preamble, and the resources in the second resource set can be used for a terminal of a second capability type to send a preamble; at least part of the resources of the first resource set and at least part of the resources of the second resource set are shared; selecting a target resource from the resource set and sending a preamble through the target resource; then, receiving a random access response; when the shared at least part of the resources comprises the target resource, sending first random access information; the first random access information can be used for indicating the capability type of the terminal, and the capability type of the terminal comprises the first capability type or the second capability type.

Description

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on April 1, 2021, with application number 202110365109.5 and invention name “A Random Access Method”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to communication methods and devices. Background Art

[0003] In some scenarios, a terminal needs to establish a communication connection with a base station (such as a gNB) to obtain communication services. In some solutions, a communication connection between the terminal and the base station can be established through random access (RA). For example, a terminal can use random access to establish a communication connection with the base station during initial power-up, connection loss, and cell handover.

[0004] See also Figure 1 , shows the steps for a terminal to perform random access: First, the terminal sends a random access sequence (random access preamble), also known as message 1 (message 1, msg1) to the base station, which is used to indicate that the terminal has an access request. After receiving the preamble from the terminal, the base station sends a random access response (random access response, RAR), also known as message 2 (message 2, msg2) to the terminal. In msg2, the base station instructs the terminal to send message 3 (message 3, msg3) to help the base station identify the identity of the terminal. After receiving msg2 from the base station, the terminal sends msg3 to the base station according to the scheduling instruction of msg2. Among them, msg3 carries information about the terminal, such as the identification (ID) information of the device, etc., and msg3 can also carry a radio resource control (RRC) connection establishment request (connection request). After receiving msg3 from the terminal, the base station can determine the identity of the access terminal according to the information carried in msg3, and send message 4 (message 4, msg4) to the terminal to complete the connection establishment and the random access process.

[0005] Compared to the aforementioned terminals (referred to as standard terminals), in some scenarios, certain terminals, such as wearable devices and smartwatches, may have lower communication capabilities due to factors such as power consumption and maintenance costs. These terminals with low communication capabilities are referred to as reduced-capability terminals. In scenarios where reduced-capability terminals coexist with standard terminals, terminals are required to report their respective capability types (reduced or standard) to facilitate optimal scheduling for different terminal types.

[0006] Terminal capability reporting and random access procedures are usually performed together, and existing technologies fail to flexibly optimize the configuration of random access resources during this process. Summary of the Invention

[0007] The embodiments of the present application provide a communication method and apparatus that can improve the flexibility of resource configuration during random access.

[0008] To achieve the above objectives, this application adopts the following technical solutions:

[0009] In a first aspect, a communication method is provided. The communication method can be executed by a terminal or a component capable of implementing terminal functions (such as a chip system of the terminal). Taking the terminal as an example, the method includes: the terminal obtains configuration information; the configuration information is used to indicate a resource set, and the resource set includes a first resource set and / or a second resource set; the resources in the first resource set can be used for a first capability type terminal to send a random access preamble code, and the resources in the second resource set can be used for a second capability type terminal to send a random access preamble code; at least part of the resources of the first resource set and at least part of the resources of the second resource set are shared. The capability type of the terminal includes the first capability type or the second capability type.

[0010] Afterwards, the terminal selects a target resource from the resource set and sends a preamble through the target resource. Next, the terminal receives a random access response.

[0011] In some cases, when at least some of the shared resources include target resources, this means that the target resources used by the terminal are included not only in the resource pool of the terminal's own capability type, but also in resource pools of non-capability types. In this case, the base station cannot confirm the terminal's capability type based on the target resources. In this case, the terminal can send a first random access message and indicate the terminal's capability type through the first random access message so that the network device can learn the terminal's capability type.

[0012] In the above communication method, on the one hand, the resources configured for the first capability type terminal and the resources configured for the second capability type terminal have at least partially shared resources, that is, the resources of the two terminals are not completely isolated. Through configuration, it is possible to achieve complete sharing of resources between the two terminals, partial sharing of resources between the two terminals, and the inclusion of resources of one terminal in another terminal. In this way, the flexibility of resource configuration can be increased. It can be seen that the communication method provided in the embodiment of the present application can provide a more flexible resource configuration method for the terminal. On the other hand, for some terminals, that is, terminals whose target resources are not included in the shared resources, the target resources used by the preamble can allow the network device to know the capability type of these terminals. In other words, the network device can identify the capability type of the terminal as early as possible, and therefore can schedule the terminal according to the capability type as early as possible to improve the communication performance of the terminal as early as possible. It can be seen that this solution can give the best possible balance between communication performance and resource configuration flexibility.

[0013] Furthermore, for some terminals (i.e., terminals whose target resources are not included in the shared resources), the network device can learn the capability types of these terminals through the target resources used by the preamble. For another portion of terminals (i.e., terminals whose target resources are included in the shared resources), the network device can learn the capability types of these terminals through the first random access information. In other words, the network device can learn the capability types of these terminals in different ways for different terminals. This provides a more flexible way for terminals to report their capability types to the network device.

[0014] In one possible design, when at least part of the shared resources do not include the target resource, second random access information is sent, and the second random access information is different from the first random access information.

[0015] If the target resource is not included in at least some of the shared resources, this means that the target resource used by the terminal is only included in the resource pool corresponding to its own capability type. In this case, the network device can determine the capability type of the terminal based on the target resource in the preamble code from the terminal. Optionally, in this case, the terminal can send a second random access message without carrying capability type information.

[0016] In one possible design, the first resource set includes a first random access opportunity RO set, the first RO set including at least one first RO; the second resource set includes a second RO set, the second RO set including at least one second RO; the first RO is an RO available for a terminal of a first capability type to send a preamble, and the second RO is an RO available for a terminal of a second capability type to send a preamble;

[0017] And / or, the first resource set includes a first preamble set, the first preamble set includes at least one first preamble, and the first preamble is a preamble available to terminals of a first capability type; the second resource set includes a second preamble set, the second preamble set includes at least one second preamble, and the second preamble is a preamble available to terminals of a second capability type;

[0018] At least part of the resources of the first resource set and at least part of the resources of the second resource set are shared, including: at least part of the ROs in the first RO set are shared with at least part of the ROs in the second RO set, and / or, at least part of the preamble codes in the first preamble code set are shared with at least part of the preamble codes in the second preamble code set.

[0019] It can be seen that this resource configuration method provides configuration flexibility. The network device can flexibly select PRACH resources to be completely separated, partially overlapped, or completely overlapped.

[0020] In one possible design, the target resource includes a target RO and a target preamble;

[0021] At least some of the shared resources include target resources, including: at least some of the ROs shared by the first RO set and the second RO include the target RO, and at least some of the preambles shared by the first preamble set and the second preamble set include the target preamble.

[0022] In one possible design, at least part of the shared resources do not include the target resources, including: at least part of the ROs shared by the first RO set and the second RO do not include the target RO, and / or at least part of the preambles shared by the first preamble set and the second preamble set do not include the target preamble.

[0023] In one possible design, the configuration information may also be used to indicate at least part of the ROs shared by the first RO set and the second RO set, or at least part of the preambles shared by the first preamble set and the second preamble set, or at least part of the ROs shared by the first RO set and the second RO and at least part of the preambles shared by the first preamble set and the second preamble set.

[0024] In one possible design, the first random access information includes information indicating the capability type of the terminal, which means that the first random access information may explicitly carry the capability type information of the terminal.

[0025] In one possible design, sending the first random access information includes: sending the first random access information on a first time-frequency resource; the first time-frequency resource is discontinuous in the time domain.

[0026] In one possible design, sending the first random access information includes: sending the first random access information on a second time-frequency resource; the second time-frequency resource is continuous in the time domain.

[0027] This means that the first random access information can implicitly carry the terminal capability type information, that is, different terminal capability types can be distinguished by using different time-frequency resources. In this way, the signaling overhead when reporting the capability type can be reduced.

[0028] In one possible design, the method further includes: retransmitting the first random access information.

[0029] If the network device does not receive the first random access information or fails to parse it successfully, the network device may schedule the first random access information for retransmission. Optionally, the base station may determine a scheduling strategy for retransmitting the first random access information based on the terminal's capability type. The scheduling strategy includes determining frequency hopping and frequency domain resources. For example, if the network device determines, through symbol energy detection, that the terminal is a reduced-capability terminal, when scheduling the retransmission of the first random access information, it may choose not to perform frequency hopping, or to perform frequency hopping within the bandwidth supported by the reduced-capability terminal.

[0030] In one possible design, the random access response includes information about a scheduling strategy; the scheduling strategy includes any one or a combination of the following strategies: frequency hopping, frequency domain resources, time domain resources, modulation and coding strategy, and transmission power control strategy.

[0031] In one possible design, sending the first random access information includes:

[0032] The first random access information is sent according to the scheduling policy indicated by the random access response.

[0033] In one possible design, when at least part of the shared resources include target resources, the scheduling strategy does not indicate any one or a combination of the following: frequency hopping, the frequency hopping range exceeds the terminal supported bandwidth, the frequency domain resources exceed the terminal supported bandwidth, the modulation and coding strategy exceeds the threshold, and the transmission power control exceeds the threshold.

[0034] Taking the network device as a base station, the first capability type terminal as an ordinary terminal, and the second capability type terminal as a reduced capability terminal as an example, the base station instructs the reduced capability terminal to use a reduced communication rate (a rate not exceeding the threshold) to send message 2 (carrying a random access response) to the reduced capability terminal. It can instruct the reduced capability terminal not to perform frequency hopping of message 3 (carrying random access information), or instruct to perform frequency hopping of message 3 within the supported bandwidth of the reduced capability terminal, indicate the frequency domain resources for message 3 within the supported bandwidth to the terminal, indicate the modulation and coding strategy of message 3 that does not exceed the threshold to the terminal, and indicate the transmission power control of message 3 that does not exceed the threshold to the terminal.

[0035] In a second aspect, the present application provides a communication method, which is applied to a network device or a component (such as a chip) that can realize the function of a network device, the method comprising: sending configuration information; the configuration information is used to indicate a resource set, the resource set including a first resource set and / or a second resource set; the resources in the first resource set can be used for terminals of a first capability type to send a preamble code, and the resources in the second resource set can be used for terminals of a second capability type to send a preamble code; at least part of the resources of the first resource set and at least part of the resources of the second resource set are shared; the preamble code is received through the target resource in the resource set; and a random access response is sent; when at least part of the shared resources include the target resource, the first random access information is received; the first random access information can be used to indicate the capability type of the terminal, and the capability type of the terminal includes the first capability type or the second capability type.

[0036] In one possible design, when at least part of the shared resources do not include the target resource, second random access information is received; the second random access information is different from the first random access information.

[0037] In one possible design, the first resource set includes a first random access opportunity RO set, the first RO set including at least one first RO; the second resource set includes a second RO set, the second RO set including at least one second RO; the first RO is an RO available for a terminal of a first capability type to send a preamble, and the second RO is an RO available for a terminal of a second capability type to send a preamble;

[0038] And / or, the first resource set includes a first preamble set, the first preamble set includes at least one first preamble, and the first preamble is a preamble available to terminals of a first capability type; the second resource set includes a second preamble set, the second preamble set includes at least one second preamble, and the second preamble is a preamble available to terminals of a second capability type;

[0039] At least part of the resources of the first resource set and at least part of the resources of the second resource set are shared, including: at least part of the ROs in the first RO set are shared with at least part of the ROs in the second RO set, and / or, at least part of the preamble codes in the first preamble code set are shared with at least part of the preamble codes in the second preamble code set.

[0040] In one possible design, the target resource includes a target RO and a target preamble;

[0041] At least some of the shared resources include target resources, including: at least some of the ROs shared by the first RO set and the second RO include the target RO, and at least some of the preambles shared by the first preamble set and the second preamble set include the target preamble.

[0042] In one possible design, at least part of the shared resources do not include the target resources, including: at least part of the ROs shared by the first RO set and the second RO do not include the target RO, and / or at least part of the preambles shared by the first preamble set and the second preamble set do not include the target preamble.

[0043] In one possible design, the configuration information may also be used to indicate at least part of the ROs shared by the first RO set and the second RO set, or at least part of the preambles shared by the first preamble set and the second preamble set, or at least part of the ROs shared by the first RO set and the second RO and at least part of the preambles shared by the first preamble set and the second preamble set.

[0044] In one possible design, the first random access information includes information indicating a capability type of the terminal.

[0045] In one possible design, receiving first random access information includes: receiving the first random access information on a first time-frequency resource; the first time-frequency resource is discontinuous in the time domain.

[0046] In one possible design, receiving the first random access information includes: receiving the first random access information on a second time-frequency resource; the second time-frequency resource is continuous in the time domain.

[0047] In one possible design, the method further includes receiving retransmitted first random access information.

[0048] In one possible design, the random access response includes information about a scheduling strategy; the scheduling strategy includes any one or a combination of the following strategies: frequency hopping, frequency domain resources, time domain resources, modulation and coding strategy, and transmission power control strategy.

[0049] In one possible design, receiving the first random access information includes: receiving the first random access information according to a scheduling strategy.

[0050] In one possible design, when at least part of the shared resources include target resources, the scheduling strategy does not indicate any one or a combination of the following: frequency hopping, the frequency hopping range exceeds the terminal supported bandwidth, the frequency domain resources exceed the terminal supported bandwidth, the modulation and coding strategy exceeds the threshold, and the transmission power control exceeds the threshold.

[0051] In a third aspect, the present application provides a communication device, which is applied to a terminal or a component (such as a chip) capable of implementing terminal functions, and the device includes:

[0052] a processing unit, configured to obtain configuration information; the configuration information is used to indicate a resource set, the resource set including a first resource set and / or a second resource set; resources in the first resource set can be used for a terminal of a first capability type to send a preamble, and resources in the second resource set can be used for a terminal of a second capability type to send a preamble; at least part of the resources of the first resource set and at least part of the resources of the second resource set are shared; and a target resource is selected from the resource set;

[0053] A transceiver unit, configured to send a preamble via a target resource; and receive a random access response;

[0054] The transceiver unit is further configured to send first random access information when at least part of the shared resources include the target resource; the first random access information can be used to indicate the capability type of the terminal, and the capability type of the terminal includes the first capability type or the second capability type.

[0055] In one possible design, when at least part of the shared resources do not include the target resources, second random access information is sent; the second random access information is different from the first random access information.

[0056] In one possible design, the first resource set includes a first random access opportunity RO set, the first RO set including at least one first RO; the second resource set includes a second RO set, the second RO set including at least one second RO; the first RO is an RO available for a terminal of a first capability type to send a preamble, and the second RO is an RO available for a terminal of a second capability type to send a preamble;

[0057] And / or, the first resource set includes a first preamble set, the first preamble set includes at least one first preamble, and the first preamble is a preamble available to terminals of a first capability type; the second resource set includes a second preamble set, the second preamble set includes at least one second preamble, and the second preamble is a preamble available to terminals of a second capability type;

[0058] At least part of the resources of the first resource set and at least part of the resources of the second resource set are shared, including: at least part of the ROs in the first RO set are shared with at least part of the ROs in the second RO set, and / or, at least part of the preamble codes in the first preamble code set are shared with at least part of the preamble codes in the second preamble code set.

[0059] In one possible design, the target resource includes a target RO and a target preamble;

[0060] At least part of the shared resources include target resources, including: at least part of the ROs shared by the first RO set and the second RO include the target RO, and at least part of the preambles shared by the first preamble set and the second preamble set include the target preamble

[0061] At least some of the shared resources do not include the target resource, including: at least some of the ROs shared by the first RO set and the second RO do not include the target RO, and / or at least some of the preambles shared by the first preamble set and the second preamble set do not include the target preamble.

[0062] In one possible design, the configuration information may also be used to indicate at least part of the ROs shared by the first RO set and the second RO set, or at least part of the preambles shared by the first preamble set and the second preamble set, or at least part of the ROs shared by the first RO set and the second RO and at least part of the preambles shared by the first preamble set and the second preamble set.

[0063] In one possible design, the first random access information includes information indicating a capability type of the terminal.

[0064] In one possible design, the transceiver unit is used to send the first random access information, including: sending the first random access information on the first time-frequency resource; the first time-frequency resource is discontinuous in the time domain.

[0065] In one possible design, the transceiver unit is used to send the first random access information, including: sending the first random access information on the second time-frequency resource; the second time-frequency resource is continuous in the time domain.

[0066] In one possible design, the transceiver unit is also used to retransmit the first random access information.

[0067] In one possible design, the random access response includes information about a scheduling strategy; the scheduling strategy includes any one or a combination of the following strategies: frequency hopping, frequency domain resources, time domain resources, modulation and coding strategy, and transmission power control strategy.

[0068] In one possible design, the transceiver unit, configured to send the first random access information, includes:

[0069] The first random access information is sent according to the scheduling policy indicated by the random access response.

[0070] In one possible design, when at least part of the shared resources include target resources, the scheduling strategy does not indicate any one or a combination of the following: frequency hopping, the frequency hopping range exceeds the terminal supported bandwidth, the frequency domain resources exceed the terminal supported bandwidth, the modulation and coding strategy exceeds the threshold, and the transmission power control exceeds the threshold.

[0071] In a fourth aspect, the present application provides a communication device that can be applied to a network device or a component (such as a chip) capable of implementing network device functions, the device comprising:

[0072] A transceiver unit, configured to send configuration information; the configuration information is used to indicate a resource set, the resource set including a first resource set and / or a second resource set; resources in the first resource set can be used for terminals of a first capability type to send preambles, and resources in the second resource set can be used for terminals of a second capability type to send preambles; at least part of the resources of the first resource set and at least part of the resources of the second resource set are shared;

[0073] The transceiver unit is further configured to receive a preamble code through a target resource in the resource set;

[0074] The transceiver unit is further configured to send a random access response;

[0075] The transceiver unit is further configured to receive first random access information when at least part of the shared resources include the target resource; the first random access information can be used to indicate a capability type of the terminal, and the capability type of the terminal includes a first capability type or a second capability type.

[0076] In one possible design, when at least part of the shared resources do not include the target resource, second random access information is received; the second random access information is different from the first random access information.

[0077] In one possible design, the first resource set includes a first random access opportunity RO set, the first RO set including at least one first RO; the second resource set includes a second RO set, the second RO set including at least one second RO; the first RO is an RO available for a terminal of a first capability type to send a preamble, and the second RO is an RO available for a terminal of a second capability type to send a preamble;

[0078] And / or, the first resource set includes a first preamble set, the first preamble set includes at least one first preamble, and the first preamble is a preamble available to terminals of a first capability type; the second resource set includes a second preamble set, the second preamble set includes at least one second preamble, and the second preamble is a preamble available to terminals of a second capability type;

[0079] At least part of the resources of the first resource set and at least part of the resources of the second resource set are shared, including: at least part of the ROs in the first RO set are shared with at least part of the ROs in the second RO set, and / or, at least part of the preamble codes in the first preamble code set are shared with at least part of the preamble codes in the second preamble code set.

[0080] In one possible design, the target resource includes a target RO and a target preamble;

[0081] At least some of the shared resources include target resources, including: at least some of the ROs shared by the first RO set and the second RO include the target RO, and at least some of the preambles shared by the first preamble set and the second preamble set include the target preamble.

[0082] At least some of the shared resources do not include the target resource, including: at least some of the ROs shared by the first RO set and the second RO do not include the target RO, and / or at least some of the preambles shared by the first preamble set and the second preamble set do not include the target preamble.

[0083] In one possible design, the configuration information may also be used to indicate at least part of the ROs shared by the first RO set and the second RO set, or at least part of the preambles shared by the first preamble set and the second preamble set, or at least part of the ROs shared by the first RO set and the second RO and at least part of the preambles shared by the first preamble set and the second preamble set.

[0084] In one possible design, the first random access information includes information indicating a capability type of the terminal.

[0085] In one possible design, the transceiver unit is used to receive first random access information, including: receiving the first random access information on a first time-frequency resource; the first time-frequency resource is discontinuous in the time domain.

[0086] In one possible design, the transceiver unit is used to receive the first random access information, including: receiving the first random access information on the second time-frequency resource; the second time-frequency resource is continuous in the time domain.

[0087] In one possible design, the transceiver unit is also used to receive the retransmitted first random access information.

[0088] In one possible design, the random access response includes information about a scheduling strategy; the scheduling strategy includes any one or a combination of the following strategies: frequency hopping, frequency domain resources, time domain resources, modulation and coding strategy, and transmission power control strategy.

[0089] In one possible design, a transceiver unit, configured to receive first random access information, includes:

[0090] First random access information is received according to the scheduling policy.

[0091] In one possible design, when the target resources include at least part of the shared resources, the scheduling strategy does not indicate any one or a combination of the following: frequency hopping, the frequency hopping range exceeds the terminal supported bandwidth, the frequency domain resources exceed the terminal supported bandwidth, the modulation and coding strategy exceeds the threshold, and the transmission power control exceeds the threshold.

[0092] In a fifth aspect, a communication device is provided. The communication device is used to implement the various communication methods described above. The communication device includes modules, units, or means corresponding to the communication methods described above. The modules, units, or means can be implemented through hardware, software, or hardware executing corresponding software implementations. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0093] In a sixth aspect, a communication device is provided. The communication device includes: a processor and a memory; the memory is configured to store computer instructions, and when the processor executes the instructions, the communication device executes the communication method of any one of the first and second aspects.

[0094] In a seventh aspect, a communication device is provided, comprising: a processor coupled to a memory, the processor configured to read and execute instructions in the memory, so that the communication device executes the communication method of any one of the first and second aspects.

[0095] In the eighth aspect, a chip system is provided, which includes a processor and an input / output port, the processor is used to implement the processing functions involved in the communication method of any one of the first and second aspects above, and the input / output port is used to implement the transceiver functions involved in the communication method of any one of the first and second aspects above.

[0096] In one possible design, the chip system also includes a memory, which is used to store program instructions and data for implementing the functions involved in the communication method of any one of the first and second aspects above.

[0097] The chip system may be composed of chips, or may include chips and other discrete devices.

[0098] In a ninth aspect, a communication system is provided, which includes one or more terminal devices and a network device.

[0099] In a tenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions, which, when executed on a computer, cause the computer to execute the communication method according to any one of the first and second aspects.

[0100] In an eleventh aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are executed on a computer, the computer executes the communication method according to any one of the first and second aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0101] Figure 1A schematic diagram of a random access process provided in an embodiment of the present application;

[0102] Figure 2 A schematic diagram of random access opportunities provided in an embodiment of the present application;

[0103] Figure 3 A schematic diagram of a random access preamble provided in an embodiment of the present application;

[0104] Figure 4 A schematic diagram of frequency hopping / non-frequency hopping provided in an embodiment of the present application;

[0105] Figure 5-1 A schematic diagram of the working mechanism of the reduced-capacity terminal provided in an embodiment of the present application;

[0106] Figure 5-2 A schematic diagram of the working mechanism of a common terminal provided in an embodiment of the present application;

[0107] Figure 6 A schematic diagram of random access opportunities and preamble resource allocation provided in an embodiment of the present application;

[0108] Figure 7 A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0109] Figure 8 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0110] Figure 9 A flow chart of a communication method provided in an embodiment of the present application;

[0111] Figure 10-14 A schematic diagram of random access opportunities and preamble resource allocation provided in an embodiment of the present application;

[0112] Figure 15-18 A schematic diagram of resource indication of a preamble provided in an embodiment of the present application;

[0113] Figure 19 A schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0114] To make the description of the following embodiments clear and concise, a brief introduction to the relevant technical terms involved in the embodiments of the present application is first given:

[0115] 1. Messages during random access

[0116] 1.1msg1

[0117] MSG1 can carry a preamble and is typically sent on a physical random access channel (PRACH). As a possible implementation, the base station specifies some resources for the PRACH. The time-frequency resources used to send the preamble are called random access opportunities (RACH occasions, ROs), also known as PRACH transmission opportunities. The names of the resources used to send the preamble are not limited in the embodiments of the present application.

[0118] like Figure 2 As shown, the resources shown in the white squares represent RO, that is, the time-frequency resources used to send preamble, and the black part can be used to send other data and control signaling, such as for sending other signaling during random access.

[0119] The resources used to send the preamble also include the preamble's code domain resources. The code domain resources, or preamble format, can be understood as a specific preamble sequence. Each preamble has its own ID. Preambles with different IDs often have different sequences and are orthogonal to each other. This allows the base station to identify different preambles if two terminals send different preambles within the same RO.

[0120] As a possible implementation, within an RO, the code domain resources available for sending the preamble or the preamble format may be specified by the protocol. Alternatively, the code domain resources available for the terminal to send the preamble may be configured by the base station.

[0121] For example, Figure 3 As shown in the figure, the base station can configure 64 preamble sequences. When the terminal performs random access, it randomly selects a preamble sequence (for example, preamble32) from the 64 preamble sequences configured by the base station. Figure 2 An RO is selected from RO1-RO8 (for example, RO3 is selected). Afterwards, the terminal may send preamble 32 on the selected RO (RO3).

[0122] When the base station configures the RO and preamble code domain resources to the terminal, as a possible implementation method, before the random access process, the terminal can monitor the broadcast message from the base station, for example, the system information block (SIB) and the master information block (MIB) from the base station, so as to obtain the available RO and preamble sequence.

[0123] Generally, since the random access process is randomly initiated by terminals within a cell, there is a possibility of conflicts between terminals. For example, at a certain moment, two different terminals need to perform random access. If both terminals select the same RO and the same preamble sequence, the preambles they send will conflict, and the base station will not be able to identify the access requests of both terminals. In this case, contention for access will usually occur, and it can be confirmed in the subsequent steps of random access which terminal successfully competed and which terminal failed. If the two terminals select different ROs (the preamble sequences are the same or different), or different preamble sequences (the ROs are the same or different), there will usually be no conflict. The base station can identify the access requests of the two terminals and will not cause contention for access.

[0124] 1.2msg2

[0125] After receiving the preamble sent by the terminal, the base station will send a random access response (carried in msg2) to the terminal to schedule the terminal to send msg3. Part of the information carried in msg2 is shown in Table 1.

[0126] Table 1

[0127]

[0128] The timing advance command (TAC) is transmission time adjustment information given to the terminal.

[0129] A temporary cell radio network temporary identifier (C-RNTI) is used to indicate a temporary ID to the UE for subsequent communication by the terminal.

[0130] The uplink (UL) grant is used to schedule the terminal to send msg3. Part of the indication information of the UL grant in the random access response is shown in Table 2 below.

[0131] Table 2

[0132]

[0133] The frequency hopping flag is used to indicate whether the msg3 sent by the terminal adopts frequency hopping.

[0134] PUSCH frequency domain resource allocation is used to indicate the frequency domain position and bandwidth used by MSG3, such as but not limited to subcarriers.

[0135] PUSCH time domain resource allocation is used to indicate the time domain position used by msg3, such as but not limited to time slot, symbol, etc.

[0136] The modulation and coding strategy is used to indicate the modulation and coding strategy used by msg3, including but not limited to the modulation and coding rate.

[0137] The TPC command of the PUSCH is used to indicate the transmission power adjustment used by msg3.

[0138] The CSI request is used to instruct the terminal to feedback CSI.

[0139] It should be noted that after the base station schedules the terminal to send msg3, if the base station does not receive msg3, or receives msg3 but fails to parse it, the base station will schedule the terminal to retransmit msg3. The base station schedules msg3 retransmission without using a random access response. Instead, it schedules the terminal to retransmit msg3 through downlink control signaling (DCI).

[0140] 1.3msg3

[0141] After sending msg1, the terminal will monitor the downlink channel within a certain period of time to detect whether there is a random access response for itself. After receiving the random access response sent to itself, the terminal sends msg3 according to the indication information in the random access response, such as shown in Table 2.

[0142] Exemplarily, the terminal determines whether to use frequency hopping when sending msg3 according to the "frequency hopping flag" field (or domain) shown in Table 2.

[0143] Frequency hopping refers to the use of different frequencies for transmitted signals, such as by varying the carrier frequency used to transmit the signal, or by using different frequencies in different time domains. Frequency hopping can achieve a certain degree of diversity gain.

[0144] For example Figure 4As shown in Table 2, msg3 occupies 14 orthogonal frequency division multiplexing (OFDM) symbols in time. If the value of the "frequency hopping flag" field in Table 2 is "0", it means that Figure 4 In the case of non-frequency hopping mode as shown in (2), all 14 OFDM symbols are sent at the same frequency domain position. If the value of the "frequency hopping flag" field shown in Table 2 is "1", it means that the OFDM signal is transmitted in the same frequency domain. Figure 4 In the frequency hopping mode shown in (1), the 14 OFDM symbols can be sent at different frequency domain positions, for example, the first 7 OFDM symbols and the last 7 OFDM symbols use different frequency domain positions.

[0145] For another example, the terminal determines the sending strategy of msg3 according to other indication information in the random access response, such as that shown in Table 2, such as the time-frequency position and MCS.

[0146] 2. Reduced Capability UE and its Random Access Process

[0147] To meet diverse application requirements, some wireless cellular communication system scenarios, due to factors such as cost and power consumption, do not require highly capable terminals. In other words, compared to the high communication capabilities of conventional terminals (also known as ordinary terminals or normal terminals), some terminals can be designed with lower communication capabilities. For example, wearable devices, children's smart watches, smart manhole covers, and smart water meters require much lower communication capabilities than high-end smartphones.

[0148] The low-capability device mentioned above may be referred to as a reduced capability user equipment (reduced capability UE) or a reduced capability terminal.

[0149] Considering power consumption, cost, and complexity, it's often possible to reduce the design specifications of a reduced-capability terminal, such as by lowering the supported communication bandwidth and the number of antennas. For example, in frequency bands below 6 GHz, a typical 5G phone requires 100 MHz bandwidth and four receiving antennas, while a reduced-capability terminal only requires 20 MHz bandwidth and one receiving antenna.

[0150] For random access, reduced-capability terminals face several challenges:

[0151] 1. Due to reduced communication capabilities, the communication reliability of a reduced-capability terminal is often worse than that of a standard terminal. For example, a standard terminal has four receiving antennas, while a reduced-capability terminal has only one. Therefore, the signal reception quality of the reduced-capability terminal will be correspondingly reduced.

[0152] 2. Due to the reduction in supported bandwidth, there are problems with the support of frequency hopping and other mechanisms by the reduced-capability terminal. For example, in some scenarios, the base station instructs the reduced-capability terminal to send msg3 using frequency hopping in the random access response, and the frequency hopping range exceeds the supported bandwidth range of the reduced-capability terminal. In this case, the reduced-capability terminal first sends part of the OFDM symbols, and before sending the remaining OFDM symbols, it specifies that the operating frequency must be adjusted to the specified frequency domain bandwidth position, and then the remaining OFDM symbols are sent from the specified frequency domain bandwidth position. Among them, the adjustment of the operating frequency often takes a certain amount of time, and OFDM symbols cannot be transmitted during this time. For this reason, a certain conversion time needs to be specified, and no signal is sent within the conversion time.

[0153] For example, Figure 5-1 As shown in the figure, assume that the supported bandwidth of a reduced-capability terminal is 20 MHz, while the supported bandwidth of a standard terminal is 100 MHz. After sending seven symbols, the terminal cannot transmit data during the time required to adjust the operating frequency. For example, due to the operating frequency adjustment, the 8th and 9th OFDM symbols cannot be transmitted (or the 8th and 9th symbols cannot carry signals). After the operating frequency is adjusted to the specified frequency domain location, the terminal can send symbols 10-14 at the specified frequency domain location. As can be seen, the need for operating frequency adjustment may delay signal transmission, resulting in transmission gaps (gaps), which may cause some signals to be unable to be transmitted.

[0154] For ordinary terminals, since they support a wide range of bandwidth, such as Figure 5-2 As shown, gaps are usually not formed.

[0155] As analyzed above, reduced-capability terminals often face challenges due to their lower communication performance. Taking into account the different characteristics of reduced-capability terminals and standard terminals, in some solutions, the base station can identify the terminal type during random access. Then, in subsequent steps of random access, the base station can treat different types of terminals differently. For example, if the base station knows that its communication partner is a reduced-capability terminal, it can improve communication reliability by reducing the information transmission rate. For another example, if the base station knows that its communication partner is a reduced-capability terminal, it can instruct the reduced-capability terminal not to perform frequency hopping, thus avoiding the operating frequency adjustment issues faced by the reduced-capability terminal during frequency hopping.

[0156] 3. Solution 1 for identifying terminal type during random access

[0157] In solution 1, the base station can identify the terminal type based on the msg1 received from the terminal. Specifically, separate PRACH resources are configured for standard terminals and reduced-capability terminals. In this way, standard terminals and reduced-capability terminals use different resources to send preambles, and the base station can distinguish the terminal type by receiving the preamble resources.

[0158] For example Figure 6 As shown, the base station can notify the terminal through system information (SIB and / or MIB) that ROs 1-4 are allocated to standard terminals for sending preambles, and ROs 5-8 are allocated to reduced-capability terminals. In this way, when initiating random access, the reduced-capability terminal will select an RO from ROs 5-8 to send the preamble. Accordingly, when the base station receives the preamble, if it receives the preamble through any RO from ROs 5-8, it can determine that the terminal currently initiating random access is a reduced-capability terminal.

[0159] For example Figure 6 As shown, the base station can notify the terminal through a system message that preambles 1-32 are available to standard terminals, and preambles 33-64 are available to reduced-capability terminals. Therefore, when initiating random access, the reduced-capability terminal randomly selects a preamble from preambles 33-64 and sends it. The base station can determine the terminal type based on the sequence range of the received preamble.

[0160] After the base station identifies the terminal type, it can treat different types of terminals differently in subsequent random access steps. For example, if the communication target is determined to be a reduced-capability terminal, the base station can avoid frequency hopping when scheduling MSG3 to avoid the problem of insufficient bandwidth supported by the terminal.

[0161] The problem with solution 1 is that it divides PRACH resources into completely separate parts, and the resource allocation method is not flexible enough.

[0162] Furthermore, because the resources for reduced-capability terminals are completely isolated from those for standard terminals, the resources available to these terminals are limited. When the ratio of terminals of different capability types in the actual network does not match the resource allocation ratio, the probability of preamble transmission collisions increases. For example, if the base station divides PRACH resources into two parts with a 1:1 ratio, and at certain times, the ratio of standard terminals to reduced-capability terminals in the actual preamble transmission is 4:1, then standard terminals will experience a higher probability of collisions.

[0163] 4. Solution 2 for identifying terminal type during random access

[0164] In solution 2, the base station identifies the terminal type based on the msg3 message sent by the terminal. Specifically, msg3 carries terminal category information, including standard or reduced-capability terminals. This allows the base station to determine the terminal type upon receiving msg3 and treat it differently during subsequent random access processing.

[0165] Although Solution 2 avoids the problem of inflexible resource allocation in Solution 1, since the terminal type cannot be identified early, the base station cannot perform differentiated processing on the two types of terminals in the scheduling of msg2 and msg3.

[0166] If the base station schedules MSG2 and MSG3 for different types of terminals in the same manner as for standard terminals, the reduced-capability terminals will face some problems. For example, if the base station sends MSG2 at a higher information transmission rate, the reduced-capability terminal will fail to receive it due to its limited reception capability. Alternatively, the base station can instruct the terminal to send MSG3 using frequency hopping. In this case, the reduced-capability terminal can only achieve this by adjusting its operating frequency. However, since this adjustment takes time, some data cannot be sent during this time.

[0167] Conversely, if the base station schedules all terminals according to the scheduling method for reduced-capability terminals, the overall network efficiency will be affected. For example, if a lower transmission rate is used for all terminals and frequency hopping is not performed, while the reduced-capability terminals can access normally, the lower transmission rate means reduced efficiency for ordinary terminals, and without frequency hopping, the gain of frequency diversity cannot be achieved.

[0168] It can be seen that in the current solutions 1 and 2, when reduced-capability terminals and ordinary terminals coexist, it is impossible to take into account both communication performance and resource allocation flexibility.

[0169] In order to solve the above technical problems, the embodiment of the present application provides a communication method. The method can be applied to various wireless cellular communication systems, such as the third generation (3 rd generation, 3G) mobile communication system, the fourth generation (4 th generation, 4G) mobile communication system, the fifth generation (5 th Generation (5G) mobile communication systems or future mobile communication systems. For example, new radio (NR) systems applied to 5G.

[0170] Figure 7 A schematic diagram of a communication system to which the technical solution provided in the embodiment of the present application is applicable is provided. The communication system may include a network device 100 and one or more terminal devices 200 ( Figure 2 Only one is shown). Data can be transmitted between the network device and the terminal device.

[0171] The network device 100 may be a device that can communicate with the terminal device 200. For example, the network device 100 may be a base station, which may be an evolved NodeB (eNB or eNodeB) in LTE, or a base station in NR, or a relay station or access point, or a base station in a future network, etc., which is not limited in the embodiment of the present application. Among them, the base station in NR can also be called a transmission reception point (TRP) or gNB. In the embodiment of the present application, the network device may be an independently sold network device, such as a base station, or a chip that implements the corresponding function in the network device. In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices. In the technical solution provided in the embodiment of the present application, the technical solution provided in the embodiment of the present application is described by taking the device for implementing the function of the network device as an example, which is a network device.

[0172] Among them, the terminal device 200 in the embodiment of the present application can also be called a terminal, which can be a device with wireless transceiver function. The terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (for example, on an airplane, a balloon, and a satellite, etc.). The terminal device can be a user equipment (UE). Among them, the UE includes a handheld device, a vehicle-mounted device, a wearable device, or a computing device with wireless communication function. Exemplarily, the UE can be a mobile phone, a tablet computer, or a computer with wireless transceiver function. The terminal device can also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. In the embodiment of the present application, the terminal device can be a terminal sold independently or a chip in a terminal. In the technical solutions provided in the embodiments of the present application, the technical solutions provided in the embodiments of the present application are described by taking the apparatus for realizing the functions of the terminal as an example, that is, a terminal device.

[0173] Embodiments of the present application Figure 7The network device 100 or terminal device 200 in the embodiment can be implemented by a device or a functional module in a device, and the embodiment of the present application does not specifically limit this. It is understandable that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, virtualization functions instantiated on a platform (for example, a cloud platform), or chip systems. In the embodiment of the present application, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0174] For example, a device for implementing the functions of a terminal device provided in an embodiment of the present application or a device for implementing the functions of a network device may be implemented by Figure 8 It is implemented by the device 300 in FIG. Figure 3 FIG2 is a schematic diagram of the hardware structure of an apparatus 300 provided in an embodiment of the present application. The apparatus 300 includes at least one processor 301 for implementing the functions of a terminal device or network device provided in an embodiment of the present application. The apparatus 300 may also include a bus 302 and at least one communication interface 304. The apparatus 300 may also include a memory 303.

[0175] In the embodiments of the present application, the processor may be a central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor may also be any other device having processing functionality, such as a circuit, a device, or a software module.

[0176] The bus 302 may be used to transmit information between the aforementioned components.

[0177] The communication interface 304 is used to communicate with other devices or communication networks, such as Ethernet, radio access networks (RAN), wireless local area networks (WLAN), etc. The communication interface 304 can be an interface, circuit, transceiver, or other device capable of communication, and this application does not limit this. The communication interface 304 can be coupled to the processor 301. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules.

[0178] In the embodiment of the present application, the memory may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently or be coupled to the processor, for example, via bus 302. The memory may also be integrated with the processor.

[0179] The memory 303 is used to store program instructions and can be controlled by the processor 301 to execute, thereby implementing the communication method provided in the following embodiments of the present application. The processor 301 is used to call and execute the instructions stored in the memory 303, thereby implementing the communication method provided in the following embodiments of the present application.

[0180] Optionally, the computer instructions in the embodiments of the present application may also be referred to as program codes, which is not specifically limited in the embodiments of the present application.

[0181] Optionally, the memory 303 may be included in the processor 301 .

[0182] In a specific implementation, as an embodiment, the processor 301 may include one or more CPUs, such as Figure 3 CPU0 and CPU1 in.

[0183] In a specific implementation, as an embodiment, the apparatus 300 may include multiple processors, such as Figure 3 301 and processor 307 in FIG. Each of these processors may be a single-CPU processor or a multi-CPU processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0184] In a specific implementation, as an embodiment, the apparatus 300 may further include an output device 305 and an input device 306. The output device 305 is coupled to the processor 301 and can display information in a variety of ways. For example, the output device 305 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 306 is coupled to the processor 301 and can receive user input in a variety of ways. For example, the input device 306 can be a mouse, a keyboard, a touch screen device, or a sensor device.

[0185] The above-mentioned device 300 can be a general device or a special device. Figure 3 The embodiment of the present application does not limit the type of the device 300.

[0186] This application will present various aspects, embodiments, or features in the context of systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these aspects may also be used.

[0187] Additionally, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as an "exemplary" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0188] In the embodiments of the present application, the terms "information," "signal," "message," "channel," and "signaling" may sometimes be used interchangeably. It should be noted that, when the distinction between them is not emphasized, the meanings they intend to convey are the same. The terms "of," "corresponding," and "corresponding" may sometimes be used interchangeably. It should be noted that, when the distinction between them is not emphasized, the meanings they intend to convey are the same.

[0189] In the embodiments of the present application, sometimes a subscript such as W1 may be mistakenly written as a non-subscript form such as W1. When the difference is not emphasized, the meanings to be expressed are the same.

[0190] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0191] Some of the scenarios in the embodiments of this application are Figure 1 It should be noted that the solutions in the embodiments of the present application can also be applied to other mobile communication systems, and the corresponding names can also be replaced by the names of corresponding functions in other mobile communication systems.

[0192] For ease of understanding, the communication method provided in the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0193] like Figure 9 As shown, an embodiment of the present application provides a communication method, including:

[0194] S101. The terminal obtains configuration information.

[0195] Among them, the configuration information is used to indicate a resource set. The resource set is a PRACH resource set. The resource set includes a first resource set and / or a second resource set; the resources in the first resource set can be used for a first capability type terminal to send a random access preamble (preamble, which may be referred to as a preamble in this article), and the resources in the second resource set can be used for a second capability type terminal to send a random access preamble; at least part of the resources of the first resource set and at least part of the resources of the second resource set are shared. The first capability type terminal may be the above-mentioned ordinary terminal, and the second capability type terminal may be the above-mentioned reduced capability terminal. The resources in the resource set include time-frequency domain resources and / or code domain resources. The time-frequency domain resources include RO, and the code domain resources include preamble sequences.

[0196] As a possible implementation, the terminal obtains configuration information from a network device. The network device includes but is not limited to a base station. Taking the network device as a base station as an example, the base station carries the above configuration information through a broadcast message (MIB and / or SIB). The terminal monitors the broadcast message to obtain the configuration information. Optionally, the configuration information can be represented by a bitmap in the following embodiments, or by a start point field, length field, etc. in the following embodiments. The embodiments of the present application do not limit the specific implementation of the configuration information. The bitmap, start point, length field, etc. will be described in detail in the following embodiments.

[0197] As another possible implementation, part of the information in the protocol predefined configuration information may be used, for example, a preamble sequence in the protocol predefined configuration information.

[0198] Alternatively, the terminal may have other ways to obtain configuration information, which is not limited in the embodiments of the present application.

[0199] The configuration information may be used to indicate a PRACH resource set, where the PRACH resource set includes PRACH resources for common terminals and PRACH resources for reduced-capability terminals.

[0200] It is worth noting that the PRACH resources for reduced-capability terminals and standard terminals are configured separately, that is, the configuration is performed independently. The PRACH resources of standard terminals and reduced-capability terminals can be completely separate (no overlap or shared resources), partially overlap (also known as partial sharing), completely overlap (complete sharing), or the PRACH resources of one capability type terminal include the PRACH resources of the other capability type terminal. As can be seen, this resource configuration method provides configuration flexibility, and network devices can flexibly choose to completely separate PRACH resources, partially overlap, or completely overlap, etc.

[0201] Optionally, the configuration information may also be used to indicate PRACH resources shared by common terminals and reduced-capability terminals.

[0202] It should be noted that, in the embodiment of the present application, the phrase "xx message is used to indicate yy" means that xx message can indicate yy, not that xx message is specifically used to indicate yy. This is explained here uniformly and will not be repeated below.

[0203] The following describes in detail the first resource set available for common terminals and the second resource set available for reduced-capability terminals.

[0204] The first resource set includes a first RO set, which includes at least one first RO; the second resource set includes a second RO set, which includes at least one second RO; the first RO is an RO available for a first capability type terminal to send a random access preamble code, and the second RO is an RO available for a second capability type terminal to send a random access preamble code; the first RO set and the second RO set are configured separately.

[0205] And / or, the first resource set includes a first preamble code set, the first preamble code set includes at least one first preamble code, and the first preamble code is a random access preamble code available to terminals of the first capability type; the second resource set includes a second preamble code set, the second preamble code set includes at least one second preamble code, and the second preamble code is a random access preamble code available to terminals of the second capability type; the first preamble code set and the second preamble code set are configured separately.

[0206] At least part of the resources of the first resource set and at least part of the resources of the second resource set are shared, including: at least part of the ROs in the first RO set are shared with at least part of the ROs in the second RO set, and / or, at least part of the preamble codes in the first preamble code set are shared with at least part of the preamble codes in the second preamble code set.

[0207] That is, there are at least the following configuration methods for PRACH resource sets:

[0208] 1. The first resource set includes a first RO set, and the second resource set includes a second RO set, wherein at least some ROs in the first RO set are shared with at least some ROs in the second RO set.

[0209] For example, taking the network device as a base station, for the time-frequency domain resource RO in the PRACH resource, the base station can indicate the configuration information to the terminal through a system message. Optionally, the configuration information can also indicate the ROs belonging to the shared part (i.e., RO1-RO4), and / or indicate the ROs that do not belong to the shared part. For example, Figure 10 As shown in (1), the base station can indicate the time-frequency domain positions of RO1-RO8 configured for normal terminals. RO1-RO8 consists of two parts, where RO1-RO4 are ROs that are only allowed to be used by normal terminals, and RO5-RO8 are ROs that are shared by normal terminals and reduced-capability terminals, that is, ROs that can be used by both normal terminals and reduced-capability terminals.

[0210] Optionally, the network device may determine configuration information based on network conditions. As a possible design, the network device may determine configuration information based on the actual proportion of online terminals, resource shortage, and the like.

[0211] For example, at certain moments, among the terminals that actually send preambles, the ratio of normal terminals to reduced-capability terminals is 4:1. Then, considering that the probability of collisions with normal terminals is higher, more PRACH resources can be allocated to normal terminals.

[0212] Similarly, the base station can indicate the time-frequency domain locations of RO5-RO12 configured for the reduced-capability terminal in the configuration information for the reduced-capability terminal in the system message. The ROs available to the reduced-capability terminal include two parts: RO9-RO12 are ROs that are only allowed to be used by reduced-capability terminals, and RO5-RO8 are ROs shared by standard terminals and reduced-capability terminals. Optionally, the configuration information may also indicate ROs that are not shared (i.e., RO9-RO12) and / or ROs that are shared (i.e., RO5-RO8).

[0213] For the code domain resources in the PRACH resources, common terminals and reduced-capability terminals share the same preamble sequence. In this way, the base station cannot distinguish different types of terminals based only on the received preamble. Figure 10 As shown in (2), the common terminal and the reduced-capability terminal share preamble 1-64, that is, the common terminal can use any preamble in preamble 1-64, and the reduced-capability terminal can also use any preamble in preamble 1-64. Optionally, preamble 1-64 can be configured for the terminal by a network device (such as a base station) or predefined by a protocol. The embodiment of the present application does not limit the specific implementation method of the terminal obtaining the preamble code domain resources.

[0214] In general, for a common terminal, the first resource set that can be used for the common terminal to send a random access preamble includes Figure 10 RO1-RO8 shown in (1) (i.e., the first RO set includes 8 first ROs), and Figure 10 The code domain resources preamble 1-64 (first preamble set) shared with the reduced capability terminal shown in (2) are as follows. For the reduced capability terminal, the second resource set that can be used for the reduced capability terminal to send a random access preamble includes Figure 10 RO5-RO12 (the second RO set) shown in (1), and Figure 10 Preamble 1-64 (second preamble code set) shared with common terminals as shown in (2).

[0215] It can be seen that the first preamble set (preamble1-64) is the same as the second preamble set (preamble1-64). At least some ROs in the first RO set (RO1-RO8) are shared with at least some ROs in the second RO set (RO5-RO12), and there is at least one different RO in the first RO set and the second RO set. Specifically, Figure 10 As shown, at least part of the resources shared by the normal terminal and the reduced-capability terminal include: at least part of the ROs (i.e., RO5-RO8) shared by RO1-RO8 (i.e., the first RO set) and RO5-RO12 (the second RO set), and preamble1-64 shared by the first preamble set (preamble1-64) and the second preamble set (preamble1-64).

[0216] 2. The first resource set includes a first preamble set, and the second resource set includes a second preamble set, wherein at least some preambles in the first preamble set are shared with at least some preambles in the second preamble set.

[0217] For the code domain resource preamble in the PRACH resource, for example, taking the network device as a base station, see Figure 11 As shown in (2), the base station indicates the preambles 1-48 that can be used by normal terminals in the configuration information for normal terminals in the system message. Preambles 1-48 consist of two parts, where preambles 1-16 are preamble sequences that are only allowed to be used by normal terminals, and preambles 17-48 are preamble sequences shared by normal terminals and reduced-capability terminals. Both normal terminals and reduced-capability terminals can use any preamble sequence in preambles 17-48.

[0218] Optionally, the configuration information may further indicate preamble sequences that are not part of the shared part (ie, preambles 1-16), and / or indicate shared preamble sequences (ie, preambles 17-48).

[0219] Similarly, the base station indicates preambles 17-64 that can be used by reduced-capability terminals in the configuration information for reduced-capability terminals in the system message. Preambles 17-64 consist of two parts, where preambles 49-64 are preamble sequences that are only allowed to be used by reduced-capability terminals, and preambles 17-48 are preamble sequences shared by normal terminals and reduced-capability terminals. Optionally, the configuration information may also indicate preamble sequences that are not part of the shared part (i.e., preambles 49-64) and / or indicate shared preamble sequences (i.e., preambles 17-48).

[0220] For the time-frequency domain resource RO in the PRACH resource, the normal terminal and the reduced-capability terminal share the RO. Figure 11 As shown in (1), the normal terminal and the reduced-capacity terminal share RO1-RO8.

[0221] In general, for a common terminal, the first resource set that can be used for the common terminal to send a random access preamble includes Figure 11 The time-frequency domain resources RO1-RO8 (first RO set) shared with the reduced-capability terminal shown in (1), and Figure 11 The code domain resources preamble 1-48 (first preamble set) shown in (2) are as follows. For a reduced capability terminal, a second resource set that can be used to send a random access preamble by the reduced capability terminal includes: Figure 11 RO1-RO8 (second RO set) shared with common terminals as shown in (1), and Figure 11 The code domain resources shown in (2) are preamble 17-64 (the second preamble code set).

[0222] Correspondingly, such as Figure 11 As shown, at least part of the resources shared by the normal terminal and the reduced-capability terminal include: at least part of the preamble code (i.e., preamble 17-48) shared by the first preamble code set (preamble 1-48) and the second preamble code set (preamble 17-64), and RO1-RO8 shared by the first RO set (RO1-RO8) and the second RO set (RO1-RO8).

[0223] 3. The first resource set includes a first RO set and a first preamble set, and the second resource set includes a second RO set and a second preamble set. At least some of the ROs in the first RO set are shared with at least some of the ROs in the second RO set, and / or at least some of the preambles in the first preamble set are shared with at least some of the preambles in the second preamble set.

[0224] In some embodiments, the normal terminal and the reduced-capability terminal only share part of the RO. In other words, the RO that the normal terminal can use and the RO that the reduced-capability terminal can use no longer completely overlap. Figure 11 The usable RO sets for normal terminals and reduced-capability terminals are different.

[0225] For the code domain resource preamble in the PRACH resource, such as Figure 12 As shown in (2), normal terminals can use preambles 1-48. Preambles 1-48 consist of two parts: preambles 1-16 are preamble sequences that are only allowed to be used by normal terminals, and preambles 17-48 are preamble sequences that are shared by normal terminals and reduced-capability terminals. Reduced-capability terminals can use preambles 17-64. Preambles 17-64 consist of two parts: preambles 49-64 are preamble sequences that are only allowed to be used by reduced-capability terminals, and preambles 17-48 are preamble sequences that are shared by normal terminals and reduced-capability terminals.

[0226] For the time-frequency domain resource RO in the PRACH resource, such as Figure 12 As shown in (1), ordinary terminals can use RO1-RO8. RO1-RO8 consists of two parts, of which RO1-RO4 are ROs that are only allowed to be used by ordinary terminals, and RO5-RO8 are ROs shared by ordinary terminals and reduced-capacity terminals. Reduced-capacity terminals can use RO5-RO12. RO5-RO12 consists of two parts, of which RO9-RO12 are ROs that are only allowed to be used by reduced-capacity terminals, and RO5-RO8 are ROs shared by ordinary terminals and reduced-capacity terminals.

[0227] The configuration information may indicate the preambles that can be used by the common terminal and / or the preambles that can be used by the reduced-capability terminal. The configuration information may also indicate the RO and / or preambles that are shared by the common terminal and the reduced-capability terminal.

[0228] In general, Figure 12 As shown, for a common terminal, the first resource set that can be used for the common terminal to send a random access preamble includes Figure 12 The time-frequency domain resources RO1-RO8 (i.e., the first RO set) shown in (1), and Figure 12 The code domain resources preamble 1-48 (first preamble set) shown in (2) are as follows. For a reduced capability terminal, a second resource set that can be used to send a random access preamble by the reduced capability terminal includes: Figure 12 RO5-RO12 (i.e., the second RO set) shown in (1), and Figure 12 The code domain resources shown in (2) are preamble 17-64 (the second preamble code set).

[0229] Correspondingly, such as Figure 12 As shown, at least some of the resources shared by the normal terminal and the reduced-capability terminal include: at least some of the preambles (i.e., preambles 17-48) shared by the first preamble set (preambles 1-48) and the second preamble set (preambles 17-64), and some of the ROs (RO5-RO8) shared by the first RO set (RO1-RO8) and the second RO set (RO5-RO12). It should be noted that the above-mentioned RO resources are divided from the perspective of the time-frequency domain, and the above-mentioned preamble resources are divided from the perspective of the code domain.

[0230] In other embodiments, the preamble sequence that can be used by the normal terminal does not overlap with the preamble sequence that can be used by the reduced-capability terminal. Figure 12 The preamble sequences shared by common terminals and reduced-capability terminals are different.

[0231] For example, for the code domain resource preamble in the PRACH resource, such as Figure 13 As shown in (2), common terminals can use preambles 1 to 32, while reduced-capability terminals can use preambles 33 to 64. Therefore, common terminals and reduced-capability terminals do not share a common preamble sequence.

[0232] For the time-frequency domain resource RO in the PRACH resource, such as Figure 13 As shown in (1), ordinary terminals and reduced-capacity terminals share RO5-RO8. For detailed RO allocation description, please refer to Figure 10 (1) or Figure 12 Related description of (1).

[0233] In general, Figure 13 As shown, for a common terminal, the first resource set that can be used for the common terminal to send a random access preamble includes Figure 13 The time-frequency domain resources RO1-RO8 (first RO set) shown in (1), and Figure 13 The code domain resources preamble 1-32 shown in (2) are as follows. For the reduced capability terminal, the second resource set that can be used for the reduced capability terminal to send the random access preamble includes: Figure 13 RO5-RO12 (the second RO set) shown in (1), and Figure 13 The code domain resources preamble 33-64 are shown in (2).

[0234] Correspondingly, such as Figure 13 As shown, at least part of the resources shared by the common terminal and the reduced-capability terminal specifically refer to part of the ROs (RO5-RO8) shared by the first RO set (RO1-RO8) and the second RO set (RO5-RO12).

[0235] In other embodiments, there is no overlap between the ROs available to normal terminals and the ROs available to reduced-capability terminals. Figure 12 The shared ROs of ordinary terminals and reduced-capability terminals are different.

[0236] For example, for the code domain resource preamble in the PRACH resource, such as Figure 14 As shown in (2), the common terminal and the reduced-capability terminal can share part of the code domain resources preamble 17-48. The specific code domain resource configuration of the common terminal and the reduced-capability terminal can be found in Figure 12 The relevant description of (2) in the above text.

[0237] For the time-frequency domain resource RO in the PRACH resource, such as Figure 14 As shown in (1), there is no shared RO between the normal terminal and the reduced-capability terminal.

[0238] In general, if Figure 14 As shown, for a common terminal, the first resource set that can be used for the common terminal to send a random access preamble includes Figure 14 The time-frequency domain resources RO1-RO4 shown in (1) (no shared RO with the reduced-capability terminal), and Figure 14 The code domain resources preamble 1-48 (first preamble set) shown in (2) are as follows. For a reduced capability terminal, a second resource set that can be used to send a random access preamble by the reduced capability terminal includes: Figure 14RO5-RO8 shown in (1), and Figure 14 The code domain resources shown in (2) are preamble 17-64 (the second preamble code set).

[0239] Correspondingly, such as Figure 14 As shown, at least part of the resources shared by the normal terminal and the reduced-capability terminal refer to: at least part of the preambles (ie, preambles 17-48) shared by the first preamble set (preambles 1-48) and the second preamble set (preambles 17-64).

[0240] Optionally, the first resource set and the second resource set in the embodiment of the present application have at least some non-shared parts. In other words, the first resource set and the second resource set are not completely identical.

[0241] The resources shared by the normal terminal and the reduced-capability terminal may be referred to as shared resources. The shared resources include shared RO and / or shared preamble sequence.

[0242] S102: The terminal selects a target resource from the resource set, and sends a preamble to the network device through the target resource.

[0243] Accordingly, the network device receives a preamble from the terminal.

[0244] The target resource includes a target RO and a target preamble. The terminal selects the target RO and the target preamble from the resource set and sends the target preamble on the target RO.

[0245] As a possible implementation manner, the terminal selects time-frequency domain resources and / or code domain resources for sending the preamble code according to its own capability type.

[0246] For example, taking the network device as a base station, the base station configures a resource set for the terminal through a broadcast message such as Figure 10 As shown, the terminal obtains the configuration information corresponding to its capability type by listening to and reading the corresponding fields in the broadcast message. The terminal then selects a preamble sequence from preambles 1-64 based on the configuration information (for example, preamble 8 (target preamble)). If the terminal is a reduced-capability terminal, it selects an RO from RO1-RO8 to send the preamble. If the terminal is a standard terminal, it selects an RO (target RO) from RO5-RO12 to send the preamble. After completing resource selection, the terminal can send the selected preamble 8 to the network device on the selected RO.

[0247] For example, a resource collection such as Figure 11As shown, the terminal selects an RO from RO1-RO8 for sending the preamble. Furthermore, if the terminal is a reduced-capability terminal, the terminal selects a preamble sequence from preambles 17-64 (e.g., preamble 33). The terminal can then send preamble 33 to the network device on the selected RO.

[0248] As a possible implementation manner, the terminal sends a message 1 to the network device, where the message 1 carries a preamble code.

[0249] S103: The network device sends a random access response to the terminal.

[0250] Correspondingly, the terminal receives a random access response from the network device.

[0251] As a possible implementation manner, the network device sends a message 2 to the terminal, where the message 2 carries a random access response.

[0252] Optionally, the random access response includes information about a scheduling strategy; the scheduling strategy includes any one or a combination of the following strategies: frequency hopping, frequency domain resources, time domain resources, modulation and coding strategy, and transmission power control strategy. Exemplarily, the random access response includes information about the scheduling strategy shown in Table 2.

[0253] In some cases, after receiving a preamble from a terminal, the network device can determine whether the terminal is a standard terminal or a reduced-capability terminal based on the target resource used by the terminal to send the preamble. As a possible design, if the target resource used by the terminal to send the preamble is not among the shared resources, the base station can determine the terminal type based on the target resource used by the terminal to send the preamble.

[0254] Optionally, the target resource used by the terminal to send the preamble is not in the shared resource, which may be that the RO used by the terminal to send the preamble is not in the shared RO, and / or the preamble sequence used by the terminal to send the preamble is not in the shared preamble sequence. Specifically, it may be that the preamble sequence used by the terminal to send the preamble is not in the shared preamble sequence, and the RO used by the terminal to send the preamble is in the shared RO. Alternatively, it may be that the RO used by the terminal to send the preamble is not in the shared RO, and the preamble sequence used by the terminal to send the preamble is in the shared preamble sequence. Or, the preamble sequence used by the terminal to send the preamble is not in the shared preamble sequence, and the RO used by the terminal to send the preamble is not in the shared RO. In short, the preamble sequence used by the terminal to send the preamble is not in the shared preamble sequence, or the RO used by the terminal to send the preamble is not in the shared RO.

[0255] For example, taking the network device as a base station, assuming the configured resource set is as follows Figure 10 As shown, if the base station receives the preamble code from the terminal through RO3 (not belonging to the shared RO5-RO8), the base station can determine that the terminal initiating random access is a normal terminal. If the base station receives the preamble code from the terminal through RO10 (not belonging to the shared RO5-RO8), the base station can confirm that the terminal initiating random access is a reduced-capability terminal.

[0256] For example, suppose the configured resource set is Figure 11 As shown, if the preamble code received by the base station from the terminal is preamble15 (not belonging to the shared preamble17-48), the base station can determine that the terminal initiating random access is a normal terminal. If the preamble code received by the base station is preamble55 (not belonging to preamble17-48), the base station can confirm that the terminal initiating random access is a reduced capability terminal.

[0257] For example, suppose the configured resource set is Figure 12 As shown in the figure, if the preamble code received by the base station from the terminal through RO6 is preamble15 (not belonging to the shared preamble17-48), the base station can determine that the terminal initiating random access is a normal terminal. For another example, if the preamble code received by the base station from the terminal through RO1 is preamble17 (belonging to the shared preamble17-48), the base station can determine that the terminal initiating random access is a normal terminal. For another example, if the preamble code received by the base station from the terminal through RO1 is preamble15 (not belonging to the shared preamble17-48), the base station can determine that the terminal initiating random access is a normal terminal.

[0258] For example, suppose the configured resource collection is Figure 13 As shown, if the base station receives preamble 17 from the terminal (there is no shared preamble sequence), no matter through which RO the base station receives the preamble 17, the base station can confirm that the terminal initiating random access is a common terminal.

[0259] For example, suppose the configured resource collection is Figure 14 As shown, if the base station receives a preamble from the terminal through RO1 (no shared RO exists), no matter which preamble the base station receives through RO1, the base station can confirm that the terminal initiating random access is a common terminal.

[0260] In this case, for terminals whose capability types can be distinguished through message 1, the base station can adopt different scheduling strategies for terminals of different capability types in message 2, message 3 and subsequent steps of random access.

[0261] As a possible design, for a reduced-capability terminal, the scheduling policy sent by the base station to the reduced-capability terminal does not indicate any one or a combination of the following: frequency hopping, a frequency hopping range exceeding the terminal's supported bandwidth, frequency domain resources exceeding the terminal's supported bandwidth, a modulation and coding strategy exceeding a threshold, or transmission power control exceeding a threshold. In other words, the base station instructs the reduced-capability terminal to use a reduced communication rate (a rate that does not exceed the threshold) to send Message 2 to the reduced-capability terminal. It may instruct the reduced-capability terminal not to perform frequency hopping for Message 3, or instruct it to perform frequency hopping for Message 3 within the supported bandwidth of the reduced-capability terminal, indicate the frequency domain resources within the supported bandwidth for Message 3 to the terminal, indicate the modulation and coding strategy for Message 3 that does not exceed the threshold to the terminal, and indicate the transmission power control for Message 3 that does not exceed the threshold to the terminal.

[0262] Similarly, for a common terminal, a message 2 is sent to the common terminal using a normal communication rate, and the common terminal may be instructed to schedule a message 3 using a frequency hopping or non-frequency hopping method.

[0263] In other cases, network equipment cannot determine whether a terminal is a standard terminal or a reduced-capability terminal based on the target resource used by the terminal to send the preamble. As a possible design, if the target resource used by the terminal to send the preamble is within the shared resource, or if the terminal uses the shared resource to send the preamble, the base station cannot determine the terminal type based on the target resource used by the terminal to send the preamble.

[0264] Optionally, the target resource for the terminal to send the preamble is in the shared resource, which may mean that the RO for the terminal to send the preamble is in the shared RO, and the preamble sequence for sending the preamble is in the shared preamble sequence.

[0265] For example, suppose the configured resource collection is Figure 10 As shown, if the base station receives the preamble from the terminal through RO6 (in the shared RO), the base station cannot confirm the capability type of the terminal initiating random access.

[0266] For example, Figure 11 As shown, the ROs to which the terminal can send preambles are all shared ROs. Then, when the terminal sends any preamble in preambles 17-48 (which belong to shared preambles), the base station will not be able to confirm the capability type of the terminal.

[0267] For example, suppose the configured resource set is Figure 12 As shown, if the base station receives preamble 17 from the terminal through RO6, the base station cannot confirm the capability type of the terminal initiating random access.

[0268] In this case, for terminals whose capability types cannot be distinguished through Message 1, the base station can use the scheduling strategy for reduced-capability terminals to schedule these terminals that initiate random access until the capability types of these terminals are known. Optionally, the base station sends a scheduling strategy to these terminals, and the scheduling strategy does not indicate any one or a combination of the following: frequency hopping, the frequency hopping range exceeds the terminal supported bandwidth, the frequency domain resources exceed the terminal supported bandwidth, the modulation and coding strategy exceeds the threshold, and the transmission power control exceeds the threshold. Exemplarily, the base station sends Message 2 to these terminals at a lower transmission rate. As another example, when the base station schedules Message 3 for these terminals, it does not use frequency hopping, or indicates that the frequency hopping position is within the supported bandwidth of the reduced-capability terminal.

[0269] Alternatively, for terminals whose capability types cannot be distinguished by Message 1, such as terminals using shared resources to send preambles, the base station can treat these terminals as ordinary terminals and schedule them using the same scheduling policy as ordinary terminals. For example, Message 2 can be sent to these terminals at a normal communication rate, and Message 3 can be instructed to schedule these terminals using frequency hopping or non-frequency hopping.

[0270] It can be seen that in the embodiment of the present application, the base station has a high degree of freedom. For a terminal whose capability type cannot be distinguished through message 1, the base station can regard the terminal as an ordinary terminal or as a reduced-capability terminal.

[0271] In an embodiment of the present application, after the terminal receives a random access response from the network device, a message 3 may be sent according to the scheduling of the random access response, and the message 3 carries random access information. The random access information carried by the message 3 may be different under different conditions. As a possible design, when at least part of the shared resources include the target resource (or when the target resource is included in at least part of the shared resources), the terminal executes step S104 and sends the first random access information. When at least part of the shared resources do not include the target resource (or when the target resource includes at least part of the resources that are not shared), the terminal executes step S105 (not in step S106). Figure 9 ), the second random access information is sent. Steps S104 and S105 are respectively introduced as follows.

[0272] S104: When at least part of the shared resources include the target resource, the terminal sends first random access information.

[0273] Correspondingly, the network device receives first random access information from the terminal.

[0274] The first random access information may be used to indicate a capability type of the terminal, and the capability type of the terminal includes a first capability type or a second capability type. That is, the first random access information may be used to indicate whether the terminal is a normal terminal or a reduced capability terminal.

[0275] At least some of the shared resources include the target resource. That is, the shared resources between the standard terminal and the reduced-capability terminal include the target resource. This means that both the standard terminal and the reduced-capability terminal may use shared resources (RO and / or preamble sequence) to send preambles, and the base station cannot accurately determine the terminal's capability type based on the target resource used in Message 1. In this case, the terminal needs to send first random access information that can be used to indicate the terminal's capability type to assist the network device in determining the terminal's capability type.

[0276] For example, suppose the resource collection is Figure 10 As shown, the terminal that sends the preamble on any RO among RO5-RO8 will report its capability type through message 3 or other messages. In this way, the base station can distinguish the capability type of the terminal based on this.

[0277] As a possible design, the terminal sends a message 3 to the network device, where the message 3 carries the first random access information.

[0278] As a possible design, the terminal sends message 3 to the network device, which can be implemented as follows: the terminal sends the first random access information according to the scheduling policy indicated by the random access response. For example, the scheduling policy indicated by the random access response is shown in Table 2. The scheduling policy includes but is not limited to: a frequency hopping identifier, PUSCH frequency domain resource allocation, etc. The terminal sends message 3 according to the scheduling policy shown in Table 2.

[0279] In some embodiments, the first random access information may explicitly carry capability type information of the terminal, or in other words, the first random access information includes information that can be used to indicate the type of the terminal. For example, the first random access information carries a capability type field, and the field value of the field can be used to indicate the capability type of the terminal.

[0280] In other embodiments, the first random access information may implicitly carry the capability type information of the terminal.

[0281] As mentioned above, due to the limited supported bandwidth of reduced-capability terminals, their frequency hopping often forms (or has a high probability of forming) a gap, while the frequency hopping of ordinary terminals usually does not form a gap or has a low probability of forming a gap. Based on this characteristic, the base station can determine whether the terminal is an ordinary terminal or a reduced-capability terminal based on whether the random access information in message 3 forms a gap. Specifically, for a reduced-capability terminal, sending the first random access information can be: the terminal sends the first random access information on a first time-frequency resource; the first time-frequency resource is discontinuous in the time domain. For an ordinary terminal, sending the first random access information can be: the terminal sends the first random access information on a second time-frequency resource; the second time-frequency resource is continuous in the time domain.

[0282] For example, when the frequency hopping method is used to send message 3 (carrying the first random access information), the terminal Figure 5-1 The first random access information is sent on the first time-frequency resource shown in the black box, wherein, since the working frequency needs to be adjusted, Figure 5-1 As shown, the 8th and 9th OFDM symbols cannot be transmitted, so the first time-frequency resource is discontinuous in the time domain, forming a gap. This allows the base station to determine the capability type of the terminal initiating random access by detecting the energy strength of the symbols. For example, the base station can detect the strength of the 8th and 9th symbols to determine the capability type of the terminal. If signals are transmitted on these two symbols, it indicates a normal terminal. If no signals are transmitted on the 8th and 9th symbols, it indicates a terminal with reduced capabilities.

[0283] For example, the terminal Figure 5-2 The first random access information is sent on the second time-frequency resource shown in the black box. Since ordinary terminals do not need to adjust the working frequency, the OFDM symbols are sent normally, and the second time-frequency resource is continuous in the time domain without forming a gap.

[0284] In addition to implicitly indicating the capability type based on the Gap, there may be other ways to implicitly indicate the capability type, which is not limited in the embodiments of the present application.

[0285] For example, the base station indicates different scheduling strategies for terminals of different capability types. Subsequently, the base station accesses the first random access information according to the scheduling strategy. For example, the first random access information is received using the frequency domain resources and time domain resources shown in Table 2.

[0286] Furthermore, optionally, after receiving a message such as message 3 from the terminal, the base station may determine the capability type of the terminal according to the scheduling policy (such as specific time-frequency resources) of message 3.

[0287] For example, if the base station does not receive Message 3 or fails to parse it successfully, the base station may schedule Message 3 (carrying the first random access information) for retransmission. Optionally, the base station may determine a scheduling strategy for retransmitting Message 3 based on the terminal's capability type. The scheduling strategy includes whether to use frequency hopping, frequency domain resources, and so on. For example, if the base station determines through symbol energy detection that the terminal is a reduced-capability terminal, when scheduling the retransmission of Message 3, it may choose not to perform frequency hopping, or to perform frequency hopping within the bandwidth supported by the reduced-capability terminal.

[0288] S105: When at least part of the shared resources does not include the target resource, send second random access information.

[0289] The second random access information is different from the first random access information. The second random access information does not carry the capability type information of the terminal. In other words, the second random access information may not indicate the capability type of the terminal.

[0290] As a possible design, the terminal sends message 3, which carries second random access information.

[0291] Optionally, at least part of the shared resources do not include the target resource, and may be the RO that does not include the RO that sends the preamble in the shared RO. Figure 10 As shown, assuming that the RO of the terminal sending the preamble code is RO3 (not belonging to the shared RO5-RO8), then the base station can determine the capability type of the terminal according to RO3 of the sent preamble code, and the terminal does not need to report the capability type through the random access information of message 3.

[0292] Optionally, at least part of the shared resources do not include the target resource, which may be that the preamble sequence for sending the preamble code is not included in the shared preamble sequence. Figure 11 As shown, the preamble sequence for the terminal to send the preamble is preamble2 (not belonging to the shared preambles 17-48).

[0293] Optionally, at least part of the shared resources do not include the target resource, which may be that the RO that sends the preamble is not included in the shared RO, and / or the preamble sequence that sends the preamble is not included in the shared preamble sequence. Figure 12 As shown, the terminal sends preamble 17 on RO3. For another example, the terminal sends preamble 2 on RO5. For another example, the terminal sends preamble 2 on RO3.

[0294] Optionally, at least part of the shared resources do not include the target resource, which may be that the preamble sequence for sending the preamble code is not included in the shared preamble sequence. Figure 13 As shown, it is assumed that the preamble sequence of the terminal sending the preamble code is preamble2, and preamble2 is not in the shared preamble sequence (ie, preamble17-48).

[0295] Optionally, at least part of the shared resources do not include the target resource, which may be that the RO that sends the preamble is not included in the shared RO. Figure 14 As shown, it is assumed that the RO used by the terminal to send the preamble is RO1, and RO1 is not included in the shared RO.

[0296] It can be understood that the target resource for sending the preamble code is not included in at least part of the shared resources. The base station can distinguish the capability type of the terminal based on the target resource for sending the preamble code. Therefore, the terminal no longer needs to report its capability type through the second random access information of message 3.

[0297] The communication method provided in the embodiments of the present application enables a network device to identify the capability types of some terminals as early as possible based on the target resources for sending preamble codes, thereby facilitating early scheduling based on the capability types. For another portion of terminals, the network device can identify the capability types of these terminals based on the first random access information received from the terminals and schedule the terminals based on the capability types. In this solution, there is no need to isolate the resources of standard terminals from those of reduced-capability terminals, meaning that resources can be reused, resource configuration is more flexible, and resource utilization is higher.

[0298] The configuration of the code domain resource preamble sequence is described in detail below. There are many ways to configure the preamble sequence. The embodiment of the present application only lists the following methods 1 and 2 for example, but does not constitute a limitation on the configuration methods.

[0299] Method 1: Use bitmap to configure the preamble sequence

[0300] A bitmap may also be referred to as a bit sequence, and may include one or more bits, wherein each bit in the bitmap represents a sequence number (or index, identifier, etc.) of one or more preambles.

[0301] The bitmap includes a bitmap that can be used to indicate the preamble sequence allocation status of the terminal. For example, it can be used to indicate the preamble resource allocation of the reduced-capability terminal and / or can be used to indicate the preamble allocation of the normal terminal. Optionally, a bit value of 1 indicates that the preamble corresponding to the bit is allocated to the reduced-capability terminal, and a bit value of 0 indicates that the corresponding preamble is not allocated to the reduced-capability terminal. Alternatively, a bit value of 0 indicates that the preamble corresponding to the bit is allocated to the reduced-capability terminal, and a bit value of 1 indicates that the corresponding preamble is not allocated to the reduced-capability terminal.

[0302] Optionally, the bitmap also includes a bitmap that can be used to indicate shared resources between reduced-capability terminals and normal terminals. In this type of bitmap, bit 1 can indicate that the preamble corresponding to the bit is a preamble shared by the reduced-capability terminal and the normal terminal, and bit 0 can indicate that the preamble corresponding to the bit is not a preamble shared by the reduced-capability terminal and the normal terminal. Alternatively, bit 0 can indicate that the preamble corresponding to the bit is a preamble shared by the reduced-capability terminal and the normal terminal, and bit 1 can indicate that the preamble corresponding to the bit is not a preamble shared by the reduced-capability terminal and the normal terminal.

[0303] For example, Figure 15 As shown, it is assumed that the preamble code domain resources available to common terminals are p1-p20, and the preamble code domain resources available to reduced-capability terminals are p9-p24. The reduced-capability terminals share some resources with common terminals (ie, p9 to p20 are shared).

[0304] Then, taking one bit corresponding to one preamble code domain resource as an example, a 64-bit sequence [0,0,0,0,0,0,0,0,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,0,0,0,…,0,0] can be used to indicate Figure 15 This shows the preamble code domain resource allocation for a reduced-capability terminal. The first bit of this sequence corresponds to code domain resource p1, the second bit corresponds to p2, and so on. Bit 1 indicates that the corresponding preamble is allocated to the reduced-capability terminal, and bit 0 indicates that the corresponding preamble is not allocated to the reduced-capability terminal. This bit sequence indicates that the preamble code domain resources available to the reduced-capability terminal are p9-p24.

[0305] It is understandable that in order to reduce signaling, one bit may be used to represent multiple preamble numbers, for example, the first bit corresponds to p1-2, the second bit corresponds to p3-4, the third bit corresponds to p5-6, and so on.

[0306] A bit sequence may also be used to represent a preamble shared by the reduced-capability terminal and the normal terminal.

[0307] In one example, the 64-bit sequence [0,0,0,0,0,0,0,0,1,1,1,1,1,1,1,1,1,1,1,1,0,0,0,…,0,0,0,0] can be used to represent Figure 15This sequence shows the preambles shared by reduced-capability terminals and standard terminals. The first bit in the sequence corresponds to p1, the second bit corresponds to p2, and so on. A '1' bit indicates that the corresponding preamble is shared by standard and reduced-capability terminals, while a '0' bit indicates that the corresponding preamble is not shared by standard and reduced-capability terminals. This sequence indicates that p9-p20 are preambles shared by standard and reduced-capability terminals.

[0308] Alternatively, simplified signaling can be used to indicate the preamble shared by the reduced-capability terminal and the normal terminal. Figure 15 As shown in the figure, there are 16 preambles allocated to reduced-capability terminals, of which the first 12 preambles are shared by reduced-capability terminals and normal terminals. Therefore, a 16-bit bitmap [1,1,1,1,1,1,1,1,1,1,1,1,0,0,0,0] can be used to indicate the preambles allocated to reduced-capability terminals that are shared by reduced-capability terminals and normal terminals. The first bit of the sequence corresponds to the first preamble allocated to the reduced-capability terminal (i.e., p9), the second bit corresponds to the second preamble allocated to the reduced-capability terminal (i.e., p10), and so on. Bit '1' indicates that the corresponding preamble is shared by normal and reduced-capability terminals, and bit '0' indicates that the corresponding preamble is not a shared preamble.

[0309] In other embodiments, the preambles may be divided into multiple groups. Optionally, preambles in different groups may be used for different purposes. For example, the preambles in group A may be used for contention-based random access, while the preambles in group B may be used for non-contention-based random access.

[0310] Optionally, for each group of preambles, a bitmap may be used to represent preamble resource allocation and / or shared preambles.

[0311] For example, Figure 16 As shown, the number of preambles that a common terminal can use for random access is N = 20. These preambles are divided into two groups, 1A and 1B. Preambles 1-12 belong to group 1A, and group 1A contains N1 = 12 preambles. Preambles 13-20 belong to group 1B, and group 1B contains 8 preambles.

[0312] Still Figure 16 As shown, the preambles that can be used for random access by reduced-capability terminals are also divided into two groups, 2A and 2B. The preamble code domain resources for group 2A are p5-p12 and p21-p24. Therefore, the preamble for group 2A can be represented by a 64-bit bitmap [0,0,0,0,1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0,1,1,1,1,1,0,0,…,0,0,0] The first bit in this sequence corresponds to p1, the second bit corresponds to p2, and so on. A '1' bit indicates that the corresponding preamble is allocated to group 2A, and a '0' bit indicates that the corresponding preamble is not allocated to group 2A.

[0313] Furthermore, in group 2A, sequences p5-p12 are shared by reduced-capability terminals and standard terminals. Therefore, a 64-bit bitmap [0,0,0,0,1,1,1,1,1,1,1,1,0,0,0,…,0,0,0] can be used to indicate the shared preambles between reduced-capability terminals and standard terminals. Alternatively, to save signaling, a 12-bit bitmap [1,1,1,1,1,1,1,1,0,0,0,0] can be used to indicate the shared preambles between reduced-capability terminals and standard terminals in group 2A. The first bit of the 12-bit bitmap corresponds to the first preamble in group 2A (i.e., p5), the second bit corresponds to the second preamble in group 2A (i.e., p6), and so on. A '1' bit indicates that the corresponding preamble is shared by standard and reduced-capability terminals, and a '0' bit indicates that the corresponding preamble is not a shared preamble.

[0314] Similarly, if the preamble resources in group 2B are p17-p20 and p25-p28, a 64-bit bitmap of [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,1,1,1,0,0,0,0,1,1,1,1,0,0,…,0,0,0] can be used to represent the preamble allocated to group 2B. In group 2B, p17-p20 are preambles shared by reduced-capability terminals and standard terminals. A 64-bit bitmap of [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,1,1,0,0,…,0,0,0] can be used to indicate the preamble shared by reduced-capability terminals and standard terminals. Alternatively, to save signaling, a bitmap of length 8 [1,1,1,1,0,0,0,0] may be used to indicate the preamble shared by the reduced-capability terminals and normal terminals in group 2B.

[0315] Method 2: Use the start and length indication method to indicate the preamble configuration

[0316] The start (start) is the starting point or starting position of the allocated preamble resource, and the length (length) is the length of the allocated preamble resource. The start position and length of the preamble resource can be indicated to indicate the preamble resource allocated to the reduced-capability terminal and / or to indicate the preamble resource allocated to the normal terminal.

[0317] For example, Figure 17 As shown in the figure, assume that the available preambles for standard terminals are p1-p20, and the available preamble resources for reduced-capability terminals are p9-p24. The two are shared on p9-p20. Therefore, the preamble resource allocation for reduced-capability terminals can be represented by start = 9 and length = 16. Here, start = 9 indicates that the starting position of the preamble resource is p9, and the allocated length is 16, meaning that 16 consecutive preambles starting from p9 are allocated to the reduced-capability terminal.

[0318] Optionally, the preamble resource shared by the normal terminal and the reduced-capability terminal can be indicated by indicating the starting position and length of the preamble resource. Figure 17As shown, start = 9, length = 12 can be used to represent the preamble shared by the reduced-capability terminal and the normal terminal, which means that the 12 consecutive preambles starting from p9 are the preambles shared by the reduced-capability terminal and the normal terminal.

[0319] In some other embodiments, the preamble may be divided into multiple groups. Then, for each group, the preamble resource allocation and shared preamble may be represented by a starting point plus length.

[0320] For example, Figure 18 As shown, the number of preambbles available for random access of a common terminal is N=20, which are divided into two groups, 1A and 1B. Preambles 1-12 belong to group 1A, and the number of preambbles included in group 1A is N1=12. Preambles 13-20 belong to group 1B, and the number of preambbles included in group 1B is 8.

[0321] The preambles available for random access by downgraded-capability terminals are also divided into two groups, 2A and 2B. The preamble resources allocated to group 2A can be represented by {starting position: 5, length: 8} and {starting position: 21, length: 4}. That is, starting from preamble 5, 8 consecutive preamblers, and 4 consecutive preamblers starting from preamble 21 are allocated to group 2A.

[0322] Note that because the preamble resources in group 2A are divided into two parts, two sets of {starting position + length} are required to represent the resource allocation of group 2A. That is, the preamble resources in the same group can be allocated to multiple intervals, and the preamble numbers in each interval can be consecutive, so the base station can indicate the location of each interval separately.

[0323] In addition, {starting position: 5, length: 8} may be used to indicate the preambles p5-p12 shared by the reduced-capability terminal and the normal terminal.

[0324] Similarly, {starting position: 17, length: 4} and {starting position: 25, length: 4} can be used to indicate the preamble resources allocated to group 2B. That is, starting from preamble 17, 4 consecutive preambles, and starting from preamble 25, 4 consecutive preambles are allocated to group 2B. In addition, {starting position: 17, length: 4} can be used to indicate the preamble shared by the reduced-capability terminal and the normal terminal.

[0325] In other embodiments, the starting position (or length) may be default (e.g., predefined by the protocol). In this case, simply indicating the length (or starting position) confirms the allocated preamble. For example, if the starting position is specified as p1, then simply indicating the length, such as 16, confirms that the allocated resources are p1-16. This reduces signaling overhead.

[0326] In other embodiments, the starting point and length can be mapped to a value through methods such as joint coding. Afterwards, the allocated preamble can be confirmed by simply indicating the mapped value (for example, by carrying the value in a broadcast message). This can reduce signaling overhead. For example, V = 10 * S + L, where S is the starting point, L is the length, and V is the value after joint coding. The formula used for joint coding is not limited to V = 10 * S + L here, and can also be other, and the embodiments of the present application are not limited to this.

[0327] The above mainly uses the allocation of preamble resources to a reduced-capability terminal as an example to illustrate the preamble configuration method. For the allocation of preamble resources to a common terminal, refer to the allocation of preamble resources to a reduced-capability terminal.

[0328] In other embodiments, the network device may also obtain capability information reported by the terminal and determine the terminal's capability type based on the capability information. Capability information includes, but is not limited to, information such as the terminal's supported bandwidth and antenna configuration. For example, if the terminal reports only 20 MHz supported bandwidth and a single receive antenna, the base station can determine the terminal as a reduced-capability terminal based on this capability information. This allows the terminal to be scheduled as soon as possible based on its capability type when the terminal initiates random access, thereby improving communication performance.

[0329] It should be noted that the multiple information mentioned in the embodiments of the present application can be carried in multiple messages or in a single message. For example, RO set information and preamble set information can be carried in a single broadcast message. Alternatively, the RO set, preamble set, and other information can be carried in multiple broadcast messages.

[0330] In the case of dividing each functional module into corresponding functional modules, Figure 19 A schematic diagram of a possible structure of the communication device 19 involved in the above embodiment is shown. The device can implement the functions of the above terminal (for example, it can be a terminal or a chip). Alternatively, the device can implement the functions of a network device (for example, it can be a network device or a chip). The communication device 19 includes a processing unit 1901 and a transceiver unit 1902.

[0331] Taking the communication device 19 as a terminal device as an example, the processing unit 1901 is used to execute Figure 9 S101 (such as controlling the transceiver unit 1902 to receive configuration information) and S102, and / or for executing other steps in the above method embodiment. The transceiver unit 1902 is used to support the terminal device to execute Figure 9 S103, S104 (or S105) in.

[0332] Taking the communication device 19 as a network device as an example, the processing unit 1901 is used to determine the above configuration information and / or to perform other steps in the above method embodiment. The transceiver unit 1902 is used to support the network device to perform Figure 9 S103, S104 (or S105) in.

[0333] Optionally, the communication device 19 may further include a storage unit 1903 for storing data, programs, etc.

[0334] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0335] The present application also provides a communication device. The communication device is used to implement the various communication methods described above. The communication device includes modules, units, or means corresponding to the communication methods described above. The modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0336] An embodiment of the present application provides a chip system, which includes a processor and an input / output port. The processor is used to implement the processing functions involved in the communication method of the above method embodiment, and the input / output port is used to implement the transceiver functions involved in the communication method of the above method embodiment.

[0337] In one possible design, the chip system also includes a memory, which is used to store program instructions and data for implementing the functions involved in any of the above-mentioned communication methods.

[0338] The chip system may be composed of chips, or may include chips and other discrete devices.

[0339] An embodiment of the present application provides a communication system, which includes one or more terminal devices described above and one or more network devices.

[0340] An embodiment of the present application provides a computer-readable storage medium, including: computer instructions stored in the computer-readable storage medium; when the computer instructions are executed on a computer, the computer executes the communication method of the above method embodiment.

[0341] An embodiment of the present application provides a computer program product containing instructions, including a computer program or instructions. When the computer program or instructions are run on a computer, the computer is caused to execute the communication method described in the above method embodiment.

[0342] It should be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0343] It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Exemplary, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0344] The above embodiments can be implemented in whole or in part by software, hardware (such as circuits), firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (such as infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.

[0345] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0346] Those skilled in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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 application.

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

[0348] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0349] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0350] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0351] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0352] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: The method applied to a terminal or a chip in a terminal includes: Acquiring configuration information; the configuration information is used to indicate a resource set, the resource set including a first resource set and / or a second resource set; resources in the first resource set can be used for a terminal of a first capability type to send a preamble, and resources in the second resource set can be used for a terminal of a second capability type to send a preamble; at least part of the resources of the first resource set and at least part of the resources of the second resource set are shared; Selecting a target resource from the resource set, and sending a preamble through the target resource; receiving a random access response; When the at least part of the shared resources includes the target resource, sending first random access information; the first random access information may be used to indicate a capability type of the terminal, and the capability type of the terminal includes the first capability type or the second capability type; When the at least part of the shared resources does not include the target resource, second random access information is sent; the second random access information is different from the first random access information.

2. The communication method according to claim 1, wherein: The first resource set includes a first random access opportunity RO set, the first RO set including at least one first RO; the second resource set includes a second RO set, the second RO set including at least one second RO; the first RO is an RO available for a terminal of a first capability type to send a preamble, and the second RO is an RO available for a terminal of a second capability type to send a preamble; and / or, The first resource set includes a first preamble set, the first preamble set includes at least one first preamble, and the first preamble is a preamble available to terminals of a first capability type; the second resource set includes a second preamble set, the second preamble set includes at least one second preamble, and the second preamble is a preamble available to terminals of a second capability type; At least part of the resources of the first resource set and at least part of the resources of the second resource set are shared, including: at least part of the ROs in the first RO set are shared with at least part of the ROs in the second RO set, and / or, at least part of the preamble codes in the first preamble code set are shared with at least part of the preamble codes in the second preamble code set.

3. The communication method according to claim 2, wherein: The target resource includes a target RO and a target preamble; The at least part of the shared resources includes the target resources, including: the at least part of the ROs shared by the first RO set and the second RO includes the target RO, and the at least part of the preambles shared by the first preamble set and the second preamble set includes the target preamble.

4. The communication method according to claim 2 or 3, characterized in that: The configuration information may also be used to indicate the at least portion of ROs shared by the first RO set and the second RO set, or the at least portion of preambles shared by the first preamble set and the second preamble set, or the at least portion of ROs shared by the first RO set and the second RO and the at least portion of preambles shared by the first preamble set and the second preamble set.

5. The communication method according to any one of claims 1 to 3, characterized in that: The first random access information includes information indicating a capability type of the terminal.

6. The communication method according to any one of claims 1 to 3, characterized in that: Sending first random access information includes: sending the first random access information on a first time-frequency resource; the first time-frequency resource is discontinuous in the time domain.

7. The communication method according to any one of claims 1 to 3, characterized in that: Sending the first random access information includes: sending the first random access information on a second time-frequency resource; the second time-frequency resource is continuous in the time domain.

8. The communication method according to any one of claims 1 to 3, characterized in that: The method further includes: retransmitting the first random access information.

9. The communication method according to any one of claims 1 to 3, characterized in that: The random access response includes information about a scheduling strategy; the scheduling strategy includes any one or a combination of multiple strategies: frequency hopping, frequency domain resources, time domain resources, modulation and coding strategy, and transmission power control strategy.

10. The communication method according to claim 9, wherein: The sending the first random access information includes: First random access information is sent according to the scheduling policy indicated by the random access response.

11. The communication method according to claim 9, wherein: When at least part of the shared resources include the target resources, the scheduling strategy does not indicate any one or a combination of the following: frequency hopping, the frequency hopping range exceeds the terminal supported bandwidth, the frequency domain resources exceed the terminal supported bandwidth, the modulation and coding strategy exceeds the threshold, and the transmission power control exceeds the threshold.

12. A communication method, characterized in that: The method applied to a network device or a chip in a network device includes: Sending configuration information; the configuration information is used to indicate a resource set, the resource set including a first resource set and / or a second resource set; resources in the first resource set can be used for a terminal of a first capability type to send a preamble, and resources in the second resource set can be used for a terminal of a second capability type to send a preamble; at least part of the resources of the first resource set and at least part of the resources of the second resource set are shared; receiving a preamble through a target resource in the resource set; Sending a random access response; When the at least part of the shared resources includes the target resource, receiving first random access information; the first random access information may be used to indicate a capability type of the terminal, the capability type of the terminal including the first capability type or the second capability type; When the at least part of the shared resources does not include the target resource, second random access information is received; the second random access information is different from the first random access information.

13. The communication method according to claim 12, wherein: The first resource set includes a first random access opportunity RO set, the first RO set including at least one first RO; the second resource set includes a second RO set, the second RO set including at least one second RO; the first RO is an RO available for a terminal of a first capability type to send a preamble, and the second RO is an RO available for a terminal of a second capability type to send a preamble; and / or, The first resource set includes a first preamble set, the first preamble set includes at least one first preamble, and the first preamble is a preamble available to terminals of a first capability type; the second resource set includes a second preamble set, the second preamble set includes at least one second preamble, and the second preamble is a preamble available to terminals of a second capability type; At least part of the resources of the first resource set and at least part of the resources of the second resource set are shared, including: at least part of the ROs in the first RO set are shared with at least part of the ROs in the second RO set, and / or, at least part of the preamble codes in the first preamble code set are shared with at least part of the preamble codes in the second preamble code set.

14. The communication method according to claim 13, wherein: The target resource includes a target RO and a target preamble; The at least part of the shared resources includes the target resources, including: the at least part of the ROs shared by the first RO set and the second RO includes the target RO, and the at least part of the preambles shared by the first preamble set and the second preamble set includes the target preamble.

15. The communication method according to claim 13 or 14, characterized in that: The configuration information may also be used to indicate the at least portion of ROs shared by the first RO set and the second RO set, or the at least portion of preambles shared by the first preamble set and the second preamble set, or the at least portion of ROs shared by the first RO set and the second RO and the at least portion of preambles shared by the first preamble set and the second preamble set.

16. The communication method according to any one of claims 12 to 14, characterized in that: The first random access information includes information indicating a capability type of the terminal.

17. The communication method according to any one of claims 12 to 14, characterized in that: Receiving first random access information includes: receiving the first random access information on a first time-frequency resource; the first time-frequency resource is discontinuous in the time domain.

18. The communication method according to any one of claims 12 to 14, characterized in that: Receiving first random access information includes: receiving the first random access information on a second time-frequency resource; the second time-frequency resource is continuous in the time domain.

19. The communication method according to any one of claims 12 to 14, characterized in that: The method further includes receiving retransmitted first random access information.

20. The communication method according to any one of claims 12 to 14, characterized in that: The random access response includes information about a scheduling strategy; the scheduling strategy includes any one or a combination of multiple strategies: frequency hopping, frequency domain resources, time domain resources, modulation and coding strategy, and transmission power control strategy.

21. The communication method according to claim 20, wherein: The receiving first random access information includes: First random access information is received according to the scheduling policy.

22. The communication method according to claim 20, wherein: When at least part of the shared resources include the target resources, the scheduling strategy does not indicate any one or a combination of the following: frequency hopping, the frequency hopping range exceeds the terminal supported bandwidth, the frequency domain resources exceed the terminal supported bandwidth, the modulation and coding strategy exceeds the threshold, and the transmission power control exceeds the threshold.

23. A terminal device, characterized in that: include: one or more processors and one or more memories; The one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, where the computer program code includes computer instructions. When the one or more processors execute the computer instructions, the terminal device executes the method according to any one of claims 1 to 11.

24. A network device, characterized in that: include: one or more processors and one or more memories; The one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, where the computer program code includes computer instructions. When the one or more processors execute the computer instructions, the network device executes the method according to any one of claims 12 to 22.

25. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which, when called by the computer, are used to enable the computer to execute the method of any one of claims 1 to 11, or the method of any one of claims 12 to 22.

26. A computer program product comprising instructions, characterized in that When the computer program product is run on a computer, the computer is enabled to execute the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 22.

27. A chip, characterized in that: The chip is coupled to the memory and is configured to read and execute program instructions stored in the memory to implement the method according to any one of claims 1 to 11, or to implement the method according to any one of claims 12 to 22.

Images