Method and apparatus for accessing a network device

Abstract

The application discloses a method and device for accessing a network device, relates to the field of wireless communication, and can control the number of reduced capability (REDCAP) terminals accessing the network device, and improves network transmission performance. The method comprises the following steps: a terminal device receives first information from a network device, the first information being used for indicating whether a REDCAP terminal is allowed to access the network device; and the terminal device determines whether to access the network device according to the first information. The REDCAP terminal comprises a first type of REDCAP terminal and a second type of REDCAP terminal, the frequency domain range in which the first type of REDCAP terminal and the second type of REDCAP terminal work is the same, the bandwidth of the second type of REDCAP terminal is smaller than that of the first type of REDCAP terminal, and / or the number of receiving antennas of the second type of REDCAP terminal is smaller than that of the first type of REDCAP terminal.

Description

[0001] This application is a divisional application. The original application has the application number 202011032886.X and the original application date is September 27, 2020. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication, and more particularly to methods and apparatus for accessing network devices. Background Technology

[0003] In new radio (NR) systems, network devices (e.g., base stations) broadcast synchronization signals / physical broadcast channel blocks (SSBs). If a terminal device wants to access the network for wireless communication services, it receives the SSB and retrieves system information from it. This system information indicates whether the terminal device is permitted to access the network. If the system information indicates that network access is permitted, the terminal device will subsequently access the network through a random access procedure. If the system information indicates that network access is prohibited, the terminal device will not be able to access the network.

[0004] Currently, a new type of terminal device is being considered for introduction in NR systems—the reduced capability (REDCAP) terminal. Compared to ordinary terminals whose network access permissions are indicated in the SSB (Service Subsystem Block), REDCAP terminals have longer battery life, lower complexity, and lower cost, making them widely applicable. However, REDCAP terminals have narrower bandwidth or fewer receive antennas than ordinary terminals, resulting in lower transmission capacity. A large number of REDCAP terminals in the network can lead to a decline in overall network transmission performance, such as a decrease in average spectral efficiency. Summary of the Invention

[0005] This application provides a method and apparatus for accessing network devices, which can control the number of REDCAP terminals accessing the network devices and improve network transmission performance.

[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0007] In a first aspect, embodiments of this application provide a method for accessing a network device. The method includes: a terminal device receiving first information from the network device, the first information indicating whether a REDCAP terminal is allowed to access the network device, the REDCAP terminal including a first type of REDCAP terminal and a second type of REDCAP terminal, the first type of REDCAP terminal and the second type of REDCAP terminal operating in the same frequency domain range, the bandwidth of the second type of REDCAP terminal being less than that of the first type of REDCAP terminal, and / or the number of receiving antennas of the second type of REDCAP terminal being less than that of the first type of REDCAP terminal; the terminal device determining whether to access the network device based on the first information, wherein the terminal device is either the first type of REDCAP terminal or the second type of REDCAP terminal.

[0008] The method provided in the first aspect above allows the terminal device to receive first information from a network device indicating whether a first type of REDCAP terminal is allowed to access the network device and whether a second type of REDCAP terminal is allowed to access the network device, and to determine whether to access the network device based on the first information. In this way, the network device can control the number of first type REDCAP terminals and second type REDCAP terminals accessing the network device to ensure the transmission performance of the network managed by the network device.

[0009] One possible implementation is that the first information includes first indication information and second indication information; wherein the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device; or, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the first and second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the network device. Based on the above method, the first indication information and the second indication information can respectively indicate whether the first type of REDCAP terminal is allowed to access the network device and whether the second type of REDCAP terminal is allowed to access the network. The first indication information and the second indication information can also jointly indicate whether the first type of REDCAP terminal is allowed to access the network device and whether the second type of REDCAP terminal is allowed to access the network, providing flexibility in the indication method.

[0010] One possible implementation is that the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device. The first indication information includes empty fields in the MIB, and the second indication information includes reserved fields in the additional physical broadcasting channel (PBCH) payload. Alternatively, the first indication information includes a "prohibit access" field in the MIB, and the second indication information includes empty fields in the MIB or reserved fields in the additional PBCH payload (additional PBCH payload / additional timing related PBCH payload bits), or fields in the PBCH other than those in the MIB. Based on the above method, the first and second indication information can respectively indicate whether the first type of REDCAP terminal is allowed to access the network device, providing clear and convenient indication.

[0011] One possible implementation is that the first indication information is used to indicate whether a first type of REDCAP terminal is allowed to access the network device, and the first and second indication information are used to indicate whether a second type of REDCAP terminal is allowed to access the network device. The first indication information includes empty fields in the MIB, and the second indication information includes reserved fields in the additional PBCH payload. Based on the above method, whether a first type of REDCAP terminal is allowed to access the network device will affect whether a second type of REDCAP terminal is allowed to access the network device. Therefore, the priority of first and second type REDCAP terminals accessing the network device can be distinguished to ensure that higher-priority terminal types are given priority access to the network device.

[0012] One possible implementation is that the first information is included in the SSB, which includes the MIB and an additional PBCH payload. Based on the above method, the network device can indicate whether to allow a REDCAP terminal to access the network device via the MIB and the additional PBCH payload in the SSB.

[0013] One possible implementation is that the first indication information is included in a reserved field of the downlink control information (DCI), and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in a reserved field of the DCI, and the second indication information is included in a system information block type 1 (SIB1) information block; or, the first indication information is included in an SIB1 information block, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in an SIB1 information block, and the second indication information is included in an SIB1 information block; wherein, the DCI is used to schedule SIB1. Based on the above method, the network device can indicate whether to allow the REDCAP terminal to access the network device through the reserved field in the DCI and / or the SIB1 information block.

[0014] One possible implementation is that the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "prohibit access" field in the MIB; the second indication information is included in a reserved field in the DCI, or the second indication information is included in the SIB1 information block; or the first indication information is included in a reserved field in the DCI, or the first indication information is included in the SIB1 information block, and the second indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "prohibit access" field in the MIB, wherein the DCI is used to schedule SIB1. Based on the above method, the network device can indicate whether to allow the REDCAP terminal to access the network device through the reserved fields in the SSB and DCI, or the network device can indicate whether to allow the REDCAP terminal to access the network device through the SSB and SIB1 information block.

[0015] One possible implementation is that the first information indicates permission for the first type of REDCAP terminal and / or the second type of REDCAP terminal to access the network device. The method further includes: the terminal device sending second information to the network device, the second information indicating that the terminal device is either the first type of REDCAP terminal or the second type of REDCAP terminal. Based on the above method, the terminal device can report its type to the network device through the second information. On the one hand, this avoids the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the maximum bandwidth of the REDCAP terminals. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmission.

[0016] One possible implementation is that the second information is carried on a physical random access channel (PRACH), the resources of which correspond to either the first type of REDCAP terminal or the second type of REDCAP terminal. The PRACH resources include at least one of the time-domain resources, frequency-domain resources, or code-domain resources of the PRACH. Alternatively, the second information is carried in Msg3, MsgA, or radio resource control (RRC) signaling. Based on the above methods, the terminal device can report its type to the network device through various methods such as PRACH resources, Msg3, MsgA, or RRC signaling, so that the network device can identify the type of the terminal device.

[0017] One possible implementation is that the first information indicates that both the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device; the method further includes: the terminal device sending second information to the network device, the second information indicating that the terminal device belongs to the REDCAP terminal category; the terminal device sending third information to the network device, the third information indicating that the terminal device is either the first type of REDCAP terminal or the second type of REDCAP terminal. Based on the above method, the terminal device can report its type to the network device through the second and third information, so that the network device can identify the type of the terminal device. On the one hand, this avoids the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the maximum bandwidth of the REDCAP terminals. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmission.

[0018] One possible implementation is that the second information is carried in the PRACH, and the resources of the PRACH correspond to the REDCAP terminal. The PRACH resources include at least one of the time-domain resources, frequency-domain resources, or code-domain resources of the PRACH; the third information is carried in Msg3, MsgA, or RRC signaling. Based on the above method, the first type of REDCAP terminal can share the PRACH resources with the second type of REDCAP terminal. This avoids excessive fragmentation of PRACH resources, thus preventing excessive degradation of random access capacity.

[0019] Secondly, embodiments of this application provide a method for accessing a network device. The method includes: the network device determining first information, the first information indicating whether a REDCAP terminal is allowed to access the network device, the REDCAP terminal including a first type of REDCAP terminal and a second type of REDCAP terminal, the first type of REDCAP terminal and the second type of REDCAP terminal operating in the same frequency domain range, the bandwidth of the second type of REDCAP terminal being less than that of the first type of REDCAP terminal, and / or the number of receiving antennas of the second type of REDCAP terminal being less than that of the first type of REDCAP terminal; the network device sending the first information to a terminal device.

[0020] The method provided in the second aspect above allows the network device to determine first information indicating whether to allow a first type of REDCAP terminal to access the network device and whether to allow a second type of REDCAP terminal to access the network device, and to send the first information to the terminal device. In this way, the network device can control the number of first type REDCAP terminals and second type REDCAP terminals accessing the network device to ensure the transmission performance of the network managed by the network device.

[0021] One possible implementation is that the first information includes first indication information and second indication information; wherein the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device; or, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the first and second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the network device. Based on the above method, the first indication information and the second indication information can respectively indicate whether the first type of REDCAP terminal is allowed to access the network device and whether the second type of REDCAP terminal is allowed to access the network. The first indication information and the second indication information can also jointly indicate whether the first type of REDCAP terminal is allowed to access the network device and whether the second type of REDCAP terminal is allowed to access the network, providing flexibility in the indication method.

[0022] One possible implementation is that the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device. The first indication information includes a free field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload. Alternatively, the first indication information includes a "prohibit access" field in the MIB, and the second indication information includes a free field in the MIB or a reserved field in the additional PBCH payload. Based on the above method, the first and second indication information can respectively indicate whether the first type of REDCAP terminal is allowed to access the network device, providing clear and convenient indication.

[0023] One possible implementation is that the first indication information is used to indicate whether a first type of REDCAP terminal is allowed to access the network device, and the first and second indication information are used to indicate whether a second type of REDCAP terminal is allowed to access the network device. The first indication information includes empty fields in the MIB, and the second indication information includes reserved fields in the additional PBCH payload. Based on the above method, whether a first type of REDCAP terminal is allowed to access the network device will affect whether a second type of REDCAP terminal is allowed to access the network device. Therefore, the priority of first and second type REDCAP terminals accessing the network device can be distinguished to ensure that higher-priority terminal types are given priority access to the network device.

[0024] One possible implementation is that the first information is included in the SSB, which includes the MIB and an additional PBCH payload. Based on the above method, the network device can indicate whether to allow a REDCAP terminal to access the network device via the MIB and the additional PBCH payload in the SSB.

[0025] One possible implementation is that the first indication information is included in a reserved field of the DCI, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in a reserved field of the DCI, and the second indication information is included in the SIB1 information block; or, the first indication information is included in the SIB1 information block, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in the SIB1 information block, and the second indication information is included in the SIB1 information block; wherein, the DCI is used for scheduling SIB1. Based on the above method, the network device can indicate whether to allow the REDCAP terminal to access the network device through the reserved field in the DCI and / or the SIB1 information block.

[0026] One possible implementation is that the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "prohibit access" field in the MIB; the second indication information is included in a reserved field in the DCI, or the second indication information is included in the SIB1 information block; or the first indication information is included in a reserved field in the DCI, or the first indication information is included in the SIB1 information block, and the second indication information is included in a spare field in the MIB, a reserved field in the additional PBCH payload, or a "prohibit access" field in the MIB, wherein the DCI is used to schedule SIB1. Based on the above method, the network device can indicate whether to allow the REDCAP terminal to access the network device through the reserved fields in the SSB and DCI, or the network device can indicate whether to allow the REDCAP terminal to access the network device through the SSB and SIB1 information block.

[0027] One possible implementation is that the first information indicates that the first type of REDCAP terminal and / or the second type of REDCAP terminal are allowed to access the network device. The method further includes: the network device receiving second information from the terminal device, the second information indicating that the terminal device is either the first type of REDCAP terminal or the second type of REDCAP terminal. Based on the above method, the network device can receive the second information from the terminal device and determine whether the terminal device is the first type of REDCAP terminal or the second type of REDCAP terminal through the second information. On the one hand, this avoids the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the maximum bandwidth of the REDCAP terminal. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmission.

[0028] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to either the first type of REDCAP terminal or the second type of REDCAP terminal. The PRACH resources include at least one of the time-domain resources, frequency-domain resources, or code-domain resources of the PRACH; alternatively, the second information is carried in Msg3, MsgA, or RRC signaling. Based on the above methods, network devices can determine the type of terminal device through various methods such as PRACH resources, Msg3, MsgA, or RRC signaling.

[0029] One possible implementation is that the first information indicates that both the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device; the method further includes: the network device receiving second information from the terminal device, the second information indicating that the terminal device is a REDCAP terminal; the network device receiving third information from the terminal device, the third information indicating that the terminal device is either the first type of REDCAP terminal or the second type of REDCAP terminal. Based on the above method, the network device can determine whether the terminal device is the first type of REDCAP terminal or the second type of REDCAP terminal through the second and third information. On the one hand, this avoids the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the maximum bandwidth of the REDCAP terminals. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmission.

[0030] In one possible implementation, the second information is carried in a PRACH, the resources of which correspond to the REDCAP terminal. The PRACH resources include at least one of the time-domain resources, frequency-domain resources, or code-domain resources of the PRACH; the third information is carried in Msg3, MsgA, or RRC signaling. Based on the above method, the network device can determine the type of terminal device by combining the PRACH resources and the Msg3, MsgA, or RRC signaling.

[0031] Thirdly, embodiments of this application provide a communication device that can implement the methods described in the first aspect or any possible implementation of the first aspect. The device includes corresponding units or components for performing the described methods. The units included in the device can be implemented in software and / or hardware. The device can be, for example, a terminal, or a chip, chip system, or processor that supports the implementation of the described methods in a terminal.

[0032] Fourthly, embodiments of this application provide a communication device that can implement the methods in the second aspect or any possible implementation of the second aspect described above. The device includes corresponding units or components for performing the above methods. The units included in the device can be implemented in software and / or hardware. The device can be, for example, a network device, or a chip, chip system, or processor that supports the implementation of the above methods in a network device.

[0033] Fifthly, embodiments of this application provide a communication device, including: a processor coupled to a memory, the memory being used to store programs or instructions, which, when executed by the processor, cause the device to implement the method described in the first aspect or any possible implementation of the first aspect.

[0034] In a sixth aspect, embodiments of this application provide a communication device, including: a processor coupled to a memory for storing programs or instructions, wherein when the program or instructions are executed by the processor, the device implements the method described in the second aspect above, or any possible implementation of the second aspect.

[0035] In a seventh aspect, embodiments of this application provide a communication device for implementing the method described in the first aspect or any possible implementation of the first aspect.

[0036] Eighthly, embodiments of this application provide a communication device for implementing the method described in the second aspect or any possible implementation of the second aspect.

[0037] Ninthly, embodiments of this application provide a computer-readable medium having a computer program or instructions stored thereon, which, when executed, cause a computer to perform the method described in the first aspect or any possible implementation thereof.

[0038] In a tenth aspect, embodiments of this application provide a computer-readable medium having a computer program or instructions stored thereon, which, when executed, cause a computer to perform the method described in the second aspect above, or any possible implementation thereof.

[0039] Eleventhly, embodiments of this application provide a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the method described in the first aspect or any possible implementation of the first aspect.

[0040] In a twelfth aspect, embodiments of this application provide a computer program product comprising computer program code, which, when executed on a computer, causes the computer to perform the methods described in the second aspect above, or any possible implementation thereof.

[0041] In a thirteenth aspect, embodiments of this application provide a chip, including: a processor coupled to a memory, the memory being used to store programs or instructions, wherein when the program or instructions are executed by the processor, the chip causes the chip to implement the method described in the first aspect above, or any possible implementation of the first aspect.

[0042] In a fourteenth aspect, embodiments of this application provide a chip, including: a processor coupled to a memory, the memory being used to store programs or instructions, which, when executed by the processor, cause the chip to implement the method described in the second aspect above, or any possible implementation of the second aspect.

[0043] In a fifteenth aspect, embodiments of this application provide a communication system. This system includes the apparatus described in the third aspect and / or the apparatus described in the fourth aspect, or the system includes the apparatus described in the fifth aspect and / or the apparatus described in the sixth aspect, or the system includes the apparatus described in the seventh aspect and / or the apparatus described in the eighth aspect.

[0044] It is understood that any of the communication devices, chips, computer-readable media, computer program products or communication systems provided above are used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0045] In a sixteenth aspect, embodiments of this application provide a method for accessing a network device. The method includes: a terminal device receiving first information from the network device, the first information indicating whether a REDCAP terminal is allowed to access the network device, the REDCAP terminal including a first type REDCAP terminal and a second type REDCAP terminal, or the REDCAP terminal including a third type REDCAP terminal, the first type REDCAP terminal and the second type REDCAP terminal operating in the same frequency domain range, the third type REDCAP terminal operating in a different frequency domain range than the first type REDCAP terminal and the second type REDCAP terminal; the second type REDCAP terminal having a smaller bandwidth than the first type REDCAP terminal, and / or the second type REDCAP terminal having a smaller number of receiving antennas than the first type REDCAP terminal; the terminal device determining whether to access the network device based on the first information, wherein the terminal device is the first type REDCAP terminal, or the second type REDCAP terminal, or the third type REDCAP terminal.

[0046] The method provided in the sixteenth aspect above allows the terminal device to receive first information from the network device indicating whether a first type of REDCAP terminal is allowed to access the network device, and whether a second type of REDCAP terminal is allowed to access the network device, or to receive first information from the network device indicating whether a third type of REDCAP terminal is allowed to access the network device, and to determine whether to access the network device based on the first information. In this way, the network device can control the number of first, second, or third type REDCAP terminals accessing the network device to ensure the transmission performance of the network managed by the network device.

[0047] One possible implementation is that the REDCAP terminal includes a first type of REDCAP terminal and a second type of REDCAP terminal; the first information includes first indication information and second indication information; wherein, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device; or, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the first and second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the network device. Based on the above method, the first indication information and the second indication information can respectively indicate whether the first type of REDCAP terminal is allowed to access the network device and whether the second type of REDCAP terminal is allowed to access the network. The first indication information and the second indication information can also jointly indicate whether the first type of REDCAP terminal is allowed to access the network device and whether the second type of REDCAP terminal is allowed to access the network, providing flexibility in the indication method.

