Communication method and device

Abstract

This application provides a communication method, including: a terminal device receiving a Master Information Block (MIB), the MIB including first indication information and second indication information, the first indication information indicating whether a cell is prohibited, and the second indication information indicating whether a cell reselection operation is permitted; when the first indication information indicates that the cell is prohibited, the terminal device determines whether to perform a cell reselection operation based on the second indication information, wherein the terminal device is a RedCap UE with reduced capabilities. Based on the above technical solution, RedCap UEs can use different IFR indications when a cell is prohibited, thereby accelerating the efficiency of the terminal device in determining whether to perform a cell reselection operation.

Description

[0001] This application is a divisional application. The original application has the application number 202111193246.1 and the original application date is October 13, 2021. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method, apparatus, and system. Background Technology

[0003] The three main scenarios for the 5th generation (5G) new radio (NR) include: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communication (mMTC).

[0004] Reduced capability UEs (RedCap UEs) are a further enhancement technology for 5G NR. These UEs have lower capabilities compared to eMBB and URLLC. For example, RedCap UEs may reduce the complexity of features such as: reduced maximum bandwidth capability, reduced number of transmit / receive antennas / antenna branches, reduced maximum multiple input multiple output (MIMO) layers, and reduced maximum modulation order.

[0005] In the existing technology, there are still some problems with the access control process of RedCap UE, such as low access efficiency and additional energy consumption. Therefore, the technical staff is currently working to optimize the access control process of RedCap UE.

[0006] Therefore, the embodiments of this application aim to solve the problems of how to enable RedCap UEs to use different IFR indications when the cell is prohibited, so as to speed up the efficiency of terminal equipment to determine the cell reselection operation; and how to design a UE behavior rule when a specific RedCap IFR is not sent, so as to clarify how the UE determines the same frequency reselection operation. Summary of the Invention

[0007] This application provides a communication method that enables a terminal device (RedCap UE) to use different IFR indications when a cell is prohibited, thereby speeding up the efficiency of the terminal device in determining the cell reselection operation. It also enables the design of a behavior rule for cases where a specific RedCap IFR is not sent, so as to clarify how the terminal device (RedCap UE) determines the same-frequency reselection operation.

[0008] In a first aspect, a communication method is provided, comprising: a terminal device receiving a Master Information Block (MIB), the MIB including first indication information and second indication information, the first indication information indicating whether a cell is prohibited, and the second indication information indicating whether a co-frequency reselection operation is permitted; when the first indication information indicates that the cell is prohibited, the terminal device determines whether to perform a co-frequency reselection operation based on the second indication information, wherein the terminal device is a RedCap UE with reduced capabilities.

[0009] It should be noted that the embodiments of this application are not limited to RedCap UE as the terminal device. That is, the embodiments of this application are also applicable to terminals that have the same or similar access control mechanisms as RedCap UE.

[0010] Based on the above technical solution, the terminal device (RedCap UE) receives the Master Information Block (MIB) and, if the first indication information in the MIB indicates that the current cell is prohibited, determines whether to perform a cell reselection operation based on the second indication information in the MIB. This enables the terminal device (RedCap UE) to use different IFR indications when a cell is prohibited, thereby accelerating the efficiency of the terminal device in determining whether to perform a cell reselection operation.

[0011] In a second aspect, a communication method is provided, comprising: a terminal device receiving first information; and, if the first information does not include third indication information, the terminal device determining that a same-frequency reselection operation is permitted, wherein the third indication information is used to indicate whether a same-frequency reselection operation is permitted.

[0012] It should be noted that the embodiments of this application are not limited to RedCap UE as the terminal device. That is, the embodiments of this application are also applicable to terminals that have the same or similar access control mechanisms as RedCap UE.

[0013] Based on the above technical solution, the terminal device (RedCap UE) receives first information. If the first information does not include third indication information indicating whether to perform a frequency reselection operation, the terminal device determines that a frequency reselection operation is allowed. Therefore, a behavioral rule is designed for situations where a specific RedCap IFR is not sent, to clarify how the terminal device (RedCap UE) determines the frequency reselection operation.

[0014] In conjunction with the second aspect, in some implementations of the second aspect, the first information further includes fourth indication information, and the method further includes: the terminal device determines that the current cell of the terminal device is blocked according to the fourth indication information, wherein the fourth indication information is used to indicate whether the current cell of the terminal device is blocked.

[0015] In conjunction with the second aspect, in some implementations of the second aspect, the terminal device is a RedCap UE with reduced capabilities.

[0016] Thirdly, a communication method is provided, comprising: a network device sending a main information block (MIB), the MIB including first indication information and second indication information, the first indication information being used to indicate whether a cell is prohibited, and the second indication information being used to indicate whether a co-frequency reselection operation is permitted; when the first indication information indicates that the cell is prohibited, the second indication information being used to indicate whether a terminal device is to perform a co-frequency reselection operation, wherein the terminal device is a RedCap UE with reduced capabilities.

[0017] Based on the above technical solution, the network device sends a Master Information Block (MIB) to the terminal device (RedCap UE). If the first indication information in the MIB indicates that the current cell is blocked, the second indication information in the MIB indicates whether to perform a cell reselection operation. This allows the terminal device (RedCap UE) to use different IFR indications when a cell is blocked, thereby accelerating the efficiency of the terminal device in determining whether to perform a cell reselection operation.

[0018] Fourthly, a communication method is provided, comprising: a network device sending first information; and, if the first information does not include third indication information, instructing a terminal device to determine whether a same-frequency reselection operation is permitted, wherein the third indication information is used to indicate whether a same-frequency reselection operation is permitted.

[0019] Based on the above technical solution, the network device sends a first message to the terminal device (RedCap UE). If the first message does not include a third indication message indicating whether to perform a frequency reselection operation, the network device indicates that the terminal device is allowed to perform a frequency reselection operation. Therefore, a behavioral rule is designed for the case where a specific RedCap IFR is not sent, to clarify how the terminal device (RedCap UE) determines the frequency reselection operation.

