Communication method and related device

Abstract

A communication method and a related device, in the method, a first terminal device receives system information, the system information indicates whether a cell under a network device is an access prohibited cell of a terminal device with reduced capability, the system information further comprises first information, and the first information is a first information indicating whether the cell under the network device is an access prohibited cell of the terminal device with reduced capability. The first information indicates whether a cell under the network equipment supports the terminal equipment with reduced capability to execute the emergency service in an access forbidding state or not. And the first terminal equipment determines whether to access a cell under the network equipment to execute the emergency service according to the system information. According to the invention, for the access control of the RedCapp / eRedCap UE, a scheme capable of allowing the RedCapp / eRedCap UE to execute the emergency service in the access forbidding state is provided, and the communication flexibility is improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication method and related devices. Background Art

[0002] In the new radio (NR) system, network equipment (such as a base station) broadcasts a synchronization signal / physical broadcast channel block (synchronization signal and PBCH block, SSB). If the terminal device expects 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 includes a cell status indication. Generally speaking, the terminal device needs to determine whether a certain cell can be used as a candidate cell in the subsequent cell selection / reselection process based on the cell status indication in the system information. Generally speaking, when the system information indicates that a certain cell is a barred cell, the terminal device cannot select or reselect to the cell, even for an emergency call. The terminal device cannot select or reselect to the cell.

[0003] Currently, in the NR system, reduced capability (Redcap) user equipment (UE) was introduced in release 17 (R17), and enhanced reduced capability (eRedcap) UE was further introduced in R18. Compared with traditional NR terminals, RedCap / eRedCap UE has longer battery life, lower complexity and lower cost, so RedCap / eRedCap UE has been widely used. However, for the access control of RedCap / eRedCap UE, the network may consider the network transmission efficiency. For example, when the network transmission efficiency is low, the network may prohibit RedCap / eRedCap UE from accessing the cell. As a result, RedCap / eRedCap UE cannot initiate emergency calls, or cannot send and receive relevant information in special business scenarios such as earthquakes, fires, or alarms, which limits the application scenarios of RedCap / eRedCap UE and has low flexibility. Summary of the invention

[0004] The present application provides a communication method and related devices, which are conducive to improving communication flexibility.

[0005] In a first aspect, the present application provides a communication method, and optionally, the execution subject of the method may be a terminal device, or a component or device (such as a processor, a chip, or a chip system, etc.) applied to the terminal device, or a logic module or software that can realize all or part of the functions of the terminal device. The method includes: receiving system information, wherein the system information indicates whether a cell under a network device is a prohibited access cell for a terminal device with reduced capabilities, and the system information also includes first information, wherein the first information indicates whether the cell under the network device supports a terminal device with reduced capabilities to perform emergency services in a prohibited access state. Determine whether it is possible to access the cell under the network device to perform emergency services based on the system information.

[0006] In this application, for the access control of RedCap / eRedCap UE, a solution is proposed that allows RedCap / eRedCap UE to perform emergency services in a prohibited access state, thereby improving communication flexibility. Specifically, this application can enable RedCap / eRedCap UE to support emergency services even when the cell is prohibited by carrying the first information in the system information. For example, the emergency service can be an emergency call, or a notification of an earthquake, fire, etc.

[0007] In one possible design, the first terminal device is a reduced capability terminal device or an enhanced reduced capability terminal device, and the first terminal device is in an unconnected state or is a terminal device performing a radio resource control RRC reestablishment process in a connected state;

[0008] The determining, according to the system information, whether it is possible to access a cell under the network device to perform an emergency service includes:

[0009] When the system information indicates that the cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, and the first information indicates that the cell under the network device supports terminal devices with reduced capabilities to perform emergency services in a prohibited access state, it is determined that the cell under the network device can be accessed to perform emergency services.

[0010] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0011] The system information does not include same-frequency reselection indication information corresponding to the terminal device with reduced capability.

[0012] Under this implementation method, for a RedCap / eRedCap UE in a non-connected state (such as an idle state or an inactive state), or a RedCap / eRedCap UE performing an RRC reconstruction process in a connected state, when the system information does not include the same-frequency reselection indication information corresponding to the terminal device with reduced capabilities, it can be determined that the cell under the network device is a prohibited access cell for the terminal device with reduced capabilities.

[0013] In a possible design, the first terminal device includes one antenna channel; and the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0014] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the first indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 1 antenna channel.

[0015] In this implementation mode, for a RedCap / eRedCap UE in a non-connected state (for example, an idle state or an inactive state), or a RedCap / eRedCap UE performing an RRC reconstruction process in a connected state, when the system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the first indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 1 antenna channel, if the RedCap / eRedCap UE happens to be a RedCap / eRedCap UE with 1 antenna channel (1Rx branch), then the RedCap / eRedCap UE can determine that the cell under the network device is a prohibited access cell.

[0016] In a possible design, the first terminal device includes two antenna channels; and the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0017] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the second indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 2 antenna channels.

[0018] In this implementation mode, for a RedCap / eRedCap UE in a non-connected state (for example, an idle state or an inactive state), or a RedCap / eRedCap UE performing an RRC reconstruction process in a connected state, when the system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the second indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 2 antenna channels, if the RedCap / eRedCap UE happens to be a RedCap / eRedCap UE with 2 antenna channels (2Rx branch), then the RedCap / eRedCap UE can determine that the cell under the network device is a prohibited access cell.

[0019] In a possible design, the first terminal device supports a half-duplex mode under frequency division duplex FDD; and the system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including:

[0020] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and does not include the third indication information, where the third indication information is the indication information for allowing the terminal device with reduced capability in half-duplex to access the cell.

[0021] In this implementation, when the third indication information is not included in the system information, it indicates that the cell under the network device does not support the terminal device with reduced capability of half-duplex. However, if the RedCap / eRedCap UE only supports the half-duplex mode under frequency division duplex (FDD), the network device cannot serve the RedCap / eRedCap UE. Therefore, the RedCap / eRedCap UE may consider the cell under the network device as a cell that it is prohibited to access.

[0022] In one possible design, the system information indicates that the cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, and the first information indicates that the cell under the network device supports the terminal devices with reduced capabilities to perform emergency services in a prohibited access state;

[0023] The determining, according to the system information, whether it is possible to access a cell under the network device to perform an emergency service includes:

[0024] In the case where it is determined according to the system information that the cell under the network device is an acceptable cell, determining that the cell under the network device can be accessed to perform emergency services;

[0025] The acceptable cells meet the following conditions:

[0026] Supports terminal devices with reduced capabilities to perform emergency services in a prohibited access state.

[0027] In this implementation, a new requirement is added when defining acceptable cells: for RedCap / eRedCap UE, in emergency service scenarios (or during the duration of emergency services), ignore the indication of prohibited cells (or describe as acceptable cells supporting terminal devices with reduced capabilities to perform emergency services in a prohibited access state). Generally speaking, terminal devices with reduced capabilities can access cells under network devices to perform emergency services during the duration of emergency services.

[0028] In one possible design, the acceptable cell also satisfies a cell selection criterion.

[0029] In a possible design, the first terminal device is an enhanced reduced-capability terminal device; and the system information indicates that a cell under the network device is a prohibited access cell for the reduced-capability terminal device, including:

[0030] The frequency band information of the cell under the network device is not greater than 5 MHz, and the system information indicates a terminal device that does not support enhanced reduction capabilities.

[0031] In this implementation, when the frequency band (band) of the cell of the network device or the cell carrier bandwidth is less than or equal to 5MHz, and the system information indicates that the cell of the network device supports RedCap UE but not eRedCap UE, the cell of the network device is a cell prohibited from access by eRedCap UE.

[0032] In a possible design, the first terminal device is a first type of enhanced reduced capability terminal device, and the first type of enhanced reduced capability terminal device is an enhanced reduced capability terminal device with a peak rate equal to 10 Mbps and supporting a 20 MHz bandwidth; the system information indicates that the cell under the network device is a prohibited access cell for the reduced capability terminal device, including:

[0033] The system information indicates that the terminal device supports reduced capabilities and does not support enhanced reduced capabilities.

[0034] In this implementation, when the system information indicates that the cell of the network device supports RedCap UE but does not support eRedCap UE, for the first type of enhanced reduced-capability terminal device (assuming it is marked as eRedCap UE1), the cell of the network device is a cell that the eRedCap UE is prohibited from accessing. The first type of enhanced reduced-capability terminal device is an enhanced reduced-capability terminal device with a peak rate equal to 10Mbps and supporting a 20MHz bandwidth.

[0035] In a possible design, the first terminal device is a terminal device with reduced capabilities; and the system information indicates that a cell under the network device is a prohibited access cell for the terminal device with reduced capabilities, including:

[0036] The frequency band information of the cell under the network device is not greater than 20 MHz, and the system information indicates that the terminal device with reduced capability is not supported.

[0037] In this implementation, when the cell of the network device is located in a band or the cell carrier bandwidth is less than or equal to 20 MHz, and the system information indicates that the cell of the network device does not support RedCap UE, the cell of the network device is a cell prohibited from access by RedCap UE.

[0038] In one possible design, the method further includes:

[0039] In the case of determining that the cell under the network device can be accessed to perform the emergency service, sending second information indicating the type of enhanced reduced capability terminal device to which the first terminal device belongs;

[0040] Among them, the types of enhanced reduction capability terminal devices include first type of enhanced reduction capability terminal devices and second type of enhanced reduction capability terminal devices. The first type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting 20MHz bandwidth. The second type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting less than 20MHz bandwidth.

[0041] In this implementation mode, the first terminal device can also report to the network device the type of enhanced reduced-capability terminal device to which it belongs. This is beneficial for the network device to allocate resources adapted to the capabilities of the first terminal device based on the type of eRedCap UE to which the first terminal device belongs, thereby avoiding the configured resources exceeding the capabilities supported by the first terminal device.

[0042] In one possible design, the second information includes a type of enhanced reduced-capability terminal device to which the first terminal device belongs; or,

[0043] The second information includes capability information of the first terminal device, where the capability information is used to indicate the type of enhanced reduced-capability terminal device to which the first terminal device belongs.

[0044] In this implementation, the second information may indicate the type of eRedCap UE to which the first terminal device belongs in a direct or indirect manner. The direct manner is that the second information directly includes the type of enhanced reduced-capability terminal device to which the first terminal device belongs. The indirect manner is that the second information includes the capability information of the first terminal device, and the capability information is used to indicate the type of enhanced reduced-capability terminal device to which the first terminal device belongs.

[0045] In a possible design, determining, according to the system information, whether a cell under the network device can be accessed to perform an emergency service includes:

[0046] Determine whether it is possible to access the cell under the network device to perform the emergency service within the duration of the emergency service according to the system information.

[0047] In a second aspect, the present application provides a communication method, and optionally, the execution subject of the method may be a network device, or a component or device (such as a processor, a chip, or a chip system, etc.) applied to the network device, or a logic module or software that can implement all or part of the network device functions. The method includes: determining system information, wherein the system information indicates whether a cell under the network device is a prohibited access cell for a terminal device with reduced capabilities, and the system information also includes first information, wherein the first information indicates whether the cell under the network device supports a terminal device with reduced capabilities to perform emergency services in a prohibited access state. Send the system information.

[0048] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0049] The system information does not include same-frequency reselection indication information corresponding to the terminal device with reduced capability.

[0050] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0051] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the first indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 1 antenna channel.

[0052] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0053] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the second indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 2 antenna channels.

[0054] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0055] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and does not include the third indication information, where the third indication information is the indication information for allowing the terminal device with reduced capability in half-duplex to access the cell.

[0056] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0057] The frequency band information of the cell under the network device is not greater than 5 MHz, and the system information indicates a terminal device that does not support enhanced reduction capabilities.

[0058] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0059] The system information indicates that the terminal device supports reduced capabilities and does not support enhanced reduced capabilities.

[0060] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0061] The frequency band information of the cell under the network device is not greater than 20 MHz, and the system information indicates that the terminal device with reduced capability is not supported.

[0062] In one possible design, the method further includes:

[0063] receiving second information indicating a type of enhanced reduced-capability terminal device to which the first terminal device belongs;

[0064] Among them, the types of enhanced reduction capability terminal devices include first type of enhanced reduction capability terminal devices and second type of enhanced reduction capability terminal devices. The first type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting 20MHz bandwidth. The second type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting less than 20MHz bandwidth.

[0065] In one possible design, the second information includes a type of enhanced reduced-capability terminal device to which the first terminal device belongs; or,

[0066] The second information includes capability information of the first terminal device, where the capability information is used to indicate the type of enhanced reduced-capability terminal device to which the first terminal device belongs.

[0067] In a third aspect, the present application provides a communication device, which may be a terminal device or a module or chip in a terminal device. The communication device includes:

[0068] a transceiver unit, configured to receive system information, wherein the system information indicates whether a cell under the network device is a prohibited access cell for a terminal device with reduced capabilities, wherein the system information further includes first information indicating whether the cell under the network device supports the terminal device with reduced capabilities to perform emergency services in a prohibited access state;

[0069] The processing unit is used to determine whether it is possible to access the cell under the network device to perform emergency services according to the system information.

[0070] In one possible design, the first terminal device is a reduced capability terminal device or an enhanced reduced capability terminal device, and the first terminal device is in an unconnected state or is a terminal device performing a radio resource control RRC reestablishment process in a connected state;

[0071] In the case of determining whether it is possible to access a cell under the network device to perform an emergency service according to the system information, the processing unit is used to:

[0072] When the system information indicates that the cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, and the first information indicates that the cell under the network device supports terminal devices with reduced capabilities to perform emergency services in a prohibited access state, it is determined that the cell under the network device can be accessed to perform emergency services.

[0073] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0074] The system information does not include same-frequency reselection indication information corresponding to the terminal device with reduced capability.

[0075] In a possible design, the first terminal device includes one antenna channel; and the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0076] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the first indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 1 antenna channel.

[0077] In a possible design, the first terminal device includes two antenna channels; and the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0078] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the second indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 2 antenna channels.

[0079] In a possible design, the first terminal device supports a half-duplex mode under frequency division duplex FDD; and the system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including:

[0080] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and does not include the third indication information, where the third indication information is the indication information for allowing the terminal device with reduced capability in half-duplex to access the cell.

[0081] In one possible design, the system information indicates that the cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, and the first information indicates that the cell under the network device supports the terminal devices with reduced capabilities to perform emergency services in a prohibited access state;

[0082] In the case of determining whether it is possible to access a cell under the network device to perform an emergency service according to the system information, the processing unit is used to:

[0083] In the case where it is determined according to the system information that the cell under the network device is an acceptable cell, determining that the cell under the network device can be accessed to perform emergency services;

[0084] The acceptable cells meet the following conditions:

[0085] Supports terminal devices with reduced capabilities to perform emergency services in a prohibited access state.

[0086] In one possible design, the acceptable cell also satisfies a cell selection criterion.

[0087] In a possible design, the first terminal device is an enhanced reduced-capability terminal device; and the system information indicates that a cell under the network device is a prohibited access cell for the reduced-capability terminal device, including:

[0088] The frequency band information of the cell under the network device is not greater than 5 MHz, and the system information indicates a terminal device that does not support enhanced reduction capabilities.

[0089] In a possible design, the first terminal device is a first type of enhanced reduced capability terminal device, and the first type of enhanced reduced capability terminal device is an enhanced reduced capability terminal device with a peak rate equal to 10 Mbps and supporting a 20 MHz bandwidth; the system information indicates that the cell under the network device is a prohibited access cell for the reduced capability terminal device, including:

[0090] The system information indicates that the terminal device supports reduced capabilities and does not support enhanced reduced capabilities.

[0091] In a possible design, the first terminal device is a terminal device with reduced capabilities; and the system information indicates that a cell under the network device is a prohibited access cell for the terminal device with reduced capabilities, including:

[0092] The frequency band information of the cell under the network device is not greater than 20 MHz, and the system information indicates that the terminal device with reduced capability is not supported.

[0093] In one possible design, the transceiver unit is further used for:

[0094] In the case of determining that the cell under the network device can be accessed to perform the emergency service, sending second information indicating the type of enhanced reduced capability terminal device to which the first terminal device belongs;

[0095] Among them, the types of enhanced reduction capability terminal devices include first type of enhanced reduction capability terminal devices and second type of enhanced reduction capability terminal devices. The first type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting 20MHz bandwidth. The second type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting less than 20MHz bandwidth.

[0096] In one possible design, the second information includes a type of enhanced reduced-capability terminal device to which the first terminal device belongs; or,

[0097] The second information includes capability information of the first terminal device, where the capability information is used to indicate the type of enhanced reduced-capability terminal device to which the first terminal device belongs.

[0098] In a possible design, in the case of determining, according to the system information, whether a cell under the network device can be accessed to perform an emergency service, the processing unit is configured to:

[0099] Determine whether it is possible to access the cell under the network device to perform the emergency service within the duration of the emergency service according to the system information.

[0100] In a fourth aspect, the present application provides a communication device, which may be a terminal device or a module or chip in a terminal device. The communication device includes:

[0101] a processing unit, configured to determine system information, the system information indicating whether a cell under the network device is a prohibited access cell for a terminal device with reduced capabilities, the system information further comprising first information indicating whether the cell under the network device supports the terminal device with reduced capabilities to perform emergency services in a prohibited access state;

[0102] The transceiver unit is used to send the system information.

[0103] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0104] The system information does not include same-frequency reselection indication information corresponding to the terminal device with reduced capability.

[0105] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0106] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the first indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 1 antenna channel.

[0107] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0108] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the second indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 2 antenna channels.

[0109] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0110] The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and does not include the third indication information, where the third indication information is the indication information for allowing the terminal device with reduced capability in half-duplex to access the cell.

[0111] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0112] The frequency band information of the cell under the network device is not greater than 5 MHz, and the system information indicates a terminal device that does not support enhanced reduction capabilities.

[0113] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0114] The system information indicates that the terminal device supports reduced capabilities and does not support enhanced reduced capabilities.

[0115] In a possible design, the system information indicates that a cell under the network device is a prohibited access cell for a terminal device with reduced capability, including:

[0116] The frequency band information of the cell under the network device is not greater than 20 MHz, and the system information indicates that the terminal device with reduced capability is not supported.

[0117] In one possible design, the transceiver unit is further used for:

[0118] receiving second information indicating a type of enhanced reduced-capability terminal device to which the first terminal device belongs;

[0119] Among them, the types of enhanced reduction capability terminal devices include first type of enhanced reduction capability terminal devices and second type of enhanced reduction capability terminal devices. The first type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting 20MHz bandwidth. The second type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting less than 20MHz bandwidth.

[0120] In one possible design, the second information includes a type of enhanced reduced-capability terminal device to which the first terminal device belongs; or,

[0121] The second information includes capability information of the first terminal device, where the capability information is used to indicate the type of enhanced reduced-capability terminal device to which the first terminal device belongs.

[0122] In a fifth aspect, the present application provides a communication device, which includes a processor, and the processor is used to execute a computer program so that the communication device executes any method as described in any one of the first aspect to the fourth aspect.

[0123] In one possible design, the communication device may be a chip that implements the method of any one of the first to fourth aspects or a device including a chip.

[0124] In one possible design, the communication device further includes a transceiver, and the processor is coupled to the transceiver.

[0125] In a possible design, the communication device further includes a memory. The processor is coupled to the memory, a computer program is stored in the memory, and the processor is further used to call the computer program in the memory. Exemplarily, the processor and the memory may also be integrated together.

[0126] In a sixth aspect, the present application provides a communication device, which includes a processor, and the processor is used to implement any method as described in any one of the first to fourth aspects through a logic circuit or execution code instructions.

[0127] Optionally, the communication device further includes an interface circuit, which is used to receive signals from other communication devices outside the communication device and transmit them to the processor or to send signals from the processor to other communication devices outside the communication device.

[0128] In a seventh aspect, the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a computer, the method as described in any one of the first to fourth aspects is implemented.

[0129] In an eighth aspect, the present application provides a computer program product. When a computer reads and executes the computer program product, the computer executes any one of the methods described in any one of the first to fourth aspects.

[0130] In a ninth aspect, the present application provides a communication system, comprising a communication device for implementing the method described in any one of the first aspect or the second aspect, and a communication device for implementing the method described in any one of the third aspect or the fourth aspect.

[0131] The beneficial effects of the second to ninth aspects can refer to the beneficial effects of the first aspect and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0132] Figure 1 It is a schematic diagram of the architecture of a communication system applied in an embodiment of the present application;

[0133] Figure 2 It is a flow chart of the communication method provided in the embodiment of the present application;

[0134] Figure 3 is a schematic diagram of the structure of a possible communication device provided in an embodiment of the present application;

[0135] Figure 4 It is a schematic diagram of the structure of a possible communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0136] The specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0137] The terms "first" and "second" and the like in the specification, claims and drawings of this application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.

[0138] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0139] In the present application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0140] In this application, "sending information to... (such as a terminal)" can be understood as the destination of the information being the terminal. It can include sending information to the terminal directly or indirectly. "Receiving information from... (such as a terminal)" or "receiving information from... (such as a terminal)" can be understood as the source of the information being the terminal, which can include receiving information from the terminal directly or indirectly. The information may be processed as necessary between the source and destination of the information, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be repeated here.

[0141] In order to better understand the embodiments of the present application, the system architecture involved in the embodiments of the present application is first introduced below:

[0142] The technical solution of the present application can be applied to non-terrestrial networks (NTN) or scenarios where NTN and terrestrial networks (TN) are integrated. NTN systems can be, for example, satellite communication systems, high altitude platform station (HAPS) communication systems, global navigation satellite systems (GNSS), etc. TN systems can be, for example, fourth-generation (4G) communication systems (e.g., long-term evolution (LTE) systems), worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) communication systems (e.g., new radio (NR) systems), sixth-generation mobile communication (6G) systems, and future mobile communication systems.

[0143] The communication system provided in the present application may include one or more network devices and one or more terminals.

[0144] Below Figure 1 The system architecture shown is explained as an example. Figure 1 , Figure 1 Schematic diagram of the architecture of the communication system used in the embodiment of the present application. Figure 1 As shown, the communication system 1000 includes a radio access network (RAN) 100 and a core network (CN) 200. Optionally, the communication system 1000 may also include the Internet 300. The RAN 100 includes at least one network device (such as Figure 1 110a and 110b, collectively referred to as 110) and at least one terminal (such as Figure 1 RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment ( Figure 1The terminal 120 is connected to the network device 110 in a wireless manner. The network device 110 is connected to the core network 200 in a wireless or wired manner. The core network device in the core network 200 and the network device 110 in the RAN 100 may be different physical devices, or may be the same physical device that integrates the core network logical function and the radio access network logical function.

[0145] It should be noted that RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as a 4G or 5G mobile communication system, or an evolution system after 5G (such as a 6G mobile communication system). RAN 100 can also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (cloud radio access network, CRAN), etc. RAN 100 can also be a communication system that integrates two or more of the above systems. It should be noted that Figure 1 The number of network devices and terminals is only for illustration and should not be regarded as a specific limitation of the present application. The terminals and network devices involved in the system architecture are described in detail below.

[0146] 1. Terminal

[0147] Terminal can also be called terminal equipment, user equipment (UE), mobile station (MS), mobile terminal equipment (MT), mobile terminal, mobile equipment (ME), access terminal, user unit, user station, mobile station, remote station, remote terminal, user terminal, wireless communication equipment, user agent or user device, etc., or equipment used to provide voice or data connectivity to users, or IoT devices. For example, terminal equipment includes handheld devices with wireless connection function, vehicle-mounted devices, etc. At present, terminal devices can be: mobile phones, tablet computers, laptops, PDAs, mobile internet devices (MID), wearable devices (such as smart watches, smart bracelets, pedometers, etc.), vehicle-mounted equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed railways, etc.), satellite terminal equipment, virtual reality (VR) equipment, augmented reality (AR) equipment, smart point of sale (POS) machines, customer-premises equipment (CPE), wireless terminal devices in industrial control, smart home equipment (such as refrigerators, televisions, air conditioners, electric meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminal devices in unmanned driving, wireless terminal devices in telemedicine, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, or wireless terminal devices in smart homes, flying equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. The terminal device may also be other devices with terminal device functions. For example, the terminal device may also be a device that functions as a terminal device in D2D communication. The embodiments of the present application do not limit the device form of the terminal device. The device used to implement the function of the terminal device may be a terminal device; or it may be a device that can support the terminal device to implement the function, such as a chip system. The device may be installed in the terminal device or used in combination with the terminal device. In the embodiments of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices.

[0148] 2. Network equipment

[0149] A network device is a node in a radio access network (RAN), and can also be referred to as an access network device, or a RAN node (or device). A network device is used to help a terminal device achieve wireless access. The multiple network devices 110 in the communication system 1000 can be nodes of the same type or different types. In some scenarios, the roles of the network device 110 and the terminal device 120 are relative, for example, Figure 1 The network element 120i may be a helicopter or a drone, which may be configured as a mobile base station. For the terminal devices 120j that access the RAN 100 through the network element 120i, the network element 120i is a base station; but for the base station 110a, the network element 120i is a terminal device. The network device 110 and the terminal device 120 are sometimes referred to as communication devices, for example Figure 1 The network elements 110a and 110b may be understood as communication devices having base station functions, and the network elements 120a-120j may be understood as communication devices having terminal equipment functions.

[0150] In one possible scenario, the network device may be a device with base station functions, such as an evolved NodeB (eNodeB), a transmitting and receiving point (TRP), a transmitting point (TP), a next generation NodeB (gNB), a next generation base station in a 6G mobile communication system, an integrated access and backhaul (IAB) node, a non-ground network device in an NTN, i.e., a device that can be deployed on a high altitude platform or a satellite, etc. The network device may be a macro base station (e.g. Figure 1 110a in), micro base stations or indoor stations (such as Figure 1 The network device may be a base station in device-to-device (D2D) communication, Internet of Vehicles communication, drone communication, or machine communication. Optionally, the network device may also be a server, a wearable device, a vehicle or an onboard device. For example, the network device in vehicle to everything (V2X) technology may be a road side unit (RSU).

[0151] All or part of the functions of the network device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The network device in this application can also be a logical node, logical module or software that can implement all or part of the network device functions.

[0152] In another possible scenario, multiple network devices collaborate to assist the terminal device in achieving wireless access, and different network devices respectively implement part of the functions of the base station. For example, the network device may include a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU may be set separately, or may be included in the same network element, such as a baseband unit (BBU). The RU may be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). It is understandable that the network device may be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU may be divided into a network device in the access network RAN, or the CU may be divided into a network device in the core network CN, without limitation here.

[0153] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, CU, CU-CP, CU-UP, DU and RU are described as examples in this application. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0154] In the embodiments of the present application, the form of the network device is not limited. The device for realizing the function of the network device can be the network device; or it can be a device that can support the network device to realize the function, such as a chip system. The device can be installed in the network device or used in combination with the network device.

[0155] The following is an explanation of the relevant technical features involved in the embodiments of the present application. It should be noted that these explanations are intended to make the embodiments of the present application easier to understand and should not be regarded as limiting the scope of protection claimed by the present application.

[0156] 1. Reduced capability (Redcap) terminal devices

[0157] Redcap terminal equipment is also called Redcap terminal or RedcapUE. With the rapid development of wireless communications, 5G communication systems have emerged to meet and enrich people's growing needs. As an integral part of 5G, the market demand for the Internet of Things is growing rapidly. Therefore, in response to this demand, 5G introduced a simple terminal device in R17, namely RedcapUE. Compared with traditional NR terminals, this terminal supports narrower bandwidth, lower capabilities and lower costs. Specifically, RedcapUE reduces the complexity of the terminal by cutting the performance of the traditional NR terminal. At the same time, by enhancing some power-saving functions, it reduces the power consumption of the terminal, allowing specific IoT terminals to have higher battery life.

[0158] Exemplarily, the Redcap UE has one or more of the following capabilities:

[0159] (1) The maximum bandwidth on frequency range 1 (FR1) is 20 MHz.

[0160] (2) In the 4-step random access channel (RACH) process, Msg1 can be used for early identification of RedCap UE.

[0161] (3) A separate initial uplink bandwidth part (BWP) is configured for RedCap UEs. The initial uplink BWP includes the configuration required for the RedCap UE to perform random access and includes a frequency hopping switch on the common physical uplink control channel (PUCCH) resources.

[0162] (4) A separate initial downlink BWP is configured for the RedCap UE. The initial downlink BWP includes a common search space / control resource set (CORESET) for random access. If it is used for paging, it also needs to include the cell-defined SSB. If it is only used for random access, it may or may not include the SSB. If it is a separate initial downlink BWP used in the connected state and used as BWP#0 configuration option 1, it needs to include the cell-defined SSB.

[0163] (5) On each carrier frequency, one UE-specific downlink BWP configured by radio resource control (RRC) is supported.

[0164] (6) On each carrier frequency, one UE-specific uplink BWP configured by RRC is supported.

[0165] (7) Use RRC to reconfigure any parameters related to BWP.

[0166] (8) UE-specific RRC-configured downlink BWP, including cell-defined SSB or non-cell-defined SSB.

[0167] (9) On the RRC-configured downlink BWP, measurements based on non-cell-defined SSBs can be performed.

[0168] 2. Enhanced reduced capability (eRedcap) terminal devices

[0169] The terminal equipment of eRedcap is also called eRedcap terminal or eRedcap UE. eRedcap UE is an enhanced reduced capability terminal proposed by R18, which means further tailoring the terminal performance on the basis of RedcapUE to achieve the purpose of reducing the complexity of the terminal. Among them, eRedcapUE can be further divided into two types of terminals, namely the first type of enhanced reduced capability terminal equipment (for example, recorded as eRedCap UE1, or recorded as BW3 / PR3+PR1) and the second type of enhanced reduced capability terminal equipment (for example, recorded as eRedCap UE2, or recorded as 20MHz+PR1). Among them, the first type of enhanced reduced capability terminal equipment is an enhanced reduced capability terminal equipment with a peak rate of 10Mbps and supports a bandwidth of 20MHz, and the second type of enhanced reduced capability terminal equipment is an enhanced reduced capability terminal equipment with a peak rate of 10Mbps and supports a bandwidth less than 20MHz. For example, the second type of enhanced reduced capability terminal equipment is an enhanced reduced capability terminal equipment with a peak rate of 10Mbps and supports a bandwidth of 5MHz.

[0170] For example, the second type of enhanced reduced-capability terminal equipment (i.e., eRedCap UE2) has, in addition to the capabilities described in (1) to (9) above, one or more of the following capabilities:

[0171] (10) The uplink / downlink peak data rate (referred to as peak rate) is 10Mbps.

[0172] (11) The maximum number of physical resource blocks (PRBs) that can be scheduled / configured for unicast on the physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) is 25 PRBs for a 15 kHz subcarrier spacing configuration and 12 PRBs for a 30 kHz subcarrier spacing configuration.