[0048] One possible implementation is that the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device. The first indication information includes a free field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload. Alternatively, the first indication information includes a "prohibit access" field in the MIB, and the second indication information includes a free field in the MIB, or includes a reserved field in the additional PBCH payload. Based on the above method, the first and second indication information can respectively indicate whether the first type of REDCAP terminal is allowed to access the network device, providing clear and convenient indication.

[0049] One possible implementation is that the first indication information is used to indicate whether a first type of REDCAP terminal is allowed to access the network device, and the first and second indication information are used to indicate whether a second type of REDCAP terminal is allowed to access the network device. The first indication information includes empty fields in the MIB, and the second indication information includes reserved fields in the additional PBCH payload. Based on the above method, whether a first type of REDCAP terminal is allowed to access the network device will affect whether a second type of REDCAP terminal is allowed to access the network device. Therefore, the priority of first and second type REDCAP terminals accessing the network device can be distinguished to ensure that higher-priority terminal types are given priority access to the network device.

[0050] One possible implementation is that the first indication information is included in a reserved field of the DCI, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in a reserved field of the DCI, and the second indication information is included in the SIB1 information block; or, the first indication information is included in the SIB1 information block, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in the SIB1 information block, and the second indication information is included in the SIB1 information block; wherein, the DCI is used for scheduling SIB1. Based on the above method, the network device can indicate whether to allow the REDCAP terminal to access the network device through the reserved field in the DCI and / or the SIB1 information block.

[0051] One possible implementation is that the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "prohibit access" field in the MIB; the second indication information is included in a reserved field in the DCI, or the second indication information is included in the SIB1 information block; or the first indication information is included in a reserved field in the DCI, or the first indication information is included in the SIB1 information block, and the second indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "prohibit access" field in the MIB, wherein the DCI is used to schedule SIB1. Based on the above method, the network device can indicate whether to allow the REDCAP terminal to access the network device through the reserved fields in the SSB and DCI, or the network device can indicate whether to allow the REDCAP terminal to access the network device through the SSB and SIB1 information block.

[0052] In one possible implementation, the REDCAP terminal includes the third type of REDCAP terminal; the first information includes third indication information; wherein the third indication information is used to indicate whether the third type of REDCAP terminal is allowed to access the network device. Based on the above method, the network device can indicate whether the third type of REDCAP terminal is allowed to access the network device through the third indication information.

[0053] One possible implementation is that the third indication information includes a blank field in the MIB; or, the third indication information includes a "Do Not Access" field in the MIB. Based on the above methods, the network device can indicate whether a third-type REDCAP terminal is allowed to access the network device through a blank field in the MIB, or it can indicate whether a third-type REDCAP terminal is allowed to access the network device through a "Do Not Access" field in the MIB, providing flexibility in the indication method.

[0054] One possible implementation is that the first information is included in the SSB, which includes the MIB and the additional PBCH payload. Based on the above method, the network device can indicate whether to allow a REDCAP terminal to access the network device through the MIB and the additional PBCH payload in the SSB.

[0055] One possible implementation is that the third indication information is included in a reserved field of the DCI; or, the third indication information is included in the SIB1 information block. Based on the above methods, the network device can indicate whether a third-type REDCAP terminal is allowed to access the network device through a reserved field in the DCI, or it can indicate whether a third-type REDCAP terminal is allowed to access the network device through the SIB1 information block, providing flexibility in the indication method.

[0056] One possible implementation is that the first information indicates that the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal is allowed to access the network device; or the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device; the method further includes: the terminal device sending second information to the network device, the second information indicating that the terminal device is the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal. Based on the above method, the terminal device can report its type to the network device through the second information. On the one hand, this can avoid the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the maximum bandwidth of the REDCAP terminals. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmission.

[0057] One possible implementation is that the second information is carried in a PRACH, and the resources of the PRACH correspond to the first type of REDCAP terminal, the second type of REDCAP terminal, or the third type of REDCAP terminal. The PRACH resources include at least one of the time-domain resources, frequency-domain resources, or code-domain resources of the PRACH; or, the second information is carried in Msg3, MsgA, or RRC signaling. Based on the above method, the terminal device can report its type to the network device through various methods such as PRACH resources, Msg3, MsgA, or RRC signaling, so that the network device can identify the type of the terminal device.

[0058] One possible implementation is that the first information indicates that both the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device; the method further includes: the terminal device sending second information to the network device, the second information indicating that the terminal device belongs to the REDCAP terminal category; the terminal device sending third information to the network device, the third information indicating that the terminal device is either the first type of REDCAP terminal or the second type of REDCAP terminal. Based on the above method, the terminal device can report its type to the network device through the second and third information, so that the network device can identify the type of the terminal device. On the one hand, this avoids the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the maximum bandwidth of the REDCAP terminals. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmission.

[0059] One possible implementation is that the second information is carried in the PRACH, and the resources of the PRACH correspond to the REDCAP terminal. The PRACH resources include at least one of the time-domain resources, frequency-domain resources, or code-domain resources of the PRACH; the third information is carried in Msg3, MsgA, or RRC signaling. Based on the above method, the first type of REDCAP terminal can share the PRACH resources with the second type of REDCAP terminal. This avoids excessive fragmentation of PRACH resources, thus preventing excessive degradation of random access capacity.

[0060] In a seventeenth aspect, embodiments of this application provide a method for accessing a network device. The method includes: the network device determining first information, the first information indicating whether a REDCAP terminal is allowed to access the network device, the REDCAP terminal including a first type of REDCAP terminal and a second type of REDCAP terminal, or the REDCAP terminal including a third type of REDCAP terminal, the first type of REDCAP terminal and the second type of REDCAP terminal operating in the same frequency domain range, the third type of REDCAP terminal operating in a different frequency domain range than the first type of REDCAP terminal and the second type of REDCAP terminal; the second type of REDCAP terminal having a smaller bandwidth than the first type of REDCAP terminal, and / or the second type of REDCAP terminal having a smaller number of receiving antennas than the first type of REDCAP terminal; and the network device sending the first information to the terminal device.

[0061] The method provided in the seventeenth aspect above allows a network device to determine first information indicating whether to allow a first type of REDCAP terminal to access the network device and whether to allow a second type of REDCAP terminal to access the network device, or to determine first information indicating whether to allow a third type of REDCAP terminal to access the network device, and to send the first information to the terminal device. In this way, the network device can control the number of first type REDCAP terminals and second type REDCAP terminals accessing the network device to ensure the transmission performance of the network managed by the network device.

[0062] One possible implementation is that the REDCAP terminal includes a first type of REDCAP terminal and a second type of REDCAP terminal; the first information includes first indication information and second indication information; wherein, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device; or, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the first and second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the network device. Based on the above method, the first indication information and the second indication information can respectively indicate whether the first type of REDCAP terminal is allowed to access the network device and whether the second type of REDCAP terminal is allowed to access the network. The first indication information and the second indication information can also jointly indicate whether the first type of REDCAP terminal is allowed to access the network device and whether the second type of REDCAP terminal is allowed to access the network, providing flexibility in the indication method.

[0063] One possible implementation is that the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device. The first indication information includes a free field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload. Alternatively, the first indication information includes a "prohibit access" field in the MIB, and the second indication information includes a free field in the MIB, or includes a reserved field in the additional PBCH payload. Based on the above method, the first and second indication information can respectively indicate whether the first type of REDCAP terminal is allowed to access the network device, providing clear and convenient indication.

[0064] One possible implementation is that the first indication information is used to indicate whether a first type of REDCAP terminal is allowed to access the network device, and the first and second indication information are used to indicate whether a second type of REDCAP terminal is allowed to access the network device. The first indication information includes empty fields in the MIB, and the second indication information includes reserved fields in the additional PBCH payload. Based on the above method, whether a first type of REDCAP terminal is allowed to access the network device will affect whether a second type of REDCAP terminal is allowed to access the network device. Therefore, the priority of first and second type REDCAP terminals accessing the network device can be distinguished to ensure that higher-priority terminal types are given priority access to the network device.

[0065] One possible implementation is that the first indication information is included in a reserved field of the DCI, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in a reserved field of the DCI, and the second indication information is included in the SIB1 information block; or, the first indication information is included in the SIB1 information block, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in the SIB1 information block, and the second indication information is included in the SIB1 information block; wherein, the DCI is used for scheduling SIB1. Based on the above method, the network device can indicate whether to allow the REDCAP terminal to access the network device through the reserved field in the DCI and / or the SIB1 information block.

[0066] One possible implementation is that the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "prohibit access" field in the MIB; the second indication information is included in a reserved field in the DCI, or the second indication information is included in the SIB1 information block; or the first indication information is included in a reserved field in the DCI, or the first indication information is included in the SIB1 information block, and the second indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "prohibit access" field in the MIB, wherein the DCI is used to schedule SIB1. Based on the above method, the network device can indicate whether to allow the REDCAP terminal to access the network device through the reserved fields in the SSB and DCI, or the network device can indicate whether to allow the REDCAP terminal to access the network device through the SSB and SIB1 information block.

[0067] One possible implementation is that the REDCAP terminal includes the third type of REDCAP terminal; the first information includes third indication information; wherein the third indication information is used to indicate whether the third type of REDCAP terminal is allowed to access the network device. Based on the above method, the network device can indicate whether the third type of REDCAP terminal is allowed to access the network device through the third indication information.

[0068] One possible implementation is that the third indication information includes a blank field in the MIB; or, the third indication information includes a "Do Not Access Denied" field in the MIB. Based on the above methods, the network device can indicate whether to allow the third type REDCAP terminal to access the network device through a blank field in the MIB or the "Do Not Access Denied" field of the MIB terminal, providing a flexible indication method.

[0069] One possible implementation is that the first information is included in the SSB, which includes the MIB and an additional PBCH payload. Based on the above method, the network device can indicate whether to allow a REDCAP terminal to access the network device via the MIB and the additional PBCH payload in the SSB.

[0070] One possible implementation is that the third indication information is included in a reserved field of the DCI; or, the third indication information is included in the SIB1 information block. Based on the above methods, the network device can indicate whether a third-type REDCAP terminal is allowed to access the network device through a reserved field in the DCI, or it can indicate whether a third-type REDCAP terminal is allowed to access the network device through the SIB1 information block, providing flexibility in the indication method.

[0071] One possible implementation is that the first information indicates that the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal is allowed to access the network device; or, the first information indicates that both the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device. The method further includes: the network device receiving second information from the terminal device, the second information indicating that the terminal device is the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal. Based on the above method, the network device can receive second information from the terminal device and determine whether the terminal device is the first type of REDCAP terminal or the second type of REDCAP terminal through the second information. On the one hand, this avoids the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the maximum bandwidth of the REDCAP terminals. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmission.

[0072] One possible implementation is that the second information is carried in a PRACH, and the resources of the PRACH correspond to the first type of REDCAP terminal, the second type of REDCAP terminal, or the third type of REDCAP terminal. The PRACH resources include at least one of the time-domain resources, the frequency-domain resources, or the code-domain resources of the PRACH. Alternatively, the second information is carried in Msg3, MsgA, or RRC signaling. Based on the above methods, network devices can determine the type of terminal device through various methods such as PRACH resources, Msg3, MsgA, or RRC signaling.

[0073] One possible implementation is that the first information indicates that both the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device; the method further includes: the network device receiving second information from the terminal device, the second information indicating that the terminal device belongs to the REDCAP terminal category; the network device receiving third information from the network device, the third information indicating that the terminal device is either the first type of REDCAP terminal or the second type of REDCAP terminal. Based on the above method, the network device can determine whether the terminal device is the first type of REDCAP terminal or the second type of REDCAP terminal through the second and third information. On the one hand, this avoids the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the maximum bandwidth of the REDCAP terminals. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmission.

[0074] In one possible implementation, the second information is carried in a PRACH, the resources of which correspond to the REDCAP terminal. The PRACH resources include at least one of the time-domain resources, frequency-domain resources, or code-domain resources of the PRACH; the third information is carried in Msg3, MsgA, or RRC signaling. Based on the above method, the network device can determine the type of terminal device by combining the PRACH resources and the Msg3, MsgA, or RRC signaling.

[0075] Eighteenthly, embodiments of this application provide a communication device, the communication device comprising: a receiving module and a processing module; the receiving module being configured to receive first information from a network device, the first information being used to indicate whether a REDCAP terminal is allowed to access the network device, the REDCAP terminal including a first type REDCAP terminal and a second type REDCAP terminal, or the REDCAP terminal including a third type REDCAP terminal, the first type REDCAP terminal and the second type REDCAP terminal operating in the same frequency domain range, the third type REDCAP terminal operating in a different frequency domain range than the first type REDCAP terminal and the second type REDCAP terminal; the second type REDCAP terminal having a smaller bandwidth than the first type REDCAP terminal, and / or the second type REDCAP terminal having a smaller number of receiving antennas than the first type REDCAP terminal; the processing module being configured to determine whether to access the network device based on the first information, wherein the communication device is the first type REDCAP terminal, or the second type REDCAP terminal, or the third type REDCAP terminal.

[0076] One possible implementation is that the REDCAP terminal includes the first type of REDCAP terminal and the second type of REDCAP terminal; the first information includes first indication information and second indication information; wherein the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device; or, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the network device.

[0077] One possible implementation is that the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device; the first indication information includes a free field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload; or, the first indication information includes a whether access is prohibited field in the MIB, and the second indication information includes a free field in the MIB, or includes a reserved field in the additional PBCH payload.

[0078] In one possible implementation, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the network device; the first indication information includes a spare field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload.

[0079] One possible implementation is that the first indication information is included in a reserved field of the DCI, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in a reserved field of the DCI, and the second indication information is included in the SIB1 information block; or, the first indication information is included in the SIB1 information block, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in the SIB1 information block, and the second indication information is included in the SIB1 information block; wherein the DCI is used to schedule SIB1.

[0080] One possible implementation is that the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "disable access" field in the MIB, and the second indication information is included in a reserved field in the DCI, or the second indication information is included in the SIB1 information block; or; the first indication information is included in a reserved field in the DCI, or the first indication information is included in the SIB1 information block, and the second indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "disable access" field in the MIB, wherein the DCI is used to schedule SIB1.

[0081] One possible implementation is that the REDCAP terminal includes the third type of REDCAP terminal; the first information includes third indication information; wherein the third indication information is used to indicate whether the third type of REDCAP terminal is allowed to access the network device.

[0082] One possible implementation is that the third indication information includes a blank field in the MIB; or, the third indication information includes a field in the MIB indicating whether access is prohibited.

[0083] One possible implementation is that the first information is included in the SSB, which includes the MIB and the additional PBCH payload.

[0084] One possible implementation is that the third indication information is included in a reserved field of the DCI; or, the third indication information is included in the SIB1 information block.

[0085] In one possible implementation, the first information indicates that the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal is allowed to access the network device; or, the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device. The communication device further includes: a sending module; the sending module is configured to send second information to the network device, the second information being used to indicate that the communication device is the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal.

[0086] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, the frequency domain resources, or the code domain resources of the PRACH; or, the second information is carried in Msg3, MsgA, or RRC signaling.

[0087] In one possible implementation, the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device; the sending module is further configured to send second information to the network device, the second information being used to indicate that the communication device belongs to the REDCAP terminal; the sending module is further configured to send third information to the network device, the third information being used to indicate that the communication device is the first type of REDCAP terminal or the second type of REDCAP terminal.

[0088] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH; the third information is carried in Msg3, MsgA, or RRC signaling.

[0089] Nineteenthly, embodiments of this application provide a communication device, the communication device comprising: a processing module and a transmitting module; the processing module is configured to determine first information, the first information being used to indicate whether a REDCAP terminal is allowed to access the communication device, the REDCAP terminal including a first type REDCAP terminal and a second type REDCAP terminal, or the REDCAP terminal including a third type REDCAP terminal, the first type REDCAP terminal and the second type REDCAP terminal operating in the same frequency domain range, the third type REDCAP terminal operating in a different frequency domain range than the first type REDCAP terminal and the second type REDCAP terminal; the second type REDCAP terminal having a smaller bandwidth than the first type REDCAP terminal, and / or the second type REDCAP terminal having a smaller number of receiving antennas than the first type REDCAP terminal; the transmitting module is configured to transmit the first information to the terminal device.

[0090] One possible implementation is that the REDCAP terminal includes the first type of REDCAP terminal and the second type of REDCAP terminal; the first information includes first indication information and second indication information; wherein the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the communication device; or, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the communication device.

[0091] One possible implementation is that the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the communication device; the first indication information includes a free field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload; or, the first indication information includes a whether access is prohibited field in the MIB, and the second indication information includes a free field in the MIB, or includes a reserved field in the additional PBCH payload.

[0092] In one possible implementation, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the communication device; the first indication information includes a spare field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload.

[0093] One possible implementation is that the first indication information is included in a reserved field of the DCI, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in a reserved field of the DCI, and the second indication information is included in the SIB1 information block; or, the first indication information is included in the SIB1 information block, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in the SIB1 information block, and the second indication information is included in the SIB1 information block; wherein the DCI is used to schedule SIB1.

[0094] One possible implementation is that the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "disable access" field in the MIB, and the second indication information is included in a reserved field in the DCI, or the second indication information is included in the SIB1 information block; or; the first indication information is included in a reserved field in the DCI, or the first indication information is included in the SIB1 information block, and the second indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "disable access" field in the MIB, wherein the DCI is used to schedule SIB1.

[0095] One possible implementation is that the REDCAP terminal includes the third type of REDCAP terminal; the first information includes third indication information; wherein the third indication information is used to indicate whether the third type of REDCAP terminal is allowed to access the communication device.

[0096] One possible implementation is that the third indication information includes a blank field in the MIB; or, the third indication information includes a field in the MIB indicating whether access is prohibited.

[0097] One possible implementation is that the first information is included in the SSB, which includes the MIB and the additional PBCH payload.

[0098] One possible implementation is that the third indication information is included in a reserved field of the DCI; or, the third indication information is included in the SIB1 information block.

[0099] One possible implementation is that the first information indicates that the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal is allowed to access the communication device; or, the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the communication device, and the communication device further includes: a receiving module; the receiving module is configured to receive second information from the terminal device, the second information being used to indicate that the terminal device is the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal.

[0100] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, the frequency domain resources, or the code domain resources of the PRACH; or, the second information is carried in Msg3, MsgA, or RRC signaling.

[0101] In one possible implementation, the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the communication device; the receiving module is further configured to receive second information from the terminal device, the second information being used to indicate that the terminal device belongs to the REDCAP terminal; the receiving module is further configured to receive third information from the communication device, the third information being used to indicate that the terminal device is the first type of REDCAP terminal or the second type of REDCAP terminal.