[0020] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first information also includes fourth indication information, and the method further includes: the fourth indication information is used to indicate that the current cell of the terminal device is blocked.

[0021] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the terminal device is a RedCap UE with reduced capabilities.

[0022] Fifthly, a communication apparatus is provided, comprising: a receiving unit for receiving a Master Information Block (MIB), the MIB including first indication information and second indication information, the first indication information indicating whether a cell is prohibited and the second indication information indicating whether a co-frequency reselection operation is permitted; and a processing unit for determining, based on the second indication information, whether to perform a co-frequency reselection operation when the first indication information indicates that the cell is prohibited, wherein the terminal device is a RedCap UE with reduced capabilities.

[0023] A sixth aspect provides a communication device, comprising: a receiving unit for receiving first information; and a processing unit for determining, in the absence of third indication information, that a same-frequency reselection operation is permitted, wherein the third indication information is used to indicate whether a same-frequency reselection operation is permitted.

[0024] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the first information further includes fourth indication information, and the processing unit is further configured to: determine that the current cell of the terminal device is blocked based on the fourth indication information, wherein the fourth indication information is used to indicate whether the current cell of the terminal device is blocked.

[0025] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the terminal device is a RedCap UE with reduced capabilities.

[0026] A seventh aspect provides a communication apparatus, comprising: a transmitting unit for transmitting a main information block (MIB), the MIB including first indication information and second indication information, the first indication information indicating whether a cell is prohibited and the second indication information indicating whether a co-frequency reselection operation is permitted; and a processing unit, wherein, when the first indication information indicates that the cell is prohibited, the second indication information is used to instruct a terminal device whether to perform a co-frequency reselection operation, wherein the terminal device is a RedCap UE with reduced capabilities.

[0027] Eighthly, a communication apparatus is provided, comprising: a transmitting unit for transmitting first information; and a processing unit for instructing a terminal device to determine whether a same-frequency reselection operation is permitted, provided that the first information does not include third indication information, wherein the third indication information is used to indicate whether a same-frequency reselection operation is permitted.

[0028] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the first information further includes fourth indication information, and the processing unit is further configured to: the fourth indication information is used to indicate that the current cell of the terminal device is blocked.

[0029] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the terminal device is a RedCap UE with reduced capabilities.

[0030] Ninthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform the method in any of the possible implementations of the first to fourth aspects described above.

[0031] In a tenth aspect, a computer-readable medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods in any of the possible implementations of the first to fourth aspects described above.

[0032] Eleventhly, a chip system is provided, including a memory and a processor, the memory for storing a computer program and the processor for calling and running the computer program from the memory, such that a communication device equipped with the chip system performs the method in any of the possible implementations of the first to fourth aspects described above.

[0033] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data. Attached Figure Description

[0034] Figure 1 This is a schematic diagram of a system architecture applied in this application.

[0035] Figure 2 This is a schematic flowchart of a communication method provided in an embodiment of this application.

[0036] Figure 3 This is a schematic flowchart illustrating a communication method provided in another embodiment of this application.

[0037] Figure 4 This is a schematic flowchart illustrating a communication method provided in another embodiment of this application.

[0038] Figure 5 This is a schematic flowchart illustrating a communication method provided in another embodiment of this application.

[0039] Figure 6 This is a schematic flowchart illustrating a communication method provided in another embodiment of this application.

[0040] Figure 7 This is a schematic block diagram of the device 700 provided in this application.

[0041] Figure 8This is a schematic block diagram of the device 800 provided in this application.

[0042] Figure 9 This is a schematic structural diagram of the device provided in the embodiments of this application. Detailed Implementation

[0043] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0044] The technical solutions provided in this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th Generation (5G) systems, or New Radio (NR), etc.

[0045] Terminal equipment can be user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device. In the embodiments of this application, terminal equipment can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc.

[0046] Access network equipment can be an evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved Node B (or home Node B (HNB)), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP) in a wireless fidelity (WIFI) system. Access network equipment can also be a gNB in ​​5G, such as NR, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU).

[0047] In some deployments, a gNB may include a centralized unit (CU) and a distribution unit (DU). A gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), media access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered to be sent by the DU, or by the DU+AAU. It is understood that network devices can be devices that include one or more of the following: CU nodes, DU nodes, and AAU nodes. In addition, the CU can be classified as a network device in the radio access network (RAN) or as a network device in the core network (CN), and this application does not limit this.

[0048] The naming of network elements may differ in different network systems. The following explanation uses the naming of network elements in 5G networks as an example to illustrate this application.

[0049] First, combined Figure 1 The diagram shown illustrates the 5G network architecture and provides a brief explanation of the main network elements involved in the 5G network system.

[0050] 1. User equipment (UE) 101: Corresponding terminal equipment.

[0051] 2. Radio access network (RAN) element 102: hereinafter referred to as RAN, corresponding to access network equipment. For example, RAN can be an NB, eNB, gNB, ng-eNB, or any other access network equipment.

[0052] 3. User plane function (UPF) 103: Used for packet routing and forwarding, as well as quality of service (QoS) processing of user plane data.

[0053] 4. Data network (DN) 104: A network used to provide data transmission.

[0054] 5. AMF 105: Corresponding mobility management network element.

[0055] 6. Session Management Function (SMF) 106: Primarily used for session management, allocation and management of Internet Protocol (IP) addresses for user equipment, selection of manageable user plane functions, endpoints for policy control and billing function interfaces, and downlink data notification, etc.

[0056] 7. Policy control function (PCF) 107: A unified policy framework used to guide network behavior, providing policy rule information to control plane function elements (such as AMF, SMF, etc.).

[0057] 8. Application function (AF) 108: Used for data routing affected by applications, accessing network open function elements, and interacting with the policy framework for policy control, etc.

[0058] 9. Unified Data Management (UDM) 109: Used to handle UE identification, access authentication, registration, and mobility management, etc.

[0059] 10. Unified Data Repository (UDR): This mainly includes the following functions: access to data types such as contract data, policy data, and application data.