[0173] (12) When the number of PRBs occupied by the random access response (RAR) PDSCH and MsgB PDSCH (if supported) is greater than 25 / 12 PRBs for 15 or 30 kHz subcarrier spacing, the processing time for 15 / 30 kHz SCS is relaxed to 1 / 0.5 ms.

[0174] (13) The network may be configured to attach a separate early indication for Rel-18eRedCap UE in Msg1.

[0175] Optionally, for the first type of enhanced reduced-capability terminal equipment (i.e., eRedCap UE1), it has capabilities similar to those of eRedCapUE2, but there are subtle differences, such as not supporting the above-mentioned capability (11), or the bandwidth supported by eRedCapUE1 is not reduced compared to RedCap UE, or, it can also be based on other capabilities or preferences to distinguish eRedCap UE1 from eRedCap UE2.

[0176] 3. Community Types

[0177] In the 5G communication system, cells are classified and defined according to the services that the cells can provide to terminal devices. Generally, there are the following types:

[0178] (1) Acceptable cell

[0179] An acceptable cell is a cell where a terminal device can camp to obtain limited services (such as making emergency calls, receiving earthquake and tsunami warning system (ETWS), and commercial mobile alert system (CMAS) notifications). Such a cell should meet the following requirements, which are the minimum set of requirements for making emergency calls and receiving ETWS and CMAS notifications in an NR network:

[0180] ① The community is not barred;

[0181] ②Meet the community selection criteria.

[0182] (2) Suitable cell

[0183] (2-1) For a terminal device in non-standard stand-alone non-public network (SNPN) access mode, a cell is considered suitable if the following conditions are met:

[0184] ① The cell is part of a selected public land mobile network (PLMN) or a registered PLMN or a PLMN in an equivalent PLMN list, and for that PLMN:

[0185] The PLMN identifier of the PLMN is broadcast by the cell, the cell is not associated with a closed access group (CAG) identifier, and the CAG-only indication for the PLMN in the terminal device does not exist or is false; or, the allowed CAG list for the PLMN in the terminal device includes the CAG identifier broadcast by the cell for the PLMN.

[0186] ②Meet the community selection criteria

[0187] ③ Based on the information provided by the non-access stratum (NAS), determine:

[0188] (i) The community is not prohibited;

[0189] (ii) the cell is part of at least one tracking area which is not part of the list of "prohibited tracking areas for roaming" belonging to the selected SNPN or the registered SNPN of the terminal device.

[0190] (2-2) For a terminal device operating in SNPN access mode, a cell is considered suitable if the following conditions are met:

[0191] ① The cell is part of the SNPN selected by the terminal device or the registered SNPN;

[0192] ②Meet the community selection criteria;

[0193] ③ Based on the latest information provided by NAS, determine:

[0194] (i) The community is not prohibited;

[0195] (ii) the cell is part of at least one tracking area that is not part of a list of "Forbidden Tracking Areas for Roaming" belonging to the selected SNPN or the registered SNPN of the terminal device.

[0196] (3) Barred cell

[0197] The cell may be indicated as a prohibited cell in the system information, for example, the prohibited cell may be indicated by a cell status indication field in a master information block (MIB) or a system information block 1 (SIB1).

[0198] For example, when the value of the cellBarred field included in the MIB is barred, it means that the cell is prohibited from being accessed by terminal devices (or called a prohibited cell, or an access prohibited cell, or a prohibited cell); when the value of the cellBarred field included in the MIB is not barred, it means that the cell is not prohibited from being accessed by terminal devices (or called a non-prohibited cell, or a non-access prohibited cell, or a non-prohibited cell).

[0199] For another example, when the value of the non-terrestrial network cell barred (cellBarredNTN) field included in SIB1 is barred, it indicates that terminal equipment is prohibited from accessing the cell. When the value of the cell barred (cellBarred) field included in SIB1 is not barred, it indicates that terminal equipment is not prohibited from accessing the cell.

[0200] For another example, when the value of the field "Prohibition of terminal devices with reduced capability of 1 wireless channel from accessing the cell" (cellBarredRedCap1Rx) included in SIB1 is barred, it indicates that terminal devices are prohibited from accessing the cell. When the value of the field "Prohibition of terminal devices with reduced capability of 1 wireless channel from accessing the cell" (cellBarredRedCap1Rx) included in SIB1 is not barred, it indicates that terminal devices are not prohibited from accessing the cell.

[0201] For another example, when the value of the field "Prohibition of terminal devices with reduced capabilities of 2 radio channels from accessing the cell" (cellBarredRedCap2Rx) included in SIB1 is barred, it indicates that terminal devices are prohibited from accessing the cell. When the value of the field "Prohibition of terminal devices with reduced capabilities of 2 radio channels from accessing the cell" (cellBarredRedCap2Rx) included in SIB1 is not barred, it indicates that terminal devices are not prohibited from accessing the cell.

[0202] (4) Reserved cell

[0203] The cell may be indicated as a reserved cell in the system information, for example, the reserved cell may be indicated through a special reserved indication field in the MIB or SIB1.

[0204] For example, when the value of the cell reserved for operator use (cellReservedForOperatorUse) field included in SIB1 is reserved, it means that the cell is reserved (or called a reserved cell); when the value of the cellReservedForOperatorUse field included in SIB1 is not reserved, it means that the cell is not reserved (ie, it is not a reserved cell).