[0102] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH; the third information is carried in Msg3, MsgA, or RRC signaling.

[0103] In a twentieth aspect, embodiments of this application provide a communication device, comprising: a processor coupled to a memory for storing programs or instructions, wherein when the programs or instructions are executed by the processor, the device implements the method described in the sixteenth aspect or any possible implementation thereof.

[0104] In a twentieth aspect, embodiments of this application provide a communication device, comprising: a processor coupled to a memory for storing programs or instructions, wherein when the programs or instructions are executed by the processor, the device enables the method described in the seventeenth aspect or any possible implementation thereof.

[0105] In a twentieth aspect, embodiments of this application provide a communication device for implementing the method described in the sixteenth aspect or any possible implementation thereof.

[0106] In a twentieth aspect, embodiments of this application provide a communication device for implementing the method described in the seventeenth aspect or any possible implementation thereof.

[0107] In a twentieth aspect, embodiments of this application provide a computer-readable medium having a computer program or instructions stored thereon, which, when executed, cause a computer to perform the method described in the sixteenth aspect or any possible implementation thereof.

[0108] In a twentieth aspect, embodiments of this application provide a computer-readable medium having a computer program or instructions stored thereon, which, when executed, cause a computer to perform the method described in the seventeenth aspect or any possible implementation thereof.

[0109] In a twentieth aspect, embodiments of this application provide a computer program product comprising computer program code, which, when executed on a computer, causes the computer to perform the methods described in the sixteenth aspect or any possible implementation thereof.

[0110] In a twentieth aspect, embodiments of this application provide a computer program product comprising computer program code, which, when executed on a computer, causes the computer to perform the method described in the seventeenth aspect or any possible implementation thereof.

[0111] In a twentieth aspect, an embodiment of this application provides a chip, comprising: a processor coupled to a memory, the memory being used to store programs or instructions, wherein when the program or instructions are executed by the processor, the chip causes the chip to implement the method described in the sixteenth aspect above, or any possible implementation thereof.

[0112] In a twentieth aspect, an embodiment of this application provides a chip, comprising: a processor coupled to a memory, the memory being used to store programs or instructions, wherein when the program or instructions are executed by the processor, the chip causes the chip to implement the method described in the seventeenth aspect above, or any possible implementation thereof.

[0113] In a thirtieth aspect, embodiments of this application provide a communication system. This system includes the apparatus described in the eighteenth aspect and / or the apparatus described in the nineteenth aspect, or the system includes the apparatus described in the twentieth aspect and / or the apparatus described in the twenty-first aspect, or the system includes the apparatus described in the twenty-second aspect and / or the apparatus described in the twenty-third aspect.

[0114] It is understood that any of the communication devices, chips, computer-readable media, computer program products or communication systems provided above are used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here. Attached Figure Description

[0115] Figure 1 This is a schematic diagram of the communication system architecture provided in the embodiments of this application;

[0116] Figure 2 This is a schematic diagram of the hardware structure of the communication device provided in the embodiments of this application;

[0117] Figure 3 A flowchart illustrating the method for accessing a network device provided in this application embodiment. Figure 1 ;

[0118] Figure 4 A flowchart illustrating the method for accessing a network device provided in this application embodiment. Figure 2 ;

[0119] Figure 5 A flowchart illustrating the method for accessing a network device provided in this application embodiment. Figure 3 ;

[0120] Figure 6 A flowchart illustrating the method for accessing a network device provided in this application embodiment. Figure 4 ;

[0121] Figure 7 A flowchart illustrating the method for accessing a network device provided in this application embodiment. Figure 5 ;

[0122] Figure 8 A flowchart illustrating the method for accessing a network device provided in this application embodiment. Figure 6 ;

[0123] Figure 9 Schematic diagram of the communication device provided in the embodiments of this application Figure 1 ;

[0124] Figure 10 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 ;

[0125] Figure 11 Schematic diagram of the communication device provided in the embodiments of this application Figure 3 ;

[0126] Figure 12 Schematic diagram of the communication device provided in the embodiments of this application Figure 4 ;

[0127] Figure 13 This is a schematic diagram of the chip structure provided in an embodiment of this application;

[0128] Figure 14 This is a schematic diagram of the composition of a communication system provided in an embodiment of this application. Detailed Implementation

[0129] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0130] The method provided in this application can be used in various communication systems. For example, the communication system can be a 5th generation (5G) communication system, a new radio (NR) system, a 3rd generation partnership project (3GPP) related communication system, and future evolution communication systems, etc., without limitation. The following only uses... Figure 1 Taking the communication system 10 shown as an example, the method provided in the embodiments of this application will be described.

[0131] like Figure 1 The diagram shown is a schematic diagram of the architecture of the communication system 10 provided in an embodiment of this application. Figure 1 In this context, the communication system 10 may include one or more network devices 101 (only one is shown) and terminal devices 102-104 that can communicate with the network devices 101. Figure 1 This is merely an illustrative diagram and does not constitute a limitation on the applicable scenarios of the technical solutions provided in this application.

[0132] exist Figure 1 In a network interface, network devices provide wireless access services to terminal devices. Specifically, each network device corresponds to a service coverage area. Terminal devices entering this area can communicate with the network device via the Uu port to receive the wireless access services provided by the network device. Communication between the terminal device and the network device can be achieved through a Uu port link. The Uu port link can be divided into uplink (UL) and downlink (DL) based on the direction of data transmission. UL transmits uplink data from the terminal device to the network device, while DL transmits downlink data from the network device to the terminal device. For example: Figure 1 In this system, terminal device 103 is located within the coverage area of ​​network device 101. Network device 101 can send downlink data to terminal device 103 via DL, and terminal device 103 can send uplink data to network device 101 via UL.

[0133] Figure 1The network devices in the diagram, such as network device 101, can be any device with wireless transceiver capabilities. These include, but are not limited to, base stations (gNodeB or gNB) or transmission receiving points (TRPs) in NR, and base stations evolved from 3GPP. Base stations can be macro base stations, micro base stations, pico base stations, small cells, relay stations, or balloon stations. Multiple base stations can support networks using the same technology mentioned above, or networks using different technologies. A base station can contain one or more co-located or non-co-located TRPs. Network devices can also be radio controllers, centralized units (CUs), and / or distributed units (DUs) in cloud radio access network (CRAN) scenarios. Network devices can also be servers, wearable devices, machine communication devices, or vehicle-mounted devices. The following explanation uses a base station as an example. The multiple network devices can be base stations of the same type or different types. A base station can communicate with a terminal device, or it can communicate with a terminal device through a relay station.

[0134] Figure 1The terminal devices, such as terminal 102, terminal 103, or terminal 104, are devices with wireless transceiver capabilities. They can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; they can also be deployed on water (such as on ships); and they can be deployed in the air (such as on airplanes, balloons, and satellites). These terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, terminals in industrial control, vehicle-mounted terminals, terminals in self-driving cars, terminals in assisted driving, terminals in remote medical care, terminals in smart grids, terminals in transportation safety, terminals in smart cities, terminals in smart homes, etc. The embodiments in this application do not limit the application scenarios. Terminal devices are sometimes also referred to as terminal equipment, user equipment (UE), access terminals, vehicle-mounted terminals, industrial control terminals, UE units, UE stations, mobile stations, mobile terminals, remote stations, remote terminals, mobile devices, UE terminal equipment, wireless communication equipment, machine terminals, UE agents, or UE devices, etc. Terminal devices can be fixed or mobile.

[0135] By way of example and not limitation, the terminal device in this application can be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0136] In this application, the terminal device can be a terminal in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and machine-to-machine interconnection. The terminal device in this application can be a terminal in machine-type communication (MTC). The terminal device in this application can be an on-board module, on-board component, on-board chip, or on-board unit built into a vehicle as one or more components or units. The vehicle can implement the methods of this application through the built-in on-board module, on-board component, on-board chip, or on-board unit.

[0137] Figure 1 In the communication system 10 shown, network device 101 broadcasts SSBs. SSBs include the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcasting channel (PBCH). PBCH includes the master information block (MIB) and additional PBCH payload (or additional timing-related PBCH payload). A description of PSS and SSS can be found in conventional technical explanations and will not be repeated here.

[0138] The MIB includes at least one of the following information: system frame number (SFN), subcarrier spacing (subCarrierSpacingCommon), SSB subcarrier offset (ssb-SubcarrierOffset), demodulation reference signal (DMRS) symbol position in a time slot (dmrs-TypeA-Position), configuration information of control resource set (CORESET)#0 and Type 0 common search space (pdcch-ConfigSIB1), whether access is prohibited (cellBarred) field, whether intraFreqReselection is allowed field, or a spare field. The descriptions of SFN, subcarrier spacing, SSB subcarrier offset, DMRS symbol position in a time slot, configuration information of CORESET#0 and Type 0 common search space, whether access is prohibited field, whether intraFreqReselection is allowed field, and spare field can be found in conventional technical explanations and will not be elaborated upon here.

[0139] The additional PBCH payload includes information in the PBCH other than the MIB. For example, taking the frequency range of the communication system 10 as frequency range 1 (FR1), i.e., the frequency at which the communication system 10 operates is less than 6 GHz, the additional PBCH payload includes at least one of the following: SFN supplementary field, half-frame indicator field, most significant bit (MSB) indicator field of SSB subcarrier offset, or a reserved field. The descriptions of the SFN supplementary field, half-frame indicator field, MSB bit indicator field of SSB subcarrier offset, and reserved field can be found in conventional technical explanations and will not be repeated here.

[0140] For example, taking the frequency range of the communication system 10 as frequency range 2 (FR2), i.e., the frequency at which the communication system 10 operates is greater than or equal to 6 GHz, the additional PBCH payload includes at least one of the following: SFN supplementary field, half-frame indicator field, or 3MSB bit indicator field of SSB index. The descriptions of the SFN supplementary field, half-frame indicator field, and 3MSB bit indicator field of SSB index can be found in the explanations in conventional techniques and will not be repeated here.

[0141] If a terminal device, such as terminal device 102, terminal device 103, or terminal device 104, wants to access network device 101, the terminal device will receive an SSB (Service Subsystem Block). Based on the PBCH (Power Buffer Channel) in the SSB, it will receive downlink control information (DCI). The DCI is used to schedule System Information Block Type 1 (SIB1), and SIB1 includes an SIB1 information block. After receiving the DCI, the terminal device can receive SIB1 based on the DCI and obtain the random access channel (RACH) configuration information from the SIB1 information block. The RACH configuration information includes random access-related parameters, such as the time-domain resources of the random access preamble and / or the frequency-domain resources of the preamble. Subsequently, the terminal device can initiate a random access procedure to access network device 101.

[0142] For example, a terminal device can access network device 101 via either a four-step RACH or a two-step RACH. The following description uses a terminal device 102 initiating a random access procedure as an example.

[0143] (1) 4-step RACH method. The process of terminal device 102 accessing network device 101 via 4-step RACH method may include the following steps 1-4.

[0144] Step 1: Terminal device 102 sends a random access request to network device 101.

[0145] Sending a random access request is manifested as sending a random access preamble. This random access request is also known as the first message or message 1 (Msg1) in the random access process.

[0146] Step 2: After detecting the random access request sent by the terminal device 102, the network device 101 sends a random access response (RAR) to the terminal device 102.

[0147] The random access response is also known as the second message or message 2 (Msg2) in the random access process.

[0148] Step 3: Terminal device 102 receives RAR from network device 101 and sends uplink data to network device 101.

[0149] This uplink data is also known as the third message or message 3 (Msg3) in the random access procedure. In one scenario, Msg3 includes control plane data (CP data), such as radio resource control (RRC) information. For example, RRC information may include an RRC connection establishment request or an RRC connection resume request. In another scenario, Msg3 includes both control plane data and user plane data.

[0150] Step 4: Network device 101 receives uplink data from terminal device 102 and sends a contention resolution message to terminal device 102.

[0151] Correspondingly, terminal device 102 receives a contention resolution message from network device 101.

[0152] Among them, the contention resolution message is also known as the fourth message or message 4 (Msg4) in the random access procedure.

[0153] (2) 2-step RACH method. The process of terminal device 102 accessing network device 101 via 2-step RACH method may include the following steps a-b.

[0154] Step a: Terminal device 102 sends message A (MsgA) to network device 101.

[0155] MsgA includes a random access preamble and a physical uplink shared channel (PUSCH). In step a, MsgA is equivalent to Msg1 in step 1 and Msg3 in step 3 above, which can also be understood as sending Msg1 and Msg3 "together".

[0156] Step b: Network device 101 receives MsgA from terminal device 102 and sends message B (MsgB) to terminal device 102.

[0157] Correspondingly, terminal device 102 receives message B (MsgB) from network device 101.

[0158] MsgB includes at least one of a response message for the preamble and a response message for uplink data. In other words, MsgB includes at least one of RAR and contention resolution messages. Understandably, if MsgB does not include a contention resolution message, the aforementioned 2-step RACH method would be transformed into a 4-step RACH method.

[0159] Understandable. Figure 1 Terminal devices in this context can be categorized into different types based on their requirements. For example, according to bandwidth or the number of receiving antennas, terminal devices can be divided into REDCAP terminals and ordinary terminals. REDCAP terminals have a smaller bandwidth than ordinary terminals, and / or, the number of receiving antennas is less than that of ordinary terminals. For instance, an ordinary terminal may have a bandwidth of up to 100MHz, while a REDCAP terminal has a bandwidth less than 100MHz; similarly, an ordinary terminal may have up to four receiving antennas, while a REDCAP terminal may only have two or one. Therefore, REDCAP terminals can be used in scenarios with low bandwidth requirements, such as industrial sensors, video surveillance, or wearable devices.

[0160] Furthermore, REDCAP terminals can be classified according to bandwidth or the number of receiving antennas.

[0161] For example, taking the operating frequency range of communication system 10 as FR1, the REDCAP terminal may include a first type of REDCAP terminal and a second type of REDCAP terminal. The bandwidth of the second type of REDCAP terminal is less than that of the first type of REDCAP terminal. For example, the bandwidth of the first type of REDCAP terminal is greater than 10MHz and less than or equal to 20MHz. The bandwidth of the second type of REDCAP terminal is greater than 0MHz and less than or equal to 10MHz. Alternatively, the number of receiving antennas of the second type of REDCAP terminal is less than that of the first type of REDCAP terminal. For example, the first type of REDCAP terminal has two receiving antennas, and the second type of REDCAP terminal has one receiving antenna. Or, the bandwidth of the second type of REDCAP terminal is less than that of the first type of REDCAP terminal, and the number of receiving antennas of the second type of REDCAP terminal is less than that of the first type of REDCAP terminal. For example, the bandwidth of the first type of REDCAP terminal is greater than 10MHz and less than or equal to 20MHz, and the first type of REDCAP terminal has two receiving antennas. The bandwidth of the second type of REDCAP terminal is greater than 0MHz and less than or equal to 10MHz, and the second type of REDCAP terminal has one receiving antenna.

[0162] For example, taking the frequency domain range of the communication system 10 as FR2, the REDCAP terminal may include a third type of REDCAP terminal. The bandwidth of the third type of REDCAP terminal is greater than or equal to 50MHz.

[0163] It is understood that the first type of REDCAP terminal, the second type of REDCAP terminal, and the third type of REDCAP terminal in the embodiments of this application are merely examples of names for different types of terminal devices. In actual applications, the first type of REDCAP terminal, the second type of REDCAP terminal, and the third type of REDCAP terminal can also be named in other ways without limitation.

[0164] Understandably, before initiating a random access procedure, a terminal device must determine whether it is allowed to access the network device based on the network device's instructions. For the aforementioned ordinary terminals, the network device can indicate whether to allow ordinary terminals to access the network device through the "Access Denied" field (i.e., the "cellBarred" field) in the MIB. However, for the aforementioned Type I, Type II, and Type III REDCAP terminals, there is currently no method that allows the network device to control the access of Type I, Type II, and Type III REDCAP terminals.

[0165] To address the aforementioned problems, embodiments of this application provide a method for accessing a network device, which can control the number of REDCAP terminals accessing the network device. The method includes: a terminal device receiving first information from the network device indicating whether to allow a REDCAP terminal to access the network device, and determining whether to access the network device based on the first information. Specifically, please refer to the following... Figures 3-8 As described in [the text].

[0166] Figure 1 The communication system 10 shown is for illustrative purposes only and is not intended to limit the technical solutions of this application. Those skilled in the art should understand that in specific implementations, the communication system 10 may also include other devices, and the number of network devices and terminals can be determined according to specific needs without limitation.

[0167] Optionally, embodiments of this application Figure 1 Each network element, such as network device 101, terminal device 102, terminal device 103, or terminal device 104, can be a functional module within a device. It is understood that the functional module can be a component in a hardware device, such as a communication chip or communication component in a terminal device or network device, or a software functional module running on hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform).

[0168] For example, Figure 1Each network element in the network can be accessed through Figure 2 This is achieved through the communication device 200. Figure 2 The diagram shows a hardware structure of a communication device applicable to embodiments of this application. The communication device 200 includes at least one processor 201, a communication line 202, a memory 203, and at least one communication interface 204.

[0169] The processor 201 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0170] Communication line 202 may include a path for transmitting information between the aforementioned components, such as a bus.

[0171] Communication interface 204 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet interface, radio access network (RAN) interface, wireless local area network (WLAN) interface, etc.

[0172] The memory 203 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via communication line 202. The memory may also be integrated with the processor. The memory provided in this application embodiment is generally non-volatile. The memory 203 is used to store computer execution instructions involved in the scheme of this application and is controlled by the processor 201 for execution. The processor 201 is used to execute computer execution instructions stored in the memory 203, thereby implementing the method provided in the embodiments of this application.

[0173] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0174] In a specific implementation, as one embodiment, the processor 201 may include one or more CPUs, for example... Figure 2 CPU0 and CPU1 in the CPU.

[0175] In a specific implementation, as one example, the communication device 200 may include multiple processors, such as... Figure 2 Processors 201 and 207 are described herein. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here may refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0176] In a specific implementation, as one embodiment, the communication device 200 may further include an output device 205 and an input device 206. The output device 205 communicates with the processor 201 and can display information in various ways. For example, the output device 205 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 206 communicates with the processor 201 and can receive user input in various ways. For example, the input device 206 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0177] The aforementioned communication device 200 can be a general-purpose device or a dedicated device. In specific implementations, the communication device 200 can be a desktop computer, laptop computer, network server, PDA (personal digital assistant), mobile phone, tablet computer, wireless terminal device, embedded device, or other similar device. Figure 2 Devices with similar structures. This application does not limit the type of communication device 200 to any particular embodiment.

