Communication method and apparatus

Abstract

Embodiments of the present application relate to the technical field of communications, and discloses a communication method and apparatus, used for improving the service continuity of RedCap terminals. The method comprises: determining, in an idle state, whether at least one NR neighbor cell of a currently camped-on cell supports RedCap or eRedCap; and when none of the at least one NR neighbor cell supports RedCap or eRedCap, reporting, in a connected state, to a first network device a first indication indicating that RedCap or eRedCap is not supported, wherein the first network device is a network device corresponding to the currently camped-on cell. In the present application, when none of NR neighbor cells of the currently camped‑on cell supports RedCap, a RedCap terminal will report a non-RedCap capability to a network device corresponding to the currently camped-on cell, so that the RedCap terminal can switch, as a non‑RedCap terminal, to an NR cell that does not support RedCap, and works normally as a non-RedCap terminal in the NR cell that does not support RedCap. Thus, the RedCap terminal is prevented from switching as a RedCap terminal to an NR cell that does not support RedCap, which would cause service interruption due to the inability to operate normally, thereby improving the service continuity of the RedCap terminal.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411554807.X, filed on November 1, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to communication methods and apparatus. Background Technology

[0003] Reduced capability (RedCap) is a fifth-generation mobile communication technology (5G) defined by the 3rd generation partnership project (3GPP) standardization organization, also known as lightweight 5G.

[0004] RedCap reduces the capabilities of a terminal while ensuring application requirements and performance. This is achieved by reducing bandwidth, the number of transmit and receive antennas, lowering the data rate, adjusting the modulation method, and introducing half-duplex mode. This reduces the complexity of the terminal and aims to reduce terminal costs, power consumption, and extend its lifespan. RedCap is more conducive to the popularization and commercialization of 5G networks.

[0005] In related technologies, RedCap terminals can only work normally in New Radio (NR) cells that support RedCap or in non-NR cells (such as Long Term Evolution (LTE) cells). When a RedCap terminal moves from a non-NR cell to an NR cell, it may switch to an NR cell that does not support RedCap, which may cause the RedCap terminal to malfunction and result in service interruption. Summary of the Invention

[0006] This application provides a communication method and apparatus for improving the service continuity of RedCap terminals. To achieve the above objective, this application adopts the following technical solution:

[0007] In a first aspect, embodiments of this application provide a communication method, the method comprising: determining, in an idle state, whether at least one NR neighboring cell of the currently camped cell supports RedCap or eRedCap; and, in a connected state, reporting a first indication that RedCap or eRedCap is not supported to a first network device, wherein the first network device is the network device corresponding to the currently camped cell.

[0008] The solution provided in this application embodiment allows a RedCap (eRedCap) terminal to report non-RedCap (non-eRedCap) capabilities to the network device corresponding to the currently camped cell when none of the NR neighboring cells of the current camped cell support RedCap (eRedCap) technology. This enables the RedCap (eRedCap) terminal to switch to an NR cell that does not support RedCap (eRedCap) technology as a non-RedCap (non-eRedCap) terminal and work normally in the NR cell that does not support RedCap (eRedCap) technology. This avoids the RedCap (eRedCap) terminal switching to an NR cell that does not support RedCap (eRedCap) technology as a RedCap (eRedCap) terminal, which would cause service interruption due to inability to work normally. This improves the service continuity of the RedCap (eRedCap) terminal.

[0009] In one possible implementation, the user can switch from the currently active cell to the target cell while in the connected state and report the first instruction to the second network device, which is the network device corresponding to the target cell.

[0010] Understandably, after a RedCap terminal switches to an NR cell that does not support RedCap, the RedCap terminal reports a first instruction to the second network device corresponding to the NR cell that does not support RedCap. This allows the NR cell under the second network device that does not support RedCap to treat the RedCap terminal as a non-RedCap terminal, so that the RedCap terminal can work normally in the NR cell that does not support RedCap as a non-RedCap terminal, thereby ensuring the service continuity of the RedCap terminal.

[0011] In one possible implementation, if at least one of the aforementioned NR neighboring cells supports RedCap or eRedCap, a second indication supporting RedCap or eRedCap is reported to the first network device in the aforementioned connected state; Radio Resource Control (RRC) is rebuilt to access the NR cell that does not support RedCap or eRedCap; and the aforementioned first indication is reported to a third network device, wherein the third network device is the network device corresponding to the aforementioned NR cell.

[0012] Understandably, when a RedCap terminal has a RedCap-enabled neighboring NR cell in its current camping cell, it will report RedCap capabilities to the network device corresponding to that cell, enabling the RedCap terminal to access the RedCap-enabled NR cell. After accessing a RedCap-enabled NR cell, an anomaly may cause RRC (Redirect Reset) reconstruction. In this case, the RedCap terminal can access either a RedCap-enabled or non-RedCap-enabled NR cell. If access to a non-RedCap-enabled NR cell is reconstructed via RRC, the terminal can report non-RedCap capabilities to the third-party network device corresponding to the non-RedCap-enabled NR cell. This allows the third-party network device to treat the RedCap terminal as a non-RedCap terminal, enabling the RedCap terminal to operate normally in the non-RedCap-enabled NR cell, thus ensuring the service continuity of the RedCap terminal.

[0013] In one possible implementation, if an NR cell that does not support RedCap or eRedCap is found during the aforementioned RRC reconstruction process, the user can immediately access the NR cell that does not support RedCap or eRedCap.

[0014] It is understood that, since the RedCap terminal in the solution provided in this application embodiment can work normally in an NR cell that does not support RedCap in the working mode of a non-RedCap terminal, the RedCap terminal can not be barred from searching for and accessing an NR cell that does not support RedCap during the RRC reconstruction process. Instead, when an NR cell that does not support RedCap is found, it can immediately access the NR cell that does not support RedCap to quickly restore NR cell access, thereby improving the continuity of terminal services.

[0015] In one possible implementation, a system message is received in the aforementioned idle state; based on the aforementioned system message, it is determined whether the at least one NR neighbor cell supports RedCap or eRedCap.

[0016] Understandably, system information blocks (SIBs) play a crucial role in communication systems, ensuring that terminals can correctly access the network and providing necessary system configuration information, thereby guaranteeing the normal operation of the terminals and the realization of communication functions. Devices within a cell can receive system information to determine whether neighboring cells support RedCap.