[0205] For another example, when the value of the cell reserved for other uses (cellReservedForOtherUse) field included in SIB1 is true, it indicates that the cell is reserved (or called a reserved cell). It should be noted that the value of the above cellReservedForOtherUse field is true, indicating that SIB1 includes the cellReservedForOtherUse field, that is, if the cellReservedForOtherUse field appears in SIB1, its value is true.

[0206] For another example, when the value of the cellReservedForFutureUse field included in SIB1 is true, it indicates that the cell is reserved (or called a reserved cell). Similarly, the value of the cellReservedForFutureUse field is true, indicating that SIB1 includes the cellReservedForOtherUse field, that is, if the cellReservedForFutureUse field appears in SIB1, its value is true.

[0207] It should be understood that the cell selection / reselection process of the terminal device can be controlled by the cell status indication field and the special reserved indication field. Generally speaking, when a cell is neither a prohibited cell nor a reserved cell, the cell can be used as a candidate cell in the cell selection / reselection process. That is to say, the terminal device can judge whether the cell can be used as a candidate cell in the subsequent cell selection / reselection process based on the above indication field information. For example, when the value of the cell status indication field is not barred (i.e., the cell does not prohibit terminal device access) and not reserved (i.e., the cell is not restricted to operator use only), and true does not appear (i.e., the cell is not used for other purposes, nor is it used for future use), the terminal device can use the cell as a candidate cell in the subsequent cell selection / reselection process.

[0208] Optionally, in addition to the above-mentioned cell status indication field or special reserved indication field, there are some other indication fields, which also play a similar role, so that the terminal device can judge whether it can access the cell based on its own type and capabilities. For example, other indication fields can be the terminal device access cell with reduced capabilities that allows half-duplex (halfDuplexRedCapAllowed) field included in SIB1 or the integrated access and backhaul (IAB) (iab-Support) field. Among them, when the value of halfDuplexRedCapAllowed is true, it means that the cell supports half-duplex; when the value of the iab-Support field is true, it means that the cell supports IAB.

[0209] It should be understood that the value of the halfDuplexRedCapAllowed / iab-Support field is true here, indicating that the halfDuplexRedCapAllowed / iab-Support field is included in SIB1, that is, if the halfDuplexRedCapAllowed / iab-Support field appears in SIB1, its value is true. Correspondingly, if the halfDuplexRedCapAllowed / iab-Support field is not included in SIB1 (that is, the halfDuplexRedCapAllowed / iab-Support field does not appear in SIB1, or halfDuplexRedCapAllowed / iab-Support is not broadcast by the cell), it means that the cell does not support half-duplex / IAB.

[0210] Take halfDuplexRedCapAllowed as an example. When halfDuplexRedCapAllowed is not broadcast by the cell (i.e., the halfDuplexRedCapAllowed field is not included in SIB1), it means that the cell does not support half-duplex terminal equipment with reduced capabilities. However, if RedCapUE only supports half-duplex mode under frequency division duplex (FDD), the cell will be unable to provide services for RedCap UE supporting half-duplex mode. Therefore, RedCap UE can consider the cell as a cell that it is prohibited to access, or the cell status can be regarded as prohibited.

[0211] It should be understood that the current protocol stipulates that when the cell status is indicated as prohibited (or the cell is deemed to be in a prohibited state), the terminal device cannot select / reselect the cell, even for emergency calls. However, the current protocol restrictions are too strict, because the network may consider network transmission efficiency for access control of RedCap / eRedCap UE. For example, when the network transmission efficiency is low, the network may prohibit RedCap / eRedCap UE from accessing the cell. Therefore, RedCap / eRedCap UE cannot initiate emergency calls, or cannot send and receive relevant information in special business scenarios such as earthquakes, fires, or alarms, which limits the application scenarios of RedCap / eRedCap UE and has low flexibility.

[0212] Based on this, the present application proposes a communication method, which is conducive to improving communication flexibility.

[0213] The communication method and communication device provided by this application are described in detail below:

[0214] See also Figure 2 , Figure 2 is a flow chart of the communication method provided in the embodiment of the present application. Figure 2 As shown, the communication method includes the following steps S201 to S203. Figure 2 The method execution subject shown may be a terminal device (for example, a first terminal device is used as an example for schematic illustration, wherein the first terminal device may be a traditional NR terminal, a RedCap UE or an eRedCap UE, etc., and the following application mainly introduces the case where the first terminal device is a RedCap UE or an eRedCap UE) and a network device, or, Figure 2 The execution subject of the method shown can also be a chip in a terminal device and a chip in a network device. For the convenience of description, Figure 2 The following mainly uses terminal devices and network devices as the execution subjects of the method as examples. It should be noted that: Figure 2 is a schematic flow chart of a method embodiment of the present application, showing detailed communication steps or operations of the method, but these steps or operations are only examples, and the present application embodiment may also perform other operations or Figure 2 In addition, Figure 2 The steps in Figure 2 are executed in a different order than those presented, and may not be executed in the order Figure 2 All operations in . Among them:

[0215] S201, a network device sends system information to a first terminal device. Correspondingly, the terminal device receives the system information from the network device.

[0216] Here, the system information may indicate whether the cell under the network device is a prohibited access cell for a terminal device with reduced capabilities. In addition, the system information also includes first information, which indicates whether the cell under the network device supports the terminal device with reduced capabilities to perform emergency services in a prohibited access state (or the first information is understood as whether the indication of the prohibited cell can be ignored in an emergency service situation). Generally speaking, the system information may be MIB or SIB (for example, SIB may be SIB1), etc., and this application does not limit this. For ease of understanding, this application mainly uses the system message SIB1 as an example for schematic illustration.

[0217] In some scenarios, SIB1 may include an indication information, which is used to indicate whether the cell under the network device is a prohibited access cell for a terminal device with reduced capabilities of N antenna channels, where N is a positive integer. For example, in a case 1, SIB1 may include a first indication information, which is used to indicate whether the cell under the network device is a prohibited access cell for a terminal device with reduced capabilities of 1 antenna channel. Exemplarily, the first indication information may also be referred to as prohibited access cell indication information (or cellBarredRedCap1Rx) for a terminal device with reduced capabilities of 1 wireless channel. It should be understood that the message name / name or the name of each parameter in the message involved in the present application is only an example, and other names may also be used in the specific implementation, and the embodiments of the present application do not specifically limit this. For another example, in a case 2, SIB1 may include a second indication information, which is used to indicate whether the cell under the network device is a prohibited access cell for a terminal device with reduced capabilities of 2 antenna channels. Exemplarily, the second indication information may also be referred to as prohibited access cell indication information (or cellBarredRedCap2Rx) for a terminal device with reduced capabilities of 2 wireless channels.

[0218] In some other scenarios, SIB1 may also include third indication information, where the third indication information is indication information for allowing a half-duplex reduced-capability terminal device to access the cell, such as halfDuplexRedCapAllowed.

[0219] Optionally, SIB1 may also indicate whether RedCap UE is supported, and / or whether eRedCap UE is supported. It should be understood that the way in which SIB1 indicates whether RedCap UE is supported may be that SIB1 includes an indication information (e.g., fourth indication information). When the fourth indication information indicates support, it indicates that the cell under the network device supports RedCap UE. When the fourth indication information indicates non-support, it indicates that the cell under the network device does not support RedCap UE. Alternatively, another indication information (e.g., fifth indication information) may be defined. When SIB1 includes the fifth indication information, it indicates that the cell under the network device supports RedCap UE. When SIB1 does not include the fifth indication information, it indicates that the cell under the network device does not support RedCap UE. Similarly, the way in which SIB1 indicates whether eRedCap UE is supported may refer to the aforementioned way in which SIB1 indicates whether RedCap UE is supported, which will not be repeated here.

[0220] Optionally, SIB1 may also include intra-frequency reselection indication information corresponding to a terminal device with reduced capabilities, and the intra-frequency reselection indication information indicates that RedCap / eRedCap UE is allowed to perform intra-frequency reselection. Exemplarily, the intra-frequency reselection indication information corresponding to a terminal device with reduced capabilities may be intraFreqReselectionRedCap. Generally speaking, when SIB1 contains intra-frequency reselection indication information corresponding to a terminal device with reduced capabilities (or when intraFreqReselectionRedCap appears in SIB1), the value of intraFreqReselectionRedCap is true, indicating that RedCap / eRedCap UE is supported / allowed to perform intra-frequency reselection; when SIB1 does not contain intra-frequency reselection indication information corresponding to a terminal device with reduced capabilities (or when intraFreqReselectionRedCap does not appear in SIB1), it indicates that RedCap / eRedCap UE is not supported / allowed to perform intra-frequency reselection. It should be understood that when the RedCap / eRedCap UE is not supported to perform intra-frequency reselection, it means that the cell of the network device is a prohibited cell. When the RedCap / eRedCap UE is supported to perform intra-frequency reselection, it is necessary to further combine other indication information to determine whether the cell of the network device is a prohibited cell. For example, the other indication information may be the first indication information, the second indication information or the third indication information, etc. See the subsequent description for details.

[0221] S202. The first terminal device determines whether it can access a cell under the network device to perform emergency services based on system information.