[0178] The following is combined with Figure 1 and Figure 2 The method for accessing network devices provided in the embodiments of this application will be described in detail.

[0179] It should be noted that the message names between network elements or the names of parameters in the messages in the following embodiments of this application are just examples. Other names may be used in the specific implementation. This application does not limit them in this respect.

[0180] It should be noted that in the description of this application, terms such as "first" or "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order. Information such as "first information" in this application, which has different numbers, is used only for the convenience of the context. The different order numbers themselves do not have specific technical meanings. For example, "first information," "second information," etc., can be understood as one or any one of a series of information.

[0181] It should be noted that in the following embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the following embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0182] It is understood that the same step or a step or message with the same function in the embodiments of this application can be referenced and learned from each other in different embodiments.

[0183] It is understood that in the embodiments of this application, network devices and / or terminal devices may perform some or all of the steps in the embodiments of this application. These steps are merely examples, and the embodiments of this application may also perform other steps or variations thereof. Furthermore, the steps may be performed in different orders as presented in the embodiments of this application, and it is not necessary to perform all the steps in the embodiments of this application.

[0184] In this application embodiment, the specific structure of the execution subject of the method for accessing a network device is not particularly limited. As long as communication can be performed according to the method for accessing a network device by running a program that records the code of the method for accessing a network device according to this application embodiment, for example, the execution subject of the method for accessing a network device provided in this application embodiment can be a network device, or a component applied in a network device, such as a chip; this application does not limit this. Alternatively, the execution subject of the method for accessing a network device provided in this application embodiment can be a terminal device, or a component applied in a terminal device, such as a chip; this application does not limit this. The following embodiments describe the method for accessing a network device using network devices and terminal devices as examples.

[0185] like Figure 3 As shown, this application provides a method for accessing a network device, which includes steps 301-303.

[0186] Step 301: The network device determines the first information.

[0187] Among them, network devices can be Figure 1 Network device 101.

[0188] The first piece of information can be used to indicate whether a REDCAP terminal is allowed to access the network device. REDCAP terminals include Type I REDCAP terminals and Type II REDCAP terminals. Type I and Type II REDCAP terminals operate in the same frequency range. For example, if the operating frequency range of both Type I and Type II REDCAP terminals is less than 6 GHz, this range is denoted as FR1. For an introduction to Type I and Type II REDCAP terminals when the operating frequency range is FR1, please refer to the above. Figure 1 As described in [the text].

[0189] One possible implementation is that the first information includes first indication information and second indication information. The first indication information and the second indication information can respectively indicate whether a first type of REDCAP terminal is allowed to access the network device, and whether a second type of REDCAP terminal is allowed to access the network. The first indication information and the second indication information can also jointly indicate whether a first type of REDCAP terminal is allowed to access the network device, and whether a second type of REDCAP terminal is allowed to access the network. For example, the first indication information and the second indication information can indicate whether a first type of REDCAP terminal is allowed to access the network device, and whether a second type of REDCAP terminal is allowed to access the network, in the following manner.

[0190] Method 1: The first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device.

[0191] Understandably, in this situation, the network device can use the first instruction information and the second instruction information to indicate whether to allow the first type of REDCAP terminal to access the network device and whether to allow the second type of REDCAP terminal to access the network, respectively. The instructions are clear and very convenient.

[0192] For method 1, there are 6 possible scenarios:

[0193] Case 1.1: The first piece of information is included in the SSB. For an introduction to the SSB, please refer to the above. Figure 1 The description in the text.

[0194] One possible implementation is that the first indication information includes empty fields in the MIB. The second indication information includes reserved fields in the additional PBCH payload.

[0195] For example, the first indication information indicates whether a Type 1 REDCAP terminal is allowed to access the network device via a 1-bit field in the MIB. For instance, if the value of the 1-bit is 1, the first indication information indicates that a Type 1 REDCAP terminal is allowed to access the network device; if the value of the 1-bit is 0, the first indication information indicates that a Type 1 REDCAP terminal is not allowed to access the network device, and vice versa.

[0196] For example, the second indication information indicates whether a Type 2 REDCAP terminal is allowed to access the network device via a 1-bit reserved field in the additional PBCH payload. For instance, if the value of this 1-bit is 1, the second indication information indicates that a Type 2 REDCAP terminal is allowed to access the network device; if the value of this 1-bit is 0, the second indication information indicates that a Type 2 REDCAP terminal is not allowed to access the network device, and vice versa. It can be understood that this 1-bit can be either a high-order bit or a low-order bit in the reserved field, without limitation.

[0197] Another possible implementation is that the first indication information includes a field in the MIB indicating whether access is prohibited, and the second indication information includes a blank field in the MIB or a reserved field in the additional PBCH payload.

[0198] Understandably, the bandwidth of Type I REDCAP terminals is similar to that of ordinary terminals, and both can share CORESET#0, exhibiting good compatibility. Furthermore, the presence of Type I REDCAP terminals has a relatively small impact on network performance. Therefore, Type I REDCAP terminals can reuse the field indicating whether network access is permitted from ordinary terminals. In other words, the "prohibit access" field is used not only to indicate whether ordinary terminals are allowed to access the network device but also to indicate whether Type I REDCAP terminals are allowed to access the network device. However, Type II REDCAP terminals have significantly smaller bandwidth than ordinary terminals. Type II REDCAP terminals may not be able to share CORESET#0 with ordinary terminals, exhibiting poor compatibility. The number of Type II REDCAP terminals has a greater impact on network performance. Therefore, a different field is needed to indicate whether Type II REDCAP terminals are allowed to access the network device, unlike the "prohibit access" field. Additionally, reusing the "prohibit access" field from ordinary terminals for Type I REDCAP terminals saves bits, allowing these saved bits to be used for other purposes, which is beneficial for the backward compatibility expansion of the communication system.

[0199] For example, if the value of the "Do Not Prohibit Access" field is 1, the first indication information indicates that ordinary terminals are allowed to access the network device, and that first-type REDCAP terminals are allowed to access the network device. If the value of the "Do Not Prohibit Access" field is 0, the first indication information indicates that ordinary terminals are not allowed to access the network device, and that first-type REDCAP terminals are not allowed to access the network device, and vice versa.

[0200] For example, the second indication information indicates whether a Type 2 REDCAP terminal is allowed to access the network device via a 1-bit field in the MIB. For instance, if the value of this 1-bit is 1, the second indication information indicates that a Type 2 REDCAP terminal is allowed to access the network device; if the value of this 1-bit is 0, the second indication information indicates that a Type 2 REDCAP terminal is not allowed to access the network device, and vice versa. Alternatively, the second indication information indicates whether a Type 2 REDCAP terminal is allowed to access the network device via a 1-bit field in the additional PBCH payload. For instance, if the value of this 1-bit is 1, the second indication information indicates that a Type 2 REDCAP terminal is allowed to access the network device; if the value of this 1-bit is 0, the second indication information indicates that a Type 2 REDCAP terminal is not allowed to access the network device, and vice versa. It is understood that the 1-bit field can be either a high-order bit or a low-order bit of the reserved field, without limitation.

[0201] Case 1.2: The first information is included in the DCI. This DCI is used to schedule SIB1.

[0202] SIB1 includes the SIB1 information block. For a description of the SIB1 information block, please refer to the explanations in conventional technical documentation.

[0203] One possible implementation is that the first indication information is included in a reserved field of the DCI, and the second indication information is included in a reserved field of the DCI.

[0204] The inclusion of the first and second indication information within the reserved fields of the DCI can be understood as follows: the first indication information includes a first portion of the DCI reserved field, and the second indication information includes a second portion of the DCI reserved field. For example, when the DCI reserved field is 5 bits, the first indication information includes one bit from the 5 bits to indicate whether a Type 1 REDCAP terminal is allowed to access the network device, and the second indication information includes the other bit from the 5 bits to indicate whether a Type 2 REDCAP terminal is allowed to access the network device. Alternatively, a portion of the DCI reserved field can be used to jointly indicate whether access is allowed by both Type 1 and Type 2 REDCAP terminals.

[0205] For example, the first indication information includes 1 bit in the reserved field of the DCI, used to indicate whether a first type of REDCAP terminal is allowed to access the network device. For instance, if the value of this 1 bit is 1, the first indication information indicates that the first type of REDCAP terminal is allowed to access the network device; if the value of this 1 bit is 0, the first indication information indicates that the first type of REDCAP terminal is not allowed to access the network device, and vice versa. The second indication information includes another 1 bit in the reserved field of the DCI, used to indicate whether a second type of REDCAP terminal is allowed to access the network device. For instance, if the value of this 1 bit is 1, the second indication information indicates that the second type of REDCAP terminal is allowed to access the network device; if the value of this 1 bit is 0, the second indication information indicates that the second type of REDCAP terminal is not allowed to access the network device, and vice versa.

[0206] Case 1.3: The first information is included in the SIB1 information block.

[0207] One possible implementation is that the first instruction information is included in the SIB1 information block, and the second instruction information is included in the SIB1 information block.

[0208] The inclusion of first and second indication information within the SIB1 information block can be understood as follows: the first indication information comprises a first portion of the SIB1 information block, and the second indication information comprises a second portion of the SIB1 information block. For example, when the SIB1 information block is 32 bits, the first indication information includes one bit from the 32 bits to indicate whether a Type 1 REDCAP terminal is allowed to access the network device, and the second indication information includes the other bit from the 32 bits to indicate whether a Type 2 REDCAP terminal is allowed to access the network device. Alternatively, a portion of the SIB1 information block can be used to jointly indicate whether access is allowed for both Type 1 and Type 2 REDCAP terminals.

[0209] For example, the first indication information includes 1 bit in the SIB1 information block, used to indicate whether a first type of REDCAP terminal is allowed to access the network device. For instance, if the value of this 1 bit is 1, the first indication information indicates that the first type of REDCAP terminal is allowed to access the network device; if the value of this 1 bit is 0, the first indication information indicates that the first type of REDCAP terminal is not allowed to access the network device, and vice versa. The second indication information includes another 1 bit in the SIB1 information block, used to indicate whether a second type of REDCAP terminal is allowed to access the network device. For instance, if the value of this 1 bit is 1, the second indication information indicates that the second type of REDCAP terminal is allowed to access the network device; if the value of this 1 bit is 0, the second indication information indicates that the second type of REDCAP terminal is not allowed to access the network device, and vice versa.

[0210] Understandably, the 1 bit in the SIB1 information block used to indicate whether a Type 1 REDCAP terminal is allowed to access the network device can be included in a newly added information element (IE) in the SIB1 information block, or it can be included in the original IE in the SIB1 information block. Similarly, the 1 bit in the SIB1 information block used to indicate whether a Type 2 REDCAP terminal is allowed to access the network device can be included in a newly added IE in the SIB1 information block, or it can be included in the original IE in the SIB1 information block.

[0211] Case 1.4: The first information is included in DCI and SIB1.

[0212] One possible implementation is that the first indication information is included in a reserved field of the DCI, and the second indication information is included in the SIB1 information block.

[0213] For example, the first indication information includes 1 bit in the reserved field of the DCI, used to indicate whether a first type of REDCAP terminal is allowed to access the network device. For instance, if the value of this 1 bit is 1, the first indication information indicates that the first type of REDCAP terminal is allowed to access the network device; if the value of this 1 bit is 0, the first indication information indicates that the first type of REDCAP terminal is not allowed to access the network device, and vice versa. The second indication information includes 1 bit in the SIB1 information block, used to indicate whether a second type of REDCAP terminal is allowed to access the network device. For instance, if the value of this 1 bit is 1, the second indication information indicates that the second type of REDCAP terminal is allowed to access the network device; if the value of this 1 bit is 0, the second indication information indicates that the second type of REDCAP terminal is not allowed to access the network device, and vice versa.

[0214] Another possible implementation is that the first indication information is included in the SIB1 information block, and the second indication information is included in the reserved field of the DCI.

[0215] For example, the first indication information includes 1 bit in the SIB1 information block, used to indicate whether a first type of REDCAP terminal is allowed to access the network device. For instance, if the value of this 1 bit is 1, the first indication information indicates that the first type of REDCAP terminal is allowed to access the network device; if the value of this 1 bit is 0, the first indication information indicates that the first type of REDCAP terminal is not allowed to access the network device, and vice versa. The second indication information includes 1 bit in the reserved field of the DCI, used to indicate whether a second type of REDCAP terminal is allowed to access the network device. For instance, if the value of this 1 bit is 1, the second indication information indicates that the second type of REDCAP terminal is allowed to access the network device; if the value of this 1 bit is 0, the second indication information indicates that the second type of REDCAP terminal is not allowed to access the network device, and vice versa.

[0216] Case 1.5: The first information is included in the SSB and DCI.

[0217] One possible implementation is that the first indication information includes a spare field in the MIB, or a reserved field in the additional PBCH payload, or a field in the MIB indicating whether access is prohibited, and the second indication information is included in a reserved field in the DCI.

[0218] The first indication information, including a spare field in the MIB, a reserved field in the additional PBCH payload, or a field indicating whether access is prohibited in the MIB, can be referred to in Case 1.1 above. The second indication information, including a reserved field in the DCI, can be referred to in Case 1.2 above. For example, the first indication information may include a spare field in the MIB, and the second indication information may include a reserved field in the DCI; of course, other configuration combinations are also applicable.

[0219] Another possible implementation is that the first indication information is included in the reserved field of the DCI, and the second indication information includes an empty field in the MIB, a reserved field in the additional PBCH payload, or a field in the MIB indicating whether access is prohibited.

[0220] Where the first indication information is included in a reserved field of the DCI, refer to the above-described case 1.2. Where the second indication information includes a spare field in the MIB, a reserved field in an additional PBCH payload, or a field indicating whether access is prohibited in the MIB, refer to the above-described case 1.1. For example, the first indication information may be included in a reserved field of the DCI, and the second indication information may be included in a spare field of the MIB; of course, other configuration combinations are also applicable.

[0221] Case 1.6: The first information is included in SSB and SIB1.

[0222] One possible implementation is that the first indication information includes a spare field in the MIB, or a reserved field in the additional PBCH payload, or a field in the MIB indicating whether access is prohibited, and the second indication information is included in the SIB1 information block.

[0223] The first indication information, including empty fields in the MIB, reserved fields in the additional PBCH payload, or whether access is prohibited in the MIB, can be referred to in Case 1.1 above. The second indication information in the SIB1 information block can be referred to in Case 1.3 above. For example, the first indication information may include empty fields in the MIB, and the second indication information may be included in the SIB1 information block; of course, other configuration combinations are also applicable.

[0224] Another possible implementation is that the first indication information is included in the SIB1 information block, and the second indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a field in the MIB indicating whether access is prohibited.

[0225] The first indication information within the SIB1 information block can be referenced as described in Case 1.3 above. The second indication information, including empty fields in the MIB, reserved fields in the additional PBCH payload, or a "disable access" field in the MIB, can be referenced as described in Case 1.1 above. For example, the first indication information may be included in the SIB1 information block, and the second indication information may include empty fields in the MIB; other configuration combinations are also applicable.

[0226] Method 2: The first indication information is used to indicate whether a Type 1 REDCAP terminal is allowed to access the network device, and the first and second indication information are used to indicate whether a Type 2 REDCAP terminal is allowed to access the network device. In other words, the first indication information is used to indicate whether REDCAP terminals (including Type 1 and Type 2 REDCAP terminals) are allowed to access the network device. The second indication information is used to indicate whether a Type 2 REDCAP terminal is allowed to access the network device.

[0227] Understandably, if the first instruction indicates that REDCAP terminals are not allowed to access the network device, then neither the first type of REDCAP terminal nor the second type of REDCAP terminal can access the network device. If the first instruction indicates that REDCAP terminals are allowed to access the network device, then the first type of REDCAP terminal can access the network device. In this case, if the second instruction indicates that the second type of REDCAP terminal is allowed to access the network device, then the second type of REDCAP terminal can access the network device; if the second instruction indicates that the second type of REDCAP terminal is not allowed to access the network device, then the second type of REDCAP terminal cannot access the network device.

[0228] Understandably, the bandwidth of Type I REDCAP terminals is similar to that of ordinary terminals, and they can share CORESET#0. Therefore, Type I REDCAP terminals have a smaller impact on the network transmission performance provided by network devices. Consequently, compared to Type II REDCAP terminals, Type I REDCAP terminals have a higher priority for accessing network devices.

[0229] For method 2, there are 6 possible scenarios:

[0230] Case 2.1: The first information is included in the SSB.

[0231] One possible implementation is that the first indication information includes empty fields in the MIB, and the second indication information includes reserved fields in the additional PBCH payload.

[0232] For example, the first indication information indicates whether a Type 1 REDCAP terminal is allowed to access the network device via a 1-bit field in the MIB. For instance, if the value of the 1-bit is 1, the first indication information indicates that a Type 1 REDCAP terminal is allowed to access the network device; if the value of the 1-bit is 0, the first indication information indicates that a Type 1 REDCAP terminal is not allowed to access the network device, and vice versa.

[0233] For example, if the first indication information indicates permission for a first-type REDCAP terminal to access the network device via a 1-bit empty field in the MIB, the second indication information indicates whether permission for a second-type REDCAP terminal to access the network device is granted via a 1-bit reserved field in the additional PBCH payload. For instance, if the first indication information indicates permission for a first-type REDCAP terminal to access the network device via a 1-bit empty field in the MIB, and the value of the 1-bit reserved field is 1, the second indication information indicates permission for a second-type REDCAP terminal to access the network device; if the value of the 1-bit reserved field is 0, the second indication information indicates disallowance for a second-type REDCAP terminal to access the network device, and vice versa. It is understood that the 1-bit reserved field can be either a high-order bit or a low-order bit of the reserved field, without limitation.

[0234] Understandably, in Method 2, if the first indication information indicates that the first type of REDCAP terminal is not allowed to access the network, the second type of REDCAP terminal is also not allowed to access the network device. Therefore, the 1 bit in the reserved field does not need to be used to indicate whether the second type of REDCAP terminal is allowed to access the network device, but can be used for other purposes. For example, the 1 bit in the reserved field can be used to indicate whether the REDCAP terminal can search for the SSB of other cells on the same frequency. In this way, the first information can indicate more information, increasing the flexibility of the first information indication.

[0235] Case 2.2: The first information is included in the DCI.

[0236] The description of Case 2.2 can be found in Case 1.2 above.