[0017] Secondly, embodiments of this application provide a communication device, which may be a terminal, a module applied to the terminal (such as a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the terminal's functions. The device includes a processing unit and a transceiver unit. The processing unit is configured to determine, in an idle state, whether at least one NR neighboring cell of the currently camped cell supports RedCap or eRedCap. The transceiver unit is configured to, in a connected state, report a first indication that RedCap or eRedCap is not supported to a first network device if none of the at least one NR neighboring cell supports RedCap or eRedCap. The first network device is the network device corresponding to the currently camped cell.

[0018] In one possible implementation, the transceiver unit is further configured to: switch from the currently camped cell to the target cell in the connected state, and report the first instruction to the second network device, wherein the second network device is the network device corresponding to the target cell.

[0019] In one possible implementation, the transceiver unit is further configured to: report a second indication of supporting RedCap or eRedCap to the first network device in the connected state when there is a neighboring cell supporting RedCap or eRedCap in at least one of the NR neighboring cells; perform RRC reconstruction to access the NR cell that does not support RedCap or eRedCap; and report the first indication to a third network device, wherein the third network device is the network device corresponding to the NR cell.

[0020] In one possible implementation, the transceiver unit is specifically used to: immediately access the NR cell when the NR cell is found during the RRC reconstruction process.

[0021] In one possible implementation, the processing unit is specifically used to: receive a system message in the idle state; and determine, based on the system message, whether the at least one NR neighbor cell supports RedCap or eRedCap.

[0022] Thirdly, embodiments of this application also provide a communication device, which includes: at least one processor, which, when the at least one processor executes program code or instructions, implements the method described in the first aspect or any possible implementation thereof.

[0023] Alternatively, the communication device may be a chip or a chip system.

[0024] Optionally, the device may further include at least one memory for storing the program code or instructions.

[0025] Fourthly, embodiments of this application also provide a chip, including: an input interface, an output interface, and at least one processor. Optionally, the chip further includes a memory. The at least one processor is used to execute code in the memory, and when the at least one processor executes the code, the chip implements the method described in the first aspect or any possible implementation thereof.

[0026] Alternatively, the chip described above can also be an integrated circuit.

[0027] Fifthly, embodiments of this application also provide a computer-readable storage medium for storing a computer program, the computer program including methods for implementing the first aspect or any possible implementation thereof.

[0028] Sixthly, embodiments of this application also provide a computer program product containing instructions that, when run on a computer, cause the computer to implement the method described in the first aspect or any possible implementation thereof.

[0029] The communication device, computer storage medium, computer program product, and chip provided in this embodiment are all used to execute the communication method provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the communication method provided above, and will not be repeated here. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0031] Figure 1 is a schematic diagram of a communication system provided in an embodiment of this application;

[0032] Figure 2 is a schematic diagram of the structure of a network device provided in an embodiment of this application;

[0033] Figure 3 is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0034] Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0035] Figure 5 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0036] Figure 6 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0037] Figure 7 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0038] Figure 8 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0039] Figure 9 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0040] Figure 10 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0041] Figure 11 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0042] Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

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

[0044] Figure 14 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0045] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of the embodiments of this application.

[0046] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0047] The terms "first" and "second," etc., in the specification and drawings of the embodiments of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

[0048] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of the embodiments of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0049] It should be noted that in the description of the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

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

[0051] Figure 1 shows a schematic diagram of the architecture of a communication system 100 provided in an embodiment of this application. In Figure 1, the communication system 100 may include one or more network devices 200 (only one is shown in the figure) and one or more terminals 300 that can communicate with the network device 101. Figure 1 is only a schematic diagram and does not constitute a limitation on the applicable scenarios of the technical solutions provided in this application.

[0052] For example, the terminal 300 described above may be a RedCap terminal or an eRedCap terminal.

[0053] Network device 200 is located on the network side of the aforementioned communication system, used to help terminals achieve wireless access, and is a device or chip or chip system that can be installed in the device, possessing wireless transceiver capabilities. This network device includes, but is not limited to: access network equipment, access network nodes, radio access network (RAN) nodes, RAN entities or access nodes, base stations, evolved NodeBs (eNodeBs), access points (APs), transmission reception points (TRPs or transmission points (TPs), next-generation NodeBs (gNBs), base stations in future mobile communication systems, or access points (APs) in wireless fidelity (Wi-Fi) systems. The network device can be a macro base station, micro base station or indoor station, relay node or donor node, an open radio access network (ORAN), or a wireless controller in a centralized radio access network (CRAN) scenario. Network equipment can also be one or a group of antenna panels (including multiple antenna panels) in a 5th generation (5G) base station. Alternatively, it can be a network node constituting a gNB, TRP, TP, or transmission measurement function (TMF), such as a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), a radio unit (RU), or a roadside unit (RSU) with base station functionality. Optionally, network equipment can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the network equipment in vehicle-to-everything (V2X) technology can be an RSU. Optionally, network equipment can also be a control unit in autonomous driving, a central controller in a smart factory / smart home, or a handheld or automatic control remote sensor for flight equipment. Optionally, network equipment can also be a central control or control panel, such as a drone controller or a control unit in industrial control.All or part of the functions of the network device in this application can also be implemented through software functions running on hardware, or through 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 capable of implementing all or part of the functions of a network device.

[0054] The form of the network device is not limited in the embodiments of this application. The device used to implement the function of the network device can be the network device itself, or it can be a device that supports the network device in implementing the function, such as a chip system. The device can be installed in the network device or used in conjunction with the network device.

[0055] Terminal 300 is a device, equipment, module, chip, or chip system with transceiver functions. This terminal may also be referred to as user equipment (UE), terminal equipment, access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. The terminals in the embodiments of this application can be mobile phones, cellular phones, smartphones, tablets, mice, remote controls, styluses, set-top boxes, routers, cameras, screens, smart screens, wireless data cards, personal digital assistant computers (PDAs), wireless modems, handsets, laptop computers, smartwatches, smart bracelets, wireless headphones, electronic whiteboards, machine-type communication (MTC) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, smart home devices (e.g., refrigerators, televisions, air conditioners, washing machines, rice cookers, table lamps, electricity meters, etc.), smart robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, and transportation security. Wireless terminals in various applications include those related to safety, smart cities, smart homes, in-vehicle terminals, in-vehicle screens, in-vehicle audio systems, car keys, roadside units (RSUs) with terminal functions, and flying equipment (e.g., intelligent robots, hot air balloons, drones, airplanes). The terminal in this application can also be an in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit integrated into a vehicle as one or more components or units. The terminal can also be other devices with terminal functions; for example, it can be a device that functions as a terminal in device-to-device (D2D) communication.

[0056] The embodiments of this application do not limit the device form of the terminal. The device used to implement the functions of the terminal can be the terminal itself; it can also be a device that supports the terminal in implementing the functions, such as a chip system. The device can be installed in the terminal or used in conjunction with the terminal. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices.

[0057] It should be noted that the solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.

[0058] It should be noted that the communication system 100 shown in Figure 1 is only one implementation of the embodiment of this application. In actual applications, the communication system 100 may include more or fewer components, which is not limited here.

