Method and apparatus for accessing network device
By sending instructions to REDCAP terminal devices in the NR system and controlling their access number, the problem of network transmission performance degradation caused by the bandwidth and number of antennas of REDCAP devices is solved, and the spectrum efficiency of the network and the reliability of device access is improved.
Patent Information
- Application Number
- JP2024177450
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2020-09-27
- Filing Date
- 2024-10-09
- Publication Date
- 2025-02-04
AI Technical Summary
In NR systems, the REDUCED CAPABILITY (REDCAP) terminal equipment has a narrow bandwidth and a small number of receiving antennas, resulting in a degradation of network transmission performance, especially when a large number of REDCAP devices are accessed, the average spectrum efficiency of the network is reduced.
The first information is sent to the REDCAP terminal device through the network device, indicating whether it is allowed to access the network, and the number of accesses is controlled according to the type of the terminal device (first type and second type REDCAP), and different signaling mechanisms such as MIB, PBCH, DCI and SIB1 are used to ensure transmission performance.
Effectively control the number of REDCAP devices access, improve network transmission performance, avoid over-allocation of resources, and ensure priority access and transmission reliability of REDCAP devices.
Smart Images

Figure 2025016500000001_ABST
Abstract
Description
[Technical field]
[0001] The present application relates to the field of wireless communications, and in particular to a network device access method and apparatus. [Background technology]
[0002] In a new radio (NR) system, a network device (e.g., a base station) broadcasts a synchronization signal / physical broadcast channel block (SSB). When a terminal device intends to access the network to obtain wireless communication services, the terminal device receives the SSB and obtains system information based on the SSB. The system information indicates whether the terminal device is authorized to access the network. If the system information indicates that the terminal device is authorized to access the network, the terminal device subsequently accesses the network by a random access procedure. If the system information indicates that the terminal device is prohibited from accessing the network, the terminal device cannot access the network.
[0003] Currently, a new type of terminal device, namely, reduced capability (REDCAP) terminal, is being considered for introduction in the NR system. Compared with a general terminal in which network access is permitted or not is indicated by SSB, a REDCAP terminal has a longer battery life, lower complexity, and lower cost. Therefore, a REDCAP terminal may be widely applied. However, a REDCAP terminal has a narrower bandwidth or fewer receiving antennas than the general terminal. As a result, a REDCAP terminal has a lower transmission capability than a general terminal. When a large number of REDCAP terminals access the network, the overall transmission performance of the network is degraded. For example, the average spectrum efficiency of the network is degraded. Summary of the Invention
[0004] The present application provides a network device access method and apparatus, so as to control the number of REDCAP terminals accessing a network device and improve network transmission performance.
[0005] In order to achieve the above objectives, the following technical solutions are used in the embodiments of this application.
[0006] According to a first aspect, an embodiment of the present application provides a network device access method, the method includes: a terminal device receives first information from a network device, the first information indicating whether a REDCAP terminal is authorized to access the network device, the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, the first type REDCAP terminal and the second type REDCAP terminal operate in the same frequency range, and 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; and the terminal device determines whether to access the network device based on the first information, the terminal device being a first type REDCAP terminal or a second type REDCAP terminal.
[0007] According to the method provided in the first aspect, the terminal device may receive from the network device first information indicating whether a first-type REDCAP terminal is permitted to access the network device and whether a second-type REDCAP terminal is permitted to access the network device, and 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 so as to ensure the transmission performance of the network managed by the network device.
[0008] In a possible implementation, the first information includes first indication information and second indication information, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether a second type REDCAP terminal is authorized to access the network device, or the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, and the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized to access the network device. Based on the above method, the first indication information and the second indication information may respectively indicate whether a first type REDCAP terminal is authorized to access the network device and whether a second type REDCAP terminal is authorized to access the network. Alternatively, the first indication information and the second indication information may together indicate whether a first type REDCAP terminal is authorized to access the network device and whether a second type REDCAP terminal is authorized to access the network. The indication method is flexible.
[0009] In a possible implementation, the first indication information indicates whether the first type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether the second type REDCAP terminal is authorized to access the network device, and the first indication information includes a spare field in the MIB, and the second indication information includes a reserved field in an additional physical broadcast channel (PBCH) payload, or the first indication information includes a cellBarred field in the MIB, and the second indication information includes a spare field in the MIB, or includes a reserved field in an additional PBCH payload (additional PBCH payload / additional timing-related PBCH payload bits), or includes a field other than the MIB in the PBCH. Based on the above method, the first indication information and the second indication information can separately indicate whether the first type REDCAP terminal is authorized to access the network device. The indications are clear and easy to use.
[0010] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized 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. Based on the above method, whether a first type REDCAP terminal is authorized to access the network device affects whether a second type REDCAP terminal is authorized to access the network device. Therefore, the priority of the first type REDCAP terminal and the second type REDCAP terminal to access the network device can be distinguished to ensure that the terminal type with a higher priority has preferential access to the network device.
[0011] In a possible implementation, the first information is included in an SSB, and the SSB includes a MIB and an additional PBCH payload. Based on the above method, the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the MIB and the additional PBCH payload in the SSB.
[0012] In a possible implementation, the first indication information is included in a reserved field in downlink control information (DCI), the second indication information is included in a reserved field in the DCI, the first indication information is included in a reserved field in the DCI, the second indication information is included in a system information block Type 1 (SIB1) information block, the first indication information is included in a SIB1 information block, the second indication information is included in a reserved field in the DCI, or the first indication information is included in a SIB1 information block, the second indication information is included in a SIB1 information block, and the DCI is used to schedule SIB1. Based on the above method, the network device may indicate whether a REDCAP terminal is authorized to access the network device by using a reserved field in the DCI and / or a SIB1 information block.
[0013] In a possible implementation, the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred 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 cellBarred field in the MIB, and the DCI is used to schedule SIB1. Based on the above method, the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the SSB and the reserved field in the DCI, or the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the SSB and the SIB1 information block.
[0014] In a possible implementation, the first information indicates that a first type REDCAP terminal and / or a second type REDCAP terminal is authorized to access the network device. The method further includes the terminal device sending second information to the network device, where the second information indicates that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal. Based on the above method, the terminal device may report the type of the terminal device to the network device in the second information. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission or downlink transmission, the scheduled frequency range may be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device may use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0015] In a possible implementation, the second information is carried on a physical random access channel (PRACH), the resource of the PRACH corresponds to a first type REDCAP terminal or a second type REDCAP terminal, and the resource of the PRACH includes at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH; or the second information is carried in Msg3, MsgA, or radio resource control (RRC) signaling. Based on the above method, the terminal device may report the type of the terminal device to the network device by using multiple methods such as PRACH resource, Msg3, MsgA, or RRC signaling, so that the network device identifies the type of the terminal device.
[0016] In a possible implementation, the first information indicates that a first type REDCAP terminal and a second type REDCAP terminal are permitted to access the network device. The method further includes: the terminal device transmits second information to the network device, where the second information indicates that the terminal device is a REDCAP terminal; and the terminal device transmits third information to the network device, where the third information indicates that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal. Based on the above method, the terminal device may report the type of the terminal device to the network device in the second information and the third information, so that the network device identifies the type of the terminal device. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission or downlink transmission, the scheduled frequency range may be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device may use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0017] In a possible implementation, the second information is carried by PRACH, the resource of PRACH corresponds to a REDCAP terminal, the resource of PRACH includes at least one of the following: time domain resource of PRACH, frequency domain resource of PRACH, or code domain resource of PRACH, and the third information is carried by Msg3, MsgA, or RRC signaling. Based on the above method, the first type REDCAP terminal can share the PRACH resource with the second type REDCAP terminal. In this way, excessive division of the PRACH resource can be avoided, that is, excessive degradation of random access capability is avoided.
[0018] According to a second aspect, an embodiment of the present application provides a network device access method, the method includes: a network device determines first information, the first information indicating whether a REDCAP terminal is authorized to access the network device, the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, the first type REDCAP terminal and the second type REDCAP terminal operate in the same frequency range, and 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, and the network device transmits the first information to the terminal device.
[0019] According to the method provided in the second aspect, the network device may determine first information indicating whether a first-type REDCAP terminal is authorized to access the network device and whether a second-type REDCAP terminal is authorized to access the network device, and transmit 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 so as to ensure the transmission performance of the network managed by the network device.
[0020] In a possible implementation, the first information includes first indication information and second indication information, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether a second type REDCAP terminal is authorized to access the network device, or the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, and the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized to access the network device. Based on the above method, the first indication information and the second indication information may respectively indicate whether a first type REDCAP terminal is authorized to access the network device and whether a second type REDCAP terminal is authorized to access the network. Alternatively, the first indication information and the second indication information may together indicate whether a first type REDCAP terminal is authorized to access the network device and whether a second type REDCAP terminal is authorized to access the network. The indication method is flexible.
[0021] In a possible implementation, the first indication information indicates whether a first-type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether a second-type REDCAP terminal is authorized to access the network device, and 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, or the first indication information includes a cellBarred field in the MIB, and the second indication information includes a spare field in the MIB or includes a reserved field in the additional PBCH payload. Based on the above method, the first indication information and the second indication information can separately indicate whether a first-type REDCAP terminal is authorized to access the network device. The indication is clear and easy to use.
[0022] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized 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. Based on the above method, whether a first type REDCAP terminal is authorized to access the network device affects whether a second type REDCAP terminal is authorized to access the network device. Therefore, the priority of the first type REDCAP terminal and the second type REDCAP terminal to access the network device can be distinguished to ensure that the terminal type with a higher priority has preferential access to the network device.
[0023] In a possible implementation, the first information is included in an SSB, and the SSB includes a MIB and an additional PBCH payload. Based on the above method, the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the MIB and the additional PBCH payload in the SSB.
[0024] In a possible implementation, the first indication information is included in a reserved field in the DCI, the second indication information is included in a reserved field in the DCI, the first indication information is included in a reserved field in the DCI, the second indication information is included in a SIB1 information block, the first indication information is included in the SIB1 information block, the second 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 the SIB1 information block, and the DCI is used to schedule SIB1. Based on the above method, the network device may indicate whether a REDCAP terminal is authorized to access the network device by using the reserved field in the DCI and / or the SIB1 information block.
[0025] In a possible implementation, the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred 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 cellBarred field in the MIB, and the DCI is used to schedule SIB1. Based on the above method, the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the SSB and the reserved field in the DCI, or the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the SSB and the SIB1 information block.
[0026] In a possible implementation, the first information indicates that a first type REDCAP terminal and / or a second type REDCAP terminal is authorized to access the network device. The method further includes the network device receiving second information from the terminal device, where the second information indicates that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal. Based on the above method, the network device may receive the second information from the terminal device and determine that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal by using the second information. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission or downlink transmission, the scheduled frequency range may be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device may use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0027] In a possible implementation, the second information is carried in a PRACH, and the resource of the PRACH corresponds to a first type REDCAP terminal or a second type REDCAP terminal, and the resource of the PRACH includes at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH, or the second information is carried in Msg3, MsgA, or RRC signaling. Based on the above method, the network device may determine the type of the terminal device by using multiple methods such as a PRACH resource, Msg3, MsgA, or RRC signaling.
[0028] In a possible implementation, the first information indicates that a first type REDCAP terminal and a second type REDCAP terminal are permitted 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; and the network device receiving third information from the terminal device, the third information indicating that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal. Based on the above method, the network device may determine that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal by using the second information and the third information. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission or downlink transmission, the scheduled frequency range may be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device may use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0029] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a REDCAP terminal, the resources of the PRACH include at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH, and the third information is carried in Msg3, MsgA, or RRC signaling. Based on the above method, the network device can determine the type of the terminal device by combining the PRACH resources with Msg3, MsgA, or RRC signaling.
[0030] According to a third aspect, an embodiment of the present application provides a communication device to implement the method according to the first aspect or any one of the possible implementations of the first aspect. The device includes corresponding units or components configured to execute the above method. The units included in the device may be implemented by software and / or hardware. The device may be a terminal or, for example, a chip, a chip system, or a processor capable of assisting a terminal to implement the above method.
[0031] According to a fourth aspect, an embodiment of the present application provides a communication device to implement the method according to the second aspect or any one of the possible implementations of the second aspect. The device comprises corresponding units or components configured to execute the above method. The units included in the device may be implemented by software and / or hardware. The device may be a network device or a chip, a chip system, or a processor that can for example assist the network device to implement the above method.
[0032] According to a fifth aspect, an embodiment of the present application provides a communication device including a processor, the processor coupled to a memory, the memory configured to store a program or instructions, which when executed by the processor, can cause the device to perform a method according to the first aspect or any one of the possible implementations of the first aspect.
[0033] According to a sixth aspect, an embodiment of the present application provides a communication device including a processor, the processor coupled to a memory, the memory configured to store a program or instructions, which when executed by the processor, can cause the device to perform a method according to the second aspect or any one of the possible implementations of the second aspect.
[0034] According to a seventh aspect, an embodiment of the present application provides a communication device, the device being configured to perform a method according to the first aspect or any one of the possible implementations of the first aspect.
[0035] According to an eighth aspect, an embodiment of the present application provides a communication device, the device being configured to perform a method according to the second aspect or any one of the possible implementations of the second aspect.
[0036] According to a ninth aspect, an embodiment of the present application provides a computer readable medium having stored thereon a computer program or instructions which, when executed, cause a computer to perform a method according to the first aspect or any one of the possible implementations of the first aspect.
[0037] According to a ninth aspect, an embodiment of the present application provides a computer readable medium having stored thereon a computer program or instructions which, when executed, causes a computer to perform a method according to the second aspect or any one of the possible implementations of the second aspect.
[0038] According to an eleventh aspect, an embodiment of the present application provides a computer program product, comprising computer program code, which when executed on a computer, causes the computer to perform a method according to the first aspect or any one of the possible implementations of the first aspect.
[0039] According to a twelfth aspect, an embodiment of the present application provides a computer program product, comprising computer program code, which when executed on a computer, causes the computer to perform a method according to the second aspect or any one of the possible implementations of the second aspect.
[0040] According to a thirteenth aspect, an embodiment of the present application provides a chip including a processor, the processor coupled to a memory, the memory configured to store programs or instructions, the programs or instructions being executed by the processor causing the chip to perform a method according to the first aspect or any one of the possible implementations of the first aspect.
[0041] According to a fourteenth aspect, an embodiment of the present application provides a chip including a processor, the processor coupled to a memory, the memory configured to store programs or instructions, the programs or instructions being executed by the processor causing the chip to perform a method according to the second aspect or any one of the possible implementations of the second aspect.
[0042] According to a fifteenth aspect, an embodiment of the present application provides a communication system, the system comprising an apparatus according to the third aspect and / or an apparatus according to the fourth aspect, the system comprising an apparatus according to the fifth aspect and / or an apparatus according to the sixth aspect, or the system comprising an apparatus according to the seventh aspect and / or an apparatus according to the eighth aspect.
[0043] It can be understood that any of the above-mentioned communication devices, chips, computer-readable media, computer program products, communication systems, etc. are configured to perform the above-mentioned corresponding methods. Therefore, for advantageous effects that can be achieved by the communication devices, chips, computer-readable media, computer program products, communication systems, etc., please refer to the advantageous effects of the corresponding methods. Details will not be described again here.
[0044] According to a sixteenth aspect, an embodiment of the present application provides a network device access method, the method including: a terminal device receiving first information from a network device, the first information indicating whether a REDCAP terminal is authorized 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 range, the frequency range in which the third type REDCAP terminal operates is different from the frequency range in which the first type REDCAP terminal and the second type REDCAP terminal operate, 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; and determining whether the terminal device should access the network device based on the first information, the terminal device being a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal.
[0045] According to the method provided in the sixteenth aspect, the terminal device may receive from the network device first information indicating whether a first-type REDCAP terminal is permitted to access the network device and whether a second-type REDCAP terminal is permitted to access the network device, or receive from the network device first information indicating whether a third-type REDCAP terminal is permitted to access the network device, and 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, or the number of third-type REDCAP terminals accessing the network device, in order to ensure the transmission performance of the network managed by the network device.
[0046] In a possible implementation, the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, and the first information includes first indication information and second indication information, where the first indication information indicates whether the first type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether the second type REDCAP terminal is authorized to access the network device, or the first indication information indicates whether the first type REDCAP terminal is authorized to access the network device, and the first indication information and the second indication information indicate whether the second type REDCAP terminal is authorized to access the network device. Based on the above method, the first indication information and the second indication information may respectively indicate whether the first type REDCAP terminal is authorized to access the network device and whether the second type REDCAP terminal is authorized to access the network. Alternatively, the first indication information and the second indication information may together indicate whether the first type REDCAP terminal is authorized to access the network device and whether the second type REDCAP terminal is authorized to access the network. The indication method is flexible.
[0047] In a possible implementation, the first indication information indicates whether a first-type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether a second-type REDCAP terminal is authorized to access the network device, and 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, or the first indication information includes a cellBarred field in the MIB, and the second indication information includes a spare field in the MIB or includes a reserved field in the additional PBCH payload. Based on the above method, the first indication information and the second indication information can separately indicate whether a first-type REDCAP terminal is authorized to access the network device. The indication is clear and easy to use.
[0048] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized 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. Based on the above method, whether a first type REDCAP terminal is authorized to access the network device affects whether a second type REDCAP terminal is authorized to access the network device. Therefore, the priority of the first type REDCAP terminal and the second type REDCAP terminal to access the network device can be distinguished to ensure that the terminal type with a higher priority has preferential access to the network device.
[0049] In a possible implementation, the first indication information is included in a reserved field in the DCI, the second indication information is included in a reserved field in the DCI, the first indication information is included in a reserved field in the DCI, the second indication information is included in a SIB1 information block, the first indication information is included in the SIB1 information block, the second 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 the SIB1 information block, and the DCI is used to schedule SIB1. Based on the above method, the network device may indicate whether a REDCAP terminal is authorized to access the network device by using the reserved field in the DCI and / or the SIB1 information block.
[0050] In a possible implementation, the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred 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 cellBarred field in the MIB, and the DCI is used to schedule SIB1. Based on the above method, the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the SSB and the reserved field in the DCI, or the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the SSB and the SIB1 information block.
[0051] In a possible implementation, the REDCAP terminal includes a third type REDCAP terminal, the first information includes third indication information, and the third indication information indicates whether the third type REDCAP terminal is authorized to access the network device. Based on the above method, the network device can indicate whether the third type REDCAP terminal is authorized to access the network device by using the third indication information.
[0052] In a possible implementation, the third indication information includes a spare field in the MIB, or the third indication information includes a cellBarred field in the MIB. Based on the above method, the network device can indicate whether the third type REDCAP terminal is permitted to access the network device by using the spare field in the MIB, or can indicate whether the third type REDCAP terminal is permitted to access the network device by using the cellBarred field in the MIB. The indication method is flexible.
[0053] In a possible implementation, the first information is included in an SSB, and the SSB includes a MIB and an additional PBCH payload. Based on the above method, the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the MIB and the additional PBCH payload in the SSB.
[0054] In a possible implementation, the third indication information is included in a reserved field in the DCI, or the third indication information is included in the SIB1 information block. Based on the above method, the network device can indicate whether the third type REDCAP terminal is authorized to access the network device by using a reserved field in the DCI, or can indicate whether the third type REDCAP terminal is authorized to access the network device by using the SIB1 information block. The indication method is flexible.
[0055] In a possible implementation, the first information indicates that a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal is permitted to access the network device, or the first indication information indicates whether a first type REDCAP terminal and a second type REDCAP terminal are permitted to access the network device. The method further includes the terminal device sending the second information to the network device, where the second information indicates that the terminal device is a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal. Based on the above method, the terminal device may report the type of the terminal device to the network device in the second information. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission or downlink transmission, the scheduled frequency range may be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device may use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0056] In a possible implementation, the second information is carried in the PRACH, and the resource of the PRACH corresponds to a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal, and the resource of the PRACH includes at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH, or the second information is carried in Msg3, MsgA, or RRC signaling. Based on the above method, the terminal device may report the type of the terminal device to the network device by using multiple methods such as the PRACH resource, Msg3, MsgA, or RRC signaling, so that the network device identifies the type of the terminal device.
[0057] In a possible implementation, the first information indicates that a first type REDCAP terminal and a second type REDCAP terminal are permitted to access the network device. The method further includes: the terminal device transmits second information to the network device, where the second information indicates that the terminal device is a REDCAP terminal; and the terminal device transmits third information to the network device, where the third information indicates that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal. Based on the above method, the terminal device may report the type of the terminal device to the network device in the second information and the third information, so that the network device identifies the type of the terminal device. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission or downlink transmission, the scheduled frequency range may be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device may use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0058] In a possible implementation, the second information is carried by PRACH, the resource of PRACH corresponds to a REDCAP terminal, the resource of PRACH includes at least one of the following: time domain resource of PRACH, frequency domain resource of PRACH, or code domain resource of PRACH, and the third information is carried by Msg3, MsgA, or RRC signaling. Based on the above method, the first type REDCAP terminal can share the PRACH resource with the second type REDCAP terminal. In this way, excessive division of the PRACH resource can be avoided, that is, excessive degradation of random access capability is avoided.
[0059] According to a seventeenth aspect, an embodiment of the present application provides a network device access method, the method includes: a network device determining first information, the first information indicating whether a REDCAP terminal is authorized 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 range, the frequency range in which the third type REDCAP terminal operates is different from the frequency range in which the first type REDCAP terminal and the second type REDCAP terminal operate, 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, and the network device transmits the first information to the terminal device.
[0060] According to the method provided in the seventeenth aspect, the network device may determine first information indicating whether a first-type REDCAP terminal is permitted to access the network device and whether a second-type REDCAP terminal is permitted to access the network device, or determine first information indicating whether a third-type REDCAP terminal is permitted to access the network device, and transmit 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.
[0061] In a possible implementation, the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, and the first information includes first indication information and second indication information, where the first indication information indicates whether the first type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether the second type REDCAP terminal is authorized to access the network device, or the first indication information indicates whether the first type REDCAP terminal is authorized to access the network device, and the first indication information and the second indication information indicate whether the second type REDCAP terminal is authorized to access the network device. Based on the above method, the first indication information and the second indication information may respectively indicate whether the first type REDCAP terminal is authorized to access the network device and whether the second type REDCAP terminal is authorized to access the network. Alternatively, the first indication information and the second indication information may together indicate whether the first type REDCAP terminal is authorized to access the network device and whether the second type REDCAP terminal is authorized to access the network. The indication method is flexible.
[0062] In a possible implementation, the first indication information indicates whether a first-type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether a second-type REDCAP terminal is authorized to access the network device, and 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, or the first indication information includes a cellBarred field in the MIB, and the second indication information includes a spare field in the MIB or includes a reserved field in the additional PBCH payload. Based on the above method, the first indication information and the second indication information can separately indicate whether a first-type REDCAP terminal is authorized to access the network device. The indication is clear and easy to use.
[0063] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized 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. Based on the above method, whether a first type REDCAP terminal is authorized to access the network device affects whether a second type REDCAP terminal is authorized to access the network device. Therefore, the priority of the first type REDCAP terminal and the second type REDCAP terminal to access the network device can be distinguished to ensure that the terminal type with a higher priority has preferential access to the network device.
[0064] In a possible implementation, the first indication information is included in a reserved field in the DCI, the second indication information is included in a reserved field in the DCI, the first indication information is included in a reserved field in the DCI, the second indication information is included in a SIB1 information block, the first indication information is included in the SIB1 information block, the second 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 the SIB1 information block, and the DCI is used to schedule SIB1. Based on the above method, the network device may indicate whether a REDCAP terminal is authorized to access the network device by using the reserved field in the DCI and / or the SIB1 information block.
[0065] In a possible implementation, the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred 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 cellBarred field in the MIB, and the DCI is used to schedule SIB1. Based on the above method, the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the SSB and the reserved field in the DCI, or the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the SSB and the SIB1 information block.
[0066] In a possible implementation, the REDCAP terminal includes a third type REDCAP terminal, the first information includes third indication information, and the third indication information indicates whether the third type REDCAP terminal is authorized to access the network device. Based on the above method, the network device can indicate whether the third type REDCAP terminal is authorized to access the network device by using the third indication information.
[0067] In a possible implementation, the third indication information includes a spare field in the MIB, or the third indication information includes a cellBarred field in the MIB. Based on the above method, the network device can indicate whether the third type REDCAP terminal is allowed to access the network device by using the spare field in the MIB or the cellBarred field in the MIB. The indication method is flexible.
[0068] In a possible implementation, the first information is included in an SSB, and the SSB includes a MIB and an additional PBCH payload. Based on the above method, the network device can indicate whether a REDCAP terminal is authorized to access the network device by using the MIB and the additional PBCH payload in the SSB.
[0069] In a possible implementation, the third indication information is included in a reserved field in the DCI, or the third indication information is included in the SIB1 information block. Based on the above method, the network device can indicate whether the third type REDCAP terminal is authorized to access the network device by using a reserved field in the DCI, or can indicate whether the third type REDCAP terminal is authorized to access the network device by using the SIB1 information block. The indication method is flexible.
[0070] In a possible implementation, the first information indicates that a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal is permitted to access the network device, or the first indication information indicates whether a first type REDCAP terminal and a second type REDCAP terminal are permitted to access the network device. The method further includes the network device receiving second information from the terminal device, where the second information indicates that the terminal device is a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal. Based on the above method, the network device may receive the second information from the terminal device and determine that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal by using the second information. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission or downlink transmission, the scheduled frequency range may be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device may use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0071] In a possible implementation, the second information is carried in the PRACH, and the resource of the PRACH corresponds to a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal, and the resource of the PRACH includes at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH, or the second information is carried in Msg3, MsgA, or RRC signaling. Based on the above method, the network device may determine the type of the terminal device by using multiple methods such as the PRACH resource, Msg3, MsgA, or RRC signaling.
[0072] In a possible implementation, the first information indicates that a first type REDCAP terminal and a second type REDCAP terminal are permitted 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; and the network device receiving third information from the terminal device, the third information indicating that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal. Based on the above method, the network device may determine that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal by using the second information and the third information. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission or downlink transmission, the scheduled frequency range may be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device may use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0073] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a REDCAP terminal, the resources of the PRACH include at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH, and the third information is carried in Msg3, MsgA, or RRC signaling. Based on the above method, the network device can determine the type of the terminal device by combining the PRACH resources with Msg3, MsgA, or RRC signaling.
[0074] According to an eighteenth aspect, an embodiment of the present application provides a communication device, the communication device includes a receiving module and a processing module. The receiving module is configured to receive first information from a network device, the first information indicating whether a REDCAP terminal is authorized 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 range, the frequency range in which the third type REDCAP terminal operates is different from the frequency range in which the first type REDCAP terminal and the second type REDCAP terminal operate, 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. The processing module is configured to determine whether to access the network device based on the first information, the communication device is a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal.
[0075] In a possible implementation, the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, and the first information includes first instruction information and second instruction information, where the first instruction information indicates whether the first type REDCAP terminal is authorized to access the network device and the second instruction information indicates whether the second type REDCAP terminal is authorized to access the network device, or the first instruction information indicates whether the first type REDCAP terminal is authorized to access the network device and the first instruction information and the second instruction information indicate whether the second type REDCAP terminal is authorized to access the network device.
[0076] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether a second type REDCAP terminal is authorized to access the network device, and 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, or the first indication information includes a cellBarred field in the MIB and the second indication information includes a spare field in the MIB or a reserved field in the additional PBCH payload.
[0077] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized 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.
[0078] In a possible implementation, the first indication information is included in a reserved field in the DCI, the second indication information is included in a reserved field in the DCI, the first indication information is included in a reserved field in the DCI and the second indication information is included in a SIB1 information block, the first indication information is included in the SIB1 information block and the second 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 the SIB1 information block, and the DCI is used to schedule SIB1.
[0079] In a possible implementation, the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred 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 cellBarred field in the MIB, and the DCI is used to schedule SIB1.
[0080] In a possible implementation, the REDCAP terminal includes a third type REDCAP terminal, the first information includes third indication information, and the third indication information indicates whether the third type REDCAP terminal is authorized to access the network device.
[0081] In a possible implementation, the third indication information includes a spare field in the MIB, or the third indication information includes a cellBarred field in the MIB.
[0082] In a possible implementation, the first information is included in an SSB, which includes a MIB and additional PBCH payload.
[0083] In a possible implementation, the third indication information is included in a reserved field in the DCI, or the third indication information is included in the SIB1 information block.
[0084] In a possible implementation, the first information indicates that a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal is authorized to access the network device, or the first indication information indicates whether a first type REDCAP terminal and a second type REDCAP terminal are authorized 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, where the second information indicates that the communication device is a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal.
[0085] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal, and the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, or the second information is carried in Msg3, MsgA, or RRC signaling.
[0086] In a possible implementation, the first information indicates that a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the network device. The sending module is further configured to send second information to the network device, the second information indicating that the communication device is a REDCAP terminal. The sending module is further configured to send third information to the network device, the third information indicating that the communication device is a first type REDCAP terminal or a second type REDCAP terminal.
[0087] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a REDCAP terminal, the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, and the third information is carried in Msg3, MsgA, or RRC signaling.
[0088] According to a nineteenth aspect, an embodiment of the present application provides a communication device, the communication device includes a processing module and a transmitting module. The processing module is configured to determine first information, the first information indicating whether a REDCAP terminal is authorized to access the communication 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 range, the frequency range in which the third type REDCAP terminal operates is different from the frequency range in which the first type REDCAP terminal and the second type REDCAP terminal operate, 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. The transmitting module is configured to transmit the first information to the terminal device.
[0089] In a possible implementation, the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, and the first information includes first indication information and second indication information, where the first indication information indicates whether the first type REDCAP terminal is authorized to access the communication device and the second indication information indicates whether the second type REDCAP terminal is authorized to access the communication device, or the first indication information indicates whether the first type REDCAP terminal is authorized to access the communication device and the first indication information and the second indication information indicate whether the second type REDCAP terminal is authorized to access the communication device.
[0090] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the communication device, and the second indication information indicates whether a second type REDCAP terminal is authorized to access the communication device, and 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, or the first indication information includes a cellBarred field in the MIB and the second indication information includes a spare field in the MIB or includes a reserved field in the additional PBCH payload.
[0091] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the communication device, the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized 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.
[0092] In a possible implementation, the first indication information is included in a reserved field in the DCI, the second indication information is included in a reserved field in the DCI, the first indication information is included in a reserved field in the DCI and the second indication information is included in a SIB1 information block, the first indication information is included in the SIB1 information block and the second 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 the SIB1 information block, and the DCI is used to schedule SIB1.
[0093] In a possible implementation, the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred 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 cellBarred field in the MIB, and the DCI is used to schedule SIB1.
[0094] In a possible implementation, the REDCAP terminal includes a third type REDCAP terminal, the first information includes third indication information, and the third indication information indicates whether the third type REDCAP terminal is authorized to access the communication device.
[0095] In a possible implementation, the third indication information includes a spare field in the MIB, or the third indication information includes a cellBarred field in the MIB.
[0096] In a possible implementation, the first information is included in an SSB, which includes a MIB and additional PBCH payload.
[0097] In a possible implementation, the third indication information is included in a reserved field in the DCI, or the third indication information is included in the SIB1 information block.
[0098] In a possible implementation, the first information indicates that a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal is authorized to access the communication device, or the first indication information indicates whether a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the communication device. The communication device further includes a receiving module. The receiving module is configured to receive second information from the terminal device, the second information indicating that the terminal device is a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal.
[0099] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal, and the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, or the second information is carried in Msg3, MsgA, or RRC signaling.
[0100] In a possible implementation, the first information indicates that a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the communication device. The receiving module is further configured to receive second information from the terminal device, the second information indicating that the terminal device is a REDCAP terminal. The receiving module is further configured to receive third information from the terminal device, the third information indicating that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal.
[0101] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a REDCAP terminal, the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, and the third information is carried in Msg3, MsgA, or RRC signaling.
[0102] According to a twentieth aspect, an embodiment of the present application provides a communication device including a processor. The processor is coupled to a memory, the memory being configured to store programs or instructions. When the programs or instructions are executed by the processor, the device can perform a method according to the sixteenth aspect or any one of the sixteenth possible implementations.
[0103] According to a twenty-first aspect, an embodiment of the present application provides a communication device including a processor. The processor is coupled to a memory, the memory being configured to store a program or instructions. When the program or instructions are executed by the processor, the device can perform a method according to the seventeenth aspect or any one of the seventeenth possible implementations.
[0104] According to a twenty-second aspect, an embodiment of the present application provides a communication device, the device being capable of implementing the method according to the sixteenth aspect or any one of the sixteenth possible implementations.
[0105] According to a twenty-third aspect, an embodiment of the present application provides a communication device, the device being capable of implementing the method according to the seventeenth aspect or any one of the seventeenth possible implementations.
[0106] According to a twenty-fourth aspect, an embodiment of the present application provides a computer readable medium, the computer readable medium storing a computer program or instructions, which when executed can cause a computer to perform a method according to the sixteenth aspect or any one of the sixteenth possible implementations.
[0107] According to a twenty-fifth aspect, an embodiment of the present application provides a computer readable medium, the computer readable medium storing a computer program or instructions which, when executed, can cause a computer to perform a method according to the seventeenth aspect or any one of the seventeenth possible implementations.
[0108] According to a twenty-sixth aspect, an embodiment of the present application provides a computer program product, the computer program product comprising computer program code which, when executed on a computer, enables the computer to perform a method according to the sixteenth aspect or any one of the sixteenth possible implementations.
[0109] According to a twenty-seventh aspect, an embodiment of the present application provides a computer program product, the computer program product comprising computer program code which, when executed on a computer, enables the computer to perform a method according to the seventeenth aspect or any one of the seventeenth possible implementations.
[0110] According to a twenty-eighth aspect, an embodiment of the present application provides a chip including a processor, the processor coupled to a memory, the memory configured to store programs or instructions, the programs or instructions being executed by the processor causing the chip to perform a method according to the sixteenth aspect or any one of the sixteenth possible implementations.
[0111] According to a twenty-ninth aspect, an embodiment of the present application provides a chip including a processor. The processor is coupled to a memory, the memory configured to store programs or instructions. When the programs or instructions are executed by the processor, the chip can perform a method according to the seventeenth aspect or any one of the seventeenth possible implementations.
[0112] According to a thirtieth aspect, an embodiment of the present application provides a communication system, the system comprising an apparatus according to the eighteenth aspect and / or an apparatus according to the nineteenth aspect, the system comprising an apparatus according to the twentieth aspect and / or an apparatus according to the twenty-first aspect, or the system comprising an apparatus according to the twenty-second aspect and / or an apparatus according to the twenty-third aspect.
[0113] It can be understood that any of the above-mentioned communication devices, chips, computer-readable media, computer program products, communication systems, etc. are configured to perform the above-mentioned corresponding methods. Therefore, for advantageous effects that can be achieved by the communication devices, chips, computer-readable media, computer program products, communication systems, etc., please refer to the advantageous effects of the corresponding methods. Details will not be described again here. [Brief description of the drawings]
[0114] [Figure 1] FIG. 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application; [Diagram 2] FIG. 2 is a schematic diagram of a hardware structure of a communication device according to an embodiment of the present application; [Diagram 3] 1 is a first schematic flowchart of a network device access method according to an embodiment of the present application; [Figure 4] 2 is a second schematic flowchart of a network device access method according to an embodiment of the present application; [Diagram 5] 4 is a third schematic flowchart of a network device access method according to an embodiment of the present application. [Figure 6] 4 is a fourth schematic flowchart of a network device access method according to an embodiment of the present application. [Figure 7] 5 is a fifth schematic flowchart of a network device access method according to an embodiment of the present application. [Figure 8] 6 is a sixth schematic flowchart of a network device access method according to an embodiment of the present application. [Figure 9] FIG. 1 is a first schematic diagram of a structure of a communication device according to an embodiment of the present application. [Figure 10] FIG. 2 is a second schematic diagram of the structure of a communication device according to an embodiment of the present application. [Figure 11] FIG. 13 is a third schematic diagram of the structure of a communication device according to an embodiment of the present application. [Figure 12] FIG. 4 is a fourth schematic diagram of the structure of a communication device according to an embodiment of the present application. [Figure 13] FIG. 2 is a schematic diagram of a chip structure according to an embodiment of the present application. [Figure 14] FIG. 1 is a schematic diagram of a configuration of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0115] The following provides a detailed description of implementations of the present application with reference to the accompanying drawings.
[0116] The method provided in the embodiment of the present application may be applied to various communication systems. For example, the communication system may be a 5th generation (5G) communication system, a new radio (NR) system, a 3rd generation partnership project (3GPP) related communication system, a future evolved communication system, etc. This is not limited. The following only uses the communication system 10 shown in FIG. 1 as an example to describe the method provided in the embodiment of the present application.
[0117] Fig. 1 is a schematic diagram of an architecture of a communication system 10 according to an embodiment of the present application. In Fig. 1, the communication system 10 may include one or more network devices 101 (only one network device is shown here) and terminal devices 102 to 104 that can communicate with the network device 101. Fig. 1 is merely a schematic diagram and does not constitute a limitation on applicable scenarios of the technical solution provided in the present application.
[0118] In FIG. 1, a network device may provide a wireless access service for a terminal device. Specifically, each network device corresponds to one service coverage area. A terminal device that enters the area may communicate with the network device through a Uu interface to receive the wireless access service provided by the network device. The terminal device and the network device may communicate with each other through a Uu interface link. The Uu interface link may be classified into an uplink (UL) and a downlink (DL) based on the direction of data transmission on the Uu interface link. Uplink data transmitted from the terminal device to the network device may be transmitted in the UL, and downlink data transmitted from the network device to the terminal device may be transmitted in the DL. For example, in FIG. 1, the terminal device 103 is located in the coverage area of the network device 101. The network device 101 may transmit downlink data to the terminal device 103 through the DL, and the terminal device 103 may transmit uplink data to the network device 101 through the UL.
[0119] The network device in FIG. 1, for example, the network device 101, may be any device with a radio transceiver function. The network device includes, but is not limited to, a base station (gNodeB or gNB) or a transmission receiving point / transmission reception point (TRP) in NR, a base station in evolved 3GPP, etc. The base station may be a macro base station, a micro base station, a picocell base station, a small base station, a relay station, a balloon station, etc. Multiple base stations may support the above network using the same technology, or may support the above network using different technologies. The base station may include one or more co-located or non-co-located TRPs. The network device may alternatively be a radio controller, a central unit (CU), and / or a distributed unit (DU) in a cloud radio access network (CRAN) scenario. The network device may alternatively be a server, a wearable device, a machine communication device, an in-vehicle device, etc. The network device being a base station is used as an example for the following description. The network devices may be the same type of base station or may be different types of base stations. A base station may communicate with a terminal device or may communicate with the terminal device through a relay station.
[0120] The terminal device in FIG. 1, for example, the terminal device 102, the terminal device 103, or the terminal device 104, is a device equipped with a wireless transceiver function and may be deployed on the ground, where the deployment includes indoor, outdoor, handheld, wearable, or vehicle-mounted deployment, may be deployed on water (e.g., on a ship), or may be deployed in the air (e.g., on an aircraft, a balloon, and a satellite). The terminal device may be a mobile phone, a tablet computer (Pad), a computer equipped with a wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a terminal in industrial control, an in-vehicle terminal, a terminal in self-driving, a terminal in assisted driving, a terminal in remote medical, a terminal in a smart grid, a terminal in transportation safety, a terminal in a smart city, a terminal in a smart home, etc. The application scenario is not limited by the embodiments of the present application. A terminal equipment may also sometimes be referred to as a terminal device, user equipment (UE), access terminal, vehicle mounted terminal, industrial control terminal, UE unit, UE station, mobile station, remote station, remote terminal, mobile device, UE terminal device, wireless communication device, machine terminal, UE agent, UE equipment, etc. A terminal equipment may be fixed or mobile.
[0121] By way of example and not of limitation, the terminal device of the present application may be a wearable device. A wearable device may also be called a wearable intelligent device, which is a general term for wearable devices, such as glasses, gloves, watches, clothes, and shoes, that are intelligently designed and developed for daily wear by using wearable technology. A wearable device is a portable device that can be directly worn on the body or integrated into the user's clothes or ornaments. A wearable device is not only a hardware device, but also implements powerful functions through software assistance, data exchange, and cloud interaction. Generalized wearable intelligent devices include full-function and large-scale devices that can implement full or partial functions without relying on a smartphone, such as smart watches or smart glasses, and devices that focus only on one type of application and need to work with other devices, such as smartphones, such as various smart bands or smart jewelry for monitoring physical symptoms.
[0122] In the present application, the terminal device may be a terminal in an internet of things (IoT) system. IoT is an important component of the future development of information technology. The main technical feature of IoT is to connect objects to a network by using communication technologies to implement an intelligent network of human-machine and object-object interconnections. The terminal device of the present application may be a terminal in machine type communication (MTC). The terminal device of the present application may be an on-board module, on-board component, on-board chip, or on-board unit configured in a vehicle as one or more components or units. The vehicle may implement the method of the present application by using the on-board module, on-board component, on-board chip, or on-board unit configured in the vehicle.
[0123] In the communication system 10 shown in Fig. 1, the network device 101 transmits SSB in a broadcast manner. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The PBCH includes a master information block (MIB) and an additional PBCH payload (or additional timing-related PBCH payload). For the description of PSS and SSS, please refer to the description in the prior art. Details will not be described.
[0124] The MIB includes at least one of the following information: a system frame number (SFN), a common subcarrier spacing (subCarrierSpacingCommon), an SSB subcarrier offset (ssb-SubcarrierOffset), a symbol position (dmrs-TypeA-Position) of a demodulation reference signal (DMRS) in one slot, configuration information of a control resource set (CORESET) #0 and a common search space of type 0 (pdcch-ConfigSIB1), a cellBarred (cellBarred) field, an intraFreqReselection (intraFreqReselection) field, or a spare field. For the description of SFN, common subcarrier spacing, SSB subcarrier offset, DMRS symbol position within one slot, CORESET #0 configuration information and common search space of type 0, cellBarred field, intraFreqReselection field, and spare field, please refer to the explanation and description in the prior art, and details will not be described.
[0125] The additional PBCH payload includes information other than the MIB in the PBCH. For example, the frequency range in which the communication system 10 operates is frequency range 1 (FR1), and specifically, the operating frequency of the communication system 10 is less than 6 GHz. The additional PBCH payload includes at least one of the following information: an SFN supplementary field, a half-frame indicator field, an indicator field indicating the most significant bit (MSB) bit of the SSB subcarrier offset, or a reserved field. For the description of the SFN supplementary field, the half-frame indicator field, the indicator field indicating the MSB bit of the SSB subcarrier offset, and the reserved field, please refer to the description and description in the prior art. Details will not be described.
[0126] For example, the frequency range in which the communication system 10 operates is frequency range 2 (FR2), specifically, the operating frequency of the communication system 10 is 6 GHz or higher. The additional PBCH payload includes at least one of the following information: a SFN supplementary field, a half-frame indicator field, or an indicator field indicating the three most significant bits of the SSB index. For the description of the SFN supplementary field, the half-frame indicator field, and the indicator field indicating the three most significant bits of the SSB index, please refer to the description and description in the prior art. Details will not be described.
[0127] When a terminal device, for example, terminal device 102, terminal device 103, or terminal device 104, intends to access the network device 101, the terminal device receives an SSB and receives downlink control information (DCI) based on a PBCH in the SSB, where the DCI is for scheduling a system information block Type 1 (SIB1), and the SIB1 includes a SIB1 information block. After receiving the DCI, the terminal device may receive SIB1 based on the DCI and obtain random access channel (RACH) configuration information in the SIB1 information block. The RACH configuration information includes random access related parameters, for example, time domain resources of a random access preamble and / or frequency domain resources of the preamble. After that, the terminal device may initiate a random access procedure to access the network device 101.
[0128] For example, the terminal device may access the network device 101 in the following four-step RACH scheme or two-step RACH scheme: An example in which the terminal device 102 initiates a random access procedure is used below for description.
[0129] (1) Four-Step RACH Scheme The process in which the terminal apparatus 102 accesses the network device 101 in the four-step RACH scheme may include the following steps 1 to 4.
[0130] Step 1: The terminal device 102 sends a random access request to the network device 101 .
[0131] Sending a random access request is referred to as sending a random access preamble, which is also called the first message or message 1 (Msg1) in the random access procedure.
[0132] 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.
[0133] The random access response is also called the second message or message (Msg2) in the random access procedure.
[0134] Step 3: The terminal device 102 receives the RAR from the network device 101 and transmits uplink data to the network device 101.
[0135] The uplink data is also referred to as the third message or message 3 (Msg3) in the random access procedure. In one case, Msg3 includes control plane data (CP data), such as radio resource control (RRC) information. For example, the RRC information includes an RRC connection establishment request, an RRC connection resume request, etc. In another case, Msg3 includes control plane data and user plane data.
[0136] Step 4: The network device 101 receives uplink data from the terminal device 102 and sends a contention resolution message to the terminal device 102.
[0137] In response, the terminal device 102 receives a contention resolution message from the network device 101 .
[0138] The contention resolution message is also called the fourth message or message 4 (Msg4) in the random access procedure.
[0139] (2) Two-step RACH Method The process in which the terminal device 102 accesses the network device 101 in the two-step RACH method may include the following steps a and b.
[0140] Step a: The terminal device 102 transmits a message A (MsgA) to the network device 101 .
[0141] MsgA includes a random access preamble and a physical uplink shared channel (PUSCH). MsgA in step a is equivalent to Msg1 in step 1 and Msg3 in step 3. Alternatively, it may be understood as "sending Msg1 and Msg3 together."
[0142] Step b: The network device 101 receives MsgA from the terminal device 102 and transmits a message B (MsgB) to the terminal device 102.
[0143] In response, the terminal device 102 receives a message B (MsgB) from the network device 101 .
[0144] MsgB includes at least one of the following: a response message to a preamble and a response message to uplink data. In other words, MsgB includes at least one of the following: an RAR and a contention resolution message. It can be understood that if MsgB does not include a contention resolution message, the 2-step RACH scheme is changed to a 4-step RACH scheme.
[0145] It can be understood that the terminal device in FIG. 1 may be classified into different types of terminal devices according to requirements. For example, based on the size of the bandwidth or the number of receiving antennas, the terminal device may be classified into a REDCAP terminal and a general terminal. The bandwidth of the REDCAP terminal is smaller than that of the general terminal, and / or the number of receiving antennas of the REDCAP terminal is smaller than that of the general terminal. For example, the bandwidth of the general terminal can reach 100 MHz, and the bandwidth of the REDCAP terminal is less than 100 MHz. As another example, the number of receiving antennas of the general terminal can reach 4, and the number of receiving antennas of the REDCAP terminal is only 2 or 1. Therefore, the REDCAP terminal may be applied to scenarios where the bandwidth requirement is not high. For example, the REDCAP terminal may be an industrial sensor, a video monitoring device, a wearable device, etc.
[0146] Additionally, REDCAP terminals may be classified based on the size of the bandwidth or the number of receive antennas.
[0147] For example, the frequency range in which the communication system 10 operates is FR1. The REDCAP terminals may include a first type REDCAP terminal and a second type REDCAP terminal. The bandwidth of the second type REDCAP terminal is smaller than that of the first type REDCAP terminal. For example, the bandwidth of the first type REDCAP terminal is greater than 10 MHz and less than or equal to 20 MHz, and the bandwidth of the second type REDCAP terminal is greater than 0 MHz and less than or equal to 10 MHz. Alternatively, the number of receiving antennas of the second type REDCAP terminal is smaller than that of the first type REDCAP terminal. For example, the number of receiving antennas of the first type REDCAP terminal is 2, and the number of receiving antennas of the second type REDCAP terminal is 1. Alternatively, the bandwidth of the second type REDCAP terminal is smaller than that of the first type REDCAP terminal, and the number of receiving antennas of the second type REDCAP terminal is smaller than that of the first type REDCAP terminal. For example, the bandwidth of a first type REDCAP terminal is greater than 10 MHz and less than or equal to 20 MHz, and the number of receiving antennas of the first type REDCAP terminal is 2, and the bandwidth of a second type REDCAP terminal is greater than 0 MHz and less than or equal to 10 MHz, and the number of receiving antennas of the second type REDCAP terminal is 1.
[0148] For example, the frequency range in which the communication system 10 operates may be FR2, and the REDCAP terminals may include third-type REDCAP terminals, the bandwidth of which is equal to or greater than 50 MHz.
[0149] It can be understood that in the embodiment of the present application, the first type REDCAP terminal, the second type REDCAP terminal, and the third type REDCAP terminal are merely examples of names of different types of terminal devices. In practical application, the first type REDCAP terminal, the second type REDCAP terminal, and the third type REDCAP terminal may alternatively be named in other ways. This is not limited.
[0150] It can be understood that before starting the random access procedure, the terminal device further needs to determine whether the terminal device is allowed to access the network device based on the instruction of the network device. For a general terminal, the network device can indicate whether the general terminal is allowed to access the network device by using a cell barred field (i.e., a cellBarred field) in the MIB. However, for the first type REDCAP terminal, the second type REDCAP terminal, and the third type REDCAP terminal, there is no method to enable the network device to control the access of the first type REDCAP terminal, the second type REDCAP terminal, and the third type REDCAP terminal.
[0151] In order to solve the above problem, the embodiment of the present application provides a network device access method, so as to control the number of REDCAP terminals accessing the network device. The method includes: a terminal device receives first information from the network device, indicating whether the REDCAP terminal is permitted to access the network device, and determines whether to access the network device based on the first information. Specifically, please refer to the following description of Figures 3 to 8.
[0152] The communication system 10 shown in Fig. 1 is merely used as an example and is not intended to limit the technical solution of the present application. Those skilled in the art should understand that in a specific implementation process, the communication system 10 may further include other devices, and the number of network devices and the number of terminals may alternatively be determined according to specific requirements. This is not limited.
[0153] Optionally, each network element in Fig. 1 in the embodiment of the present application, such as the network device 101, the terminal device 102, the terminal device 103, or the terminal device 104, may be a function module in a device. It may be understood that the function module may be an element in a hardware device, such as a communication chip or a communication component in a terminal device or a network device, or may be a software function module executed in hardware or a virtualized function instantiated in a platform (e.g., a cloud platform).
[0154] For example, each network element in Fig. 1 may be implemented by a communication device in Fig. 2. Fig. 2 is a schematic diagram of a hardware structure of a communication device that may be used in the embodiments of the present 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.
[0155] 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 configured to control program execution in the solutions of the present application.
[0156] The communication lines 202 may include a path, such as a bus, for transmitting information between the above components.
[0157] The communication interface 204 is configured to communicate with other devices or communication networks by using any device such as a transceiver, for example an Ethernet interface, a radio access network (RAN) interface, or a wireless local area network (WLAN) interface.
[0158] The memory 203 may be, but is not limited to, a read-only memory (ROM), other type of static storage device capable of storing static information and instructions, a random access memory (RAM), or other type of dynamic storage device capable of storing information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other compact disc storage, an optical disc storage (compact disc, laser disc, optical disc, digital versatile disc, Blue-ray disc, etc.), a magnetic disc storage medium or other magnetic storage device, or any other medium that may be configured to carry or store the expected program code in the form of instruction or data structures and that can be accessed by a computer. The memory may exist independently and is connected to the processor through communication lines 202. The memory may alternatively be integrated with the processor. The memory provided in the embodiment of the present application is configured to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 201. The processor 201 is configured to execute the computer-executable instructions stored in the memory 203 to implement the method provided in the embodiment of the present application.
[0159] Optionally, the computer executable instructions of this embodiment of the present application may also be referred to as application program code, which is not specifically limited in this embodiment of the present application.
[0160] In a specific implementation, in an embodiment, the processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
[0161] In a specific implementation, in an embodiment, communication device 200 may include multiple processors, processor 201 and processor 207 of FIG. 2. Each of the processors may be a single-core (single-CPU) processor or a multi-core (multi-CPUT) processor, where a processor may be one or more devices, circuits, and / or processing cores configured to process data (e.g., computer program instructions).
[0162] In a specific implementation, in an 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 may display information in a number of 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. The input device 206 communicates with the processor 201 and may receive input from a user in a number of ways. For example, the input device 206 may be a mouse, a keyboard, a touch screen device, or a sensor device.
[0163] The above communication device 200 may be a general-purpose device or a special-purpose device. In a specific implementation, the communication device 200 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device with a structure similar to that of FIG. 2. The type of the communication device 200 is not limited in this embodiment of the present application.
[0164] The following describes in detail the network device access method according to the embodiment of the present application with reference to FIG. 1 and FIG.
[0165] It should be noted that the names of messages between network elements, the names of parameters in messages, etc. in the following embodiments of the present application are merely examples, and other names may exist in specific implementations, which are not particularly limited in the embodiments of the present application.
[0166] It should be noted that in the specification of this application, the words "first" or "second" are used merely for distinction and description, and should not be understood as indicating or implying relative importance, or indicating or implying order. Different sequential numbers of information such as "first information" and "second information" in this application are used merely for contextual convenience, and the different sequential numbers have no specific technical meaning. For example, the first information or the second information can be understood as one or any one of a series of information.
[0167] It should be noted that in the following embodiments of the present application, the words "example" or "for example" are used to denote giving an example, illustration, or description. Any embodiment or design scheme described in the following embodiments of the present application as an example or with "for example" should not be described as being preferred or having more advantages over other embodiments or design schemes. Indeed, the use of the words "example" or "for example" is intended to express a relative concept in a particular way.
[0168] It may be understood that the same steps or steps or messages having the same function in the embodiments of the present application may be cross-referenced in different embodiments.
[0169] It may be understood that in the embodiments of the present application, the network device and / or the terminal device may perform some or all of the steps in the embodiments of the present application. The steps are merely examples. Other steps or variations of various steps may alternatively be performed in the embodiments of the present application. Furthermore, the steps may be performed in an order different from that presented in the embodiments of the present application, and not all steps in the embodiments of the present application need to be performed.
[0170] In the embodiment of the present application, the specific structure of the execution entity of the network device access method is not particularly limited in the embodiment of the present application, provided that the program recording the code of the network device access method in the embodiment of the present application can be executed to perform communication according to the network device access method in the embodiment of the present application. For example, the execution entity of the network device access method provided in the embodiment of the present application may be a network device or a component used in the network device, such as a chip. This is not limited in the present application. Alternatively, the network device access method provided in the embodiment of the present application may be executed by a terminal device or a component used in the terminal device, such as a chip. This is not limited in the present application. The following embodiment is described by using an example in which the network device access method is executed by the network device and the terminal device separately.
[0171] 3 shows a network device access method according to an embodiment of the present application, which includes steps 301 to 303.
[0172] Step 301: A network device determines first information.
[0173] The network device may be network device 101 of FIG.
[0174] The first information may indicate whether the REDCAP terminal is authorized to access the network device. The REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal. The first type REDCAP terminal and the second type REDCAP terminal operate in the same frequency range (have the same frequency range). For example, the operating frequency of the first type REDCAP terminal and the second type REDCAP terminal is less than 6 GHz, and the range is denoted as FR1. When the operating frequency is FR1, please refer to the description of FIG. 1 for the description of the first type REDCAP terminal and the second type REDCAP terminal.
[0175] In a possible implementation, the first information includes first indication information and second indication information. The first indication information and the second indication information may indicate whether a first type REDCAP terminal is authorized to access the network device and whether a second type REDCAP terminal is authorized to access the network, respectively. Alternatively, the first indication information and the second indication information together may indicate whether a first type REDCAP terminal is authorized to access the network device and whether a second type REDCAP terminal is authorized to access the network. For example, the first indication information and the second indication information may indicate whether a first type REDCAP terminal is authorized to access the network device and whether a second type REDCAP terminal is authorized to access the network device in the following manner:
[0176] Method 1: The first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether a second type REDCAP terminal is authorized to access the network device.
[0177] In this case, the network device can separately indicate whether the first type REDCAP terminal is authorized to access the network device and whether the second type REDCAP terminal is authorized to access the network by using the first indication information and the second indication information, respectively. The indication is clear and easy to use.
[0178] For method 1, there are six possible cases:
[0179] Case 1.1: The first information is included in the SSB. For the description of the SSB, please refer to the description of FIG. 1.
[0180] In a possible implementation, the first indication comprises a spare field in the MIB and the second indication comprises a reserved field in the additional PBCH payload.
[0181] For example, the first indication information indicates whether the first type REDCAP terminal is authorized to access the network device by using one bit of a spare field in the MIB, for example, if the value of the bit is 1, the first indication information indicates that the first type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the first indication information indicates that the first type REDCAP terminal is not authorized to access the network device, and vice versa.
[0182] For example, the second indication information indicates whether the second type REDCAP terminal is authorized to access the network device by using one bit of a reserved field in the additional PBCH payload. For example, if the value of the bit is 1, the second indication information indicates that the second type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the second indication information indicates that the second type REDCAP terminal is not authorized to access the network device. This also applies in reverse. It can be understood that the bit may be a high-order bit in the reserved field or a low-order bit in the reserved field. This is not limited.
[0183] In other possible implementations, the first indication includes a cellBarred field in the MIB and the second indication includes a spare field in the MIB or includes a reserved field in an additional PBCH payload.
[0184] It can be seen that the bandwidth of the first type REDCAP terminal is similar to that of a general terminal, and the two terminals may share CORESET #0, and the compatibility is excellent. Therefore, the first type REDCAP terminal can reuse the field of the general terminal to indicate whether it is authorized to access the network device. Specifically, in addition to indicating whether the general terminal is authorized to access the network device, the cellBarred field further indicates whether the first type REDCAP terminal is authorized to access the network device. However, the bandwidth of the second type REDCAP terminal is much smaller than that of the general terminal, and the second type REDCAP terminal may not share CORESET #0 with the bandwidth of the general terminal, and the compatibility is poor. Therefore, a field different from the cellBarred field needs to be used to indicate whether the second type REDCAP terminal is authorized to access the network device. Furthermore, the first type REDCAP terminal reuses the field of the general terminal to indicate whether it is authorized to access the network device, which can save the number of bits, and the saved bits are used for other purposes. This promotes the extension of the hardware compatibility of the communication system.
[0185] For example, if the value of the cellBarred field is 1, the first indication information indicates that a general terminal is authorized to access the network device and a first type REDCAP terminal is authorized to access the network device, or if the value of the cellBarred field is 0, the first indication information indicates that a general terminal is not authorized to access the network device and a first type REDCAP terminal is not authorized to access the network device. This also applies in reverse.
[0186] For example, the second indication information indicates whether the second type REDCAP terminal is authorized to access the network device by using one bit of a spare field in the MIB. For example, if the value of the bit is 1, the second indication information indicates that the second type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the second indication information indicates that the second type REDCAP terminal is not authorized to access the network device. This also applies in reverse. Alternatively, the second indication information indicates whether the second type REDCAP terminal is authorized to access the network device by using one bit of a reserved field in the additional PBCH payload. For example, if the value of the bit is 1, the second indication information indicates that the second type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the second indication information indicates that the second type REDCAP terminal is not authorized to access the network device. This also applies in reverse. It can be understood that the bit may be a high-order bit in the reserved field or a low-order bit in the reserved field. This is not limited.
[0187] Case 1.2: The first information is included in the DCI. The DCI is used to schedule the SIB1.
[0188] SIB1 contains the SIB1 information block, for a description of the SIB1 information block please refer to the description in the prior art.
[0189] In a possible implementation, the first indication information is included in a reserved field in the DCI, and the second indication information is included in a reserved field in the DCI.
[0190] The inclusion of the first indication information and the second indication information in the reserved field in the DCI may be understood as the first indication information including a first portion of the reserved field in the DCI, and the second indication information including a second portion of the reserved field in the DCI. For example, when the reserved field in the DCI is 5 bits, the first indication information includes one of the 5 bits to indicate whether the first type REDCAP terminal is authorized to access the network device, and the second indication information includes the other one of the 5 bits to indicate whether the second type REDCAP terminal is authorized to access the network device. Alternatively, the portion of the reserved field in the DCI may jointly indicate whether the first type REDCAP terminal and the second type REDCAP terminal are authorized to access the network device.
[0191] For example, the first indication information includes one bit of a reserved field in the DCI to indicate whether a first type REDCAP terminal is authorized to access the network device. For example, if the value of the bit is 1, the first indication information indicates that the first type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the first indication information indicates that the first type REDCAP terminal is not authorized to access the network device. This also applies in reverse. The second indication information includes another bit of a reserved field in the DCI to indicate whether a second type REDCAP terminal is authorized to access the network device. For example, if the value of the bit is 1, the second indication information indicates that the second type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the second indication information indicates that the second type REDCAP terminal is not authorized to access the network device. This also applies in reverse.
[0192] Case 1.3: The first information is contained in the SIB1 information block.
[0193] In a possible implementation, the first indication information is included in the SIB1 information block and the second indication information is included in the SIB1 information block.
[0194] The first indication information and the second indication information are included in the SIB1 information block, and may be understood as the first indication information including a first portion of the SIB1 information block and the second indication information including a second portion of the SIB1 information block. For example, when the SIB1 information block is 32 bits, the first indication information includes one of the 32 bits to indicate whether the first type REDCAP terminal is authorized to access the network device, and the second indication information includes the other one of the 32 bits to indicate whether the second type REDCAP terminal is authorized to access the network device. Alternatively, the portions of the SIB1 information block may jointly indicate whether the first type REDCAP terminal and the second type REDCAP terminal are authorized to access the network device.
[0195] For example, the first indication information includes one bit of the SIB1 information block to indicate whether the first type REDCAP terminal is authorized to access the network device. For example, if the value of the bit is 1, the first indication information indicates that the first type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the first indication information indicates that the first type REDCAP terminal is not authorized to access the network device. This also applies in reverse. The second indication information includes another bit of the SIB1 information block to indicate whether the second type REDCAP terminal is authorized to access the network device. For example, if the value of the bit is 1, the second indication information indicates that the second type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the second indication information indicates that the second type REDCAP terminal is not authorized to access the network device. This also applies in reverse.
[0196] A bit of the SIB1 information block indicating whether a first type REDCAP terminal is permitted to access the network device may be included in an information element (IE) newly added to the SIB1 information block, or may be included in an original IE in the SIB1 information block. A bit of the SIB1 information block indicating whether a second type REDCAP terminal is permitted to access the network device may be included in an IE newly added to the SIB1 information block, or may be included in an original IE in the SIB1 information block.
[0197] Case 1.4: The first information is included in DCI and SIB1.
[0198] In a possible implementation, the first indication information is included in a reserved field in the DCI, and the second indication information is included in the SIB1 information block.
[0199] For example, the first indication information includes one bit of a reserved field in the DCI to indicate whether a first type REDCAP terminal is authorized to access the network device. For example, if the value of the bit is 1, the first indication information indicates that a first type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the first indication information indicates that a first type REDCAP terminal is not authorized to access the network device. This also applies in reverse. The second indication information includes one bit of the SIB1 information block to indicate whether a second type REDCAP terminal is authorized to access the network device. For example, if the value of the bit is 1, the second indication information indicates that a second type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the second indication information indicates that a second type REDCAP terminal is not authorized to access the network device. This also applies in reverse.
[0200] In another possible implementation, the first indication information is included in the SIB1 information block and the second indication information is included in a reserved field in the DCI.
[0201] For example, the first indication information includes one bit of the SIB1 information block to indicate whether the first type REDCAP terminal is authorized to access the network device. For example, if the value of the bit is 1, the first indication information indicates that the first type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the first indication information indicates that the first type REDCAP terminal is not authorized to access the network device. This also applies in reverse. The second indication information includes one bit of a reserved field in the DCI to indicate whether the second type REDCAP terminal is authorized to access the network device. For example, if the value of the bit is 1, the second indication information indicates that the second type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the second indication information indicates that the second type REDCAP terminal is not authorized to access the network device. This also applies in reverse.
[0202] Case 1.5: The first information is contained in SSB and DCI.
[0203] In a possible implementation, the first indication information includes a spare field in the MIB, or a reserved field in the additional PBCH payload, or a cellBarred field in the MIB, and the second indication information is included in a reserved field in the DCI.
[0204] For the first indication information including a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred field in the MIB, see the above description of case 1.1. For the second indication information included in a reserved field in the DCI, see the above description of case 1.2. For example, the first indication information includes a spare field in the MIB, and the second indication information is included in a reserved field in the DCI. Certainly, other configuration combinations are also applicable.
[0205] In other possible implementations, the first indication information is included in a reserved field in the DCI, and the second indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred field in the MIB.
[0206] For the case where the first indication information is included in a reserved field in the DCI, see the description of case 1.2 above. For the second indication information including a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred field in the MIB, see the description of case 1.1 above. For example, the first indication information is included in a reserved field in the DCI, and the second indication information includes a spare field in the MIB. Certainly, other configuration combinations are also applicable.
[0207] Case 1.6: The first information is included in the SSB and SIB1.
[0208] In a possible implementation, the first indication information includes a spare field in the MIB, or a reserved field in the additional PBCH payload, or a cellBarred field in the MIB, and the second indication information is included in the SIB1 information block.
[0209] For the first indication information including a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred field in the MIB, see the above description of case 1.1. For the second indication information included in the SIB1 information block, see the above description of case 1.3. For example, the first indication information includes a spare field in the MIB, and the second indication information is included in the SIB1 information block. Certainly, other configuration combinations are also applicable.
[0210] In other possible implementations, 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 cellBarred field in the MIB.
[0211] For the case where the first indication information is included in the SIB1 information block, see the above description of case 1.3. For the second indication information including a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred field in the MIB, see the above description of case 1.1. For example, the first indication information is included in the SIB1 information block, and the second indication information includes a spare field in the MIB. Certainly, other configuration combinations are also applicable.
[0212] Method 2: The first indication information indicates whether a first type REDCAP terminal is permitted to access the network device, and the first indication information and the second indication information indicate whether a second type REDCAP terminal is permitted to access the network device. In other words, the first indication information indicates whether a REDCAP terminal (including a first type REDCAP terminal and a second type REDCAP terminal) is permitted to access the network device. The second indication information indicates whether a second type REDCAP terminal is permitted to access the network device.
[0213] It can be understood that when the first indication information indicates that the REDCAP terminal is not authorized to access the network device, neither the first type REDCAP terminal nor the second type REDCAP terminal can access the network device. When the first indication information indicates that the REDCAP terminal is authorized to access the network device, the first type REDCAP terminal may access the network device. In this case, when the second indication information indicates that the second type REDCAP terminal is authorized to access the network device, the second type REDCAP terminal may access the network device, or when the second indication information indicates that the second type REDCAP terminal is not authorized to access the network device, the second type REDCAP terminal cannot access the network device.
[0214] It can be understood that the bandwidth of the first type REDCAP terminal is similar to that of a general terminal, and the two terminals may share CORESET #0. Therefore, the first type REDCAP terminal has a small impact on the transmission performance of the network provided by the network device. Therefore, compared with the second type REDCAP terminal, the first type REDCAP terminal has a higher priority for accessing the network device.
[0215] For method 2, there are six possible cases:
[0216] The first indication information is included in the SSB.
[0217] In a possible implementation, the first indication comprises a spare field in the MIB and the second indication comprises a reserved field in the additional PBCH payload.
[0218] For example, the first indication information indicates whether the first type REDCAP terminal is authorized to access the network device by using one bit of a spare field in the MIB, for example, if the value of the bit is 1, the first indication information indicates that the first type REDCAP terminal is authorized to access the network device, or if the value of the bit is 0, the first indication information indicates that the first type REDCAP terminal is not authorized to access the network device, and vice versa.
[0219] For example, when the first indication information indicates that the first type REDCAP terminal is permitted to access the network device by using one bit of a spare field in the MIB, the second indication information indicates whether the second type REDCAP terminal is permitted to access the network device by using one bit of a reserved field in the additional PBCH payload. For example, when the first indication information indicates that the first type REDCAP terminal is permitted to access the network device by using one bit of a spare field in the MIB, if the value of the bit of the reserved field is 1, the second indication information indicates that the second type REDCAP terminal is permitted to access the network device, or if the value of the bit of the reserved field is 0, the second indication information indicates that the second type REDCAP terminal is not permitted to access the network device. This also applies in reverse. It can be understood that the bit in the reserved field may be a high-order bit in the reserved field or a low-order bit in the reserved field. This is not limited.
[0220] In method 2, if the first indication information indicates that the first type REDCAP terminal is not permitted to access the network device, the second type REDCAP terminal is not permitted to access the network device. Thus, the bit of the reserved field does not need to indicate whether the second type REDCAP terminal is permitted to access the network device. For example, the bit of the reserved field may indicate whether the REDCAP terminal can search for SSBs of other cells on the same frequency. In this way, the first information may indicate further information, thereby improving the flexibility of indicating information by the first information.
[0221] Case 2.2: The first information is included in the DCI.
[0222] For the description of case 2.2, please refer to the description of case 1.2.
[0223] Case 2.3: The first information is contained in the SIB1 information block.
[0224] For the description of case 2.3, please refer to the description of case 1.3.
[0225] Case 2.4: The first information is included in DCI and SIB1.
[0226] For the description of case 2.4, please refer to the description of case 1.4.
[0227] Case 2.5: The first information is contained in SSB and DCI.
[0228] For the description of case 2.5, please refer to the description of case 1.5.
[0229] Case 2.6: The first information is included in the SSB and SIB1.
[0230] For the description of case 2.6, please refer to the description of case 1.6.
[0231] In a possible implementation, the network device determines the first information based on a transmission performance of a network managed by the network device. For example, if the transmission performance of the network is equal to or greater than a threshold, the network device does not limit the number of REDCAP terminals, or if the transmission performance of the network is less than the threshold, the network device limits the number of REDCAP terminals. For example, the transmission performance of the network may be related to the total number of terminal devices currently being served by the network device, the transmission spectrum efficiency of the network, etc. For example, the transmission performance of the network is low when the total number of terminal devices currently being served by the network device is high compared to when the total number of terminal devices currently being served by the network device is low. As another example, the transmission performance of the network is high when the transmission spectrum efficiency of the network is high compared to when the transmission spectrum efficiency of the network is low.
[0232] Step 302: The network device sends first information to the terminal device.
[0233] The terminal device is one or more of the terminal devices in Fig. 1. For example, the terminal device is the terminal device 102 in Fig. 1, or the terminal device is the terminal device 102 and the terminal device 103 in Fig. 1.
[0234] In response, the terminal device receives the first information from the network device.
[0235] Step 303: The terminal device determines whether to access the network device based on the first information.
[0236] The terminal device may be a first type REDCAP terminal, a second type REDCAP terminal, or a general terminal.
[0237] In a possible implementation, if the terminal device is a general terminal, the terminal device determines whether to access the network device based on the cellBarred field (cell barred field). For example, if the value of the cellBarred field is 1, the terminal device determines to access the network device, or if the value of the cellBarred field is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0238] In a possible implementation, if the terminal device is a first type REDCAP terminal, the terminal device determines whether to access the network device based on the first indication information.
[0239] For example, the first indication information indicates whether the first type REDCAP terminal is allowed to access the network device by using one bit of a spare field in the MIB, where if the value of the bit is 1, the terminal device determines to access the network device, and if the value of the bit is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0240] For example, the first indication information indicates whether the first type REDCAP terminal is allowed to access the network device by using a cellBarred field in the MIB. If the value of the cellBarred field is 1, the terminal device determines to access the network device, and if the value of the cellBarred field is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0241] For example, the first indication information includes one bit in a reserved field in the DCI to indicate whether the first type REDCAP terminal is authorized to access the network device. If the value of the bit is 1, the terminal device determines to access the network device, and if the value of the bit is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0242] For example, the first indication information includes one bit in the SIB1 information block to indicate whether the first type REDCAP terminal is authorized to access the network device. If the value of the bit is 1, the terminal device determines to access the network device, and if the value of the bit is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0243] In a possible implementation, for 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 indication information.
[0244] For example, the second indication information indicates whether the second type REDCAP terminal is allowed to access the network device by using one bit of a spare field in the MIB. If the value of the bit is 1, the terminal device determines to access the network device, and if the value of the bit is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0245] For example, the second indication information indicates whether the second type REDCAP terminal is allowed to access the network device by using one bit of a reserved field in the additional PBCH payload. If the value of the bit is 1, the terminal device determines to access the network device, and if the value of the bit is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0246] For example, the second indication information includes one bit in a reserved field in the DCI to indicate whether the second type REDCAP terminal is authorized to access the network device. If the value of the bit is 1, the terminal device determines to access the network device, and if the value of the bit is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0247] For example, the second indication information includes one bit in the SIB1 information block to indicate whether the second type REDCAP terminal is authorized to access the network device. If the value of the bit is 1, the terminal device determines to access the network device, and if the value of the bit is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0248] In a possible implementation, for 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 indication information and the second indication information.
[0249] For example, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device and whether a second type REDCAP terminal is authorized to access the network device by using one bit of a spare field in the MIB, and the second indication information indicates whether a second type REDCAP terminal is authorized to access the network device by using one bit of a reserved field in the additional PBCH payload. If the value of the bit in the spare field is 0, the terminal device determines not to access the network device, if the value of the bit in the spare field is 1 and the value of the bit in the reserved field is 1, the terminal device determines to access the network device, or if the value of the bit in the spare field is 1 and the value of the bit in the reserved field is 0, the terminal device determines not to access the network device. Alternatively, if the value of the bit in the spare field is 1, the terminal device determines not to access the network device, and if the value of the bit in the spare field is 0 and the value of the bit in the reserved field is 0, the terminal device determines to access the network device, or if the value of the bit in the spare field is 0 and the value of the bit in the reserved field is 1, the terminal device determines not to access the network device.
[0250] For example, the first indication information includes one bit of a reserved field in the DCI to indicate whether a first type REDCAP terminal is authorized to access the network device and whether a second type REDCAP terminal is authorized to access the network device, and the second indication information includes one bit of the SIB1 information block to indicate whether a second type REDCAP terminal is authorized to access the network device. If the value of the bit in the reserved field is 0, the terminal device determines not to access the network device, if the value of the bit in the reserved field is 1 and the value of the bit in the SIB1 information block is 1, the terminal device determines to access the network device, or if the value of the bit in the reserved field is 1 and the value of the bit in the SIB1 information block is 0, the terminal device determines not to access the network device. Alternatively, if the value of the bit in the reserved field is 1, the terminal device determines not to access the network device, and if the value of the bit in the reserved field is 0 and the value of the bit in the SIB1 information block is 0, the terminal device determines to access the network device, or if the value of the bit in the reserved field is 0 and the value of the bit in the SIB1 information block is 1, the terminal device determines not to access the network device.
[0251] Based on the method shown in Fig. 3, the network device may transmit first information to the terminal device, which indicates whether the first type REDCAP terminal is permitted to access the network device and whether the second type REDCAP terminal is permitted to access the network device. After receiving the first information, the terminal device may determine whether to access the network device. In this way, the network device may 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.
[0252] It can be seen that, compared with a general terminal, a REDCAP terminal has a smaller bandwidth. Therefore, different processing methods are required when a network device schedules resources for a REDCAP terminal and a general terminal. For example, when scheduling resources for a REDCAP terminal, a network device cannot schedule frequency domain resources that exceed the maximum bandwidth of the REDCAP terminal. Furthermore, compared with a general terminal, a REDCAP terminal has a smaller number of antennas. This means that the receiving antenna gain of a REDCAP terminal is smaller. Therefore, when scheduling a REDCAP terminal to perform downlink reception, a network device may need to use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0253] In summary, in the process of communicating with the terminal device, the network device has different processing methods for REDCAP terminals and general terminals. Therefore, the REDCAP terminal needs to report the type of the REDCAP terminal at an appropriate time. For example, the REDCAP terminal may report the type of the REDCAP terminal in a random access procedure, or the REDCAP terminal may report the type of the REDCAP terminal by using radio resource control (RRC) signaling after the random access is successful. In this way, the network device can allocate appropriate resources to the REDCAP terminal based on the type of the REDCAP terminal to improve the transmission reliability of the REDCAP terminal. It should be understood that if the REDCAP terminal reports the type of the REDCAP terminal first, the network device can identify the type of the REDCAP terminal and prepare for subsequent transmission to improve the transmission reliability.
[0254] Optionally, in a possible implementation of the method shown in Fig. 3, if the first information indicates that a first type REDCAP terminal is permitted to access the network device, if the first information indicates that a second type REDCAP terminal is permitted to access the network device, or if the first information indicates that a first type REDCAP terminal is permitted to access the network device and a second type REDCAP terminal is permitted to access the network device, the terminal device indicated in the first information and permitted to access the network device may report the type of the terminal device to the network device by using the second information, so that the network device identifies the type of the terminal device. Specifically, as shown in Fig. 4, the method shown in Fig. 3 further includes step 401.
[0255] Step 401: The terminal device sends second information to the network device.
[0256] The second information indicates that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal. For example, if the terminal device is a first type REDCAP terminal, the second information indicates that the terminal device is a first type REDCAP terminal. If the terminal device is a second type REDCAP terminal, the second information indicates that the terminal device is a second type REDCAP terminal.
[0257] In a possible implementation, the second information is carried on a physical random access channel (PRACH). The PRACH resource corresponds to a first-type REDCAP terminal or a second-type REDCAP terminal. The PRACH resource includes at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH. For example, the PRACH time domain resource and the PRACH frequency domain resource may be a time domain resource-frequency domain resource of a random access channel occasion (RACH occasion, RO), and the PRACH code domain resource may be a preamble used by the terminal device to transmit the PRACH in the RO.
[0258] The PRACH resource is configured by the network device for the terminal device. The network device may configure the PRACH resource corresponding to the first type REDCAP terminal and / or the PRACH resource corresponding to the second type REDCAP terminal for the terminal device. Specifically, please refer to the following four exemplary cases.
[0259] Case 1: When the terminal device is a first-type REDCAP terminal and the first information indicates that the first-type REDCAP terminal is authorized to access the network device, the network device configures a PRACH resource corresponding to the first-type REDCAP terminal for the first-type REDCAP terminal. The terminal device transmits second information to the network device by using the PRACH resource corresponding to the first-type REDCAP terminal.
[0260] Case 2: When the terminal device is a first type REDCAP terminal and the first information indicates that the first type REDCAP terminal is authorized to access the network device, or when the terminal device is a first type REDCAP terminal and the first information indicates that the first type REDCAP terminal is authorized to access the network device and the second type REDCAP terminal is authorized to access the network device, the network device configures a PRACH resource corresponding to the first type REDCAP terminal for the first type REDCAP terminal, and configures a PRACH resource corresponding to the second type REDCAP terminal for the second type REDCAP terminal. The terminal device transmits the second information to the network device by using the PRACH resource corresponding to the first type REDCAP terminal.
[0261] Case 3: When the terminal device is a second-type REDCAP terminal and the first information indicates that the second-type REDCAP terminal is authorized to access the network device, the network device configures a PRACH resource corresponding to the second-type REDCAP terminal for the second-type REDCAP terminal. The terminal device transmits the second information to the network device by using the PRACH resource corresponding to the second-type REDCAP terminal.
[0262] Case 4: When the terminal device is a second type REDCAP terminal and the first information indicates that the second type REDCAP terminal is authorized to access the network device, or when the terminal device is a second type REDCAP terminal and the first information indicates that the first type REDCAP terminal is authorized to access the network device and the second type REDCAP terminal is authorized to access the network device, the network device configures a PRACH resource corresponding to the first type REDCAP terminal for the first type REDCAP terminal, and configures a PRACH resource corresponding to the second type REDCAP terminal for the second type REDCAP terminal. The terminal device transmits the second information to the network device by using the PRACH resource corresponding to the second type REDCAP terminal.
[0263] It may be appreciated that the PRACH resources may alternatively be predefined, for example, the PRACH resources may be defined in a protocol.
[0264] It may be understood that the PRACH resources corresponding to the first-type REDCAP terminals are different from the PRACH resources corresponding to the second-type REDCAP terminals.
[0265] In another possible implementation, the second information is carried in Msg3, MsgA, or RRC signaling. In other words, the terminal device may report the type of the terminal in Msg3, MsgA, or RRC signaling. For the description of Msg3 and MsgA, please refer to the corresponding description in FIG. 1.
[0266] Furthermore, the second information includes a type identifier of the terminal device. For example, the identifier of the first type REDCAP terminal is ID1, and the identifier of the second type REDCAP terminal is ID2. When the second information includes ID1, the second information indicates that the type of the terminal device is a first type REDCAP terminal. When the second information includes ID2, the second information indicates that the type of the terminal device is a second type REDCAP terminal.
[0267] It may be understood that when the network device indicates that the generic terminal is allowed to access the network device, the generic terminal may or may not report the terminal type. If the generic terminal does not report the terminal type, if the network device does not receive the type reported by the terminal device, the network device may determine that the terminal device is a generic terminal. The generic terminal may report the type of the terminal device to the network device by using multiple methods such as PRACH, Msg3, MsgA, or RRC signaling. For details, please refer to the description of reporting the terminal type by the REDCAP terminal in step 401. The details will not be described again.
[0268] Correspondingly, the network device receives second information from the terminal device. The network device can then determine the type of the terminal device based on the second information.
[0269] For example, for the above cases 1 and 2, the network device determines that the terminal device is a first type REDCAP terminal. For the above cases 3 and 4, the network device determines that the terminal device is a second type REDCAP terminal.
[0270] For example, the identifier of the first type REDCAP terminal is ID1, and the identifier of the second type REDCAP terminal is ID2. If the second information includes ID1, the network device determines that the type of the terminal device is a first type REDCAP terminal. If the second information includes ID2, the network device determines that the type of the terminal device is a second type REDCAP terminal.
[0271] Based on the method shown in Figure 4, the terminal device may report the type of the terminal device to the network device by using multiple methods such as PRACH, Msg3, MsgA, or RRC signaling, so that the network device identifies the type of the terminal device. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission and downlink transmission, the scheduled frequency range can be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device can use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0272] Optionally, in a possible implementation of the method shown in Figure 3, when the terminal device is a first type REDCAP terminal or a second type REDCAP terminal, and the first information indicates that the first type REDCAP terminal and the second type REDCAP terminal are permitted to access the network device, the terminal device reports the type of the terminal device to the network device by using the second information and the third information, so that the network device identifies the type of the terminal device. Specifically, as shown in Figure 5, the method shown in Figure 3 further includes step 501 and step 502.
[0273] Step 501: The terminal device sends second information to the network device.
[0274] In a possible implementation, the second information is carried on a PRACH, where the resources of the PRACH correspond to a REDCAP terminal, and the resources of the PRACH include at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH.
[0275] The PRACH resource is configured by the network device for the terminal device. The network device may configure the PRACH resource corresponding to the REDCAP terminal for the terminal device, the network device may configure the PRACH resource corresponding to the REDCAP terminal and the PRACH resource corresponding to a general terminal for the terminal device, or the network device may configure the PRACH resource corresponding to the first type REDCAP terminal and the PRACH resource corresponding to the second type REDCAP terminal for the terminal device. Specifically, please refer to the following two exemplary cases.
[0276] Case 5: When a network device configures a PRACH resource corresponding to a REDCAP terminal for a terminal device, or when a network device configures a PRACH resource corresponding to a REDCAP terminal and a PRACH resource corresponding to a general terminal for a terminal device, if the terminal device is a first type REDCAP terminal or a second type REDCAP terminal, the terminal device transmits second information to the network device by using the PRACH resource corresponding to the REDCAP terminal.
[0277] In this case, the first type REDCAP terminal and the second type REDCAP terminal share the PRACH resource. Therefore, the second information can indicate that the terminal device is a REDCAP terminal or a REDCAP type terminal, but cannot indicate whether the terminal device is specifically a first type REDCAP terminal or a second type REDCAP terminal.
[0278] Case 6: When the network device configures a PRACH resource corresponding to a first type REDCAP terminal and a general terminal and a PRACH resource corresponding to a second type REDCAP terminal for a terminal device, if the terminal device is a first type REDCAP terminal, the terminal device transmits second information to the network device by using the PRACH resource corresponding to the first type REDCAP terminal and the general terminal. The second information indicates that the terminal device is one of the first type REDCAP terminal and the general terminal. If the terminal device is a second type REDCAP terminal, the terminal device transmits second information to the network device by using the PRACH resource corresponding to the second type REDCAP terminal, where the second information indicates that the terminal device is a second type REDCAP terminal.
[0279] In this case, the first type REDCAP terminal and the general terminal share the PRACH resource. Therefore, when the terminal device is a first type REDCAP terminal, the second information can indicate that the terminal device is one of the first type REDCAP terminal and the general terminal, but cannot indicate whether the terminal device is a first type REDCAP terminal or a general terminal. When the terminal device is a second type REDCAP terminal, the second information can directly indicate that the terminal device is a second type REDCAP terminal.
[0280] Correspondingly, the network device receives second information from the terminal equipment.
[0281] For case 5 above, the network device may determine that the terminal device is a REDCAP terminal based on the second information.
[0282] For the above case 6, the network device may determine, based on the second information, that the terminal device is one of a first type REDCAP terminal and a general terminal, or the network device determines, based on the second information, that the terminal device is a second type REDCAP terminal.
[0283] Step 502: The terminal device sends third information to the network device.
[0284] In a possible implementation, the third information is carried in Msg3, MsgA, or RRC signaling.
[0285] It may be understood that when the network device cannot determine the type of the terminal device based on the second information, the terminal device transmits the third information to the network device. For example, when the network device determines that the terminal device is a REDCAP terminal based on the second information, or when the network device determines that the terminal device is one of a first type REDCAP terminal and a general terminal based on the second information, the terminal device transmits the third information to the network device.
[0286] In a possible implementation, if the network device determines that the terminal device is a REDCAP terminal based on the second information, the third information indicates that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal. For example, if the terminal device is a first type REDCAP terminal, the third information indicates that the terminal device is a first type REDCAP terminal. If the terminal device is a second type REDCAP terminal, the third information indicates that the terminal device is a second type REDCAP terminal.
[0287] Furthermore, the third information includes a type identifier of the terminal device. For example, the identifier of a first type REDCAP terminal is ID1, and the identifier of a second type REDCAP terminal is ID2. When the third information includes ID1, the third information indicates that the type of the terminal device is a first type REDCAP terminal. When the third information includes ID2, the third information indicates that the type of the terminal device is a second type REDCAP terminal.
[0288] In a possible implementation, when the network device determines based on the second information that the terminal device is one of a first type REDCAP terminal and a general terminal, the third information indicates that the terminal device is a first type REDCAP terminal.
[0289] Furthermore, the third information includes a type identifier of the terminal device. For example, the identifier of the first type REDCAP terminal is ID1. When the third information includes ID1, the third information indicates that the type of the terminal device is a first type REDCAP terminal.
[0290] It may be understood that when the network device indicates that a generic terminal accesses the network device, the generic terminal may or may not report the terminal type. If the generic terminal does not report the terminal type, if the network device does not receive the type reported by the terminal device, the network device may determine that the terminal device is a generic terminal. The generic terminal may report the type of the terminal device to the network device by using multiple methods such as PRACH, Msg3, MsgA, or RRC signaling. For details, please refer to the description of reporting the terminal type by the REDCAP terminal in steps 501 and 502. Details will not be described again.
[0291] Correspondingly, the network device receives third information from the terminal equipment.
[0292] Furthermore, the network device determines the type of the terminal equipment based on the third information.
[0293] For example, if the network device determines that the terminal device is a REDCAP terminal based on the second information, and if the third information indicates that the terminal device is a first type REDCAP terminal, the network device determines that the type of the terminal device is a first type REDCAP terminal, or if the third information indicates that the terminal device is a second type REDCAP terminal, the network device determines that the type of the terminal device is a second type REDCAP terminal.
[0294] For example, if the network device determines based on the second information that the terminal device is one of a first type REDCAP terminal and a general terminal, and if the third information indicates that the terminal device is a first type REDCAP terminal, the network device determines that the type of the terminal device is a first type REDCAP terminal.
[0295] Based on the method shown in FIG. 5, the terminal device may report the type of the terminal device to the network device in the second information and the third information, so that the network device identifies the type of the terminal device. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission or downlink transmission, the scheduled frequency range may be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device may use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability. Furthermore, in the method shown in FIG. 5, the first type REDCAP terminal may share the PRACH resource with the second type REDCAP terminal, or the first type REDCAP terminal may share the PRACH resource with a general terminal. In this way, excessive division of the PRACH resource may be avoided, that is, excessive reduction of the random access capability is avoided.
[0296] In addition to the above case where the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, the REDCAP terminal may further include a third type REDCAP terminal. The frequency range in which the third type REDCAP terminal operates is different from the frequency range in which the first type REDCAP terminal and the second type REDCAP terminal operate. For example, the frequency range in which the first type REDCAP terminal and the second type REDCAP terminal operate is FR1, and the frequency range in which the third type REDCAP terminal operates is 6 GHz or higher, and the frequency is expressed as FR2.
[0297] The following describes a network device access method provided in an embodiment of the present application by using an example in which a REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, or a REDCAP terminal includes a third type REDCAP terminal.
[0298] 6 shows a network device access method according to an embodiment of the present application, which includes steps 601 to 602.
[0299] Step 601: A network device determines first information.
[0300] The network device may be network device 101 of FIG.
[0301] The first information may indicate whether the REDCAP terminal is authorized to access the network device. The REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal. Alternatively, the REDCAP terminal includes a third type REDCAP terminal. For the description of the first type REDCAP terminal and the second type REDCAP terminal, please refer to the description of step 301. The frequency range in which the third type REDCAP terminal operates is different from the frequency range in which the first type REDCAP terminal and the second type REDCAP terminal operate. For example, the frequency range in which the first type REDCAP terminal and the second type REDCAP terminal operate is FR1, and the frequency range in which the third type REDCAP terminal operates is FR2. When the frequency range in which the third type REDCAP terminal operates is FR2, please refer to the description of FIG. 1 for the description of the third type REDCAP terminal.
[0302] It should be noted that if the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, please refer to the description of step 301 for the description of the first information.
[0303] The following describes the contents included in the first information when the REDCAP terminal includes a third type REDCAP terminal.
[0304] In a possible implementation, the first information includes third indication information, and the third indication information may indicate whether a third type REDCAP terminal is authorized to access the network device. The third indication information has the following four cases:
[0305] Case 3.1: The third indication information includes a spare field in the MIB.
[0306] For example, the third indication information indicates whether the third type REDCAP terminal is permitted to access the network device by using one bit of a spare field in the MIB. For example, if the value of the bit is 1, the third indication information indicates that the third type REDCAP terminal is permitted to access the network device. Alternatively, if the value of the bit is 0, the third indication information indicates that the third type REDCAP terminal is not permitted to access the network device. This also applies in reverse.
[0307] Case 3.2: The third indication information includes a cellBarred field.
[0308] For example, if the value of the cellBarred field is 1, the third indication information indicates that the third type REDCAP terminal is authorized to access the network device, and if the value of the cellBarred field is 0, the third indication information indicates that the third type REDCAP terminal is not authorized to access the network device. This also applies in reverse.
[0309] It can be seen that the bandwidth of the third type REDCAP terminal is similar to that of a general terminal, and the two terminals may share CORESET #0, and the compatibility is excellent. Furthermore, the presence of the third type REDCAP terminal has little impact on the network performance. Therefore, the third type REDCAP terminal can reuse the field of the general terminal for indicating whether the general terminal is authorized to access the network device. That is, in addition to indicating whether the general terminal is authorized to access the network device, the cellBarred field further indicates whether the third type REDCAP terminal is authorized to access the network device. Furthermore, the third type REDCAP terminal reuses the field of the general terminal for indicating whether the general terminal is authorized to access the network device, so that the number of bits can be saved, and the saved bits are used for other purposes. This promotes the extension of the hardware compatibility of the communication system.
[0310] Case 3.3: The third indication information is included in a reserved field in the DCI.
[0311] For example, the third indication information includes one bit of a reserved field in the DCI to indicate whether a third type REDCAP terminal is authorized to access the network device. For example, if the value of the bit is 1, the third indication information indicates that a third type REDCAP terminal is authorized to access the network device, and if the value of the bit is 0, the third indication information indicates that a third type REDCAP terminal is not authorized to access the network device. This also applies in reverse.
[0312] Case 3.4: The third indication information is included in the SIB1 information block.
[0313] For example, the third indication information includes one bit in the SIB1 information block to indicate whether the third type REDCAP terminal is authorized to access the network device. For example, if the value of the bit is 1, the third indication information indicates that the third type REDCAP terminal is authorized to access the network device, and if the value of the bit is 0, the third indication information indicates that the third type REDCAP terminal is not authorized to access the network device. This also applies in reverse.
[0314] A bit in the SIB1 information block indicating whether a third type REDCAP terminal is authorized to access the network device may be included in a newly added IE to the SIB information block or may be included in the original IE in the SIB1 information block.
[0315] In a possible implementation, the network device determines the first information based on a transmission performance of a network managed by the network device, for example, when the transmission performance of the network is equal to or greater than a threshold, the network device does not limit the number of REDCAP terminals, or when the transmission performance of the network is below the threshold, the network device limits the number of REDCAP terminals.
[0316] Step 602: The network device sends first information to the terminal device.
[0317] For the description of step 602, please refer to step 302 above. The details will not be described again.
[0318] Step 603: The terminal device determines whether to access the network device based on the first information.
[0319] The terminal device may be a first type REDCAP terminal, a second type REDCAP terminal, a third type REDCAP terminal, or a general terminal.
[0320] When the terminal device is a first type REDCAP terminal, a second type REDCAP terminal, or a general terminal, the process of the terminal device determining whether to access the network device based on the first information can be referred to the description of step 303. Details are not described again.
[0321] The following describes a process in which, when the terminal device is a third type REDCAP terminal, the terminal device determines whether to access the network device based on the first information.
[0322] For example, the third indication information indicates whether the third type REDCAP terminal is allowed to access the network device by using one bit of a spare field in the MIB. If the value of the bit is 1, the terminal device determines to access the network device, and if the value of the bit is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0323] For example, the third indication information indicates whether the third type REDCAP terminal is allowed to access the network device by using a cellBarred field in the MIB. When the value of the cellBarred field is 1, the terminal device determines to access the network device, and when the value of the cellBarred field is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0324] For example, the third indication information includes one bit in a reserved field in the DCI to indicate whether the third type REDCAP terminal is authorized to access the network device. If the value of the bit is 1, the terminal device determines to access the network device, and if the value of the bit is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0325] For example, the third indication information includes one bit in the SIB1 information block to indicate whether the third type REDCAP terminal is permitted to access the network device. If the value of the bit is 1, the terminal device determines to access the network device, and if the value of the bit is 0, the terminal device determines not to access the network device. This also applies in the reverse case.
[0326] Based on the method shown in FIG. 6, the network device may send to the terminal device first information indicating whether the first type REDCAP terminal is permitted to access the network device and whether the second type REDCAP terminal is permitted to access the network device, or the network device may send to the terminal device first information indicating whether the third type REDCAP terminal is permitted to access the network device. After receiving the first information, the terminal device may determine whether to access the network device. In this way, in order to ensure the transmission performance of the network managed by the network device, the network device can control the number of the first type REDCAP terminal and the second type REDCAP terminal that access the network device, or the network device may control the number of the third type REDCAP terminal that accesses the network device.
[0327] It can be seen that, compared with a general terminal, a REDCAP terminal has a smaller bandwidth. Therefore, different processing methods are required when a network device schedules resources for a REDCAP terminal and a general terminal. For example, when scheduling resources for a REDCAP terminal, a network device cannot schedule frequency domain resources that exceed the maximum bandwidth of the REDCAP terminal. Furthermore, compared with a general terminal, a REDCAP terminal has a smaller number of antennas. This means that the receiving antenna gain of a REDCAP terminal is smaller. Therefore, when scheduling a REDCAP terminal to perform downlink reception, a network device may need to use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0328] In summary, in the process of communicating with the terminal device, the network device has different processing methods for REDCAP terminals and general terminals. Therefore, the REDCAP terminal needs to report the type of the REDCAP terminal at an appropriate time. For example, the REDCAP terminal may report the type of the REDCAP terminal in a random access procedure, or the REDCAP terminal may report the type of the REDCAP terminal by using RRC signaling after the random access is successful. In this way, the network device can allocate appropriate resources to the REDCAP terminal based on the type of the REDCAP terminal to improve the transmission reliability of the REDCAP terminal. It should be understood that when the REDCAP terminal reports the type of the REDCAP terminal first, the network device can identify the type of the REDCAP terminal and prepare for subsequent transmission to improve the transmission reliability.
[0329] Optionally, in a possible implementation of the method shown in Fig. 6, if the first information indicates that a first type REDCAP terminal is permitted to access the network device, if the first information indicates that a second type REDCAP terminal is permitted to access the network device, if the first information indicates that a first type REDCAP terminal is permitted to access the network device and a second type REDCAP terminal is permitted to access the network device, or if the first information indicates that a third type REDCAP terminal is permitted to access the network device, the terminal device indicated in the first information and permitted to access the network device may report the type of the terminal device to the network device by using the second information, so that the network device identifies the type of the terminal device. Specifically, as shown in Fig. 7, the method shown in Fig. 6 further includes step 701.
[0330] Step 701: The terminal device sends second information to the network device.
[0331] The second information indicates that the terminal device is a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal. For example, if the terminal device is a first type REDCAP terminal, the second information indicates that the terminal device is a first type REDCAP terminal. If the terminal device is a second type REDCAP terminal, the second information indicates that the terminal device is a second type REDCAP terminal. If the terminal device is a third type REDCAP terminal, the second information indicates that the terminal device is a third type REDCAP terminal.
[0332] In a possible implementation, the second information is carried in a PRACH. The PRACH resource corresponds to a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal. The PRACH resource includes at least one of the following: a PRACH time domain resource, a PRACH frequency domain resource, or a PRACH code domain resource. For example, the PRACH time domain resource and the PRACH frequency domain resource may be a time domain resource-frequency domain resource of a random access channel occasion (RACH occasion, RO), and the PRACH code domain resource may be a preamble used by the terminal device to transmit the PRACH in the RO.
[0333] If the terminal device is a first type REDCAP terminal and the first information indicates that the first type REDCAP terminal is authorized to access the network device, or if the terminal device is a first type REDCAP terminal and the first information indicates that the first type REDCAP terminal is authorized to access the network device and the second type REDCAP terminal is authorized to access the network device, please refer to the description of step 401 for the description of the resource of the PRACH. Details will not be described again.
[0334] If the terminal device is a second type REDCAP terminal and the first information indicates that the second type REDCAP terminal is authorized to access the network device, or if the terminal device is a second type REDCAP terminal and the first information indicates that the first type REDCAP terminal is authorized to access the network device and the second type REDCAP terminal is authorized to access the network device, please refer to the description of step 401 for the description of the resource of the PRACH. Details will not be described again.
[0335] The following describes resources of the PRACH when the terminal device is a third type REDCAP terminal and the first information indicates that the third type REDCAP terminal is authorized to access the network device.
[0336] The PRACH resource is configured by the network device for the terminal device. The network device may configure a PRACH resource corresponding to a third type REDCAP terminal for the terminal device.
[0337] For example, the network device configures a PRACH resource corresponding to the third type REDCAP terminal for the third type REDCAP terminal. The terminal device transmits the second information to the network device by using the PRACH resource corresponding to the third type REDCAP terminal.
[0338] It can be understood that the network device may further configure, for each type of terminal, a PRACH resource corresponding to that type of terminal. In this way, when reporting the type of the terminal device, the terminal device transmits the second information to the network device by using the PRACH resource corresponding to the terminal device.
[0339] For example, the network device configures a PRACH resource corresponding to the first type REDCAP terminal for the first type REDCAP terminal, configures a PRACH resource corresponding to the second type REDCAP terminal for the second type REDCAP terminal, and configures a PRACH resource corresponding to the third type REDCAP terminal for the third type REDCAP terminal. When the terminal device is a first type REDCAP terminal, the terminal device transmits the second information to the network device by using a PRACH resource corresponding to the first type REDCAP terminal. When the terminal device is a second type REDCAP terminal, the terminal device transmits the second information to the network device by using a PRACH resource corresponding to the second type REDCAP terminal. When the terminal device is a third type REDCAP terminal, the terminal device transmits the second information to the network device by using a PRACH resource corresponding to the third type REDCAP terminal.
[0340] It may be appreciated that the PRACH resources may alternatively be predefined, for example, the PRACH resources may be defined in a protocol.
[0341] In another possible implementation, the second information is carried in Msg3, MsgA, or RRC signaling. In other words, the terminal device may report the type of the terminal in Msg3, MsgA, or RRC signaling. For the description of Msg3 and MsgA, please refer to the corresponding description in FIG. 1.
[0342] Furthermore, the second information includes a type identifier of the terminal device. For example, the identifier of the first type REDCAP terminal is ID1, and the identifier of the second type REDCAP terminal is ID2. When the second information includes ID1, the second information indicates that the type of the terminal device is a first type REDCAP terminal. When the second information includes ID2, the second information indicates that the type of the terminal device is a second type REDCAP terminal.
[0343] For example, the identifier of the third type REDCAP terminal is ID3. When the second information includes ID3, the second information indicates that the type of the terminal device is a third type REDCAP terminal.
[0344] It may be understood that when the network device indicates that the generic terminal is allowed to access the network device, the generic terminal may or may not report the terminal type. If the generic terminal does not report the terminal type, if the network device does not receive the type reported by the terminal device, the network device may determine that the terminal device is a generic terminal. The generic terminal may report the type of the terminal device to the network device by using multiple methods such as PRACH, Msg3, MsgA, or RRC signaling. For details, please refer to the description of reporting the terminal type by the REDCAP terminal in step 701. The details will not be described again.
[0345] Correspondingly, the network device receives second information from the terminal device. The network device can then determine the type of the terminal device based on the second information.
[0346] The terminal device is a first type REDCAP terminal or a second type REDCAP terminal. For the process in which the network device determines the type of the terminal device based on the second information, please refer to the description of step 401. Details will not be described again.
[0347] For example, the terminal device transmits the second information to the network device by using a PRACH resource corresponding to a third type REDCAP terminal. The network device determines that the terminal device is a third type REDCAP terminal.
[0348] For example, the identifier of the third type REDCAP terminal is ID3. When the second information includes ID3, the network device determines that the type of the terminal device is a third type REDCAP terminal.
[0349] Based on the method shown in Figure 7, the terminal device may report the type of the terminal device to the network device by using multiple methods such as PRACH, Msg3, MsgA, or RRC signaling, so that the network device identifies the type of the terminal device. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission and downlink transmission, the scheduled frequency range can be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device can use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability.
[0350] Optionally, in a possible implementation of the method shown in Figure 6, when the terminal device is a first type REDCAP terminal or a second type REDCAP terminal, and the first information indicates that the first type REDCAP terminal and the second type REDCAP terminal are permitted to access the network device, the terminal device reports the type of the terminal device to the network device by using the second information and the third information, so that the network device identifies the type of the terminal device. Specifically, as shown in Figure 8, the method shown in Figure 6 further includes steps 801 and 802.
[0351] Step 801: The terminal device sends second information to the network device.
[0352] Step 802: The terminal device sends third information to the network device.
[0353] For the description of step 801 and step 802, please refer to the description of step 501 and step 502. The details will not be described again.
[0354] Based on the method shown in FIG. 8, the terminal device may report the type of the terminal device to the network device in the second information and the third information, so that the network device identifies the type of the terminal device. In this way, when the network device schedules the REDCAP terminal to perform uplink transmission or downlink transmission, the scheduled frequency range may be prevented from exceeding the maximum bandwidth of the REDCAP terminal. Furthermore, when scheduling the REDCAP terminal to perform downlink reception, the network device may use a lower coding bit rate or perform repeated transmission to improve downlink transmission reliability. Furthermore, in the method shown in FIG. 8, the first type REDCAP terminal may share the PRACH resource with the second type REDCAP terminal, or the first type REDCAP terminal may share the PRACH resource with a general terminal. In this way, excessive division of the PRACH resource may be avoided, that is, excessive reduction of the random access capability is avoided.
[0355] The above has mainly described the solutions provided in the embodiments of the present application from the perspective of interactions between network elements. It can be understood that in order to implement the above functions, the above network devices or terminal equipment include corresponding hardware structures and / or software modules for implementing the functions. Those skilled in the art should easily realize that the present application can be implemented by hardware or a combination of hardware and computer software, in combination with the example units and algorithm operations described in the embodiments disclosed herein. Whether the functions are performed by hardware or hardware driven by computer software depends on the specific application or 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 it should not be considered that the implementation goes beyond the scope of the present application.
[0356] In the embodiment of the present application, the functional modules of the network device or terminal device may be divided according to the above method example. For example, each functional module may be divided according to the corresponding function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware, or may be implemented in the form of a software functional module. It should be noted that in the embodiment of the present application, the module division is an example and is merely a logical functional division. In actual implementation, other division manners may be used.
[0357] 9 is a schematic diagram of a structure of a communication device 90 according to an embodiment of the present application. For example, the communication device 90 is a terminal device 90. For example, the terminal device 90 is, for example, the terminal device of the embodiment shown in FIG. 3, the embodiment shown in FIG. 4, or the embodiment shown in FIG. 5.
[0358] The terminal device 90 includes a transceiver module 901 and a processing module 902. For example, the terminal device 90 may be a terminal device, or may be a chip used in a terminal device, or other composite device, component, etc. having the function of a terminal device. When the terminal device 90 is a terminal device, the transceiver module 901 may be a transceiver, which may include an antenna, a radio frequency circuit, etc., and the processing module 902 may be a processor (or processing circuit), for example, a baseband processor, which may include one or more CPUs. When the terminal device 90 is a component having the function of a terminal device, the transceiver module 901 may be a radio frequency unit, and the processing module 902 may be a processor (or processing circuit), for example, a baseband processor. When the terminal device 90 is a chip system, the transceiver module 901 may be an input / output interface of a chip (e.g., a baseband chip), and the processing module 902 may be a processor (or processing circuit) of the chip system, which may include one or more central processing units. It should be understood that the transceiver module 901 in this embodiment of the present application may be implemented by a transceiver or transceiver-related circuitry, and the processing module 902 may be implemented by a processor or processor-related circuitry (also referred to as processing).
[0359] For example, the transceiver module 901 may be configured to perform all the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 3, e.g., step 302, and / or may be configured to support other processes of the techniques described herein. The processing module 902 may be configured to perform all the operations other than the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 3, e.g., step 303, and / or may be configured to support other processes of the techniques described herein.
[0360] As another example, the transceiver module 901 may be configured to perform all the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 4, e.g., step 302 and step 401, and / or may be configured to support other processes of the techniques described herein. The processing module 902 may be configured to perform all the operations except for the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 4, e.g., step 303, and / or may be configured to support other processes of the techniques described herein.
[0361] As another example, the transceiver module 901 may be configured to perform all the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 5, e.g., step 302, step 501, and step 502, and / or may be configured to support other processes of the techniques described herein. The processing module 902 may be configured to perform all the operations except for the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 3, e.g., step 303, and / or may be configured to support other processes of the techniques described herein.
[0362] The transceiver module 901 is configured to receive first information from the network device, the first information indicating whether a REDCAP terminal is authorized to access the network device, the REDCAP terminal including a first type REDCAP terminal and a second type REDCAP terminal, the first type REDCAP terminal and the second type REDCAP terminal operating in the same frequency range, and 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.
[0363] The processing module 902 is configured to determine whether to access the network device based on the first information, where the communication device is a first type REDCAP terminal or a second type REDCAP terminal.
[0364] In a possible implementation, the first information includes first instruction information and second instruction information, where the first instruction information indicates whether a first type REDCAP terminal is authorized to access the network device and the second instruction information indicates whether a second type REDCAP terminal is authorized to access the network device, or the first instruction information indicates whether a first type REDCAP terminal is authorized to access the network device and the first instruction information and the second instruction information indicate whether a second type REDCAP terminal is authorized to access the network device.
[0365] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether a second type REDCAP terminal is authorized to access the network device, and 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, or the first indication information includes a cellBarred field in the MIB and the second indication information includes a spare field in the MIB or a reserved field in the additional PBCH payload.
[0366] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized 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.
[0367] In a possible implementation, the first information is included in an SSB, which includes a MIB and additional PBCH payload.
[0368] In a possible implementation, the first indication information is included in a reserved field in the DCI, the second indication information is included in the reserved field in the DCI, the first indication information is included in the reserved field in the DCI, the second indication information is included in a SIB1 information block, the first indication information is included in the SIB1 information block, the second 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 the SIB1 information block, and the DCI is used to schedule SIB1.
[0369] In a possible implementation, the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred 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 cellBarred field in the MIB, and the DCI is used to schedule SIB1.
[0370] In a possible implementation, the first information indicates that a first type REDCAP terminal and / or a second type REDCAP terminal is authorized to access the network device. The transceiver module 901 is configured to transmit second information to the network device, the second information indicating that the communication device is a first type REDCAP terminal or a second type REDCAP terminal.
[0371] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a first-type REDCAP terminal or a second-type REDCAP terminal, and the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, or the second information is carried in Msg3, MsgA, or RRC signaling.
[0372] In a possible implementation, the first information indicates that a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the network device. The transceiver module 901 is further configured to transmit second information to the network device, the second information indicating that the communication device is a REDCAP terminal. The transceiver module 901 is further configured to transmit third information to the network device, the third information indicating that the communication device is a first type REDCAP terminal or a second type REDCAP terminal.
[0373] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a REDCAP terminal, the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, and the third information is carried in Msg3, MsgA, or RRC signaling.
[0374] For other functions that may be implemented by the terminal device 90, please refer to the relevant descriptions of the embodiment shown in Fig. 3, the method embodiment shown in Fig. 4, or the embodiment shown in Fig. 5. Details will not be described again.
[0375] 10 is a schematic diagram of a structure of a communication device 100 according to an embodiment of the present application. For example, the communication device 100 is a network device 100. For example, the network device 100 is, for example, the network device of the embodiment shown in FIG. 3, the embodiment shown in FIG. 4, or the embodiment shown in FIG. 5.
[0376] The network device 100 includes a processing module 1001 and a transceiver module 1002. For example, the network device 100 may be a network device, or may be a chip used in a network device, or other composite device, component, etc. having the functionality of a network device. When the network device 100 is a network device, the processing module 1001 may be a processor (or processing circuit), for example, a baseband processor. The baseband processor may include one or more CPUs. The transceiver module 1002 may be a transceiver, which may include an antenna, a radio frequency circuit, etc. When the network device 100 is a component having the functionality of a network device, the processing module 1001 may be a processor (or processing circuit), for example, a baseband processor. The transceiver module 1002 may be a radio frequency unit. When the network device 100 is a chip system, the processing module 1001 may be a processor (or processing circuit) of the chip system, and may include one or more central processing units. The transceiver module 1002 may be an input / output interface of a chip (e.g., a baseband chip). It should be understood that the processing module 1001 in this embodiment of the present application may be implemented by a processor or processor-related circuitry (also called processing), and the transceiver module 1002 may be implemented by a transceiver or transceiver-related circuitry.
[0377] For example, processing module 1001 may be configured to perform all operations except for the transmit and receive operations, e.g., step 301, performed by the network device in the embodiment shown in Figure 3, and / or may be configured to support other processes of the techniques described herein. Transceiver module 1002 may be configured to perform all transmit and receive operations, e.g., step 302, performed by the network device in the embodiment shown in Figure 3, and / or may be configured to support other processes of the techniques described herein.
[0378] As another example, processing module 1001 may be configured to perform all operations except for the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 4, e.g., step 301, and / or may be configured to support other processes of the techniques described herein. Transceiver module 1002 may be configured to perform all transmit and receive operations performed by the terminal device in the embodiment shown in Figure 4, e.g., step 302 and step 401, and / or may be configured to support other processes of the techniques described herein.
[0379] As another example, processing module 1001 may be configured to perform all operations except for the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 5, e.g., step 301, and / or may be configured to support other processes of the techniques described herein. Transceiver module 1002 may be configured to perform all transmit and receive operations performed by the terminal device in the embodiment shown in Figure 5, e.g., step 302, step 501, and step 502, and / or may be configured to support other processes of the techniques described herein.
[0380] The processing module 1001 is configured to determine first information, the first information indicating whether a REDCAP terminal is authorized to access the communication device, the REDCAP terminal including a first type REDCAP terminal and a second type REDCAP terminal, the first type REDCAP terminal and the second type REDCAP terminal operating in the same frequency range, and 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.
[0381] The transceiver module 1002 is configured to transmit the first information to the terminal device.
[0382] In a possible implementation, the first information includes first indication information and second indication information, where the first indication information indicates whether a first type REDCAP terminal is authorized to access the communication device and the second indication information indicates whether a second type REDCAP terminal is authorized to access the communication device, or the first indication information indicates whether a first type REDCAP terminal is authorized to access the communication device and the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized to access the communication device.
[0383] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the communication device, and the second indication information indicates whether a second type REDCAP terminal is authorized to access the communication device, and 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, or the first indication information includes a cellBarred field in the MIB and the second indication information includes a spare field in the MIB or a reserved field in the additional PBCH payload.
[0384] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the communication device, the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized 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.
[0385] In a possible implementation, the first information is included in an SSB, which includes a MIB and additional PBCH payload.
[0386] In a possible implementation, the first indication information is included in a reserved field in the DCI, the second indication information is included in a reserved field in the DCI, the first indication information is included in a reserved field in the DCI and the second indication information is included in a SIB1 information block, the first indication information is included in the SIB1 information block and the second 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 the SIB1 information block, and the DCI is used to schedule SIB1.
[0387] In a possible implementation, the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred 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 cellBarred field in the MIB, and the DCI is used to schedule SIB1.
[0388] In a possible implementation, the first information indicates that a first type REDCAP terminal and / or a second type REDCAP terminal is authorized to access the communication device. The transceiver module 1002 is configured to receive second information from the terminal device, the second information indicating that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal.
[0389] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a first-type REDCAP terminal or a second-type REDCAP terminal, and the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, or the second information is carried in Msg3, MsgA, or RRC signaling.
[0390] In a possible implementation, the first information indicates that a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the communication device. The transceiver module 1002 is further configured to receive second information from the terminal device, the second information indicating that the terminal device is a REDCAP terminal. The transceiver module 1002 is further configured to receive third information from the terminal device, the third information indicating that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal.
[0391] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a REDCAP terminal, the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, and the third information is carried in Msg3, MsgA, or RRC signaling.
[0392] For other functions that may be implemented by the network device 100, please refer to the relevant descriptions of the embodiment shown in Fig. 3, the method embodiment shown in Fig. 4, or the embodiment shown in Fig. 5. Details will not be described again.
[0393] 11 is a schematic diagram of a structure of a communication device 110 according to an embodiment of the present application. For example, the structure of the communication device 110 is a terminal device 110. For example, the terminal device 110 is, for example, the terminal device of the embodiment shown in FIG. 6, the embodiment shown in FIG. 7, or the embodiment shown in FIG. 8.
[0394] The terminal device 110 includes a transceiver module 1101 and a processing module 1102. For example, the terminal device 110 may be a terminal device, or may be a chip used in a terminal device, or other composite device, component, etc. having the function of a terminal device. When the terminal device 110 is a terminal device, the transceiver module 901 may be a transceiver, which may include an antenna, a radio frequency circuit, etc., and the processing module 1102 may be a processor (or processing circuit), such as a baseband processor, which may include one or more CPUs. When the terminal device 110 is a component having the function of a terminal device, the transceiver module 1101 may be a radio frequency unit, and the processing module 1102 may be a processor (or processing circuit), such as a baseband processor. When the terminal device 110 is a chip system, the transceiver module 1101 may be an input / output interface of the chip (e.g., a baseband chip), and the processing module 1102 may be a processor (or processing circuit) of the chip system and may include one or more central processing units. It should be understood that the transceiver module 1101 in this embodiment of the present application may be implemented by a transceiver or a transceiver-related circuit component, and the processing module 1102 may be implemented by a processor or a processor-related circuit component (or referred to as processing).
[0395] For example, transceiver module 1101 may be configured to perform all of the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 6, e.g., step 602, and / or may be configured to support other processes of the techniques described herein. Processing module 1102 may be configured to perform all of the operations except for the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 3, e.g., step 603, and / or may be configured to support other processes of the techniques described herein.
[0396] As another example, transceiver module 1101 may be configured to perform all of the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 7, e.g., step 602 and step 701, and / or may be configured to support other processes of the techniques described herein. Processing module 1102 may be configured to perform all of the operations performed by the terminal device in the embodiment shown in Figure 7, except for the transmit and receive operations, e.g., step 603, and / or may be configured to support other processes of the techniques described herein.
[0397] As another example, transceiver module 1101 may be configured to perform all of the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 8, e.g., step 602, step 801, and step 802, and / or may be configured to support other processes of the techniques described herein. Processing module 1102 may be configured to perform all of the operations performed by the terminal device in the embodiment shown in Figure 8, except for the transmit and receive operations, e.g., step 603, and / or may be configured to support other processes of the techniques described herein.
[0398] The transceiver module 1101 is configured to receive first information from the network device, the first information indicating whether a REDCAP terminal is authorized 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 range, the frequency range in which the third type REDCAP terminal operates is different from the frequency range in which the first type REDCAP terminal and the second type REDCAP terminal operate, 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.
[0399] The processing module 1102 is configured to determine whether to access the network device based on the first information, where the communication device is a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal.
[0400] In a possible implementation, the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, and the first information includes first instruction information and second instruction information, where the first instruction information indicates whether the first type REDCAP terminal is authorized to access the network device and the second instruction information indicates whether the second type REDCAP terminal is authorized to access the network device, or the first instruction information indicates whether the first type REDCAP terminal is authorized to access the network device and the first instruction information and the second instruction information indicate whether the second type REDCAP terminal is authorized to access the network device.
[0401] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, and the second indication information indicates whether a second type REDCAP terminal is authorized to access the network device, and 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, or the first indication information includes a cellBarred field in the MIB and the second indication information includes a spare field in the MIB or a reserved field in the additional PBCH payload.
[0402] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the network device, the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized 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.
[0403] In a possible implementation, the first indication information is included in a reserved field in the DCI, the second indication information is included in a reserved field in the DCI, the first indication information is included in a reserved field in the DCI and the second indication information is included in a SIB1 information block, the first indication information is included in the SIB1 information block and the second 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 the SIB1 information block, and the DCI is used to schedule SIB1.
[0404] In a possible implementation, the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred 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 cellBarred field in the MIB, and the DCI is used to schedule SIB1.
[0405] In a possible implementation, the REDCAP terminal includes a third type REDCAP terminal, the first information includes third indication information, and the third indication information indicates whether the third type REDCAP terminal is authorized to access the network device.
[0406] In a possible implementation, the third indication information includes a spare field in the MIB, or the third indication information includes a cellBarred field in the MIB.
[0407] In a possible implementation, the first information is included in an SSB, which includes a MIB and additional PBCH payload.
[0408] In a possible implementation, the third indication information is included in a reserved field in the DCI, or the third indication information is included in the SIB1 information block.
[0409] In a possible implementation, the first information indicates that a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal is authorized to access the network device, or the first indication information indicates whether a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the network device. The transceiver module 1101 is configured to transmit second information to the network device, the second information indicating that the communication device is a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal.
[0410] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal, and the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, or the second information is carried in Msg3, MsgA, or RRC signaling.
[0411] In a possible implementation, the first information indicates that a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the network device. The transceiver module 1101 is further configured to transmit second information to the network device, the second information indicating that the communication device is a REDCAP terminal. The transceiver module 1101 is further configured to transmit third information to the network device, the third information indicating that the communication device is a first type REDCAP terminal or a second type REDCAP terminal.
[0412] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a REDCAP terminal, the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, and the third information is carried in Msg3, MsgA, or RRC signaling.
[0413] For other functions that may be implemented by the terminal device 110, please refer to the relevant descriptions of the embodiment shown in Figure 3, the method embodiment shown in Figure 4, or the embodiment shown in Figure 5. Details will not be described again.
[0414] 12 is a schematic diagram of a structure of a communication device 120 according to an embodiment of the present application. For example, the communication device 120 is a network device 120. For example, the network device 120 is the network device of the embodiment shown in FIG. 6, the embodiment shown in FIG. 7, or the embodiment shown in FIG. 8.
[0415] The network device 120 includes a processing module 1201 and a transceiver module 1202. For example, the network device 120 may be a network device, or may be a chip used in a network device, or other composite device, component, etc. having the functionality of a network device. When the network device 120 is a network device, the processing module 1201 may be a processor (or processing circuit), for example, a baseband processor. The baseband processor may include one or more CPUs. The transceiver module 1202 may be a transceiver, which may include an antenna, a radio frequency circuit, etc. When the network device 120 is a component having the functionality of a network device, the processing module 1201 may be a processor (or processing circuit), for example, a baseband processor. The transceiver module 1202 may be a radio frequency unit. When the network device 120 is a chip system, the processing module 1201 may be a processor (or processing circuit) of the chip system, and may include one or more central processing units. The transceiver module 1202 may be an input / output interface of a chip (e.g., a baseband chip). It should be understood that the processing module 1201 in this embodiment of the present application may be implemented by a processor or processor-related circuitry (also called processing), and the transceiver module 1202 may be implemented by a transceiver or transceiver-related circuitry.
[0416] For example, processing module 1201 may be configured to perform all operations except for the transmit and receive operations, e.g., step 601, performed by the network device in the embodiment shown in Figure 6, and / or may be configured to support other processes of the techniques described herein. Transceiver module 1202 may be configured to perform all transmit and receive operations, e.g., step 602, performed by the network device in the embodiment shown in Figure 6, and / or may be configured to support other processes of the techniques described herein.
[0417] As another example, processing module 1201 may be configured to perform all operations except for the transmit and receive operations performed by the terminal device in the embodiment shown in Figure 7, e.g., step 601, and / or may be configured to support other processes of the techniques described herein. Transceiver module 1202 may be configured to perform all transmit and receive operations performed by the terminal device in the embodiment shown in Figure 7, e.g., steps 602 and 701, and / or may be configured to support other processes of the techniques described herein.
[0418] As another example, processing module 1201 may be configured to perform all operations except for the transmit and receive operations performed by the terminal device in the embodiment shown in FIG. 8, e.g., step 601, and / or may be configured to support other processes of the techniques described herein. Transceiver module 1202 may be configured to perform all transmit and receive operations performed by the terminal device in the embodiment shown in FIG. 8, e.g., step 602, step 801, and step 802, and / or may be configured to support other processes of the techniques described herein.
[0419] The processing module 1201 is configured to determine first information, the first information indicating whether a REDCAP terminal is authorized to access the communication 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 range, the frequency range in which the third type REDCAP terminal operates is different from the frequency range in which the first type REDCAP terminal and the second type REDCAP terminal operate, 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.
[0420] The transceiver module 1202 is configured to transmit the first information to the terminal device.
[0421] In a possible implementation, the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, and the first information includes first indication information and second indication information, where the first indication information indicates whether the first type REDCAP terminal is authorized to access the communication device and the second indication information indicates whether the second type REDCAP terminal is authorized to access the communication device, or the first indication information indicates whether the first type REDCAP terminal is authorized to access the communication device and the first indication information and the second indication information indicate whether the second type REDCAP terminal is authorized to access the communication device.
[0422] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the communication device, and the second indication information indicates whether a second type REDCAP terminal is authorized to access the communication device, and 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, or the first indication information includes a cellBarred field in the MIB and the second indication information includes a spare field in the MIB or includes a reserved field in the additional PBCH payload.
[0423] In a possible implementation, the first indication information indicates whether a first type REDCAP terminal is authorized to access the communication device, the first indication information and the second indication information indicate whether a second type REDCAP terminal is authorized 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.
[0424] In a possible implementation, the first indication information is included in a reserved field in the DCI, the second indication information is included in a reserved field in the DCI, the first indication information is included in a reserved field in the DCI and the second indication information is included in a SIB1 information block, the first indication information is included in the SIB1 information block and the second 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 the SIB1 information block, and the DCI is used to schedule SIB1.
[0425] In a possible implementation, the first indication information includes a spare field in the MIB, a reserved field in the additional PBCH payload, or a cellBarred 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 a 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 a 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 cellBarred field in the MIB, and the DCI is used to schedule SIB1. In a possible implementation, the REDCAP terminal includes a third type REDCAP terminal, the first information includes third indication information, and the third indication information indicates whether the third type REDCAP terminal is authorized to access the communication device.
[0426] In a possible implementation, the third indication information includes a spare field in the MIB, or the third indication information includes a cellBarred field in the MIB.
[0427] In a possible implementation, the first information is included in an SSB, which includes a MIB and additional PBCH payload.
[0428] In a possible implementation, the third indication information is included in a reserved field in the DCI, or the third indication information is included in the SIB1 information block.
[0429] In a possible implementation, the first information indicates that a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal is authorized to access the communication device, or the first indication information indicates whether a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the communication device. The transceiver module 1202 is configured to receive second information from the terminal device, the second information indicating that the terminal device is a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal.
[0430] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a first type REDCAP terminal, a second type REDCAP terminal, or a third type REDCAP terminal, and the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, or the second information is carried in Msg3, MsgA, or RRC signaling.
[0431] In a possible implementation, the first information indicates that a first type REDCAP terminal and a second type REDCAP terminal are authorized 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 is a REDCAP terminal. The transceiver module 1202 is further configured to receive third information from the terminal device, the third information indicating that the terminal device is a first type REDCAP terminal or a second type REDCAP terminal.
[0432] In a possible implementation, the second information is carried in a PRACH, the resources of the PRACH correspond to a REDCAP terminal, the resources of the PRACH include at least one of the following: time domain resources of the PRACH, frequency domain resources of the PRACH, or code domain resources of the PRACH, and the third information is carried in Msg3, MsgA, or RRC signaling.
[0433] For other functions that may be implemented by the network device 120, please refer to the relevant descriptions of the embodiment shown in Figure 6, the method embodiment shown in Figure 7, or the embodiment shown in Figure 8. Details will not be described again.
[0434] 13 is a schematic diagram of a structure of a chip according to an embodiment of the present application. The chip 130 includes one or more processors 1301 and an interface circuit 1302. Optionally, the chip 130 may further include a bus 1303.
[0435] The processor 1301 may be an integrated circuit chip and has signal processing capabilities. In the implementation process, the steps of the above method may be completed by using an integrated logic circuit of hardware in the processor 1301 or an instruction in the form of software. The 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 device, a discrete gate or transceiver logic device, or a discrete hardware component. The processor may implement or execute the methods and steps disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc.
[0436] The interface circuit 1302 is configured to transmit or receive data, instructions, or information. The processor 1301 may perform processing by using the data, instructions, or other information received by the interface circuit 1302, and may transmit the processed information by using the interface circuit 1302.
[0437] Optionally, the chip 130 further includes memory, which may include read-only memory and random access memory, to provide operating instructions and data to the processor, and a portion of the memory may further include non-volatile random access memory (NVRAM).
[0438] Optionally, the memory may store executable software modules or data structures, and the processor may perform corresponding operations by invoking operational instructions stored in the memory (which may be stored in an operating system).
[0439] Optionally, the chip 130 may be used in a communication device (including a terminal device or a network device) in the embodiments of the present application. Optionally, the interface circuit 1302 may be configured to output the execution result of the processor 1301. For the communication method provided in one or more embodiments of the present application, please refer to the above embodiments. Details will not be described again here.
[0440] It should be noted that the functions corresponding to the processor 1301 and the interface circuit 1302 may be implemented by using a hardware design, may be implemented by using a software design, or may be implemented by combining software and hardware, which is not limited here.
[0441] Fig. 14 is a schematic diagram of a configuration of a communication system. As shown in Fig. 14, the communication system 140 may include a terminal device 1401 and a network device 1402. Fig. 14 is only an exemplary accompanying drawing, and the network elements and the number of network elements included in the communication system 140 shown in Fig. 14 are not limited in this embodiment of the present application.
[0442] The terminal device 1401 has the functionality of the communication device shown in FIG. 9 and may be configured to receive first information from the network device 1402 indicating whether a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the network device 1402, and to determine whether to access the network device 1402 based on the first information.
[0443] The network device 1402 may have the functionality of the communications device shown in FIG. 10 and may be configured to determine first information indicating whether a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the network device 1402 and to transmit the first information to the terminal device 1401.
[0444] Alternatively, the terminal device may have the functionality of the communications device shown in FIG. 11 and be configured to receive first information from the network device 1402 indicating whether a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the network device 1402, or receive first information from the network device 1402 indicating whether a third type REDCAP terminal is authorized to access the network device, and determine whether to access the network device 1402 based on the first information.
[0445] The network device 1402 may have the functionality of the communication device shown in FIG. 12 and may be configured to determine first information indicating whether a first type REDCAP terminal and a second type REDCAP terminal are authorized to access the network device 1402, or to determine first information indicating whether a third type REDCAP terminal is authorized to access the network device and transmit the first information to the terminal device 1401.
[0446] It should be noted that all relevant contents of the steps in the above method embodiments may be cited in the functional description of the corresponding network elements in the communication system 140. The details will not be described again here.
[0447] The above description of the implementation allows those skilled in the art to understand that the above division of functional modules is taken as an example for explanation, for convenience and concise description. In actual application, the above functions can be allocated to different modules and implemented according to requirements, that is, the internal structure of the device is divided into different functional modules to implement all or part of the above functions.
[0448] In some embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the described apparatus embodiment is merely an example. For example, the modularization or division into units is merely a logical division of functions, and may be other divisions in actual implementation. For example, multiple units or components may be combined or integrated into other devices, or some features may be omitted or not implemented. Furthermore, the shown or discussed mutual couplings or direct couplings or communication connections may be implemented by using some interface. Indirect couplings or communication connections between devices or units may be implemented in electronic, mechanical, or other forms.
[0449] The units described as separate parts may or may not be physically separated, and the parts shown as units may be one or more physical units, located in one place or distributed in different places. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.
[0450] Furthermore, the functional units in the embodiments of the present application may be integrated into one processing unit, each of the units may exist physically alone, or two or more units may be integrated into one unit. The integrated units may be implemented in the form of hardware or software functional units.
[0451] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a readable storage medium. Based on such understanding, the technical solution of the present application may be essentially, or the part contributing to the prior art, or all or part of the technical solution may be implemented in the form of a software product. The software product is stored in a storage medium and includes some instructions for instructing a device (which may be a single-core microcomputer, chip, etc.) or a processor to execute all or part of the steps of the method described in the embodiments of the present application. The above storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.
[0452] The above description is merely a specific implementation of the present application, and is not intended to limit the protection scope of the present application. Any variation or replacement within the technical scope disclosed in the present application should fall within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
[0453] This application claims priority to Chinese Patent Application No. 202011032886.X, filed with the State Intellectual Property Office of the People's Republic of China on September 27, 2020, for the invention titled "NETWORK DEVICE ACCESSING METHOD AND APPARATUS," the entire text of which is incorporated herein by reference.
Claims
1. A network device access method applied to a terminal device or to a chip in the terminal device, comprising: receiving first information from a network device, the first information indicating whether a reduced performance (REDCAP) terminal is permitted to access the network device, the REDCAP terminal including a first type REDCAP terminal and a second type REDCAP terminal, the first type REDCAP terminal and the second type REDCAP terminal operate in the same frequency range, and the number of receiving antennas of the second type REDCAP terminal is less than that of the first type REDCAP terminal; determining whether to access the network device based on the first information, the terminal device being the first type REDCAP terminal or the second type REDCAP terminal; The method according to claim 1,
2. the first information includes first indication information and second indication information, The first indication information indicates whether the first type REDCAP terminal is permitted to access the network device, and the second indication information indicates whether the second type REDCAP terminal is permitted to access the network device, or the first indication information indicates whether the first type REDCAP terminal is permitted to access the network device, and the first indication information and the second indication information indicate whether the second type REDCAP terminal is permitted to access the network device. The method of claim 1.
3. The first indication information is included in a reserved field in Downlink Control Information (DCI), and the second indication information is included in the reserved field in the DCI; or The first indication information is included in a reserved field in a DCI, and the second indication information is included in a system information block type 1 (SIB1); or The first indication information is included in SIB1, and the second indication information is included in a reserved field in DCI; or The first indication information is included in SIB1, and the second indication information is included in SIB1; The DCI is used to schedule the SIB1. The method of claim 2.
4. the first information indicates that the first type REDCAP terminal and the second type REDCAP terminal are authorized to access the network device; The method comprises: sending second information to the network device, the second information indicating that the terminal device is a REDCAP terminal; and sending third information to the network device, the third information indicating that the terminal device is the first type REDCAP terminal or the second type REDCAP terminal; Further comprising 4. The method according to any one of claims 1 to 3.
5. The second information is carried in Msg3 or MsgA, or the second information is carried in a PRACH, and a resource of the PRACH corresponds to the REDCAP terminal, and the resource of the PRACH includes at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH; The third information is carried by Msg3, MsgA, or RRC signaling. The method according to claim 4.
6. The number of receiving antennas of the second type REDCAP terminal is 1; The number of receiving antennas of the first type REDCAP terminal is two.
6. The method according to any one of claims 1 to 5.
7. A network device access method applied to a network device or to a chip within said network device, comprising: determining first information, the first information indicating whether a reduced performance (REDCAP) terminal is permitted to access the network device, the REDCAP terminal including a first type REDCAP terminal and a second type REDCAP terminal, the first type REDCAP terminal and the second type REDCAP terminal operate in the same frequency range, and a number of receiving antennas of the second type REDCAP terminal is less than that of the first type REDCAP terminal; transmitting the first information to a terminal device; The method according to claim 1,
8. the first information includes first indication information and second indication information, The first indication information indicates whether the first type REDCAP terminal is permitted to access the network device, and the second indication information indicates whether the second type REDCAP terminal is permitted to access the network device, or the first indication information indicates whether the first type REDCAP terminal is permitted to access the network device, and the first indication information and the second indication information indicate whether the second type REDCAP terminal is permitted to access the network device. The method of claim 7.
9. The first indication information is included in a reserved field in Downlink Control Information (DCI), and the second indication information is included in the reserved field in the DCI; or The first indication information is included in a reserved field in a DCI, and the second indication information is included in a system information block type 1 (SIB1); or The first indication information is included in SIB1, and the second indication information is included in a reserved field in DCI; or The first indication information is included in SIB1, and the second indication information is included in SIB1; The DCI is used to schedule the SIB1. The method according to claim 8.
10. the first information indicates that the first type REDCAP terminal and the second type REDCAP terminal are authorized to access the network device; The method comprises: receiving second information from the terminal device, the second information indicating that the terminal device is a REDCAP terminal; and receiving third information from the terminal device, the third information indicating that the terminal device is the first type REDCAP terminal or the second type REDCAP terminal; Further comprising 10. The method according to any one of claims 7 to 9.
11. The second information is carried in Msg3 or MsgA, or the second information is carried in a PRACH, and a resource of the PRACH corresponds to the REDCAP terminal, and the resource of the PRACH includes at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH; The third information is carried by Msg3, MsgA, or RRC signaling. The method of claim 10.
12. The number of receiving antennas of the second type REDCAP terminal is 1; The number of receiving antennas of the first type REDCAP terminal is two.
12. The method according to any one of claims 7 to 11.
13. A communication device having a receiving module and a processing module, The receiving module is configured to receive first information, the first information indicating whether a reduced performance (REDCAP) terminal is allowed to access a network device, the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, the first type REDCAP terminal and the second type REDCAP terminal operate in the same frequency range, and the number of receiving antennas of the second type REDCAP terminal is less than that of the first type REDCAP terminal; The processing module is configured to determine whether to access the network device based on the first information, the communication device belonging to the first type REDCAP terminal or the second type REDCAP terminal; Communications equipment.
14. the first information includes first indication information and second indication information, The first indication information indicates whether the first type REDCAP terminal is permitted to access the network device, and the second indication information indicates whether the second type REDCAP terminal is permitted to access the network device, or the first indication information indicates whether the first type REDCAP terminal is permitted to access the network device, and the first indication information and the second indication information indicate whether the second type REDCAP terminal is permitted to access the network device.
14. The communication device of claim 13.
15. The first indication information is included in a reserved field in Downlink Control Information (DCI), and the second indication information is included in the reserved field in the DCI; or The first indication information is included in a reserved field in a DCI, and the second indication information is included in a system information block type 1 (SIB1); or The first indication information is included in SIB1, and the second indication information is included in a reserved field in DCI; or The first indication information is included in SIB1, and the second indication information is included in SIB1; The DCI is used to schedule the SIB1.
15. The communication device of claim 14.
16. the first information indicates that the first type REDCAP terminal and the second type REDCAP terminal are authorized to access the network device; The communication device further comprises a transmitting module; The transmitting module is configured to transmit second information to the network device, the second information indicating that the communication device is a REDCAP terminal; the transmitting module is further configured to transmit third information to the network device, the third information indicating that the communication device is the first type REDCAP terminal or the second type REDCAP terminal; A communication device according to any one of claims 13 to 15.
17. The second information is carried in Msg3 or MsgA, or the second information is carried in a PRACH, and a resource of the PRACH corresponds to the REDCAP terminal, and the resource of the PRACH includes at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH; The third information is carried by Msg3, MsgA, or RRC signaling.
17. The communication device of claim 16.
18. The number of receiving antennas of the second type REDCAP terminal is 1; The number of receiving antennas of the first type REDCAP terminal is two. A communication device according to any one of claims 13 to 17.
19. A communication device having a processing module and a transmission module, The processing module is configured to determine first information, the first information indicating whether a reduced performance (REDCAP) terminal is allowed to access the communication device, the REDCAP terminal includes a first type REDCAP terminal and a second type REDCAP terminal, the first type REDCAP terminal and the second type REDCAP terminal operate in the same frequency range, and a number of receiving antennas of the second type REDCAP terminal is less than that of the first type REDCAP terminal; The transmission module is configured to transmit the first information to a terminal device. Communications equipment.
20. the first information includes first indication information and second indication information, The first indication information indicates whether the first type REDCAP terminal is authorized to access the communication device, and the second indication information indicates whether the second type REDCAP terminal is authorized to access the communication device, or the first indication information indicates whether the first type REDCAP terminal is authorized to access the communication device, and the first indication information and the second indication information indicate whether the second type REDCAP terminal is authorized to access the communication device.
20. The communication device of claim 19.
21. The first indication information is included in a reserved field in Downlink Control Information (DCI), and the second indication information is included in the reserved field in the DCI; or The first indication information is included in a reserved field in a DCI, and the second indication information is included in a system information block type 1 (SIB1); or The first indication information is included in SIB1, and the second indication information is included in a reserved field in DCI; or The first indication information is included in SIB1, and the second indication information is included in SIB1; The DCI is used to schedule the SIB1.
21. The communication device of claim 20.
22. the first information indicates that the first type REDCAP terminal and the second type REDCAP terminal are authorized to access the communication device; The communication device further comprises a receiving module; The receiving module is configured to receive second information from the terminal device, the second information indicating that the terminal device is a REDCAP terminal; the receiving module is further configured to receive third information from the terminal device, the third information indicating that the terminal device is the first type REDCAP terminal or the second type REDCAP terminal; 22. A communication device according to any one of claims 19 to 21.
23. The second information is carried in Msg3 or MsgA, or the second information is carried in a PRACH, and a resource of the PRACH corresponds to the REDCAP terminal, and the resource of the PRACH includes at least one of the following: a time domain resource of the PRACH, a frequency domain resource of the PRACH, or a code domain resource of the PRACH; The third information is carried by Msg3, MsgA, or RRC signaling.
23. The communication device of claim 22.
24. The number of receiving antennas of the second type REDCAP terminal is 1; The number of receiving antennas of the first type REDCAP terminal is two.
24. A communication device according to any one of claims 19 to 23.
25. 1. A communications device having a processor, comprising: the processor is coupled to a memory, the memory being configured to store programs or instructions; When the program or the instructions are executed by the processor, the communication device is capable of performing the method according to any one of claims 1 to 6 or the method according to any one of claims 7 to 12. Communications equipment.
26. comprising instructions which, when executed by a processor of a device, cause said device to carry out a method according to any one of claims 1 to 6 or any one of claims 7 to 12, Computer-readable medium.
27. A communication system comprising a communication device according to any one of claims 13 to 18 and / or a communication device according to any one of claims 19 to 24.
Citation Information
Patent Citations
Network device access method and apparatus
JP2023544558A