[0237] Case 2.3: The first information is included in the SIB1 information block.

[0238] The description of situation 2.3 can be found in situation 1.3 above.

[0239] Case 2.4: The first information is included in DCI and SIB1.

[0240] The description of situation 2.4 can be found in situation 1.4 above.

[0241] Case 2.5: The first information is included in the SSB and DCI.

[0242] The description of Case 2.5 can be found in Case 1.5 above.

[0243] Case 2.6: The first information is included in SSB and SIB1.

[0244] The description of Case 2.6 can be found in Case 1.6 above.

[0245] One possible implementation involves the network device determining the first information based on the transmission performance of the network it manages. For example, if the network's transmission performance is greater than or equal to a threshold, the network device does not limit the number of REDCAP terminals; if the network's transmission performance is less than the threshold, the network device limits the number of REDCAP terminals. Exemplarily, the network's transmission performance may be related to the total number of terminal devices currently served by the network device, or the network's transmission spectrum efficiency, etc. For example, a larger number of terminal devices currently served by the network device compared to a smaller number results in lower network transmission performance. Conversely, a higher transmission spectrum efficiency compared to a lower network transmission spectrum efficiency results in higher network transmission performance.

[0246] Step 302: The network device sends the first information to the terminal device.

[0247] The terminal device is Figure 1 Any one or more terminal devices in the [context]. For example, the terminal device is [the following]. Figure 1 Terminal device 102 in the middle; or, the terminal device is Figure 1 Terminal devices 102 and 103 in the middle.

[0248] Correspondingly, the terminal device receives the first information from the network device.

[0249] Step 303: The terminal device determines whether to access the network device based on the first information.

[0250] The terminal device is either a Type I REDCAP terminal, a Type II REDCAP terminal, or a regular terminal.

[0251] One possible implementation is that, if the terminal device is a regular terminal, the terminal device determines whether to access the network device based on the "Access Denied" field (cellBarred field). For example, if the value of the "Access Denied" field is 1, the terminal device determines to access the network device; if the value of the "Access Denied" field is 0, the terminal device determines not to access the network device, and vice versa.

[0252] One possible implementation is that, if the terminal device is a Type I REDCAP terminal, the terminal device determines whether to access the network device based on the first instruction information.

[0253] For example, taking the first indication information indicating whether a first type of REDCAP terminal is allowed to access the network device through 1 bit in the empty field of the MIB, if the value of the 1 bit is 1, the terminal device determines to access the network device; if the value of the 1 bit is 0, the terminal device determines not to access the network device, and vice versa.

[0254] For example, taking the first indication information indicating whether a first type of REDCAP terminal is allowed to access the network device through the "Do Not Access Deny" field in the MIB as an example, if the value of the "Do Not Access Deny" field is 1, the terminal device determines to access the network device; if the value of the "Do Not Access Deny" field is 0, the terminal device determines not to access the network device, and vice versa.

[0255] For example, taking 1 bit in the reserved field of DCI in the first indication information as an example, which is used to indicate whether a first type of REDCAP terminal is allowed to access the network device, if the value of the 1 bit is 1, the terminal device determines to access the network device; if the value of the 1 bit is 0, the terminal device determines not to access the network device, and vice versa.

[0256] For example, taking the first indication information including 1 bit in the SIB1 information block to indicate whether the first type of REDCAP terminal is allowed to access the network device, if the value of the 1 bit is 1, the terminal device determines to access the network device; if the value of the 1 bit is 0, the terminal device determines not to access the network device, and vice versa.

[0257] One possible implementation is that, for the above method 1, if the terminal device is a second type REDCAP terminal, the terminal device determines whether to access the network device based on the second instruction information.

[0258] For example, taking the second indication information indicating whether a second type of REDCAP terminal is allowed to access the network device through 1 bit in the empty field of the MIB, if the value of the 1 bit is 1, the terminal device determines to access the network device; if the value of the 1 bit is 0, the terminal device determines not to access the network device, and vice versa.

[0259] For example, if the second indication information indicates whether a second type of REDCAP terminal is allowed to access the network device through a reserved field in the additional PBCH payload, the terminal device determines to access the network device if the value of the 1 bit is 1, and determines not to access the network device if the value of the 1 bit is 0, and vice versa.

[0260] For example, taking 1 bit in the reserved field of DCI in the second indication information as an example, which is used to indicate whether a second type REDCAP terminal is allowed to access the network device, if the value of the 1 bit is 1, the terminal device determines to access the network device; if the value of the 1 bit is 0, the terminal device determines not to access the network device, and vice versa.

[0261] For example, taking the second indication information including 1 bit in the SIB1 information block to indicate whether a second type of REDCAP terminal is allowed to access the network device, if the value of the 1 bit is 1, the terminal device determines to access the network device; if the value of the 1 bit is 0, the terminal device determines not to access the network device, and vice versa.

[0262] One possible implementation is that, for the above method 2, if the terminal device is a second type REDCAP terminal, the terminal device determines whether to access the network device based on the first instruction information and the second instruction information.

[0263] For example, taking the first indication information indicating whether a first type of REDCAP terminal is allowed to access the network device and whether a second type of REDCAP terminal is allowed to access the network device through a 1-bit empty field in the MIB, and the second indication information indicating whether a second type of REDCAP terminal is allowed to access the network device through a 1-bit reserved field in the additional PBCH payload, if the value of the 1-bit empty field is 0, the terminal device determines not to access the network device; if the value of the 1-bit empty field and the value of the 1-bit reserved field are both 1, the terminal device determines to access the network device; if the value of the 1-bit empty field and the value of the 1-bit reserved field are both 0, the terminal device determines not to access the network device. Alternatively, if the value of the 1-bit empty field is 1, the terminal device determines not to access the network device; if the value of the 1-bit empty field and the value of the 1-bit reserved field are both 0, the terminal device determines to access the network device; if the value of the 1-bit empty field and the value of the 1-bit reserved field are both 1, the terminal device determines not to access the network device.

[0264] For example, taking the first indication information including 1 bit in the reserved field of DCI to indicate whether a first type of REDCAP terminal is allowed to access the network device and whether a second type of REDCAP terminal is allowed to access the network device, and the second indication information including 1 bit in the SIB1 information block to indicate whether a second type of REDCAP terminal is allowed to access the network device, if the value of the 1 bit in the reserved field is 0, the terminal device determines not to access the network device; if the value of the 1 bit in the reserved field is 1 and the value of the 1 bit in the SIB1 information block is 1, the terminal device determines to access the network device; if the value of the 1 bit in the reserved field is 1 and the value of the 1 bit in the SIB1 information block is 0, the terminal device determines not to access the network device. Alternatively, if the value of the 1 bit in the reserved field is 1, the terminal device determines not to access the network device; if the value of the 1 bit in the reserved field is 0 and the value of the 1 bit in the SIB1 information block is 0, the terminal device determines to access the network device; if the value of the 1 bit in the reserved field is 0 and the value of the 1 bit in the SIB1 information block is 1, the terminal device determines not to access the network device.

[0265] based on Figure 3 The method shown allows a network device to send first information to a terminal device, indicating whether to allow a first type of REDCAP terminal to access the network device and whether to allow a second type of REDCAP terminal to access the network device. Upon receiving this first information, the terminal device can determine whether to access the network device. In this way, the network device can control the number of first and second type REDCAP terminals accessing the network device to ensure the transmission performance of the network managed by the network device.

[0266] Understandably, REDCAP terminals have lower bandwidth compared to regular terminals. Therefore, network devices need to employ different processing methods when allocating resources for REDCAP and regular terminals. For example, when allocating resources for REDCAP terminals, network devices cannot allocate frequency domain resources exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, compared to regular terminals, REDCAP terminals have fewer antennas, meaning their receiving antenna gain is lower. Therefore, when scheduling downlink reception for REDCAP terminals, network devices may need to use a lower coding rate or perform repeated transmissions to increase downlink transmission reliability.

[0267] In summary, during communication with terminal devices, network devices handle REDCAP terminals differently from ordinary terminals. Therefore, REDCAP terminals need to report their type at appropriate times. For example, a REDCAP terminal can report its type during random access, or it can report its type via radio resource control (RRC) signaling after successful random access. This allows network devices to allocate appropriate resources to the REDCAP terminal based on its type, improving the reliability of REDCAP transmission. It should be understood that the earlier a REDCAP terminal reports its type, the earlier the network device can identify the REDCAP terminal's type, preparing for subsequent transmission and improving transmission reliability.

[0268] Optional, in Figure 3 In one possible implementation of the method shown, if the first information indicates that a first type of REDCAP terminal is allowed to access the network device; or if the first information indicates that a second type of REDCAP terminal is allowed to access the network device; or if the first information indicates that both a first type of REDCAP terminal and a second type of REDCAP terminal are allowed to access the network device, the terminal device indicated in the first information as allowed to access the network device can report the type of the terminal device to the network device through the second information, so that the network device can identify the type of the terminal device. Specifically, as shown... Figure 4 As shown, Figure 3 The method shown also includes step 401.

[0269] Step 401: The terminal device sends the second information to the network device.

[0270] The second information is used to indicate whether the terminal device is a Type I REDCAP terminal or a Type II REDCAP terminal. For example, if the terminal device is a Type I REDCAP terminal, the second information is used to indicate that the terminal device is a Type I REDCAP terminal; if the terminal device is a Type II REDCAP terminal, the second information is used to indicate that the terminal device is a Type II REDCAP terminal.

[0271] One possible implementation involves carrying the second information on the physical random access channel (PRACH). The PRACH resources correspond to either a Type I REDCAP terminal or a Type II REDCAP terminal. The PRACH resources include at least one of the following: PRACH time-domain resources, PRACH frequency-domain resources, or PRACH code-domain resources. For example, the PRACH time-domain resources and PRACH frequency-domain resources can be the time-domain and frequency-domain resources of the random access channel occurrence (RO), while the PRACH code-domain resources can be the preamble code of the PRACH transmitted by the terminal device on the RO.

[0272] The PRACH resources are configured by the network device for the terminal device. The network device can configure the PRACH resources corresponding to the first type of REDCAP terminal and / or the PRACH resources corresponding to the second type of REDCAP terminal. Specifically, the following four exemplary cases can be referred to:

[0273] Scenario 1: If the terminal device is a Type I REDCAP terminal, and the first information indicates that the Type I REDCAP terminal is allowed to access the network device, the network device configures the PRACH resources corresponding to the Type I REDCAP terminal for the Type I REDCAP terminal. The terminal device sends the second information to the network device through the PRACH resources corresponding to the Type I REDCAP terminal.

[0274] Scenario 2: When the terminal device is a Type I REDCAP terminal, and the first information indicates that Type I REDCAP terminals are allowed to access the network device; or, when the terminal device is a Type I REDCAP terminal, and the first information indicates that both Type I REDCAP terminals and Type II REDCAP terminals are allowed to access the network device, the network device configures the PRACH resources corresponding to the Type I REDCAP terminal for the Type I REDCAP terminal, and configures the PRACH resources corresponding to the Type II REDCAP terminal for the Type II REDCAP terminal. The terminal device sends the second information to the network device through the PRACH resources corresponding to the Type I REDCAP terminal.

[0275] Scenario 3: If the terminal device is a Type II REDCAP terminal, and the first information indicates that the Type II REDCAP terminal is allowed to access the network device, the network device configures the PRACH resources corresponding to the Type II REDCAP terminal for the Type II REDCAP terminal. The terminal device sends the second information to the network device through the PRACH resources corresponding to the Type II REDCAP terminal.

[0276] Scenario 4: When the terminal device is a Type II REDCAP terminal, and the first information indicates that the Type II REDCAP terminal is allowed to access the network device; or, when the terminal device is a Type II REDCAP terminal, and the first information indicates that both Type I REDCAP and Type II REDCAP terminals are allowed to access the network device, the network device configures the PRACH resources corresponding to the Type I REDCAP terminal for the Type I REDCAP terminal, and configures the PRACH resources corresponding to the Type II REDCAP terminal for the Type II REDCAP terminal. The terminal device sends the second information to the network device through the PRACH resources corresponding to the Type II REDCAP terminal.

[0277] Understandably, the resources for the PRACH mentioned above can also be predefined; for example, the resources for the PRACH mentioned above can be defined in the protocol.

[0278] It is understandable that the PRACH resources corresponding to the first type of REDCAP terminal are different from those corresponding to the second type of REDCAP terminal.

[0279] Another possible implementation is that the second information is carried in Msg3, MsgA, or RRC signaling. That is, the terminal device can report its type in Msg3, MsgA, or RRC signaling. For an introduction to Msg3 and MsgA, please refer to [link to relevant documentation]. Figure 1 The corresponding description in the text.

[0280] Furthermore, the second information includes an identifier of the type of terminal device. For example, taking ID 1 as the identifier of a first type of REDCAP terminal and ID 2 as the identifier of a second type of REDCAP terminal, if the second information includes ID 1, then the second information indicates that the type of terminal device is a first type of REDCAP terminal; if the second information includes ID 2, then the second information indicates that the type of terminal device is a second type of REDCAP terminal.

[0281] Understandably, if a network device indicates that a regular terminal is allowed to access the network device, the regular terminal may or may not report its terminal type. If a regular terminal does not report its terminal type, the network device, having not received the reported type from the terminal device, can determine that the terminal device is a regular terminal. Regular terminals can also report their terminal type to the network device through various methods such as PRACH, Msg3, MsgA, or RRC signaling. For details, please refer to the description of REDCAP terminal reporting of terminal type in step 401 above; further elaboration is omitted here.

[0282] Correspondingly, the network device receives the second information from the terminal device. Subsequently, the network device can determine the type of the terminal device based on the second information.

[0283] For example, in cases 1 and 2 above, the network device determines the terminal device to be a Type 1 REDCAP terminal. In cases 3 and 4 above, the network device determines the terminal device to be a Type 2 REDCAP terminal.

[0284] For example, taking ID 1 as the identifier of the first type of REDCAP terminal and ID 2 as the identifier of the second type of REDCAP terminal, if the second information includes ID 1, the network device determines that the type of the terminal device is the first type of REDCAP terminal; if the second information includes ID 2, the network device determines that the type of the terminal device is the second type of REDCAP terminal.

[0285] based on Figure 4 The method shown allows the terminal device to report its type to the network device via various methods such as PRACH, Msg3, MsgA, or RRC signaling, enabling the network device to identify the terminal device type. On one hand, this avoids the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the REDCAP terminal's maximum bandwidth. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmissions.

[0286] Optional, in Figure 3 In one possible implementation of the method shown, the terminal device is either a Type I REDCAP terminal or a Type II REDCAP terminal. The first information indicates that both Type I and Type II REDCAP terminals are permitted to access the network device. The terminal device then reports its type to the network device via the second and third information, so that the network device can identify the type of the terminal device. Specifically, as shown... Figure 5 As shown, Figure 3 The method shown also includes steps 501 and 502.

[0287] Step 501: The terminal device sends the second information to the network device.

[0288] One possible implementation is that the second information is carried in the PRACH. The resources of the PRACH correspond to those of the REDCAP terminal. The resources of the PRACH include at least one of the time-domain resources, frequency-domain resources, or code-domain resources of the PRACH.

[0289] The PRACH resources are configured by the network device for the terminal device. The network device can configure the PRACH resources corresponding to REDCAP terminals for the terminal device; or, the network device can configure the PRACH resources corresponding to REDCAP terminals and ordinary terminals for the terminal device; or, the network device can configure the PRACH resources corresponding to the first type of REDCAP terminals and ordinary terminals, and the PRACH resources corresponding to the second type of REDCAP terminals for the terminal device. Specifically, the following two exemplary cases can be referred to:

[0290] Scenario 5: When the network device configures the PRACH resources corresponding to a REDCAP terminal for the terminal device; or, when the network device configures the PRACH resources corresponding to a REDCAP terminal and the PRACH resources corresponding to a normal terminal for the terminal device, if the terminal device is a Type I REDCAP terminal or a Type II REDCAP terminal, the terminal device sends second information to the network device through the PRACH resources corresponding to the REDCAP terminal. The second information is used to indicate that the terminal device belongs to the REDCAP terminal category.

[0291] In this scenario, Type I REDCAP terminals and Type II REDCAP terminals share PRACH resources. Therefore, the second information can indicate whether the terminal device is a REDCAP terminal or a terminal of the REDCAP type, but it cannot indicate whether the terminal device is specifically a Type I REDCAP terminal or a Type II REDCAP terminal.

[0292] Scenario 6: When the network device configures PRACH resources corresponding to Type I REDCAP terminals and ordinary terminals, and PRACH resources corresponding to Type II REDCAP terminals for the terminal device, if the terminal device is a Type I REDCAP terminal, the terminal device sends second information to the network device through the PRACH resources corresponding to Type I REDCAP terminals and ordinary terminals. The second information indicates that the terminal device is either a Type I REDCAP terminal or a normal terminal. If the terminal device is a Type II REDCAP terminal, the terminal device sends second information to the network device through the PRACH resources corresponding to Type II REDCAP terminals, whereby the second information indicates that the terminal device is a Type II REDCAP terminal.

[0293] In this scenario, Type I REDCAP terminals share PRACH resources with ordinary terminals. Therefore, if the terminal device is a Type I REDCAP terminal, the second information can indicate whether the terminal device is a Type I REDCAP terminal or an ordinary terminal, but it cannot indicate whether the terminal device is a Type I REDCAP terminal or an ordinary terminal. If the terminal device is a Type II REDCAP terminal, the second information can directly indicate that the terminal device is a Type II REDCAP terminal.

[0294] Correspondingly, the network device receives the second information from the terminal device.

[0295] In case 5 above, the network device can determine that the terminal device is a REDCAP terminal based on the second information.

[0296] In case 6 above, the network device can determine the terminal device as either a Type I REDCAP terminal or a regular terminal based on the second information; or, the network device can determine the terminal device as a Type II REDCAP terminal based on the second information.

[0297] Step 502: The terminal device sends third information to the network device.

[0298] One possible implementation is that the third information is carried in Msg3, MsgA, or RRC signaling.

[0299] Understandably, if the network device cannot determine the type of the terminal device based on the second information, the terminal device sends third information to the network device. For example, if the network device determines that the terminal device is a REDCAP terminal based on the second information; or if the network device determines that the terminal device is either a Type I REDCAP terminal or a regular terminal based on the second information, the terminal device sends third information to the network device.