[0060] It is understood that the aforementioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0061] It should be understood that, Figure 1 The interfaces between network elements shown are merely examples and should not be construed as limiting this application.

[0062] It should also be understood that the network architecture described above for the embodiments of this application is merely an example, and the network architecture applicable to the embodiments of this application is not limited thereto. Any network architecture capable of realizing the functions of the above-described network elements is applicable to the embodiments of this application.

[0063] It should also be understood that Figure 1 The 5G system architecture shown is one application scenario / network architecture of this application embodiment. This application embodiment can also be applied to other application scenarios / network architectures, such as the communication architecture between terminal devices and gNB (5G base station) or next-generation evolved NodeB (ng-eNB) (i.e., 4G base station connected to the core network). This application embodiment does not limit this.

[0064] The above content briefly describes the system architecture and possible application scenarios of the embodiments of this application. In order to better understand the technical solutions of the embodiments of this application, before introducing the embodiments of this application, the nouns or terms involved in this application will be briefly introduced first.

[0065] 1. Reduced capability UE (RedCap UE)

[0066] RedCap UE refers to a terminal with reduced capabilities, which are lower-end compared to enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC). For example, RedCap UE may reduce the complexity of features such as: reduced maximum bandwidth capability, reduced number of transmit and receive antennas / antenna branches, reduced maximum multiple input multiple output (MIMO) layer capability, reduced maximum modulation order capability, and support for half-frequency division duplexing (FDD), etc.

[0067] 2. System Information (SI)

[0068] System information is a message sent by the base station that contains information required for UE initialization, as well as information related to other functions / features. System information is divided into minimum system information (Minimum SI) and other system information (Other SI).

[0069] The minimum system information consists of the master information block (MIB) and system information block 1 (SIB1), also known as the remaining minimum system information (RMSI). The MIB is periodically broadcast on the broadcast channel (BCH). SIB1 is periodically broadcast on the downlink shared channel (DL-SCH) or sent to RRC-connected UEs via dedicated signaling.

[0070] Other system information consists of other SIBs, such as SIB2 to SIB9. Other SIBs are broadcast periodically on the DL-SCH, or on demand (i.e., the network only broadcasts a certain SIB when an RRC idle (RRC_IDLE) or RRC inactive (RRC_INACTIVE) UE requests it; otherwise, it does not send the SIB), or they are sent to RRC connected UEs via dedicated signaling.

[0071] It should be noted that the basic process for the UE to obtain system information in the RRC idle state and RRC inactive state is as follows: the UE first obtains the MIB, obtains SIB1 based on the scheduling information in the MIB, and then obtains other SIBs based on the scheduling information in SIB1.

[0072] 3. Cell bar mechanism

[0073] It is an access control mechanism. In NR, the network sends a cell-barred field in the main information block (MIB), which indicates whether the current cell is barred or not barred. If a cell is barred, UEs in RRC idle state and RRC inactive state cannot camp on that cell, and will not consider that cell as a candidate cell for cell reselection for a certain period of time.

[0074] 4. Intra-frequency reselection mechanism

[0075] In NR, the network sends an intra-frequency reselection indication (IFRI) field (intraFreqReselection) in the main information block (MIB). This field indicates whether the UE can consider neighboring cells with the same frequency as the current cell (i.e., co-frequency neighboring cells) as candidate cells for cell reselection when the current cell is prohibited. If the field indicates "allowed," the UE can consider co-frequency neighboring cells when performing cell reselection; if the field indicates "not allowed," the UE cannot consider co-frequency neighboring cells as candidate cells for cell reselection for a certain period of time.

[0076] Because RedCap UEs are degraded terminals, they typically require more resources or special scheduling from the network compared to non-RedCap UEs when accessing the network. Therefore, the standard has agreed that networks need mechanisms to specifically control access for RedCap UEs.

[0077] Based on this, this application proposes a communication method that enables a terminal device (RedCap UE) to use different IFR indications when a cell is prohibited, thereby speeding up the efficiency of the terminal device in determining the cell reselection operation. It also proposes a behavior rule for cases where a specific RedCap IFR is not sent, so as to clarify how the terminal device (RedCap UE) determines the same-frequency reselection operation.

[0078] The method provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. It should be noted that the figures are for illustrative purposes only and should not be construed as limiting the scope of this application. The names of various network elements are defined only to distinguish different functions and should not be construed as limiting the scope of this application. This application does not preclude the possibility of defining other network elements to achieve the same or similar functions.

[0079] Figure 2 This is a schematic flowchart of a communication method provided in an embodiment of this application, which includes at least the following steps.

[0080] S210, the network device sends a Master Information Block (MIB) to the terminal device, and correspondingly, the terminal device receives the MIB sent by the network device. The MIB includes first indication information and second indication information. The first indication information indicates whether the cell is prohibited, and the second indication information indicates whether intra-frequency reselection is permitted.

[0081] S220, if the first indication information indicates that the cell is prohibited, the terminal device determines whether to perform a same-frequency reselection operation based on the second indication information.

[0082] Specifically, the terminal device can be a RedCap UE with reduced capabilities, the first indication information can be the cellBarred field in the MIB, and the second indication information can be the intraFreqReselection field in the MIB.

[0083] In one possible implementation, the cellBarred field in the MIB received by the terminal device indicates that the cell is blocked. For example, if the cellBarred field is set to "barred", the terminal device determines that it cannot camp on the current cell. In this case, the terminal device determines whether to perform a frequency reselection operation based on the second indication information (the intraFreqReselection field in the MIB).

[0084] Specifically, if the intraFreqReselection field in the MIB indicates that intra-frequency reselection is allowed, for example, if the intraFreqReselection field is set to "allowed", the terminal device can consider the intra-frequency neighboring cells of the current cell as candidate cells for cell reselection.

[0085] If the intraFreqReselection field in the MIB indicates that intra-frequency reselection is not allowed, for example, if the intraFreqReselection field is set to "not allowed", then the terminal device will not consider the intra-frequency neighboring cells of the current cell as candidate cells for cell reselection (within a certain period of time).

[0086] It should be understood that the cell / current cell is the cell that sent the above MIB / SIB1 information.