[0059] Referring to FIG2, FIG2 illustrates a network device 200 provided in some embodiments of this application. As shown in FIG2, the network device 200 may include: one or more processors 201, memory 202, communication interface 203, transmitter 205, receiver 206, coupler 207, and antenna 208. These components may be connected via bus 204 or other means; FIG2 illustrates a connection via bus as an example. Wherein:

[0060] The communication interface 203 can be used by the network device 200 to communicate with other communication devices, such as terminals or other network devices. Specifically, the communication interface 203 can be an LTE or 4G communication interface, or a 5G or future new radio interface communication interface. Not limited to wireless communication interfaces, the network device 200 can also be configured with a wired communication interface 203 to support wired communication; for example, the backhaul link between one network device 200 and other network devices 200 can be a wired communication connection.

[0061] Transmitter 205 can be used to process the signal output by processor 201, such as signal modulation. Receiver 206 can be used to process the mobile communication signal received by antenna 208, such as signal demodulation. In some embodiments of this application, transmitter 205 and receiver 206 can be considered as a wireless modem. In network device 200, the number of transmitters 205 and receivers 206 can be one or more. Antenna 208 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line. Coupler 207 can be used to split the mobile communication signal into multiple paths and distribute them to multiple receivers 206.

[0062] Memory 202 is coupled to processor 201 and is used to store various software programs and / or sets of instructions. Specifically, memory 202 may include high-speed random access memory and may also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 202 may store an operating system (hereinafter referred to as the system), such as uCOS, VxWorks, RTLinux, or other embedded operating systems. Memory 202 may also store network communication programs that can be used to communicate with one or more additional devices, one or more terminals, or one or more network devices.

[0063] Processor 201 can be used for radio channel management, call and communication link establishment and teardown, and cell handover control for users within the control area. Specifically, processor 201 may include: an administration / communication module (AM / CM) (for the center of voice and information switching), a basic module (BM) (for call processing, signaling processing, radio resource management, radio link management and circuit maintenance), a transcoder and sub-multiplexer (TCSM) (for multiplexing, demultiplexing and code conversion functions), etc.

[0064] In this embodiment, the processor 201 can be used to read and execute computer-readable instructions. Specifically, the processor 201 can be used to call a program stored in the memory 202, such as the implementation program of the resource allocation method provided in one or more embodiments of this application on the network device 200 side, and execute the instructions contained in the program.

[0065] It should be noted that the network device 200 shown in Figure 2 is only one implementation of the embodiment of this application. In actual applications, the network device 200 may include more or fewer components, which is not limited here.

[0066] Referring to Figure 3, Figure 3 illustrates a terminal 300 provided in some embodiments of this application. As shown in Figure 3, the terminal 300 may include: one or more processors 301, a memory 302, a communication interface 303, a receiver 305, a transmitter 306, a coupler 307, an antenna 308, a user interface 309, and input / output modules (including an audio input / output module 310, a key input module 311, and a display 312, etc.). These components can be connected via a bus 304 or other means; Figure 3 illustrates a connection via a bus as an example.

[0067] The communication interface 303 can be used by the terminal 300 to communicate with other communication devices, such as network devices. Specifically, the communication interface 303 can be a Long Term Evolution (LTE) or 4G communication interface, or a 5G or future New Radio (NR) communication interface. Not limited to wireless communication interfaces, the terminal 300 can also be configured with a wired communication interface 303, such as a local access network (LAN) interface.

[0068] Transmitter 306 can be used to process the signal output by processor 301, such as signal modulation. Receiver 305 can be used to process the mobile communication signal received by antenna 308, such as signal demodulation. In some embodiments of this application, transmitter 306 and receiver 305 can be considered as a wireless modem. In terminal 300, the number of transmitter 306 and receiver 305 can be one or more. Antenna 308 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line. Coupler 307 is used to split the mobile communication signal received by antenna 308 into multiple paths and distribute them to multiple receivers 305.

[0069] In addition to the transmitter 306 and receiver 305 shown in Figure 3, the terminal 300 may also include other communication components, such as a global positioning system (GPS) module, a Bluetooth module, and a wireless fidelity (Wi-Fi) module. Not limited to the wireless communication signals described above, the terminal 300 may also support other wireless communication signals, such as satellite signals, shortwave signals, etc. Not limited to wireless communication, the terminal 300 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.

[0070] The aforementioned input / output modules can be used to realize the interaction between the terminal 300 and the user / external environment, and may mainly include an audio input / output module 310, a key input module 311, and a display 312. Specifically, the aforementioned input / output modules may also include: a camera, a touch screen, and sensors, etc. All of the aforementioned input / output modules communicate with the processor 301 through the user interface 309.

[0071] Memory 302 is coupled to processor 301 and is used to store various software programs and / or multiple sets of instructions. Specifically, memory 302 may include high-speed random access memory and may also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 302 may store an operating system (hereinafter referred to as the system), such as embedded operating systems like Android, iOS, Windows, or Linux. Memory 302 may also store network communication programs, which can be used to communicate with one or more additional devices, one or more terminals, or one or more network devices. Memory 302 may also store user interface programs, which can realistically display the content of the application through a graphical user interface and receive user control operations on the application through input controls such as menus, dialog boxes, and buttons.

[0072] In some embodiments of this application, memory 302 may be used to store the implementation program of the resource allocation method provided in one or more embodiments of this application on the terminal 300 side. For the implementation of the resource allocation method provided in one or more embodiments of this application, please refer to the following embodiments.

[0073] The processor 301 can be used to read and execute computer-readable instructions. Specifically, the processor 301 can be used to call a program stored in the memory 312, such as the implementation program of the resource allocation method provided in one or more embodiments of this application on the terminal 300 side, and execute the instructions contained in the program.

[0074] It should be noted that the terminal 300 shown in Figure 3 is only one implementation of the embodiment of this application. In actual applications, the terminal 300 may include more or fewer components, which is not limited here.

[0075] Figure 4 illustrates a communication method provided in an embodiment of this application. This method can be executed by the terminal 300 in the communication system 100 described above. As shown in Figure 4, the method includes:

[0076] S401. In idle state, determine whether at least one NR neighbor cell of the currently camped cell supports RedCap or eRedCap.

[0077] The currently camped cell can be an NR cell or a non-NR cell (such as an LTE cell).

[0078] In one possible implementation, the terminal can receive system messages and, in the idle state, determine whether at least one NR neighbor cell of the currently camped cell supports RedCap or eRedCap based on the system messages.

[0079] For example, the terminal can receive SIB4 or SIB24 in the idle state; and determine whether the at least one NR neighbor cell supports RedCap based on the aforementioned SIB4 or SIB24.

[0080] For example, after a RedCap terminal camps in a cell, it can receive SIB4 sent by the network device of the currently camped cell in the idle state and determine whether the cell under each frequency point supports RedCap and the correspondence between frequency points and cells based on whether the inter-frequency measurement configuration of each frequency point in the SIB4 carries a specific field (such as redCapAccessAllowed-r17), and determine whether the NR neighboring cells of the currently camped cell support RedCap.