[0300] In one possible implementation, if the network device determines that the terminal device is a REDCAP terminal based on the second information, the third information is used to indicate whether the terminal device is a Type I REDCAP terminal or a Type II REDCAP terminal. For example, if the terminal device is a Type I REDCAP terminal, the third information is used to indicate that the terminal device is a Type I REDCAP terminal; if the terminal device is a Type II REDCAP terminal, the third information is used to indicate that the terminal device is a Type II REDCAP terminal.

[0301] Furthermore, the third information includes an identifier of the terminal device type. For example, taking ID 1 as the identifier of a first type of REDCAP terminal and ID 2 as the identifier of a second type of REDCAP terminal, if the third information includes ID 1, then the third information indicates that the terminal device type is a first type of REDCAP terminal; if the third information includes ID 2, then the third information indicates that the terminal device type is a second type of REDCAP terminal.

[0302] In one possible implementation, if the network device determines that the terminal device is either a Type I REDCAP terminal or a normal terminal based on the second information, the third information is used to indicate that the terminal device is a Type I REDCAP terminal.

[0303] Furthermore, the third information includes an identifier of the type of terminal device. For example, taking ID 1 as the identifier of a first-type REDCAP terminal, if the third information includes ID 1, then the third information indicates that the type of terminal device is a first-type REDCAP terminal.

[0304] Understandably, if a network device indicates that a regular terminal is allowed to access the network device, the regular terminal may or may not report its terminal type. If a regular terminal does not report its terminal type, the network device, having not received the reported type from the terminal device, can determine that the terminal device is a regular terminal. Regular terminals can also report their terminal type to the network device through various methods such as PRACH, Msg3, MsgA, or RRC signaling. For details, please refer to the description of REDCAP terminal reporting of terminal type in steps 501 and 502 above, which will not be elaborated upon here.

[0305] Correspondingly, the network device receives third information from the terminal device.

[0306] Furthermore, the network device determines the type of terminal device based on third-party information.

[0307] For example, if the network device determines that the terminal device is a REDCAP terminal based on the second information, and the third information is used to indicate that the terminal device is a first type of REDCAP terminal, then the network device determines that the type of the terminal device is a first type of REDCAP terminal; if the third information is used to indicate that the terminal device is a second type of REDCAP terminal, then the network device determines that the type of the terminal device is a second type of REDCAP terminal.

[0308] For example, if the network device determines that the terminal device is either a first-type REDCAP terminal or a normal terminal based on the second information, and the third information is used to indicate that the terminal device is a first-type REDCAP terminal, then the network device determines that the type of the terminal device is a first-type REDCAP terminal.

[0309] based on Figure 5 The method shown allows the terminal device to report its type to the network device via second and third information, enabling the network device to identify the terminal device's type. On one hand, this avoids the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the REDCAP terminal's maximum bandwidth. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmission. Furthermore, in Figure 5 In the method shown, the first type of REDCAP terminal can share PRACH resources with the second type of REDCAP terminal, or the first type of REDCAP terminal can share PRACH resources with ordinary terminals. This avoids excessive fragmentation of PRACH resources, thus preventing excessive degradation of random access capacity.

[0310] It is understandable that, in addition to the aforementioned cases where REDCAP terminals include both Type I and Type II REDCAP terminals, REDCAP terminals may also include Type III REDCAP terminals. The operating frequency range of Type III REDCAP terminals differs from that of Type I and Type II REDCAP terminals. For example, Type I and Type II REDCAP terminals operate in a frequency range of FR1, while Type III REDCAP terminals operate in a frequency range greater than or equal to 6 GHz, denoted as FR2.

[0311] The following describes the method for accessing network devices provided in this application embodiment, taking as an example either a REDCAP terminal including a first type of REDCAP terminal and a second type of REDCAP terminal, or a REDCAP terminal including a third type of REDCAP terminal.

[0312] like Figure 6 The image shows a method for accessing a network device according to an embodiment of this application. The method for accessing a network device includes steps 601-603.

[0313] Step 601: The network device determines the first information.

[0314] Among them, network devices can be Figure 1 Network device 101.

[0315] The first piece of information can be used to indicate whether a REDCAP terminal is allowed to access the network device. The REDCAP terminal includes either a first-type REDCAP terminal or a second-type REDCAP terminal; or, a third-type REDCAP terminal. The descriptions of the first-type and second-type REDCAP terminals can be found in step 301 above. The operating frequency range of the third-type REDCAP terminal differs from that of the first-type and second-type REDCAP terminals. For example, the first-type and second-type REDCAP terminals operate in frequency range FR1, while the third-type REDCAP terminal operates in frequency range FR2. When the third-type REDCAP terminal operates in frequency range FR2, the description of the third-type REDCAP terminal can be found above. Figure 1 As described in [the text].

[0316] It should be noted that when the REDCAP terminal includes both the first type of REDCAP terminal and the second type of REDCAP terminal, the description of the first information can be referred to in step 301 above.

[0317] The following describes the contents of the first information when the REDCAP terminal includes the third type of REDCAP terminal.

[0318] One possible implementation is that the first information includes third indication information. This third indication information can be used to indicate whether a third-type REDCAP terminal is allowed to access the network device. The third indication information can have the following four forms:

[0319] Case 3.1: The third instruction information includes empty fields in the MIB.

[0320] For example, the third indication information indicates whether a third type of REDCAP terminal is allowed to access the network device through a 1-bit field in the MIB. For instance, if the value of this 1-bit is 1, the third indication information indicates that the third type of REDCAP terminal is allowed to access the network device; if the value of this 1-bit is 0, the third indication information indicates that the third type of REDCAP terminal is not allowed to access the network device, and vice versa.

[0321] Case 3.2: The third indication information includes whether access is prohibited (cellBarred field).

[0322] For example, if the value of the "Do Not Prohibit Access" field is 1, the third indication information indicates that the third type of REDCAP terminal is allowed to access the network device; if the value of the "Do Not Prohibit Access" field is 0, the third indication information indicates that the third type of REDCAP terminal is not allowed to access the network device, and vice versa.

[0323] Understandably, the bandwidth of a Type 3 REDCAP terminal is similar to that of a regular terminal, and both can share CORESET#0, resulting in good compatibility. Furthermore, the presence of a Type 3 REDCAP terminal has minimal impact on network performance. Therefore, a Type 3 REDCAP terminal can reuse the field indicating whether network access is permitted in a regular terminal. In other words, the "prohibit access" field is used not only to indicate whether network access is permitted for regular terminals but also for Type 3 REDCAP terminals. Additionally, reusing the "prohibit access" field in a Type 3 REDCAP terminal saves bits, allowing these bits to be used for other purposes and facilitating backward compatibility expansion of the communication system.

[0324] Case 3.3: The third instruction information is included in the reserved field of the DCI.

[0325] For example, the third indication information includes 1 bit in the reserved field of the DCI, used to indicate whether a third type REDCAP terminal is allowed to access the network device. For instance, if the value of this 1 bit is 1, the third indication information indicates that a third type REDCAP terminal is allowed to access the network device; if the value of this 1 bit is 0, the third indication information indicates that a third type REDCAP terminal is not allowed to access the network device, and vice versa.

[0326] Case 3.4: The third instruction information is included in the SIB1 information block.

[0327] For example, the third indication information includes 1 bit in the SIB1 information block, used to indicate whether a third type REDCAP terminal is allowed to access the network device. For instance, if the value of this 1 bit is 1, the third indication information indicates that a third type REDCAP terminal is allowed to access the network device; if the value of this 1 bit is 0, the third indication information indicates that a third type REDCAP terminal is not allowed to access the network device, and vice versa.

[0328] Understandably, the 1 bit in the SIB1 information block used to indicate whether a third-type REDCAP terminal is allowed to access the network device can be included in the newly added IE in the SIB1 information block, or it can be included in the original IE in the SIB1 information block.

[0329] One possible implementation is that the network device determines the first information based on the transmission performance of the network it manages. For example, if the network transmission performance is greater than or equal to a threshold, the network device does not limit the number of REDCAP terminals; if the network transmission performance is less than the threshold, the network device limits the number of REDCAP terminals.

[0330] Step 602: The network device sends the first information to the terminal device.

[0331] The description of step 602 can be found in step 302 above, and will not be repeated here.

[0332] Step 603: The terminal device determines whether to access the network device based on the first information.

[0333] The terminal device can be a Type I REDCAP terminal, a Type II REDCAP terminal, a Type III REDCAP terminal, or a regular terminal.

[0334] When the terminal device is a Type I REDCAP terminal, a Type II REDCAP terminal, or a regular terminal, the process by which the terminal device determines whether to access the network device based on the first information can be referred to in step 303 above, and will not be repeated here.

[0335] The following describes the process by which the terminal device determines whether to access the network device based on the first information when the terminal device is a Type III REDCAP terminal.

[0336] For example, taking the third indication information indicating whether a third type of REDCAP terminal is allowed to access the network device through 1 bit in the empty field of the MIB, if the value of the 1 bit is 1, the terminal device determines to access the network device; if the value of the 1 bit is 0, the terminal device determines not to access the network device, and vice versa.

[0337] For example, taking the third indication information indicating whether a third type of REDCAP terminal is allowed to access the network device through the "Do Not Access Deny" field in the MIB, if the value of the "Do Not Access Deny" field is 1, the terminal device determines to access the network device; if the value of the "Do Not Access Deny" field is 0, the terminal device determines not to access the network device, and vice versa.

[0338] For example, taking 1 bit in the reserved field of DCI in the third indication information as an example, which is used to indicate whether a third type REDCAP terminal is allowed to access the network device, if the value of the 1 bit is 1, the terminal device determines to access the network device; if the value of the 1 bit is 0, the terminal device determines not to access the network device, and vice versa.

[0339] For example, taking the third indication information including 1 bit in the SIB1 information block to indicate whether a third type REDCAP terminal is allowed to access the network device, if the value of the 1 bit is 1, the terminal device determines to access the network device; if the value of the 1 bit is 0, the terminal device determines not to access the network device, and vice versa.

[0340] based on Figure 6The method shown allows the network device to send first information to the terminal device indicating whether to allow a first type of REDCAP terminal to access the network device and whether to allow a second type of REDCAP terminal to access the network device; alternatively, the network device can send first information to the terminal device indicating whether to allow a third type of REDCAP terminal to access the network device. Upon receiving this first information, the terminal device can determine whether to access the network device. Thus, the network device can control the number of first and second type REDCAP terminals accessing the network device, or the network device can control the number of third type REDCAP terminals accessing the network device, to ensure the transmission performance of the network managed by the network device.

[0341] Understandably, REDCAP terminals have lower bandwidth compared to regular terminals. Therefore, network devices need to employ different processing methods when allocating resources for REDCAP and regular terminals. For example, when allocating resources for REDCAP terminals, network devices cannot allocate frequency domain resources exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, compared to regular terminals, REDCAP terminals have fewer antennas, meaning their receiving antenna gain is lower. Therefore, when scheduling downlink reception for REDCAP terminals, network devices may need to use a lower coding rate or perform repeated transmissions to increase downlink transmission reliability.

[0342] In summary, network devices handle REDCAP terminals and ordinary terminals differently during communication with terminal devices. Therefore, REDCAP terminals need to report their type at appropriate times. For example, a REDCAP terminal can report its type during random access, or it can report its type via RRC signaling after successful random access. This allows network devices to allocate appropriate resources to REDCAP terminals based on their type, improving the reliability of REDCAP terminal transmission. It should be understood that the earlier a REDCAP terminal reports its type, the earlier the network device can identify the REDCAP terminal's type, preparing for subsequent transmissions and improving transmission reliability.

[0343] Optional, in Figure 6In one possible implementation of the method shown, if the first information indicates that a first type of REDCAP terminal is allowed to access the network device; or, if the first information indicates that a second type of REDCAP terminal is allowed to access the network device; or, if the first information indicates that both a first type of REDCAP terminal and a second type of REDCAP terminal are allowed to access the network device; or, if the first information indicates that a third type of REDCAP terminal is allowed to access the network device, the terminal device indicated in the first information as allowed to access the network device can report the type of the terminal device to the network device through the second information, so that the network device can identify the type of the terminal device. Specifically, as shown... Figure 7 As shown, Figure 6 The method shown also includes step 701.

[0344] Step 701: The terminal device sends the second information to the network device.

[0345] The second information is used to indicate whether the terminal device is a Type I REDCAP terminal, a Type II REDCAP terminal, or a Type III REDCAP terminal. For example, if the terminal device is a Type I REDCAP terminal, the second information is used to indicate that the terminal device is a Type I REDCAP terminal; if the terminal device is a Type II REDCAP terminal, the second information is used to indicate that the terminal device is a Type II REDCAP terminal; if the terminal device is a Type III REDCAP terminal, the second information is used to indicate that the terminal device is a Type III REDCAP terminal.

[0346] One possible implementation involves carrying the second information on the PRACH. The PRACH resources correspond to those of a Type I, Type II, or Type III REDCAP terminal. The PRACH resources include at least one of the following: PRACH time-domain resources, PRACH frequency-domain resources, or PRACH code-domain resources. For example, the PRACH time-domain resources and PRACH frequency-domain resources can be the time-domain and frequency-domain resources of a random access channel occasion (RO), while the PRACH code-domain resources can be the preamble code of the PRACH transmitted by the terminal device on the RO.

[0347] Wherein, if the terminal device is a type REDCAP terminal and the first information indicates that the type REDCAP terminal is allowed to access the network device; or, if the terminal device is a type REDCAP terminal and the first information indicates that the type REDCAP terminal is allowed to access the network device, and the type REDCAP terminal is allowed to access the network device, the description of the PRACH resources can be referred to in step 401 above, and will not be repeated here.

[0348] Wherein, if the terminal device is a type II REDCAP terminal and the first information indicates that the type II REDCAP terminal is allowed to access the network device; or, if the terminal device is a type II REDCAP terminal and the first information indicates that the type I REDCAP terminal is allowed to access the network device, and the type II REDCAP terminal is allowed to access the network device, the description of the PRACH resources can be referred to in step 401 above, and will not be repeated here.

[0349] The following describes the PRACH resource situation when the terminal device is a Type 3 REDCAP terminal and the first information indicates that the Type 3 REDCAP terminal is allowed to access the network device.

[0350] The PRACH resources are configured by the network device for the terminal device. The network device can configure the PRACH resources corresponding to the Type 3 REDCAP terminal for the terminal device.

[0351] For example, the network device configures the PRACH resources corresponding to the third-type REDCAP terminal for the third-type REDCAP terminal. The terminal device sends the second information to the network device through the PRACH resources corresponding to the third-type REDCAP terminal.

[0352] Understandably, network devices can also configure PRACH resources corresponding to each type of terminal. Thus, when a terminal device reports its type, it sends second information to the network device using the PRACH resources corresponding to that terminal device.

[0353] For example, the network device configures the PRACH resources corresponding to the first type of REDCAP terminal, configures the PRACH resources corresponding to the second type of REDCAP terminal, and configures the PRACH resources corresponding to the third type of REDCAP terminal. If the terminal device is a first type of REDCAP terminal, the terminal device sends the second information to the network device through the PRACH resources corresponding to the first type of REDCAP terminal. If the terminal device is a second type of REDCAP terminal, the terminal device sends the second information to the network device through the PRACH resources corresponding to the second type of REDCAP terminal. If the terminal device is a third type of REDCAP terminal, the terminal device sends the second information to the network device through the PRACH resources corresponding to the third type of REDCAP terminal.

[0354] Understandably, the resources for the PRACH mentioned above can also be predefined; for example, the resources for the PRACH mentioned above can be defined in the protocol.

[0355] Another possible implementation is that the second information is carried in Msg3, MsgA, or RRC signaling. That is, the terminal device can report its type in Msg3, MsgA, or RRC signaling. For an introduction to Msg3 and MsgA, please refer to [link to relevant documentation]. Figure 1 The corresponding description in the text.

[0356] Furthermore, the second information includes an identifier of the type of terminal device. For example, taking ID 1 as the identifier of a first type of REDCAP terminal and ID 2 as the identifier of a second type of REDCAP terminal, if the second information includes ID 1, then the second information indicates that the type of terminal device is a first type of REDCAP terminal; if the second information includes ID 2, then the second information indicates that the type of terminal device is a second type of REDCAP terminal.

[0357] For example, taking ID 3 as the identifier of a third type REDCAP terminal, if the second information includes ID 3, then the second information indicates that the type of the terminal device is a third type REDCAP terminal.

[0358] Understandably, if a network device indicates that a regular terminal is allowed to access the network device, the regular terminal may or may not report its terminal type. If a regular terminal does not report its terminal type, the network device, having not received the reported type from the terminal device, can determine that the terminal device is a regular terminal. Regular terminals can also report their terminal type to the network device through various methods such as PRACH, Msg3, MsgA, or RRC signaling. For details, please refer to the description of REDCAP terminal reporting of terminal type in step 701 above; further elaboration is omitted here.

[0359] Correspondingly, the network device receives the second information from the terminal device. Subsequently, the network device can determine the type of the terminal device based on the second information.

[0360] The terminal device is either a Type I REDCAP terminal or a Type II REDCAP terminal. The process by which the network device determines the type of the terminal device based on the second information can be referred to in step 401 above, and will not be repeated here.

[0361] For example, if a terminal device sends second information to a network device through the PRACH resources corresponding to a third-type REDCAP terminal, the network device determines that the terminal device is a third-type REDCAP terminal.

[0362] For example, if the identifier of a third type REDCAP terminal is ID 3, and the second information includes ID 3, then the network device determines that the type of the terminal device is a third type REDCAP terminal.

[0363] based on Figure 7The method shown allows the terminal device to report its type to the network device via various methods such as PRACH, Msg3, MsgA, or RRC signaling, enabling the network device to identify the terminal device type. On one hand, this avoids the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the REDCAP terminal's maximum bandwidth. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmissions.

[0364] Optional, in Figure 6 In one possible implementation of the method shown, the terminal device is either a Type I REDCAP terminal or a Type II REDCAP terminal. The first information indicates that both Type I and Type II REDCAP terminals are permitted to access the network device. The terminal device then reports its type to the network device via the second and third information, so that the network device can identify the type of the terminal device. Specifically, as shown... Figure 8 As shown, Figure 6 The method shown also includes steps 801 and 802.

[0365] Step 801: The terminal device sends the second information to the network device.

[0366] Step 802: The terminal device sends third information to the network device.

[0367] The descriptions of steps 801-802 can be found in the descriptions of steps 501-502 above, and will not be repeated here.