[0087] It should be understood that co-frequency neighboring cells of the current cell can be understood as those with the same frequency as the current cell. For example, they can be neighboring cells with the same frequency as the cell's synchronization signal / physical broadcast channel block (SSB).

[0088] Based on the above technical solution, the terminal device (RedCap UE) can use different IFR indications when the cell is blocked, so as to speed up the efficiency of the terminal device in determining the cell reselection operation.

[0089] Figure 3 This is a schematic flowchart of a communication method provided in an embodiment of this application, which includes at least the following steps.

[0090] S310, the network device sends the first information to the terminal device, and the terminal device receives the first information accordingly.

[0091] S320, if the first information does not include the third indication information, the terminal device determines that the same-frequency reselection operation is allowed, wherein the third indication information is used to indicate whether the same-frequency reselection operation is allowed.

[0092] Specifically, the terminal device can be a RedCap UE with reduced capabilities, the first information can be System Information Block 1 (SIB1), and the third indication information can be the RedCap-specific intraFreqReselection field in SIB1.

[0093] In one possible implementation, the terminal device receives first information SIB1. If the first information SIB1 does not include the RedCap-specific intraFreqReselection field, the terminal device determines that a co-frequency cell reselection operation is allowed. That is, the terminal device can consider that a co-frequency cell reselection operation is permitted. Then, the terminal device can consider co-frequency neighboring cells of the current cell as candidate cells for cell reselection.

[0094] In one possible implementation, the terminal device receives first information SIB1. If the first information SIB1 does not include the RedCap specific intraFreqReselection field, the terminal device obtains the intraFreqReselection field from the MIB and determines whether to perform a same-frequency reselection operation based on the intraFreqReselection field in the MIB.

[0095] Specifically, if the intraFreqReselection field in the MIB indicates that intra-frequency reselection is allowed, for example, if the intraFreqReselection field is set to "allowed", the terminal device can consider the intra-frequency neighboring cells of the current cell as candidate cells for cell reselection.

[0096] If the intraFreqReselection field in the MIB indicates that intra-frequency reselection is not allowed, for example, if the intraFreqReselection field is set to "not allowed", then the terminal device will not consider the intra-frequency neighboring cells of the current cell as candidate cells for cell reselection (within a certain period of time).

[0097] Optionally, before S320, the method may further include S311, whereby the first information received by the terminal device further includes fourth indication information, and the terminal device determines that the current cell of the terminal device is blocked according to the fourth indication information, wherein the fourth indication information is used to indicate that the current cell is blocked.

[0098] Specifically, the fourth indication information can be the RedCap-specific cellBarred field in SIB1. The terminal device indicates that the cell is blocked based on the RedCap-specific cellBarred field in SIB1. For example, if the RedCap-specific cellBarred field is set to "barred", it is determined that the current cell is blocked, that is, the terminal device determines that it cannot camp on the current cell.

[0099] It should be noted that S311 can be an optional step, that is, S311 can be a condition for executing S320. That is, the terminal device will only determine whether the RedCap-specific intraFreqReselection field is included in SIB1 if it determines that the current cell is blocked based on the RedCap-specific cellBarred field in SIB1.

[0100] Based on the above technical solution, a behavior rule can be designed for the case where a specific RedCap IFR is not transmitted, so as to clarify how the terminal device (RedCap UE) determines the same-frequency reselection operation.

[0101] Figure 4 This is a schematic flowchart of a communication method provided in an embodiment of this application, which includes at least the following steps.

[0102] S410, RedCap UE obtains MIB, which includes the cellBarred field. The cellBarred field is used to indicate whether the current cell of the RedCap UE is blocked.

[0103] S420, RedCap UE determines whether the cellBarred field contained in the MIB indicates that the current cell is blocked.

[0104] In one possible implementation, if the cellBarred field in the MIB indicates that the current cell is disabled, for example, if the cellBarred field is set to "barred", then the terminal device determines that it cannot camp on the current cell. In this case, step S430 is executed.

[0105] S430, RedCap UE determines whether to perform intra-frequency reselection operation based on the intraFreqReselection field in the MIB.

[0106] Specifically, if the intraFreqReselection field in the MIB indicates that intra-frequency reselection is allowed, for example, if the intraFreqReselection field is set to "allowed", then the RedCap UE can consider the intra-frequency neighboring cells of the current cell as candidate cells for cell reselection.

[0107] If the intraFreqReselection field in the MIB indicates that intra-frequency reselection is not allowed, for example, if the intraFreqReselection field is set to "not allowed", then the RedCap UE will not consider the current cell's intra-frequency neighboring cells as candidate cells for cell reselection (within a certain period of time).

[0108] In another possible implementation, if the cellBarred field in the MIB indicates that the cell is not barred, for example, if the cellBarred field is set to "not barred", then steps S440-S460 are executed.

[0109] S440, RedCap UE obtains SIB1, which contains a RedCap-specific cellBarred field. The RedCap-specific cellBarred field is used to indicate whether the current cell of the RedCap UE is blocked.

[0110] In S450, the RedCap UE determines that the RedCap-specific cellBarred field contained in SIB1 indicates that the current cell is disabled. In other words, the RedCap UE determines that it cannot camp on the current cell. At this time, S460 is executed.

[0111] It is understandable that the condition under which a RedCap UE determines whether it can perform a same-frequency reselection operation based on the RedCap-specific intraFreqReselection field in SIB1 is that the RedCap UE determines that the cell is prohibited based on the RedCap-specific cellBarred field in SIB1, that is, the RedCap UE determines that it cannot camp on the current cell.

[0112] For example:

[0113] If the RedCap-specific cellBarred field indicates that RedCap UEs of 1Rx branch and 2Rx branches are not allowed to camp in the current cell, then RedCap UEs of 1Rx branch and 2Rx branches will determine that they cannot camp in the current cell. Subsequently, the RedCap-specific intraFreqReselection field in SIB1 will be used to determine whether a same-frequency reselection operation can be performed.