[0081] The correspondence between frequency points and cells can be a correspondence between frequency point identifiers and cell identifiers, such as the correspondence between a frequency point unique code (Identity Document, ID) and a cell ID.

[0082] Understandably, system messages play a crucial role in communication systems, ensuring that terminals can correctly access the network and providing necessary system configuration information, thereby guaranteeing the normal operation of the terminals and the realization of communication functions. Devices within a cell can receive system messages to determine whether neighboring cells support RedCap.

[0083] For example, the eRedCap terminal can receive SIB4 or SIB24 in the idle state; and determine whether the at least one NR neighbor cell supports eRedCap based on the aforementioned SIB4 or SIB24.

[0084] For example, after the eRedCap terminal is camped in a cell, it can receive the SIB4 sent by the network device of the currently camped cell in the idle state and determine whether the cell under each frequency point supports eRedCap and the correspondence between frequency points and cells based on whether the inter-frequency measurement configuration of each frequency point in the SIB4 carries a specific field, and determine whether the NR neighboring cells of the currently camped cell support eRedCap.

[0085] Understandably, system messages play a crucial role in communication systems, ensuring that terminals can correctly access the network and providing necessary system configuration information, thereby guaranteeing the normal operation of the terminals and the realization of communication functions. Devices within a cell can receive system messages to determine whether neighboring cells support eRedCap.

[0086] In one possible implementation, the system can receive indication information sent by other devices in the idle state and determine whether at least one NR neighbor cell of the currently camped cell supports RedCap or eRedCap based on the indication information.

[0087] The indication information is used to indicate whether at least one NR neighbor cell of the currently residing cell supports RedCap or eRedCap.

[0088] For example, a RedCap terminal can receive indication information sent by a server or other terminals in the currently camped cell, and determine whether at least one NR neighbor cell of the currently camped cell supports RedCap based on the indication information.

[0089] For example, a RedCap terminal can receive indication information sent by other RedCap terminals in the currently camped cell, and determine whether at least one NR neighbor cell of the currently camped cell supports RedCap based on the indication information.

[0090] For example, an eRedCap terminal can receive indication information sent by a server or other terminals in the currently camped cell, and determine whether at least one NR neighbor cell of the currently camped cell supports eRedCap based on the indication information.

[0091] For example, an eRedCap terminal can receive indication information sent by other eRedCap terminals in the currently camped cell, and determine whether at least one NR neighbor cell of the currently camped cell supports eRedCap based on the indication information.

[0092] S402. If each of the at least one NR neighboring cells of the currently camped cell does not support RedCap or eRedCap, report a first indication that RedCap or eRedCap is not supported to the first network device in connected state.

[0093] The first network device mentioned above is the network device corresponding to the currently occupied cell.

[0094] For example, if RedCap is not supported in each of at least one of the NR neighboring cells of the currently camped cell, the RedCap terminal may report a first indication that RedCap is not supported to the first network device in connected state.

[0095] As shown in Figure 5, assuming the RedCap terminal is currently camped in LTE cell 1, and the neighboring cells of LTE cell 1 include NR cell 1 and NR cell 2, neither NR cell 1 nor NR cell 2 supports RedCap. The RedCap terminal receives a system message sent by the evolved node B (eNB) 1 corresponding to LTE cell 1 and determines, based on the system message, that each of the NR neighboring cells of LTE cell 1 does not support RedCap. The RedCap terminal can then report a first indication of RedCap non-support to eNB 1.

[0096] The solution provided in this application embodiment allows a RedCap terminal to report non-RedCap capabilities to the network device corresponding to the currently camped cell when none of the NR neighboring cells of the current camped cell support RedCap. This enables the RedCap terminal to switch to an NR cell that does not support RedCap as a non-RedCap terminal and work normally in the NR cell that does not support RedCap, thereby avoiding the RedCap terminal being unable to work normally and causing service interruption when switching to an NR cell that does not support RedCap as a RedCap terminal, thus improving the service continuity of the RedCap terminal.

[0097] For example, if each of the at least one NR neighboring cells of the currently camped cell does not support eRedCap, the eRedCap terminal may report a first indication that eRedCap is not supported to the first network device in connected state.

[0098] The solution provided in this application embodiment allows an eRedCap terminal to report non-eRedCap capabilities to the network device corresponding to the currently camped cell when none of the NR neighboring cells of the current camped cell support eRedCap. This enables the eRedCap terminal to switch to an NR cell that does not support eRedCap as a non-eRedCap terminal and work normally in the NR cell that does not support eRedCap, thereby avoiding the eRedCap terminal being unable to work normally and causing service interruption when switching to an NR cell that does not support eRedCap as an eRedCap terminal, thus improving the service continuity of the eRedCap terminal.

[0099] In one possible implementation, the user can switch from the currently active cell to the target cell while in the connected state and report the first instruction to the second network device, which is the network device corresponding to the target cell.

[0100] For example, a RedCap terminal can switch from its current camped cell to a target cell that does not support RedCap while in connected mode. After switching to a target cell that does not support RedCap, the RedCap terminal can report a first indication that RedCap is not supported to the second network device corresponding to the target cell.

[0101] For example, after receiving a first indication from a RedCap terminal that RedCap is not supported, the first network device can, based on the first indication, cause the RedCap terminal to switch from its current cell to a target cell that does not support RedCap while in connected mode. After switching to the target cell that does not support RedCap, the RedCap terminal can report the first indication that RedCap is not supported to the second network device corresponding to the target cell.

[0102] As shown in Figure 5, after receiving the first indication from the RedCap terminal that RedCap is not supported, eNB1 can send a handover indication to the RedCap terminal to instruct it to switch to NR cell 1, which does not support RedCap. The RedCap terminal responds to the handover indication and switches from LTE cell 1 to NR cell 1, which does not support RedCap. After switching to NR cell 1, the network device gNB1 corresponding to NR cell 1 sends a capability query request to the RedCap terminal. The RedCap terminal responds to the capability query request and reports the first indication that RedCap is not supported to gNB1.

[0103] For example, after receiving a first indication from a RedCap terminal that RedCap is not supported, the first network device can redirect the RedCap terminal from its current cell to a target cell that does not support RedCap while in connected mode. After being redirected to the target cell, the RedCap terminal can report the first indication that RedCap is not supported to the second network device corresponding to the target cell.

[0104] Understandably, after a RedCap terminal switches to an NR cell that does not support RedCap, the RedCap terminal reports a first instruction to the second network device corresponding to the NR cell that does not support RedCap. This allows the NR cell under the second network device that does not support RedCap to treat the RedCap terminal as a non-RedCap terminal, so that the RedCap terminal can work normally in the NR cell that does not support RedCap as a non-RedCap terminal, thereby ensuring the service continuity of the RedCap terminal.