[0222] In some feasible implementations (a), after receiving the system information, the first terminal device may store the received system information. If the first terminal device is a RedCap / eRedCap UE in a non-connected state (for example, an idle state or an inactive state), or the first terminal device is a RedCap / eRedCap UE performing an RRC reconstruction process in a connected state (or described as the first terminal device being a connected RedCap / eRedCap UE and the timer T311 of the first terminal device is running), then the first terminal device may determine that the first terminal device can access the cell under the network device to perform emergency services when the system information indicates that the cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, and the first information indicates that the cell under the network device supports terminal devices with reduced capabilities to perform emergency services in a prohibited access state.

[0223] The following first introduces several implementation methods of indicating that the cell under the network device is a prohibited access cell for terminal devices with reduced capabilities through system information:

[0224] An implementation method 1, when the system information does not include the intra-frequency reselection indication information corresponding to the terminal device with reduced capability (for example, SIB1 does not include intraFreqReselectionRedCap), the first terminal device can determine that the cell under the network device is a prohibited access cell based on the system information that does not include intraFreqReselectionRedCap.

[0225] An implementation method 2, when the system information includes intra-frequency reselection indication information corresponding to the terminal device with reduced capability (for example, SIB1 includes intraFreqReselectionRedCap), and the first indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of one antenna channel (for example, SIB1 includes cellBarredRedCap1Rx, and the value of cellBarredRedCap1Rx is barred), if the first terminal device is a RedCap / eRedCap UE including one antenna channel, then the first terminal device can determine that the cell under the network device is a prohibited access cell based on the system information.

[0226] An implementation method 3, when the system information includes intra-frequency reselection indication information corresponding to the terminal device with reduced capability (for example, SIB1 includes intraFreqReselectionRedCap), and the first indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 2 antenna channels (for example, SIB1 includes cellBarredRedCap2Rx, and the value of cellBarredRedCap2Rx is barred), if the first terminal device is a RedCap / eRedCap UE including 2 antenna channels, then the first terminal device can determine that the cell under the network device is a prohibited access cell based on the system information.

[0227] An implementation method 4, when the system information includes the intra-frequency reselection indication information corresponding to the terminal device with reduced capability (for example, SIB1 includes intraFreqReselectionRedCap), and does not include the third indication information (here, the third indication information is the indication information allowing the terminal device with reduced capability in half-duplex to access the cell, such as halfDuplexRedCapAllowed), if the first terminal device is a RedCap / eRedCap UE that only supports the half-duplex mode under FDD, then the first terminal device can determine that the cell under the network device is a prohibited access cell based on the system information.

[0228] It should be noted that in the current standards, when any of the above implementation modes 1 to 4 occurs, the RedCap / eRedCap UE may determine the cell under the network device as a prohibited access cell (referred to as a prohibited cell). However, in the present application, since a new information (i.e., the first information) is added to the system information, and the first information indicates that the cell under the network device supports the terminal device with reduced capabilities to perform emergency services in a prohibited access state (or the first information indicates that in the case of emergency services, the indication of the prohibited cell can be ignored), therefore, the RedCap / eRedCap UE combines the indication of the first information, even if any of the above-mentioned implementation methods 1 to 4 occurs, the RedCap / eRedCap UE can also consider that the cell is not a prohibited cell, or, it is described as the cell is not a prohibited cell during the duration of the emergency service, or, it is described as the RedCap / eRedCap UE considers the cell to be a prohibited cell, but when the RedCap / eRedCap UE has an emergency service, it can still select / reselect the cell for emergency services, or, it is described as the RedCap / eRedCap UE considers the cell to be a prohibited cell, but when the RedCap / eRedCap UE has an emergency service, it can select / reselect the cell for emergency services during the duration of the emergency service). That is to say, the above implementation (a) adjusts the judgment condition of the prohibited cell, namely: when the first information included in the system information indicates that the cell under the network device supports the terminal device with reduced capability to perform emergency services in the prohibited access state, the cell under the network device is considered not to be a prohibited cell.

[0229] In some feasible implementation methods (ii), the first terminal device determines whether it can access the cell under the network device to perform emergency services based on the system information. It can be understood that: when the cell under the network device is determined to be an acceptable cell based on the system information (that is, when the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capabilities, and the first information included in the system information indicates that the cell under the network device supports the terminal device with reduced capabilities to perform emergency services in a prohibited access state, the cell under the network device can be determined to be an acceptable cell), the first terminal device can determine that it can access the cell under the network device to perform emergency services. In the implementation method (ii) of the present application, the acceptable cell meets the following conditions: the terminal device with reduced capabilities can perform emergency services in a prohibited access state (hereinafter referred to as condition 1). That is to say, the implementation method (ii) adds a judgment condition for an acceptable cell (that is, condition 1), which can replace the existing judgment condition ① (that is, the cell is not prohibited) introduced in "(1) Acceptable cell" in the above "3. Cell type", so that even if the existing judgment condition ① is not met, if the new condition 1 is met, combined with condition ② (that is, the cell selection standard is met), the cell can also be considered as an acceptable cell. Optionally, the newly added condition 1 can also be described as: for RedCap / eRedCap UE, in an emergency service scenario (or during the duration of the emergency service), ignore the indication of the prohibited cell. Here, "the indication of the prohibited cell" generally refers to the first indication information in the above implementation method 2 (e.g., cellBarredRedCap1Rx) or the second indication information in the implementation method 3 (e.g., cellBarredRedCap2Rx), etc., and this application does not limit this.

[0230] Optionally, in some feasible implementation modes (three), the first terminal device determines whether it can access the cell under the network device to perform emergency services based on the system information. It can also be understood that: when the cell under the network device is determined to be a suitable cell based on the system information, the first terminal device determines that it can access the cell under the network device to perform emergency services. In implementation mode (three) of the present application, the suitable cell meets the following conditions: the terminal device with reduced capabilities is supported to perform emergency services in a prohibited access state (hereinafter referred to as condition 1). Similar to the above implementation mode (two), implementation mode (three) also adds a judgment condition for a suitable cell (i.e., condition 1). This condition 1 can replace the existing judgment condition (i) introduced in "(2) Suitable cell" in the above "3. Cell type" (i.e., the cell is not prohibited), so that even if the existing judgment condition (i) is not met, if the new condition 1 is met, combined with the other conditions introduced in "(2) Suitable cell", the cell can also be considered to be a suitable cell.

[0231] Optionally, in some feasible implementation modes (four), another implementation mode (hereinafter referred to as implementation mode 5) is proposed in which the cell under the system information indicating the network device is a prohibited access cell for the terminal device with reduced capability, and the implementation mode 5 is:

[0232] In the case where the first terminal device is an eRedCap UE (e.g., eRedCap UE1 or eRedCap UE2), if the frequency band information of the cell under the network device is not greater than the first bandwidth (e.g., the first bandwidth may be 5MHz), and the system information indicates that the eRedCap UE is not supported, then the first terminal device may determine that the cell under the network device is a prohibited access cell based on the system information. In other words, when the frequency band (band) of the cell of the network device or the cell carrier bandwidth is less than or equal to 5MHz, and the system information indicates that the eRedCap UE is not supported, the cell under the network device is a cell prohibited from access by the eRedCap UE.

[0233] It should be noted that, in the current standard, when the above-mentioned implementation method 5 occurs, eRedCap UE1 or eRedCap UE2 can determine that the cell under the network device is a prohibited access cell (referred to as a prohibited cell). However, in the present application, since a new information (i.e., the first information) is added to the system information, and the first information indicates that the cell under the network device supports terminal devices with reduced capabilities to perform emergency services in a prohibited access state, therefore, eRedCap UE1 or eRedCap UE2 combines the indication of the first information, even if the above-mentioned implementation method 5 occurs, eRedCap UE1 or eRedCap UE2 can also consider that the cell is not a prohibited cell.

[0234] Optionally, in some feasible implementation modes (V), another implementation mode (hereinafter referred to as implementation mode 6) is proposed in which the cell under the system information indicating the network device is a prohibited access cell for the terminal device with reduced capability, and the implementation mode 6 is:

[0235] In the case that the first terminal device is a first type enhanced reduced-capability terminal device (i.e., eRedCap UE1), if the system information indicates (the cell of the network device) that the reduced-capability terminal device is supported but the enhanced reduced-capability terminal device is not supported, then the first terminal device can determine, based on the system information, that the cell under the network device is an access-prohibited cell (or that the cell under the network device is an access-prohibited cell for eRedCap UE1).

[0236] It should be noted that, in the current standard, when the above-mentioned implementation method 6 occurs, eRedCap UE1 can determine that the cell under the network device is a prohibited access cell (referred to as a prohibited cell). However, in the present application, since a new information (i.e., the first information) is added to the system information, and the first information indicates that the cell under the network device supports terminal devices with reduced capabilities to perform emergency services in a prohibited access state, therefore, eRedCap UE1 combines the indication of the first information, and even if the above-mentioned implementation method 6 occurs, eRedCap UE1 can also consider that the cell is not a prohibited cell.

[0237] Optionally, in some feasible implementations (six), another implementation method (hereinafter referred to as implementation method 7) is proposed in which the cell under the system information indicating the network device is a prohibited access cell for the terminal device with reduced capability, and the implementation method 7 is:

[0238] In the case where the first terminal device is a RedCap UE, if the frequency band information of the cell under the network device is not greater than the second bandwidth (for example, the second bandwidth is 20MHz), and the system information indicates that RedCap UE is not supported, then the first terminal device can determine that the cell under the network device is a prohibited access cell based on the system information. In other words, when the band of the cell of the network device or the cell carrier bandwidth is less than or equal to 20MHz, and the system information indicates that the cell of the network device does not support RedCap UE, the cell under the network device is a cell prohibited from access by RedCap UE.

[0239] It should be noted that, in the current standard, when the above-mentioned implementation method 7 occurs, the RedCap UE can determine that the cell under the network device is a prohibited access cell (referred to as a prohibited cell). However, in the present application, since a new information (i.e., the first information) is added to the system information, and the first information indicates that the cell under the network device supports the terminal device with reduced capabilities to perform emergency services in a prohibited access state, the RedCap UE combines the indication of the first information, and even if the above-mentioned implementation method 7 occurs, the RedCap UE can also consider that the cell is not a prohibited cell.

[0240] S203: The first terminal device sends second information to the network device. Correspondingly, the network device receives the second information from the first terminal device.

[0241] In some feasible implementations, when it is determined that the first terminal device can access the cell under the network device to perform emergency services, the first terminal device sends second information to the network device, and the second information is used to indicate the type of eRedCap UE to which the first terminal device belongs. There are mainly two types of eRedCap UE, namely eRedCap UE1 and eRedCap UE2. For the explanation of eRedCap UE1 and eRedCap UE2, please refer to the relevant description in the aforementioned related technical feature "2. Enhanced reduced capability terminal device", which will not be repeated here.

[0242] It should be understood that the second information may indicate the type of eRedCapUE to which the first terminal device belongs in a direct or indirect manner.

[0243] Exemplarily, the second information directly includes the type of eRedCap UE to which the first terminal device belongs. For example, a new information element (IE) may be added in Msg5, and the newly added information element is used to carry information about the type of eRedCap UE to which the first terminal device belongs. For another example, the information about the type of eRedCap UE to which the first terminal device belongs may also be carried in a medium access control control element (MAC CE), or a new MAC CE may be designed to indicate information about the type of eRedCap UE to which the first terminal device belongs.

[0244] As another example, the second information includes capability information (or expected configuration information) of the first terminal device, and the capability information (or expected configuration information) is used to indicate the type of eRedCap UE to which the first terminal device belongs. Taking the number of PRBs as an example, the first terminal device can report through Msg5 that the maximum number of PRBs it supports (or the expected maximum number of PRBs) is 25 PRBs under a 15kHz subcarrier spacing configuration, and / or, 12 PRBs under a 30kHz subcarrier spacing configuration. It should be understood that the current difference between eRedCap UE1 and eRedCap UE2 is that the maximum number of PRBs supported is different, but different types of eRedCap UEs can also be distinguished based on other capabilities or preferences such as peak rate.

[0245] It should be noted that the sending of the above-mentioned second information can use the RACH process. For example, when it is determined that the cell under the network device can be accessed to perform emergency services, the first terminal device can initiate the RACH process. Here, the RACH process can be a contention-based random access (CBRA) process or a non-contention-based random access (CFRA) process. For the specific processes of CBRA and CFRA, please refer to TS38321, which will not be repeated here.

[0246] Exemplarily, when sending Msg1 or Msg3, the first terminal device may indicate that the first terminal device is an eRedCap UE through Msg1 or Msg3. Further, when sending Msg5, Msg5 may be used to indicate whether the first terminal device is specifically eRedCap UE1 or eRedCap UE2. Among them, Msg1 is a random access preamble code, and Msg3 may be an RRC establishment request message (RRCSetupRequest) message transmitted during the RRC establishment process, including the RRC connection establishment reason and the terminal identifier (ID). The terminal ID may be an S temporary mobile user identity (S-temporary mobile subscriber identity, S-TMSI) or a random number. Optionally, Msg3 may also be an RRC recovery request (RRCResumeRequest) message in the RRC recovery process, or an RRC reconstruction request (RRCReestablishmentRequest) message in the RRC reconstruction process, etc. Correspondingly, Msg5 can be the RRC establishment message (RRCSetup) message and the RRC establishment completion message (RRCSetupComplete) message transmitted during the RRC establishment process, or the RRC recovery message (RRCResume) message and the RRC recovery completion message (RRCResumeComplete) message transmitted during the RRC recovery process, or the RRC reconstruction message (RRCReestablishment) message and the RRC reconstruction completion message (RRCReestablishmentComplete) message transmitted during the RRC reconstruction process.

[0247] It should be understood that there are two possible implementations of indicating that the first terminal device is an eRedCap UE through Msg1 or Msg3:

[0248] Type 1: The network device configures exclusive resources for sending Msg1 or Msg3 for the eRedCap UE, so the first terminal device can use the configured exclusive resources to send Msg1 or Msg3 to the network device, so that the network device can preliminarily determine that the first terminal device is an eRedCap UE based on the resources occupied by Msg1 or Msg3.

[0249] Type 2: The network device does not configure exclusive resources for eRedCap UE to send Msg1 or Msg3, but configures resources for RedCap UE to send Msg1 or Msg3. Therefore, the first terminal device can reuse the resources configured for RedCap UE to send Msg1 or Msg3 to the network device. Under this implementation method, the network device can determine that the first terminal device may be RedCap UE or eRedCap UE based on the resources occupied by Msg1 or Msg3.

[0250] Furthermore, in the CBRA process, after the first terminal device receives Msg4 from the network device, the first terminal device may then send Msg5 to the network device. In addition to the information defined in TS38331, Msg5 may also include the second information in the present application, which is used to indicate whether the type of the eRedCap UE is eRedCap UE1 or eRedCapUE2. This helps the network device configure a bandwidth and transmission mode that matches the capabilities of the first terminal device based on the specific type of eRedCap UE reported by the first terminal device, so as to avoid the configured bandwidth resources or transmission mode exceeding the capabilities supported by the first terminal device.

[0251] Optionally, when it is determined that the first terminal device can access the cell under the network device to perform emergency services, the first terminal device can also enter the connected state to perform emergency tasks, such as initiating an emergency call, or receiving an ETWS notification, or receiving a CMAS notification. Optionally, when it is determined that the first terminal device can access the cell under the network device to perform emergency services, the first terminal device can also use a small data transmission (SDT) process to send data, etc., which is not limited here.

[0252] It should be noted that the above step S203 is an optional step. Step S203 can also be used as an independent embodiment, that is, the reporting of the type of eRedCap UE1 or eRedCap UE2 may not depend on the scenario of executing emergency services in the cell under the aforementioned network device.

[0253] In the embodiment of the present application, with respect to the access control of RedCap / eRedCap UE, a solution is proposed that can allow RedCap / eRedCap UE to perform emergency services in an access-prohibited state, thereby improving communication flexibility.

[0254] The following will be combined Figure 3-4 The communication device provided in this application is described in detail.

[0255] It is understandable that in order to implement the functions in the above embodiments, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0256] Figure 3 and Figure 4 Schematic diagram of the structure of possible communication devices provided in the embodiments of the present application. These communication devices can be used to implement the functions of the terminal device (such as the first terminal device) or the network device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of the present application, the terminal device can be such as Figure 1 One of the terminals 120a-120j shown in FIG. 1 may also be a module (such as a chip) applied to a terminal device. The network device may be, for example, Figure 2 The satellite shown may also be a module (such as a chip) used in network equipment.

[0257] like Figure 3 As shown, the communication device 300 includes a processing unit 310 and a transceiver unit 320. The communication device 300 is used to implement the above Figure 2 The functions of the terminal device or the network device in the method embodiment shown in FIG.

[0258] When the communication device 300 is used to implement Figure 2 In the method embodiment shown, the functions of the first terminal device are:

[0259] The transceiver unit 320 is configured to receive system information, wherein the system information indicates whether a cell under the network device is a prohibited access cell for a terminal device with reduced capabilities, and the system information further includes first information, wherein the first information indicates whether the cell under the network device supports the terminal device with reduced capabilities to perform emergency services in a prohibited access state;

[0260] The processing unit 310 is used to determine whether it is possible to access the cell under the network device to perform emergency services according to the system information.

[0261] When the communication device 300 is used to implement Figure 2 The functions of the network device in the method embodiment shown are:

[0262] The processing unit 310 is configured to determine system information, wherein the system information indicates whether a cell under the network device is a prohibited access cell for a terminal device with reduced capabilities, and the system information further includes first information, wherein the first information indicates whether the cell under the network device supports the terminal device with reduced capabilities to perform emergency services in a prohibited access state;

[0263] The transceiver unit 320 is configured to send the system information.

[0264] For more detailed description of the processing unit 310 and the transceiver unit 320, please refer to Figure 2 The method embodiment shown is described in detail.

[0265] like Figure 4 As shown, the communication device 400 includes a processor 410 and an interface circuit 420. The processor 410 and the interface circuit 420 are coupled to each other. It is understood that the interface circuit 420 can be a transceiver or an input-output interface. Exemplarily, the communication device 400 may also include a memory 430 for storing instructions executed by the processor 410 or storing input data required by the processor 410 to execute instructions or storing data generated after the processor 410 executes instructions.