[0114] Assuming the RedCap-specific cellBarred field indicates that RedCap UEs in the 1Rx branch are not allowed to camp in the current cell, then RedCap UEs in the 1Rx branch are certain they cannot camp in the current cell. Subsequently, the RedCap-specific intraFreqReselection field in SIB1 determines whether a same-frequency reselection operation can be performed. However, RedCap UEs in the 2Rxbranches can camp in the current cell.

[0115] Assuming the RedCap-specific cellBarred field indicates that RedCap UEs in the 2Rx branch are not allowed to camp in the current cell, then RedCap UEs in the 2Rx branch are certain they cannot camp in the current cell. Subsequently, the RedCap-specific intraFreqReselection field in SIB1 determines whether a same-frequency reselection operation can be performed. However, RedCap UEs in the 1Rxbranches can camp in the current cell.

[0116] S460, RedCap UE determines whether to perform intra-frequency reselection operation based on the RedCap-specific intraFreqReselection field in SIB1.

[0117] Specifically, if the RedCap-specific intraFreqReselection field in SIB1 indicates that intra-frequency cell reselection is allowed, then the RedCap UE may consider the current cell's intra-frequency neighboring cells as candidate cells for cell reselection. If the RedCap-specific intraFreqReselection field in SIB1 indicates that intra-frequency cell reselection is not allowed, then the RedCap UE will not consider the current cell's intra-frequency neighboring cells as candidate cells for cell reselection (within a certain period of time).

[0118] It should be noted that after executing S430, the Redcap UE no longer needs to obtain SIB1. This can be understood as follows: if S430 is executed, S440-S460 will not be executed.

[0119] Figure 5 This is a schematic flowchart of an access control method provided in an embodiment of this application. The method includes at least the following steps.

[0120] S510, RedCap UE obtains SIB1, which contains a RedCap-specific cellBarred field. The RedCap-specific cellBarred field is used to indicate whether the current cell of the RedCap UE is blocked.

[0121] S520, the RedCap UE determines that the RedCap-specific cellBarred field contained in SIB1 indicates that the current cell is disabled. For example, if the RedCap-specific cellBarred field is set to "barred", that is, the RedCap UE determines that it cannot camp on the current cell, then proceed to step S530.

[0122] It should be understood that step S520 is an optional step. That is, S520 can be understood as a condition for executing S520. Specifically, the terminal device will only determine whether the RedCap-specific intraFreqReselection field is included in SIB1 if it determines that the current cell is blocked based on the RedCap-specific cellBarred field in SIB1.

[0123] For example:

[0124] If the RedCap-specific cellBarred field indicates that RedCap UEs on 1Rx branch and 2Rx branches are not allowed to camp on the current cell, then RedCap UEs on 1Rx branch and 2Rx branches will determine that they cannot camp on the current cell. Subsequently, it will be determined whether the RedCap-specific intraFreqReselection field is included in SIB1.

[0125] If the RedCap-specific cellBarred field indicates that RedCap UEs in the 1Rx branch are not allowed to camp in the current cell, then the RedCap UE in the 1Rx branch is certain that it cannot camp in the current cell, and the subsequent determination will be whether the RedCap-specific intraFreqReselection field is included in SIB1. However, RedCap UEs in the 2Rx branches can camp in the current cell.

[0126] If the RedCap-specific cellBarred field indicates that RedCap UEs from 2Rx branches are not allowed to camp on the current cell, then RedCap UEs from 2Rx branches are certain they cannot camp on the current cell, and it is subsequently determined whether the RedCap-specific intraFreqReselection field is included in SIB1. However, RedCap UEs from 1Rx branches can camp on the current cell.

[0127] S530, RedCap UE determines whether SIB1 contains the RedCap-specific intraFreqReselection field.

[0128] In one possible implementation, if SIB1 contains a RedCap-specific intraFreqReselection field, then step S540 is executed.

[0129] S540, RedCap UE determines whether to perform intra-frequency reselection operation based on the RedCap-specific intraFreqReselection field.

[0130] Specifically, if the RedCap-specific intraFreqReselection field in SIB1 indicates that intra-frequency cell reselection is allowed, then the RedCap UE may consider intra-frequency neighboring cells of the current cell as candidate cells for cell reselection. If the RedCap-specific intraFreqReselection field in SIB1 indicates that intra-frequency cell reselection is not allowed, then the RedCap UE will not consider intra-frequency neighboring cells of the current cell as candidate cells for cell reselection (for a certain period of time).

[0131] In another possible implementation, if SIB1 does not contain a RedCap-specific intraFreqReselection field, then step S550 is executed.

[0132] Specifically, if the RedCap UE determines that SIB1 does not contain the RedCap-specific intraFreqReselection field, then the same-frequency reselection rule of the RedCap UE can be implemented in two possible ways.

[0133] One possible implementation: If the RedCap UE considers intra-frequency reselection to be allowed, then the RedCap UE can consider the intra-frequency neighboring cells of the current cell as candidate cells for cell reselection.

[0134] Another possible implementation: RedCap UE determines whether intra-frequency reselection is possible based on the intraFreqReselection field in the MIB.

[0135] Specifically, if the intraFreqReselection field in the MIB indicates that intra-frequency reselection is allowed, for example, if the intraFreqReselection field is set to "allowed", then the RedCap UE can consider the intra-frequency neighboring cells of the current cell as candidate cells for cell reselection.

[0136] If the intraFreqReselection field in the MIB indicates that intra-frequency reselection is not allowed, for example, if the intraFreqReselection field is set to "not allowed", then the RedCap UE will not consider the current cell's intra-frequency neighboring cells as candidate cells for cell reselection (within a certain period of time).

[0137] It should be noted that the methods described above can also be combined, such as... Figure 6 As shown, Figure 6 A schematic flowchart of a communication method provided in another embodiment of this application is shown, which specifically includes the following steps.

[0138] S610, RedCap UE obtains MIB, which includes the cellBarred field. The cellBarred field is used to indicate whether the current cell of the RedCap UE is blocked.

[0139] S620, RedCap UE determines whether the cellBarred field contained in the MIB indicates that the current cell is blocked.