[0105] For example, an eRedCap terminal can switch from its current camped cell to a target cell that does not support eRedCap while in connected mode. After switching to a target cell that does not support eRedCap, the eRedCap terminal can report a first indication that eRedCap is not supported to the second network device corresponding to the target cell.

[0106] For example, after receiving a first indication from the eRedCap terminal that eRedCap is not supported, the first network device can, based on the first indication, cause the eRedCap terminal to switch from its current camped cell to a target cell that does not support eRedCap while in connected mode. After switching to the target cell that does not support eRedCap, the eRedCap terminal can report the first indication that eRedCap is not supported to the second network device corresponding to the target cell.

[0107] For example, after receiving a first indication from the eRedCap terminal that eRedCap is not supported, the first network device can redirect the eRedCap terminal from its current cell to a target cell that does not support eRedCap in connected mode, based on the first indication. After being redirected to the target cell that does not support eRedCap, the eRedCap terminal can report the first indication that eRedCap is not supported to the second network device corresponding to the target cell.

[0108] Understandably, after an eRedCap terminal switches to an NR cell that does not support eRedCap, the eRedCap terminal reports a first instruction to the second network device corresponding to the NR cell that does not support eRedCap. This allows the NR cell under the second network device that does not support eRedCap to treat the eRedCap terminal as a non-eRedCap terminal, so that the eRedCap terminal can work normally in the NR cell that does not support eRedCap as a non-eRedCap terminal, thereby ensuring the service continuity of the eRedCap terminal.

[0109] In one possible implementation, the first network device and the second network device can be the same network device.

[0110] Accordingly, if the first network device and the second network device are the same network device, the currently camped cell and the aforementioned target cell can be different cells under the same network device.

[0111] In one possible implementation, when switching from a target cell that does not support RedCap or eRedCap to a new camping cell, a first indication that RedCap or eRedCap is not supported can be reported to the network device corresponding to the new camping cell.

[0112] The new host cell can be an NR cell or a non-NR cell. The new host cell can be the same cell as the currently host cell or a cell under the same network device.

[0113] For example, when a RedCap terminal switches from a target cell that does not support RedCap to a new camping cell, it can report a first indication that RedCap is not supported to the network device corresponding to the new camping cell.

[0114] For example, a RedCap terminal can report a first indication that RedCap is not supported to the first network device when it returns to the currently camped cell from a target cell that does not support RedCap.

[0115] Referring to Figure 5, as shown in Figure 6, after the RedCap terminal switches back to LTE cell 1 from NR cell 1 which does not support RedCap, eNB1 sends a capability query request to the RedCap terminal. In response to the capability query request, the RedCap terminal reports the first indication that it does not support RedCap to eNB1.

[0116] Referring to Figure 5, as shown in Figure 7, after the RedCap terminal switches from NR cell 1, which does not support RedCap, to LTE cell 2, the network device eNB2 corresponding to LTE cell 2 sends a capability query request to the RedCap terminal. In response to the capability query request, the RedCap terminal reports a first indication to eNB2 that it does not support RedCap.

[0117] As another example, when an eRedCap terminal switches from a target cell that does not support eRedCap to a new camping cell, it can report a first indication that eRedCap is not supported to the network device corresponding to the new camping cell.

[0118] For example, if an eRedCap terminal returns to the currently camped cell from a target cell that does not support eRedCap, it can report a first indication to the first network device that eRedCap is not supported.

[0119] In one possible implementation, if at least one of the NR neighboring cells of the currently camped cell supports RedCap or eRedCap, a second indication supporting RedCap or eRedCap can be reported to the first network device in the aforementioned connected state.

[0120] For example, if at least one of the NR neighboring cells of the currently camped cell supports RedCap, the RedCap terminal can report a second indication of RedCap support to the first network device in connected state.

[0121] As shown in Figure 8, assuming the RedCap terminal is currently camped in LTE cell 1, and the neighboring cells of LTE cell 1 include NR cell 1 and NR cell 2, NR cell 1 supports RedCap, while NR cell 2 does not. The RedCap terminal receives a system message sent by eNB1 and determines, based on the system message, that there is a neighboring cell among the NR neighboring cells of LTE cell 1 that supports RedCap. The RedCap terminal can then report a second indication of RedCap support to eNB1.

[0122] As another example, if at least one of the NR neighboring cells of the currently camped cell supports eRedCap, the eRedCap terminal can report a second indication of eRedCap support to the first network device in connected state.

[0123] In one possible implementation, the user can switch from the currently active cell to the target cell while in the connected state and report the second instruction to the second network device, which is the network device corresponding to the target cell.

[0124] For example, a RedCap terminal can switch from its current camped cell to a target cell that supports RedCap while in connected mode. After switching to the target cell that supports RedCap, the RedCap terminal can report a second indication of RedCap support to the second network device corresponding to the target cell.

[0125] For example, after receiving a second indication of RedCap support reported by a RedCap terminal, the first network device can, based on the second indication, switch the RedCap terminal from its current camped cell to a target cell that supports RedCap while in connected mode. After switching to the target cell that supports RedCap, the RedCap terminal can report a second indication of RedCap support to the second network device corresponding to the target cell.

[0126] As shown in Figure 8, after receiving the second indication of RedCap support reported by the RedCap terminal, eNB1 can send a handover indication to the RedCap terminal to instruct it to switch to NR cell 1, which supports RedCap. The RedCap terminal responds to the handover indication and switches from LTE cell 1 to NR cell 1, which supports RedCap. After switching to NR cell 1, the network device gNB1 corresponding to NR cell 1 sends a capability query request to the RedCap terminal. The RedCap terminal responds to the capability query request and reports the second indication of RedCap support to gNB1.

[0127] For example, after receiving a second indication of RedCap support reported by a RedCap terminal, the first network device can redirect the RedCap terminal from its current camped cell to a target cell that supports RedCap in connected mode, based on the second indication. After redirecting to the target cell that supports RedCap, the RedCap terminal can report a second indication of RedCap support to the second network device corresponding to the target cell.

[0128] For example, an eRedCap terminal can switch from its currently camped cell to a target cell that supports eRedCap while in connected mode. After switching to a target cell that supports eRedCap, the eRedCap terminal can report a second indication of eRedCap support to the second network device corresponding to the target cell.

[0129] For example, after receiving a second indication of eRedCap support from the eRedCap terminal, the first network device can, based on the second indication, switch the eRedCap terminal from its current camped cell to a target cell that supports eRedCap while in connected mode. After switching to the target cell that supports eRedCap, the eRedCap terminal can report a second indication of eRedCap support to the second network device corresponding to the target cell.