[0368] based on Figure 8 The method shown allows the terminal device to report its type to the network device via second and third information, enabling the network device to identify the terminal device's type. On one hand, this avoids the network device scheduling REDCAP terminals for uplink or downlink transmissions at frequencies exceeding the REDCAP terminal's maximum bandwidth. On the other hand, when scheduling REDCAP terminals for downlink reception, the network device can use a lower coding rate or perform repeated transmissions to increase the reliability of downlink transmission. Furthermore, in Figure 8 In the method shown, the first type of REDCAP terminal can share PRACH resources with the second type of REDCAP terminal, or the first type of REDCAP terminal can share PRACH resources with ordinary terminals. This avoids excessive fragmentation of PRACH resources, thus preventing excessive degradation of random access capacity.

[0369] The above mainly describes the solutions provided by the embodiments of this application from the perspective of interaction between various network elements. It is understood that the network devices or terminal devices described above, in order to achieve the above functions, include hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the unit and algorithm operations of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0370] This application embodiment can divide network devices or terminal devices into functional modules according to the above method examples. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0371] Figure 9 This is a schematic diagram of the structure of a communication device 90 provided in an embodiment of this application. Exemplarily, the communication device 90 is, for example, a terminal device 90. Exemplarily, the terminal device 90 is, for example, a... Figure 3 The embodiment shown, Figure 4 The illustrated embodiments or Figure 5 The terminal device described in the illustrated embodiment.

[0372] The terminal device 90 includes a transceiver module 901 and a processing module 902. Exemplarily, the terminal device 90 can be a terminal device, or a chip or other combination device or component having the aforementioned terminal device functions. When the terminal device 90 is a terminal device, the transceiver module 901 can be a transceiver, which may include an antenna and radio frequency circuitry, etc., and the processing module 902 can be a processor (or processing circuitry), such as a baseband processor, which may include one or more CPUs. When the terminal device 90 is a component having the aforementioned terminal device functions, the transceiver module 901 can be a radio frequency unit, and the processing module 902 can be a processor (or processing circuitry), such as a baseband processor. When the terminal device 90 is a chip system, the transceiver module 901 can be an input / output interface of a chip (e.g., a baseband chip), and the processing module 902 can be a processor (or processing circuitry) of the chip system, which may include one or more central processing units. It should be understood that the transceiver module 901 in the embodiments of this application can be implemented by a transceiver or transceiver-related circuit components, and the processing module 902 can be implemented by a processor or processor-related circuit components (or, referred to as processing circuit).

[0373] For example, the transceiver module 901 can be used to perform... Figure 3 The embodiments shown include all transmit and receive operations performed by the terminal device, such as step 302, and / or other processes used to support the techniques described herein. Processing module 902 can be used to perform... Figure 3 In the embodiments shown, all operations performed by the terminal device other than the transmit / receive operation, such as step 303, and / or other processes used to support the technology described herein.

[0374] For example, the transceiver module 901 can be used to perform... Figure 4 In the illustrated embodiment, all transmit and receive operations performed by the terminal device, such as steps 302 and 401, and / or other processes used to support the techniques described herein, are included. Processing module 902 can be used to perform... Figure 4 In the embodiments shown, all operations performed by the terminal device other than the transmit / receive operation, such as step 303, and / or other processes used to support the technology described herein.

[0375] For example, the transceiver module 901 can be used to perform... Figure 5 In the illustrated embodiment, all transmit and receive operations performed by the terminal device, such as steps 302, 501, and 502, and / or other processes used to support the techniques described herein, are included. Processing module 902 can be used to execute... Figure 3In the embodiments shown, all operations performed by the terminal device other than the transmit / receive operation, such as step 303, and / or other processes used to support the technology described herein.

[0376] The transceiver module 901 is used to receive first information from the network device. The first information is used to indicate whether the REDCAP terminal is allowed to access the network device. The REDCAP terminal includes a first type of REDCAP terminal and a second type of REDCAP terminal. The first type of REDCAP terminal and the second type of REDCAP terminal operate in the same frequency domain range. The bandwidth of the second type of REDCAP terminal is smaller than that of the first type of REDCAP terminal, and / or the number of receiving antennas of the second type of REDCAP terminal is smaller than that of the first type of REDCAP terminal.

[0377] The processing module 902 is used to determine whether to access the network device based on the first information, wherein the communication device is either the first type of REDCAP terminal or the second type of REDCAP terminal.

[0378] One possible implementation is that the first information includes first indication information and second indication information; wherein the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device; or, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the network device.

[0379] One possible implementation is that the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device; the first indication information includes a free field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload; or, the first indication information includes a whether access is prohibited field in the MIB, and the second indication information includes a free field in the MIB or includes a reserved field in the additional PBCH payload.

[0380] In one possible implementation, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the network device. The first indication information includes a spare field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload.

[0381] One possible implementation is that the first information is included in the SSB, which includes the MIB and the additional PBCH payload.

[0382] One possible implementation is that the first indication information is included in a reserved field of the DCI, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in a reserved field of the DCI, and the second indication information is included in the SIB1 information block; or, the first indication information is included in the SIB1 information block, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in the SIB1 information block, and the second indication information is included in the SIB1 information block; wherein the DCI is used to schedule SIB1.

[0383] One possible implementation is that the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "disable access" field in the MIB, and the second indication information is included in a reserved field in the DCI, or the second indication information is included in the SIB1 information block; or; the first indication information is included in a reserved field in the DCI, or the first indication information is included in the SIB1 information block, and the second indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "disable access" field in the MIB, wherein the DCI is used to schedule SIB1.

[0384] In one possible implementation, the first information indicates that the first type of REDCAP terminal and / or the second type of REDCAP terminal are allowed to access the network device. The transceiver module 901 is used to send second information to the network device, the second information being used to indicate that the communication device is the first type of REDCAP terminal or the second type of REDCAP terminal.

[0385] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the first type of REDCAP terminal or the second type of REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH; or, the second information is carried in Msg3, MsgA, or RRC signaling.

[0386] In one possible implementation, the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device; the transceiver module 901 is further configured to send second information to the network device, the second information being used to indicate that the communication device belongs to the REDCAP terminal; the transceiver module 901 is further configured to send third information to the network device, the third information being used to indicate that the communication device is the first type of REDCAP terminal or the second type of REDCAP terminal.

[0387] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH; the third information is carried in Msg3, MsgA, or RRC signaling.

[0388] For other functions that terminal device 90 can perform, please refer to [reference needed]. Figure 3 The embodiment shown, Figure 4 The method embodiments shown or Figure 5 The relevant descriptions of the embodiments shown will not be elaborated upon further.

[0389] Figure 10 This is a schematic diagram of the structure of a communication device 100 provided in an embodiment of this application. Exemplarily, the communication device 100 is, for example, a network device 100. Exemplarily, the network device 100 is, for example, a... Figure 3 The embodiment shown, Figure 4 The illustrated embodiments or Figure 5 The network device described in the illustrated embodiment.

[0390] Network device 100 includes a processing module 1001 and a transceiver module 1002. Exemplarily, network device 100 can be a network device, or a chip or other combination of devices or components having the aforementioned network device functions applied within a network device. When network device 100 is a network device, processing module 1001 can be a processor (or processing circuitry), such as a baseband processor, which may include one or more CPUs. Transceiver module 1002 can be a transceiver, which may include antennas and radio frequency circuitry, etc. When network device 100 is a component having the aforementioned network device functions, processing module 1001 can be a processor (or processing circuitry), such as a baseband processor. Transceiver module 1002 can be a radio frequency unit. When network device 100 is a chip system, processing module 1001 can be a processor (or processing circuitry) of the chip system, and may include one or more central processing units. Transceiver module 1002 can be an input / output interface of a chip (e.g., a baseband chip). It should be understood that the processing module 1001 in the embodiments of this application can be implemented by a processor or processor-related circuit components (or, referred to as processing circuitry), and the transceiver module 1002 can be implemented by a transceiver or transceiver-related circuit components.

[0391] For example, processing module 1001 can be used to execute Figure 3 In the illustrated embodiment, all operations performed by the network device other than the send / receive operation, such as step 301, and / or other processes used to support the techniques described herein, are included. The transceiver module 1002 can be used to perform... Figure 3 The embodiments shown include all send and receive operations performed by the network device, such as step 302, and / or other processes used to support the techniques described herein.

[0392] For example, processing module 1001 can be used to execute... Figure 4 In the illustrated embodiment, all operations performed by the network device other than the send / receive operation, such as step 301, and / or other processes used to support the techniques described herein, are included. The transceiver module 1002 can be used to perform... Figure 4 All transmit and receive operations performed by the network device in the illustrated embodiments, such as steps 302 and 401, and / or other processes used to support the techniques described herein.

[0393] For example, processing module 1001 can be used to execute... Figure 5 In the illustrated embodiment, all operations performed by the network device other than the send / receive operation, such as step 301, and / or other processes used to support the techniques described herein, are included. The transceiver module 1002 can be used to perform... Figure 5The embodiments shown include all send and receive operations performed by the network device, such as steps 302, 501, and 502, and / or other processes used to support the techniques described herein.

[0394] The processing module 1001 is used to determine first information, which is used to indicate whether to allow a REDCAP terminal to access the communication device. The REDCAP terminal includes a first type of REDCAP terminal and a second type of REDCAP terminal. The first type of REDCAP terminal and the second type of REDCAP terminal operate in the same frequency domain range. The bandwidth of the second type of REDCAP terminal is smaller than that of the first type of REDCAP terminal, and / or the number of receiving antennas of the second type of REDCAP terminal is smaller than that of the first type of REDCAP terminal.

[0395] The transceiver module 1002 is used to send the first information to the terminal device.

[0396] One possible implementation is that the first information includes first indication information and second indication information; wherein the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the communication device; or, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the communication device.

[0397] One possible implementation is that the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the communication device; the first indication information includes a free field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload; or, the first indication information includes a whether access is prohibited field in the MIB, and the second indication information includes a free field in the MIB or includes a reserved field in the additional PBCH payload.

[0398] In one possible implementation, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the communication device. The first indication information includes a blank field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload.

[0399] One possible implementation is that the first information is included in the SSB, which includes the MIB and the additional PBCH payload.

[0400] One possible implementation is that the first indication information is included in a reserved field of the DCI, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in a reserved field of the DCI, and the second indication information is included in the SIB1 information block; or, the first indication information is included in the SIB1 information block, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in the SIB1 information block, and the second indication information is included in the SIB1 information block; wherein the DCI is used to schedule SIB1.

[0401] One possible implementation is that the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "disable access" field in the MIB, and the second indication information is included in a reserved field in the DCI, or the second indication information is included in the SIB1 information block; or; the first indication information is included in a reserved field in the DCI, or the first indication information is included in the SIB1 information block, and the second indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "disable access" field in the MIB, wherein the DCI is used to schedule SIB1.

[0402] In one possible implementation, the first information indicates that the first type of REDCAP terminal and / or the second type of REDCAP terminal are allowed to access the communication device. The transceiver module 1002 is used to receive second information from the terminal device, the second information being used to indicate that the terminal device is the first type of REDCAP terminal or the second type of REDCAP terminal.

[0403] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the first type of REDCAP terminal or the second type of REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH; or, the second information is carried in Msg3, MsgA, or RRC signaling.

[0404] In one possible implementation, the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the communication device; the transceiver module 1002 is further configured to receive second information from the terminal device, the second information being used to indicate that the terminal device is a data REDCAP terminal; the transceiver module 1002 is further configured to receive third information from the terminal device, the third information being used to indicate that the terminal device is the first type of REDCAP terminal or the second type of REDCAP terminal.

[0405] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH; the third information is carried in Msg3, MsgA, or RRC signaling.

[0406] For other functions that network device 100 can perform, please refer to [link / reference]. Figure 3 The embodiment shown, Figure 4 The method embodiments shown or Figure 5 The relevant descriptions of the embodiments shown will not be elaborated upon further.

[0407] Figure 11 This is a schematic diagram of the structure of the communication device 110 provided in an embodiment of this application. Exemplarily, the communication device 110 is, for example, a terminal device 110. Exemplarily, the terminal device 110 is, for example, a... Figure 6 The embodiment shown, Figure 7 The illustrated embodiments or Figure 8 The terminal device described in the illustrated embodiment.

[0408] Terminal device 110 includes a transceiver module 1101 and a processing module 1102. Exemplarily, terminal device 110 can be a terminal device, or a chip or other combination device or component having the aforementioned terminal device functions applied within a terminal device. When terminal device 110 is a terminal device, transceiver module 1101 can be a transceiver, which may include an antenna and radio frequency circuitry, etc., and processing module 1102 can be a processor (or processing circuitry), such as a baseband processor, which may include one or more CPUs. When terminal device 110 is a component having the aforementioned terminal device functions, transceiver module 1101 can be a radio frequency unit, and processing module 1102 can be a processor (or processing circuitry), such as a baseband processor. When terminal device 110 is a chip system, transceiver module 1101 can be an input / output interface of a chip (e.g., a baseband chip), and processing module 1102 can be a processor (or processing circuitry) of the chip system, which may include one or more central processing units. It should be understood that the transceiver module 1101 in the embodiments of this application can be implemented by a transceiver or transceiver-related circuit components, and the processing module 1102 can be implemented by a processor or processor-related circuit components (or, referred to as processing circuit).

[0409] For example, transceiver module 1101 can be used to perform... Figure 6 The embodiments shown include all transmit and receive operations performed by the terminal device, such as step 602, and / or other processes used to support the techniques described herein. Processing module 1102 can be used to perform... Figure 3In the illustrated embodiments, all operations performed by the terminal device other than the transmit / receive operation, such as step 603, and / or other processes used to support the technology described herein.

[0410] For example, the transceiver module 1101 can be used to perform... Figure 7 In the illustrated embodiment, all transmit and receive operations performed by the terminal device, such as steps 602 and 701, and / or other processes used to support the techniques described herein, are included. Processing module 1102 can be used to perform... Figure 7 In the illustrated embodiments, all operations performed by the terminal device other than the transmit / receive operation, such as step 603, and / or other processes used to support the technology described herein.

[0411] For example, the transceiver module 1101 can be used to perform... Figure 8 The embodiments shown include all transmit and receive operations performed by the terminal device, such as steps 602, 801, and 802, and / or other processes used to support the techniques described herein. Processing module 1102 can be used to perform... Figure 8 In the illustrated embodiments, all operations performed by the terminal device other than the transmit / receive operation, such as step 603, and / or other processes used to support the technology described herein.

[0412] The transceiver module 1101 is used to receive first information from the network device. The first information is used to indicate whether the REDCAP terminal is allowed to access the network device. The REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, or the REDCAP terminal includes a third type REDCAP terminal. The first type REDCAP terminal and the second type REDCAP terminal operate in the same frequency domain range, while the third type REDCAP terminal operates in a different frequency domain range than the first type REDCAP terminal and the second type REDCAP terminal. The bandwidth of the second type REDCAP terminal is smaller than that of the first type REDCAP terminal, and / or the number of receiving antennas of the second type REDCAP terminal is smaller than that of the first type REDCAP terminal.

[0413] The processing module 1102 is used to determine whether to access the network device based on the first information, wherein the communication device is the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal.

[0414] One possible implementation is that the REDCAP terminal includes the first type of REDCAP terminal and the second type of REDCAP terminal; the first information includes first indication information and second indication information; wherein the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device; or, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the network device.

[0415] One possible implementation is that the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the network device; the first indication information includes a free field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload; or, the first indication information includes a whether access is prohibited field in the MIB, and the second indication information includes a free field in the MIB, or includes a reserved field in the additional PBCH payload.

[0416] In one possible implementation, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the network device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the network device; the first indication information includes a spare field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload.

[0417] One possible implementation is that the first indication information is included in a reserved field of the DCI, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in a reserved field of the DCI, and the second indication information is included in the SIB1 information block; or, the first indication information is included in the SIB1 information block, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in the SIB1 information block, and the second indication information is included in the SIB1 information block; wherein the DCI is used to schedule SIB1.

[0418] One possible implementation is that the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "disable access" field in the MIB, and the second indication information is included in a reserved field in the DCI, or the second indication information is included in the SIB1 information block; or; the first indication information is included in a reserved field in the DCI, or the first indication information is included in the SIB1 information block, and the second indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "disable access" field in the MIB, wherein the DCI is used to schedule SIB1.

[0419] One possible implementation is that the REDCAP terminal includes the third type of REDCAP terminal; the first information includes third indication information; wherein the third indication information is used to indicate whether the third type of REDCAP terminal is allowed to access the network device.

[0420] One possible implementation is that the third indication information includes a blank field in the MIB; or, the third indication information includes a field in the MIB indicating whether access is prohibited.

[0421] One possible implementation is that the first information is included in the SSB, which includes the MIB and the additional PBCH payload.

[0422] One possible implementation is that the third indication information is included in a reserved field of the DCI; or, the third indication information is included in the SIB1 information block.

[0423] In one possible implementation, the first information indicates that the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal is allowed to access the network device; or, the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device, and the transceiver module 1101 is used to send second information to the network device, the second information being used to indicate that the communication device is the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal.

[0424] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, the frequency domain resources, or the code domain resources of the PRACH; or, the second information is carried in Msg3, MsgA, or RRC signaling.

[0425] In one possible implementation, the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device; the transceiver module 1101 is further configured to send second information to the network device, the second information being used to indicate that the communication device belongs to the REDCAP terminal; the transceiver module 1101 is further configured to send third information to the network device, the third information being used to indicate that the communication device is the first type of REDCAP terminal or the second type of REDCAP terminal.

[0426] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH; the third information is carried in Msg3, MsgA, or RRC signaling.

[0427] For other functions that the terminal device 110 can perform, please refer to [reference needed]. Figure 3 The embodiment shown, Figure 4 The method embodiments shown or Figure 5 The relevant descriptions of the embodiments shown will not be elaborated upon further.

[0428] Figure 12 This is a schematic diagram of the structure of the communication device 120 provided in an embodiment of this application. Exemplarily, the communication device 120 is, for example, a network device 120. Exemplarily, the network device 120 is, for example, a... Figure 6 The embodiment shown, Figure 7 The illustrated embodiments or Figure 8 The network device described in the illustrated embodiment.

[0429] Network device 120 includes a processing module 1201 and a transceiver module 1202. Exemplarily, network device 120 can be a network device, or a chip or other combination of devices or components having the aforementioned network device functions applied within a network device. When network device 120 is a network device, processing module 1201 can be a processor (or processing circuitry), such as a baseband processor, which may include one or more CPUs. Transceiver module 1202 can be a transceiver, which may include antennas and radio frequency circuitry, etc. When network device 120 is a component having the aforementioned network device functions, processing module 1201 can be a processor (or processing circuitry), such as a baseband processor. Transceiver module 1202 can be a radio frequency unit. When network device 120 is a chip system, processing module 1201 can be a processor (or processing circuitry) of the chip system, and may include one or more central processing units. Transceiver module 1202 can be an input / output interface of a chip (e.g., a baseband chip). It should be understood that the processing module 1201 in the embodiments of this application can be implemented by a processor or processor-related circuit components (or, referred to as processing circuitry), and the transceiver module 1202 can be implemented by a transceiver or transceiver-related circuit components.