[0140] In one possible implementation, if the cellBarred field in the MIB indicates that the current cell is disabled, for example, if the cellBarred field is set to "barred", then the terminal device determines that it cannot camp on the current cell. In this case, step S630 is executed.

[0141] In S630, the RedCap UE determines whether to perform a same-frequency reselection operation based on the intraFreqReselection field in the MIB. S630 is similar to S430, and for simplicity, it will not be described in detail here.

[0142] In another possible implementation, if the cellBarred field in the MIB indicates that the cell is not blocked, for example, if the cellBarred field is set to "not barred", then step S640 is executed.

[0143] S640, RedCap UE obtains SIB1, which contains a RedCap-specific cellBarred field. The RedCap-specific cellBarred field is used to indicate whether the current cell of the RedCap UE is blocked.

[0144] Optionally, the method may also include S650, whereby the RedCap UE determines that the RedCap-specific cellBarred field contained in SIB1 indicates that the current cell is disabled. For example, if the RedCap-specific cellBarred field is set to "barred", that is, the RedCap UE determines that it cannot camp on the current cell, then S660 is executed.

[0145] It should be understood that step S650 is an optional step. That is, S650 can be understood as a condition for executing S660. Specifically, the terminal device will only determine whether the RedCap-specific intraFreqReselection field is included in SIB1 if it determines that the current cell is blocked based on the RedCap-specific cellBarred field in SIB1.

[0146] For example:

[0147] If the RedCap-specific cellBarred field indicates that RedCap UEs on 1Rx branch and 2Rx branches are not allowed to camp on the current cell, then RedCap UEs on 1Rx branch and 2Rx branches will determine that they cannot camp on the current cell. Subsequently, it will be determined whether the RedCap-specific intraFreqReselection field is included in SIB1.

[0148] If the RedCap-specific cellBarred field indicates that RedCap UEs in the 1Rx branch are not allowed to camp in the current cell, then the RedCap UE in the 1Rx branch is certain that it cannot camp in the current cell, and the subsequent determination will be whether the RedCap-specific intraFreqReselection field is included in SIB1. However, RedCap UEs in the 2Rx branches can camp in the current cell.

[0149] If the RedCap-specific cellBarred field indicates that RedCap UEs from 2Rx branches are not allowed to camp on the current cell, then RedCap UEs from 2Rx branches are certain they cannot camp on the current cell, and it is subsequently determined whether the RedCap-specific intraFreqReselection field is included in SIB1. However, RedCap UEs from 1Rx branches can camp on the current cell.

[0150] S660, RedCap UE determines whether SIB1 contains the RedCap-specific intraFreqReselection field.

[0151] In one possible implementation, if SIB1 contains a RedCap-specific intraFreqReselection field, then step S670 is executed.

[0152] In S670, the RedCap UE determines whether to perform a same-frequency reselection operation based on the RedCap-specific intraFreqReselection field. S670 is similar to S540, and for simplicity, it will not be described in detail here.

[0153] In another possible implementation, if SIB1 does not contain a RedCap-specific intraFreqReselection field, then step S680 is executed.

[0154] Specifically, if the RedCap UE determines that SIB1 does not contain the RedCap-specific intraFreqReselection field, then the same-frequency reselection rule of the RedCap UE can be implemented in two possible ways.

[0155] One possible implementation: If the RedCap UE considers intra-frequency reselection to be allowed, then the RedCap UE can consider the intra-frequency neighboring cells of the current cell as candidate cells for cell reselection.

[0156] Another possible implementation: RedCap UE determines whether intra-frequency reselection is possible based on the intraFreqReselection field in the MIB.

[0157] Specifically, if the intraFreqReselection field in the MIB indicates that intra-frequency reselection is allowed, for example, if the intraFreqReselection field is set to "allowed", then the RedCap UE can consider the intra-frequency neighboring cells of the current cell as candidate cells for cell reselection.

[0158] If the intraFreqReselection field in the MIB indicates that intra-frequency reselection is not allowed, for example, if the intraFreqReselection field is set to "not allowed", then the RedCap UE will not consider the current cell's intra-frequency neighboring cells as candidate cells for cell reselection (within a certain period of time).

[0159] The above technical solutions enable the terminal device (RedCap UE) to use different IFR indications when the cell is prohibited, thereby speeding up the efficiency of the terminal device in determining the cell reselection operation. Furthermore, it is possible to design a behavior rule for the case where a specific RedCap IFR is not sent, so as to clarify how the terminal device (RedCap UE) determines the same-frequency reselection operation.

[0160] The various embodiments described herein can be independent solutions or combinations thereof based on their inherent logic, and all such solutions fall within the protection scope of this application.

[0161] It is understood that the methods and operations implemented by each device in the above method embodiments can also be implemented by components of the corresponding device (such as chips or circuits).

[0162] The foregoing mainly describes the solutions provided by the embodiments of this application from the perspective of various interactions. It is understood that each network element, such as a transmitting or receiving device, includes corresponding hardware structures and / or software modules to perform the aforementioned functions. Those skilled in the art should recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

[0164] It should be understood that the specific examples in the embodiments of this application are only for the purpose of helping those skilled in the art to better understand the embodiments of this application, and are not intended to limit the scope of the embodiments of this application.

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

[0166] The above, combined with Figures 2 to 6 The methods provided in the embodiments of this application are described in detail below. Figures 7 to 9 The apparatus provided in the embodiments of this application is described in detail. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, for content not described in detail, please refer to the method embodiments above. For the sake of brevity, it will not be repeated here.

[0167] refer to Figure 7 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device is used to implement the various steps of the corresponding terminal devices in the above embodiments, such as... Figure 7 As shown, the communication device 700 includes a receiving unit 710 and a processing unit 720.

[0168] In the first embodiment, the communication device is used to implement the various steps of the corresponding terminal devices in the above embodiments:

[0169] The receiving unit 710 is used to receive a master information block (MIB), which includes first indication information and second indication information. The first indication information is used to indicate whether the cell is prohibited, and the second indication information is used to indicate whether a co-frequency reselection operation is allowed. The processing unit 720, when the first indication information indicates that the cell is prohibited, is used to determine whether to perform a co-frequency reselection operation based on the second indication information. The terminal device is a RedCap UE with reduced capabilities.

[0170] In the second embodiment, the communication device is used to implement the various steps of the corresponding terminal devices in the above embodiments:

[0171] The receiving unit 710 is used to receive first information; the processing unit 720 is used to determine whether the same-frequency reselection operation is allowed if the first information does not include third indication information, wherein the third indication information is used to indicate whether the same-frequency reselection operation is allowed.

[0172] Optionally, in some embodiments, the first information further includes fourth indication information, and the processing unit 720 is further configured to: determine that the current cell of the terminal device is blocked according to the fourth indication information, wherein the fourth indication information is used to indicate whether the current cell of the terminal device is blocked.

[0173] Optionally, in some embodiments, the terminal device is a RedCap UE with reduced capabilities.

[0174] refer to Figure 8 This is a schematic diagram of a communication device provided in an embodiment of this application. This communication device is used to implement the various steps of the corresponding network devices in the above embodiments, such as... Figure 8 As shown, the communication device 800 includes a transmitting unit 810 and a processing unit 820.

[0175] In the first embodiment, the communication device is used to implement the various steps of the corresponding network devices in the above embodiments:

[0176] The sending unit 810 is used to send a main information block (MIB), which includes first indication information and second indication information. The first indication information is used to indicate whether the cell is prohibited, and the second indication information is used to indicate whether the same-frequency reselection operation is allowed. The processing unit 820, when the first indication information indicates that the cell is prohibited, uses the second indication information to indicate whether the terminal device should perform the same-frequency reselection operation, wherein the terminal device is a RedCap UE with reduced capabilities.

[0177] In the second embodiment, the communication device is used to implement the various steps of the corresponding network devices in the above embodiments:

[0178] The sending unit 810 is used to send first information; the processing unit 820, when the first information does not include third indication information, is used to instruct the terminal device to determine whether to allow the same-frequency reselection operation, wherein the third indication information is used to indicate whether the same-frequency reselection operation is allowed.

[0179] Optionally, in some embodiments, the first information further includes fourth indication information, and the processing unit 820 is further configured to: use the fourth indication information to indicate that the current cell of the terminal device is blocked.

[0180] Optionally, in some embodiments, the terminal device is a RedCap UE with reduced capabilities.

[0181] It should be understood that the division of units in the above communication device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the communication device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, while some modules can be implemented in hardware. For example, each unit can be a separately established processing element, or it can be integrated into a chip within the communication device. Alternatively, it can be stored as a program in memory, called and executed by a processing element of the communication device. Moreover, these units can be fully or partially integrated together, or implemented independently. The processing element mentioned here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0182] In one example, a unit in any of the above communication devices can be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. As another example, when a unit in the communication device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling programs. Furthermore, these units can be integrated together and implemented as a system-on-a-chip (SOC).

[0183] refer to Figure 9 This is a schematic diagram of a communication device provided in an embodiment of this application, used to implement the operation of the terminal device and network device in the above embodiments. Figure 9As shown, the communication device includes a processor 910 and an interface 930, with the processor 910 coupled to the interface 930. The interface 930 is used to enable communication with other devices. The interface 930 can be a transceiver or an input / output interface. The interface 930 can be, for example, an interface circuit. Optionally, the communication device also includes a memory 920 for storing instructions executed by the processor 910, or storing input data required by the processor 910 to execute instructions, or storing data generated after the processor 910 executes instructions.

[0184] The methods executed by the terminal device and network device in the above embodiments can be implemented by the processor 910 calling a program stored in memory (which can be memory 920 in the terminal device and network device, or external memory). That is, the terminal device and network device may include a processor 910, which executes the methods executed by the terminal device and network device in the above method embodiments by calling a program in memory. The processor here can be an integrated circuit with signal processing capabilities, such as a CPU. The terminal device and network device can be implemented by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or one or more microprocessors (DSPs), or one or more FPGAs, or a combination of at least two of these integrated circuit forms. Alternatively, the above implementation methods can be combined.

[0185] Specifically, Figure 7 and Figure 8 The function / implementation process of each unit can be obtained through Figure 9 The processor 910 in the communication device 900 shown calls computer-executable instructions stored in the memory 920 to implement the function. Alternatively, Figure 7 and Figure 8 The function / implementation process of the processing unit in the middle can be obtained through Figure 9 The processor 910 in the communication device 900 shown calls computer execution instructions stored in the memory 920 to implement the communication. Figure 7 and Figure 8 The function / implementation process of the receiving unit or transmitting unit in the middle can be obtained through Figure 9 This is achieved through interface 930 in the communication device 900 shown.

[0186] It should be understood that the processing unit in the above-described apparatus includes a processor coupled to a memory for storing computer programs or instructions and / or data, and the processor for executing the computer programs or instructions and / or data stored in the memory, so that the method in the above-described method embodiments is executed.

[0187] It should also be understood that the division of units in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, while others are implemented in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, and its function can be called and executed by a processing element within the device. Here, the processing element can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0188] This application also provides a computer-readable storage medium storing a computer program for implementing the methods in the above-described method embodiments. When the computer program is run on a computer, the computer can implement the methods in the above-described method embodiments.

[0189] This application also provides a system-on-a-chip (SoC) comprising a processing unit and a communication unit. The processing unit may be, for example, a processor, and the communication unit may be, for example, an input / output interface, pins, or circuitry. The processing unit can execute computer instructions to cause the chip within the communication device to perform any of the communication methods provided in the embodiments of this application.

[0190] The aforementioned processor may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The aforementioned processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads messages from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0191] It is understood that the storage element in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0192] It should be understood that the phrase "one embodiment" or "an embodiment" mentioned in the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence number of the above-described processes does not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0193] In addition, the terms “system” and “network” are often used interchangeably in this article.

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

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

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

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