[0130] For example, after receiving a second indication of eRedCap support from an eRedCap terminal, the first network device can redirect the eRedCap terminal from its current cell to a target cell that supports eRedCap in connected mode, based on the second indication. After redirecting to the target cell that supports eRedCap, the eRedCap terminal can report a second indication of eRedCap support to the second network device corresponding to the target cell.

[0131] In one possible implementation, RRC reconstruction can be performed to access an NR cell that does not support RedCap or eRedCap; the first instruction mentioned above can be reported to a third network device, which is the network device corresponding to the NR cell.

[0132] For example, if an RRC reconstruction occurs after a RedCap terminal switches or redirects to an NR neighbor cell that supports RedCap, the RedCap terminal can perform an RRC reconstruction to access an NR cell that does not support RedCap, and after accessing the NR cell that does not support RedCap, report a first indication that RedCap is not supported to the third network device corresponding to the NR cell that does not support RedCap.

[0133] For example, if an RRC rebuild occurs after a RedCap terminal switches to a target cell that supports RedCap, the RedCap terminal can send an RRC setup request to the third network device corresponding to the NR cell that does not support RedCap and receive an RRC setup request response from the third network device. After receiving the RRC setup request response, the RedCap terminal sends an RRC setup complete message to the third network device to access the NR cell that does not support RedCap. After receiving a capability query request from the third network device, the RedCap terminal reports a first indication that RedCap is not supported to the third network device.

[0134] Referring to Figure 8 and as shown in Figure 9, after the RedCap terminal performs RRC reconstruction in NR cell 1 that supports RedCap to access NR cell 2 that does not support RedCap, the network device gNB2 corresponding to NR cell 2 sends a capability query request to the RedCap terminal. The RedCap terminal responds to the capability query request and reports the first indication that it does not support RedCap to gNB2.

[0135] For example, if an RRC reconstruction occurs after a RedCap terminal is redirected to a target cell that supports RedCap, the RedCap terminal can send an RRC establishment request to the third network device corresponding to the NR cell that does not support RedCap and receive an RRC establishment request response from the third network device. After receiving the RRC establishment request response, the RedCap terminal sends an RRC establishment completion message to the third network device to access the NR cell that does not support RedCap. After receiving a capability query request from the third network device, the RedCap terminal reports a first indication that RedCap is not supported to the third network device.

[0136] Understandably, when a RedCap terminal has a RedCap-enabled neighboring NR cell in its current camping cell, it will report RedCap capabilities to the network device corresponding to that cell, enabling the RedCap terminal to access the RedCap-enabled NR cell. After accessing a RedCap-enabled NR cell, an anomaly may cause RRC (Redirect Reset) reconstruction. In this case, the RedCap terminal can access either a RedCap-enabled or non-RedCap-enabled NR cell. If access to a non-RedCap-enabled NR cell is reconstructed via RRC, the terminal can report non-RedCap capabilities to the third-party network device corresponding to the non-RedCap-enabled NR cell. This allows the third-party network device to treat the RedCap terminal as a non-RedCap terminal, enabling the RedCap terminal to operate normally in the non-RedCap-enabled NR cell, thus ensuring the service continuity of the RedCap terminal.

[0137] For example, if an RRC reconstruction occurs after an eRedCap terminal switches or redirects to an NR neighbor cell that supports eRedCap, the eRedCap terminal can perform an RRC reconstruction to access an NR cell that does not support eRedCap. After accessing the NR cell that does not support eRedCap, the terminal reports a first indication that eRedCap is not supported to the third network device corresponding to the NR cell that does not support eRedCap.

[0138] For example, if an RRC reconstruction occurs after an eRedCap terminal switches to a target cell that supports eRedCap, the eRedCap terminal can send an RRC establishment request to the third network device corresponding to the NR cell that does not support eRedCap and receive an RRC establishment request response from the third network device. After receiving the RRC establishment request response, the eRedCap terminal sends an RRC establishment completion message to the third network device to access the NR cell that does not support eRedCap. After receiving a capability query request from the third network device, the eRedCap terminal reports a first indication that it does not support eRedCap to the third network device.

[0139] For example, if an RRC reconstruction occurs after an eRedCap terminal is redirected to a target cell that supports eRedCap, the eRedCap terminal can send an RRC establishment request to the third network device corresponding to the NR cell that does not support eRedCap and receive an RRC establishment request response from the third network device. After receiving the RRC establishment request response, the eRedCap terminal sends an RRC establishment completion message to the third network device to access the NR cell that does not support eRedCap. After receiving a capability query request from the third network device, the eRedCap terminal reports a first indication that it does not support eRedCap to the third network device.

[0140] Understandably, when an eRedCap terminal has an eRedCap-enabled neighboring NR cell in its current camped cell, it will report its eRedCap capability to the network device corresponding to that cell, enabling the eRedCap terminal to access the eRedCap-enabled NR cell. After accessing an eRedCap-enabled NR cell, an anomaly may cause RRC (Recurrent Record) reconstruction. In this case, the eRedCap terminal can access either an eRedCap-enabled or non-eRedCap-enabled NR cell. If access to an non-eRedCap-enabled NR cell is reconstructed via RRC, the terminal can report non-eRedCap capability to the third network device corresponding to the non-eRedCap-enabled NR cell. This allows the third network device to treat the eRedCap terminal as a non-eRedCap terminal, enabling the eRedCap terminal to operate normally in the non-eRedCap-enabled NR cell, thus ensuring the service continuity of the eRedCap terminal.

[0141] Among them, the aforementioned RRC establishment completion message includes a direct transmission message, in which the next generation-radio access network-RCU (NG-RAN-RCU) in the direct transmission message is supported, and the aforementioned direct transmission message can be a non-access stratum (NAS).

[0142] In one possible implementation, upon receiving the aforementioned RRC establishment completion message, a direct transmission message is sent.

[0143] For example, when a network device (such as the third network device mentioned above) receives the RRC establishment completion message, it can send a direct transmission message to the access and mobility management function (AMF). After receiving the direct transmission message, the AMF can clear the stored terminal capabilities.

[0144] Understandably, since the AMF clears the saved terminal capabilities after receiving a direct transmission message, the network device needs to send a capability query request to the terminal to re-query the terminal capabilities.

[0145] In one possible implementation, when an NR cell that does not support RedCap or eRedCap is found during the RRC reconstruction process, the NR cell that does not support RedCap or eRedCap is immediately accessed.

[0146] For example, when RedCap finds an NR cell that does not support RedCap during the RRC reconstruction process, it can immediately access the aforementioned NR cell that does not support RedCap.

[0147] For example, when RedCap encounters an NR cell that does not support RedCap during RRC reconstruction, it can choose not to add the NR cell that does not support RedCap to the bar list, but can immediately access the aforementioned NR cell that does not support RedCap.