[0430] For example, processing module 1201 can be used to execute Figure 6 In the illustrated embodiment, all operations performed by the network device other than the transmit / receive operation, such as step 601, and / or other processes used to support the techniques described herein, are included. The transceiver module 1202 can be used to perform... Figure 6 The embodiments shown include all send and receive operations performed by the network device, such as step 602, and / or other processes used to support the techniques described herein.

[0431] For example, processing module 1201 can be used to execute... Figure 7 In the illustrated embodiment, all operations performed by the network device other than the transmit / receive operation, such as step 601, and / or other processes used to support the techniques described herein, are included. The transceiver module 1202 can be used to perform... Figure 7 All transmit and receive operations performed by the network device in the illustrated embodiments, such as steps 602 and 701, and / or other processes used to support the techniques described herein.

[0432] For example, processing module 1201 can be used to execute... Figure 8 In the illustrated embodiment, all operations performed by the network device other than the transmit / receive operation, such as step 601, and / or other processes used to support the techniques described herein, are included. The transceiver module 1202 can be used to perform... Figure 8The embodiments shown include all transmit and receive operations performed by the network device, such as steps 602, 801, and 802, and / or other processes used to support the techniques described herein.

[0433] The processing module 1201 is used to determine first information, which is used to indicate whether to allow a REDCAP terminal to access the communication device. The REDCAP terminal includes a first type of REDCAP terminal and a second type of REDCAP terminal, or the REDCAP terminal includes a third type of REDCAP terminal. The first type of REDCAP terminal and the second type of REDCAP terminal operate in the same frequency domain range, while the third type of REDCAP terminal operates in a different frequency domain range than the first type of REDCAP terminal and the second type of REDCAP terminal. The bandwidth of the second type of REDCAP terminal is smaller than that of the first type of REDCAP terminal, and / or the number of receiving antennas of the second type of REDCAP terminal is smaller than that of the first type of REDCAP terminal.

[0434] The transceiver module 1202 is used to send the first information to the terminal device.

[0435] One possible implementation is that the REDCAP terminal includes the first type of REDCAP terminal and the second type of REDCAP terminal; the first information includes first indication information and second indication information; wherein the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the communication device; or, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the communication device.

[0436] One possible implementation is that the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the second indication information is used to indicate whether the second type of REDCAP terminal is allowed to access the communication device; the first indication information includes a free field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload; or, the first indication information includes a whether access is prohibited field in the MIB, and the second indication information includes a free field in the MIB, or includes a reserved field in the additional PBCH payload.

[0437] In one possible implementation, the first indication information is used to indicate whether the first type of REDCAP terminal is allowed to access the communication device, and the first indication information and the second indication information are used to indicate whether the second type of REDCAP terminal is allowed to access the communication device; the first indication information includes a spare field in the MIB, and the second indication information includes a reserved field in the additional PBCH payload.

[0438] One possible implementation is that the first indication information is included in a reserved field of the DCI, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in a reserved field of the DCI, and the second indication information is included in the SIB1 information block; or, the first indication information is included in the SIB1 information block, and the second indication information is included in a reserved field of the DCI; or, the first indication information is included in the SIB1 information block, and the second indication information is included in the SIB1 information block; wherein the DCI is used to schedule SIB1.

[0439] One possible implementation is that the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "prohibit access" field in the MIB; the second indication information is included in a reserved field in the DCI, or the second indication information is included in the SIB1 information block; or; the first indication information is included in a reserved field in the DCI, or the first indication information is included in the SIB1 information block, and the second indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a "prohibit access" field in the MIB, wherein the DCI is used to schedule SIB1. Another possible implementation is that the REDCAP terminal includes the third type of REDCAP terminal; the first information includes third indication information; wherein the third indication information is used to indicate whether the third type of REDCAP terminal is allowed to access the communication device.

[0440] One possible implementation is that the third indication information includes a blank field in the MIB; or, the third indication information includes a field in the MIB indicating whether access is prohibited.

[0441] One possible implementation is that the first information is included in the SSB, which includes the MIB and the additional PBCH payload.

[0442] One possible implementation is that the third indication information is included in a reserved field of the DCI; or, the third indication information is included in the SIB1 information block.

[0443] In one possible implementation, the first information indicates that the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal is allowed to access the communication device; or, the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the communication device, and the transceiver module 1202 is used to receive second information from the terminal device, the second information being used to indicate that the terminal device is the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal.

[0444] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the first type of REDCAP terminal, or the second type of REDCAP terminal, or the third type of REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, the frequency domain resources, or the code domain resources of the PRACH; or, the second information is carried in Msg3, MsgA, or RRC signaling.

[0445] In one possible implementation, the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the communication device; the transceiver module 1202 is further configured to receive second information from the terminal device, the second information indicating that the terminal device belongs to the REDCAP terminal; the transceiver module 1202 is further configured to receive third information from the communication device, the third information indicating that the terminal device is the first type of REDCAP terminal or the second type of REDCAP terminal.

[0446] One possible implementation is that the second information is carried in a PRACH, the resources of which correspond to the REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH; the third information is carried in Msg3, MsgA, or RRC signaling.

[0447] For other functions that network device 120 can perform, please refer to [link / reference]. Figure 6 The embodiment shown, Figure 7 The method embodiments shown or Figure 8 The relevant descriptions of the embodiments shown will not be elaborated upon further.

[0448] Figure 13 This is a schematic diagram of a chip structure provided in an embodiment of this application. Chip 130 includes one or more processors 1301 and interface circuitry 1302. Optionally, chip 130 may further include a bus 1303. Wherein:

[0449] Processor 1301 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed through integrated logic circuits in the hardware of processor 1301 or through software instructions. Processor 1301 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods and steps disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor.

[0450] Interface circuit 1302 is used for sending or receiving data, instructions, or information. Processor 1301 can process the data, instructions, or other information received by interface circuit 1302, and can send the processed information out through interface circuit 1302.

[0451] Optionally, chip 130 also includes memory, which may include read-only memory and random access memory, and provides operation instructions and data to the processor. A portion of the memory may also include non-volatile random access memory (NVRAM).

[0452] Optionally, the memory stores executable software modules or data structures, and the processor can execute corresponding operations by calling the operation instructions stored in the memory (which may be stored in the operating system).

[0453] Optionally, chip 130 can be used in the communication device (including terminal device or network device) involved in the embodiments of this application. Optionally, interface circuit 1302 can be used to output the execution result of processor 1301. For communication methods provided by one or more embodiments of this application, please refer to the foregoing embodiments, which will not be repeated here.

[0454] It should be noted that the functions of the processor 1301 and the interface circuit 1302 can be implemented through hardware design, software design, or a combination of hardware and software; no restrictions are imposed here.

[0455] Figure 14 A schematic diagram of the composition of a communication system is shown, such as Figure 14 As shown, the communication system 140 may include a terminal device 1401 and a network device 1402. It should be noted that... Figure 14 The accompanying drawings are merely illustrative and are not intended to limit the scope of the embodiments described in this application. Figure 14 The communication system 140 shown includes network elements and the number of network elements.

[0456] Among them, the terminal device 1401 has the above-mentioned Figure 9 The communication device shown can be used to receive first information from network device 1402 indicating whether to allow the first type REDCAP terminal and the second type REDCAP terminal to access network device 1402, and determine whether to access network device 1402 based on the first information.

[0457] Network device 1402 has the above-mentioned features Figure 10 The communication device shown can be used to determine first information indicating whether to allow the first type of REDCAP terminal and the second type of REDCAP terminal to access the network device 1402, and send the first information to the terminal device 1401.

[0458] Alternatively, the terminal device has the above-mentioned features. Figure 11 The communication device shown can be used to receive first information from network device 1402 indicating whether to allow a first type of REDCAP terminal and a second type of REDCAP terminal to access network device 1402, or to receive first information from network device 1402 indicating whether to allow a third type of REDCAP terminal to access network device 1402, and determine whether to access network device 1402 based on the first information.

[0459] Network device 1402 has the above-mentioned features Figure 12 The communication device shown can be used to determine first information indicating whether to allow a first type of REDCAP terminal and a second type of REDCAP terminal to access the network device 1402, or to determine first information indicating whether to allow a third type of REDCAP terminal to access the network device 1402, and send the first information to the terminal device 1401.

[0460] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding network element of the communication system 140, and will not be repeated here.

[0461] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0462] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0463] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0464] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0465] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0466] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for accessing a network device, applied to a terminal device or a chip in a terminal device, characterized in that, The method includes: The system receives a system information block (SIB1) from a network device. SIB1 includes first information indicating whether a degraded REDCAP terminal is allowed to access the network device. The REDCAP terminal has a bandwidth of less than 100MHz. The REDCAP terminal includes a first type of REDCAP terminal and a second type of REDCAP terminal, both operating in the same frequency domain. The first information includes first indication information and second indication information, wherein the first indication information indicates whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information indicates whether the second type of REDCAP terminal is allowed to access the network device. The second type of REDCAP terminal has fewer receiving antennas than the first type of REDCAP terminal. Whether to access the network device is determined based on the first information, wherein the terminal device is either the first type of REDCAP terminal or the second type of REDCAP terminal; When the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device, the method further includes: Send a second message to the network device; the second message is used to indicate that the terminal device belongs to the REDCAP terminal; wherein the second message is carried in message 3Msg3 or message AMsgA, or the second message is carried in the physical random access channel PRACH; The network device sends a third message, which is carried in Radio Resource Control (RRC) signaling, and the third message is used to indicate whether the terminal device is a first type REDCAP terminal or a second type REDCAP terminal.

2. The method according to claim 1, characterized in that, The resources of the PRACH correspond to the REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH.

3. The method according to claim 2, characterized in that, The first type of REDCAP terminal and the second type of REDCAP terminal share the PRACH resources corresponding to the REDCAP terminal.

4. The method according to claim 2 or 3, characterized in that, The PRACH resources configured in the network device include the PRACH resources corresponding to the REDCAP terminal and the PRACH resources corresponding to ordinary terminals.

5. The method according to any one of claims 1-3, characterized in that, The second type of REDCAP terminal has 1 receiving antenna, while the first type of REDCAP terminal has 2 receiving antennas.

6. The method according to any one of claims 1-3, characterized in that, The first type of REDCAP terminal and the second type of REDCAP terminal operate in a frequency range of FR1, where the frequency range of FR1 is less than 6 GHz.

7. The method according to claim 4, characterized in that, The bandwidth of the REDCAP terminal is less than that of the ordinary terminal, and / or the number of receiving antennas of the REDCAP terminal is less than that of the ordinary terminal.

8. A method for sending system information, characterized in that, The method includes: A system information block (SIB1) is sent to the terminal device. The SIB1 includes first information, which indicates whether to allow a reduced-capability REDCAP terminal to access the network device. The bandwidth of the REDCAP terminal is less than 100MHz. The REDCAP terminal includes a first type of REDCAP terminal and a second type of REDCAP terminal. The first type of REDCAP terminal and the second type of REDCAP terminal operate in the same frequency domain. The first information includes first indication information and second indication information. The first indication information indicates whether to allow the first type of REDCAP terminal to access the network device, and the second indication information indicates whether to allow the second type of REDCAP terminal to access the network device. The second type of REDCAP terminal has fewer receiving antennas than the first type of REDCAP terminal. When the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device, the method further includes: Receive second information from the terminal device, the second information being used to indicate that the terminal device belongs to the REDCAP terminal; wherein, the second information is carried in message 3Msg3 or message AMsgA, or the second information is carried in the physical random access channel PRACH; The terminal device receives third information, which is carried in Radio Resource Control (RRC) signaling, and the third information is used to indicate whether the terminal device is a first type REDCAP terminal or a second type REDCAP terminal.

9. The method according to claim 8, characterized in that, The resources of the PRACH correspond to the REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH.

10. The method according to claim 8, characterized in that, The first type of REDCAP terminal and the second type of REDCAP terminal share the PRACH resources corresponding to the REDCAP terminal.

11. The method according to claim 9 or 10, characterized in that, The PRACH resources configured in the network device include the PRACH resources corresponding to the REDCAP terminal and the PRACH resources corresponding to ordinary terminals.

12. The method according to any one of claims 8-10, characterized in that, The second type of REDCAP terminal has 1 receiving antenna, while the first type of REDCAP terminal has 2 receiving antennas.

13. The method according to any one of claims 8-10, characterized in that, The first type of REDCAP terminal and the second type of REDCAP terminal operate in a frequency range of FR1, where the frequency range of FR1 is less than 6 GHz.

14. The method according to claim 11, characterized in that, The bandwidth of the REDCAP terminal is less than that of the ordinary terminal, and / or the number of receiving antennas of the REDCAP terminal is less than that of the ordinary terminal.

15. A communication device, characterized in that, The communication device includes: a transceiver module and a processing module; The transceiver module is configured to receive a system information block (SIB1) from a network device. SIB1 includes first information indicating whether a REDCAP terminal with reduced capability is allowed to access the network device. The REDCAP terminal has a bandwidth of less than 100MHz. The REDCAP terminal includes a first type of REDCAP terminal and a second type of REDCAP terminal, both operating in the same frequency domain. The first information includes first indication information and second indication information, wherein the first indication information indicates whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information indicates whether the second type of REDCAP terminal is allowed to access the network device. The second type of REDCAP terminal has fewer receiving antennas than the first type of REDCAP terminal. The processing module is used to determine whether to access the network device based on the first information, wherein the communication device belongs to the first type of REDCAP terminal or the second type of REDCAP terminal; When the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device, the transceiver module is further configured to: Send a second message to the network device; the second message is used to indicate that the communication device belongs to the REDCAP terminal; wherein the second message is carried in message 3Msg3 or message AMsgA, or the second message is carried in the physical random access channel PRACH; The transceiver module is further configured to send third information to the network device. The third information is carried in Radio Resource Control (RRC) signaling and is used to indicate whether the communication device is a first type REDCAP terminal or a second type REDCAP terminal.

16. The communication device according to claim 15, characterized in that, The resources of the PRACH correspond to the REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH.

17. The communication device according to claim 16, characterized in that, The first type of REDCAP terminal and the second type of REDCAP terminal share the PRACH resources corresponding to the REDCAP terminal.

18. The communication device according to claim 16 or 17, characterized in that, The PRACH resources configured in the network device include the PRACH resources corresponding to the REDCAP terminal and the PRACH resources corresponding to ordinary terminals.

19. The communication device according to any one of claims 15-17, characterized in that, The second type of REDCAP terminal has 1 receiving antenna, while the first type of REDCAP terminal has 2 receiving antennas.

20. The communication device according to any one of claims 15-17, characterized in that, The first type of REDCAP terminal and the second type of REDCAP terminal operate in a frequency range of FR1, where the frequency range of FR1 is less than 6 GHz.

21. The communication device according to claim 18, characterized in that, The bandwidth of the REDCAP terminal is less than that of the ordinary terminal, and / or the number of receiving antennas of the REDCAP terminal is less than that of the ordinary terminal.

22. A communication device, characterized in that, The communication device includes a transceiver module; The transceiver module is used to send a system information block (SIB1) to the terminal device. SIB1 includes first information, which indicates whether a reduced-capacity REDCAP terminal is allowed to access the communication device. The bandwidth of the REDCAP terminal is less than 100MHz. The REDCAP terminal includes a first type of REDCAP terminal and a second type of REDCAP terminal. The first type of REDCAP terminal and the second type of REDCAP terminal operate in the same frequency domain. The first information includes first indication information and second indication information. The first indication information indicates whether the first type of REDCAP terminal is allowed to access the network device, and the second indication information indicates whether the second type of REDCAP terminal is allowed to access the network device. The second type of REDCAP terminal has fewer receiving antennas than the first type of REDCAP terminal. When the first information indicates that the first type of REDCAP terminal and the second type of REDCAP terminal are allowed to access the network device, the transceiver module is further configured to: Receive second information from the terminal device, the second information being used to indicate that the terminal device belongs to the REDCAP terminal; wherein, the second information is carried in message 3Msg3 or message AMsgA, or the second information is carried in the physical random access channel PRACH; The terminal device receives third information, which is carried in Radio Resource Control (RRC) signaling, and the third information is used to indicate whether the terminal device is a first type REDCAP terminal or a second type REDCAP terminal.

23. The communication device according to claim 22, characterized in that, The resources of the PRACH correspond to the REDCAP terminal, and the resources of the PRACH include at least one of the time domain resources, frequency domain resources, or code domain resources of the PRACH.

24. The communication device according to claim 23, characterized in that, The first type of REDCAP terminal and the second type of REDCAP terminal share the PRACH resources corresponding to the REDCAP terminal.

25. The communication device according to claim 23 or 24, characterized in that, The PRACH resources configured in the network device include the PRACH resources corresponding to the REDCAP terminal and the PRACH resources corresponding to ordinary terminals.

26. The communication device according to any one of claims 22-24, characterized in that, The second type of REDCAP terminal has 1 receiving antenna, while the first type of REDCAP terminal has 2 receiving antennas.

27. The communication device according to any one of claims 22-24, characterized in that, The first type of REDCAP terminal and the second type of REDCAP terminal operate in a frequency range of FR1, where the frequency range of FR1 is less than 6 GHz.

28. The communication device according to claim 25, characterized in that, The bandwidth of the REDCAP terminal is less than that of the ordinary terminal, and / or the number of receiving antennas of the REDCAP terminal is less than that of the ordinary terminal.

29. A communication device, characterized in that, include: A processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the apparatus to perform the method as claimed in any one of claims 1 to 7, or the method as claimed in any one of claims 8 to 14.

30. A computer-readable medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1 to 7 or the method as described in any one of claims 8 to 14.

31. A chip, characterized in that, include: A processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the chip to perform the method as claimed in any one of claims 1 to 7 or the method as claimed in any one of claims 8 to 14.

32. A communication system, characterized in that, include: The apparatus as described in any one of claims 15-21, and / or the apparatus as described in any one of claims 22-28.

33. A computer program product containing instructions, characterized in that, It includes computer program code, which, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 7, or the method as described in any one of claims 8 to 14.

Images