[0198] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0199] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A communication method applied to a RedCap UE (Red Cap UE) or a chip within a RedCap UE, characterized in that, The method comprises: Receive the Master Information Block (MIB), where the cellBarred field in the MIB indicates whether the cell is blocked; If the cellBarred field in the MIB indicates that the cell is not blocked, and if System Information Block 1 (SIB1) does not include the RedCap-specific intraFreqReselection field, then intra-frequency reselection is permitted, wherein SIB1 is received after the MIB. The RedCap-specific intraFreqReselection field indicates whether RedCap UEs are allowed to perform same-frequency reselection.

2. The method according to claim 1, characterized in that, The RedCap UE is either a 1Rx branchRedCap UE or a 2Rx branchesRedCap UE.

3. The method according to claim 2, characterized in that, The method further comprises: If the cellBarred field in the MIB indicates that the cell is not blocked, and if the SIB1 includes a RedCap-specific intraFreqReselection field, then determine whether intra-frequency reselection is allowed based on the RedCap-specific intraFreqReselection field. The RedCap UE is a 1Rx branch RedCap UE, and the RedCap-specific cellBarred field in SIB1 indicates that a 1Rx branch RedCap UE is not allowed to camp in the cell.

4. The method according to claim 2, characterized in that, The method further comprises: If the cellBarred field in the MIB indicates that the cell is not blocked, and if the SIB1 includes a RedCap-specific intraFreqReselection field, then determine whether intra-frequency reselection is allowed based on the RedCap-specific intraFreqReselection field. The RedCap UE is a 2Rx branches RedCap UE, and the RedCap-specific cellBarred field in SIB1 indicates that 2Rx branches RedCap UEs are not allowed to camp in the cell.

5. The method according to claim 1, characterized in that, The method further includes: if the cellBarred field in the MIB indicates that the cell is blocked, determining that the cell is blocked.

6. The method according to any one of claims 1-5, characterized in that, The RedCap UE or the chip is in the Radio Resource Control (RRC) idle state or the RRC inactive state.

7. A communication method applied to a network device or a chip in a network device, characterized in that, The method comprises: Send a main information block (MIB), in which the cellBarred field indicates whether the cell is blocked; Send system information block 1 (SIB1); If the cellBarred field in the MIB indicates that the cell is not blocked, and if the SIB1 does not include the RedCap-specific intraFreqReselection field, then a RedCap UE with reduced capabilities is allowed to perform intra-frequency reselection, wherein the SIB1 is sent after the MIB; The RedCap-specific intraFreqReselection field indicates whether RedCap UEs are allowed to perform same-frequency reselection.

8. The method according to claim 7, characterized in that, The RedCap UE is either a 1Rx branchRedCap UE or a 2Rx branchesRedCap UE.

9. The method according to claim 8, characterized in that, The method further comprises: If the cellBarred field in the MIB indicates that the cell is not prohibited, the SIB1 includes a RedCap-specific intraFreqReselection field, and if the RedCap-specific intraFreqReselection field indicates that the RedCap UE is allowed to perform intra-frequency reselection, then the RedCap UE is allowed to perform intra-frequency reselection. The RedCap UE is a 1Rx branch RedCap UE, and the RedCap-specific cellBarred field in SIB1 indicates that a 1Rx branch RedCap UE is not allowed to camp in the cell.

10. The method according to claim 8, characterized in that, The method further comprises: If the cellBarred field in the MIB indicates that the cell is not prohibited, the SIB1 includes a RedCap-specific intraFreqReselection field, and if the RedCap-specific intraFreqReselection field indicates that the RedCap UE is allowed to perform intra-frequency reselection, then the RedCap UE is allowed to perform intra-frequency reselection. The RedCap UE is a 2Rx branches RedCap UE, and the RedCap-specific cellBarred field in SIB1 indicates that 2Rx branches RedCap UEs are not allowed to camp in the cell.

11. The method according to claim 8, characterized in that, The method further comprises: If the cellBarred field in the MIB indicates that the cell is not prohibited, the SIB1 includes a RedCap-specific intraFreqReselection field, and if the RedCap-specific intraFreqReselection field indicates that the RedCap UE is not allowed to perform intra-frequency reselection, then the RedCap UE is not allowed to perform intra-frequency reselection. The RedCap UE is a 1Rx branch RedCap UE, and the RedCap-specific cellBarred field in SIB1 indicates that a 1Rx branch RedCap UE is not allowed to camp in the cell.

12. The method according to claim 8, characterized in that, The method further comprises: If the cellBarred field in the MIB indicates that the cell is not prohibited, the SIB1 includes a RedCap-specific intraFreqReselection field, and if the RedCap-specific intraFreqReselection field indicates that the RedCap UE is not allowed to perform intra-frequency reselection, then the RedCap UE is not allowed to perform intra-frequency reselection. The RedCap UE is a 2Rx branches RedCap UE, and the RedCap-specific cellBarred field in SIB1 indicates that 2Rx branches RedCap UEs are not allowed to camp in the cell.

13. The method according to any one of claims 7-12, characterized in that, The RedCap UE is in the Radio Resource Control (RRC) idle state or the RRC inactive state.

14. A communication device comprising a processor and an interface coupled to the processor, the interface being configured to communicate with other devices, wherein when a computer program or instructions are executed by the processor, the method described in any one of claims 1-6 is executed or implemented.

15. The communication device according to claim 14, characterized in that, The communication device further includes a memory coupled to the processor, the memory storing the computer program or instructions.

16. A communication device comprising a processor and an interface coupled to the processor, the interface being configured to communicate with other devices, wherein when a computer program or instructions are executed by the processor, the method described in any one of claims 7-13 is performed or implemented.

17. The communication device according to claim 16, characterized in that, The communication device further includes a memory coupled to the processor, the memory storing the computer program or instructions.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed, cause the method described in any one of claims 1-6 to be performed or implemented.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed, cause the method described in any one of claims 7-13 to be performed or implemented.

20. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed, cause the method described in any one of claims 1-6 to be performed or implemented.

21. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed, cause the method described in any one of claims 7-13 to be performed or implemented.

Images