[0148] It is understood that, since the RedCap terminal in the solution provided in this application embodiment can work normally in an NR cell that does not support RedCap in the working mode of a non-RedCap terminal, the RedCap terminal can not be prohibited from searching for and accessing an NR cell that does not support RedCap during the RRC reconstruction process. Instead, when an NR cell that does not support RedCap is found, it can immediately access the NR cell that does not support RedCap to quickly restore NR cell access, thereby improving the continuity of terminal services.

[0149] For example, when eRedCap finds an NR cell that does not support eRedCap during the RRC reconstruction process, it can immediately access the aforementioned NR cell that does not support eRedCap.

[0150] For example, when eRedCap encounters an NR cell that does not support eRedCap during RRC reconstruction, it can choose not to add the NR cell that does not support eRedCap to the bar list, but can immediately access the aforementioned NR cell that does not support eRedCap.

[0151] It is understood that, since the eRedCap terminal in the solution provided in this application embodiment can work normally in an NR cell that does not support eRedCap in the working mode of a non-eRedCap terminal, the eRedCap terminal can not be prohibited from searching for and accessing NR cells that do not support eRedCap during the RRC reconstruction process. Instead, when an NR cell that does not support eRedCap is found, it can immediately access the NR cell that does not support eRedCap to quickly restore NR cell access, thereby improving the continuity of terminal services.

[0152] In one possible implementation, the first network device and the third network device can be the same network device.

[0153] Accordingly, if the first network device and the third network device are the same network device, the currently camped cell and the aforementioned NR cells that do not support RedCap or eRedCap can be different cells under the same network device.

[0154] In one possible implementation, the second network device and the third network device can be the same network device.

[0155] Accordingly, if the second network device and the third network device are the same network device, the target cell and the NR cell that does not support RedCap or eRedCap can be different cells under the same network device.

[0156] In one possible implementation, when switching from a target cell that supports RedCap or eRedCap to a new camping cell, a second instruction to support RedCap or eRedCap can be reported to the network device corresponding to the new camping cell.

[0157] The new host cell can be an NR cell or a non-NR cell. The new host cell can be the same cell as the currently host cell or a cell under the same network device.

[0158] For example, when a RedCap terminal switches from a target cell that supports RedCap to a new camping cell, it can report a second instruction to the network device corresponding to the new camping cell that supports RedCap.

[0159] For example, if a RedCap terminal returns to the currently camped cell from a target cell that supports RedCap, it can report a second instruction to the first network device to support RedCap.

[0160] Referring to Figure 8, as shown in Figure 10, after the RedCap terminal switches back to LTE cell 1 from NR cell 1 that supports RedCap, eNB1 sends a capability query request to the RedCap terminal. In response to the capability query request, the RedCap terminal reports a second indication of RedCap support to eNB1.

[0161] Referring to Figure 8, as shown in Figure 11, after the RedCap terminal switches from NR cell 1, which supports RedCap, to LTE cell 2, the network device eNB2 corresponding to LTE cell 2 sends a capability query request to the RedCap terminal. In response to the capability query request, the RedCap terminal reports a second indication that it supports RedCap to eNB2.

[0162] For example, when an eRedCap terminal switches from a target cell that supports eRedCap to a new camping cell, it can report a second indication that it supports eRedCap to the network device corresponding to the new camping cell.

[0163] For example, if an eRedCap terminal returns to the currently camped cell from a target cell that supports eRedCap, it can report a second instruction to the first network device that supports eRedCap.

[0164] The following describes a communication device used to perform the above communication method.

[0165] It is understood that, in order to achieve the above-mentioned functions, the communication device includes hardware and / or software modules that perform the respective functions. Based on the algorithm steps of the examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0166] This application embodiment can divide the communication device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0167] When dividing each function into modules according to its corresponding function.

[0168] Figure 12 shows a possible configuration of the communication device involved in the above embodiments. The device can be a terminal, a module applied to the terminal (such as a processor, chip, or chip system), or a logic node, logic module, or software capable of implementing all or part of the terminal functions. As shown in Figure 12, the communication device 1200 may include a processing unit 1201 and a transceiver unit 1202.

[0169] Processing unit 1201 is used to determine, in the idle state, whether at least one NR neighbor cell of the currently camped cell supports RedCap or eRedCap.

[0170] Transceiver unit 1202 is configured to report a first indication that RedCap or eRedCap is not supported to a first network device in a connected state when each of the at least one NR neighboring cells does not support RedCap or eRedCap, wherein the first network device is the network device corresponding to the currently camped cell.

[0171] In one possible implementation, the transceiver unit 1202 is further configured to: switch from the currently camped cell to the target cell in the connected state, and report the first instruction to the second network device, wherein the second network device is the network device corresponding to the target cell.

[0172] In one possible implementation, the transceiver unit 1202 is further configured to: report a second indication of supporting RedCap or eRedCap to the first network device in the connected state when there is a neighboring cell supporting RedCap or eRedCap in at least one of the NR neighboring cells; perform RRC reconstruction to access the NR cell that does not support RedCap or eRedCap; and report the first indication to a third network device, wherein the third network device is the network device corresponding to the NR cell.

[0173] In one possible implementation, the transceiver unit 1202 is specifically used to: immediately access the NR cell when the NR cell is found during the RRC reconstruction process.

[0174] In one possible implementation, the processing unit 1201 is specifically used to: receive a system message in the idle state; and determine, based on the system message, whether the at least one NR neighbor cell supports RedCap or eRedCap.

[0175] This application also provides a chip, which can be the chip of the aforementioned communication device. Figure 13 shows a schematic diagram of the structure of a chip 1300. The chip 1300 includes one or more processors 1301 and interface circuits 1302. Optionally, the chip 1300 may also include a bus 1303.

[0176] Processor 1301 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above communication method can be completed through the integrated logic circuitry in the hardware of processor 1301 or through software instructions.

[0177] Optionally, the processor 1301 described above may be a general-purpose processor, a digital signal processing (DSP) processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the various methods and steps disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor.

[0178] The interface circuit 1302 can be used to send or receive data, instructions or information. The processor 1301 can use the data, instructions or other information received by the interface circuit 1302 to process the data, instructions or other information, and can send the processed information out through the interface circuit 1302.

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

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

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

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

[0183] Figure 14 is a schematic diagram of an electronic device provided in an embodiment of this application. The electronic device can be a communication device, a chip in the communication device, or a functional module. As shown in Figure 14, the electronic device 1400 includes a processor 1401, a transceiver 1402, and a communication line 1403.

[0184] The processor 1401 is used to execute any step of the communication method provided in the embodiments of this application, and in the process of executing any step of the communication method provided in the embodiments of this application, it can selectively call the transceiver 1402 and the communication line 1403 to complete the corresponding operation.

[0185] Furthermore, the electronic device 1400 may also include a memory 1404. The processor 1401, the memory 1404, and the transceiver 1402 can be connected via a communication line 1403.