[0266] When the communication device 400 is used to implement Figure 2 When the method is shown, the processor 410 is used to implement the function of the processing unit 310, and the interface circuit 420 is used to implement the function of the transceiver unit 320.

[0267] When the above communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiment. The terminal device chip receives information sent by the network device to the terminal device through other modules in the terminal device (such as a radio frequency module or an antenna); or, the terminal device chip sends information to other modules in the terminal device (such as a radio frequency module or an antenna), and the information is sent by the terminal device to the network device.

[0268] When the above-mentioned communication device is a module applied to a network device, the network device module implements the function of the network device in the above-mentioned method embodiment. The network device module receives information from other modules in the network device (such as a radio frequency module or an antenna), and the information is sent by the terminal device to the network device; or, the network device module sends information to other modules in the network device (such as a radio frequency module or an antenna), and the information is sent by the network device to the terminal device. The network device module here can be a baseband chip of the network device, or it can be other modules.

[0269] The present application also provides a communication device, which includes a processor. When the communication device is a terminal device, the processor is used to implement the above-mentioned implementation. Figure 2 The actions performed by the first terminal device in the method shown in the figure, when the communication device is a network device, the processor is used to implement the above implementation Figure 2 Actions performed by the network device in the method shown.

[0270] The present application also provides a communication system, which includes a terminal device and a network device. The terminal device is used to implement Figure 2 The actions performed by the first terminal device in the method shown, the network device is used to implement the above implementation Figure 2 Actions performed by the network device in the method shown.

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

[0272] The method steps in the embodiments of the present application can be implemented in hardware, or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, register, hard disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and can write information to the storage medium. The storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a network device or a terminal device. The processor and the storage medium can also be present in a network device or a terminal device as discrete components.

[0273] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device or other programmable device. The computer program or instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instruction may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server, data center, etc. that integrates one or more available media. The available medium may be a magnetic medium, for example, a floppy disk, a hard disk, a tape; it may also be an optical medium, for example, a digital video disc; it may also be a semiconductor medium, for example, a solid-state hard disk. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0274] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0275] It is understood that the various numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that: Applied to a first terminal device, the method includes: Receiving system information, the system information indicating whether a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, the system information also including first information indicating whether the cell under the network device supports the terminal devices with reduced capabilities to perform emergency services in a prohibited access state; Determine whether it is possible to access a cell under the network device to perform emergency services according to the system information.

2. The method according to claim 1, characterized in that The first terminal device is a reduced capability terminal device or an enhanced reduced capability terminal device, and the first terminal device is in a non-connected state or is a terminal device performing a radio resource control RRC reestablishment process in a connected state; The determining, according to the system information, whether it is possible to access a cell under the network device to perform an emergency service includes: When the system information indicates that the cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, and the first information indicates that the cell under the network device supports terminal devices with reduced capabilities to perform emergency services in a prohibited access state, it is determined that the cell under the network device can be accessed to perform emergency services.

3. The method according to claim 1 or 2, characterized in that: The system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The system information does not include same-frequency reselection indication information corresponding to the terminal device with reduced capability.

4. The method according to claim 1 or 2, characterized in that: The first terminal device includes one antenna channel; the system information indicates that the cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the first indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 1 antenna channel.

5. The method according to claim 1 or 2, characterized in that: The first terminal device includes two antenna channels; the system information indicates that the cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the second indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 2 antenna channels.

6. The method according to claim 1 or 2, characterized in that: The first terminal device supports a half-duplex mode under frequency division duplex FDD; and the system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and does not include the third indication information, where the third indication information is the indication information for allowing the terminal device with reduced capability in half-duplex to access the cell.

7. The method according to claim 1, characterized in that The system information indicates that the cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, and the first information indicates that the cell under the network device supports the terminal devices with reduced capabilities to perform emergency services in a prohibited access state; The determining, according to the system information, whether it is possible to access a cell under the network device to perform an emergency service includes: In the case where it is determined according to the system information that the cell under the network device is an acceptable cell, determining that the cell under the network device can be accessed to perform emergency services; The acceptable cells meet the following conditions: Supports terminal devices with reduced capabilities to perform emergency services in a prohibited access state.

8. The method according to claim 7, characterized in that The acceptable cells also satisfy the cell selection criteria.

9. The method according to claim 1, characterized in that: The first terminal device is an enhanced reduced-capability terminal device; The system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The frequency band information of the cell under the network device is not greater than 5 MHz, and the system information indicates a terminal device that does not support enhanced reduction capabilities.

10. The method according to claim 1, characterized in that The first terminal device is a first type of enhanced reduced capability terminal device, and the first type of enhanced reduced capability terminal device is an enhanced reduced capability terminal device with a peak rate equal to 10 Mbps and supporting a 20 MHz bandwidth; The system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The system information indicates that the terminal device supports reduced capabilities and does not support enhanced reduced capabilities.

11. The method according to claim 1, characterized in that: The first terminal device is a terminal device with reduced capabilities; and the system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The frequency band information of the cell under the network device is not greater than 20 MHz, and the system information indicates that the terminal device with reduced capability is not supported.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: In the case of determining that the cell under the network device can be accessed to perform the emergency service, sending second information indicating the type of enhanced reduced capability terminal device to which the first terminal device belongs; Among them, the types of enhanced reduction capability terminal devices include first type of enhanced reduction capability terminal devices and second type of enhanced reduction capability terminal devices. The first type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting 20MHz bandwidth. The second type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting less than 20MHz bandwidth.

13. The method according to claim 12, characterized in that The second information includes the type of enhanced reduced-capability terminal device to which the first terminal device belongs; or, The second information includes capability information of the first terminal device, where the capability information is used to indicate the type of enhanced reduced-capability terminal device to which the first terminal device belongs.

14. The method according to any one of claims 1 to 13, characterized in that: The determining, according to the system information, whether it is possible to access a cell under the network device to perform an emergency service includes: Determine whether it is possible to access the cell under the network device to perform the emergency service within the duration of the emergency service according to the system information.

15. A communication method, characterized in that: Applied to a network device, the method comprises: Determine system information, the system information indicating whether the cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, the system information also including first information indicating whether the cell under the network device supports the terminal devices with reduced capabilities to perform emergency services in a prohibited access state; The system information is sent.

16. The method according to claim 15, characterized in that The system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The system information does not include same-frequency reselection indication information corresponding to the terminal device with reduced capability.

17. The method according to claim 15, characterized in that The system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the first indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 1 antenna channel.

18. The method according to claim 15, characterized in that The system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and the second indication information included in the system information indicates that the cell under the network device is a prohibited access cell for the terminal device with reduced capability of 2 antenna channels.

19. The method according to claim 15, characterized in that The system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The system information includes the same-frequency reselection indication information corresponding to the terminal device with reduced capability, and does not include the third indication information, where the third indication information is the indication information for allowing the terminal device with reduced capability in half-duplex to access the cell.

20. The method according to claim 15, characterized in that The system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The frequency band information of the cell under the network device is not greater than 5 MHz, and the system information indicates a terminal device that does not support enhanced reduction capabilities.

21. The method according to claim 15, characterized in that The system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The system information indicates that the terminal device supports reduced capabilities and does not support enhanced reduced capabilities.

22. The method according to claim 15, characterized in that The system information indicates that a cell under the network device is a prohibited access cell for terminal devices with reduced capabilities, including: The frequency band information of the cell under the network device is not greater than 20 MHz, and the system information indicates that the terminal device with reduced capability is not supported.

23. The method according to any one of claims 15 to 22, characterized in that: The method further comprises: receiving second information indicating a type of enhanced reduced-capability terminal device to which the first terminal device belongs; Among them, the types of enhanced reduction capability terminal devices include first type of enhanced reduction capability terminal devices and second type of enhanced reduction capability terminal devices. The first type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting 20MHz bandwidth. The second type of enhanced reduction capability terminal devices are enhanced reduction capability terminal devices with a peak rate equal to 10Mbps and supporting less than 20MHz bandwidth.

24. The method according to claim 23, characterized in that The second information includes the type of enhanced reduced-capability terminal device to which the first terminal device belongs; or, The second information includes capability information of the first terminal device, where the capability information is used to indicate the type of enhanced reduced-capability terminal device to which the first terminal device belongs.

25. A communication device, comprising a unit or module for executing the method according to any one of claims 1 to 14, or comprising a unit or module for executing the method according to any one of claims 15 to 24.

26. A communication device, characterized in that: The method comprises a processor, wherein the processor is used to implement the method according to any one of claims 1 to 14, or to implement the method according to any one of claims 15 to 24.

27. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 14 is implemented, or the method according to any one of claims 15 to 24 is implemented.

28. A computer program product, characterized in that The method comprises a computer program code, and when the computer program code is executed on a computer, the method according to any one of claims 1 to 14 is implemented, or the method according to any one of claims 15 to 24 is implemented.

29. A communication system, characterized in that: It comprises a communication device for implementing the method described in any one of claims 1 to 14, and a communication device for implementing the method described in any one of claims 15 to 24.

Images