[0186] The processor 1401 can be a processor, a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor 1401 can also be other devices with processing capabilities, such as circuits, devices, or software modules, without limitation.

[0187] Transceiver 1402 is used to communicate with other devices or other communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. Transceiver 1402 can be a module, circuit, transceiver, or any device capable of enabling communication.

[0188] The transceiver 1402 is mainly used for sending and receiving commands and information, and may include a transmitter and a receiver to send and receive commands and information, respectively; operations other than sending and receiving commands and information are implemented by the processor.

[0189] Communication line 1403 is used to transmit information between the various components included in electronic device 1400.

[0190] In one design, the processor can be viewed as a logic circuit, and the transceiver as an interface circuit.

[0191] Memory 1404 is used to store instructions. These instructions can be computer programs.

[0192] The memory 1404 can be volatile memory or non-volatile memory, or it can include both. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM). Memory 1404 can also be a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices. It should be noted that the memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0193] It should be noted that the memory 1404 can exist independently of the processor 1401, or it can be integrated with the processor 1401. The memory 1404 can be used to store instructions, program code, or some data, etc. The memory 1404 can be located inside or outside the electronic device 1400, without limitation. The processor 1401 is used to execute the instructions stored in the memory 1404 to implement the method provided in the above embodiments of this application.

[0194] In one example, processor 1401 may include one or more processor cores, such as processor core 0 and processor core 1 in Figure 14.

[0195] As an alternative implementation, the electronic device 1400 may include multiple processors, for example, in addition to processor 1401 in FIG. 14, it may also include processor 1407.

[0196] As an optional implementation, the electronic device 1400 also includes an output device 1405 and an input device 1406. For example, the input device 1406 is a device such as a keyboard, mouse, microphone, or joystick, and the output device 1405 is a device such as a display screen or speaker.

[0197] It should be noted that the electronic device 1400 can be a chip system or a device with a similar structure to that shown in Figure 14. The chip system can be composed of chips or may include chips and other discrete components. Actions, terms, etc., involved in the various embodiments of this application can be referenced interchangeably without limitation. The message names or parameter names in the messages used for interaction between devices in the embodiments of this application are merely examples; other names may be used in specific implementations without limitation. Furthermore, the composition structure shown in Figure 14 does not constitute a limitation on the electronic device 1400. In addition to the components shown in Figure 14, the electronic device 1400 may include more or fewer components than those shown in Figure 14, or combine certain components, or have different component arrangements.

[0198] The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits, mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), p-type metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0199] This application also provides a communication device, which includes at least one processor. When the at least one processor executes program code or instructions, it implements the aforementioned method steps to achieve the communication method in the above embodiments.

[0200] Optionally, the device may further include at least one memory for storing the program code or instructions.

[0201] This application also provides a computer storage medium storing computer instructions. When the computer instructions are executed on a communication device, the communication device performs the aforementioned related method steps to implement the communication method in the above embodiments.

[0202] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the communication method described in the above embodiments.

[0203] This application also provides a communication device, which may specifically be a chip, integrated circuit, component, or module. Specifically, the device may include a connected processor and a memory for storing instructions, or the device may include at least one processor for fetching instructions from external memory. When the device is running, the processor can execute instructions to cause the chip to perform the communication methods described in the above-described method embodiments.

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

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

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

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

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

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

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

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

Claims

1. A communication method, characterized in that, include: In idle state, determine whether at least one new air interface NR neighbor cell of the currently camped cell supports RedCap or enhanced RedCap; If none of the at least one NR neighboring cells support RedCap or eRedCap, a first indication that RedCap or eRedCap is not supported is reported to a first network device in connected state, wherein the first network device is the network device corresponding to the currently camped cell.

2. The method according to claim 1, characterized in that, The method further includes: In the connected state, when switching from the current cell to the target cell, the first instruction is reported to the second network device, which is the network device corresponding to the target cell.

3. The method according to claim 1 or 2, characterized in that, The method further includes: If a neighboring cell in at least one of the NR neighboring cells supports RedCap or eRedCap, a second indication of support for RedCap or eRedCap is reported to the first network device in the connected state. Perform Radio Resource Control (RRC) reconstruction to access NR cells that do not support RedCap or eRedCap; The first instruction is reported to a third network device, which is the network device corresponding to the NR cell.

4. The method according to claim 3, characterized in that, The process of performing RRC reconstruction to access NR cells that do not support RedCap or eRedCap includes: When the NR cell is found during the RRC reconstruction process, the user immediately accesses the NR cell.

5. The method according to any one of claims 1 to 4, characterized in that, The step of determining whether at least one NR neighbor cell of the currently camped cell supports RedCap or eRedCap in the idle state includes: Receive system messages in the idle state; The system message determines whether the at least one NR neighbor cell supports RedCap or eRedCap.

6. A communication device, characterized in that, include: Processing unit and transceiver unit; The processing unit is used to determine, in the idle state, whether at least one NR neighbor cell of the currently camped cell supports RedCap or eRedCap; The transceiver unit is configured to, in a connected state, report a first indication that RedCap or eRedCap is not supported to a first network device when none of the at least one NR neighboring cells support RedCap or eRedCap, wherein the first network device is the network device corresponding to the currently camped cell.

7. The apparatus according to claim 6, characterized in that, The transceiver unit is also used for: In the connected state, when switching from the current cell to the target cell, the first instruction is reported to the second network device, which is the network device corresponding to the target cell.

8. The apparatus according to claim 6 or 7, characterized in that, The transceiver unit is also used for: If a neighboring cell in at least one of the NR neighboring cells supports RedCap or eRedCap, a second indication of support for RedCap or eRedCap is reported to the first network device in the connected state. Perform RRC reconstruction to access NR cells that do not support RedCap or eRedCap; The first instruction is reported to a third network device, which is the network device corresponding to the NR cell.

9. The apparatus according to claim 8, characterized in that, The transceiver unit is specifically used for: When the NR cell is found during the RRC reconstruction process, the user immediately accesses the NR cell.

10. The apparatus according to any one of claims 6 to 9, characterized in that, The processing unit is specifically used for: Receive system messages in the idle state; The system message determines whether the at least one NR neighbor cell supports RedCap or eRedCap.

11. A communication device comprising at least one processor and a memory, characterized in that, The at least one processor executes a program or instructions stored in a memory to cause the communication device to implement the method of any one of claims 1 to 5.

12. A computer-readable storage medium for storing a computer program, characterized in that, When the computer program is run on a computer or processor, it causes the computer or processor to perform the method of any one of claims 1 to 5.

13. A computer program product, the computer program product comprising instructions, characterized in that, When the instructions are executed on a computer or processor, the computer or processor causes the computer or processor to perform the method of any one of claims 1 to 5.

Images